Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nNo Description Provided
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ObservationMethod where concept is-a _VerificationMethodRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | NI | NoInformation | \n \n Description:The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value. \r\n\n |
| 2 | INV | invalid | \n \n Description:The value as represented in the instance is not a member of the set of permitted data values in the constrained value domain of a variable. \r\n\n |
| 3 | DER | derived | \n \n Description:An actual value may exist, but it must be derived from the provided information (usually an EXPR generic data type extension will be used to convey the derivation expressionexpression . \r\n\n |
| 3 | OTH | other | \n \n Description:The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). \r\n\n \n Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. \r\n\n With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. \r\n\n |
| 4 | NINF | negative infinity | \n Negative infinity of numbers. \r\n\n |
| 4 | PINF | positive infinity | \n Positive infinity of numbers. \r\n\n |
| 3 | UNC | un-encoded | \n \n Description: The actual value has not yet been encoded within the approved value domain. \r\n\n \n Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM. \r\n\n \n Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. \r\n\n Data type properties such as original text and translations may be present when this null flavor is included. \r\n\n |
| 2 | MSK | masked | \n There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information. \r\n\n Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail. \r\n\n |
| 2 | NA | not applicable | \n Known to have no proper value (e.g., last menstrual period for a male). \r\n\n |
| 2 | UNK | unknown | \n \n Description:A proper value is applicable, but not known. \r\n\n \n Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: \r\n\n \n Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown')\n Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)\n \n |
| 3 | ASKU | asked but unknown | \n Information was sought but not found (e.g., patient was asked but didn't know) \r\n\n |
| 4 | NAV | temporarily unavailable | \n Information is not available at this time but it is expected that it will be available later. \r\n\n |
| 3 | NASK | not asked | \n This information has not been sought (e.g., patient was not asked) \r\n\n |
| 3 | NAVU | Not available | \n Information is not available at this time (with no expectation regarding whether it will or will not be available in the future). \r\n\n |
| 4 | NAV | ||
| 3 | QS | Sufficient Quantity | \n \n Description:The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. e.g. 'Add 10mg of ingredient X, 50mg of ingredient Y, and sufficient quantity of water to 100mL.' The null flavor would be used to express the quantity of water. \r\n\n |
| 3 | TRC | trace | \n The content is greater than zero, but too small to be quantified. \r\n\n |
| 1 | NP | not present | \n Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default, or no-information (NI) as the default of all defaults. \r\n\n |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | ART | act relationship type | \n \n Description: A directed association between a source Act and a target Act. \r\n\n \n Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute) \r\n\n |
| 2 | (_ActClassTemporallyPertains) Abstract | ||
| 2 | (_ActRelationshipAccounting) Abstract | \n Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. \r\n\n | |
| 3 | (_ActRelationshipCostTracking) Abstract | \n Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. \r\n\n | |
| 4 | CHRG | has charge | \n A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service. \r\n\n The financial transaction will define the charge (bill) for delivery or performance of the service. \r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. \r\n\n |
| 4 | COST | has cost | \n A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service. \r\n\n The financial transaction will define the cost of delivery or performance of the service. \r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. \r\n\n |
| 3 | (_ActRelationshipPosting) Abstract | \n Expresses values for describing the relationship between a FinancialTransaction and an Account. \r\n\n | |
| 4 | CREDIT | has credit | \n A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance. \r\n\n |
| 4 | DEBIT | has debit | \n A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance. \r\n\n |
| 2 | (_ActRelationshipConditional) Abstract | \n Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred \r\n\n | |
| 3 | CIND | has contra-indication | \n A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used. \r\n\n |
| 3 | PRCN | has pre-condition | \n A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable. \r\n\n |
| 3 | RSON | has reason | \n \n Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication. \r\n\n \n Discussion: In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship. \r\n\n |
| 4 | BLOCK | blocks | \n \n Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring. \r\n\n |
| 4 | DIAG | diagnoses | \n \n Description: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 4 | IMM | immunization against | \n \n Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease) \r\n\n |
| 5 | ACTIMM | active immunization against | \n \n Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease) \r\n\n |
| 5 | PASSIMM | passive immunization against | \n \n Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease). \r\n\n |
| 4 | MITGT | mitigates | \n The source act removes or lessens the occurrence or effect of the target act. \r\n\n |
| 5 | RCVY | recovers | \n \n Definition: The source act is performed to recover from the effects of the target act. \r\n\n |
| 4 | PRYLX | prophylaxis of | \n \n Description: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 4 | TREAT | treats | \n \n Description: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 5 | ADJUNCT | adjunctive treatment | \n \n Description: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified. \r\n\n |
| 5 | MTREAT | maintenance treatment | \n \n Description: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 5 | PALLTREAT | palliates | \n \n Description: The source act is intended to provide palliation for the effects of the target act. \r\n\n |
| 5 | SYMP | symptomatic relief | \n \n Description: The source act is intented to provide symptomatic relief for the effects of the target act. \r\n\n |
| 3 | TRIG | has trigger | \n A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified. \r\n\n \n Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded. \r\n\n |
| 2 | (_ActRelationshipTemporallyPertains) Abstract | \n Abstract collector for ActRelationhsip types that relate two acts by their timing. \r\n\n | |
| 3 | (_ActRelationshipTemporallyPertainsApproximates) Abstract | \n Abstract collector for ActRelationship types that relate two acts by their approximate timing. \r\n\n | |
| 4 | ENE | ends near end | \n A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is ENS \r\n\n |
| 5 | ECW | ends concurrent with | \n A relationship in which the source act's effective time ends with the end of the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 6 | CONCURRENT | concurrent with | \n A relationship in which the source act's effective time is the same as the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 6 | SBSECWE | starts before start of, ends with | \n The source Act starts before the start of the target Act, and ends with the target Act. \r\n\n \n UsageNote: Inverse code is SASECWE\n \r\n\n |
| 4 | ENS | ends near start | \n A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is ENE \r\n\n |
| 5 | ECWS | ends concurrent with start of | \n The source Act ends when the target act starts (i.e. if we say "ActOne ECWS ActTwo", it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SCWE\n \r\n\n |
| 4 | SNE | starts near end | \n A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is SNS \r\n\n |
| 5 | SCWE | starts concurrent with end of | \n The source Act starts when the target act ends (i.e. if we say "ActOne SCWE ActTwo", it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SBSECWS\n \r\n\n |
| 4 | SNS | starts near start | \n A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is SNE \r\n\n |
| 5 | SCW | starts concurrent with | \n A relationship in which the source act's effective time starts with the start of the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 6 | CONCURRENT | ||
| 6 | SCWSEBE | starts with. ends before end of | \n The source Act starts with.the target Act and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SCWSEAE\n \r\n\n |
| 6 | SCWSEAE | starts with, ends after end of | The source Act starts with the target Act, and ends after the end of the target Act. |
| 3 | EAS | ends after start of | \n A relationship in which the source act ends after the target act starts. \r\n\n \n UsageNote: Inverse code is SBE\n \r\n\n |
| 4 | EAE | ends after end of | \n A relationship in which the source act ends after the target act ends. \r\n\n \n UsageNote: Inverse code is EBE\n \r\n\n |
| 5 | SASEAE | starts after start of, ends after end of | \n The source Act starts after start of the target Act and ends after end of the target Act. \r\n\n \n UsageNote: Inverse code is SBSEBE\n \r\n\n |
| 6 | SBEEAE | contains end of | \n The source Act contains the end of the target Act. \r\n\n \n UsageNote: Inverse code is EDU\n \r\n\n |
| 7 | SASSBEEAS | start after start of, contains end of | \n The source Act start after the start of the target Act, and contains the end of the target Act. \r\n\n \n UsageNote: Inverse code is SBSEASEBE\n \r\n\n |
| 7 | SBSEAE | contains time of | \n The source Act contains the time of the target Act. \r\n\n \n UsageNote: Inverse code is DURING\n \r\n\n |
| 7 | SCWSEAE | ||
| 6 | SASSBEEAS | ||
| 4 | SAS | starts after start of | \n The source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SBS\n \r\n\n |
| 5 | SASEAE | ||
| 5 | SAE | starts after end of | \n A relationship in which the source act starts after the target act ends. \r\n\n \n UsageNote: Inverse code is EBS\n \r\n\n |
| 5 | DURING | occurs during | \n A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBSEAE\n \r\n\n |
| 5 | SASECWE | starts after start of, ends with | \n The source Act starts after start of the target Act, and ends with the target Act. \r\n\n \n UsageNote: Inverse code is SBSECWE\n \r\n\n |
| 3 | EASORECWS | ends after or concurrent with start of | \n A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EBSORECWS \r\n\n |
| 4 | EAS | ||
| 4 | EAEORECW | ends after or concurrent with end of | \n A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EBEORECW \r\n\n |
| 5 | EAE | ||
| 5 | ECW | ||
| 4 | ECWS | ||
| 3 | INDEPENDENT | independent of time of | \n The source Act is independent of the time of the target Act. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 3 | SAEORSCWE | starts after or concurrent with end of | \n A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SBEORSCWE \r\n\n |
| 4 | SCWE | ||
| 4 | SAE | ||
| 3 | SASORSCW | starts after or concurrent with start of | \n A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SBSORSCW \r\n\n |
| 4 | SAS | ||
| 4 | SCW | ||
| 3 | SBEORSCWE | starts before or concurrent with end of | \n A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SAEORSCWE \r\n\n |
| 4 | OVERLAP | overlaps with | \n A relationship in which the source act's effective time overlaps the target act's effective time in any way. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 5 | ECW | ||
| 5 | EDU | ends during | \n A relationship in which the source act ends within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBEEAE\n \r\n\n |
| 6 | SBSEASEBE | contains start of, ends before end of | \n The source Act contains the start of the target Act, and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SASSBEEAS\n \r\n\n |
| 6 | SCWSEBE | ||
| 5 | SBEEAE | ||
| 5 | SBSEAS | contains start of | \n The source Act contains the start of the target Act. \r\n\n \n UsageNote: Inverse code is SDU\n \r\n\n |
| 6 | SBSECWE | ||
| 6 | SBSEASEBE | ||
| 6 | SBSEAE | ||
| 5 | SCW | ||
| 5 | SCWE | ||
| 5 | SDU | starts during | \n A relationship in which the source act starts within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBSEAS\n \r\n\n |
| 6 | SASSBEEAS | ||
| 4 | SBE | starts before end of | The source Act starts before the end of the target Act (i.e. if we say "ActOne SBE ActTwo", it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is EAS\n \r\n\n |
| 5 | EBE | ends before end of | The source Act ends before the end of the target Act (i.e. if we say "ActOne EBE ActTwo", it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is EAE\n \r\n\n |
| 6 | SBSEBE | starts before start of, ends before end of | \n The source Act starts before the start of the target Act, and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SASEAE\n \r\n\n |
| 7 | SBSEASEBE | ||
| 7 | EBSORECWS | ends before or concurrent with start of | \n A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EASORECWS \r\n\n |
| 8 | ECWS | ||
| 8 | EBS | ends before start of | \n A relationship in which the source act ends before the target act starts. \r\n\n \n UsageNote: Inverse code is SAE\n \r\n\n |
| 5 | SBSEASEBE | ||
| 5 | SCWSEBE | ||
| 5 | EBEORECW | ends before or concurrent with end of | \n A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EAEORECW \r\n\n |
| 6 | ECW | ||
| 6 | EBE | ||
| 5 | SBSORSCW | starts before or concurrent with start of | \n A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SASORSCW \r\n\n |
| 6 | SCW | ||
| 6 | SBS | starts before start of | \n A relationship in which the source act begins before the target act begins. \r\n\n \n UsageNote: Inverse code is SAS\n \r\n\n |
| 7 | SBSEBE | ||
| 7 | SBSEAS | ||
| 2 | AUTH | authorized by | \n A relationship in which the target act authorizes or certifies the source act. \r\n\n |
| 2 | CAUS | is etiology for | \n \n Description: An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act. \r\n\n \n Examples:\n \r\n\n \n a growth of Staphylococcus aureus may be considered the cause of an abscess\n contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced\n lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed\n \n |
| 2 | COMP | has component | \n The target act is a component of the source act, with no semantics regarding composition or aggregation implied. \r\n\n |
| 3 | CTRLV | has control variable | \n A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation. \r\n\n |
| 3 | MBR | has member | \n The target Acts are aggregated by the source Act. Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source. \r\n\n \n UsageNotes: This explicitly represents the conventional notion of aggregation. The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts). \r\n\n It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST\n \r\n\n |
| 4 | STEP | has step | \n A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently. \r\n\n \n UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode. \r\n\n \n OpenIssue: Need Additional guidelines on when each approach should be used. \r\n\n |
| 5 | ARR | arrival | \n The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act. \r\n\n |
| 5 | DEP | departure | \n The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act. \r\n\n |
| 3 | PART | has part | \n The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act. \r\n\n \n UsageNote: In UML 1.1, this is a "composition" defined as: \n "A form of aggregation with strong ownership and coincident lifetime as part of the whole. Parts with non-fixed multiplicity may be created after the composite itself, but once created they live and die with it (i.e., they share lifetimes). Such parts can also be explicitly removed before the death of the composite. Composition may be recursive."\n \r\n\n |
| 2 | COVBY | covered by | \n A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy. \r\n\n |
| 2 | DRIV | is derived from | \n Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts. \r\n\n |
| 2 | ELNK | episodeLink | \n Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter. \r\n\n |
| 2 | EVID | provides evidence for | \n Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc. \r\n\n \n Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies. \r\n\n |
| 2 | EXACBY | exacerbated by | \n \n Description:The source act is aggravated by the target act. (Example "chest pain" EXACBY "exercise") \r\n\n |
| 2 | EXPL | has explanation | \n This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition. \r\n\n |
| 2 | INTF | interfered by | \n the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act. \r\n\n \n UsageNote: This provides the semantics to document barriers to care \r\n\n |
| 2 | ITEMSLOC | items located | \n Items located \r\n\n |
| 2 | LIMIT | limited by | \n A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood. \r\n\n |
| 2 | META | has metadata | \n \n Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act. \r\n\n \n Constraint: Source act must have either a mood code that is not "EVN" (event) or its "isCriterion" attribute must set to "true". Target act must be an Act with a mood code of EVN and with isCriterionInd attribute set to "true". \r\n\n |
| 2 | MFST | is manifestation of | \n An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation. \r\n\n |
| 2 | NAME | assigns name | \n Used to assign a "name" to a condition thread. Source is a condition node, target can be any service. \r\n\n |
| 2 | OUTC | has outcome | \n An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called "post-conditional".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment. \r\n\n |
| 3 | (_ActRelationsipObjective) Abstract | \n The target act is a desired outcome of the source act. Source is any act (typically an intervention). Target must be an observation in criterion mood. \r\n\n | |
| 4 | OBJC | has continuing objective | \n A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood. \r\n\n |
| 4 | OBJF | has final objective | \n A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood. \r\n\n |
| 3 | GOAL | has goal | \n A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood. \r\n\n |
| 3 | RISK | has risk | \n A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed. \r\n\n |
| 2 | PERT | has pertinent information | \n This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays. \r\n\n |
| 2 | PREV | has previous instance | \n A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services. \r\n\n |
| 2 | REFR | refers to | \n A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee. \r\n\n |
| 3 | USE | uses | \n Indicates that the source act makes use of (or will make use of) the information content of the target act. \r\n\n \n UsageNotes: A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate. \r\n\n \n Rationale: There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference. \r\n\n |
| 2 | REFV | has reference values | \n Reference ranges are essentially descriptors of a class of result values assumed to be "normal", "abnormal", or "critical." Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results. \r\n\n |
| 2 | RELVBY | relieved by | \n \n Description:The source act is wholly or partially alleviated by the target act. (Example "chest pain" RELVBY "sublingual nitroglycerin administration") \r\n\n |
| 2 | SEQL | is sequel | \n An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation. \r\n\n |
| 3 | APND | is appendage | \n An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered. \r\n\n |
| 3 | BSLN | has baseline | \n Indicates that the target observation(s) provide an initial reference for the source observation or observation group. \r\n\n \n UsageConstraints: Both source and target must be Observations or specializations thereof. \r\n\n |
| 3 | COMPLY | complies with | \n \n Description:The source act complies with, adheres to, conforms to, or is permissible under (in whole or in part) the policy, contract, agreement, law, conformance criteria, certification guidelines or requirement conveyed by the target act. \r\n\n Examples for compliance relationships are: audits of adherence with a security policy, certificate of conformance to system certification requirements, or consent directive in compliance with or permissible under a privacy policy. \r\n\n |
| 3 | DOC | documents | \n The source act documents the target act. \r\n\n |
| 3 | FLFS | fulfills | \n The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act. \r\n\n |
| 4 | OCCR | occurrence | \n The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the "completion track" but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa). \r\n\n |
| 4 | OREF | references order | \n Relates either an appointment request or an appointment to the order for the service being scheduled. \r\n\n |
| 4 | SCH | schedules request | \n Associates a specific time (and associated resources) with a scheduling request or other intent. \r\n\n |
| 3 | GEN | has generalization | \n The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic). \r\n\n |
| 3 | GEVL | evaluates (goal) | \n A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a "goal distance" (e.g., goal to observation) can be "calculated" and need not be sent explicitly. \r\n\n |
| 3 | INST | instantiates (master) | \n Used to capture the link between a potential service ("master" or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master's defaults. \r\n\n |
| 3 | MOD | modifies | \n Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target). \r\n\n \n Usage:The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead. \r\n\n Name from source to target = "modifiesPrior" \r\n\n Name from target to source = "modifiesByNew" \r\n\n |
| 3 | MTCH | matches (trigger) | \n A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is "observation of pain" and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger. \r\n\n |
| 3 | OPTN | has option | \n A relationship between a source Act that provides more detailed properties to the target Act. \r\n\n The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements. \r\n\n The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements. \r\n\n Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. \r\n\n |
| 3 | RCHAL | re-challenge | \n \n Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated. \r\n\n |
| 3 | REV | reverses | \n A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. \r\n\n Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction. \r\n\n Constraints: the "completion track" mood of the target Act must be equally or more "actual" than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT. \r\n\n |
| 3 | RPLC | replaces | \n A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type. \r\n\n |
| 3 | SUCC | succeeds | \n \n Definition: A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act. \r\n\n |
| 3 | UPDT | updates (condition) | \n A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread. \r\n\n |
| 3 | XCRPT | Excerpts | \n The source is an excerpt from the target. \r\n\n |
| 4 | VRXCRPT | Excerpt verbatim | \n The source is a direct quote from the target. \r\n\n |
| 3 | XFRM | transformation | \n Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.) \r\n\n |
| 2 | SPRT | has support | \n Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post). \r\n\n |
| 3 | SPRTBND | has bounded support | \n A specialization of "has support" (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the "ST elevation" observation -- the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general "has support" relation is used. Likewise, if a ROI on an image defines the true bounds of a "1st degree burn", the relation "has bounded support" is used; but if the ROI only points to the approximate area of the burn, the general "has support" relation is used. \r\n\n |
| 2 | SUBJ | has subject | \n Relates an Act to its subject Act that the first Act is primarily concerned with. \r\n\n Examples \r\n\n \n \n The first Act may be a ControlAct manipulating the subject Act \r\n\n \n \n The first act is a region of interest (ROI) that defines a region within the subject Act. \r\n\n \n \n The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. \r\n\n \n \n Constraints \r\n\n An Act may have multiple subject acts. \r\n\n Rationale \r\n\n The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship. \r\n\n |
| 3 | QUALF | has qualifier | \n The target observation qualifies (refines) the semantics of the source observation. \r\n\n \n UsageNote: This is not intended to replace concept refinement and qualification via vocabulary. It is used when there are multiple components which together provide the complete understanding of the source Act. \r\n\n |
| 2 | SUMM | summarized by | \n An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period. \r\n\n |
| 2 | VALUE | has value | \n \n Description:Indicates that the target Act represents the result of the source observation Act. \r\n\n \n FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified \r\n\n \n UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute. For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation. \r\n\n The valueNegationInd attribute on the source Act has the same semantics of "negated finding" when it applies to the target of a VALUE ActRelationship as it does to the value attribute. On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding. Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd. \r\n\n \n OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation. \r\n\n |
| 1 | CURE | curative indication | |
| 1 | CURE.ADJ | adjunct curative indication | |
| 1 | MTGT.ADJ | adjunct mitigation | |
| 1 | RACT | ||
| 1 | SUGG |
Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Examples:\nprohibit redisclosure without consent directive
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a RefrainPolicyRelease Date: 2018-08-12
\r\nNo Description Provided
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActReason where concept is-a _SubstanceAdminSubstitutionReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReason| Code | Display | |
| _SubstanceAdminSubstitutionReason | SubstanceAdminSubstitutionReason | SubstanceAdminSubstitutionReason |
A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind of device is identified by the code attribute inherited from Entity. Usage:\nThis includes durable (reusable) medical equipment as well as disposable equipment.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityClass where concept is-a DEVRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nA named tag set for metadata used to populate a security category label field that "segments" an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System) Usage Note:\nThis is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk."
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a COMPTRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_ActAccountCode) Abstract | \n An account represents a grouping of financial transactions that are tracked and reported together with a single balance. \t \tExamples of account codes (types) are Patient billing accounts (collection of charges), Cost centers; Cash. \r\n\n | |
| 2 | ACCTRECEIVABLE | account receivable | \n An account for collecting charges, reversals, adjustments and payments, including deductibles, copayments, coinsurance (financial transactions) credited or debited to the account receivable account for a patient's encounter. \r\n\n |
| 2 | CASH | Cash | |
| 2 | CC | credit card | \n \n Description: Types of advance payment to be made on a plastic card usually issued by a financial institution used of purchasing services and/or products. \r\n\n |
| 3 | AE | American Express | |
| 3 | DN | Diner's Club | |
| 3 | DV | Discover Card | |
| 3 | MC | Master Card | |
| 3 | V | Visa | |
| 2 | PBILLACCT | patient billing account | \n An account representing charges and credits (financial transactions) for a patient's encounter. \r\n\n |
| 1 | (_ActAdjudicationCode) Abstract | \n Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results. \r\n\n | |
| 2 | (_ActAdjudicationGroupCode) Abstract | \n Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals). \r\n\n | |
| 3 | CONT | contract | \n Transaction counts and value totals by Contract Identifier. \r\n\n |
| 3 | DAY | day | \n Transaction counts and value totals for each calendar day within the date range specified. \r\n\n |
| 3 | LOC | location | \n Transaction counts and value totals by service location (e.g clinic). \r\n\n |
| 3 | MONTH | month | \n Transaction counts and value totals for each calendar month within the date range specified. \r\n\n |
| 3 | PERIOD | period | \n Transaction counts and value totals for the date range specified. \r\n\n |
| 3 | PROV | provider | \n Transaction counts and value totals by Provider Identifier. \r\n\n |
| 3 | WEEK | week | \n Transaction counts and value totals for each calendar week within the date range specified. \r\n\n |
| 3 | YEAR | year | \n Transaction counts and value totals for each calendar year within the date range specified. \r\n\n |
| 2 | AA | adjudicated with adjustments | \n The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges). \r\n\n Also includes the concept 'Adjudicate as zero' and items not covered under a particular Policy. \r\n\n Invoice element can be reversed (nullified). \r\n\n Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). \r\n\n |
| 3 | ANF | adjudicated with adjustments and no financial impact | \n The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges) without changing the amount. \r\n\n Invoice element can be reversed (nullified). \r\n\n Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). \r\n\n |
| 2 | AR | adjudicated as refused | \n The invoice element has passed through the adjudication process but payment is refused due to one or more reasons. \r\n\n Includes items such as patient not covered, or invoice element is not constructed according to payer rules (e.g. 'invoice submitted too late'). \r\n\n If one invoice element line item in the invoice element structure is rejected, the remaining line items may not be adjudicated and the complete group is treated as rejected. \r\n\n A refused invoice element can be forwarded to the next payer (for Coordination of Benefits) or modified and resubmitted to refusing payer. \r\n\n Invoice element cannot be reversed (nullified) as there is nothing to reverse. \r\n\n Recommend that the invoice element is not saved for DUR (Drug Utilization Reporting). \r\n\n |
| 2 | AS | adjudicated as submitted | \n The invoice element was/will be paid exactly as submitted, without financial adjustment(s). \r\n\n If the dollar amount stays the same, but the billing codes have been amended or financial adjustments have been applied through the adjudication process, the invoice element is treated as "Adjudicated with Adjustment". \r\n\n If information items are included in the adjudication results that do not affect the monetary amounts paid, then this is still Adjudicated as Submitted (e.g. 'reached Plan Maximum on this Claim'). \r\n\n Invoice element can be reversed (nullified). \r\n\n Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). \r\n\n |
| 1 | (_ActAdjudicationResultActionCode) Abstract | \n Actions to be carried out by the recipient of the Adjudication Result information. \r\n\n | |
| 2 | DISPLAY | Display | \n The adjudication result associated is to be displayed to the receiver of the adjudication result. \r\n\n |
| 2 | FORM | Print on Form | \n The adjudication result associated is to be printed on the specified form, which is then provided to the covered party. \r\n\n |
| 1 | (_ActBillableModifierCode) Abstract | \n \n Definition:An identifying modifier code for healthcare interventions or procedures. \r\n\n | |
| 2 | CPTM | CPT modifier codes | \n \n Description:CPT modifier codes are found in Appendix A of CPT 2000 Standard Edition. \r\n\n |
| 2 | HCPCSA | HCPCS Level II and Carrier-assigned | \n \n Description:HCPCS Level II (HCFA-assigned) and Carrier-assigned (Level III) modifiers are reported in Appendix A of CPT 2000 Standard Edition and in the Medicare Bulletin. \r\n\n |
| 1 | (_ActBillingArrangementCode) Abstract | \n The type of provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider, over a specified period. \r\n\n | |
| 2 | BLK | block funding | \n A billing arrangement where a Provider charges a lump sum to provide a prescribed group (volume) of services to a single patient which occur over a period of time. Services included in the block may vary. \r\n\n This billing arrangement is also known as Program of Care for some specific Payors and Program Fees for other Payors. \r\n\n |
| 2 | CAP | capitation funding | \n A billing arrangement where the payment made to a Provider is determined by analyzing one or more demographic attributes about the persons/patients who are enrolled with the Provider (in their practice). \r\n\n |
| 2 | CONTF | contract funding | \n A billing arrangement where a Provider charges a lump sum to provide a particular volume of one or more interventions/procedures or groups of interventions/procedures. \r\n\n |
| 2 | FINBILL | financial | \n A billing arrangement where a Provider charges for non-clinical items. This includes interest in arrears, mileage, etc. Clinical content is not \tincluded in Invoices submitted with this type of billing arrangement. \r\n\n |
| 2 | ROST | roster funding | \n A billing arrangement where funding is based on a list of individuals registered as patients of the Provider. \r\n\n |
| 2 | SESS | sessional funding | \n A billing arrangement where a Provider charges a sum to provide a group (volume) of interventions/procedures to one or more patients within a defined period of time, typically on the same date. Interventions/procedures included in the session may vary. \r\n\n |
| 2 | FFS | fee for service | \n A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product. \r\n\n Fee for Service is used when an individual intervention/procedure/event is used for billing purposes. In other words, fees are associated with the intervention/procedure/event. For example, a specific CCI (Canadian Classification of Interventions) code has an associated fee and is used for billing purposes. \r\n\n |
| 3 | FFPS | first fill, part fill, partial strength | \n A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets) \r\n\n |
| 3 | FFCS | first fill complete, partial strength | \n A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | TFS | trial fill partial strength | \n A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 1 | (_ActBoundedROICode) Abstract | \n Type of bounded ROI. \r\n\n | |
| 2 | ROIFS | fully specified ROI | \n A fully specified bounded Region of Interest (ROI) delineates a ROI in which only those dimensions participate that are specified by boundary criteria, whereas all other dimensions are excluded. For example a ROI to mark an episode of "ST elevation" in a subset of the EKG leads V2, V3, and V4 would include 4 boundaries, one each for time, V2, V3, and V4. \r\n\n |
| 2 | ROIPS | partially specified ROI | \n A partially specified bounded Region of Interest (ROI) specifies a ROI in which at least all values in the dimensions specified by the boundary criteria participate. For example, if an episode of ventricular fibrillations (VFib) is observed, it usually doesn't make sense to exclude any EKG leads from the observation and the partially specified ROI would contain only one boundary for time indicating the time interval where VFib was observed. \r\n\n |
| 1 | (_ActCareProvisionCode) Abstract | \n \n Description:The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care. \r\n\n | |
| 2 | (_ActCredentialedCareCode) Abstract | \n \n Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements. \r\n\n \n Example:Hospital license; physician license; clinic accreditation. \r\n\n | |
| 3 | (_ActCredentialedCareProvisionPersonCode) Abstract | \n \n Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing individuals. \r\n\n | |
| 4 | CACC | certified anatomic pathology and clinical pathology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CAIC | certified allergy and immunology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CAMC | certified aerospace medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CANC | certified anesthesiology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CAPC | certified anatomic pathology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CBGC | certified clinical biochemical genetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCCC | certified clinical cytogenetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCGC | certified clinical genetics (M.D.) care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCPC | certified clinical pathology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCSC | certified colon and rectal surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CDEC | certified dermatology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CDRC | certified diagnostic radiology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CEMC | certified emergency medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CFPC | certified family practice care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CIMC | certified internal medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CMGC | certified clinical molecular genetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CNEC | certified neurology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board \r\n\n |
| 4 | CNMC | certified nuclear medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CNQC | certified neurology with special qualifications in child neurology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CNSC | certified neurological surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COGC | certified obstetrics and gynecology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COMC | certified occupational medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COPC | certified ophthalmology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COSC | certified orthopaedic surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COTC | certified otolaryngology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPEC | certified pediatrics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPGC | certified Ph.D. medical genetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPHC | certified public health and general preventive medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPRC | certified physical medicine and rehabilitation care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPSC | certified plastic surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPYC | certified psychiatry care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CROC | certified radiation oncology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CRPC | certified radiological physics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CSUC | certified surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CTSC | certified thoracic surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CURC | certified urology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CVSC | certified vascular surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | LGPC | licensed general physician care | \n \n Description:Scope of responsibility taken-on for physician care of a patient as defined by a governmental licensing agency. \r\n\n |
| 3 | (_ActCredentialedCareProvisionProgramCode) Abstract | \n \n Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing programs within organizations. \r\n\n | |
| 4 | AALC | accredited assisted living care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | AAMC | accredited ambulatory care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ABHC | accredited behavioral health care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ACAC | accredited critical access hospital care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ACHC | accredited hospital care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | AHOC | accredited home care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ALTC | accredited long term care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | AOSC | accredited office-based surgery care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | CACS | certified acute coronary syndrome care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CAMI | certified acute myocardial infarction care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CAST | certified asthma care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CBAR | certified bariatric surgery care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CCAD | certified coronary artery disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CCAR | certified cardiac care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CDEP | certified depression care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CDGD | certified digestive/gastrointestinal disorders care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CDIA | certified diabetes care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CEPI | certified epilepsy care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CFEL | certified frail elderly care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CHFC | certified heart failure care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CHRO | certified high risk obstetrics care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CHYP | certified hyperlipidemia care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CMIH | certified migraine headache care | \n \n Description:. \r\n\n |
| 4 | CMSC | certified multiple sclerosis care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | COJR | certified orthopedic joint replacement care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CONC | certified oncology care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | COPD | certified chronic obstructive pulmonary disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CORT | certified organ transplant care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CPAD | certified parkinsons disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CPND | certified pneumonia disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CPST | certified primary stroke center care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSDM | certified stroke disease management care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSIC | certified sickle cell care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSLD | certified sleep disorders care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSPT | certified spine treatment care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CTBU | certified trauma/burn center care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CVDC | certified vascular diseases care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CWMA | certified wound management care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CWOH | certified women's health care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 2 | (_ActEncounterCode) Abstract | \n Domain provides codes that qualify the ActEncounterClass (ENC) \r\n\n | |
| 3 | AMB | ambulatory | \n A comprehensive term for health care provided in a healthcare facility (e.g. a practitioneraTMs office, clinic setting, or hospital) on a nonresident basis. The term ambulatory usually implies that the patient has come to the location and is not assigned to a bed. Sometimes referred to as an outpatient encounter. \r\n\n |
| 3 | EMER | emergency | \n A patient encounter that takes place at a dedicated healthcare service delivery location where the patient receives immediate evaluation and treatment, provided until the patient can be discharged or responsibility for the patient's care is transferred elsewhere (for example, the patient could be admitted as an inpatient or transferred to another facility.) \r\n\n |
| 3 | FLD | field | \n A patient encounter that takes place both outside a dedicated service delivery location and outside a patient's residence. Example locations might include an accident site and at a supermarket. \r\n\n |
| 3 | HH | home health | \n Healthcare encounter that takes place in the residence of the patient or a designee \r\n\n |
| 3 | IMP | inpatient encounter | \n A patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients generally stay at least overnight and provided with room, board, and continuous nursing service. \r\n\n |
| 4 | ACUTE | inpatient acute | \n An acute inpatient encounter. \r\n\n |
| 4 | NONAC | inpatient non-acute | \n Any category of inpatient encounter except 'acute' \r\n\n |
| 3 | OBSENC | observation encounter | \n An encounter where the patient usually will start in different encounter, such as one in the emergency department (EMER) but then transition to this type of encounter because they require a significant period of treatment and monitoring to determine whether or not their condition warrants an inpatient admission or discharge. In the majority of cases the decision about admission or discharge will occur within a time period determined by local, regional or national regulation, often between 24 and 48 hours. \r\n\n |
| 3 | PRENC | pre-admission | \n A patient encounter where patient is scheduled or planned to receive service delivery in the future, and the patient is given a pre-admission account number. When the patient comes back for subsequent service, the pre-admission encounter is selected and is encapsulated into the service registration, and a new account number is generated. \r\n\n \n Usage Note: This is intended to be used in advance of encounter types such as ambulatory, inpatient encounter, virtual, etc. \r\n\n |
| 3 | SS | short stay | \n An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours. \r\n\n |
| 3 | VR | virtual | \n A patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone conference, email exchange, robotic surgery, and televideo conference. \r\n\n |
| 2 | (_ActMedicalServiceCode) Abstract | \n General category of medical service provided to the patient during their encounter. \r\n\n | |
| 3 | ALC | Alternative Level of Care | \n Provision of Alternate Level of Care to a patient in an acute bed. Patient is waiting for placement in a long-term care facility and is unable to return home. \r\n\n |
| 3 | CARD | Cardiology | \n Provision of diagnosis and treatment of diseases and disorders affecting the heart \r\n\n |
| 3 | CHR | Chronic | \n Provision of recurring care for chronic illness. \r\n\n |
| 3 | DNTL | Dental | \n Provision of treatment for oral health and/or dental surgery. \r\n\n |
| 3 | DRGRHB | Drug Rehab | \n Provision of treatment for drug abuse. \r\n\n |
| 3 | GENRL | General | \n General care performed by a general practitioner or family doctor as a responsible provider for a patient. \r\n\n |
| 3 | MED | Medical | \n Provision of diagnostic and/or therapeutic treatment. \r\n\n |
| 3 | OBS | Obstetrics | \n Provision of care of women during pregnancy, childbirth and immediate postpartum period. Also known as Maternity. \r\n\n |
| 3 | ONC | Oncology | \n Provision of treatment and/or diagnosis related to tumors and/or cancer. \r\n\n |
| 3 | PALL | Palliative | \n Provision of care for patients who are living or dying from an advanced illness. \r\n\n |
| 3 | PED | Pediatrics | \n Provision of diagnosis and treatment of diseases and disorders affecting children. \r\n\n |
| 3 | PHAR | Pharmaceutical | \n Pharmaceutical care performed by a pharmacist. \r\n\n |
| 3 | PHYRHB | Physical Rehab | \n Provision of treatment for physical injury. \r\n\n |
| 3 | PSYCH | Psychiatric | \n Provision of treatment of psychiatric disorder relating to mental illness. \r\n\n |
| 3 | SURG | Surgical | \n Provision of surgical treatment. \r\n\n |
| 1 | (_ActClaimAttachmentCategoryCode) Abstract | \n \n Description: Coded types of attachments included to support a healthcare claim. \r\n\n | |
| 2 | AUTOATTCH | auto attachment | \n \n Description: Automobile Information Attachment \r\n\n |
| 2 | DOCUMENT | document | \n \n Description: Document Attachment \r\n\n |
| 2 | HEALTHREC | health record | \n \n Description: Health Record Attachment \r\n\n |
| 2 | IMG | image attachment | \n \n Description: Image Attachment \r\n\n |
| 2 | LABRESULTS | lab results | \n \n Description: Lab Results Attachment \r\n\n |
| 2 | MODEL | model | \n \n Description: Digital Model Attachment \r\n\n |
| 2 | WIATTCH | work injury report attachment | \n \n Description: Work Injury related additional Information Attachment \r\n\n |
| 2 | XRAY | x-ray | \n \n Description: Digital X-Ray Attachment \r\n\n |
| 1 | (_ActConsentType) Abstract | \n \n Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research. \r\n\n | |
| 2 | ICOL | information collection | \n \n Definition: Consent to have healthcare information collected in an electronic health record. This entails that the information may be used in analysis, modified, updated. \r\n\n |
| 2 | IDSCL | information disclosure | \n \n Definition: Consent to have collected healthcare information disclosed. \r\n\n |
| 2 | INFA | information access | \n \n Definition: Consent to access healthcare information. \r\n\n |
| 3 | INFAO | access only | \n \n Definition: Consent to access or "read" only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way. This level ensures that data which is masked or to which access is restricted will not be. \r\n\n \n Example: Opened and then emailed or screen printed for use outside of the consent directive purpose. \r\n\n |
| 3 | INFASO | access and save only | \n \n Definition: Consent to access and save only, which entails that access to the saved copy will remain locked. \r\n\n |
| 2 | IRDSCL | information redisclosure | \n \n Definition: Information re-disclosed without the patient's consent. \r\n\n |
| 2 | RESEARCH | research information access | \n \n Definition: Consent to have healthcare information in an electronic health record accessed for research purposes. \r\n\n |
| 3 | RSDID | de-identified information access | \n \n Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes, but without consent to re-identify the information under any circumstance. \r\n\n |
| 3 | RSREID | re-identifiable information access | \n \n Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent. \r\n\n \n Example:: Where there is a need to inform the subject of potential health issues. \r\n\n |
| 1 | (_ActContainerRegistrationCode) Abstract | \n Constrains the ActCode to the domain of Container Registration \r\n\n | |
| 2 | ID | Identified | \n Used by one system to inform another that it has received a container. \r\n\n |
| 2 | IP | In Position | \n Used by one system to inform another that the container is in position for specimen transfer (e.g., container removal from track, pipetting, etc.). \r\n\n |
| 2 | L | Left Equipment | \n Used by one system to inform another that the container has been released from that system. \r\n\n |
| 2 | M | Missing | \n Used by one system to inform another that the container did not arrive at its next expected location. \r\n\n |
| 2 | O | In Process | \n Used by one system to inform another that the specific container is being processed by the equipment. It is useful as a response to a query about Container Status, when the specific step of the process is not relevant. \r\n\n |
| 2 | R | Process Completed | \n Status is used by one system to inform another that the processing has been completed, but the container has not been released from that system. \r\n\n |
| 2 | X | Container Unavailable | \n Used by one system to inform another that the container is no longer available within the scope of the system (e.g., tube broken or discarded). \r\n\n |
| 1 | (_ActControlVariable) Abstract | \n An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure. \r\n\n Control variables are forms of observations because just as with clinical observations, the Observation.code determines the parameter and the Observation.value assigns the value. While control variables sometimes can be observed (by noting the control settings or an actually measured feedback loop) they are not primary observations, in the sense that a control variable without a primary act is of no use (e.g., it makes no sense to record a blood pressure position without recording a blood pressure, whereas it does make sense to record a systolic blood pressure without a diastolic blood pressure). \r\n\n | |
| 2 | AUTO | auto-repeat permission | \n Specifies whether or not automatic repeat testing is to be initiated on specimens. \r\n\n |
| 2 | ENDC | endogenous content | \n A baseline value for the measured test that is inherently contained in the diluent. In the calculation of the actual result for the measured test, this baseline value is normally considered. \r\n\n |
| 2 | REFLEX | reflex permission | \n Specifies whether or not further testing may be automatically or manually initiated on specimens. \r\n\n |
| 1 | (_ActCoverageConfirmationCode) Abstract | \n Response to an insurance coverage eligibility query or authorization request. \r\n\n | |
| 2 | (_ActCoverageAuthorizationConfirmationCode) Abstract | \n Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside. \r\n\n | |
| 3 | AUTH | Authorized | \n Authorization approved and funds have been set aside to pay for specified healthcare service(s) and/or product(s) within defined criteria for the authorization. \r\n\n |
| 3 | NAUTH | Not Authorized | \n Authorization for specified healthcare service(s) and/or product(s) denied. \r\n\n |
| 2 | (_ActCoverageEligibilityConfirmationCode) Abstract | \n Indication of eligibility coverage for healthcare service(s) and/or product(s). \r\n\n | |
| 3 | ELG | Eligible | \n Insurance coverage is in effect for healthcare service(s) and/or product(s). \r\n\n |
| 3 | NELG | Not Eligible | \n Insurance coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility. \r\n\n |
| 1 | (_ActCoverageLimitCode) Abstract | \n Criteria that are applicable to the authorized coverage. \r\n\n | |
| 2 | (_ActCoverageQuantityLimitCode) Abstract | \n Maximum amount paid or maximum number of services/products covered; or maximum amount or number covered during a specified time period under the policy or program. \r\n\n | |
| 3 | COVPRD | coverage period | \n Codes representing the time period during which coverage is available; or financial participation requirements are in effect. \r\n\n |
| 3 | LFEMX | life time maximum | \n \n Definition: Maximum amount paid by payer or covered party; or maximum number of services or products covered under the policy or program during a covered party's lifetime. \r\n\n |
| 3 | NETAMT | Net Amount | \n Maximum net amount that will be covered for the product or service specified. \r\n\n |
| 3 | PRDMX | period maximum | \n \n Definition: Maximum amount paid by payer or covered party; or maximum number of services/products covered under the policy or program by time period specified by the effective time on the act. \r\n\n |
| 3 | UNITPRICE | Unit Price | \n Maximum unit price that will be covered for the authorized product or service. \r\n\n |
| 3 | UNITQTY | Unit Quantity | \n Maximum number of items that will be covered of the product or service specified. \r\n\n |
| 2 | COVMX | coverage maximum | \n \n Definition: Codes representing the maximum coverate or financial participation requirements. \r\n\n |
| 3 | LFEMX | ||
| 3 | PRDMX | ||
| 2 | (_ActCoveredPartyLimitCode) Abstract | \n Codes representing the types of covered parties that may receive covered benefits under a policy or program. \r\n\n | |
| 1 | (_ActCoverageTypeCode) Abstract | \n \n Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties. \r\n\n | |
| 2 | (_ActInsurancePolicyCode) Abstract | \n Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs. \r\n\n | |
| 3 | EHCPOL | extended healthcare | \n Private insurance policy that provides coverage in addition to other policies (e.g. in addition to a Public Healthcare insurance policy). \r\n\n |
| 3 | HSAPOL | health spending account | \n Insurance policy that provides for an allotment of funds replenished on a periodic (e.g. annual) basis. The use of the funds under this policy is at the \tdiscretion of the covered party. \r\n\n |
| 3 | AUTOPOL | automobile | \n Insurance policy for injuries sustained in an automobile accident. Will also typically covered non-named parties to the policy, such as pedestrians \tand passengers. \r\n\n |
| 4 | COL | collision coverage policy | \n \n Definition: An automobile insurance policy under which the insurance company will cover the cost of damages to an automobile owned by the named insured that are caused by accident or intentionally by another party. \r\n\n |
| 4 | UNINSMOT | uninsured motorist policy | \n \n Definition: An automobile insurance policy under which the insurance company will indemnify a loss for which another motorist is liable if that motorist is unable to pay because he or she is uninsured. Coverage under the policy applies to bodily injury damages only. Injuries to the covered party caused by a hit-and-run driver are also covered. \r\n\n |
| 3 | PUBLICPOL | public healthcare | \n Insurance policy funded by a public health system such as a provincial or national health plan. Examples include BC MSP (British Columbia \tMedical Services Plan) OHIP (Ontario Health Insurance Plan), NHS (National Health Service). \r\n\n |
| 4 | DENTPRG | dental program | \n \n Definition: A public or government health program that administers and funds coverage for dental care to assist program eligible who meet financial and health status criteria. \r\n\n |
| 4 | DISEASEPRG | public health program | \n \n Definition: A public or government health program that administers and funds coverage for health and social services to assist program eligible who meet financial and health status criteria related to a particular disease. \r\n\n \n Example: Reproductive health, sexually transmitted disease, and end renal disease programs. \r\n\n |
| 5 | CANPRG | women's cancer detection program | \n \n Definition: A program that provides low-income, uninsured, and underserved women access to timely, high-quality screening and diagnostic services, to detect breast and cervical cancer at the earliest stages. \r\n\n \n Example: To improve women's access to screening for breast and cervical cancers, Congress passed the Breast and Cervical Cancer Mortality Prevention Act of 1990, which guided CDC in creating the National Breast and Cervical Cancer Early Detection Program (NBCCEDP), which provides access to critical breast and cervical cancer screening services for underserved women in the United States. An estimated 7 to 10% of U.S. women of screening age are eligible to receive NBCCEDP services. Federal guidelines establish an eligibility baseline to direct services to uninsured and underinsured women at or below 250% of federal poverty level; ages 18 to 64 for cervical screening; ages 40 to 64 for breast screening. \r\n\n |
| 5 | ENDRENAL | end renal program | \n \n Definition: A public or government program that administers publicly funded coverage of kidney dialysis and kidney transplant services. \r\n\n Example: In the U.S., the Medicare End-stage Renal Disease program (ESRD), the National Kidney Foundation (NKF) American Kidney Fund (AKF) The Organ Transplant Fund. \r\n\n |
| 5 | HIVAIDS | HIV-AIDS program | \n \n Definition: Government administered and funded HIV-AIDS program for beneficiaries meeting financial and health status criteria. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. \r\n\n \n Example: In the U.S., the Ryan White program, which is administered by the Health Resources and Services Administration. \r\n\n |
| 4 | MANDPOL | mandatory health program | |
| 4 | MENTPRG | mental health program | \n \n Definition: Government administered and funded mental health program for beneficiaries meeting financial and mental health status criteria. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. \r\n\n \n Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA). \r\n\n |
| 4 | SAFNET | safety net clinic program | \n \n Definition: Government administered and funded program to support provision of care to underserved populations through safety net clinics. \r\n\n \n Example: In the U.S., safety net providers such as federally qualified health centers (FQHC) receive funding under PHSA Section 330 grants administered by the Health Resources and Services Administration. \r\n\n |
| 4 | SUBPRG | substance use program | \n \n Definition: Government administered and funded substance use program for beneficiaries meeting financial, substance use behavior, and health status criteria. Beneficiaries may be required to enroll as a result of legal proceedings. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. \r\n\n \n Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA). \r\n\n |
| 4 | SUBSIDIZ | subsidized health program | \n \n Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n |
| 5 | SUBSIDMC | subsidized managed care program | \n \n Definition: A government health program that provides coverage through managed care contracts for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n \n Discussion: The structure and business processes for underwriting and administering a subsidized managed care program is further specified by the Underwriter and Payer Role.class and Role.code. \r\n\n |
| 5 | SUBSUPP | subsidized supplemental health program | \n \n Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria for a supplemental health policy or program such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n \n Example: Supplemental health coverage program may cover the cost of a health program or policy financial participations, such as the copays and the premiums, and may provide coverage for services in addition to those covered under the supplemented health program or policy. In the U.S., Medicaid programs may pay the premium for a covered party who is also covered under the Medicare program or a private health policy. \r\n\n \n Discussion: The structure and business processes for underwriting and administering a subsidized supplemental retiree health program is further specified by the Underwriter and Payer Role.class and Role.code. \r\n\n |
| 3 | WCBPOL | worker's compensation | \n Insurance policy for injuries sustained in the work place or in the course of employment. \r\n\n |
| 2 | (_ActInsuranceTypeCode) Abstract | \n \n Definition: Set of codes indicating the type of insurance policy. Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions. The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly. A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss. An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer. A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured. \r\n\n \n Discussion: In contrast to programs, an insurance policy has one or more policy holders, who own the policy. The policy holder may be the covered party, a relative of the covered party, a partnership, or a corporation, e.g., an employer. A subscriber of a self-insured health insurance policy is a policy holder. A subscriber of an employer sponsored health insurance policy is holds a certificate of coverage, but is not a policy holder; the policy holder is the employer. See CoveredRoleType. \r\n\n | |
| 3 | AUTOPOL | ||
| 3 | (_ActHealthInsuranceTypeCode) Abstract | \n \n Definition: Set of codes indicating the type of health insurance policy that covers health services provided to covered parties. A health insurance policy is a written contract for insurance between the insurance company and the policyholder, and contains pertinent facts about the policy owner (the policy holder), the health insurance coverage, the insured subscribers and dependents, and the insurer. Health insurance is typically administered in accordance with a plan, which specifies (1) the type of health services and health conditions that will be covered under what circumstances (e.g., exclusion of a pre-existing condition, service must be deemed medically necessary; service must not be experimental; service must provided in accordance with a protocol; drug must be on a formulary; service must be prior authorized; or be a referral from a primary care provider); (2) the type and affiliation of providers (e.g., only allopathic physicians, only in network, only providers employed by an HMO); (3) financial participations required of covered parties (e.g., co-pays, coinsurance, deductibles, out-of-pocket); and (4) the manner in which services will be paid (e.g., under indemnity or fee-for-service health plans, the covered party typically pays out-of-pocket and then file a claim for reimbursement, while health plans that have contractual relationships with providers, i.e., network providers, typically do not allow the providers to bill the covered party for the cost of the service until after filing a claim with the payer and receiving reimbursement). \r\n\n | |
| 4 | DENTAL | dental care policy | \n \n Definition: A health insurance policy that that covers benefits for dental services. \r\n\n |
| 4 | DISEASE | disease specific policy | \n \n Definition: A health insurance policy that covers benefits for healthcare services provided for named conditions under the policy, e.g., cancer, diabetes, or HIV-AIDS. \r\n\n |
| 4 | DRUGPOL | drug policy | \n \n Definition: A health insurance policy that covers benefits for prescription drugs, pharmaceuticals, and supplies. \r\n\n |
| 4 | EHCPOL | ||
| 4 | HIP | health insurance plan policy | \n \n Definition: A health insurance policy that covers healthcare benefits by protecting covered parties from medical expenses arising from health conditions, sickness, or accidental injury as well as preventive care. Health insurance policies explicitly exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy. \r\n\n \n Discussion: Health insurance policies are offered by health insurance plans that typically reimburse providers for covered services on a fee-for-service basis, that is, a fee that is the allowable amount that a provider may charge. This is in contrast to managed care plans, which typically prepay providers a per-member/per-month amount or capitation as reimbursement for all covered services rendered. Health insurance plans include indemnity and healthcare services plans. \r\n\n |
| 4 | HSAPOL | ||
| 4 | LTC | long term care policy | \n \n Definition: An insurance policy that covers benefits for long-term care services people need when they no longer can care for themselves. This may be due to an accident, disability, prolonged illness or the simple process of aging. Long-term care services assist with activities of daily living including: \r\n\n \n \n Help at home with day-to-day activities, such as cooking, cleaning, bathing and dressing \r\n\n \n \n Care in the community, such as in an adult day care facility \r\n\n \n \n Supervised care provided in an assisted living facility \r\n\n \n \n Skilled care provided in a nursing home \r\n\n \n \n |
| 4 | MCPOL | managed care policy | \n \n Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment. Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program. Employees may be required to pay premiums toward the cost of coverage as well. \r\n\n Managed care policies specifically exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy. \r\n\n \n Discussion: Managed care policies are offered by managed care plans that contract with selected providers or health care organizations to provide comprehensive health care at a discount to covered parties and coordinate the financing and delivery of health care. Managed care uses medical protocols and procedures agreed on by the medical profession to be cost effective, also known as medical practice guidelines. Providers are typically reimbursed for covered services by a capitated amount on a per member per month basis that may reflect difference in the health status and level of services anticipated to be needed by the member. \r\n\n |
| 5 | POS | point of service policy | \n \n Definition: A policy for a health plan that has features of both an HMO and a FFS plan. Like an HMO, a POS plan encourages the use its HMO network to maintain discounted fees with participating providers, but recognizes that sometimes covered parties want to choose their own provider. The POS plan allows a covered party to use providers who are not part of the HMO network (non-participating providers). However, there is a greater cost associated with choosing these non-network providers. A covered party will usually pay deductibles and coinsurances that are substantially higher than the payments when he or she uses a plan provider. Use of non-participating providers often requires the covered party to pay the provider directly and then to file a claim for reimbursement, like in an FFS plan. \r\n\n |
| 5 | HMO | health maintenance organization policy | \n \n Definition: A policy for a health plan that provides coverage for health care only through contracted or employed physicians and hospitals located in particular geographic or service areas. HMOs emphasize prevention and early detection of illness. Eligibility to enroll in an HMO is determined by where a covered party lives or works. \r\n\n |
| 5 | PPO | preferred provider organization policy | \n \n Definition: A network-based, managed care plan that allows a covered party to choose any health care provider. However, if care is received from a "preferred" (participating in-network) provider, there are generally higher benefit coverage and lower deductibles. \r\n\n |
| 4 | MENTPOL | mental health policy | \n \n Definition: A health insurance policy that covers benefits for mental health services and prescriptions. \r\n\n |
| 4 | POS | ||
| 4 | SUBPOL | substance use policy | \n \n Definition: A health insurance policy that covers benefits for substance use services. \r\n\n |
| 4 | VISPOL | vision care policy | \n \n Definition: Set of codes for a policy that provides coverage for health care expenses arising from vision services. \r\n\n A health insurance policy that covers benefits for vision care services, prescriptions, and products. \r\n\n |
| 3 | DIS | disability insurance policy | \n \n Definition: An insurance policy that provides a regular payment to compensate for income lost due to the covered party's inability to work because of illness or injury. \r\n\n |
| 3 | EWB | employee welfare benefit plan policy | \n \n Definition: An insurance policy under a benefit plan run by an employer or employee organization for the purpose of providing benefits other than pension-related to employees and their families. Typically provides health-related benefits, benefits for disability, disease or unemployment, or day care and scholarship benefits, among others. An employer sponsored health policy includes coverage of health care expenses arising from sickness or accidental injury, coverage for on-site medical clinics or for dental or vision benefits, which are typically provided under a separate policy. Coverage excludes health care expenses covered by accident or disability, workers' compensation, liability or automobile insurance. \r\n\n |
| 3 | FLEXP | flexible benefit plan policy | \n \n Definition: An insurance policy that covers qualified benefits under a Flexible Benefit plan such as group medical insurance, long and short term disability income insurance, group term life insurance for employees only up to $50,000 face amount, specified disease coverage such as a cancer policy, dental and/or vision insurance, hospital indemnity insurance, accidental death and dismemberment insurance, a medical expense reimbursement plan and a dependent care reimbursement plan. \r\n\n \n Discussion: See UnderwriterRoleTypeCode flexible benefit plan which is defined as a benefit plan that allows employees to choose from several life, health, disability, dental, and other insurance plans according to their individual needs. Also known as cafeteria plans. Authorized under Section 125 of the Revenue Act of 1978. \r\n\n |
| 3 | LIFE | life insurance policy | \n \n Definition: A policy under which the insurer agrees to pay a sum of money upon the occurrence of the covered partys death. In return, the policyholder agrees to pay a stipulated amount called a premium at regular intervals. Life insurance indemnifies the beneficiary for the loss of the insurable interest that a beneficiary has in the life of a covered party. For persons related by blood, a substantial interest established through love and affection, and for all other persons, a lawful and substantial economic interest in having the life of the insured continue. An insurable interest is required when purchasing life insurance on another person. Specific exclusions are often written into the contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion. \r\n\n \n Discussion:A life insurance policy may be used by the covered party as a source of health care coverage in the case of a viatical settlement, which is the sale of a life insurance policy by the policy owner, before the policy matures. Such a sale, at a price discounted from the face amount of the policy but usually in excess of the premiums paid or current cash surrender value, provides the seller an immediate cash settlement. Generally, viatical settlements involve insured individuals with a life expectancy of less than two years. In countries without state-subsidized healthcare and high healthcare costs (e.g. United States), this is a practical way to pay extremely high health insurance premiums that severely ill people face. Some people are also familiar with life settlements, which are similar transactions but involve insureds with longer life expectancies (two to fifteen years). \r\n\n |
| 4 | ANNU | annuity policy | \n \n Definition: A policy that, after an initial premium or premiums, pays out a sum at pre-determined intervals. \r\n\n For example, a policy holder may pay $10,000, and in return receive $150 each month until he dies; or $1,000 for each of 14 years or death benefits if he dies before the full term of the annuity has elapsed. \r\n\n |
| 4 | TLIFE | term life insurance policy | \n \n Definition: Life insurance under which the benefit is payable only if the insured dies during a specified period. If an insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing. \r\n\n |
| 4 | ULIFE | universal life insurance policy | \n \n Definition: Life insurance under which the benefit is payable upon the insuredaTMs death or diagnosis of a terminal illness. If an insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing \r\n\n |
| 3 | PNC | property and casualty insurance policy | \n \n Definition: A type of insurance that covers damage to or loss of the policyholderaTMs property by providing payments for damages to property damage or the injury or death of living subjects. The terms "casualty" and "liability" insurance are often used interchangeably. Both cover the policyholder's legal liability for damages caused to other persons and/or their property. \r\n\n |
| 3 | REI | reinsurance policy | \n \n Definition: An agreement between two or more insurance companies by which the risk of loss is proportioned. Thus the risk of loss is spread and a disproportionately large loss under a single policy does not fall on one insurance company. Acceptance by an insurer, called a reinsurer, of all or part of the risk of loss of another insurance company. \r\n\n \n Discussion: Reinsurance is a means by which an insurance company can protect itself against the risk of losses with other insurance companies. Individuals and corporations obtain insurance policies to provide protection for various risks (hurricanes, earthquakes, lawsuits, collisions, sickness and death, etc.). Reinsurers, in turn, provide insurance to insurance companies. \r\n\n For example, an HMO may purchase a reinsurance policy to protect itself from losing too much money from one insured's particularly expensive health care costs. An insurance company issuing an automobile liability policy, with a limit of $100,000 per accident may reinsure its liability in excess of $10,000. A fire insurance company which issues a large policy generally reinsures a portion of the risk with one or several other companies. Also called risk control insurance or stop-loss insurance.\n \r\n\n |
| 3 | SURPL | surplus line insurance policy | \n \n Definition: \n \r\n\n \n \n A risk or part of a risk for which there is no normal insurance market available. \r\n\n \n \n Insurance written by unauthorized insurance companies. Surplus lines insurance is insurance placed with unauthorized insurance companies through licensed surplus lines agents or brokers. \r\n\n \n \n |
| 3 | UMBRL | umbrella liability insurance policy | \n \n Definition: A form of insurance protection that provides additional liability coverage after the limits of your underlying policy are reached. An umbrella liability policy also protects you (the insured) in many situations not covered by the usual liability policies. \r\n\n |
| 2 | (_ActProgramTypeCode) Abstract | \n \n Definition: A set of codes used to indicate coverage under a program. A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight. Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation. Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds. \r\n\n \n Discussion: Programs do not have policy holders or subscribers. Program eligibles are enrolled based on health status, statutory eligibility, financial status, or age. Program eligibles who are covered parties under the program may be referred to as members, beneficiaries, eligibles, or recipients. Programs risk are underwritten by not for profit organizations such as governmental entities, and the beneficiaries typically do not pay for any or some portion of the cost of coverage. See CoveredPartyRoleType. \r\n\n | |
| 3 | PUBLICPOL | ||
| 3 | WCBPOL | ||
| 3 | CHAR | charity program | \n \n Definition: A program that covers the cost of services provided directly to a beneficiary who typically has no other source of coverage without charge. \r\n\n |
| 3 | CRIME | crime victim program | \n \n Definition: A program that covers the cost of services provided to crime victims for injuries or losses related to the occurrence of a crime. \r\n\n |
| 3 | EAP | employee assistance program | \n \n Definition: An employee assistance program is run by an employer or employee organization for the purpose of providing benefits and covering all or part of the cost for employees to receive counseling, referrals, and advice in dealing with stressful issues in their lives. These may include substance abuse, bereavement, marital problems, weight issues, or general wellness issues. The services are usually provided by a third-party, rather than the company itself, and the company receives only summary statistical data from the service provider. Employee's names and services received are kept confidential. \r\n\n |
| 3 | GOVEMP | government employee health program | \n \n Definition: A set of codes used to indicate a government program that is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health and financial status. Government programs are established or permitted by legislation with provisions for ongoing government oversight. Regulation mandates the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency is charged with implementing the program in accordance to the regulation \r\n\n \n Example: Federal employee health benefit program in the U.S. \r\n\n |
| 3 | HIRISK | high risk pool program | \n \n Definition: A government program that provides health coverage to individuals who are considered medically uninsurable or high risk, and who have been denied health insurance due to a serious health condition. In certain cases, it also applies to those who have been quoted very high premiums a" again, due to a serious health condition. The pool charges premiums for coverage. Because the pool covers high-risk people, it incurs a higher level of claims than premiums can cover. The insurance industry pays into the pool to make up the difference and help it remain viable. \r\n\n |
| 3 | IND | indigenous peoples health program | \n \n Definition: Services provided directly and through contracted and operated indigenous peoples health programs. \r\n\n \n Example: Indian Health Service in the U.S. \r\n\n |
| 3 | MILITARY | military health program | \n \n Definition: A government program that provides coverage for health services to military personnel, retirees, and dependents. A covered party who is a subscriber can choose from among Fee-for-Service (FFS) plans, and their Preferred Provider Organizations (PPO), or Plans offering a Point of Service (POS) Product, or Health Maintenance Organizations. \r\n\n \n Example: In the U.S., TRICARE, CHAMPUS. \r\n\n |
| 3 | RETIRE | retiree health program | \n \n Definition: A government mandated program with specific eligibility requirements based on premium contributions made during employment, length of employment, age, and employment status, e.g., being retired, disabled, or a dependent of a covered party under this program. Benefits typically include ambulatory, inpatient, and long-term care, such as hospice care, home health care and respite care. \r\n\n |
| 3 | SOCIAL | social service program | \n \n Definition: A social service program funded by a public or governmental entity. \r\n\n \n Example: Programs providing habilitation, food, lodging, medicine, transportation, equipment, devices, products, education, training, counseling, alteration of living or work space, and other resources to persons meeting eligibility criteria. \r\n\n |
| 3 | VET | veteran health program | \n \n Definition: Services provided directly and through contracted and operated veteran health programs. \r\n\n |
| 1 | (_ActDetectedIssueManagementCode) Abstract | \n Codes dealing with the management of Detected Issue observations \r\n\n | |
| 2 | (_ActAdministrativeDetectedIssueManagementCode) Abstract | \n Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains. \r\n\n | |
| 3 | (_AuthorizationIssueManagementCode) Abstract | ||
| 4 | EMAUTH | emergency authorization override | \n Used to temporarily override normal authorization rules to gain access to data in a case of emergency. Use of this override code will typically be monitored, and a procedure to verify its proper use may be triggered when used. \r\n\n |
| 5 | 21 | authorization confirmed | \n \n Description: Indicates that the permissions have been externally verified and the request should be processed. \r\n\n |
| 2 | 1 | Therapy Appropriate | \n Confirmed drug therapy appropriate \r\n\n |
| 3 | 19 | Consulted Supplier | \n Consulted other supplier/pharmacy, therapy confirmed \r\n\n |
| 3 | 2 | Assessed Patient | \n Assessed patient, therapy is appropriate \r\n\n |
| 3 | 22 | appropriate indication or diagnosis | \n \n Description: The patient has the appropriate indication or diagnosis for the action to be taken. \r\n\n |
| 3 | 23 | prior therapy documented | \n \n Description: It has been confirmed that the appropriate pre-requisite therapy has been tried. \r\n\n |
| 3 | 3 | Patient Explanation | \n Patient gave adequate explanation \r\n\n |
| 3 | 4 | Consulted Other Source | \n Consulted other supply source, therapy still appropriate \r\n\n |
| 3 | 5 | Consulted Prescriber | \n Consulted prescriber, therapy confirmed \r\n\n |
| 4 | 6 | Prescriber Declined Change | \n Consulted prescriber and recommended change, prescriber declined \r\n\n |
| 3 | 7 | Interacting Therapy No Longer Active/Planned | \n Concurrent therapy triggering alert is no longer on-going or planned \r\n\n |
| 2 | 14 | Supply Appropriate | \n Confirmed supply action appropriate \r\n\n |
| 3 | 15 | Replacement | \n Patient's existing supply was lost/wasted \r\n\n |
| 3 | 16 | Vacation Supply | \n Supply date is due to patient vacation \r\n\n |
| 3 | 17 | Weekend Supply | \n Supply date is intended to carry patient over weekend \r\n\n |
| 3 | 18 | Leave of Absence | \n Supply is intended for use during a leave of absence from an institution. \r\n\n |
| 3 | 20 | additional quantity on separate dispense | \n \n Description: Supply is different than expected as an additional quantity has been supplied in a separate dispense. \r\n\n |
| 2 | 8 | Other Action Taken | \n Order is performed as issued, but other action taken to mitigate potential adverse effects \r\n\n |
| 3 | 10 | Provided Patient Education | \n Provided education or training to the patient on appropriate therapy use \r\n\n |
| 3 | 11 | Added Concurrent Therapy | \n Instituted an additional therapy to mitigate potential negative effects \r\n\n |
| 3 | 12 | Temporarily Suspended Concurrent Therapy | \n Suspended existing therapy that triggered interaction for the duration of this therapy \r\n\n |
| 3 | 13 | Stopped Concurrent Therapy | \n Aborted existing therapy that triggered interaction. \r\n\n |
| 3 | 9 | Instituted Ongoing Monitoring Program | \n Arranged to monitor patient for adverse effects \r\n\n |
| 1 | (_ActExposureCode) Abstract | \n Concepts that identify the type or nature of exposure interaction. Examples include "household", "care giver", "intimate partner", "common space", "common substance", etc. to further describe the nature of interaction. \r\n\n | |
| 2 | CHLDCARE | Day care - Child care Interaction | \n \n Description: Exposure participants' interaction occurred in a child care setting \r\n\n |
| 2 | CONVEYNC | Common Conveyance Interaction | \n \n Description: An interaction where the exposure participants traveled in/on the same vehicle (not necessarily concurrently, e.g. both are passengers of the same plane, but on different flights of that plane). \r\n\n |
| 2 | HLTHCARE | Health Care Interaction - Not Patient Care | \n \n Description: Exposure participants' interaction occurred during the course of health care delivery or in a health care delivery setting, but did not involve the direct provision of care (e.g. a janitor cleaning a patient's hospital room). \r\n\n |
| 2 | HOMECARE | Care Giver Interaction | \n \n Description: Exposure interaction occurred in context of one providing care for the other, i.e. a babysitter providing care for a child, a home-care aide providing assistance to a paraplegic. \r\n\n |
| 2 | HOSPPTNT | Hospital Patient Interaction | \n \n Description: Exposure participants' interaction occurred when both were patients being treated in the same (acute) health care delivery facility. \r\n\n |
| 2 | HOSPVSTR | Hospital Visitor Interaction | \n \n Description: Exposure participants' interaction occurred when one visited the other who was a patient being treated in a health care delivery facility. \r\n\n |
| 2 | HOUSEHLD | Household Interaction | \n \n Description: Exposure interaction occurred in context of domestic interaction, i.e. both participants reside in the same household. \r\n\n |
| 2 | INMATE | Inmate Interaction | \n \n Description: Exposure participants' interaction occurred in the course of one or both participants being incarcerated at a correctional facility \r\n\n |
| 2 | INTIMATE | Intimate Interaction | \n \n Description: Exposure interaction was intimate, i.e. participants are intimate companions (e.g. spouses, domestic partners). \r\n\n |
| 2 | LTRMCARE | Long Term Care Facility Interaction | \n \n Description: Exposure participants' interaction occurred in the course of one or both participants being resident at a long term care facility (second participant may be a visitor, worker, resident or a physical place or object within the facility). \r\n\n |
| 2 | PLACE | Common Space Interaction | \n \n Description: An interaction where the exposure participants were both present in the same location/place/space. \r\n\n |
| 2 | PTNTCARE | Health Care Interaction - Patient Care | \n \n Description: Exposure participants' interaction occurred during the course of health care delivery by a provider (e.g. a physician treating a patient in her office). \r\n\n |
| 2 | SCHOOL2 | School Interaction | \n \n Description: Exposure participants' interaction occurred in an academic setting (e.g., participants are fellow students, or student and teacher). \r\n\n |
| 2 | SOCIAL2 | Social/Extended Family Interaction | \n \n Description: An interaction where the exposure participants are social associates or members of the same extended family \r\n\n |
| 2 | SUBSTNCE | Common Substance Interaction | \n \n Description: An interaction where the exposure participants shared or co-used a common substance (e.g. drugs, needles, or common food item). \r\n\n |
| 2 | TRAVINT | Common Travel Interaction | \n \n Description: An interaction where the exposure participants traveled together in/on the same vehicle/trip (e.g. concurrent co-passengers). \r\n\n |
| 2 | WORK2 | Work Interaction | \n \n Description: Exposure interaction occurred in a work setting, i.e. participants are co-workers. \r\n\n |
| 1 | (_ActFinancialTransactionCode) Abstract | ||
| 2 | CHRG | Standard Charge | \n A type of transaction that represents a charge for a service or product. Expressed in monetary terms. \r\n\n |
| 2 | REV | Standard Charge Reversal | \n A type of transaction that represents a reversal of a previous charge for a service or product. Expressed in monetary terms. It has the opposite effect of a standard charge. \r\n\n |
| 1 | (_ActIncidentCode) Abstract | \n Set of codes indicating the type of incident or accident. \r\n\n | |
| 2 | MVA | Motor vehicle accident | \n Incident or accident as the result of a motor vehicle accident \r\n\n |
| 2 | SCHOOL | School Accident | \n Incident or accident is the result of a school place accident. \r\n\n |
| 2 | SPT | Sporting Accident | \n Incident or accident is the result of a sporting accident. \r\n\n |
| 2 | WPA | Workplace accident | \n Incident or accident is the result of a work place accident \r\n\n |
| 1 | (_ActInformationAccessCode) Abstract | \n \n Description: The type of health information to which the subject of the information or the subject's delegate consents or dissents. \r\n\n | |
| 2 | ACADR | adverse drug reaction access | \n \n Description: Provide consent to collect, use, disclose, or access adverse drug reaction information for a patient. \r\n\n |
| 2 | ACALL | all access | \n \n Description: Provide consent to collect, use, disclose, or access all information for a patient. \r\n\n |
| 2 | ACALLG | allergy access | \n \n Description: Provide consent to collect, use, disclose, or access allergy information for a patient. \r\n\n |
| 2 | ACCONS | informational consent access | \n \n Description: Provide consent to collect, use, disclose, or access informational consent information for a patient. \r\n\n |
| 2 | ACDEMO | demographics access | \n \n Description: Provide consent to collect, use, disclose, or access demographics information for a patient. \r\n\n |
| 2 | ACDI | diagnostic imaging access | \n \n Description: Provide consent to collect, use, disclose, or access diagnostic imaging information for a patient. \r\n\n |
| 2 | ACIMMUN | immunization access | \n \n Description: Provide consent to collect, use, disclose, or access immunization information for a patient. \r\n\n |
| 2 | ACLAB | lab test result access | \n \n Description: Provide consent to collect, use, disclose, or access lab test result information for a patient. \r\n\n |
| 2 | ACMED | medication access | \n \n Description: Provide consent to collect, use, disclose, or access medical condition information for a patient. \r\n\n |
| 2 | ACMEDC | medical condition access | \n \n Definition: Provide consent to view or access medical condition information for a patient. \r\n\n |
| 2 | ACMEN | mental health access | \n \n Description:Provide consent to collect, use, disclose, or access mental health information for a patient. \r\n\n |
| 2 | ACOBS | common observations access | \n \n Description: Provide consent to collect, use, disclose, or access common observation information for a patient. \r\n\n |
| 2 | ACPOLPRG | policy or program information access | \n \n Description: Provide consent to collect, use, disclose, or access coverage policy or program for a patient. \r\n\n |
| 2 | ACPROV | provider information access | \n \n Description: Provide consent to collect, use, disclose, or access provider information for a patient. \r\n\n |
| 2 | ACPSERV | professional service access | \n \n Description: Provide consent to collect, use, disclose, or access professional service information for a patient. \r\n\n |
| 2 | ACSUBSTAB | substance abuse access | \n \n Description:Provide consent to collect, use, disclose, or access substance abuse information for a patient. \r\n\n |
| 1 | (_ActInformationAccessContextCode) Abstract | \n Concepts conveying the context in which authorization given under jurisdictional law, by organizational policy, or by a patient consent directive permits the collection, access, use or disclosure of specified patient health information. \r\n\n | |
| 2 | INFAUT | authorized information transfer | \n Authorization to collect, access, use, or disclose specified patient health information in accordance with jurisdictional law, organizational policy, or a patient's consent directive, which may be implied, deemed, opt-in, opt-out, or explicit. \r\n\n |
| 3 | INFCON | after explicit consent | \n Authorization to collect, access, use, or disclose specified patient health information as explicitly consented to by the subject of the information or the subject's representative. \r\n\n |
| 2 | INFCRT | only on court order | \n Authorization to collect, access, use, or disclose specified patient health information in accordance with judicial system protocol, such as in the case of a subpoena or court order. \r\n\n |
| 2 | INFDNG | only if danger to others | \n Authorization to collect, access, use, or disclose specified patient health information where deemed necessary to avert potential danger to other persons in accordance with jurisdictional law, organizational policy, or standards of practice. For example, disclosure about a person threatening violence. \r\n\n |
| 2 | INFEMER | only in an emergency | \n Authorization to collect, access, use, or disclose specified patient health information in accordance with emergency information transfer protocol dictated by jurisdictional law, organization policy, or standards of practice. For example, sharing of health information during disaster response. \r\n\n |
| 2 | INFPWR | only if public welfare risk | \n Authorization to collect, access, use, or disclose specified patient health information necessary to avert potential public welfare risk in accordance with jurisdictional law, organizational policy, or standards of practice. For example, reporting that a person is a victim of abuse or demonstrating suicidal tendencies. \r\n\n |
| 2 | INFREG | regulatory information transfer | \n Authorization to collect, access, use, or disclose specified patient health information for public health, welfare, and safety purposes in accordance with jurisdictional law, organizational policy, or standards of practice. For example, public health reporting of notifiable conditions. \r\n\n |
| 1 | (_ActInformationCategoryCode) Abstract | \n \n Definition:Indicates the set of information types which may be manipulated or referenced, such as for recommending access restrictions. \r\n\n | |
| 2 | ALLCAT | all categories | \n \n Description: All patient information. \r\n\n |
| 2 | ALLGCAT | allergy category | \n \n Definition:All information pertaining to a patient's allergy and intolerance records. \r\n\n |
| 2 | ARCAT | adverse drug reaction category | \n \n Description: All information pertaining to a patient's adverse drug reactions. \r\n\n |
| 2 | COBSCAT | common observation category | \n \n Definition:All information pertaining to a patient's common observation records (height, weight, blood pressure, temperature, etc.). \r\n\n |
| 2 | DEMOCAT | demographics category | \n \n Definition:All information pertaining to a patient's demographics (such as name, date of birth, gender, address, etc). \r\n\n |
| 2 | DICAT | diagnostic image category | \n \n Definition:All information pertaining to a patient's diagnostic image records (orders & results). \r\n\n |
| 2 | IMMUCAT | immunization category | \n \n Definition:All information pertaining to a patient's vaccination records. \r\n\n |
| 2 | LABCAT | lab test category | \n \n Description: All information pertaining to a patient's lab test records (orders & results) \r\n\n |
| 2 | MEDCCAT | medical condition category | \n \n Definition:All information pertaining to a patient's medical condition records. \r\n\n |
| 2 | MENCAT | mental health category | \n \n Description: All information pertaining to a patient's mental health records. \r\n\n |
| 2 | PSVCCAT | professional service category | \n \n Definition:All information pertaining to a patient's professional service records (such as smoking cessation, counseling, medication review, mental health). \r\n\n |
| 2 | RXCAT | medication category | \n \n Definition:All information pertaining to a patient's medication records (orders, dispenses and other active medications). \r\n\n |
| 1 | (_ActInvoiceElementCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n | |
| 2 | (_ActInvoiceAdjudicationPaymentCode) Abstract | \n Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee and other cost elements such as bonus, retroactive adjustment and transaction fees. \r\n\n | |
| 3 | (_ActInvoiceAdjudicationPaymentGroupCode) Abstract | \n Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc. \r\n\n | |
| 4 | ALEC | alternate electronic | \n Payment initiated by the payor as the result of adjudicating a submitted invoice that arrived to the payor from an electronic source that did not provide a conformant set of HL7 messages (e.g. web claim submission). \r\n\n |
| 4 | BONUS | bonus | \n Bonus payments based on performance, volume, etc. as agreed to by the payor. \r\n\n |
| 4 | CFWD | carry forward adjusment | \n An amount still owing to the payor but the payment is 0$ and this cannot be settled until a future payment is made. \r\n\n |
| 4 | EDU | education fees | \n Fees deducted on behalf of a payee for tuition and continuing education. \r\n\n |
| 4 | EPYMT | early payment fee | \n Fees deducted on behalf of a payee for charges based on a shorter payment frequency (i.e. next day versus biweekly payments. \r\n\n |
| 4 | GARN | garnishee | \n Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee. \r\n\n |
| 4 | INVOICE | submitted invoice | \n Payment is based on a payment intent for a previously submitted Invoice, based on formal adjudication results.. \r\n\n |
| 4 | PINV | paper invoice | \n Payment initiated by the payor as the result of adjudicating a paper (original, may have been faxed) invoice. \r\n\n |
| 4 | PPRD | prior period adjustment | \n An amount that was owed to the payor as indicated, by a carry forward adjusment, in a previous payment advice \r\n\n |
| 4 | PROA | professional association deduction | \n Professional association fee that is collected by the payor from the practitioner/provider on behalf of the association \r\n\n |
| 4 | RECOV | recovery | \n Retroactive adjustment such as fee rate adjustment due to contract negotiations. \r\n\n |
| 4 | RETRO | retro adjustment | \n Bonus payments based on performance, volume, etc. as agreed to by the payor. \r\n\n |
| 4 | TRAN | transaction fee | \n Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee. \r\n\n |
| 3 | (_ActInvoiceAdjudicationPaymentSummaryCode) Abstract | \n Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee, etc. \r\n\n | |
| 4 | CONT | ||
| 4 | DAY | ||
| 4 | LOC | ||
| 4 | MONTH | ||
| 4 | PERIOD | ||
| 4 | PROV | ||
| 4 | WEEK | ||
| 4 | YEAR | ||
| 4 | INVTYPE | invoice type | \n Transaction counts and value totals by invoice type (e.g. RXDINV - Pharmacy Dispense) \r\n\n |
| 4 | PAYEE | payee | \n Transaction counts and value totals by each instance of an invoice payee. \r\n\n |
| 4 | PAYOR | payor | \n Transaction counts and value totals by each instance of an invoice payor. \r\n\n |
| 4 | SENDAPP | sending application | \n Transaction counts and value totals by each instance of a messaging application on a single processor. It is a registered identifier known to the receivers. \r\n\n |
| 2 | (_ActInvoiceDetailCode) Abstract | \n Codes representing a service or product that is being invoiced (billed). The code can represent such concepts as "office visit", "drug X", "wheelchair" and other billable items such as taxes, service charges and discounts. \r\n\n | |
| 3 | (_ActInvoiceDetailClinicalProductCode) Abstract | \n An identifying data string for healthcare products. \r\n\n | |
| 4 | UNSPSC | United Nations Standard Products and Services Classification | \n \n Description:United Nations Standard Products and Services Classification, managed by Uniform Code Council (UCC): www.unspsc.org \r\n\n |
| 3 | (_ActInvoiceDetailDrugProductCode) Abstract | \n An identifying data string for A substance used as a medication or in the preparation of medication. \r\n\n | |
| 4 | GTIN | Global Trade Item Number | \n \n Description:Global Trade Item Number is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council). \r\n\n |
| 4 | UPC | Universal Product Code | \n \n Description:Universal Product Code is one of a wide variety of bar code languages widely used in the United States and Canada for items in stores. \r\n\n |
| 3 | (_ActInvoiceDetailGenericCode) Abstract | \n The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments. \r\n\n | |
| 4 | (_ActInvoiceDetailGenericAdjudicatorCode) Abstract | \n The billable item codes to identify adjudicator specified components to the total billing of a claim. \r\n\n | |
| 5 | COIN | coinsurance | \n That portion of the eligible charges which a covered party must pay for each service and/or product. It is a percentage of the eligible amount for the service/product that is typically charged after the covered party has met the policy deductible. This amount represents the covered party's coinsurance that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. \r\n\n |
| 5 | COPAYMENT | patient co-pay | \n That portion of the eligible charges which a covered party must pay for each service and/or product. It is a defined amount per service/product of the eligible amount for the service/product. This amount represents the covered party's copayment that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. \r\n\n |
| 5 | DEDUCTIBLE | deductible | \n That portion of the eligible charges which a covered party must pay in a particular period (e.g. annual) before the benefits are payable by the adjudicator. This amount represents the covered party's deductible that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. \r\n\n |
| 5 | PAY | payment | \n The guarantor, who may be the patient, pays the entire charge for a service. Reasons for such action may include: there is no insurance coverage for the service (e.g. cosmetic surgery); the patient wishes to self-pay for the service; or the insurer denies payment for the service due to contractual provisions such as the need for prior authorization. \r\n\n |
| 5 | SPEND | spend down | \n That total amount of the eligible charges which a covered party must periodically pay for services and/or products prior to the Medicaid program providing any coverage. This amount represents the covered party's spend down that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results \r\n\n |
| 5 | COINS | co-insurance | \n The covered party pays a percentage of the cost of covered services. \r\n\n |
| 4 | (_ActInvoiceDetailGenericModifierCode) Abstract | \n The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee. \r\n\n | |
| 5 | AFTHRS | non-normal hours | \n Premium paid on service fees in compensation for practicing outside of normal working hours. \r\n\n |
| 5 | ISOL | isolation allowance | \n Premium paid on service fees in compensation for practicing in a remote location. \r\n\n |
| 5 | OOO | out of office | \n Premium paid on service fees in compensation for practicing at a location other than normal working location. \r\n\n |
| 4 | (_ActInvoiceDetailGenericProviderCode) Abstract | \n The billable item codes to identify provider supplied charges or changes to the total billing of a claim. \r\n\n | |
| 5 | CANCAPT | cancelled appointment | \n A charge to compensate the provider when a patient cancels an appointment with insufficient time for the provider to make another appointment with another patient. \r\n\n |
| 5 | DSC | discount | \n A reduction in the amount charged as a percentage of the amount. For example a 5% discount for volume purchase. \r\n\n |
| 5 | ESA | extraordinary service assessment | \n A premium on a service fee is requested because, due to extenuating circumstances, the service took an extraordinary amount of time or supplies. \r\n\n |
| 5 | FFSTOP | fee for service top off | \n Under agreement between the parties (payor and provider), a guaranteed level of income is established for the provider over a specific, pre-determined period of time. The normal course of business for the provider is submission of fee-for-service claims. Should the fee-for-service income during the specified period of time be less than the agreed to amount, a top-up amount is paid to the provider equal to the difference between the fee-for-service total and the guaranteed income amount for that period of time. The details of the agreement may specify (or not) a requirement for repayment to the payor in the event that the fee-for-service income exceeds the guaranteed amount. \r\n\n |
| 5 | FNLFEE | final fee | \n Anticipated or actual final fee associated with treating a patient. \r\n\n |
| 5 | FRSTFEE | first fee | \n Anticipated or actual initial fee associated with treating a patient. \r\n\n |
| 5 | MARKUP | markup or up-charge | \n An increase in the amount charged as a percentage of the amount. For example, 12% markup on product cost. \r\n\n |
| 5 | MISSAPT | missed appointment | \n A charge to compensate the provider when a patient does not show for an appointment. \r\n\n |
| 5 | PERFEE | periodic fee | \n Anticipated or actual periodic fee associated with treating a patient. For example, expected billing cycle such as monthly, quarterly. The actual period (e.g. monthly, quarterly) is specified in the unit quantity of the Invoice Element. \r\n\n |
| 5 | PERMBNS | performance bonus | \n The amount for a performance bonus that is being requested from a payor for the performance of certain services (childhood immunizations, influenza immunizations, mammograms, pap smears) on a sliding scale. That is, for 90% of childhood immunizations to a maximum of $2200/yr. An invoice is created at the end of the service period (one year) and a code is submitted indicating the percentage achieved and the dollar amount claimed. \r\n\n |
| 5 | RESTOCK | restocking fee | \n A charge is requested because the patient failed to pick up the item and it took an amount of time to return it to stock for future use. \r\n\n |
| 5 | TRAVEL | travel | \n A charge to cover the cost of travel time and/or cost in conjuction with providing a service or product. It may be charged per kilometer or per hour based on the effective agreement. \r\n\n |
| 5 | URGENT | urgent | \n Premium paid on service fees in compensation for providing an expedited response to an urgent situation. \r\n\n |
| 4 | (_ActInvoiceDetailTaxCode) Abstract | \n The billable item codes to identify modifications to a billable item charge by a tax factor applied to the amount. As for example 7% provincial sales tax. \r\n\n | |
| 5 | FST | federal sales tax | \n Federal tax on transactions such as the Goods and Services Tax (GST) \r\n\n |
| 5 | HST | harmonized sales Tax | \n Joint Federal/Provincial Sales Tax \r\n\n |
| 5 | PST | provincial/state sales tax | \n Tax levied by the provincial or state jurisdiction such as Provincial Sales Tax \r\n\n |
| 3 | (_ActInvoiceDetailPreferredAccommodationCode) Abstract | \n An identifying data string for medical facility accommodations. \r\n\n | |
| 4 | (_ActEncounterAccommodationCode) Abstract | \n Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type. \r\n\n | |
| 5 | (_HL7AccommodationCode) Abstract | \n \n Description:Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type. \r\n\n | |
| 6 | I | Isolation | \n Accommodations used in the care of diseases that are transmitted through casual contact or respiratory transmission. \r\n\n |
| 6 | P | Private | \n Accommodations in which there is only 1 bed. \r\n\n |
| 6 | S | Suite | \n Uniquely designed and elegantly decorated accommodations with many amenities available for an additional charge. \r\n\n |
| 6 | SP | Semi-private | \n Accommodations in which there are 2 beds. \r\n\n |
| 6 | W | Ward | \n Accommodations in which there are 3 or more beds. \r\n\n |
| 3 | (_ActInvoiceDetailClinicalServiceCode) Abstract | \n An identifying data string for healthcare procedures. \r\n\n | |
| 2 | (_ActInvoiceGroupCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. \r\n\n | |
| 3 | (_ActInvoiceInterGroupCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. \r\n\n The domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice. \r\n\n | |
| 4 | CPNDDRGING | compound drug invoice group | \n A grouping of invoice element groups and details including the ones specifying the compound ingredients being invoiced. It may also contain generic detail items such as markup. \r\n\n |
| 4 | CPNDINDING | compound ingredient invoice group | \n A grouping of invoice element details including the one specifying an ingredient drug being invoiced. It may also contain generic detail items such as tax or markup. \r\n\n |
| 4 | CPNDSUPING | compound supply invoice group | \n A grouping of invoice element groups and details including the ones specifying the compound supplies being invoiced. It may also contain generic detail items such as markup. \r\n\n |
| 4 | DRUGING | drug invoice group | \n A grouping of invoice element details including the one specifying the drug being invoiced. It may also contain generic detail items such as markup. \r\n\n |
| 4 | FRAMEING | frame invoice group | \n A grouping of invoice element details including the ones specifying the frame fee and the frame dispensing cost that are being invoiced. \r\n\n |
| 4 | LENSING | lens invoice group | \n A grouping of invoice element details including the ones specifying the lens fee and the lens dispensing cost that are being invoiced. \r\n\n |
| 4 | PRDING | product invoice group | \n A grouping of invoice element details including the one specifying the product (good or supply) being invoiced. It may also contain generic detail items such as tax or discount. \r\n\n |
| 3 | (_ActInvoiceRootGroupCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. \r\n\n Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is only specified for the root (top level) invoice element group for an Invoice. \r\n\n | |
| 4 | CPINV | clinical product invoice | \n Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s). \r\n\n For example, a crutch or a wheelchair. \r\n\n |
| 4 | CSINV | clinical service invoice | \n Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services. \r\n\n [1] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service. \r\n\n For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization). \r\n\n [2] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services. The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together. \r\n\n For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together. \r\n\n [3] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time. \r\n\n For example, the same Chiropractic adjustment (service or treatment) delivered on 3 separate occasions over a period of time at the discretion of the provider (e.g. month). \r\n\n |
| 4 | CSPINV | clinical service and product | \n A clinical Invoice Grouping consisting of one or more services and one or more product. Billing for these service(s) and product(s) are supported by multiple clinical billable events (acts). \r\n\n All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. \r\n\n For example , a brace (product) invoiced together with the fitting (service). \r\n\n |
| 4 | FININV | financial invoice | \n Invoice Grouping without clinical justification. These will not require identification of participants and associations from a clinical context such as patient and provider. \r\n\n Examples are interest charges and mileage. \r\n\n |
| 4 | OHSINV | oral health service | \n A clinical Invoice Grouping consisting of one or more oral health services. Billing for these service(s) are supported by multiple clinical billable events (acts). \r\n\n All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. \r\n\n |
| 4 | PAINV | preferred accommodation invoice | \n HealthCare facility preferred accommodation invoice. \r\n\n |
| 4 | RXCINV | Rx compound invoice | \n Pharmacy dispense invoice for a compound. \r\n\n |
| 4 | RXDINV | Rx dispense invoice | \n Pharmacy dispense invoice not involving a compound \r\n\n |
| 4 | SBFINV | sessional or block fee invoice | \n Clinical services invoice where the Invoice Group contains one billable item for multiple clinical services in one or more sessions. \r\n\n |
| 4 | VRXINV | vision dispense invoice | \n Vision dispense invoice for up to 2 lens (left and right), frame and optional discount. Eye exams are invoiced as a clinical service invoice. \r\n\n |
| 1 | (_ActInvoiceElementSummaryCode) Abstract | \n Identifies the different types of summary information that can be reported by queries dealing with Statement of Financial Activity (SOFA). The summary information is generally used to help resolve balance discrepancies between providers and payors. \r\n\n | |
| 2 | (_InvoiceElementAdjudicated) Abstract | \n Total counts and total net amounts adjudicated for all Invoice Groupings that were adjudicated within a time period based on the adjudication date of the Invoice Grouping. \r\n\n | |
| 3 | ADNFPPELAT | adjud. nullified prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFPPELCT | adjud. nullified prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFPPMNAT | adjud. nullified prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNFPPMNCT | adjud. nullified prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNFSPELAT | adjud. nullified same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFSPELCT | adjud. nullified same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFSPMNAT | adjud. nullified same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNFSPMNCT | adjud. nullified same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNPPPELAT | adjud. non-payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPPPELCT | adjud. non-payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPPPMNAT | adjud. non-payee payable prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADNPPPMNCT | adjud. non-payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADNPSPELAT | adjud. non-payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPSPELCT | adjud. non-payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPSPMNAT | adjud. non-payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADNPSPMNCT | adjud. non-payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADPPPPELAT | adjud. payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPPPELCT | adjud. payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPPPMNAT | adjud. payee payable prior-period manual amout | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADPPPPMNCT | adjud. payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADPPSPELAT | adjud. payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPSPELCT | adjud. payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPSPMNAT | adjud. payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADPPSPMNCT | adjud. payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADRFPPELAT | adjud. refused prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFPPELCT | adjud. refused prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFPPMNAT | adjud. refused prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 3 | ADRFPPMNCT | adjud. refused prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 3 | ADRFSPELAT | adjud. refused same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFSPELCT | adjud. refused same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFSPMNAT | adjud. refused same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 3 | ADRFSPMNCT | adjud. refused same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 2 | (_InvoiceElementPaid) Abstract | \n Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date. \r\n\n | |
| 3 | PDNFPPELAT | paid nullified prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFPPELCT | paid nullified prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFPPMNAT | paid nullified prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNFPPMNCT | paid nullified prior-period manual count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNFSPELAT | paid nullified same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFSPELCT | paid nullified same-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently cancelled in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFSPMNAT | paid nullified same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNFSPMNCT | paid nullified same-period manual count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNPPPELAT | paid non-payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPPPELCT | paid non-payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPPPMNAT | paid non-payee payable prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDNPPPMNCT | paid non-payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDNPSPELAT | paid non-payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPSPELCT | paid non-payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPSPMNAT | paid non-payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDNPSPMNCT | paid non-payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDPPPPELAT | paid payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPPPELCT | paid payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPPPMNAT | paid payee payable prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | PDPPPPMNCT | paid payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | PDPPSPELAT | paid payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPSPELCT | paid payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPSPMNAT | paid payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | PDPPSPMNCT | paid payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 2 | (_InvoiceElementSubmitted) Abstract | \n Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included. \r\n\n | |
| 3 | SBBLELAT | submitted billed electronic amount | \n Identifies the total net amount billed for all submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBBLELCT | submitted billed electronic count | \n Identifies the total number of submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBNFELAT | submitted nullified electronic amount | \n Identifies the total net amount billed for all submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBNFELCT | submitted cancelled electronic count | \n Identifies the total number of submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBPDELAT | submitted pending electronic amount | \n Identifies the total net amount billed for all submitted Invoice Groupings that are pended or held by the payor, within a time period and submitted electronically. Adjudicated invoice elements are not included. \r\n\n |
| 3 | SBPDELCT | submitted pending electronic count | \n Identifies the total number of submitted Invoice Groupings that are pended or held by the payor, within a time period and submitted electronically. Adjudicated invoice elements are not included. \r\n\n |
| 1 | (_ActInvoiceOverrideCode) Abstract | \n Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results. \r\n\n | |
| 2 | COVGE | coverage problem | \n Insurance coverage problems have been encountered. Additional explanation information to be supplied. \r\n\n |
| 2 | EFORM | electronic form to follow | \n Electronic form with supporting or additional information to follow. \r\n\n |
| 2 | FAX | fax to follow | \n Fax with supporting or additional information to follow. \r\n\n |
| 2 | GFTH | good faith indicator | \n The medical service was provided to a patient in good faith that they had medical coverage, although no evidence of coverage was available before service was rendered. \r\n\n |
| 2 | LATE | late invoice | \n Knowingly over the payor's published time limit for this invoice possibly due to a previous payor's delays in processing. Additional reason information will be supplied. \r\n\n |
| 2 | MANUAL | manual review | \n Manual review of the invoice is requested. Additional information to be supplied. This may be used in the case of an appeal. \r\n\n |
| 2 | OOJ | out of jurisdiction | \n The medical service and/or product was provided to a patient that has coverage in another jurisdiction. \r\n\n |
| 2 | ORTHO | orthodontic service | \n The service provided is required for orthodontic purposes. If the covered party has orthodontic coverage, then the service may be paid. \r\n\n |
| 2 | PAPER | paper documentation to follow | \n Paper documentation (or other physical format) with supporting or additional information to follow. \r\n\n |
| 2 | PIE | public insurance exhausted | \n Public Insurance has been exhausted. Invoice has not been sent to Public Insuror and therefore no Explanation Of Benefits (EOB) is provided with this Invoice submission. \r\n\n |
| 2 | PYRDELAY | delayed by a previous payor | \n Allows provider to explain lateness of invoice to a subsequent payor. \r\n\n |
| 2 | REFNR | referral not required | \n Rules of practice do not require a physician's referral for the provider to perform a billable service. \r\n\n |
| 2 | REPSERV | repeated service | \n The same service was delivered within a time period that would usually indicate a duplicate billing. However, the repeated service is a medical \tnecessity and therefore not a duplicate. \r\n\n |
| 2 | UNRELAT | unrelated service | \n The service provided is not related to another billed service. For example, 2 unrelated services provided on the same day to the same patient which may normally result in a refused payment for one of the items. \r\n\n |
| 2 | VERBAUTH | verbal authorization | \n The provider has received a verbal permission from an authoritative source to perform the service or supply the item being invoiced. \r\n\n |
| 1 | (_ActListCode) Abstract | \n Provides codes associated with ActClass value of LIST (working list) \r\n\n | |
| 2 | (_ActObservationList) Abstract | ||
| 3 | CARELIST | care plan | \n List of acts representing a care plan. The acts can be in a varierty of moods including event (EVN) to record acts that have been carried out as part of the care plan. \r\n\n |
| 3 | CONDLIST | condition list | \n List of condition observations. \r\n\n |
| 4 | INTOLIST | intolerance list | \n List of intolerance observations. \r\n\n |
| 4 | PROBLIST | problem list | \n List of problem observations. \r\n\n |
| 4 | RISKLIST | risk factors | \n List of risk factor observations. \r\n\n |
| 3 | GOALLIST | goal list | \n List of observations in goal mood. \r\n\n |
| 2 | (_ActTherapyDurationWorkingListCode) Abstract | \n Codes used to identify different types of 'duration-based' working lists. Examples include "Continuous/Chronic", "Short-Term" and "As-Needed". \r\n\n | |
| 3 | (_ActMedicationTherapyDurationWorkingListCode) Abstract | \n \n Definition:A collection of concepts that identifies different types of 'duration-based' mediation working lists. \r\n\n \n Examples:"Continuous/Chronic" "Short-Term" and "As Needed" \r\n\n | |
| 4 | ACU | short term/acute | \n \n Definition:A list of medications which the patient is only expected to consume for the duration of the current order or limited set of orders and which is not expected to be renewed. \r\n\n |
| 4 | CHRON | continuous/chronic | \n \n Definition:A list of medications which are expected to be continued beyond the present order and which the patient should be assumed to be taking unless explicitly stopped. \r\n\n |
| 4 | ONET | one time | \n \n Definition:A list of medications which the patient is intended to be administered only once. \r\n\n |
| 4 | PRN | as needed | \n \n Definition:A list of medications which the patient will consume intermittently based on the behavior of the condition for which the medication is indicated. \r\n\n |
| 2 | MEDLIST | medication list | \n List of medications. \r\n\n |
| 3 | CURMEDLIST | current medication list | \n List of current medications. \r\n\n |
| 3 | DISCMEDLIST | discharge medication list | \n List of discharge medications. \r\n\n |
| 3 | HISTMEDLIST | medication history | \n Historical list of medications. \r\n\n |
| 1 | (_ActMonitoringProtocolCode) Abstract | \n Identifies types of monitoring programs \r\n\n | |
| 2 | CTLSUB | Controlled Substance | \n A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction. \r\n\n |
| 2 | INV | investigational | \n \n Definition:A monitoring program that focuses on a drug which is under investigation and has not received regulatory approval for the condition being investigated \r\n\n |
| 2 | LU | limited use | \n \n Description:A drug that can be prescribed (and reimbursed) only if it meets certain criteria. \r\n\n |
| 2 | OTC | non prescription medicine | \n Medicines designated in this way may be supplied for patient use without a prescription. The exact form of categorisation will vary in different realms. \r\n\n |
| 2 | RX | prescription only medicine | \n Some form of prescription is required before the related medicine can be supplied for a patient. The exact form of regulation will vary in different realms. \r\n\n |
| 2 | SA | special authorization | \n \n Definition:A drug that requires prior approval (to be reimbursed) before being dispensed \r\n\n |
| 2 | SAC | special access | \n \n Description:A drug that requires special access permission to be prescribed and dispensed. \r\n\n |
| 1 | (_ActNonObservationIndicationCode) Abstract | \n \n Description:Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms. \r\n\n | |
| 2 | IND01 | imaging study requiring contrast | \n \n Description:Contrast agent required for imaging study. \r\n\n |
| 2 | IND02 | colonoscopy prep | \n \n Description:Provision of prescription or direction to consume a product for purposes of bowel clearance in preparation for a colonoscopy. \r\n\n |
| 2 | IND03 | prophylaxis | \n \n Description:Provision of medication as a preventative measure during a treatment or other period of increased risk. \r\n\n |
| 2 | IND04 | surgical prophylaxis | \n \n Description:Provision of medication during pre-operative phase; e.g., antibiotics before dental surgery or bowel prep before colon surgery. \r\n\n |
| 2 | IND05 | pregnancy prophylaxis | \n \n Description:Provision of medication for pregnancy --e.g., vitamins, antibiotic treatments for vaginal tract colonization, etc. \r\n\n |
| 1 | (_ActObservationVerificationType) Abstract | \n Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity. \r\n\n \n Examples:\n \r\n\n \n \n Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program \r\n\n \n \n Verification of record - e.g., person has record in an immunization registry \r\n\n \n \n Verification of enumeration - e.g. NPI \r\n\n \n \n Verification of Board Certification - provider specific \r\n\n \n \n Verification of Certification - e.g. JAHCO, NCQA, URAC \r\n\n \n \n Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria \r\n\n \n \n Verification of Provider Credentials \r\n\n \n \n Verification of no adverse findings - e.g. on National Provider Data Bank, Health Integrity Protection Data Base (HIPDB) \r\n\n \n \n | |
| 2 | VFPAPER | verify paper | \n \n Definition:Indicates that the paper version of the record has, should be or is being verified against the electronic version. \r\n\n |
| 1 | (_ActPaymentCode) Abstract | \n Code identifying the method or the movement of payment instructions. \r\n\n Codes are drawn from X12 data element 591 (PaymentMethodCode) \r\n\n | |
| 2 | ACH | Automated Clearing House | \n Automated Clearing House (ACH). \r\n\n |
| 2 | CHK | Cheque | \n A written order to a bank to pay the amount specified from funds on deposit. \r\n\n |
| 2 | DDP | Direct Deposit | \n Electronic Funds Transfer (EFT) deposit into the payee's bank account \r\n\n |
| 2 | NON | Non-Payment Data | \n Non-Payment Data. \r\n\n |
| 1 | (_ActPharmacySupplyType) Abstract | \n Identifies types of dispensing events \r\n\n | |
| 2 | DF | Daily Fill | \n A fill providing sufficient supply for one day \r\n\n |
| 2 | EM | Emergency Supply | \n A supply action where there is no 'valid' order for the supplied medication. E.g. Emergency vacation supply, weekend supply (when prescriber is unavailable to provide a renewal prescription) \r\n\n |
| 3 | SO | Script Owing | \n An emergency supply where the expectation is that a formal order authorizing the supply will be provided at a later date. \r\n\n |
| 2 | FF | First Fill | \n The initial fill against an order. (This includes initial fills against refill orders.) \r\n\n |
| 3 | FFS | ||
| 3 | FFC | First Fill - Complete | \n A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets). \r\n\n |
| 4 | FFCS | ||
| 3 | FFP | First Fill - Part Fill | \n A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) \r\n\n |
| 3 | FFPS | ||
| 3 | FFSS | first fill, partial strength | \n A first fill where the strength supplied is less than the ordered strength. (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 4 | FFPS | ||
| 4 | FFCS | ||
| 4 | TFS | ||
| 3 | TF | Trial Fill | \n A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance. \r\n\n |
| 4 | TFS | ||
| 2 | FS | Floor stock | \n A supply action to restock a smaller more local dispensary. \r\n\n |
| 2 | MS | Manufacturer Sample | \n A supply of a manufacturer sample \r\n\n |
| 2 | RF | Refill | \n A fill against an order that has already been filled (or partially filled) at least once. \r\n\n |
| 3 | DF | ||
| 3 | UD | Unit Dose | \n A supply action that provides sufficient material for a single dose. \r\n\n |
| 3 | RFC | Refill - Complete | \n A refill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets.) \r\n\n |
| 4 | RFCS | refill complete partial strength | \n A refill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets.) and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | RFF | Refill (First fill this facility) | \n The first fill against an order that has already been filled at least once at another facility. \r\n\n |
| 4 | RFFS | refill partial strength (first fill this facility) | \n The first fill against an order that has already been filled at least once at another facility and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | RFP | Refill - Part Fill | \n A refill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) \r\n\n |
| 4 | RFPS | refill part fill partial strength | \n A refill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | RFS | refill partial strength | \n A fill against an order that has already been filled (or partially filled) at least once and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | TB | Trial Balance | \n A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided. \r\n\n |
| 4 | TBS | trial balance partial strength | \n A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 2 | UD | ||
| 2 | UDE | unit dose equivalent | \n A supply action that provides sufficient material for a single dose via multiple products. E.g. 2 50mg tablets for a 100mg unit dose. \r\n\n |
| 1 | (_ActPolicyType) Abstract | \n \n Description:Types of policies that further specify the ActClassPolicy value set. \r\n\n | |
| 2 | (_ActPrivacyPolicy) Abstract | \n A policy deeming certain information to be private to an individual or organization. \r\n\n \n Definition: A mandate, obligation, requirement, rule, or expectation relating to privacy. \r\n\n \n Discussion: ActPrivacyPolicyType codes support the designation of the 1..* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor. 1..* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode. Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates. \r\n\n \n Usage Note: Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced. \r\n\n | |
| 3 | (_ActConsentDirective) Abstract | \n Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. \r\n\n \n Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context, and are considered closely related or synonymous from a legal perspective. \r\n\n \n Examples: \n \r\n\n \n Healthcare Privacy Consent Directive permitting or restricting in whole or part the collection, access, use, and disclosure of health information, and any associated handling caveats.\n Healthcare Medical Consent Directive to receive medical procedures after being informed of risks and benefits, thereby reducing the grantee's liability.\n Research Informed Consent for participation in clinical trials and disclosure of health information after being informed of risks and benefits, thereby reducing the grantee's liability.\n Substitute decision maker delegation in which the grantee assumes responsibility to act on behalf of the grantor.\n Contracts in which the agreement requires assent/dissent by the grantor of terms offered by a grantee, a consumer opts out of an "award" system for use of a retailer's marketing or credit card vendor's point collection cards in exchange for allowing purchase tracking and profiling.\n A mobile device or App privacy policy and terms of service to which a user must agree in whole or in part in order to utilize the service.\n Agreements between a client and an authorization server or between an authorization server and a resource operator and/or resource owner permitting or restricting e.g., collection, access, use, and disclosure of information, and any associated handling caveats.\n \n | |
| 4 | EMRGONLY | emergency only | \n This general consent directive specifically limits disclosure of health information for purpose of emergency treatment. Additional parameters may further limit the disclosure to specific users, roles, duration, types of information, and impose uses obligations. \r\n\n \n Definition: Opt-in to disclosure of health information for emergency only consent directive. \r\n\n |
| 4 | GRANTORCHOICE | grantor choice | \n A grantor's terms of agreement to which a grantee may assent or dissent, and which may include an opportunity for a grantee to request restrictions or extensions. \r\n\n \n Comment: A grantor typically is able to stipulate preferred terms of agreement when the grantor has control over the topic of the agreement, which a grantee must accept in full or may be offered an opportunity to extend or restrict certain terms. \r\n\n \n Usage Note: If the grantor's term of agreement must be accepted in full, then this is considered "basic consent". If a grantee is offered an opportunity to extend or restrict certain terms, then the agreement is considered "granular consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A PHR account holder [grantor] may require any PHR user [grantee] to accept the terms of agreement in full, or may permit a PHR user to extend or restrict terms selected by the account holder or requested by the PHR user.\n Non-healthcare: The owner of a resource server [grantor] may require any authorization server [grantee] to meet authorization requirements stipulated in the grantor's terms of agreement. \n \n |
| 4 | IMPLIED | implied consent | \n A grantor's presumed assent to the grantee's terms of agreement is based on the grantor's behavior, which may result from not expressly assenting to the consent directive offered, or from having no right to assent or dissent offered by the grantee. \r\n\n \n Comment: Implied or "implicit" consent occurs when the behavior of the grantor is understood by a reasonable person to signal agreement to the grantee's terms. \r\n\n \n Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered "basic consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient schedules an appointment with a provider, and either does not take the opportunity to expressly assent or dissent to the provider's consent directive, does not have an opportunity to do so, as in the case where emergency care is required, or simply behaves as though the patient [grantor] agrees to the rights granted to the provider [grantee] in an implicit consent directive.\n An injured and unconscious patient is deemed to have assented to emergency treatment by those permitted to do so under jurisdictional laws, e.g., Good Samaritan laws.\n Non-healthcare: Upon receiving a driver's license, the driver is deemed to have assented without explicitly consenting to undergoing field sobriety tests.\n A corporation that does business in a foreign nation is deemed to have deemed to have assented without explicitly consenting to abide by that nation's laws.\n \n |
| 4 | IMPLIEDD | implied consent with opportunity to dissent | \n A grantor's presumed assent to the grantee's terms of agreement, which is based on the grantor's behavior, and includes a right to dissent to certain terms. \r\n\n \n Comment: A grantor assenting to the grantee's terms of agreement may or may not exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent. \r\n\n \n Usage Note: Implied or "implicit" consent with an "opportunity to dissent" occurs when the grantor's behavior is understood by a reasonable person to signal assent to the grantee's terms of agreement whether the grantor requests or the grantee approves further restrictions, is considered "granular consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare Examples: A healthcare provider deems a patient's assent to disclosure of health information to family members and friends, but offers an opportunity or permits the patient to dissent to such disclosures.\n A health information exchanges deems a patient to have assented to disclosure of health information for treatment purposes, but offers the patient an opportunity to dissents to disclosure to particular provider organizations.\n Non-healthcare Examples: A bank deems a banking customer's assent to specified collection, access, use, or disclosure of financial information as a requirement of holding a bank account, but provides the user an opportunity to limit third-party collection, access, use or disclosure of that information for marketing purposes.\n \n |
| 4 | NOCONSENT | no consent | \n No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement. \r\n\n \n Comment: A "No Consent" policy scheme provides no opportunity for accommodation of an individual's preferences, and may not comply with Fair Information Practice Principles [FIPP] by enabling the data subject to object, access collected information, correct errors, or have accounting of disclosures. \r\n\n \n Usage Note: The grantee's terms of agreement, may be available to the grantor by reviewing the grantee's privacy policies, but there is no notice by which a grantor is apprised of the policy directly or able to acknowledge. \r\n\n \n Examples: \n \r\n\n \n Healthcare: Without notification or an opportunity to assent or dissent, a patient's health information is automatically included in and available (often according to certain rules) through a health information exchange. Note that this differs from implied consent, where the patient is assumed to have consented.\n Without notification or an opportunity to assent or dissent, a patient's health information is collected, accessed, used, or disclosed for research, public health, security, fraud prevention, court order, or law enforcement.\n Non-healthcare: Without notification or an opportunity to assent or dissent, a consumer's healthcare or non-healthcare internet searches are aggregated for secondary uses such as behavioral tracking and profiling.\n Without notification or an opportunity to assent or dissent, a consumer's location and activities in a shopping mall are tracked by RFID tags on purchased items.\n \n |
| 4 | NOPP | notice of privacy practices | \n Acknowledgement of custodian notice of privacy practices. \r\n\n \n Usage Notes: This type of consent directive acknowledges a custodian's notice of privacy practices including its permitted collection, access, use and disclosure of health information to users and for purposes of use specified. \r\n\n |
| 4 | OPTIN | opt-in | \n A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. \r\n\n \n Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. \r\n\n \n Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered "basic consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient [grantor] signs a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies.\n Non-healthcare: An employee [grantor] signs an employer's [grantee's] non-disclosure and non-compete agreement.\n \n |
| 4 | OPTINR | opt-in with restrictions | \n A grantor's assent to the grantee's terms of an agreement with an opportunity for to dissent to certain grantor or grantee selected terms. \r\n\n \n Comment: A grantor dissenting to the grantee's terms of agreement may or may not exercise a right to assent to grantor's pre-approved restrictions or to grantee's selected terms to which a grantor may dissent. \r\n\n \n Usage Note: Opt-in with restrictions is considered "granular consent" because the grantor has an opportunity to narrow the permissions sought by the grantee. \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient assent to grantee's consent directive terms for collection, access, use, or disclosure of health information, and dissents to disclosure to certain recipients as allowed by the provider's pre-approved restriction list.\n Non-Healthcare: A cell phone user assents to the cell phone's privacy practices and terms of use, but dissents from location tracking by turning off the cell phone's tracking capability.\n \n |
| 4 | OPTOUT | op-out | \n A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms. \r\n\n \n Comment: Rejection of a grantee's terms of agreement pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. \r\n\n \n Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered "basic consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient [grantor] declines to sign a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, revocation policies, and consequences of not assenting.\n Non-healthcare: An employee [grantor] refuses to sign an employer's [grantee's] agreement not to join unions or participate in a strike where state law protects employee's collective bargaining rights.\n A citizen [grantor] refuses to enroll in mandatory government [grantee] health insurance based on religious beliefs, which is an exemption.\n \n |
| 4 | OPTOUTE | opt-out with exceptions | \n A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms. \r\n\n \n Comment: A rejection of a grantee's terms of agreement while assenting to certain permissions sought by the grantee or requesting approval of additional grantor terms. \r\n\n \n Usage Note: Opt-out with exceptions is considered a "granular consent" because the grantor has an opportunity to accept certain permissions sought by the grantee or request additional grantor terms, while rejecting other grantee terms. \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient [grantor] dissents to a health information exchange consent directive with the exception of disclosure based on a limited "time to live" shared secret [e.g., a token or password], which the patient can give to a provider when seeking care.\n Non-healthcare: A social media user [grantor] dissents from public access to their account, but assents to access to a circle of friends.\n \n |
| 3 | (_ActPrivacyLaw) Abstract | \n A jurisdictional mandate, regulation, obligation, requirement, rule, or expectation deeming certain information to be private to an individual or organization, which is imposed on: \r\n\n \n The activity of a governed party\n The behavior of a governed party\n The manner in which an act is executed by a governed party\n \n | |
| 4 | _ActUSPrivacyLaw | _ActUSPrivacyLaw | \n \n Definition: A jurisdictional mandate in the U.S. relating to privacy. \r\n\n \n Usage Note: ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1. \r\n\n |
| 5 | 42CFRPart2 | 42 CFR Part2 | \n 42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program. \r\n\n \n Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 5 | CommonRule | Common Rule | \n U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements. \r\n\n \n Definition: U.S. federal laws governing research-related privacy policies. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. \r\n\n |
| 5 | HIPAANOPP | HIPAA notice of privacy practices | \n The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law. \r\n\n \n Definition: Notification of HIPAA Privacy Practices. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. \r\n\n |
| 5 | HIPAAPsyNotes | HIPAA psychotherapy notes | \n The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes. \r\n\n \n Definition: Authorization that must be obtained for disclosure of psychotherapy notes. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 5 | HIPAASelfPay | HIPAA self-pay | \n Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan. \r\n\n \n Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 5 | Title38Section7332 | Title 38 Section 7332 | \n Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfil the duties of the contract; and researchers who provide assurances that the information will not be identified in any report. This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes. \r\n\n \n Definition: Title 38 Part 1 - Section 1.462 Confidentiality restrictions. \r\n\n (a) General. The patient records to which Sections 1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b). \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 3 | (_InformationSensitivityPolicy) Abstract | \n A mandate, obligation, requirement, rule, or expectation characterizing the value or importance of a resource and may include its vulnerability. (Based on ISO7498-2:1989. Note: The vulnerability of personally identifiable sensitive information may be based on concerns that the unauthorized disclosure may result in social stigmatization or discrimination.) Description: Types of Sensitivity policy that apply to Acts or Roles. A sensitivity policy is adopted by an enterprise or group of enterprises (a 'policy domain') through a formal data use agreement that stipulates the value, importance, and vulnerability of information. A sensitivity code representing a sensitivity policy may be associated with criteria such as categories of information or sets of information identifiers (e.g., a value set of clinical codes or branch in a code system hierarchy). These criteria may in turn be used for the Policy Decision Point in a Security Engine. A sensitivity code may be used to set the confidentiality code used on information about Acts and Roles to trigger the security mechanisms required to control how security principals (i.e., a person, a machine, a software application) may act on the information (e.g., collection, access, use, or disclosure). Sensitivity codes are never assigned to the transport or business envelope containing patient specific information being exchanged outside of a policy domain as this would disclose the information intended to be protected by the policy. When sensitive information is exchanged with others outside of a policy domain, the confidentiality code on the transport or business envelope conveys the receiver's responsibilities and indicates the how the information is to be safeguarded without unauthorized disclosure of the sensitive information. This ensures that sensitive information is treated by receivers as the sender intends, accomplishing interoperability without point to point negotiations. \r\n\n \n Usage Note: Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an employee's sensitivity code would make little sense for use outside of a policy domain. 'Taboo' would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable InformationSensitivityPolicy Act.code may be useful in some scenarios if used in combination with a sensitivity identifier and/or Act.title. \r\n\n | |
| 4 | (_ActInformationSensitivityPolicy) Abstract | \n Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." \r\n\n \n Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. \r\n\n | |
| 5 | ETH | substance abuse information sensitivity | \n Policy for handling alcohol or drug-abuse information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to alcohol or drug-abuse information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | GDIS | genetic disease information sensitivity | \n Policy for handling genetic disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to genetic disease information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | HIV | HIV/AIDS information sensitivity | \n Policy for handling HIV or AIDS information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to HIV or AIDS information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | MST | military sexual trauma information sensitivity | \n Policy for handling information related to sexual assault or repeated, threatening sexual harassment that occurred while the patient was in the military, which is afforded heightened confidentiality. \r\n\n Access control concerns for military sexual trauma is based on the patient being subject to control by a higher ranking military perpetrator and/or censure by others within the military unit. Due to the relatively unfettered access to healthcare information by higher ranking military personnel and those who have command over the patient, there is a need to sequester this information outside of the typical controls on access to military health records. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 5 | SCA | sickle cell anemia information sensitivity | \n Policy for handling sickle cell disease information, which is afforded heightened confidentiality. Information handling protocols are based on organizational policies related to sickle cell disease information, which is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then the Act valued with this ActCode should be associated with an Act valued with any applicable laws from the ActPrivacyLaw code system. \r\n\n |
| 5 | SDV | sexual assault, abuse, or domestic violence information sensitivity | \n Policy for handling sexual assault, abuse, or domestic violence information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexual assault, abuse, or domestic violence information that is deemed sensitive. \r\n\n SDV code covers violence perpetrated by related and non-related persons. This code should be specific to physical and mental trauma caused by a related person only. The access control concerns are keeping the patient safe from the perpetrator who may have an abusive psychological control over the patient, may be stalking the patient, or may try to manipulate care givers into allowing the perpetrator to make contact with the patient. The definition needs to be clarified. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | SEX | sexuality and reproductive health information sensitivity | \n Policy for handling sexuality and reproductive health information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexuality and reproductive health information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | SPI | specially protected information sensitivity | \n Policy for handling information deemed specially protected by law or policy including substance abuse, substance use, psychiatric, mental health, behavioral health, and cognitive disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 6 | BH | behavioral health information sensitivity | \n Policy for handling information related to behavioral and emotional disturbances affecting social adjustment and physical health, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 7 | COGN | cognitive disability information sensitivity | \n Policy for handling information related to cognitive disability disorders and conditions caused by these disorders, which are afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n Examples may include dementia, traumatic brain injury, attention deficit, hearing and visual disability such as dyslexia and other disorders and related conditions which impair learning and self-sufficiency. However, the cognitive disabilities to which this term may apply versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. \r\n\n |
| 7 | DVD | developmental disability information sensitivity | \n Policy for handling information related to developmental disability disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n A diverse group of chronic conditions that are due to mental or physical impairments impacting activities of daily living, self-care, language acuity, learning, mobility, independent living and economic self-sufficiency. Examples may include Down syndrome and Autism spectrum. However, the developmental disabilities to which this term applies versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. \r\n\n |
| 7 | EMOTDIS | emotional disturbance information sensitivity | \n Policy for handling information related to emotional disturbance disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n Typical used to characterize behavioral and mental health issues of adolescents where the disorder may be temporarily diagnosed in order to avoid the potential and unnecessary stigmatizing diagnoses of disorder long term. \r\n\n |
| 6 | MH | mental health information sensitivity | \n Policy for handling information related to psychological disorders, which is afforded heightened confidentiality. Mental health information may be deemed specifically sensitive and distinct from physical health, substance use disorders, and behavioral disabilities and disorders in some jurisdictions. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 6 | PSY | psychiatry disorder information sensitivity | \n Policy for handling psychiatry psychiatric disorder information, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 6 | PSYTHPN | psychotherapy note information sensitivity | \n Policy for handling psychotherapy note information, which is afforded heightened confidentiality. \r\n\n \n Usage Note: In some jurisdiction, disclosure of psychotherapy notes requires patient consent. \r\n\n If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 6 | SUD | substance use disorder information sensitivity | \n Policy for handling information related to alcohol or drug use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 7 | ETHUD | alcohol use disorder information sensitivity | \n Policy for handling information related to alcohol use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 7 | OPIOIDUD | opioid use disorder information sensitivity | \n Policy for handling information related to opioid use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 5 | STD | sexually transmitted disease information sensitivity | \n Policy for handling sexually transmitted disease information, which will be afforded heightened confidentiality.\n Information handling protocols based on organizational policies related to sexually transmitted disease information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | TBOO | taboo | \n Policy for handling information not to be initially disclosed or discussed with patient except by a physician assigned to patient in this case. Information handling protocols based on organizational policies related to sensitive patient information that must be initially discussed with the patient by an attending physician before being disclosed to the patient. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n \n Open Issue: This definition conflates a rule and a characteristic, and there may be a similar issue with ts sibling codes. \r\n\n |
| 5 | VIO | violence information sensitivity | \n Policy for handling information related to harm by violence, which is afforded heightened confidentiality. Harm by violence is perpetrated by an unrelated person. \r\n\n Access control concerns for information about mental or physical harm resulting from violence caused by an unrelated person may include manipulation of care givers or access to records that enable the perpetrator contact or locate the patient, but the perpetrator will likely not have established abusive psychological control over the patient. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 5 | SICKLE | sickle cell | \n Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." \r\n\n \n Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. \r\n\n |
| 4 | (_EntitySensitivityPolicyType) Abstract | \n Types of sensitivity policies that may apply to a sensitive attribute on an Entity. \r\n\n \n Usage Note: EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute. May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." \r\n\n | |
| 5 | DEMO | all demographic information sensitivity | \n Policy for handling all demographic information about an information subject, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to all demographic about an information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | DOB | date of birth information sensitivity | \n Policy for handling information related to an information subject's date of birth, which will be afforded heightened confidentiality.Policies may govern sensitivity of information related to an information subject's date of birth, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | GENDER | gender and sexual orientation information sensitivity | \n Policy for handling information related to an information subject's gender and sexual orientation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's gender and sexual orientation, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | LIVARG | living arrangement information sensitivity | \n Policy for handling information related to an information subject's living arrangement, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's living arrangement, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | MARST | marital status information sensitivity | \n Policy for handling information related to an information subject's marital status, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's marital status, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | RACE | race information sensitivity | \n Policy for handling information related to an information subject's race, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's race, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | REL | religion information sensitivity | \n Policy for handling information related to an information subject's religious affiliation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's religion, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | (_RoleInformationSensitivityPolicy) Abstract | \n Types of sensitivity policies that apply to Roles. \r\n\n \n Usage Notes: RoleSensitivity codes are used to bind information to a Role.confidentialityCode per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." \r\n\n | |
| 5 | B | business information sensitivity | \n Policy for handling trade secrets such as financial information or intellectual property, which will be afforded heightened confidentiality. Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. \r\n\n \n Usage Notes: No patient related information may ever be of this confidentiality level. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | EMPL | employer information sensitivity | \n Policy for handling information related to an employer which is deemed classified to protect an employee who is the information subject, and which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to an employer, such as law enforcement or national security, the identity of which could impact the privacy, well-being, or safety of an information subject who is an employee. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | LOCIS | location information sensitivity | \n Policy for handling information related to the location of the information subject, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to the location of the information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | SSP | sensitive service provider information sensitivity | \n Policy for handling information related to a provider of sensitive services, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to providers who deliver sensitive healthcare services in order to protect the privacy, well-being, and safety of the provider and of patients receiving sensitive services. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | ADOL | adolescent information sensitivity | \n Policy for handling information related to an adolescent, which will be afforded heightened confidentiality per applicable organizational or jurisdictional policy. An enterprise may have a policy that requires that adolescent patient information be provided heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n \n Usage Note: For use within an enterprise in which an adolescent is the information subject. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | CEL | celebrity information sensitivity | \n Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality. Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n \n Usage Note: For use within an enterprise in which the information subject is deemed a celebrity or very important person. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | DIA | diagnosis information sensitivity | \n Policy for handling information related to a diagnosis, health condition or health problem, which will be afforded heightened confidentiality. Diagnostic, health condition or health problem related information may be deemed sensitive by organizational policy, and require heightened confidentiality. \r\n\n \n Usage Note: For use within an enterprise that provides heightened confidentiality to diagnostic, health condition or health problem related information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | DRGIS | drug information sensitivity | \n Policy for handling information related to a drug, which will be afforded heightened confidentiality. Drug information may be deemed sensitive by organizational policy, and require heightened confidentiality. \r\n\n \n Usage Note: For use within an enterprise that provides heightened confidentiality to drug information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | EMP | employee information sensitivity | \n Policy for handling information related to an employee, which will be afforded heightened confidentiality. When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n \n Usage Note: Policy for handling information related to an employee, which will be afforded heightened confidentiality. Description: When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n |
| 4 | PDS | patient default information sensitivity | \n Policy for specially protecting information reported by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive for another reason.) For example information reported by the patient about another person, e.g., a family member, may be deemed sensitive by default. Organizational policy may allow the sensitivity tag to be cleared on patient's request. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n For example, VA deems employee information sensitive by default. Information about a patient who is being stalked or a victim of abuse or violence may be deemed sensitive by default per a provider organization's policies. \r\n\n |
| 4 | PHY | physician requested information sensitivity | \n Policy for handling information about a patient, which a physician or other licensed healthcare provider deems sensitive. Once tagged by the provider, this may trigger alerts for follow up actions according to organizational policy or jurisdictional law. \r\n\n \n Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a physician as sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n Use cases in which this code could be used are, e.g., in systems that lack the ability to automatically detect sensitive information and must rely on manual tagging; a system that lacks an applicable sensitivity tag, or for ad hoc situations where criticality of the situation requires that the tagging be done immediately by the provider before coding or transcription of consult notes can be completed, e.g., upon detection of a patient with suicidal tendencies or potential for violence. \r\n\n |
| 4 | PRS | patient requested information sensitivity | \n Policy for specially protecting information reported by or about a patient, which the patient deems sensitive, and the patient requests that collection, access, use, or disclosure of that information be restricted. For example, a minor patient may request that information about reproductive health not be disclosed to the patient's family or to particular providers and payers. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 3 | COMPT | compartment | \n This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. \r\n\n Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk." \r\n\n |
| 4 | ACOCOMPT | accountable care organization compartment | \n A group of health care entities, which may include health care providers, care givers, hospitals, facilities, health plans, and other health care constituents who coordinate care for reimbursement based on quality metrics for improving outcomes and lowering costs, and may be authorized to access the consumer's health information because of membership in that group. \r\n\n Security Compartment Labels assigned to a consumer's information use in accountable care workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a an accountable care workflow who is requesting access to that information \r\n\n |
| 4 | CTCOMPT | care team compartment | \n Care coordination across participants in a care plan requires sharing of a healthcare consumer's information specific to that workflow. A care team member should only have access to that information while participating in that workflow or for other authorized uses. \r\n\n Security Compartment Labels assigned to a consumer's information use in care coordination workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a care team member workflow who is requesting access to that information \r\n\n |
| 4 | FMCOMPT | financial management compartment | \n Financial management department members who have access to healthcare consumer information as part of a patient account, billing and claims workflows. \r\n\n Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a financial management workflow who is requesting access to that information. \r\n\n |
| 4 | HRCOMPT | human resource compartment | \n A security category label field value, which indicates that access and use of an IT resource is restricted to members of human resources department or workflow. \r\n\n |
| 4 | LRCOMPT | legitimate relationship compartment | \n Providers and care givers who have an established relationship per criteria determined by policy are considered to have an established care provision relations with a healthcare consumer, and may be authorized to access the consumer's health information because of that relationship. Providers and care givers should only have access to that information while participating in legitimate relationship workflows or for other authorized uses. \r\n\n Security Compartment Labels assigned to a consumer's information use in legitimate relationship workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a legitimate relationship workflow who is requesting access to that information. \r\n\n |
| 4 | PACOMPT | patient administration compartment | \n Patient administration members who have access to healthcare consumer information as part of a patient administration workflows. \r\n\n Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a patient administration workflow who is requesting access to that information. \r\n\n |
| 4 | RESCOMPT | research project compartment | \n A security category label field value, which indicates that access and use of an IT resource is restricted to members of a research project. \r\n\n |
| 4 | RMGTCOMPT | records management compartment | \n A security category label field value, which indicates that access and use of an IT resource is restricted to members of records management department or workflow. \r\n\n |
| 2 | (ActTrustPolicyType) Abstract | \n A mandate, obligation, requirement, rule, or expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions. \r\n\n Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). \r\n\n Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain's trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. [Based on ISO IEC 10181-1 and NIST SP 800-63-2] \r\n\n For example, identity proofing , level of assurance, and Trust Framework. \r\n\n | |
| 3 | TRSTACCRD | trust accreditation | \n Type of security metadata about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. \r\n\n |
| 3 | TRSTAGRE | trust agreement | \n Type of security metadata about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] \r\n\n |
| 3 | TRSTASSUR | trust assurance | \n Type of security metadata about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. \r\n\n |
| 3 | TRSTCERT | trust certificate | \n Type of security metadata about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] \r\n\n |
| 3 | TRSTFWK | trust framework | \n Type of security metadata about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative] \r\n\n |
| 3 | TRSTMEC | trust mechanism | \n Type of security metadata about a security architecture system component that supports enforcement of security policies. \r\n\n |
| 2 | COVPOL | benefit policy | \n \n Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed on benefit coverage under a policy or program by a sponsor, underwriter or payor on: \r\n\n \n \n The activity of another party \r\n\n \n \n The behavior of another party \r\n\n \n \n The manner in which an act is executed \r\n\n \n \n \n Examples:A clinical protocol imposed by a payer to which a provider must adhere in order to be paid for providing the service. A formulary from which a provider must select prescribed drugs in order for the patient to incur a lower copay. \r\n\n |
| 2 | SecurityPolicy | security policy | \n Types of security policies that further specify the ActClassPolicy value set. \r\n\n \n Examples:\n \r\n\n \n obligation to encrypt\n refrain from redisclosure without consent\n \n |
| 3 | AUTHPOL | authorization policy | \n Authorisation policies are essentially security policies related to access-control and specify what activities a subject is permitted or forbidden to do, to a set of target objects. They are designed to protect target objects so are interpreted by access control agents or the run-time systems at the target system. \r\n\n A positive authorisation policy defines the actions that a subject is permitted to perform on a target. A negative authorisation policy specifies the actions that a subject is forbidden to perform on a target. Positive authorisation policies may also include filters to transform the parameters associated with their actions. (Based on PONDERS) \r\n\n |
| 4 | ACCESSCONSCHEME | access control scheme | \n An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies. \r\n\n \n Usage Note: Access control schemes are the type of access control policy, which is comprised of access control policy rules concerning the provision of the access control service. \r\n\n There are two categories of access control policies, rule-based and identity-based, which are identified in CCITT Rec. X.800 aka ISO 7498-2. Rule-based access control policies are intended to apply to all access requests by any initiator on any target in a security domain. Identity-based access control policies are based on rules specific to an individual initiator, a group of initiators, entities acting on behalf of initiators, or originators acting in a specific role. Context can modify rule-based or identity-based access control policies. Context rules may define the entire policy in effect. Real systems will usually employ a combination of these policy types; if a rule-based policy is used, then an identity-based policy is usually in effect also. \r\n\n An access control scheme may be based on access control lists, capabilities, labels, and context or a combination of these. An access control scheme is a component of an access control mechanism or "service") along with the supporting mechanisms required by that scheme to provide access control decision information (ADI) supplied by the scheme to the access decision facility (ADF also known as a PDP). (Based on ISO/IEC 10181-3:1996) \r\n\n \n Examples: \n \r\n\n \n Attribute Based Access Control (ABAC)\n Discretionary Access Control (DAC)\n History Based Access Control (HBAC)\n Identity Based Access Control (IBAC)\n Mandatory Access Control (MAC)\n Organization Based Access Control (OrBAC)\n Relationship Based Access Control (RelBac)\n Responsibility Based Access Control (RespBAC)\n Risk Adaptable Access Control (RAdAC)\n > |
| 3 | DELEPOL | delegation policy | \n Delegation policies specify which actions subjects are allowed to delegate to others. A delegation policy thus specifies an authorisation to delegate. Subjects must already possess the access rights to be delegated. \r\n\n Delegation policies are aimed at subjects delegating rights to servers or third parties to perform actions on their behalf and are not meant to be the means by which security administrators would assign rights to subjects. A negative delegation policy identifies what delegations are forbidden. \r\n\n A Delegation policy specifies the authorisation policy from which delegated rights are derived, the grantors, which are the entities which can delegate these access rights, and the grantees, which are the entities to which the access rights can be delegated. There are two types of delegation policy, positive and negative. (Based on PONDERS) \r\n\n |
| 3 | ObligationPolicy | obligation policy | \n Conveys the mandated workflow action that an information custodian, receiver, or user must perform. \r\n\n \n Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision. \r\n\n |
| 4 | ANONY | anonymize | \n Custodian system must remove any information that could result in identifying the information subject. \r\n\n |
| 4 | AOD | accounting of disclosure | \n Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual's protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested. \r\n\n |
| 4 | AUDIT | audit | \n Custodian system must monitor systems to ensure that all users are authorized to operate on information objects. \r\n\n |
| 4 | AUDTR | audit trail | \n Custodian system must monitor and maintain retrievable log for each user and operation on information. \r\n\n |
| 4 | CPLYCC | comply with confidentiality code | \n Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target. \r\n\n |
| 4 | CPLYCD | comply with consent directive | \n Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives. \r\n\n |
| 4 | CPLYJPP | comply with jurisdictional privacy policy | \n Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information. \r\n\n |
| 4 | CPLYOPP | comply with organizational privacy policy | \n Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information. \r\n\n |
| 4 | CPLYOSP | comply with organizational security policy | \n Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information. \r\n\n |
| 4 | CPLYPOL | comply with policy | \n Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information. \r\n\n |
| 4 | DECLASSIFYLABEL | declassify security label | \n Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 4 | DEID | deidentify | \n Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. \r\n\n |
| 4 | DELAU | delete after use | \n Custodian system must remove target information from access after use. \r\n\n |
| 4 | DOWNGRDLABEL | downgrade security label | \n Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 4 | DRIVLABEL | derive security label | \n Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 4 | ENCRYPT | encrypt | \n Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. \r\n\n \r\n\n \n Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.) \r\n\n |
| 5 | ENCRYPTR | encrypt at rest | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage. \r\n\n |
| 5 | ENCRYPTT | encrypt in transit | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means. \r\n\n |
| 5 | ENCRYPTU | encrypt in use | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user. \r\n\n |
| 4 | HUAPRV | human approval | \n Custodian system must require human review and approval for permission requested. \r\n\n |
| 4 | LABEL | assign security label | \n Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. \r\n\n \n Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes. \r\n\n |
| 4 | MASK | mask | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret". \r\n\n |
| 4 | MINEC | minimum necessary | \n Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. \r\n\n \n Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use. \r\n\n |
| 4 | PERSISTLABEL | persist security label | \n Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. \r\n\n |
| 4 | PRIVMARK | privacy mark | \n Custodian must create and/or maintain human readable security label tags as required by policy. \r\n\n Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label." \r\n\n |
| 4 | PSEUD | pseudonymize | \n Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject. \r\n\n |
| 4 | REDACT | redact | \n Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users. \r\n\n |
| 4 | UPGRDLABEL | upgrade security label | \n Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 3 | RefrainPolicy | refrain policy | \n Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. \r\n\n \r\n\n \n Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc. \r\n\n |
| 4 | NOAUTH | no disclosure without subject authorization | \n Prohibition on disclosure without information subject's authorization. \r\n\n |
| 4 | NOCOLLECT | no collection | \n Prohibition on collection or storage of the information. \r\n\n |
| 4 | NODSCLCD | no disclosure without consent directive | \n Prohibition on disclosure without organizational approved patient restriction. \r\n\n |
| 4 | NODSCLCDS | no disclosure without information subject's consent directive | \n Prohibition on disclosure without a consent directive from the information subject. \r\n\n |
| 4 | NOINTEGRATE | no integration | \n Prohibition on Integration into other records. \r\n\n |
| 4 | NOLIST | no unlisted entity disclosure | \n Prohibition on disclosure except to entities on specific access list. \r\n\n |
| 4 | NOMOU | no disclosure without MOU | \n Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU). \r\n\n |
| 4 | NOORGPOL | no disclosure without organizational authorization | \n Prohibition on disclosure without organizational authorization. \r\n\n |
| 4 | NOPAT | no disclosure to patient, family or caregivers without attending provider's authorization | \n Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. \r\n\n \n Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. \r\n\n Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. \r\n\n FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. \r\n\n \n displayName: Document non visible par le patient\n codingScheme: 1.2.250.1.213.1.1.4.13\n \n French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone). \r\n\n |
| 4 | NOPERSISTP | no collection beyond purpose of use | \n Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited. \r\n\n |
| 4 | NORDSCLCD | no redisclosure without consent directive | \n Prohibition on redisclosure without patient consent directive. \r\n\n |
| 4 | NORDSCLCDS | no redisclosure without information subject's consent directive | \n Prohibition on redisclosure without a consent directive from the information subject. \r\n\n |
| 4 | NORDSCLW | no disclosure without jurisdictional authorization | \n Prohibition on disclosure without authorization under jurisdictional law. \r\n\n |
| 4 | NORELINK | no relinking | \n Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked. \r\n\n |
| 4 | NOREUSE | no reuse beyond purpose of use | \n Prohibition on use of the information beyond the purpose of use initially authorized. \r\n\n |
| 4 | NOVIP | no unauthorized VIP disclosure | \n Prohibition on disclosure except to principals with access permission to specific VIP information. \r\n\n |
| 4 | ORCON | no disclosure without originator authorization | \n Prohibition on disclosure except as permitted by the information originator. \r\n\n |
| 1 | (_ActProductAcquisitionCode) Abstract | \n The method that a product is obtained for use by the subject of the supply act (e.g. patient). Product examples are consumable or durable goods. \r\n\n | |
| 2 | LOAN | Loan | \n Temporary supply of a product without transfer of ownership for the product. \r\n\n |
| 3 | RENT | Rent | \n Temporary supply of a product with financial compensation, without transfer of ownership for the product. \r\n\n |
| 2 | TRANSFER | Transfer | \n Transfer of ownership for a product. \r\n\n |
| 3 | SALE | Sale | \n Transfer of ownership for a product for financial compensation. \r\n\n |
| 1 | (_ActSpecimenTransportCode) Abstract | \n Transportation of a specimen. \r\n\n | |
| 2 | SREC | specimen received | \n \n Description:Specimen has been received by the participating organization/department. \r\n\n |
| 2 | SSTOR | specimen in storage | \n \n Description:Specimen has been placed into storage at a participating location. \r\n\n |
| 2 | STRAN | specimen in transit | \n \n Description:Specimen has been put in transit to a participating receiver. \r\n\n |
| 1 | (_ActSpecimenTreatmentCode) Abstract | \n Set of codes related to specimen treatments \r\n\n | |
| 2 | ACID | Acidification | \n The lowering of specimen pH through the addition of an acid \r\n\n |
| 2 | ALK | Alkalization | \n The act rendering alkaline by impregnating with an alkali; a conferring of alkaline qualities. \r\n\n |
| 2 | DEFB | Defibrination | \n The removal of fibrin from whole blood or plasma through physical or chemical means \r\n\n |
| 2 | FILT | Filtration | \n The passage of a liquid through a filter, accomplished by gravity, pressure or vacuum (suction). \r\n\n |
| 2 | LDLP | LDL Precipitation | |
| 2 | NEUT | Neutralization | \n The act or process by which an acid and a base are combined in such proportions that the resulting compound is neutral. \r\n\n |
| 2 | RECA | Recalcification | \n The addition of calcium back to a specimen after it was removed by chelating agents \r\n\n |
| 2 | UFIL | Ultrafiltration | \n The filtration of a colloidal substance through a semipermeable medium that allows only the passage of small molecules. \r\n\n |
| 1 | (_ActSubstanceAdministrationCode) Abstract | \n \n Description: Describes the type of substance administration being performed. This should not be used to carry codes for identification of products. Use an associated role or entity to carry such information. \r\n\n | |
| 2 | DRUG | Drug therapy | \n The introduction of a drug into a subject with the intention of altering its biologic state with the intent of improving its health status. \r\n\n |
| 2 | FD | food | \n \n Description: The introduction of material into a subject with the intent of providing nutrition or other dietary supplements (e.g. minerals or vitamins). \r\n\n |
| 2 | IMMUNIZ | Immunization | \n The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents. \r\n\n |
| 3 | BOOSTER | Booster Immunization | \n An additional immunization administration within a series intended to bolster or enhance immunity. \r\n\n |
| 3 | INITIMMUNIZ | Initial Immunization | \n The first immunization administration in a series intended to produce immunity \r\n\n |
| 1 | (_ActTaskCode) Abstract | \n \n Description: A task or action that a user may perform in a clinical information system (e.g., medication order entry, laboratory test results review, problem list entry). \r\n\n | |
| 2 | OE | order entry task | \n A clinician creates a request for a service to be performed for a given patient. \r\n\n |
| 3 | LABOE | laboratory test order entry task | \n A clinician creates a request for a laboratory test to be done for a given patient. \r\n\n |
| 3 | MEDOE | medication order entry task | \n A clinician creates a request for the administration of one or more medications to a given patient. \r\n\n |
| 2 | PATDOC | patient documentation task | \n A person enters documentation about a given patient. \r\n\n |
| 3 | ALLERLREV | allergy list review | \n \n Description: A person reviews a list of known allergies of a given patient. \r\n\n |
| 3 | CLINNOTEE | clinical note entry task | \n A clinician enters a clinical note about a given patient \r\n\n |
| 4 | DIAGLISTE | diagnosis list entry task | \n A clinician enters a diagnosis for a given patient. \r\n\n |
| 4 | DISCHINSTE | discharge instruction entry | \n A person provides a discharge instruction to a patient. \r\n\n |
| 4 | DISCHSUME | discharge summary entry task | \n A clinician enters a discharge summary for a given patient. \r\n\n |
| 4 | PATEDUE | patient education entry | \n A person provides a patient-specific education handout to a patient. \r\n\n |
| 4 | PATREPE | pathology report entry task | \n A pathologist enters a report for a given patient. \r\n\n |
| 4 | PROBLISTE | problem list entry task | \n A clinician enters a problem for a given patient. \r\n\n |
| 4 | RADREPE | radiology report entry task | \n A radiologist enters a report for a given patient. \r\n\n |
| 3 | IMMLREV | immunization list review | \n \n Description: A person reviews a list of immunizations due or received for a given patient. \r\n\n |
| 3 | REMLREV | reminder list review | \n \n Description: A person reviews a list of health care reminders for a given patient. \r\n\n |
| 4 | WELLREMLREV | wellness reminder list review | \n \n Description: A person reviews a list of wellness or preventive care reminders for a given patient. \r\n\n |
| 2 | PATINFO | patient information review task | \n A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record. \r\n\n |
| 3 | ALLERLE | allergy list entry | \n \n Description: A person enters a known allergy for a given patient. \r\n\n |
| 3 | CDSREV | clinical decision support intervention review | \n A person reviews a recommendation/assessment provided automatically by a clinical decision support application for a given patient. \r\n\n |
| 3 | CLINNOTEREV | clinical note review task | \n A person reviews a clinical note of a given patient. \r\n\n |
| 4 | DISCHSUMREV | discharge summary review task | \n A person reviews a discharge summary of a given patient. \r\n\n |
| 3 | DIAGLISTREV | diagnosis list review task | \n A person reviews a list of diagnoses of a given patient. \r\n\n |
| 3 | IMMLE | immunization list entry | \n \n Description: A person enters an immunization due or received for a given patient. \r\n\n |
| 3 | LABRREV | laboratory results review task | \n A person reviews a list of laboratory results of a given patient. \r\n\n |
| 3 | MICRORREV | microbiology results review task | \n A person reviews a list of microbiology results of a given patient. \r\n\n |
| 4 | MICROORGRREV | microbiology organisms results review task | \n A person reviews organisms of microbiology results of a given patient. \r\n\n |
| 4 | MICROSENSRREV | microbiology sensitivity test results review task | \n A person reviews the sensitivity test of microbiology results of a given patient. \r\n\n |
| 3 | MLREV | medication list review task | \n A person reviews a list of medication orders submitted to a given patient \r\n\n |
| 4 | MARWLREV | medication administration record work list review task | \n A clinician reviews a work list of medications to be administered to a given patient. \r\n\n |
| 3 | OREV | orders review task | \n A person reviews a list of orders submitted to a given patient. \r\n\n |
| 3 | PATREPREV | pathology report review task | \n A person reviews a pathology report of a given patient. \r\n\n |
| 3 | PROBLISTREV | problem list review task | \n A person reviews a list of problems of a given patient. \r\n\n |
| 3 | RADREPREV | radiology report review task | \n A person reviews a radiology report of a given patient. \r\n\n |
| 3 | REMLE | reminder list entry | \n \n Description: A person enters a health care reminder for a given patient. \r\n\n |
| 4 | WELLREMLE | wellness reminder list entry | \n \n Description: A person enters a wellness or preventive care reminder for a given patient. \r\n\n |
| 3 | RISKASSESS | risk assessment instrument task | \n A person reviews a Risk Assessment Instrument report of a given patient. \r\n\n |
| 4 | FALLRISK | falls risk assessment instrument task | \n A person reviews a Falls Risk Assessment Instrument report of a given patient. \r\n\n |
| 1 | (_ActTransportationModeCode) Abstract | \n Characterizes how a transportation act was or will be carried out. \r\n\n \n Examples: Via private transport, via public transit, via courier. \r\n\n | |
| 2 | (_ActPatientTransportationModeCode) Abstract | \n Definition: Characterizes how a patient was or will be transported to the site of a patient encounter. \r\n\n \n Examples: Via ambulance, via public transit, on foot. \r\n\n | |
| 3 | AFOOT | pedestrian transport | |
| 3 | AMBT | ambulance transport | |
| 4 | AMBAIR | fixed-wing ambulance transport | |
| 4 | AMBGRND | ground ambulance transport | |
| 4 | AMBHELO | helicopter ambulance transport | |
| 3 | LAWENF | law enforcement transport | |
| 3 | PRVTRN | private transport | |
| 3 | PUBTRN | public transport | |
| 1 | (_ObservationType) Abstract | \n Identifies the kinds of observations that can be performed \r\n\n | |
| 2 | (_ActSpecObsCode) Abstract | \n Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation \r\n\n | |
| 3 | ARTBLD | ActSpecObsArtBldCode | \n Describes the artificial blood identifier that is associated with the specimen. \r\n\n |
| 3 | DILUTION | ActSpecObsDilutionCode | \n An observation that reports the dilution of a sample. \r\n\n |
| 4 | AUTO-HIGH | Auto-High Dilution | \n The dilution of a sample performed by automated equipment. The value is specified by the equipment \r\n\n |
| 4 | AUTO-LOW | Auto-Low Dilution | \n The dilution of a sample performed by automated equipment. The value is specified by the equipment \r\n\n |
| 4 | PRE | Pre-Dilution | \n The dilution of the specimen made prior to being loaded onto analytical equipment \r\n\n |
| 4 | RERUN | Rerun Dilution | \n The value of the dilution of a sample after it had been analyzed at a prior dilution value \r\n\n |
| 3 | EVNFCTS | ActSpecObsEvntfctsCode | \n Domain provides codes that qualify the ActLabObsEnvfctsCode domain. (Environmental Factors) \r\n\n |
| 3 | INTFR | ActSpecObsInterferenceCode | \n An observation that relates to factors that may potentially cause interference with the observation \r\n\n |
| 4 | FIBRIN | Fibrin | \n The Fibrin Index of the specimen. In the case of only differentiating between Absent and Present, recommend using 0 and 1 \r\n\n |
| 4 | HEMOLYSIS | Hemolysis | \n An observation of the hemolysis index of the specimen in g/L \r\n\n |
| 4 | ICTERUS | Icterus | \n An observation that describes the icterus index of the specimen. It is recommended to use mMol/L of bilirubin \r\n\n |
| 4 | LIPEMIA | Lipemia | \n An observation used to describe the Lipemia Index of the specimen. It is recommended to use the optical turbidity at 600 nm (in absorbance units). \r\n\n |
| 3 | VOLUME | ActSpecObsVolumeCode | \n An observation that reports the volume of a sample. \r\n\n |
| 4 | AVAILABLE | Available Volume | \n The available quantity of specimen. This is the current quantity minus any planned consumption (e.g., tests that are planned) \r\n\n |
| 4 | CONSUMPTION | Consumption Volume | \n The quantity of specimen that is used each time the equipment uses this substance \r\n\n |
| 4 | CURRENT | Current Volume | \n The current quantity of the specimen, i.e., initial quantity minus what has been actually used. \r\n\n |
| 4 | INITIAL | Initial Volume | \n The initial quantity of the specimen in inventory \r\n\n |
| 2 | (_AnnotationType) Abstract | ||
| 3 | _ActPatientAnnotationType | ActPatientAnnotationType | \n \n Description:Provides a categorization for annotations recorded directly against the patient . \r\n\n |
| 4 | ANNDI | diagnostic image note | \n \n Description:A note that is specific to a patient's diagnostic images, either historical, current or planned. \r\n\n |
| 4 | ANNGEN | general note | \n \n Description:A general or uncategorized note. \r\n\n |
| 4 | ANNIMM | immunization note | A note that is specific to a patient's immunizations, either historical, current or planned. |
| 4 | ANNLAB | laboratory note | \n \n Description:A note that is specific to a patient's laboratory results, either historical, current or planned. \r\n\n |
| 4 | ANNMED | medication note | \n \n Description:A note that is specific to a patient's medications, either historical, current or planned. \r\n\n |
| 2 | (_GeneticObservationType) Abstract | \n \n Description: None provided \r\n\n | |
| 3 | GENE | gene | \n \n Description: A DNA segment that contributes to phenotype/function. In the absence of demonstrated function a gene may be characterized by sequence, transcription or homology \r\n\n |
| 2 | _ImmunizationObservationType | ImmunizationObservationType | \n \n Description: Observation codes which describe characteristics of the immunization material. \r\n\n |
| 3 | OBSANTC | antigen count | \n \n Description: Indicates the valid antigen count. \r\n\n |
| 3 | OBSANTV | antigen validity | \n \n Description: Indicates whether an antigen is valid or invalid. \r\n\n |
| 2 | (_IndividualCaseSafetyReportType) Abstract | \n A code that is used to indicate the type of case safety report received from sender. The current code example reference is from the International Conference on Harmonisation (ICH) Expert Workgroup guideline on Clinical Safety Data Management: Data Elements for Transmission of Individual Case Safety Reports. The unknown/unavailable option allows the transmission of information from a secondary sender where the initial sender did not specify the type of report. \r\n\n Example concepts include: Spontaneous, Report from study, Other. \r\n\n | |
| 3 | PAT_ADV_EVNT | patient adverse event | Indicates that the ICSR is describing problems that a patient experienced after receiving a vaccine product. |
| 3 | VAC_PROBLEM | vaccine product problem | Indicates that the ICSR is describing a problem with the actual vaccine product such as physical defects (cloudy, particulate matter) or inability to confer immunity. |
| 2 | (_LOINCObservationActContextAgeType) Abstract | \n \n Definition:The set of LOINC codes for the act of determining the period of time that has elapsed since an entity was born or created. \r\n\n | |
| 3 | 21611-9 | age patient qn est | \n \n Definition:Estimated age. \r\n\n |
| 3 | 21612-7 | age patient qn reported | \n \n Definition:Reported age. \r\n\n |
| 3 | 29553-5 | age patient qn calc | \n \n Definition:Calculated age. \r\n\n |
| 3 | 30525-0 | age patient qn definition | \n \n Definition:General specification of age with no implied method of determination. \r\n\n |
| 3 | 30972-4 | age at onset of adverse event | \n \n Definition:Age at onset of associated adverse event; no implied method of determination. \r\n\n |
| 2 | (_MedicationObservationType) Abstract | ||
| 3 | REP_HALF_LIFE | representative half-life | \n \n Description:This observation represents an 'average' or 'expected' half-life typical of the product. \r\n\n |
| 3 | SPLCOATING | coating | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, indicating whether it has one or more coatings such as sugar coating, film coating, or enteric coating. Only coatings to the external surface or the dosage form should be considered (for example, coatings to individual pellets or granules inside a capsule or tablet are excluded from consideration). \r\n\n \n Constraints: The Observation.value must be a Boolean (BL) with true for the presence or false for the absence of one or more coatings on a solid dosage form. \r\n\n |
| 3 | SPLCOLOR | color | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the color or colors that most predominantly define the appearance of the dose form. SPLCOLOR is not an FDA specification for the actual color of solid dosage forms or the names of colors that can appear in labeling. \r\n\n \n Constraints: The Observation.value must be a single coded value or a list of multiple coded values, specifying one or more distinct colors that approximate of the color(s) of distinct areas of the solid dosage form, such as the different sides of a tablet or one-part capsule, or the different halves of a two-part capsule. Bands on banded capsules, regardless of the color, are not considered when assigning an SPLCOLOR. Imprints on the dosage form, regardless of their color are not considered when assigning an SPLCOLOR. If more than one color exists on a particular side or half, then the most predominant color on that side or half is recorded. If the gelatin capsule shell is colorless and transparent, use the predominant color of the contents that appears through the colorless and transparent capsule shell. Colors can include: Black;Gray;White;Red;Pink;Purple;Green;Yellow;Orange;Brown;Blue;Turquoise. \r\n\n |
| 3 | SPLIMAGE | image | \n \n Description: A characteristic representing a single file reference that contains two or more views of the same dosage form of the product; in most cases this should represent front and back views of the dosage form, but occasionally additional views might be needed in order to capture all of the important physical characteristics of the dosage form. Any imprint and/or symbol should be clearly identifiable, and the viewer should not normally need to rotate the image in order to read it. Images that are submitted with SPL should be included in the same directory as the SPL file. \r\n\n |
| 3 | SPLIMPRINT | imprint | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the alphanumeric text that appears on the solid dosage form, including text that is embossed, debossed, engraved or printed with ink. The presence of other non-textual distinguishing marks or symbols is recorded by SPLSYMBOL. \r\n\n \n Examples: Included in SPLIMPRINT are alphanumeric text that appears on the bands of banded capsules and logos and other symbols that can be interpreted as letters or numbers. \r\n\n \n Constraints: The Observation.value must be of type Character String (ST). Excluded from SPLIMPRINT are internal and external cut-outs in the form of alphanumeric text and the letter 'R' with a circle around it (when referring to a registered trademark) and the letters 'TM' (when referring to a 'trade mark'). To record text, begin on either side or part of the dosage form. Start at the top left and progress as one would normally read a book. Enter a semicolon to show separation between words or line divisions. \r\n\n |
| 3 | SPLSCORING | scoring | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the number of equal pieces that the solid dosage form can be divided into using score line(s). \r\n\n \n Example: One score line creating two equal pieces is given a value of 2, two parallel score lines creating three equal pieces is given a value of 3. \r\n\n \n Constraints: Whether three parallel score lines create four equal pieces or two intersecting score lines create two equal pieces using one score line and four equal pieces using both score lines, both have the scoring value of 4. Solid dosage forms that are not scored are given a value of 1. Solid dosage forms that can only be divided into unequal pieces are given a null-value with nullFlavor other (OTH). \r\n\n |
| 3 | SPLSHAPE | shape | \n \n Description: A characteristic of an oral solid dosage form of a medicinal product, specifying the two dimensional representation of the solid dose form, in terms of the outside perimeter of a solid dosage form when the dosage form, resting on a flat surface, is viewed from directly above, including slight rounding of corners. SPLSHAPE does not include embossing, scoring, debossing, or internal cut-outs. SPLSHAPE is independent of the orientation of the imprint and logo. Shapes can include: Triangle (3 sided); Square; Round; Semicircle; Pentagon (5 sided); Diamond; Double circle; Bullet; Hexagon (6 sided); Rectangle; Gear; Capsule; Heptagon (7 sided); Trapezoid; Oval; Clover; Octagon (8 sided); Tear; Freeform. \r\n\n |
| 3 | SPLSIZE | size | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the longest single dimension of the solid dosage form as a physical quantity in the dimension of length (e.g., 3 mm). The length is should be specified in millimeters and should be rounded to the nearest whole millimeter. \r\n\n \n Example: SPLSIZE for a rectangular shaped tablet is the length and SPLSIZE for a round shaped tablet is the diameter. \r\n\n |
| 3 | SPLSYMBOL | symbol | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, to describe whether or not the medicinal product has a mark or symbol appearing on it for easy and definite recognition. Score lines, letters, numbers, and internal and external cut-outs are not considered marks or symbols. See SPLSCORING and SPLIMPRINT for these characteristics. \r\n\n \n Constraints: The Observation.value must be a Boolean (BL) with <u>true</u> indicating the presence and <u>false</u> for the absence of marks or symbols. \r\n\n \n Example: \n \r\n\n |
| 2 | (_ObservationIssueTriggerCodedObservationType) Abstract | \n Distinguishes the kinds of coded observations that could be the trigger for clinical issue detection. These are observations that are not measurable, but instead can be defined with codes. Coded observation types include: Allergy, Intolerance, Medical Condition, Pregnancy status, etc. \r\n\n | |
| 3 | (_CaseTransmissionMode) Abstract | \n Code for the mechanism by which disease was acquired by the living subject involved in the public health case. Includes sexually transmitted, airborne, bloodborne, vectorborne, foodborne, zoonotic, nosocomial, mechanical, dermal, congenital, environmental exposure, indeterminate. \r\n\n | |
| 4 | AIRTRNS | airborne transmission | \n Communication of an agent from a living subject or environmental source to a living subject through indirect contact via oral or nasal inhalation. \r\n\n |
| 4 | ANANTRNS | animal to animal transmission | \n Communication of an agent from one animal to another proximate animal. \r\n\n |
| 4 | ANHUMTRNS | animal to human transmission | \n Communication of an agent from an animal to a proximate person. \r\n\n |
| 4 | BDYFLDTRNS | body fluid contact transmission | \n Communication of an agent from one living subject to another living subject through direct contact with any body fluid. \r\n\n |
| 4 | BLDTRNS | blood borne transmission | \n Communication of an agent to a living subject through direct contact with blood or blood products whether the contact with blood is part of a therapeutic procedure or not. \r\n\n |
| 4 | DERMTRNS | transdermal transmission | \n Communication of an agent from a living subject or environmental source to a living subject via agent migration through intact skin. \r\n\n |
| 4 | ENVTRNS | environmental exposure transmission | \n Communication of an agent from an environmental surface or source to a living subject by direct contact. \r\n\n |
| 4 | FECTRNS | fecal-oral transmission | \n Communication of an agent from a living subject or environmental source to a living subject through oral contact with material contaminated by person or animal fecal material. \r\n\n |
| 4 | FOMTRNS | fomite transmission | \n Communication of an agent from an non-living material to a living subject through direct contact. \r\n\n |
| 4 | FOODTRNS | food-borne transmission | \n Communication of an agent from a food source to a living subject via oral consumption. \r\n\n |
| 4 | HUMHUMTRNS | human to human transmission | \n Communication of an agent from a person to a proximate person. \r\n\n |
| 4 | INDTRNS | indeterminate disease transmission mode | \n Communication of an agent to a living subject via an undetermined route. \r\n\n |
| 4 | LACTTRNS | lactation transmission | \n Communication of an agent from one living subject to another living subject through direct contact with mammalian milk or colostrum. \r\n\n |
| 4 | NOSTRNS | nosocomial transmission | \n Communication of an agent from any entity to a living subject while the living subject is in the patient role in a healthcare facility. \r\n\n |
| 4 | PARTRNS | parenteral transmission | \n Communication of an agent from a living subject or environmental source to a living subject where the acquisition of the agent is not via the alimentary canal. \r\n\n |
| 4 | PLACTRNS | transplacental transmission | \n Communication of an agent from a living subject to the progeny of that living subject via agent migration across the maternal-fetal placental membranes while in utero. \r\n\n |
| 4 | SEXTRNS | sexual transmission | \n Communication of an agent from one living subject to another living subject through direct contact with genital or oral tissues as part of a sexual act. \r\n\n |
| 4 | TRNSFTRNS | transfusion transmission | \n Communication of an agent from one living subject to another living subject through direct contact with blood or blood products where the contact with blood is part of a therapeutic procedure. \r\n\n |
| 4 | VECTRNS | vector-borne transmission | \n Communication of an agent from a living subject acting as a required intermediary in the agent transmission process to a recipient living subject via direct contact. \r\n\n |
| 4 | WATTRNS | water-borne transmission | \n Communication of an agent from a contaminated water source to a living subject whether the water is ingested as a food or not. The route of entry of the water may be through any bodily orifice. \r\n\n |
| 2 | _ObservationQualityMeasureAttribute | ObservationQualityMeasureAttribute | \n Codes used to define various metadata aspects of a health quality measure. \r\n\n |
| 3 | AGGREGATE | aggregate measure observation | \n Indicates that the observation is carrying out an aggregation calculation, contained in the value element. \r\n\n |
| 3 | CMPMSRMTH | composite measure method | \n Indicates what method is used in a quality measure to combine the component measure results included in an composite measure. \r\n\n |
| 3 | CMPMSRSCRWGHT | component measure scoring weight | \n An attribute of a quality measure describing the weight this component measure score is to carry in determining the overall composite measure final score. The value is real value greater than 0 and less than 1.0. Each component measure score will be multiplied by its CMPMSRSCRWGHT and then summed with the other component measures to determine the final overall composite measure score. The sum across all CMPMSRSCRWGHT values within a single composite measure SHALL be 1.0. The value assigned is scoped to the composite measure referencing this component measure only. \r\n\n |
| 3 | COPY | copyright | \n Identifies the organization(s) who own the intellectual property represented by the eMeasure. \r\n\n |
| 3 | CRS | clinical recommendation statement | \n Summary of relevant clinical guidelines or other clinical recommendations supporting this eMeasure. \r\n\n |
| 3 | DEF | definition | \n Description of individual terms, provided as needed. \r\n\n |
| 3 | DISC | disclaimer | \n Disclaimer information for the eMeasure. \r\n\n |
| 3 | FINALDT | finalized date/time | \n The timestamp when the eMeasure was last packaged in the Measure Authoring Tool. \r\n\n |
| 3 | GUIDE | guidance | \n Used to allow measure developers to provide additional guidance for implementers to understand greater specificity than could be provided in the logic for data criteria. \r\n\n |
| 3 | IDUR | improvement notation | \n Information on whether an increase or decrease in score is the preferred result \n(e.g., a higher score indicates better quality OR a lower score indicates better quality OR quality is within a range). \n \r\n\n |
| 3 | ITMCNT | items counted | \n Describes the items counted by the measure (e.g., patients, encounters, procedures, etc.) \r\n\n |
| 3 | KEY | keyword | \n A significant word that aids in discoverability. \r\n\n |
| 3 | MEDT | measurement end date | \n The end date of the measurement period. \r\n\n |
| 3 | MSD | measurement start date | \n The start date of the measurement period. \r\n\n |
| 3 | MSRADJ | risk adjustment | \n The method of adjusting for clinical severity and conditions present at the start of care that can influence patient outcomes for making valid comparisons of outcome measures across providers. Indicates whether an eMeasure is subject to the statistical process for reducing, removing, or clarifying the influences of confounding factors to allow more useful comparisons. \r\n\n |
| 3 | MSRAGG | rate aggregation | \n Describes how to combine information calculated based on logic in each of several populations into one summarized result. It can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure. (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). \r\n\n \n Open Issue: The description does NOT align well with the definition used in the HQMF specfication; correct the MSGAGG definition, and the possible distinction of MSRAGG as a child of AGGREGATE. \r\n\n |
| 3 | MSRIMPROV | health quality measure improvement notation | \n Information on whether an increase or decrease in score is the preferred result. This should reflect information on which way is better, an increase or decrease in score. \r\n\n |
| 3 | MSRJUR | jurisdiction | \n The list of jurisdiction(s) for which the measure applies. \r\n\n |
| 3 | MSRRPTR | reporter type | \n Type of person or organization that is expected to report the issue. \r\n\n |
| 3 | MSRRPTTIME | timeframe for reporting | \n The maximum time that may elapse following completion of the measure until the measure report must be sent to the receiver. \r\n\n |
| 3 | MSRSCORE | measure scoring | \n Indicates how the calculation is performed for the eMeasure \n(e.g., proportion, continuous variable, ratio) \r\n\n |
| 3 | MSRSET | health quality measure care setting | \n Location(s) in which care being measured is rendered \r\n\n Usage Note: MSRSET is used rather than RoleCode because the setting applies to what is being measured, as opposed to participating directly in the health quality measure documantion itself). \r\n\n |
| 3 | MSRTOPIC | health quality measure topic type | \n \r\n\n |
| 3 | MSRTP | measurement period | \n The time period for which the eMeasure applies. \r\n\n |
| 3 | MSRTYPE | measure type | \n Indicates whether the eMeasure is used to examine a process or an outcome over time \n(e.g., Structure, Process, Outcome). \r\n\n |
| 3 | RAT | rationale | \n Succinct statement of the need for the measure. Usually includes statements pertaining to Importance criterion: impact, gap in care and evidence. \r\n\n |
| 3 | REF | reference | \n Identifies bibliographic citations or references to clinical practice guidelines, sources of evidence, or other relevant materials supporting the intent and rationale of the eMeasure. \r\n\n |
| 3 | SDE | supplemental data elements | \n Comparison of results across strata can be used to show where disparities exist or where there is a need to expose differences in results. For example, Centers for Medicare & Medicaid Services (CMS) in the U.S. defines four required Supplemental Data Elements (payer, ethnicity, race, and gender), which are variables used to aggregate data into various subgroups. Additional supplemental data elements required for risk adjustment or other purposes of data aggregation can be included in the Supplemental Data Element section. \r\n\n |
| 3 | STRAT | stratification | \n Describes the strata for which the measure is to be evaluated. There are three examples of reasons for stratification based on existing work. These include: (1) evaluate the measure based on different age groupings within the population described in the measure (e.g., evaluate the whole [age 14-25] and each sub-stratum [14-19] and [20-25]); (2) evaluate the eMeasure based on either a specific condition, a specific discharge location, or both; (3) evaluate the eMeasure based on different locations within a facility (e.g., evaluate the overall rate for all intensive care units and also some strata include additional findings [specific birth weights for neonatal intensive care units]). \r\n\n |
| 3 | TRANF | transmission format | \n Can be a URL or hyperlinks that link to the transmission formats that are specified for a particular reporting program. \r\n\n |
| 3 | USE | notice of use | \n Usage notes. \r\n\n |
| 2 | (_ObservationSequenceType) Abstract | ||
| 3 | TIME_ABSOLUTE | absolute time sequence | \n A sequence of values in the "absolute" time domain. This is the same time domain that all HL7 timestamps use. It is time as measured by the Gregorian calendar \r\n\n |
| 3 | TIME_RELATIVE | relative time sequence | \n A sequence of values in a "relative" time domain. The time is measured relative to the earliest effective time in the Observation Series containing this sequence. \r\n\n |
| 2 | (_ObservationSeriesType) Abstract | ||
| 3 | (_ECGObservationSeriesType) Abstract | ||
| 4 | REPRESENTATIVE_BEAT | ECG representative beat waveforms | \n This Observation Series type contains waveforms of a "representative beat" (a.k.a. "median beat" or "average beat"). The waveform samples are measured in relative time, relative to the beginning of the beat as defined by the Observation Series effective time. The waveforms are not directly acquired from the subject, but rather algorithmically derived from the "rhythm" waveforms. \r\n\n |
| 4 | RHYTHM | ECG rhythm waveforms | \n This Observation type contains ECG "rhythm" waveforms. The waveform samples are measured in absolute time (a.k.a. "subject time" or "effective time"). These waveforms are usually "raw" with some minimal amount of noise reduction and baseline filtering applied. \r\n\n |
| 2 | _PatientImmunizationRelatedObservationType | PatientImmunizationRelatedObservationType | \n \n Description: Reporting codes that are related to an immunization event. \r\n\n |
| 3 | CLSSRM | classroom | \n \n Description: The class room associated with the patient during the immunization event. \r\n\n |
| 3 | GRADE | grade | \n \n Description: The school grade or level the patient was in when immunized. \r\n\n |
| 3 | SCHL | school | \n \n Description: The school the patient attended when immunized. \r\n\n |
| 3 | SCHLDIV | school division | \n \n Description: The school division or district associated with the patient during the immunization event. \r\n\n |
| 3 | TEACHER | teacher | \n \n Description: The patient's teacher when immunized. \r\n\n |
| 2 | (_PopulationInclusionObservationType) Abstract | \n Observation types for specifying criteria used to assert that a subject is included in a particular population. \r\n\n | |
| 3 | DENEX | denominator exclusions | \n Criteria which specify subjects who should be removed from the eMeasure population and denominator before determining if numerator criteria are met. Denominator exclusions are used in proportion and ratio measures to help narrow the denominator. \r\n\n |
| 3 | DENEXCEP | denominator exceptions | \n Criteria which specify the removal of a subject, procedure or unit of measurement from the denominator, only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories: \r\n\n \n Medical reasons\n Patient (or subject) reasons\n System reasons\n \n |
| 3 | DENOM | denominator | \n Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). The denominator can be the same as the initial population, or it may be a subset of the initial population to further constrain it for the purpose of the eMeasure. Different measures within an eMeasure set may have different denominators. Continuous Variable eMeasures do not have a denominator, but instead define a measure population. \r\n\n |
| 3 | IPOP | initial population | \n Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). \r\n\n |
| 4 | IPPOP | initial patient population | \n Criteria for specifying the patients to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). Details often include information based upon specific age groups, diagnoses, diagnostic and procedure codes, and enrollment periods. \r\n\n |
| 3 | MSROBS | measure observation | \n Defines the observation to be performed for each patient or event in the measure population. Measure observations for each case in the population are aggregated to determine the overall measure score for the population. \r\n\n \n Examples: \n \r\n\n \n the median time from arrival in the Emergency Room to departure\n the median time from decision to admit to a hospital to the actual admission for Emergency Room patients\n \n |
| 3 | MSRPOPL | measure population | \n Criteria for specifying\nthe measure population as a narrative description (e.g., all patients seen in the Emergency Department during the measurement period). This is used only in continuous variable eMeasures. \r\n\n |
| 3 | MSRPOPLEX | measure population exclusions | \n Criteria for specifying subjects who should be removed from the eMeasure's Initial Population and Measure Population. Measure Population Exclusions are used in Continuous Variable measures to help narrow the Measure Population before determining the value(s) of the continuous variable(s). \r\n\n |
| 3 | NUMER | numerator | \n Criteria for specifying the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator for proportion measures, or related to (but not directly derived from) the denominator for ratio measures (e.g., a numerator listing the number of central line blood stream infections and a denominator indicating the days per thousand of central line usage in a specific time period). \r\n\n |
| 3 | NUMEX | numerator exclusions | \n Criteria for specifying instances that should not be included in the numerator data. (e.g., if the number of central line blood stream infections per 1000 catheter days were to exclude infections with a specific bacterium, that bacterium would be listed as a numerator exclusion). Numerator Exclusions are used only in ratio eMeasures. \r\n\n |
| 2 | (_PreferenceObservationType) Abstract | \n Types of observations that can be made about Preferences. \r\n\n | |
| 3 | PREFSTRENGTH | preference strength | \n An observation about how important a preference is to the target of the preference. \r\n\n |
| 2 | ADVERSE_REACTION | Adverse Reaction | \n Indicates that the observation is of an unexpected negative occurrence in the subject suspected to result from the subject's exposure to one or more agents. Observation values would be the symptom resulting from the reaction. \r\n\n |
| 2 | ASSERTION | Assertion | \n \n Description:Refines classCode OBS to indicate an observation in which observation.value contains a finding or other nominalized statement, where the encoded information in Observation.value is not altered by Observation.code. For instance, observation.code="ASSERTION" and observation.value="fracture of femur present" is an assertion of a clinical finding of femur fracture. \r\n\n |
| 2 | CASESER | case seriousness criteria | \n \n Definition:An observation that provides a characterization of the level of harm to an investigation subject as a result of a reaction or event. \r\n\n |
| 2 | CDIO | case disease imported observation | \n An observation that states whether the disease was likely acquired outside the jurisdiction of observation, and if so, the nature of the inter-jurisdictional relationship. \r\n\n \n OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it. \r\n\n |
| 2 | CRIT | criticality | \n A clinical judgment as to the worst case result of a future exposure (including substance administration). When the worst case result is assessed to have a life-threatening or organ system threatening potential, it is considered to be of high criticality. \r\n\n |
| 2 | CTMO | case transmission mode observation | \n An observation that states the mechanism by which disease was acquired by the living subject involved in the public health case. \r\n\n \n OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it. \r\n\n |
| 2 | DX | ObservationDiagnosisTypes | \n Includes all codes defining types of indications such as diagnosis, symptom and other indications such as contrast agents for lab tests. \r\n\n |
| 3 | ADMDX | admitting diagnosis | \n Admitting diagnosis are the diagnoses documented for administrative purposes as the basis for a hospital admission. \r\n\n |
| 3 | DISDX | discharge diagnosis | \n Discharge diagnosis are the diagnoses documented for administrative purposes as the time of hospital discharge. \r\n\n |
| 3 | INTDX | intermediate diagnosis | \n Intermediate diagnoses are those diagnoses documented for administrative purposes during the course of a hospital stay. \r\n\n |
| 3 | NOI | nature of injury | \n The type of injury that the injury coding specifies. \r\n\n |
| 2 | GISTIER | GIS tier | \n \n Description: Accuracy determined as per the GIS tier code system. \r\n\n |
| 2 | HHOBS | household situation observation | \n Indicates that the observation is of a person's living situation in a household including the household composition and circumstances. \r\n\n |
| 2 | ISSUE | detected issue | \n There is a clinical issue for the therapy that makes continuation of the therapy inappropriate. \r\n\n \n Open Issue: The definition of this code does not correctly represent the concept space of its specializations (children) \r\n\n |
| 3 | (_ActAdministrativeDetectedIssueCode) Abstract | \n Identifies types of detectyed issues for Act class "ALRT" for the administrative and patient administrative acts domains. \r\n\n | |
| 4 | (_ActAdministrativeAuthorizationDetectedIssueCode) Abstract | ||
| 5 | NAT | Insufficient authorization | \n The requesting party has insufficient authorization to invoke the interaction. \r\n\n |
| 5 | SUPPRESSED | record suppressed | \n \n Description: One or more records in the query response have been suppressed due to consent or privacy restrictions. \r\n\n |
| 5 | VALIDAT | validation issue | \n \n Description:The specified element did not pass business-rule validation. \r\n\n |
| 6 | KEY204 | Unknown key identifier | \n The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient. \r\n\n |
| 6 | KEY205 | Duplicate key identifier | \n The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.). \r\n\n |
| 6 | COMPLY | Compliance Alert | \n There may be an issue with the patient complying with the intentions of the proposed therapy \r\n\n |
| 7 | DUPTHPY | Duplicate Therapy Alert | \n The proposed therapy appears to duplicate an existing therapy \r\n\n |
| 8 | DUPTHPCLS | duplicate therapeutic alass alert | \n \n Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy, though the specific mechanisms of action vary. \r\n\n |
| 8 | DUPTHPGEN | duplicate generic alert | \n \n Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy and uses the same mechanisms of action as the existing therapy. \r\n\n |
| 7 | ABUSE | commonly abused/misused alert | \n \n Description:The proposed therapy is frequently misused or abused and therefore should be used with caution and/or monitoring. \r\n\n |
| 7 | FRAUD | potential fraud | \n \n Description:The request is suspected to have a fraudulent basis. \r\n\n |
| 7 | PLYDOC | Poly-orderer Alert | \n A similar or identical therapy was recently ordered by a different practitioner. \r\n\n |
| 7 | PLYPHRM | Poly-supplier Alert | \n This patient was recently supplied a similar or identical therapy from a different pharmacy or supplier. \r\n\n |
| 6 | DOSE | Dosage problem | \n Proposed dosage instructions for therapy differ from standard practice. \r\n\n |
| 7 | DOSECOND | dosage-condition alert | \n \n Description:Proposed dosage is inappropriate due to patient's medical condition. \r\n\n |
| 7 | DOSEDUR | Dose-Duration Alert | \n Proposed length of therapy differs from standard practice. \r\n\n |
| 8 | DOSEDURH | Dose-Duration High Alert | \n Proposed length of therapy is longer than standard practice \r\n\n |
| 9 | DOSEDURHIND | Dose-Duration High for Indication Alert | \n Proposed length of therapy is longer than standard practice for the identified indication or diagnosis \r\n\n |
| 8 | DOSEDURL | Dose-Duration Low Alert | \n Proposed length of therapy is shorter than that necessary for therapeutic effect \r\n\n |
| 9 | DOSEDURLIND | Dose-Duration Low for Indication Alert | \n Proposed length of therapy is shorter than standard practice for the identified indication or diagnosis \r\n\n |
| 7 | DOSEH | High Dose Alert | \n Proposed dosage exceeds standard practice \r\n\n |
| 8 | DOSEHINDA | High Dose for Age Alert | \n Proposed dosage exceeds standard practice for the patient's age \r\n\n |
| 8 | DOSEHIND | High Dose for Indication Alert | |
| 8 | DOSEHINDSA | High Dose for Height/Surface Area Alert | \n Proposed dosage exceeds standard practice for the patient's height or body surface area \r\n\n |
| 8 | DOSEHINDW | High Dose for Weight Alert | \n Proposed dosage exceeds standard practice for the patient's weight \r\n\n |
| 7 | DOSEIVL | Dose-Interval Alert | \n Proposed dosage interval/timing differs from standard practice \r\n\n |
| 8 | DOSEIVLIND | Dose-Interval for Indication Alert | \n Proposed dosage interval/timing differs from standard practice for the identified indication or diagnosis \r\n\n |
| 7 | DOSEL | Low Dose Alert | \n Proposed dosage is below suggested therapeutic levels \r\n\n |
| 8 | DOSELINDA | Low Dose for Age Alert | \n Proposed dosage is below suggested therapeutic levels for the patient's age \r\n\n |
| 8 | DOSELIND | Low Dose for Indication Alert | |
| 8 | DOSELINDSA | Low Dose for Height/Surface Area Alert | \n Proposed dosage is below suggested therapeutic levels for the patient's height or body surface area \r\n\n |
| 8 | DOSELINDW | Low Dose for Weight Alert | \n Proposed dosage is below suggested therapeutic levels for the patient's weight \r\n\n |
| 7 | MDOSE | maximum dosage reached | \n \n Description:The maximum quantity of this drug allowed to be administered within a particular time-range (month, year, lifetime) has been reached or exceeded. \r\n\n |
| 6 | OBSA | Observation Alert | \n Proposed therapy may be inappropriate or contraindicated due to conditions or characteristics of the patient \r\n\n |
| 7 | AGE | Age Alert | \n Proposed therapy may be inappropriate or contraindicated due to patient age \r\n\n |
| 8 | ADALRT | adult alert | \n Proposed therapy is outside of the standard practice for an adult patient. \r\n\n |
| 8 | DOSEHINDA | ||
| 8 | DOSELINDA | ||
| 8 | GEALRT | geriatric alert | \n Proposed therapy is outside of standard practice for a geriatric patient. \r\n\n |
| 8 | PEALRT | pediatric alert | \n Proposed therapy is outside of the standard practice for a pediatric patient. \r\n\n |
| 7 | COND | Condition Alert | \n Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis \r\n\n |
| 8 | HGHT | ||
| 8 | LACT | Lactation Alert | \n Proposed therapy may be inappropriate or contraindicated when breast-feeding \r\n\n |
| 8 | PREG | Pregnancy Alert | \n Proposed therapy may be inappropriate or contraindicated during pregnancy \r\n\n |
| 8 | WGHT | ||
| 7 | CREACT | common reaction alert | \n \n Description:Proposed therapy may be inappropriate or contraindicated because of a common but non-patient specific reaction to the product. \r\n\n \n Example:There is no record of a specific sensitivity for the patient, but the presence of the sensitivity is common and therefore caution is warranted. \r\n\n |
| 7 | GEN | Genetic Alert | \n Proposed therapy may be inappropriate or contraindicated due to patient genetic indicators. \r\n\n |
| 7 | GEND | Gender Alert | \n Proposed therapy may be inappropriate or contraindicated due to patient gender. \r\n\n |
| 7 | LAB | Lab Alert | \n Proposed therapy may be inappropriate or contraindicated due to recent lab test results \r\n\n |
| 7 | REACT | Reaction Alert | \n Proposed therapy may be inappropriate or contraindicated based on the potential for a patient reaction to the proposed product \r\n\n |
| 8 | ALGY | Allergy Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to the proposed product. (Allergies are immune based reactions.) \r\n\n |
| 8 | INT | Intolerance Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to the proposed product. (Intolerances are non-immune based sensitivities.) \r\n\n |
| 7 | RREACT | Related Reaction Alert | \n Proposed therapy may be inappropriate or contraindicated because of a potential patient reaction to a cross-sensitivity related product. \r\n\n |
| 8 | RALG | Related Allergy Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to a cross-sensitivity related product. (Allergies are immune based reactions.) \r\n\n |
| 8 | RAR | Related Prior Reaction Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded prior adverse reaction to a cross-sensitivity related product. \r\n\n |
| 8 | RINT | Related Intolerance Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to a cross-sensitivity related product. (Intolerances are non-immune based sensitivities.) \r\n\n |
| 6 | BUS | business constraint violation | \n \n Description:A local business rule relating multiple elements has been violated. \r\n\n |
| 6 | CODE_INVAL | code is not valid | \n \n Description:The specified code is not valid against the list of codes allowed for the element. \r\n\n |
| 7 | CODE_DEPREC | code has been deprecated | \n \n Description:The specified code has been deprecated and should no longer be used. Select another code from the code system. \r\n\n |
| 6 | FORMAT | invalid format | \n \n Description:The element does not follow the formatting or type rules defined for the field. \r\n\n |
| 6 | ILLEGAL | illegal | \n \n Description:The request is missing elements or contains elements which cause it to not meet the legal standards for actioning. \r\n\n |
| 6 | LEN_RANGE | length out of range | \n \n Description:The length of the data specified falls out of the range defined for the element. \r\n\n |
| 7 | LEN_LONG | length is too long | \n \n Description:The length of the data specified is greater than the maximum length defined for the element. \r\n\n |
| 7 | LEN_SHORT | length is too short | \n \n Description:The length of the data specified is less than the minimum length defined for the element. \r\n\n |
| 6 | MISSCOND | conditional element missing | \n \n Description:The specified element must be specified with a non-null value under certain conditions. In this case, the conditions are true but the element is still missing or null. \r\n\n |
| 6 | MISSMAND | mandatory element missing | \n \n Description:The specified element is mandatory and was not included in the instance. \r\n\n |
| 6 | NODUPS | duplicate values are not permitted | \n \n Description:More than one element with the same value exists in the set. Duplicates not permission in this set in a set. \r\n\n |
| 6 | NOPERSIST | element will not be persisted | \n \n Description: Element in submitted message will not persist in data storage based on detected issue. \r\n\n |
| 6 | REP_RANGE | repetitions out of range | \n \n Description:The number of repeating elements falls outside the range of the allowed number of repetitions. \r\n\n |
| 7 | MAXOCCURS | repetitions above maximum | \n \n Description:The number of repeating elements is above the maximum number of repetitions allowed. \r\n\n |
| 7 | MINOCCURS | repetitions below minimum | \n \n Description:The number of repeating elements is below the minimum number of repetitions allowed. \r\n\n |
| 4 | (_ActAdministrativeRuleDetectedIssueCode) Abstract | ||
| 5 | KEY204 | ||
| 5 | KEY205 | ||
| 5 | KEY206 | non-matching identification | \n \n Description: Metadata associated with the identification (e.g. name or gender) does not match the identification being verified. \r\n\n |
| 5 | OBSOLETE | obsolete record returned | \n \n Description: One or more records in the query response have a status of 'obsolete'. \r\n\n |
| 3 | (_ActSuppliedItemDetectedIssueCode) Abstract | \n Identifies types of detected issues regarding the administration or supply of an item to a patient. \r\n\n | |
| 4 | (_AdministrationDetectedIssueCode) Abstract | \n Administration of the proposed therapy may be inappropriate or contraindicated as proposed \r\n\n | |
| 5 | (_AppropriatenessDetectedIssueCode) Abstract | ||
| 6 | (_InteractionDetectedIssueCode) Abstract | ||
| 7 | FOOD | Food Interaction Alert | \n Proposed therapy may interact with certain foods \r\n\n |
| 7 | TPROD | Therapeutic Product Alert | \n Proposed therapy may interact with an existing or recent therapeutic product \r\n\n |
| 8 | DRG | Drug Interaction Alert | \n Proposed therapy may interact with an existing or recent drug therapy \r\n\n |
| 8 | NHP | Natural Health Product Alert | \n Proposed therapy may interact with existing or recent natural health product therapy \r\n\n |
| 8 | NONRX | Non-Prescription Interaction Alert | \n Proposed therapy may interact with a non-prescription drug (e.g. alcohol, tobacco, Aspirin) \r\n\n |
| 6 | OBSA | ||
| 6 | PREVINEF | previously ineffective | \n \n Definition:The same or similar treatment has previously been attempted with the patient without achieving a positive effect. \r\n\n |
| 5 | COMPLY | ||
| 5 | DACT | drug action detected issue | \n \n Description:Proposed therapy may be contraindicated or ineffective based on an existing or recent drug therapy. \r\n\n |
| 5 | DOSE | ||
| 5 | DUPTHPY | ||
| 5 | TIME | timing detected issue | \n \n Description:Proposed therapy may be inappropriate or ineffective based on the proposed start or end time. \r\n\n |
| 6 | ALRTENDLATE | end too late alert | \n \n Definition:Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy. \r\n\n |
| 6 | ALRTSTRTLATE | start too late alert | \n \n Definition:Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition. \r\n\n |
| 5 | (_TimingDetectedIssueCode) Abstract | \n Proposed therapy may be inappropriate or ineffective based on the proposed start or end time. \r\n\n | |
| 6 | ENDLATE | End Too Late Alert | \n Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy \r\n\n |
| 6 | STRTLATE | Start Too Late Alert | \n Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition \r\n\n |
| 4 | (_SupplyDetectedIssueCode) Abstract | \n Supplying the product at this time may be inappropriate or indicate compliance issues with the associated therapy \r\n\n | |
| 5 | ALLDONE | already performed | \n \n Definition:The requested action has already been performed and so this request has no effect \r\n\n |
| 5 | FULFIL | fulfillment alert | \n \n Definition:The therapy being performed is in some way out of alignment with the requested therapy. \r\n\n |
| 6 | NOTACTN | no longer actionable | \n \n Definition:The status of the request being fulfilled has changed such that it is no longer actionable. This may be because the request has expired, has already been completely fulfilled or has been otherwise stopped or disabled. (Not used for 'suspended' orders.) \r\n\n |
| 6 | NOTEQUIV | not equivalent alert | \n \n Definition:The therapy being performed is not sufficiently equivalent to the therapy which was requested. \r\n\n |
| 7 | NOTEQUIVGEN | not generically equivalent alert | \n \n Definition:The therapy being performed is not generically equivalent (having the identical biological action) to the therapy which was requested. \r\n\n |
| 7 | NOTEQUIVTHER | not therapeutically equivalent alert | \n \n Definition:The therapy being performed is not therapeutically equivalent (having the same overall patient effect) to the therapy which was requested. \r\n\n |
| 6 | TIMING | event timing incorrect alert | \n \n Definition:The therapy is being performed at a time which diverges from the time the therapy was requested \r\n\n |
| 7 | INTERVAL | outside requested time | \n \n Definition:The therapy action is being performed outside the bounds of the time period requested \r\n\n |
| 7 | MINFREQ | too soon within frequency based on the usage | \n \n Definition:The therapy action is being performed too soon after the previous occurrence based on the requested frequency \r\n\n |
| 5 | HELD | held/suspended alert | \n \n Definition:There should be no actions taken in fulfillment of a request that has been held or suspended. \r\n\n |
| 5 | TOOLATE | Refill Too Late Alert | \n The patient is receiving a subsequent fill significantly later than would be expected based on the amount previously supplied and the therapy dosage instructions \r\n\n |
| 5 | TOOSOON | Refill Too Soon Alert | \n The patient is receiving a subsequent fill significantly earlier than would be expected based on the amount previously supplied and the therapy dosage instructions \r\n\n |
| 4 | HISTORIC | record recorded as historical | \n \n Description: While the record was accepted in the repository, there is a more recent version of a record of this type. \r\n\n |
| 4 | PATPREF | violates stated preferences | \n \n Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. \r\n\n |
| 5 | PATPREFALT | violates stated preferences, alternate available | \n \n Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. An alternate therapy meeting those constraints is available. \r\n\n |
| 2 | KSUBJ | knowledge subject | Categorization of types of observation that capture the main clinical knowledge subject which may be a medication, a laboratory test, a disease. |
| 2 | KSUBT | knowledge subtopic | Categorization of types of observation that capture a knowledge subtopic which might be treatment, etiology, or prognosis. |
| 2 | OINT | intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to an agent. \r\n\n |
| 3 | ALG | Allergy | \n Hypersensitivity to an agent caused by an immunologic response to an initial exposure \r\n\n |
| 4 | DALG | Drug Allergy | \n An allergy to a pharmaceutical product. \r\n\n |
| 4 | EALG | Environmental Allergy | \n An allergy to a substance other than a drug or a food. E.g. Latex, pollen, etc. \r\n\n |
| 4 | FALG | Food Allergy | \n An allergy to a substance generally consumed for nutritional purposes. \r\n\n |
| 3 | DINT | Drug Intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to a drug. \r\n\n |
| 4 | DALG | ||
| 4 | DNAINT | Drug Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 3 | EINT | Environmental Intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to environmental conditions. \r\n\n |
| 4 | EALG | ||
| 4 | ENAINT | Environmental Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 3 | FINT | Food Intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to food. \r\n\n |
| 4 | FALG | ||
| 4 | FNAINT | Food Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 3 | NAINT | Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 4 | DNAINT | ||
| 4 | ENAINT | ||
| 4 | FNAINT | ||
| 2 | SEV | Severity Observation | \n A subjective evaluation of the seriousness or intensity associated with another observation. \r\n\n |
| 2 | (_FDALabelData) Abstract | \n FDA label data \r\n\n | |
| 3 | FDACOATING | coating | \n FDA label coating \r\n\n |
| 3 | FDACOLOR | color | \n FDA label color \r\n\n |
| 3 | FDAIMPRINTCD | imprint code | \n FDA label imprint code \r\n\n |
| 3 | FDALOGO | logo | \n FDA label logo \r\n\n |
| 3 | FDASCORING | scoring | \n FDA label scoring \r\n\n |
| 3 | FDASHAPE | shape | \n FDA label shape \r\n\n |
| 3 | FDASIZE | size | \n FDA label size \r\n\n |
| 1 | (_ROIOverlayShape) Abstract | \n Shape of the region on the object being referenced \r\n\n | |
| 2 | CIRCLE | circle | \n A circle defined by two (column,row) pairs. The first point is the center of the circle and the second point is a point on the perimeter of the circle. \r\n\n |
| 2 | ELLIPSE | ellipse | \n An ellipse defined by four (column,row) pairs, the first two points specifying the endpoints of the major axis and the second two points specifying the endpoints of the minor axis. \r\n\n |
| 2 | POINT | point | \n A single point denoted by a single (column,row) pair, or multiple points each denoted by a (column,row) pair. \r\n\n |
| 2 | POLY | polyline | \n A series of connected line segments with ordered vertices denoted by (column,row) pairs; if the first and last vertices are the same, it is a closed polygon. \r\n\n |
| 1 | C | corrected | \n \n Description:Indicates that result data has been corrected. \r\n\n |
| 1 | DIET | Diet | \n Code set to define specialized/allowed diets \r\n\n |
| 2 | BR | breikost (GE) | \n A diet exclusively composed of oatmeal, semolina, or rice, to be extremely easy to eat and digest. \r\n\n |
| 2 | DM | diabetes mellitus diet | \n A diet that uses carbohydrates sparingly. Typically with a restriction in daily energy content (e.g. 1600-2000 kcal). \r\n\n |
| 2 | FAST | fasting | \n No enteral intake of foot or liquids whatsoever, no smoking. Typically 6 to 8 hours before anesthesia. \r\n\n |
| 2 | FORMULA | formula diet | \n A diet consisting of a formula feeding, either for an infant or an adult, to provide nutrition either orally or through the gastrointestinal tract via tube, catheter or stoma. \r\n\n |
| 2 | GF | gluten free | \n Gluten free diet for celiac disease. \r\n\n |
| 2 | LF | low fat | \n A diet low in fat, particularly to patients with hepatic diseases. \r\n\n |
| 2 | LP | low protein | \n A low protein diet for patients with renal failure. \r\n\n |
| 2 | LQ | liquid | \n A strictly liquid diet, that can be fully absorbed in the intestine, and therefore may not contain fiber. Used before enteral surgeries. \r\n\n |
| 2 | LS | low sodium | \n A diet low in sodium for patients with congestive heart failure and/or renal failure. \r\n\n |
| 2 | N | normal diet | \n A normal diet, i.e. no special preparations or restrictions for medical reasons. This is notwithstanding any preferences the patient might have regarding special foods, such as vegetarian, kosher, etc. \r\n\n |
| 2 | NF | no fat | \n A no fat diet for acute hepatic diseases. \r\n\n |
| 2 | PAF | phenylalanine free | \n Phenylketonuria diet. \r\n\n |
| 2 | PAR | parenteral | \n Patient is supplied with parenteral nutrition, typically described in terms of i.v. medications. \r\n\n |
| 2 | RD | reduction diet | \n A diet that seeks to reduce body fat, typically low energy content (800-1600 kcal). \r\n\n |
| 2 | SCH | schonkost (GE) | \n A diet that avoids ingredients that might cause digestion problems, e.g., avoid excessive fat, avoid too much fiber (cabbage, peas, beans). \r\n\n |
| 2 | SUPPLEMENT | nutritional supplement | \n A diet that is not intended to be complete but is added to other diets. \r\n\n |
| 2 | T | tea only | \n This is not really a diet, since it contains little nutritional value, but is essentially just water. Used before coloscopy examinations. \r\n\n |
| 2 | VLI | low valin, leucin, isoleucin | \n Diet with low content of the amino-acids valin, leucin, and isoleucin, for "maple syrup disease." \r\n\n |
| 1 | DRUGPRG | drug program | \n \n Definition: A public or government health program that administers and funds coverage for prescription drugs to assist program eligible who meet financial and health status criteria. \r\n\n |
| 1 | F | final | \n \n Description:Indicates that a result is complete. No further results are to come. This maps to the 'complete' state in the observation result status code. \r\n\n |
| 1 | PRLMN | preliminary | \n \n Description:Indicates that a result is incomplete. There are further results to come. This maps to the 'active' state in the observation result status code. \r\n\n |
| 1 | (SECOBS) Abstract | \n An observation identifying security metadata about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used to name security labels. \r\n\n \n Rationale: According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator's clearance to the target's security label. All of the following must be true for authorization to be granted: \r\n\n \n The security policy identifiers shall be identical\n The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and \n For each security category in the target label, there shall be a security category of the same type in the initiator's clearance and the initiator's classification level shall dominate that of the target.\n \n \n Examples: SecurityObservationType security label fields include: \r\n\n \n Confidentiality classification\n Compartment category\n Sensitivity category\n Security mechanisms used to ensure data integrity or to perform authorized data transformation\n Indicators of an IT resource completeness, veracity, reliability, trustworthiness, or provenance.\n \n \n Usage Note: SecurityObservationType codes designate security label field types, which are valued with an applicable SecurityObservationValue code as the "security label tag". \r\n\n | |
| 2 | SECCATOBS | security category observation | \n Type of security metadata observation made about the category of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security category metadata is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone." \r\n\n \n Rationale: A security category observation supports requirement to specify the type of IT resource to facilitate application of appropriate levels of information security according to a range of levels of impact or consequences that might result from the unauthorized disclosure, modification, or use of the information or information system. A resource is assigned to a specific category of information (e.g., privacy, medical, proprietary, financial, investigative, contractor sensitive, security management) defined by an organization or in some instances, by a specific law, Executive Order, directive, policy, or regulation. [FIPS 199] \r\n\n \n Examples: Types of security categories include: \r\n\n \n Compartment: A division of data into isolated blocks with separate security controls for the purpose of reducing risk. (ISO 2382-8). A security label tag that "segments" an IT resource by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Classification System) \n Sensitivity: The characteristic of an IT resource which implies its value or importance and may include its vulnerability. (ISO 7492-2) Privacy metadata for information perceived as undesirable to share. (HL7 Healthcare Classification System)\n \n |
| 2 | SECCLASSOBS | security classification observation | \n Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection." Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure. \r\n\n \n Rationale: A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue. This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality. \r\n\n \n Examples: Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal. Intelligence community examples include top secret, secret, and confidential. \r\n\n \n Usage Note: Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObservationValue code as the "security label tag". \r\n\n |
| 2 | SECCONOBS | security control observation | \n Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security control metadata convey instructions to users and receivers for secure distribution, transmission, and storage; dictate obligations or mandated actions; specify any action prohibited by refrain policy such as dissemination controls; and stipulate the permissible purpose of use of an IT resource. \r\n\n \n Rationale: A security control observation supports requirement to specify applicable management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. [FIPS 199] \r\n\n \n Examples: Types of security control metadata include: \r\n\n \n handling caveats\n dissemination controls\n obligations\n refrain policies\n purpose of use constraints\n \n |
| 2 | SECINTOBS | security integrity observation | \n Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. \r\n\n \n Rationale: A security integrity observation supports the requirement to guard against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. (44 U.S.C., SEC. 3542) \r\n\n \n Examples: Types of security integrity metadata include: \r\n\n \n Integrity status, which indicates the completeness or workflow status of an IT resource (data, information object, service, or system capability)\n Integrity confidence, which indicates the reliability and trustworthiness of an IT resource\n Integrity control, which indicates pertinent handling caveats, obligations, refrain policies, and purpose of use for the resource\n Data integrity, which indicate the security mechanisms used to ensure that the accuracy and consistency are preserved regardless of changes made (ISO/IEC DIS 2382-8)\n Alteration integrity, which indicate the security mechanisms used for authorized transformations of the resource\n Integrity provenance, which indicates the entity responsible for a report or assertion relayed "second-hand" about an IT resource\n \n |
| 3 | SECALTINTOBS | security alteration integrity observation | \n Type of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource. \r\n\n \n Examples: Types of security alteration integrity observation metadata, which may value the observation with a code used to indicate the mechanism used for authorized transformation of an IT resource, including: \r\n\n \n translation\n syntactic transformation\n semantic mapping\n redaction\n masking\n pseudonymization\n anonymization\n \n |
| 3 | SECDATINTOBS | security data integrity observation | \n Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency. Data integrity is defined by ISO 22600-23.3.21 as: "The property that data has not been altered or destroyed in an unauthorized manner", and by ISO/IEC 2382-8: The property of data whose accuracy and consistency are preserved regardless of changes made." \r\n\n \n Examples: Types of security data integrity observation metadata, which may value the observation, include cryptographic hash function and digital signature. \r\n\n |
| 3 | SECINTCONOBS | security integrity confidence observation | \n Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. \r\n\n \n Examples: Types of security integrity confidence observation metadata, which may value the observation, include highly reliable, uncertain reliability, and not reliable. \r\n\n \n Usage Note: A security integrity confidence observation on an Act may indicate that a valued Act.uncertaintycode attribute has been overridden by the entity responsible for ascribing the SecurityIntegrityConfidenceObservationValue. This supports the business requirements for increasing or decreasing the assessment of the reliability or trustworthiness of an IT resource based on parameters beyond the original assignment of an Act statement level of uncertainty. \r\n\n |
| 3 | (SECINTPRVOBS) Abstract | \n Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness of an IT resource in terms of workflow status such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure. Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness. \r\n\n \n Examples: Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: \r\n\n \n completeness or workflow status, such as authentication\n the entity responsible for original authoring or informing about an IT resource\n the entity responsible for a report or assertion about an IT resource relayed (second-hand)?\n the entity responsible for excerpting, transforming, or compiling an IT resource\n \n | |
| 4 | SECINTPRVABOBS | security integrity provenance asserted by observation | \n Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource. The asserting entity may not be the original informant about the resource. \r\n\n \n Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including: \r\n\n \n assertions about an IT resource by a patient\n assertions about an IT resource by a clinician\n assertions about an IT resource by a device\n \n |
| 4 | SECINTPRVRBOBS | security integrity provenance reported by observation | \n Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource. The reporting entity may not be the original author of the resource. \r\n\n \n Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include: \r\n\n \n reports about an IT resource by a patient\n reports about an IT resource by a clinician\n reports about an IT resource by a device\n \n |
| 3 | SECINTSTOBS | security integrity status observation | \n Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Indicates the completeness of an IT resource in terms of workflow status, which may impact users that are authorized to access and use the resource. \r\n\n \n Examples: Types of security integrity status observation metadata, which may value the observation, include codes from the HL7 DocumentCompletion code system such as legally authenticated, in progress, and incomplete. \r\n\n |
| 2 | (SECTRSTOBS) Abstract | \n An observation identifying trust metadata about an IT resource (data, information object, service, or system capability), which may be used as a trust attribute to populate a computable trust policy, trust credential, trust assertion, or trust label field in a security label or trust policy, which are principally used for authentication, authorization, and access control decisions. \r\n\n | |
| 3 | TRSTACCRDOBS | trust accreditation observation | \n Type of security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. \r\n\n |
| 3 | TRSTAGREOBS | trust agreement observation | \n Type of security metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] \r\n\n |
| 3 | TRSTCERTOBS | trust certificate observation | \n Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] \r\n\n \n For example,\n \r\n\n \n A Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. For example, a particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.\n A Certificate Practice Statement (CSP), which is a statement of the practices which an Authority employs in issuing and managing certificates. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.]\n \n |
| 3 | TRSTFWKOBS | trust framework observation | \n Type of security metadata observation made about a complete set of contracts, regulations or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative] \r\n\n |
| 3 | TRSTLOAOBS | trust assurance observation | \n Type of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. \r\n\n |
| 3 | TRSTMECOBS | trust mechanism observation | \n Type of security metadata observation made about a security architecture system component that supports enforcement of security policies. \r\n\n |
| 1 | SUBSIDFFS | subsidized fee for service program | \n \n Definition: A government health program that provides coverage on a fee for service basis for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n \n Discussion: The structure and business processes for underwriting and administering a subsidized fee for service program is further specified by the Underwriter and Payer Role.class and Role.code. \r\n\n |
| 1 | WRKCOMP | (workers compensation program | \n \n Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment. Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program. Employees may be required to pay premiums toward the cost of coverage as well. \r\n\n |
| 1 | (_ActProcedureCode) Abstract | \n An identifying code for healthcare interventions/procedures. \r\n\n | |
| 2 | (_ActBillableServiceCode) Abstract | \n \n Definition: An identifying code for billable services, as opposed to codes for similar services used to identify them for functional purposes. \r\n\n | |
| 1 | (_HL7DefinedActCodes) Abstract | \n Domain provides the root for HL7-defined detailed or rich codes for the Act classes. \r\n\n | |
| 1 | COPAY | ||
| 1 | DEDUCT | ||
| 1 | DOSEIND | ||
| 1 | PRA | ||
| 1 | STORE Deprecated | Storage | \n The act of putting something away for safe keeping. The "something" may be physical object such as a specimen, or information, such as observations regarding a specimen. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nDescription:\nAn act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. Thecode\nattribute of Observation and thevalue\nattribute of Observation must be considered in combination to determine the semantics of the observation. Discussion:\nStructurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. Examples:\nRecording the results of a Family History Assessment Laboratory test and associated result Physical exam test and associated result Device temperature Soil lead level
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a OBSA person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a VRFDescribes an individual's typical arrangement of working hours for an occupation.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ObservationValue where concept is-a _WorkSchedulehttp://terminology.hl7.org/CodeSystem/v3-ObservationValue| Code | Display | |
| _WorkSchedule | _WorkSchedule | Concepts that describe an individual's typical arrangement of working hours for an occupation. |
The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a FLFSType of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActInvoiceGroupCodehttp://terminology.hl7.org/CodeSystem/v3-ActCode| Code | Display | |
| _ActInvoiceGroupCode | ActInvoiceGroupCode | Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. |
Release Date: 2018-08-12
\r\nA relationship between two people characterizing their "familial" relationship
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleCode where concept is-a FAMMEMBRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nPotential values for observations of severity.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ObservationValue where concept is-a _SeverityObservationhttp://terminology.hl7.org/CodeSystem/v3-ObservationValue| Code | Display | |
| _SeverityObservation | SeverityObservation | Potential values for observations of severity. |
A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a SPECA general association between two entities that is neither partitive nor ontological.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a _RoleClassAssociativehttp://terminology.hl7.org/CodeSystem/v3-RoleClass| Code | Display | |
| _RoleClassAssociative | RoleClassAssociative | A general association between two entities that is neither partitive nor ontological. |
Definition:\nA person playing the role of program eligible under a program based on military status. Discussion:\nThis CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a member of the military meets jurisdictional or program criteria
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleCode where concept is-a MILConveys the mandated workflow action that an information custodian, receiver, or user must perform. Examples:\nencrypt Usage Note:\nPer OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a ObligationPolicySpecialization of Act to add the characteristics unique to document management services.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a DOCRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nCorresponds to the ManufacturedMaterial class
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityClass where concept is-a MMATSet of codes indicating the type of incident or accident.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActIncidentCodehttp://terminology.hl7.org/CodeSystem/v3-ActCode| Code | Display | |
| _ActIncidentCode | ActIncidentCode | Set of codes indicating the type of incident or accident. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nThe principle target that the service acts on. E.g. the patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects, consumables, and devices used as tools for a service are not subjects. However, a device may be a subject of a maintenance service.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a SBJRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nSpecifies the state change of a target Act, such as a document or an entry, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".
\nThis value set includes codes from the following code systems:
An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a INVSTGRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
Release Date: 2018-08-12
\r\nAn entity (player) that acts or is authorized to act on behalf of another entity (scoper).
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a AGNTDomain provides codes that qualify the ActEncounterClass (ENC)
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActEncounterCodehttp://terminology.hl7.org/CodeSystem/v3-ActCode| Code | Display | |
| _ActEncounterCode | ActEncounterCode | Domain provides codes that qualify the ActEncounterClass (ENC) |
Release Date: 2018-08-12
\r\nSecurity observation values used to indicate security control metadata. V:SecurityControl is the union of V:SecurityPolicy,V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, purpose of use, dissemination controls and other refrain policies, and obligations to which a custodian or receiver is required to comply.
\nThis value set includes codes from the following code systems:
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nA clinical document is a documentation of clinical observations and services, with the following characteristics: (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care; (3) Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; (5) Human readability - A clinical document is human readable."
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a DOCCLINRegions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a _ActClassROIhttp://terminology.hl7.org/CodeSystem/v3-ActClass| Code | Display | |
| _ActClassROI | ActClassROI | Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present. |
Supports communication of purpose of use at a general level.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActReason| Code | Display | |
| COVERAGE | coverage under policy or program | To perform one or more operations on information for conducting activities related to coverage under a program or policy. |
| ETREAT | Emergency Treatment | To perform one or more operations on information for provision of immediately needed health care for an emergent condition. |
| HMARKT | healthcare marketing | To perform one or more operations on information for marketing services and products related to health care. |
| HOPERAT | healthcare operations | To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care. |
| HPAYMT | healthcare payment | To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care. |
| HRESCH | healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data iincludes basic and applied research such as biomedical, population origin or ancestry, translational research, and disease, discipline, specialty specific healthcare research and clinical trial research. |
| PATRQT | patient requested | To perform one or more operations on information in response to a patient's request. |
| PUBHLTH | public health | To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions. |
| TREAT | treatment | To perform one or more operations on information for provision of health care. |
A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a COMPRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_GeneticObservationInterpretation) Abstract | \n Codes that specify interpretation of genetic analysis, such as "positive", "negative", "carrier", "responsive", etc. \r\n\n | |
| 2 | CAR | Carrier | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n |
| 2 | Carrier Deprecated | Carrier | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n \n \n Deprecation Comment: \n This code is currently the same string as the print name for this concept and is inconsistent with the conventions being used for the other codes in the coding system, as it is a full word with initial capitalization, rather than an all upper case mnemonic. The recommendation from OO is to deprecate the code "Carrier" and to add "CAR" as the new active code representation for this concept. \r\n\n |
| 1 | (_ObservationInterpretationChange) Abstract | \n Interpretations of change of quantity and/or severity. At most one of B or W and one of U or D allowed. \r\n\n | |
| 2 | B | Better | \n The current result or observation value has improved compared to the previous result or observation value (the change is significant as defined in the respective test procedure). \r\n\n [Note: This can be applied to quantitative or qualitative observations.] \r\n\n |
| 2 | D | Significant change down | \n The current result has decreased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure). \r\n\n |
| 2 | U | Significant change up | \n The current result has increased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure). \r\n\n |
| 2 | W | Worse | \n The current result or observation value has degraded compared to the previous result or observation value (the change is significant as defined in the respective test procedure). \r\n\n [Note: This can be applied to quantitative or qualitative observations.] \r\n\n |
| 1 | (_ObservationInterpretationExceptions) Abstract | \n Technical exceptions resulting in the inability to provide an interpretation. At most one allowed. Does not imply normality or severity. \r\n\n | |
| 2 | < | Off scale low | \n The result is below the minimum detection limit (the test procedure or equipment is the limiting factor). \r\n\n Synonyms: Below analytical limit, low off scale. \r\n\n |
| 2 | > | Off scale high | \n The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor). \r\n\n Synonyms: Above analytical limit, high off scale. \r\n\n |
| 2 | AC Deprecated | Anti-complementary substances present | \n A valid result cannot be obtained for the specified component / analyte due to the presence of anti-complementary substances in the sample. \r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. \r\n\n |
| 2 | IE | Insufficient evidence | \n There is insufficient evidence that the species in question is a good target for therapy with the drug. A categorical interpretation is not possible. \r\n\n [Note: A MIC with "IE" and/or a comment may be reported (without an accompanying S, I or R-categorization).] \r\n\n |
| 2 | QCF Deprecated | Quality control failure | \n A result cannot be considered valid for the specified component / analyte or organism due to failure in the quality control testing component. \r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. \r\n\n |
| 2 | TOX Deprecated | Cytotoxic substance present | \n A valid result cannot be obtained for the specified organism or cell line due to the presence of cytotoxic substances in the sample or culture. \r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. \r\n\n |
| 1 | (_ObservationInterpretationNormality) Abstract | \n Interpretation of normality or degree of abnormality (including critical or "alert" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed. \r\n\n | |
| 2 | A | Abnormal | \n The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure). \r\n\n [Note: Typically applies to non-numeric results.] \r\n\n |
| 3 | AA | Critical abnormal | \n The result or observation value is outside a reference range or expected norm at a level at which immediate action should be considered for patient safety (as defined for the respective test procedure). \r\n\n [Note: Typically applies to non-numeric results. Analogous to critical/panic limits for numeric results.] \r\n\n |
| 4 | HH | Critical high | \n The result for a quantitative observation is above a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure). \r\n\n Synonym: Above upper panic limits. \r\n\n |
| 4 | LL | Critical low | \n The result for a quantitative observation is below a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure). \r\n\n Synonym: Below lower panic limits. \r\n\n |
| 3 | H | High | \n The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure). \r\n\n Synonym: Above high normal \r\n\n |
| 4 | H> Deprecated | Significantly high | A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'H' and 'HH'.] \r\n\n \n Deprecation Comment: The code 'H>' is being deprecated in order to align with the use of the code 'HU' for "Very high" in V2 Table 0078 "Interpretation Codes". \r\n\n [Note: The use of code 'H>' is non-preferred, as this code is deprecated and on track to be retired; use code 'HU' instead. \r\n\n |
| 5 | HH | ||
| 4 | HU | Significantly high | \n A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician. \r\n\n |
| 5 | HH | ||
| 3 | L | Low | \n The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure). \r\n\n Synonym: Below low normal \r\n\n |
| 4 | L< Deprecated | Significantly low | A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'L' and 'LL'.] \r\n\n \n Deprecation Comment: The code 'L<' is being deprecated in order to align with the use of the code 'LU' for "Very low" in V2 Table 0078 "Interpretation Codes". \r\n\n [Note: The use of code 'L<' is non-preferred, as this code is deprecated and on track to be retired; use code 'LU' instead. \r\n\n |
| 5 | LL | ||
| 4 | LU | Significantly low | \n A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician. \r\n\n |
| 5 | LL | ||
| 2 | N | Normal | \n The result or observation value is within the reference range or expected norm (as defined for the respective test procedure). \r\n\n [Note: Applies to numeric or non-numeric results.] \r\n\n |
| 1 | (_ObservationInterpretationSusceptibility) Abstract | \n Interpretations of anti-microbial susceptibility testing results (microbiology). At most one allowed. \r\n\n | |
| 2 | IE | ||
| 2 | I | Intermediate | \n Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with uncertain therapeutic effect. Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)\nProjects: ISO 20776-1, ISO 20776-2 \r\n\n [Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.] \r\n\n [Note 2: This class of susceptibility implies that an infection due to the isolate can be appropriately treated in body sites where the drugs are physiologically concentrated or when a high dosage of drug can be used.] \r\n\n [Note 3: This class also indicates a "buffer zone," to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.] \r\n\n [Note 4: These breakpoints can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).] \r\n\n |
| 2 | MS Deprecated | moderately susceptible | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n \n \n Deprecation Comment: \n This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012). \r\n\n |
| 2 | NCL | No CLSI defined breakpoint | \n Use when not enough clinical trial data published by the Clinical and Laboratory Standards Institutes (CLSI) is available to establish the breakpoints for susceptible / intermediate and resistant. \r\n\n |
| 2 | NS | Non-susceptible | \n A category used for isolates for which only a susceptible interpretive criterion has been designated because of the absence or rare occurrence of resistant strains. Isolates that have MICs above or zone diameters below the value indicated for the susceptible breakpoint should be reported as non-susceptible. \r\n\n NOTE 1: An isolate that is interpreted as non-susceptible does not necessarily mean that the isolate has a resistance mechanism. It is possible that isolates with MICs above the susceptible breakpoint that lack resistance mechanisms may be encountered within the wild-type distribution subsequent to the time the susceptible-only breakpoint is set. \r\n\n NOTE 2: For strains yielding results in the "nonsusceptible" category, organism identification and antimicrobial susceptibility test results should be confirmed. \r\n\n Synonym: decreased susceptibility. \r\n\n |
| 2 | R | Resistant | \n Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic failure.\nReference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) \nProjects: ISO 20776-1, ISO 20776-2 \r\n\n [Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.] \r\n\n [Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).] \r\n\n |
| 3 | SYN-R | Synergy - resistant | \n A category for isolates where the bacteria (e.g. enterococci) are not susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent). This is predictive that this combination therapy will not be effective. \r\n\n \n Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside. \r\n\n \n Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found. \r\n\n |
| 2 | S | Susceptible | \n Bacterial strain inhibited by in vitro concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic success.\nReference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)\nSynonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2 \r\n\n [Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.] \r\n\n [Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).] \r\n\n |
| 3 | SDD | Susceptible-dose dependent | \n A category that includes isolates with antimicrobial agent minimum inhibitory concentrations (MICs) that approach usually attainable blood and tissue levels and for which response rates may be lower than for susceptible isolates. \r\n\n Reference: CLSI document M44-A2 2009 "Method for antifungal disk diffusion susceptibility testing of yeasts; approved guideline - second edition" - page 2. \r\n\n |
| 3 | SYN-S | Synergy - susceptible | \n A category for isolates where the bacteria (e.g. enterococci) are susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent). This is predictive that this combination therapy will be effective. \r\n\n \n Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside. \r\n\n \n Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found. \r\n\n |
| 2 | VS Deprecated | very susceptible | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n \n \n Deprecation Comment: \n This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012). \r\n\n |
| 1 | EX | outside threshold | \n The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.\n \r\n\n Example: A positive result on a Hepatitis screening test.\n Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects.\nThese concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes.\nMembers of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held. \r\n\n |
| 2 | HX | above high threshold | \n The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.\n \r\n\n Example: A positive result on a Hepatitis screening test.\n Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held. \r\n\n |
| 2 | LX | below low threshold | \n The numeric observation/test result is interpreted as being below the low threshold value for a particular protocol within which the result is being reported. \r\n\n Example: A Total White Blood Cell Count falling below a protocol-defined threshold value of 3000/mm^3\n Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held. \r\n\n |
| 1 | HM Deprecated | Hold for Medical Review | \n Hold for Medical Review \r\n\n \n Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 "Interpretation Codes." \r\n\n |
| 1 | (ObservationInterpretationDetection) Abstract | \n Interpretations of the presence or absence of a component / analyte or organism in a test or of a sign in a clinical observation. In keeping with laboratory data processing practice, these concepts provide a categorical interpretation of the "meaning" of the quantitative value for the same observation. \r\n\n | |
| 2 | IND | Indeterminate | \n The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure. \r\n\n \n Usage Note: For example, if the specimen was degraded, poorly processed, or was missing the required anatomic structures, then "indeterminate" (i.e. "cannot be determined") is the appropriate response, not "equivocal". \r\n\n |
| 3 | E | Equivocal | \n The test or procedure was successfully performed, but the results are borderline and can neither be declared positive / negative nor detected / not detected according to the current established criteria. \r\n\n |
| 2 | NEG | Negative | \n An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure. \r\n\n [Note: Negative does not necessarily imply the complete absence of the specified item.] \r\n\n |
| 3 | ND | Not detected | \n The presence of the specified component / analyte, organism or clinical sign could not be determined within the limit of detection of the performed test or procedure. \r\n\n |
| 2 | POS | Positive | \n A presence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure. \r\n\n |
| 3 | DET | Detected | \n The measurement of the specified component / analyte, organism or clinical sign above the limit of detection of the performed test or procedure. \r\n\n |
| 1 | (ObservationInterpretationExpectation) Abstract | \n Interpretation of the observed result taking into account additional information (contraindicators) about the patient's situation. Concepts in this category are mutually exclusive, i.e., at most one is allowed. \r\n\n | |
| 2 | EXP | Expected | \n This result has been evaluated in light of known contraindicators. Once those contraindicators have been taken into account the result is determined to be "Expected" (e.g., presence of drugs in a patient that is taking prescription medication for pain management). \r\n\n |
| 2 | UNE | Unexpected | \n This result has been evaluated in light of known contraindicators. Once those contraindicators have been taken into account the result is determined to be "Unexpected" (e.g., presence of non-prescribed drugs in a patient that is taking prescription medication for pain management). \r\n\n |
| 1 | OBX Deprecated | Interpretation qualifiers in separate OBX segments | \n Interpretation qualifiers in separate OBX segments \r\n\n \n Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 "Interpretation Codes." \r\n\n |
| 1 | (ReactivityObservationInterpretation) Abstract | \n Interpretations of the presence and level of reactivity of the specified component / analyte with the reagent in the performed laboratory test. \r\n\n | |
| 2 | NR | Non-reactive | \n An absence finding used to indicate that the specified component / analyte did not react measurably with the reagent. \r\n\n |
| 2 | RR | Reactive | \n A presence finding used to indicate that the specified component / analyte reacted with the reagent above the reliably measurable limit of the performed test. \r\n\n |
| 3 | WR | Weakly reactive | \n A weighted presence finding used to indicate that the specified component / analyte reacted with the reagent, but below the reliably measurable limit of the performed test. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | col | col | |
| 1 | colgroup | colgroup | |
| 1 | row | row | |
| 1 | rowgroup | rowgroup |
The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.)
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a LOCRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nSpecifies under what circumstances (target Act) the source-Act may, must, must not or has occurred
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a _ActRelationshipConditionalhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipType| Code | Display | |
| _ActRelationshipConditional | ActRelationshipConditional | Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred |
Description:\nUsed to enumerate the typical confidentiality constraints placed upon a clinical document. Usage Note:\nx_BasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject; or that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-Confidentiality| Code | Display | |
| N | normal | Definition: Privacy metadata indicating that the information is typical, non-stigmatizing health information, which presents typical risk of harm if disclosed without authorization. \n \n Examples: In the US, this includes what HIPAA identifies as the minimum necessary protected health information (PHI) given a covered purpose of use (treatment, payment, or operations). Includes typical, non-stigmatizing health information disclosed in an application for health, workers compensation, disability, or life insurance. \n \n Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations. \n \n Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable jurisdictional privacy law or disclosure authorization. |
| R | restricted | Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a high risk to the information subject if disclosed without authorization. May be pre-empted by jurisdictional law, e.g., for public health reporting or emergency treatment. \n \n Examples: Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual, e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer. \n \n Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations.. \n \n Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable, prevailing (default) jurisdictional privacy law or disclosure authorization.. |
| V | very restricted | . Privacy metadata indicating that the information is extremely sensitive and likely stigmatizing health information that presents a very high risk if disclosed without authorization. This information must be kept in the highest confidence. \n \n Examples: Includes information about a victim of abuse, patient requested information sensitivity, and taboo subjects relating to health status that must be discussed with the patient by an attending provider before sharing with the patient. May also include information held under legal lock ? or attorney-client privilege \n \n Map: This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject. \n \n Usage Note: This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject. |
Release Date: 2018-08-12
\r\nScoped by the manufacturer
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a MANURelease Date: 2018-08-12
\r\nA person who actually and principally carries out the action. Need not be the principal responsible actor, e.g. a surgery resident operating under supervision of attending surgeon, and may be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a PRFRelease Date: 2018-08-12
\r\nParties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness).
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a _ParticipationInformationGeneratorhttp://terminology.hl7.org/CodeSystem/v3-ParticipationType| Code | Display | |
| _ParticipationInformationGenerator | ParticipationInformationGenerator | Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness). |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | above | above | |
| 1 | below | below | |
| 1 | border | border | |
| 1 | box | box | |
| 1 | hsides | hsides | |
| 1 | lhs | lhs | |
| 1 | rhs | rhs | |
| 1 | void | void | |
| 1 | vsides | vsides |
Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject.)
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityClass where concept is-a LIVRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nTarget that is not substantially present in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the act.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a INDA role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleCode where concept is-a _ServiceDeliveryLocationRoleTypehttp://terminology.hl7.org/CodeSystem/v3-RoleCode| Code | Display | |
| _ServiceDeliveryLocationRoleType | ServiceDeliveryLocationRoleType | A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_MaterialEntityClassType) Abstract | \n Types of Material for EntityClass "MAT" \r\n\n | |
| 2 | (_ContainerEntityType) Abstract | \n Material intended to hold another material for purpose of storage or transport. \r\n\n | |
| 3 | PKG | Package | \n A material intended to hold other materials for purposes of storage or transportation \r\n\n |
| 4 | (_NonRigidContainerEntityType) Abstract | \n A container having dimensions that adjust somewhat based on the amount and shape of the material placed within it. \r\n\n | |
| 5 | BAG | Bag | \n A pouched or pendulous container. \r\n\n |
| 5 | PACKT | Packet | \n A paper \r\n\n |
| 5 | PCH | Pouch | \n A small bag or container made of a soft material. \r\n\n |
| 5 | SACH | Sachet | \n A small bag or packet containing a small portion of a substance. \r\n\n |
| 4 | (_RigidContainerEntityType) Abstract | \n A container having a fixed and inflexible dimensions and volume \r\n\n | |
| 5 | (_IndividualPackageEntityType) Abstract | \n Container intended to contain sufficient material for only one use. \r\n\n | |
| 6 | AMP | Ampule | \n A small sealed glass container that holds a measured amount of a medicinal substance. \r\n\n |
| 6 | MINIM | Minim | \n Individually dosed ophthalmic solution. One time eye dropper dispenser. \r\n\n |
| 6 | NEBAMP | Nebuamp | \n Individually dosed inhalation solution. \r\n\n |
| 6 | OVUL | Ovule | \n A container either glass or plastic and a narrow neck, for storing liquid. \r\n\n |
| 5 | (_MultiUseContainerEntityType) Abstract | \n A container intended to contain sufficient material for more than one use. (I.e. Material is intended to be removed from the container at more than one discrete time period.) \r\n\n | |
| 6 | BOT | Bottle | \n A container, typically rounded, either glass or plastic with a narrow neck and capable of storing liquid. \r\n\n |
| 7 | BOTA | Amber Bottle | \n A bottle of yellow to brown color. Used to store light-sensitive materials \r\n\n |
| 7 | BOTD | Dropper Bottle | \n A bottle with a cap designed to release the contained liquid in droplets of a specific size. \r\n\n |
| 7 | BOTG | Glass Bottle | \n A bottle made of glass \r\n\n |
| 7 | BOTP | Plastic Bottle | \n A bottle made of plastic \r\n\n |
| 8 | BOTPLY | Polyethylene Bottle | \n A bottle made of polyethylene \r\n\n |
| 6 | BOX | Box | \n A 6-sided container commonly made from paper or cardboard used for solid forms. \r\n\n |
| 6 | CAN | Can | \n A metal container in which a material is hermetically sealed to enable storage over long periods. \r\n\n |
| 6 | CART | Cartridge | \n A sealed container of liquid or powder intended to be loaded into a device. \r\n\n |
| 6 | CNSTR | Canister | \n A pressurized metal container holding a substance released as a spray or aerosol. \r\n\n |
| 6 | JAR | Jar | \n A container of glass, earthenware, plastic, etc. Top of the container has a diameter of similar size to the diameter of the container as a whole \r\n\n |
| 6 | JUG | Jug | \n A deep vessel for holding liquids, with a handle and often with a spout or lip shape for pouring. \r\n\n |
| 6 | TIN | Tin | \n A lidded container made of thin sheet metal. \r\n\n |
| 6 | TUB | Tub | \n An open flat bottomed round container. \r\n\n |
| 6 | TUBE | Tube | \n A long hollow rigid or flexible cylinder. Material is extruded by squeezing the container. \r\n\n |
| 6 | VIAL | Vial | \n A small cylindrical glass for holding liquid medicines. \r\n\n |
| 5 | BLSTRPK | Blister Pack | \n A bubblepack. Medications sealed individually, separated into doses. \r\n\n |
| 6 | CARD | Card | \n A bubble pack card. Multiple individual/separated doses. \r\n\n |
| 4 | COMPPKG | Compliance Package | \n A container intended to contain sufficient material for more than one use, but grouped or organized to provide individual access to sufficient material for a single use. Often used to ensure that the proper type and amount of material is consumed/expended for each use. \r\n\n |
| 5 | BLSTRPK | ||
| 5 | DIALPK | Dial Pack | \n Rotatable dispenser. Eg. Birth control package. \r\n\n |
| 5 | DISK | Disk | \n Object that is thin, flat, and circular. Doses of medication often contained in bubbles on the disk. \r\n\n |
| 5 | DOSET | Dosette | \n Special packaging that will help patients take their medications on a regular basis. \r\n\n |
| 5 | STRIP | Strip | \n A continuous strip of plastic sectioned into individual pouches, each one containing the quantity of 1 or more medications intended to be administered at a specific time \r\n\n |
| 4 | KIT | Kit | \n A container for a diverse collection of products intended to be used together for some purpose (e.g. Medicinal kits often contain a syringe, a needle and the injectable medication). \r\n\n |
| 5 | SYSTM | System | \n A kit in which the components are interconnected. \r\n\n |
| 2 | (_MedicalDevice) Abstract | \n A device with direct or indirect therapeutic purpose. Values for EntityCode when EntityClass = "DEV" \r\n\n | |
| 3 | (_AccessMedicalDevice) Abstract | \n A device used to allow access to a part of a body \r\n\n | |
| 4 | LINE | Line | \n A hollow tube used to administer a substance into a vein, artery or body cavity \r\n\n |
| 5 | IALINE | Intra-arterial Line | \n A line used to administer a substance into an artery \r\n\n |
| 5 | IVLINE | Intraveneous Line | \n A line used to administer a substance into a vein \r\n\n |
| 3 | (_AdministrationMedicalDevice) Abstract | \n A device intended to administer a substance to a subject \r\n\n | |
| 4 | (_InjectionMedicalDevice) Abstract | \n A device intended to administer liquid into a subject via a \r\n\n | |
| 5 | AINJ | AutoInjector | \n Automatically injects medication. \r\n\n |
| 5 | PEN | Pen | \n A device which can contain a cartridge for injection purposes. Eg. Insulin pen. \r\n\n |
| 5 | SYR | Syringe | \n A barrel with a plunger. \r\n\n |
| 4 | APLCTR | Applicator | \n A device used to apply a liquid or powder to a surface. \r\n\n |
| 4 | INH | Inhaler | \n A small device used for inhaling medicine in the form of a vapour or gas in order to ease a respiratory condition such as asthma or to relieve nasal congestion. \r\n\n |
| 5 | DSKS | Diskus | \n The device used to inhale the doses of medication contained in the disk form. \r\n\n |
| 5 | DSKUNH | Diskhaler | \n The device used to inhale the doses of medication contained in the disk form. \r\n\n |
| 5 | TRBINH | Turbuhaler | \n Asthma medication delivery device. \r\n\n |
| 4 | PMP | Pump | \n A device that is used to raise, compress, or transfer liquids or gases and is operated by a piston or similar mechanism. \r\n\n |
| 2 | (_SpecimenAdditiveEntity) Abstract | \n Set of codes related to specimen additives \r\n\n | |
| 3 | ACDA | ACD Solution A | \n ACD Solution A of trisodium citrate, 22.0g/L; citric acid, 8.0 g/L; and dextrose 24.5 g/L. Used in Blood banking and histocompatibilty testing \r\n\n |
| 3 | ACDB | ACD Solution B | \n ACD Solution B of trisodium citrate, 13.2g/L; citric acid, 4.8 g/L; and dextrose 14.7 g/L. Used in Blood banking and histocompatibilty testing. \r\n\n |
| 3 | ACET | Acetic Acid | \n 50% V/V acetic acid in water. Used as a urine preservative \r\n\n |
| 3 | AMIES | Amies transport medium | \n Sodium Chloride 3.0g, Potassium Chloride 0.2g, Calcium Chloride 0.1g, Magnesium Chloride 0.1g, Monopotassium Phosphate 0.2g, Disodium Phosphate 1.15g, Sodium Thiogly collate 1.0g, Distilled Water 1 liter \r\n\n |
| 3 | BACTM | Bacterial Transport medium | \n Any medium used to maintain bacterial viability (e.g. Stuart's, Cary-Blair, Amies) \r\n\n |
| 3 | BF10 | Buffered 10% formalin | \n Formaldehyde 4% w/v; methyl alcohol 1% w/v; phosphate buffering salts. Tissue preservative \r\n\n |
| 3 | BOR | Boric Acid | \n Powdered boric acid (usually 10 g) added to 24-hour urine collections as a preservative. \r\n\n |
| 3 | BOUIN | Bouin's solution | \n Picric acid, saturated aqueous solution (750.0 ml), 37-40% formalin (250.0 ml), glacial acetic acid (50.0 ml). Tissue preservative. \r\n\n |
| 3 | BSKM | Buffered skim milk | \n 50% skim milk in 0.01 M phosphate-buffered saline. Maintain virus viability \r\n\n |
| 3 | C32 | 3.2% Citrate | \n A 3.2% solution of Sodium Citrate in water. Used as a blood preservative \r\n\n |
| 3 | C38 | 3.8% Citrate | \n A 3.8% solution of Sodium Citrate in water. Used as a blood preservative \r\n\n |
| 3 | CARS | Carson's Modified 10% formalin | \n A modification of buffered 10% formalin used as a general tissue preservative. \r\n\n |
| 3 | CARY | Cary Blair Medium | \n Sodium Thioglycollate 1.5 g, Disodium Hydrogen Phosphate 1.1 g, Sodium Chloride 5.0 g, Calcium Chloride 0.09 g, Agar 5.0 g, per Liter of Water \r\n\n |
| 3 | CHLTM | Chlamydia transport medium | \n Any of a number of non-nutritive buffered media used to maintain Chlamydia viability during transportation to the laboratory \r\n\n |
| 3 | CTAD | CTAD | \n Buffered tri-sodium citrate solution with theophylline, adenosine and dipyridamole \r\n\n |
| 3 | EDTK15 | Potassium/K EDTA 15% | \n Potassium EDTA 15% solution in water \r\n\n |
| 3 | EDTK75 | Potassium/K EDTA 7.5% | \n Potassium EDTA 7.5% solution in water \r\n\n |
| 3 | EDTN | Sodium/Na EDTA | \n Sodium fluoride and Disodium EDTA \r\n\n |
| 3 | ENT | Enteric bacteria transport medium | \n Any of a number of non-nutritive buffered media used to maintain enteric bacterial viability during transportation to the laboratory \r\n\n |
| 3 | F10 | 10% Formalin | \n A 10% v/v solution in water of formalin( a 37% solution of formaldehyde and water). Used for tissue preservation. \r\n\n |
| 3 | FDP | Thrombin NIH; soybean trypsin inhibitor | \n Thrombin plus soybean trypsin inhibitor. For use in identifying fibrn degredation products. \r\n\n |
| 3 | FL10 | Sodium Fluoride, 10mg | \n Sodium fluoride, 10mg added as a urine preservative. \r\n\n |
| 3 | FL100 | Sodium Fluoride, 100mg | \n Sodium fluoride, 100mg added as a urine preservative. \r\n\n |
| 3 | HCL6 | 6N HCL | \n A solution of HCl containing 6moles of hydrogen ion/L. Used as a Urine Preservative. \r\n\n |
| 3 | HEPA | Ammonium heparin | \n Ammonium heparin \r\n\n |
| 3 | HEPL | Lithium/Li Heparin | \n Lithium heparin salt \r\n\n |
| 3 | HEPN | Sodium/Na Heparin | \n Sodium heparin salt \r\n\n |
| 3 | HNO3 | Nitric Acid | \n 6N Nitric acid used to preserve urine for heavy metal analysis. \r\n\n |
| 3 | JKM | Jones Kendrick Medium | \n A transport medium formulated to maintain Bordetella pertussis viability. \r\n\n |
| 3 | KARN | Karnovsky's fixative | \n 5% Glutaraldehyde, 4% Formaldehyde in 0.08M buffer. Tissue preservation \r\n\n |
| 3 | KOX | Potassium Oxalate | \n Potassium oxalate and sodium fluoride in a 1.25:1 ratio \r\n\n |
| 3 | LIA | Lithium iodoacetate | \n Iodoacetate lithium salt \r\n\n |
| 3 | M4 | M4 | \n Modified Hank's balanced salt solution supplemented with bovine serum albumin, gelatin, sucrose and glutamic acid. It is buffered to pH 7.3+ or - 0.2 with HEPES buffer. Phenol red is used to indicate pH. Vancomycin, Amphotericin B and Colistin are used to \r\n\n |
| 3 | M4RT | M4-RT | \n Modified Hank's balanced salt solution supplemented with bovine serum albumin, gelatin, sucrose and glutamic acid. It is buffered to pH 7.3+ or - 0.2 with Hepes buffer. Phenol red is used to indicate pH. Gentamicin and amphotericin B are used to inhibit c \r\n\n |
| 3 | M5 | M5 | \n Modified Hank's balanced salt solution supplemented with protein stabilizers, sucrose and glutamic acid. It is buffered to pH 7.3+ or - 0.2 with Hepes buffer. Phenol red is used to indicate pH. Vancomycin, Amphotericin B and Colistin are used to inhibit c \r\n\n |
| 3 | MICHTM | Michel's transport medium | \n 1M potassium citrate, pH 7.0 2.5 ml, 0.1M magnesium sulfate 5.0 ml, 0.1M N-ethyl malemide 5.0 ml, dH2O 87.5 ml, ammonium sulfate 55gm. Preserve antigens for Immunofluorescence procedures \r\n\n |
| 3 | MMDTM | MMD transport medium | \n A buffered medium with ammonium sulfate added to preserve antigens for Immunofluorescence procedures \r\n\n |
| 3 | NAF | Sodium Fluoride | \n Sodium fluoride \r\n\n |
| 3 | NONE | None | \n No additive. Specifically identifes the specimen as having no additives. \r\n\n |
| 3 | PAGE | Page's Saline | \n 0.12 g NaCl, 0.004 g MgSO, 0.004 g, CaCl, 0.142 g Na2HPO4 and 0.136 g KH2PO4 per liter of distilled water. Maintain Acanthaoemba viability. \r\n\n |
| 3 | PHENOL | Phenol | \n Phenol. Urine preservative \r\n\n |
| 3 | PVA | Polyvinylalcohol | \n Polyvinyl alcohol \r\n\n |
| 3 | RLM | Reagan Lowe Medium | \n A transport medium formulated to maintain Bordetella pertussis viability. \r\n\n |
| 3 | SILICA | Siliceous earth | \n Diatomaceous earth. For glucose determination blood samples \r\n\n |
| 3 | SPS | Sodium polyanethol sulfonate 0.35% in 0.85% sodium chloride | \n Sodium polyanethol sulfonate in saline. Anticomplementary and antiphagocytic properties. Used in blood culture collection. \r\n\n |
| 3 | SST | Serum Separator Tube | \n Polymer separator gel with clot activator \r\n\n |
| 3 | STUTM | Stuart transport medium | \n Sodium Glycerophosphate 10.0g, Calcium Chloride 0.1g, Mercaptoacetic Acid 1.0ml, Distilled Water 1 liter \r\n\n |
| 3 | THROM | Thrombin | \n Thrombin. Accelerates clotting. \r\n\n |
| 3 | THYMOL | Thymol | \n 2-Isopropyl-5-methyl phenol. A preservative for 24 Hr Urine samples \r\n\n |
| 3 | THYO | Thyoglycolate broth | \n A nutritive medium with a reducing agent (sodium thioglycolate) which, due to a chemical reaction, removes oxygen from the broth. \r\n\n |
| 3 | TOLU | Toluene | \n Also known as Methylbenzene; Toluol; Phenylmethane. A preservative for 24 Hr Urine samples \r\n\n |
| 3 | URETM | Ureaplasma transport medium | \n A buffered salt solution with antifungal agents added for the collection and transport of Ureaplasma specimens. \r\n\n |
| 3 | VIRTM | Viral Transport medium | \n Sucrose 74.6g, Potassium hydrogenphosphate 0.52g, L-glutamic acid 0.72g, Bovine serum albumin 5.0g, Gentamicin 50mg, Potassium dihydrogenphosphate 1.25g, L-15 medium 9.9L, Water to 10L. Maintain Virus viability. \r\n\n |
| 3 | WEST | Buffered Citrate | \n 3.8% Citrate buffered to a pH of 5.5 for Westergren Sedimentation Rate \r\n\n |
| 2 | BLDPRD | Blood Product | \n A manufactured product that is produced from the raw blood oi a donor with the intention of using it in a recipient transfusion. \r\n\n |
| 2 | VCCNE | Vaccine | \n A Type of medicine that creates an immune protection without the recipient experiencing the disease. \r\n\n |
| 2 | (_DrugEntity) Abstract | \n A substance whose therapeutic effect is produced by chemical action within the body. \r\n\n | |
| 3 | (_ClinicalDrug) Abstract | \n Any substance or mixture of substances manufactured, sold or represented for use in: (a) the diagnosis, treatment, mitigation or prevention of a disease, disorder, abnormal physical state, or its symptoms, in human beings or animals; (b) restoring, correcting or modifying organic functions in human beings or animals. \r\n\n | |
| 1 | (_NonDrugAgentEntity) Abstract | \n Indicates types of allergy and intolerance agents which are non-drugs. (E.g. foods, latex, etc.) \r\n\n | |
| 2 | NDA01 | egg | |
| 2 | NDA02 | fish | |
| 2 | NDA03 | lactose | |
| 2 | NDA04 | peanut | |
| 2 | NDA05 | soy | |
| 2 | NDA06 | sulfites | |
| 2 | NDA07 | wheat or gluten | |
| 2 | NDA08 | isocyanates | |
| 2 | NDA09 | solvents | |
| 2 | NDA10 | oils | |
| 2 | NDA11 | venoms | |
| 2 | NDA12 | latex | |
| 2 | NDA13 | shellfish | |
| 2 | NDA14 | strawberries | |
| 2 | NDA15 | tomatoes | |
| 2 | NDA16 | dust | |
| 2 | NDA17 | dust mites | |
| 1 | (_OrganizationEntityType) Abstract | \n Further classifies entities of classCode ORG. \r\n\n | |
| 2 | HHOLD | household | \n The group of persons who occupy a single housing unit. \r\n\n |
| 2 | NAT | NationEntityType | \n Codes identifying nation states. Allows for finer grained specification of Entity with classcode <= NAT \r\n\n \n Example:ISO3166 country codes. \r\n\n |
| 2 | RELIG | religious institution | \n An organization that provides religious rites of worship. \r\n\n |
| 1 | (_PlaceEntityType) Abstract | \n Types of places for EntityClass "PLC" \r\n\n | |
| 2 | BED | Bed Location | \n The location of a bed \r\n\n |
| 2 | BLDG | Building Location | \n The location of a building \r\n\n |
| 2 | FLOOR | Floor Location | \n The location of a floor of a building \r\n\n |
| 2 | ROOM | Room Location | \n The location of a room \r\n\n |
| 2 | WING | Wing Location | \n The location of a wing of a building (e.g. East Wing). The same room number for the same floor number can be distinguished by wing number in some situations \r\n\n |
| 1 | (_ResourceGroupEntityType) Abstract | \n Codes to characterize a Resource Group using categories that typify its membership and/or function \r\n\n . \r\n\n \n Example: PractitionerGroup \r\n\n | |
| 2 | PRAC | PractitionerGroup |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nConcepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ObservationValue where concept is-a _EmploymentStatushttp://terminology.hl7.org/CodeSystem/v3-ObservationValue| Code | Display | |
| _EmploymentStatus | _EmploymentStatus | Concepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment. |
Release Date: 2018-08-12
\r\nThe type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc.
\nThis value set includes codes from the following code systems:
http://loinc.orgRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | D | Deferred | \n Query response is deferred. \r\n\n |
| 1 | I | Immediate | \n Query response is immediate. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nA role played by a place at which services may be provided.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a SDLOCRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | E | emergency | |
| 1 | LD | labor and delivery | |
| 1 | NB | newborn |
No Description Provided
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ObservationValue where concept is-a _SECINTOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValue| Code | Display | |
| _SECINTOBV | security integrity | Abstract security observation values used to indicate security integrity metadata. \n \n Examples: Codes conveying integrity status, integrity confidence, and provenance. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | SEQL | sequence | \n \n Description:A transmission relationship indicating that the source transmission follows the target transmission. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nCodes for the representation of the names of human languages.
\nThis value set includes codes from the following code systems:
urn:iso:std:iso:3166Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nSensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an "employee" sensitivity code would make little sense for use outside of a policy domain. "Taboo" would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.title.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _InformationSensitivityPolicyRelease Date: 2018-08-12
\r\nNo Description Provided
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-substanceAdminSubstitution where concept is-a _ActSubstanceAdminSubstitutionCodehttp://terminology.hl7.org/CodeSystem/v3-substanceAdminSubstitution| Code | Display | |
| _ActSubstanceAdminSubstitutionCode | ActSubstanceAdminSubstitutionCode | Description: Substitution occurred or is permitted with another product that may potentially have different ingredients, but having the same biological and therapeutic effects. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | center | center | |
| 1 | char | char | |
| 1 | justify | justify | |
| 1 | left | left | |
| 1 | right | right |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | all | all | |
| 1 | cols | cols | |
| 1 | groups | groups | |
| 1 | none | none | |
| 1 | rows | rows |
Release Date: 2018-08-12
\r\nAn Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Examples:\n: Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a PROCRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nA social or legal structure formed by human beings.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityClass where concept is-a ORGRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (BindingRealms) Abstract | \n \n Description: Concepts that can be used as Binding Realms when creating Binding Statements. These codes are permitted to appear in the InfrastructureRoot.realmCode attribute. \r\n\n | |
| 2 | (AffiliateRealms) Abstract | \n \n Description: Realm codes for official HL7 organizational bodies. This includes both the HL7 International organization as well as all recognized international affiliates (past and present). These groups have the ability to bind vocabulary and develop artifacts. As well, they have the ability to have "ownership" over other binding realms and namespace realms via the owningAffiliate property of those other realm codes. \r\n\n | |
| 3 | AR | Argentina | \n \n Description: Realm code for use of Argentina \r\n\n |
| 3 | AT | Austria | \n \n Description: Realm code for use of Austria \r\n\n |
| 3 | AU | Australia | \n \n Description: Realm code for use of Australia \r\n\n |
| 3 | BR | Brazil | \n \n Description: Realm code for use of Brazil \r\n\n |
| 3 | CA | Canada | \n \n Description: Realm code for use of Canada \r\n\n |
| 3 | CH | Switzerland | \n \n Description: Realm code for use of Switzerland \r\n\n |
| 3 | CL | Chile | \n \n Description: Realm code for use of Chile \r\n\n |
| 3 | CN | China | \n \n Description: Realm code for use of China \r\n\n |
| 3 | CO | Columbia | \n \n Description: Realm code for use of Localized Version \r\n\n |
| 3 | CZ | Czech Republic | \n \n Description: Realm code for use of Czech Republic \r\n\n |
| 3 | DE | Germany | \n \n Description: Realm code for use of Germany \r\n\n |
| 3 | DK | Denmark | \n \n Description: Realm code for use of Denmark \r\n\n |
| 3 | ES | Spain | \n \n Description: Realm code for use of Spain \r\n\n |
| 3 | FI | Finland | \n \n Description: Realm code for use of Finland \r\n\n |
| 3 | FR | France | \n \n Description: Realm code for use of France \r\n\n |
| 3 | GR | Greece | \n \n Description: Realm code for use of Greece \r\n\n |
| 3 | HR | Croatia | \n \n Description: Realm code for use of Croatia \r\n\n |
| 3 | IE | Ireland | \n \n Description: Realm code for use of Ireland \r\n\n |
| 3 | IN | India | \n \n Description: Realm code for use of India \r\n\n |
| 3 | IT | Italy | \n \n Description: Realm code for use of Italy \r\n\n |
| 3 | JP | Japan | \n \n Description: Realm code for use of Japan \r\n\n |
| 3 | KR | Korea | \n \n Description: Realm code for use of Korea \r\n\n |
| 3 | LT | Lithuania | \n \n Description: Realm code for use of Lithuania \r\n\n |
| 3 | MX | Mexico | \n \n Description: Realm code for use of Mexico \r\n\n |
| 3 | NL | The Netherlands | \n \n Description: Realm code for use of The Netherlands \r\n\n |
| 3 | NZ | New Zealand | \n \n Description: Realm code for use of New Zealand \r\n\n |
| 3 | RO | Romania | \n \n Description: Realm code for use of Romania \r\n\n |
| 3 | RU | Russian Federation | \n \n Description: Realm code for use of Russian Federation \r\n\n |
| 3 | SE | Sweden | \n \n Description: Realm code for use of Sweden \r\n\n |
| 3 | SG | Singapore | \n \n Description: Realm code for use of Localized Version \r\n\n |
| 3 | SOA | Southern Africa | \n \n Description: Realm code for use of Southern Africa \r\n\n |
| 3 | TR | Turkey | \n \n Description: Realm code for use of Turkey \r\n\n |
| 3 | TW | Taiwan | \n \n Description: Realm code for use of Taiwan \r\n\n |
| 3 | UK | United Kingdom | \n \n Description: Realm code for use of United Kingdom \r\n\n |
| 3 | US | United States of America | \n \n Description: Realm code for use of United States of America \r\n\n |
| 3 | UV | Universal | \n \n Description: Realm code for use of Universal realm or context, used in every instance \r\n\n |
| 3 | UY | Uruguay | \n \n Description: Realm code for use of Uruguay \r\n\n |
| 2 | C1 | Unclassified Realm | \n \n Description: Realm code for use of Unclassified Realm \r\n\n |
| 2 | GB | Great Britain | \n \n Description: Realm code for use of Great Britain \r\n\n |
| 2 | R1 | Representative Realm | \n \n Description: Realm code for use of Representative Realm \r\n\n |
| 2 | X1 | Example Realm | \n \n Description: Realm code for use of Example Realm \r\n\n |
| 1 | (NamespaceRealms) Abstract | \n \n Description: Codes that can be used in the "realm" portion of HL7 v3 artifact identifiers. \r\n\n | |
| 2 | AffiliateRealms | ||
| 2 | GB | ||
| 2 | ZZ | Localized Version | \n \n Description: An artifact created for local use only. This realm namespace has no owning affiliate. Its use is uncontrolled, i.e. anyone can create artifacts using this realm namespace. Because of this, there is a significant likelihood of artifact identifier collisions. Implementers are encouraged to register their artifacts under an affiliate owned and controlled namespace to avoid such collision problems where possible. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_AffiliationRoleType) Abstract | \n Concepts characterizing the type of association formed by player and scoper when there is a recognized Affiliate role by which the two parties are related. \r\n\n \n Examples: Business Partner, Business Associate, Colleague \r\n\n | |
| 2 | (_AgentRoleType) Abstract | \n Parties that may or should contribute or have contributed to an Act. \r\n\n | |
| 3 | AMENDER | amender | \n An entity which corrected, edited, or amended pre-existing information. \r\n\n |
| 3 | CLASSIFIER | classifier | \n An individual authorized to assign an original classification to information, including compilations of unclassified information, based on a determination that the information requires protection against unauthorized disclosure. The individual marks the information with immutable, computable, and human readable security labels in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded, downgraded, used in derivative classification, or declassified] in a manner that preserves the overridden original classification binding and provenance. \r\n\n |
| 3 | CONSENTER | consenter | \n An entity or an entity's delegatee who is the grantee in an agreement such as a consent for services, advanced directive, or a privacy consent directive in accordance with jurisdictional, organizational, or patient policy. \r\n\n |
| 3 | CONSWIT | consent witness | \n An entity which has witnessed and attests to observing another entity being counseled about an agreement such as a consent for services, advanced directive, or a privacy consent directive. \r\n\n |
| 3 | COPART | co-participant | \n An entity which participates in the generation of and attest to veracity of content, but is not an author or coauthor. For example a surgeon who is required by institutional, regulatory, or legal rules to sign an operative report, but who was not involved in the authorship of that report. \r\n\n |
| 3 | DECLASSIFIER | declassifier | \n An individual which is authorized to declassify information based on a determination that the information no longer requires protection against unauthorized disclosure. The individual marks the information being declassified using computable and human readable security labels indicating that this is copy of previously classified information is unclassified in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded or used in derivative classification] in a manner that preserves the overridden original classification binding and provenance. \r\n\n |
| 3 | DELEGATEE | delegatee | \n A party to whom some right or authority is granted by a delegator. \r\n\n |
| 3 | DELEGATOR | delegator | \n A party that grants all or some portion its right or authority to another party. \r\n\n |
| 3 | DOWNGRDER | downgrader | \n An individual authorized to lower the classification level of labeled content and provide rationale for doing so as directed by a classification guide. \r\n\n |
| 3 | DRIVCLASSIFIER | derivative classifier | \n An individual who is only authorized to classify reproduced, extracted, or summarized classified information, or compile classified and unclassified information by applying classification markings derived from source material or as directed by a classification guide. \r\n\n |
| 3 | GRANTEE | grantee | \n An entity which accepts certain rights or authority from a grantor. \r\n\n |
| 3 | GRANTOR | grantor | \n An entity which agrees to confer certain rights or authority to a grantee. \r\n\n |
| 3 | INTPRTER | interpreter | \n An entity which converts spoken or written language into the language of key participants in an event such as when a provider is obtaining a patient's consent to treatment or permission to disclose information. \r\n\n |
| 3 | REVIEWER | reviewer | \n An entity authorized to filter information according to approved criteria. \r\n\n |
| 3 | VALIDATOR | validator | \n An entity authorized to validate information for inclusion in a record. \r\n\n |
| 2 | (_CoverageSponsorRoleType) Abstract | \n \n Description:Codes that indicate a specific type of sponsor. Used when the sponsor's role is only either as a fully insured sponsor or only as a self-insured sponsor. NOTE: Where a sponsor may be either, use the SponsorParticipationFunction.code (fully insured or self insured) to indicate the type of responsibility. (CO6-0057) \r\n\n | |
| 3 | FULLINS | Fully insured coverage sponsor | \n \n Description:An employer or organization that contracts with an underwriter to assumes the financial risk and administrative responsibility for coverage of health services for covered parties. \r\n\n |
| 3 | SELFINS | Self insured coverage sponsor | \n \n Description:An employer or organization that assumes the financial risk and administrative responsibility for coverage of health services for covered parties. \r\n\n |
| 2 | (_PayorRoleType) Abstract | \n \n Description:PayorRoleType for a particular type of policy or program benefit package or plan where more detail about the coverage administration role of the Payor is required. The functions performed by a Payor qualified by a PayorRoleType may be specified by the PayorParticpationFunction value set. \r\n\n \n Examples:A Payor that is a TPA may administer a managed care plan without underwriting the risk. \r\n\n | |
| 3 | ENROLBKR | Enrollment Broker | \n \n Description:A payor that is responsible for functions related to the enrollment of covered parties. \r\n\n |
| 3 | TPA | Third party administrator | \n \n Description:Third party administrator (TPA) is a payor organization that processes health care claims without carrying insurance risk. Third party administrators are prominent players in the managed care industry and have the expertise and capability to administer all or a portion of the claims process. They are normally contracted by a health insurer or self-insuring companies to administer services, including claims administration, premium collection, enrollment and other administrative activities. \r\n\n Self-insured employers often contract with third party administrator to handle their insurance functions. Insurance companies oftentimes outsource the claims, utilization review or membership functions to a TPA. Sometimes TPAs only manage provider networks, only claims or only utilization review. \r\n\n While some third-party administrators may operate as units of insurance companies, they are often independent. However, hospitals or provider organizations desiring to set up their own health plans will often outsource certain responsibilities to TPAs. TPAs may perform one or several payor functions, specified by the PayorParticipationFunction value set, such as provider management, enrollment, utilization management, and fee for service claims adjudication management. \r\n\n |
| 3 | UMO | Utilization management organization | \n \n Description:A payor that is responsible for review and case management of health services covered under a policy or program. \r\n\n |
| 2 | RESPRSN | responsible party | \n The role played by a party who has legal responsibility for another party. \r\n\n |
| 3 | EXCEST | executor of estate | \n The role played by a person acting as the estate executor for a deceased subscriber or policyholder who was the responsible party \r\n\n |
| 3 | GUADLTM | guardian ad lidem | \n The role played by a person appointed by the court to look out for the best interests of a minor child during the course of legal proceedings. \r\n\n |
| 3 | GUARD | guardian | \n The role played by a person or institution legally empowered with responsibility for the care of a ward. \r\n\n |
| 3 | POWATT | power of attorney | \n A relationship between two people in which one person authorizes another to act for him in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts. \r\n\n |
| 4 | DPOWATT | durable power of attorney | \n A relationship between two people in which one person authorizes another, usually a family member or relative, to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned. Unlike ordinary powers of attorney, durable powers can survive for long periods of time, and again, unlike standard powers of attorney, durable powers can continue after incompetency. \r\n\n |
| 4 | HPOWATT | healthcare power of attorney | \n A relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that continues (by its terms) to be effective even though the grantor has become mentally incompetent after signing the document. \r\n\n |
| 4 | SPOWATT | special power of attorney | \n A relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned. \r\n\n |
| 1 | (_AssignedRoleType) Abstract | ||
| 2 | (_AssignedNonPersonLivingSubjectRoleType) Abstract | \n \n Description:A role type that is used to further qualify a non-person subject playing a role where the role class attribute is set to RoleClass AssignedEntity \r\n\n | |
| 3 | ASSIST | Assistive non-person living subject | \n \n Description:Dogs trained to assist the ill or physically challenged. \r\n\n |
| 3 | BIOTH | Biotherapeutic non-person living subject | \n \n Description:Animals, including fish and insects, and microorganisms which may participate as assigned entities in biotherapies. \r\n\n |
| 4 | ANTIBIOT | Antibiotic | \n \n Description:Non-person living subject used as antibiotic. \r\n\n \n Examples:Bacteriophage, is a virus that infects bacteria. \r\n\n |
| 4 | DEBR | Debridement | \n \n Description:Maggots raised for biodebridement. \r\n\n \n Discussion: Maggot Debridement Therapy is the medical use of live maggots for cleaning non-healing wounds. \r\n\n \n Examples:Removal of burnt skin. \r\n\n |
| 3 | CCO | Clinical Companion | \n \n Description:Companion animals, such as dogs, cats, and rabbits, which may be provided to patients to improve general mood, decrease depression and loneliness, and distract from stress-inducing concerns to improve quality of life. \r\n\n |
| 3 | SEE | Seeing | \n \n Description:Dogs trained to assist persons who are seeing impaired or blind. \r\n\n |
| 3 | SNIFF | Sniffing | \n \n Description:Dogs trained or having the ability to detect imminent seizures or cancers in humans, probably as a result of volatile chemical (odors) given off by the malignancy of the host. \r\n\n |
| 1 | (_CertifiedEntityType) Abstract | \n Defines types of certifications for all entities \r\n\n | |
| 1 | _CitizenRoleType | CitizenRoleType | \n A role type used to qualify a person's legal status within a country or nation. \r\n\n |
| 2 | CAS | asylum seeker | \n A person who has fled his or her home country to find a safe place elsewhere. \r\n\n |
| 3 | CASM | single minor asylum seeker | \n A person who is someone of below legal age who has fled his or her home country, without his or her parents, to find a safe place elsewhere at time of categorization. \r\n\n |
| 2 | CN | national | \n A person who is legally recognized as a member of a nation or country, with associated rights and obligations. \r\n\n |
| 2 | CNRP | non-country member without residence permit | \n A foreigner who is present in a country (which is foreign to him/her) unlawfully or without the country's authorization (may be called an illegal alien). \r\n\n |
| 3 | CNRPM | non-country member minor without residence permit | \n A person who is below legal age present in a country, without his or her parents, (which is foreign to him/her) unlawfully or without the country's authorization. \r\n\n |
| 2 | CPCA | permit card applicant | \n A non-country member admitted to the territory of a nation or country as a non-resident for an explicit purpose. \r\n\n |
| 2 | CRP | non-country member with residence permit | \n A foreigner who is a resident of the country but does not have citizenship. \r\n\n |
| 3 | CRPM | non-country member minor with residence permit | \n A person who is a resident below legal age of the country without his or her parents and does not have citizenship. \r\n\n |
| 1 | (_ContactRoleType) Abstract | \n Types of contact for Role code "CON" \r\n\n | |
| 2 | (_AdministrativeContactRoleType) Abstract | \n A contact role used for business and/or administrative purposes. \r\n\n | |
| 3 | BILL | Billing Contact | \n A contact role used to identify a person within a Provider organization that can be contacted for billing purposes (e.g. about the content of the Invoice). \r\n\n |
| 3 | ORG | organizational contact | \n A contact for an organization for administrative purposes. Contact role specifies a person acting as a liason for the organization. \r\n\n Example: HR Department representative. \r\n\n |
| 3 | PAYOR | Payor Contact | \n A contact role used to identify a person within a Payor organization to whom this communication is addressed. \r\n\n |
| 2 | ECON Deprecated | emergency contact | \n A contact designated for contact in emergent situations. \r\n\n |
| 2 | NOK Deprecated | next of kin | \n Played by an individual who is designated as the next of kin for another individual which scopes the role. \r\n\n |
| 1 | (_IdentifiedEntityType) Abstract | \n \n Definition: A code representing the type of identifier that has been assigned to the identified entity (IDENT). \r\n\n \n Examples: Example values include Social Insurance Number, Product Catalog ID, Product Model Number. \r\n\n | |
| 2 | (_LocationIdentifiedEntityRoleCode) Abstract | \n \n Description:Describes types of identifiers other than the primary location registry identifier for a service delivery location. Identifiers may be assigned by a local service delivery organization, a formal body capable of accrediting the location for the capability to provide specific services or the identifier may be assigned at a jurisdictional level. \r\n\n | |
| 3 | ACHFID | accreditation location identifier | \n \n Description:Identifier assigned to a location by the organization responsible for accrediting the location. \r\n\n |
| 3 | JURID | jurisdiction location identifier | \n \n Description:Identifier assigned to a location by a jurisdiction. \r\n\n |
| 3 | LOCHFID | local location identifier | \n \n Description:Identifier assigned to a location by a local party (which could be the facility itself or organization overseeing a group of facilities). \r\n\n |
| 1 | (_LivingSubjectProductionClass) Abstract | \n Code indicating the primary use for which a living subject is bred or grown \r\n\n | |
| 2 | BF | Beef | \n Cattle used for meat production \r\n\n |
| 2 | BL | Broiler | \n Chickens raised for meat \r\n\n |
| 2 | BR | Breeder | \n Breeding/genetic stock \r\n\n |
| 2 | CO | Companion | \n Companion animals \r\n\n |
| 2 | DA | Dairy | \n Milk production \r\n\n |
| 2 | DR | Draft | \n Draft animals \r\n\n |
| 2 | DU | Dual | \n Dual purpose. Defined purposes based on species and breed \r\n\n |
| 2 | FI | Fiber | \n Animals raised for their fur, hair or skins \r\n\n |
| 2 | LY | Layer | \n Chickens raised for egg production \r\n\n |
| 2 | MT | Meat | \n Animals raised for meat production \r\n\n |
| 2 | MU | Multiplier | \n Poultry flocks used for chick/poult production \r\n\n |
| 2 | PL | Pleasure | \n Animals rasied for recreation \r\n\n |
| 2 | RC | Racing | \n Animals raised for racing perfomance \r\n\n |
| 2 | SH | Show | \n Animals raised for shows \r\n\n |
| 2 | VL | Veal | \n Cattle raised for veal meat production. Implicit is the husbandry method. \r\n\n |
| 2 | WL | Wool | \n Sheep, goats and other mammals raised for their fiber \r\n\n |
| 2 | WO | Working | \n Animals used to perform work \r\n\n |
| 1 | (_MedicationGeneralizationRoleType) Abstract | \n Identifies the specific hierarchical relationship between the playing and scoping medications. \r\n\n \n Examples: Generic, Generic Formulation, Therapeutic Class, etc. \r\n\n | |
| 2 | DC | therapeutic class | \n \n Description:A categorization of medicinal products by their therapeutic properties and/or main therapeutic use. \r\n\n |
| 2 | GD | generic drug | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients independent of strength, and form. \r\n\n The scoping entity identifies a unique combination of medicine ingredients; sometimes referred to as "ingredient set". \r\n\n |
| 3 | GDF | generic drug form | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients and dose form, independent of strength of the ingredients. The scoping entity identifies a unique combination of medicine ingredients in a specific dose form. \r\n\n |
| 3 | GDS | generic drug strength | \n Relates a manufactured drug product to the non-proprietary (generic) representation of is ingredients with their strength. The scoping entity identifies a unique combination of medicine ingredients with their strength. \r\n\n |
| 3 | GDSF | generic drug strength form | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients with their strength in a specific dose form. The scoping entity identifies a unique combination of medicine ingredients with their strength in a single dose form. \r\n\n |
| 2 | MGDSF | manufactured drug strength form | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients with their strength in a specific dose form. The scoping entity identifies a unique combination of medicine ingredients with their strength in a single dose form. \r\n\n |
| 1 | (_MemberRoleType) Abstract | \n Types of membership for Role code "MBR" \r\n\n | |
| 2 | TRB | Tribal Member | \n A person who is a member of a tribe. \r\n\n |
| 1 | (_PersonalRelationshipRoleType) Abstract | ||
| 2 | FAMMEMB | family member | \n A relationship between two people characterizing their "familial" relationship \r\n\n |
| 3 | CHILD | child | \n The player of the role is a child of the scoping entity. \r\n\n |
| 4 | CHLDADOPT | adopted child | \n The player of the role is a child taken into a family through legal means and raised by the scoping person (parent) as his or her own child. \r\n\n |
| 5 | DAUADOPT | adopted daughter | \n The player of the role is a female child taken into a family through legal means and raised by the scoping person (parent) as his or her own child. \r\n\n |
| 5 | SONADOPT | adopted son | \n The player of the role is a male child taken into a family through legal means and raised by the scoping person (parent) as his or her own child. \r\n\n |
| 4 | CHLDFOST | foster child | \n The player of the role is a child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties. \r\n\n |
| 5 | DAUFOST | foster daughter | \n The player of the role is a female child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties. \r\n\n |
| 5 | SONFOST | foster son | \n The player of the role is a male child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties. \r\n\n |
| 4 | DAUC | daughter | \n \n Description: The player of the role is a female child (of any type) of scoping entity (parent) \r\n\n |
| 5 | DAUADOPT | ||
| 5 | DAUFOST | ||
| 5 | DAU | natural daughter | \n The player of the role is a female offspring of the scoping entity (parent). \r\n\n |
| 5 | STPDAU | stepdaughter | \n The player of the role is a daughter of the scoping person's spouse by a previous union. \r\n\n |
| 4 | NCHILD | natural child | \n The player of the role is an offspring of the scoping entity as determined by birth. \r\n\n |
| 5 | DAU | ||
| 5 | SON | natural son | \n The player of the role is a male offspring of the scoping entity (parent). \r\n\n |
| 4 | SONC | son | \n \n Description: The player of the role is a male child (of any type) of scoping entity (parent) \r\n\n |
| 5 | SONADOPT | ||
| 5 | SONFOST | ||
| 5 | SON | ||
| 5 | STPSON | stepson | \n The player of the role is a son of the scoping person's spouse by a previous union. \r\n\n |
| 4 | STPCHLD | step child | \n The player of the role is a child of the scoping person's spouse by a previous union. \r\n\n |
| 5 | STPDAU | ||
| 5 | STPSON | ||
| 3 | EXT | extended family member | \n \n Description: A family member not having an immediate genetic or legal relationship e.g. Aunt, cousin, great grandparent, grandchild, grandparent, niece, nephew or uncle. \r\n\n |
| 4 | AUNT | aunt | \n The player of the role is a sister of the scoping person's mother or father. \r\n\n |
| 5 | MAUNT | maternal aunt | \n \n Description:The player of the role is a biological sister of the scoping person's biological mother. \r\n\n |
| 5 | PAUNT | paternal aunt | \n \n Description:The player of the role is a biological sister of the scoping person's biological father. \r\n\n |
| 4 | COUSN | cousin | \n The player of the role is a relative of the scoping person descended from a common ancestor, such as a \tgrandparent, by two or more steps in a diverging line. \r\n\n |
| 5 | MCOUSN | maternal cousin | \n \n Description:The player of the role is a biological relative of the scoping person descended from a common ancestor on the player's mother's side, such as a grandparent, by two or more steps in a diverging line. \r\n\n |
| 5 | PCOUSN | paternal cousin | \n \n Description:The player of the role is a biological relative of the scoping person descended from a common ancestor on the player's father's side, such as a grandparent, by two or more steps in a diverging line. \r\n\n |
| 4 | GGRPRN | great grandparent | \n The player of the role is a parent of the scoping person's grandparent. \r\n\n |
| 5 | GGRFTH | great grandfather | \n The player of the role is the father of the scoping person's grandparent. \r\n\n |
| 6 | MGGRFTH | maternal great-grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological mother's parent. \r\n\n |
| 6 | PGGRFTH | paternal great-grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological father's parent. \r\n\n |
| 5 | GGRMTH | great grandmother | \n The player of the role is the mother of the scoping person's grandparent. \r\n\n |
| 6 | MGGRMTH | maternal great-grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological mother's parent. \r\n\n |
| 6 | PGGRMTH | paternal great-grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological father's parent. \r\n\n |
| 5 | MGGRPRN | maternal great-grandparent | \n \n Description:The player of the role is a biological parent of the scoping person's biological mother's parent. \r\n\n |
| 6 | MGGRFTH | ||
| 6 | MGGRMTH | ||
| 5 | PGGRPRN | paternal great-grandparent | \n \n Description:The player of the role is a biological parent of the scoping person's biological father's parent. \r\n\n |
| 6 | PGGRFTH | ||
| 6 | PGGRMTH | ||
| 4 | GRNDCHILD | grandchild | \n The player of the role is a child of the scoping person's son or daughter. \r\n\n |
| 5 | GRNDDAU | granddaughter | \n The player of the role is a daughter of the scoping person's son or daughter. \r\n\n |
| 5 | GRNDSON | grandson | \n The player of the role is a son of the scoping person's son or daughter. \r\n\n |
| 4 | GRPRN | grandparent | \n The player of the role is a parent of the scoping person's mother or father. \r\n\n |
| 5 | GRFTH | grandfather | \n The player of the role is the father of the scoping person's mother or father. \r\n\n |
| 6 | MGRFTH | maternal grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological mother. \r\n\n |
| 6 | PGRFTH | paternal grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological father. \r\n\n |
| 5 | GRMTH | grandmother | \n The player of the role is the mother of the scoping person's mother or father. \r\n\n |
| 6 | MGRMTH | maternal grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological mother. \r\n\n |
| 6 | PGRMTH | paternal grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological father. \r\n\n |
| 5 | MGRPRN | maternal grandparent | \n \n Description:The player of the role is the biological parent of the scoping person's biological mother. \r\n\n |
| 6 | MGRFTH | ||
| 6 | MGRMTH | ||
| 5 | PGRPRN | paternal grandparent | \n \n Description:The player of the role is the biological parent of the scoping person's biological father. \r\n\n |
| 6 | PGRFTH | ||
| 6 | PGRMTH | ||
| 4 | INLAW | inlaw | \n A relationship between an individual and a member of their spousal partner's immediate family. \r\n\n |
| 5 | CHLDINLAW | child-in-law | \n The player of the role is the spouse of scoping person's child. \r\n\n |
| 6 | DAUINLAW | daughter in-law | \n The player of the role is the wife of scoping person's son. \r\n\n |
| 6 | SONINLAW | son in-law | \n The player of the role is the husband of scoping person's daughter. \r\n\n |
| 5 | PRNINLAW | parent in-law | \n The player of the role is the parent of scoping person's husband or wife. \r\n\n |
| 6 | FTHINLAW | father-in-law | \n The player of the role is the father of the scoping person's husband or wife. \r\n\n |
| 6 | MTHINLAW | mother-in-law | \n The player of the role is the mother of the scoping person's husband or wife. \r\n\n |
| 5 | SIBINLAW | sibling in-law | \n The player of the role is: (1) a sibling of the scoping person's spouse, or (2) the spouse of the scoping person's sibling, or (3) the spouse of a sibling of the scoping person's spouse. \r\n\n |
| 6 | BROINLAW | brother-in-law | \n The player of the role is: (1) a brother of the scoping person's spouse, or (2) the husband of the scoping person's sister, or (3) the husband of a sister of the scoping person's spouse. \r\n\n |
| 6 | SISINLAW | sister-in-law | \n The player of the role is: (1) a sister of the scoping person's spouse, or (2) the wife of the scoping person's brother, or (3) the wife of a brother of the scoping person's spouse. \r\n\n |
| 4 | NIENEPH | niece/nephew | \n The player of the role is a child of scoping person's brother or sister or of the brother or sister of the \tscoping person's spouse. \r\n\n |
| 5 | NEPHEW | nephew | \n The player of the role is a son of the scoping person's brother or sister or of the brother or sister of the \tscoping person's spouse. \r\n\n |
| 5 | NIECE | niece | \n The player of the role is a daughter of the scoping person's brother or sister or of the brother or sister of the \tscoping person's spouse. \r\n\n |
| 4 | UNCLE | uncle | \n The player of the role is a brother of the scoping person's mother or father. \r\n\n |
| 5 | MUNCLE | maternal uncle | \n \n Description:The player of the role is a biological brother of the scoping person's biological mother. \r\n\n |
| 5 | PUNCLE | paternal uncle | \n \n Description:The player of the role is a biological brother of the scoping person's biological father. \r\n\n |
| 3 | PRN | parent | \n The player of the role is one who begets, gives birth to, or nurtures and raises the scoping entity (child). \r\n\n |
| 4 | ADOPTP | adoptive parent | \n The player of the role (parent) has taken the scoper (child) into their family through legal means and raises them as his or her own child. \r\n\n |
| 5 | ADOPTF | adoptive father | \n The player of the role (father) is a male who has taken the scoper (child) into their family through legal means and raises them as his own child. \r\n\n |
| 5 | ADOPTM | adoptive mother | \n The player of the role (father) is a female who has taken the scoper (child) into their family through legal means and raises them as her own child. \r\n\n |
| 4 | FTH | father | \n The player of the role is a male who begets or raises or nurtures the scoping entity (child). \r\n\n |
| 5 | ADOPTF | ||
| 5 | FTHFOST | foster father | \n The player of the role (parent) who is a male state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary. \r\n\n The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child. \r\n\n |
| 5 | NFTH | natural father | \n The player of the role is a male who begets the scoping entity (child). \r\n\n |
| 6 | NFTHF | natural father of fetus | \n Indicates the biologic male parent of a fetus. \r\n\n |
| 5 | STPFTH | stepfather | \n The player of the role is the husband of scoping person's mother and not the scoping person's natural father. \r\n\n |
| 4 | MTH | mother | \n The player of the role is a female who conceives, gives birth to, or raises and nurtures the scoping entity (child). \r\n\n |
| 5 | ADOPTM | ||
| 5 | GESTM | gestational mother | \n The player is a female whose womb carries the fetus of the scoper. Generally used when the gestational mother and natural mother are not the same. \r\n\n |
| 5 | MTHFOST | foster mother | \n The player of the role (parent) who is a female state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary. \r\n\n The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child. \r\n\n |
| 5 | NMTH | natural mother | \n The player of the role is a female who conceives or gives birth to the scoping entity (child). \r\n\n |
| 6 | NMTHF | natural mother of fetus | \n The player is the biologic female parent of the scoping fetus. \r\n\n |
| 5 | STPMTH | stepmother | \n The player of the role is the wife of scoping person's father and not the scoping person's natural mother. \r\n\n |
| 4 | NPRN | natural parent | |
| 5 | NFTH | ||
| 5 | NMTH | ||
| 4 | PRNFOST | foster parent | \n The player of the role (parent) who is a state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary. \r\n\n The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child. \r\n\n |
| 5 | FTHFOST | ||
| 5 | MTHFOST | ||
| 4 | STPPRN | step parent | \n The player of the role is the spouse of the scoping person's parent and not the scoping person's natural parent. \r\n\n |
| 5 | STPFTH | ||
| 5 | STPMTH | ||
| 3 | SIB | sibling | \n The player of the role shares one or both parents in common with the scoping entity. \r\n\n |
| 4 | BRO | brother | \n The player of the role is a male sharing one or both parents in common with the scoping entity. \r\n\n |
| 5 | HBRO | half-brother | \n The player of the role is a male related to the scoping entity by sharing only one biological parent. \r\n\n |
| 5 | NBRO | natural brother | \n The player of the role is a male having the same biological parents as the scoping entity. \r\n\n |
| 6 | TWINBRO | twin brother | \n The scoper was carried in the same womb as the male player and shares common biological parents. \r\n\n |
| 7 | FTWINBRO | fraternal twin brother | \n The scoper was carried in the same womb as the male player and shares common biological parents but is the product of a distinct egg/sperm pair. \r\n\n |
| 7 | ITWINBRO | identical twin brother | \n The male scoper is an offspring of the same egg-sperm pair as the male player. \r\n\n |
| 5 | STPBRO | stepbrother | \n The player of the role is a son of the scoping person's stepparent. \r\n\n |
| 4 | HSIB | half-sibling | \n The player of the role is related to the scoping entity by sharing only one biological parent. \r\n\n |
| 5 | HBRO | ||
| 5 | HSIS | half-sister | \n The player of the role is a female related to the scoping entity by sharing only one biological parent. \r\n\n |
| 4 | NSIB | natural sibling | \n The player of the role has both biological parents in common with the scoping entity. \r\n\n |
| 5 | NBRO | ||
| 5 | NSIS | natural sister | \n The player of the role is a female having the same biological parents as the scoping entity. \r\n\n |
| 6 | TWINSIS | twin sister | \n The scoper was carried in the same womb as the female player and shares common biological parents. \r\n\n |
| 7 | FTWINSIS | fraternal twin sister | \n The scoper was carried in the same womb as the female player and shares common biological parents but is the product of a distinct egg/sperm pair. \r\n\n |
| 7 | ITWINSIS | identical twin sister | \n The female scoper is an offspring of the same egg-sperm pair as the female player. \r\n\n |
| 5 | TWIN | twin | \n The scoper and player were carried in the same womb and shared common biological parents. \r\n\n |
| 6 | TWINBRO | ||
| 6 | TWINSIS | ||
| 6 | FTWIN | fraternal twin | \n The scoper and player were carried in the same womb and share common biological parents but are the product of distinct egg/sperm pairs. \r\n\n |
| 7 | FTWINBRO | ||
| 7 | FTWINSIS | ||
| 6 | ITWIN | identical twin | \n The scoper and player are offspring of the same egg-sperm pair. \r\n\n |
| 7 | ITWINBRO | ||
| 7 | ITWINSIS | ||
| 4 | SIS | sister | \n The player of the role is a female sharing one or both parents in common with the scoping entity. \r\n\n |
| 5 | HSIS | ||
| 5 | NSIS | ||
| 5 | STPSIS | stepsister | \n The player of the role is a daughter of the scoping person's stepparent. \r\n\n |
| 4 | STPSIB | step sibling | \n The player of the role is a child of the scoping person's stepparent. \r\n\n |
| 5 | STPBRO | ||
| 5 | STPSIS | ||
| 3 | SIGOTHR | significant other | \n A person who is important to one's well being; especially a spouse or one in a similar relationship. (The player is the one who is important) \r\n\n |
| 4 | DOMPART | domestic partner | \n The player of the role cohabits with the scoping person but is not the scoping person's spouse. \r\n\n |
| 4 | FMRSPS | former spouse | \n Player of the role was previously joined to the scoping person in marriage and this marriage is now dissolved and inactive. \r\n\n \n Usage Note: This is significant to indicate as some jurisdictions have different legal requirements for former spouse to access the patient's record, from a general friend. \r\n\n |
| 4 | SPS | spouse | \n The player of the role is a marriage partner of the scoping person. \r\n\n |
| 5 | HUSB | husband | \n The player of the role is a man joined to a woman (scoping person) in marriage. \r\n\n |
| 5 | WIFE | wife | \n The player of the role is a woman joined to a man (scoping person) in marriage. \r\n\n |
| 2 | FRND | unrelated friend | \n The player of the role is a person who is known, liked, and trusted by the scoping person. \r\n\n |
| 2 | NBOR | neighbor | \n The player of the role lives near or next to the \tscoping person. \r\n\n |
| 2 | ONESELF | self | \n The relationship that a person has with his or her self. \r\n\n |
| 2 | ROOM | Roommate | \n One who shares living quarters with the subject. \r\n\n |
| 1 | (_PolicyOrProgramCoverageRoleType) Abstract | \n \n Description: A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria. \r\n\n Eligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law. These criteria may be: \r\n\n \n \n The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage \r\n\n \n \n May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent \r\n\n \n \n May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits. \r\n\n \n \n \n Discussion: The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role. For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead. \r\n\n In summary, the coded concepts in the Abstract Value Set "CoveredPartyRoleType" can be "post-coordinated" with the "RoleClassCoveredParty" Abstract Value Set. Decoupling these concepts is intended to support an expansive range of covered party concepts and their semantic comparability. \r\n\n | |
| 2 | (_CoverageRoleType) Abstract | \n Role recognized through the issuance of insurance coverage to an identified covered party who has this relationship with the policy holder such as the policy holder themselves (self), spouse, child, etc \r\n\n | |
| 3 | FAMDEP | family dependent | \n The player of the role is dependent of the scoping entity. \r\n\n |
| 3 | HANDIC | handicapped dependent | \n Covered party is a dependent of the policy holder with a physical or mental disability causing a disadvantage that makes independent achievement unusually difficult. \r\n\n |
| 3 | INJ | injured plaintiff | \n Covered party is an injured party with a legal claim for compensation against a policy holder under an insurance policy. \r\n\n |
| 3 | SELF | self | \n Covered party is the policy holder. Also known as the subscriber. \r\n\n |
| 3 | SPON | sponsored dependent | \n Covered party is an individual that the policy holder has assumed responsibility for, such as foster child or legal ward. \r\n\n |
| 3 | STUD | student | \n Covered party to an insurance policy has coverage through full-time or part-time attendance at a recognized educational institution as defined by a particular insurance policy. \r\n\n |
| 4 | FSTUD | full-time student | \n Covered party to an insurance policy has coverage through full-time attendance at a recognized educational institution as defined by a particular insurance policy. \r\n\n |
| 4 | PSTUD | part-time student | \n Covered party to an insurance policy has coverage through part-time attendance at a recognized educational institution as defined by a particular insurance policy. \r\n\n |
| 3 | ADOPT | adopted child | \n A child taken into one's family through legal means and raised as one's own child. \r\n\n |
| 3 | GCHILD | grandchild | \n A child of one's son or daughter. \r\n\n |
| 3 | GPARNT | grandparent | \n parent of a parent of the subject. \r\n\n |
| 3 | NAT | natural child | \n A child as determined by birth. \r\n\n |
| 3 | NIENE | niece/nephew | \n A child of one's brother or sister or of the brother or sister of one's spouse. \r\n\n |
| 3 | PARNT | parent | \n One that begets or brings forth offspring or a person who brings up and cares for for another (Webster's Collegiate Dictionary) \r\n\n |
| 3 | SPSE | spouse | \n A marriage partner; a husband or wife. \r\n\n |
| 3 | STEP | step child | \n A child receiving parental care and nurture from a person who is related to them through marriage to their parent. \r\n\n |
| 2 | (_CoveredPartyRoleType) Abstract | \n A role recognized through the eligibility of an identified living subject for benefits covered under an insurance policy or a program. Eligibility as a covered party may be conditioned on a relationship with (1) the policy holder such as the policy holder who is covered as an individual under a poliy or as a party sponsored for coverage by the policy holder. \r\n\n \n Example:An employee as a subscriber; or (2) on being scoped another covered party such as the subscriber, as in the case of a dependent. \r\n\n \n Discussion: The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". Other codes in the Abstract Value Set CoveredPartyRoleType domain can be "post-coordinated" with the EligiblePartyRoleType codes to denote comparable concepts. Decoupling the concepts is intended to support a wider range of concepts and semantic comparability of coded concepts. \r\n\n | |
| 3 | (_ClaimantCoveredPartyRoleType) Abstract | \n \n DescriptionA role recognized through the eligibility of a party play a claimant for benefits covered or provided under an insurance policy. \r\n\n | |
| 4 | CRIMEVIC | crime victim | \n \n Description: A person playing the role of program eligible under a program based on allegations of being the victim of a crime. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is "program eligible" and the person's status as a crime victim meets jurisdictional or program criteria. \r\n\n |
| 4 | INJWKR | injured worker | \n \n Description: A person playing the role of program eligible under a workers compensation program based on the filing of work-related injury claim. \r\n\n \n Discussion: This CoveredPartyRoleType.code is used when the CoveredPartyRole class code is either "program eligible", a "named insured", and "individual insured", or "dependent", and the person's status as differently abled or "handicapped" meets jurisdictional, policy, or program criteria. \r\n\n |
| 3 | (_DependentCoveredPartyRoleType) Abstract | \n \n Description: A role recognized through the eligibility of a party to play a dependent for benefits covered or provided under a health insurance policy because of an association with the subscriber that is recognized by the policy underwriter. \r\n\n | |
| 4 | COCBEN | continuity of coverage beneficiary | \n \n Description: A person playing the role of an individual insured with continuity of coverage under a policy which is being terminated based on loss of original status that was the basis for coverage. Criteria for qualifying for continuity of coverage may be set by law. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a continuity of coverage beneficiary meets jurisdictional or policy criteria. \r\n\n |
| 4 | DIFFABL | differently abled | \n \n Description: A person playing the role of program eligible under a program based on meeting criteria for health or functional limitation set by law or by the program. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible", "named insured", "individual insured", or "dependent", and the person's status as differently abled meets jurisdictional, policy, or program criteria. \r\n\n |
| 4 | WARD | ward | \n \n Description: A person, who is a minor or is deemed incompetent, who plays the role of a program eligible where eligibility for coverage is based on meeting program eligibility criteria for status as a ward of a court or jurisdiction. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is a "claimant", "program eligible", a "named insured", an "individual Insured" or a "dependent", and the person's status as a ward meets program or policy criteria. In the case of a ward covered under a program providing financial or health benefits, a governmental agency may take temporary custody of a minor or incompetent for his/her protection and care, e.g., if the ward is suffering from neglect or abuse, or has been in trouble with the law. \r\n\n |
| 3 | (_IndividualInsuredPartyRoleType) Abstract | \n A role recognized through the eligibility of a party to play an individual insured for benefits covered or provided under an insurance policy where the party is also the policy holder. \r\n\n | |
| 4 | COCBEN | ||
| 4 | RETIREE | retiree | \n \n Description: A person playing the role of an individual insured under a policy based on meeting criteria for the employment status of retired set by law or the policy. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a retiree meets jurisdictional or policy criteria. \r\n\n |
| 3 | (_ProgramEligiblePartyRoleType) Abstract | \n \n Description:A role recognized through the eligibility of a party to play a program eligible for benefits covered or provided under a program. \r\n\n | |
| 4 | CRIMEVIC | ||
| 4 | INJWKR | ||
| 4 | DIFFABL | ||
| 4 | WARD | ||
| 4 | INDIG | member of an indigenous people | \n \n Description: A person playing the role of program eligible under a program based on aboriginal ancestry or as a member of an aboriginal community. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is "program eligible" and the person's status as a member of an indigenous people meets jurisdictional or program criteria. \r\n\n |
| 4 | MIL | military | \n \n Definition: A person playing the role of program eligible under a program based on military status. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a member of the military meets jurisdictional or program criteria \r\n\n |
| 5 | ACTMIL | active duty military | \n \n Description: A person playing the role of program eligible under a program based on active military status. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the persons status as active duty military meets jurisdictional or program criteria. \r\n\n |
| 5 | RETMIL | retired military | \n \n Description: A person playing the role of program eligible under a program based on retired military status. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the persons status as retired military meets jurisdictional or program criteria. \r\n\n |
| 5 | VET | veteran | \n \n Description: A person playing the role of program eligible under a program based on status as a military veteran. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the persons status as a veteran meets jurisdictional or program criteria. \r\n\n |
| 3 | (_SubscriberCoveredPartyRoleType) Abstract | \n \n Description: A role recognized through the eligibility of a party to play a subscriber for benefits covered or provided under a health insurance policy. \r\n\n | |
| 4 | COCBEN | ||
| 4 | RETIREE | ||
| 4 | MIL | ||
| 1 | (_ResearchSubjectRoleBasis) Abstract | \n Specifies the administrative functionality within a formal experimental design for which the ResearchSubject role was established. Examples: screening - role is used for pre-enrollment evaluation portion of the design; enrolled - role is used for subjects admitted to the active treatment portion of the design. \r\n\n | |
| 2 | ERL | enrollment | \n \n Definition:The specific role being played by a research subject participating in the active treatment or primary data collection portion of a research study. \r\n\n |
| 2 | SCN | screening | \n \n Definition:The specific role being played by a research subject participating in the pre-enrollment evaluation portion of a research study. \r\n\n |
| 1 | (_ServiceDeliveryLocationRoleType) Abstract | \n A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered. \r\n\n | |
| 2 | (_DedicatedServiceDeliveryLocationRoleType) Abstract | \n A role of a place that further classifies a setting that is intended to house the provision of services. \r\n\n | |
| 3 | (_DedicatedClinicalLocationRoleType) Abstract | \n A role of a place that further classifies the clinical setting (e.g., cardiology clinic, primary care clinic, rehabilitation hospital, skilled nursing facility) in which care is delivered during an encounter. \r\n\n | |
| 4 | DX | Diagnostics or therapeutics unit | \n A practice setting where diagnostic procedures or therapeutic interventions are performed \r\n\n |
| 5 | CVDX | Cardiovascular diagnostics or therapeutics unit | \n A practice setting where cardiovascular diagnostic procedures or therapeutic interventions are performed (e.g., cardiac catheterization lab, echocardiography suite) \r\n\n |
| 6 | CATH | Cardiac catheterization lab | |
| 6 | ECHO | Echocardiography lab | |
| 5 | GIDX | Gastroenterology diagnostics or therapeutics lab | \n A practice setting where GI procedures (such as endoscopies) are performed \r\n\n |
| 6 | ENDOS | Endoscopy lab | \n (X12N 261QD0000N) \r\n\n |
| 5 | RADDX | Radiology diagnostics or therapeutics unit | \n A practice setting where radiology services (diagnostic or therapeutic) are provided (X12N 261QR0200N) \r\n\n |
| 6 | RADO | Radiation oncology unit | \n (X12N 261QX0203N) \r\n\n |
| 6 | RNEU | Neuroradiology unit | |
| 4 | HOSP | Hospital | \n An acute care institution that provides medical, surgical, or psychiatric care and treatment for the sick or the injured. \r\n\n |
| 5 | CHR | Chronic Care Facility | \n (1) A hospital including a physical plant and personnel that provides multidisciplinary diagnosis and treatment for diseases that have one or more of the following characteristics: is permanent; leaves residual disability; is caused by nonreversible pathological alteration; requires special training of the patient for rehabilitation; and/or may be expected to require a long period of supervision or care. In addition, patients require the safety, security, and shelter of these specialized inpatient or partial hospitalization settings. (2) A hospital that provides medical and skilled nursing services to patients with long-term illnesses who are not in an acute phase but who require an intensity of services not available in nursing homes \r\n\n |
| 5 | GACH | Hospitals; General Acute Care Hospital | \n (X12N 282N00000N) \r\n\n |
| 5 | MHSP | Military Hospital | \n A health care facility operated by the Department of Defense or other military operation. \r\n\n |
| 5 | PSYCHF | Psychatric Care Facility | \n Healthcare facility that cares for patients with psychiatric illness(s). \r\n\n |
| 5 | RH | Rehabilitation hospital | \n (X12N 283X00000N) \r\n\n |
| 6 | RHAT | addiction treatment center | \n \n Description: A location that plays the role of delivering services which may include life training and/or social support to people with addictions. \r\n\n |
| 6 | RHII | intellectual impairment center | \n \n Description: A location that plays the role of delivering services which may include adaptation, rehabilitation and social integration services for people with intellectual and/or pervasive development disorders such as autism or severe behaviour disorder. \r\n\n |
| 6 | RHMAD | parents with adjustment difficulties center | \n \n Description: A location that plays the role of delivering services which may social support services for adolescents who are pregnant or have child and are experiencing adaptation issues/difficulties in their current or eventual parenting role. \r\n\n |
| 6 | RHPI | physical impairment center | \n \n Description: A location that plays the role of delivering services which may include adaptation, rehabilitation and social integration services for people with physical impairments. \r\n\n |
| 7 | RHPIH | physical impairment - hearing center | \n \n Description: A location that plays the role of delivering services for people with hearing impairments. \r\n\n |
| 7 | RHPIMS | physical impairment - motor skills center | \n \n Description: A location that plays the role of delivering services for people with motor skill impairments. \r\n\n |
| 7 | RHPIVS | physical impairment - visual skills center | \n \n Description: A location that plays the role of delivering services for people with visual skill impairments. \r\n\n |
| 6 | RHYAD | youths with adjustment difficulties center | \n \n Description: A location that plays the role of delivering services which may include life training and/or social support services for the adaption, rehabilitation and social integration of youths with adjustment difficulties. \r\n\n |
| 4 | HU | Hospital unit | |
| 5 | BMTU | Bone marrow transplant unit | |
| 5 | CCU | Coronary care unit | |
| 5 | CHEST | Chest unit | \n A specialty unit in hospital that focuses on chronic respirator patients and pulmonary failure \r\n\n |
| 5 | EPIL | Epilepsy unit | |
| 5 | ER | Emergency room | \n The section of a health care facility for providing rapid treatment to victims of sudden illness or trauma. \r\n\n |
| 6 | ETU | Emergency trauma unit | |
| 5 | HD | Hemodialysis unit | |
| 5 | HLAB | hospital laboratory | \n \n Description: A location that plays the role of delivering services which may include tests done based on clinical specimens to get health information about a patient as pertaining to the diagnosis, treatment and prevention of disease. Hospital laboratories may be further divided into specialized units such as Anatomic Pathology, Microbiology, and Biochemistry. \r\n\n |
| 6 | INLAB | inpatient laboratory | \n \n Description: A location that plays the role of delivering services which may include tests are done on clinical specimens to get health information about a patient pertaining to the diagnosis, treatment, and prevention of disease for a hospital visit longer than one day. \r\n\n |
| 6 | OUTLAB | outpatient laboratory | \n \n Description: A location that plays the role of delivering services which may include tests are done on clinical specimens to get health information about a patient pertaining to the diagnosis, treatment, and prevention of disease for same day visits. \r\n\n |
| 5 | HRAD | radiology unit | \n \n Description: A location that plays the role of delivering services which may include the branch of medicine that uses ionizing and non-ionizing radiation to diagnose and treat diseases. The radiology unit may be further divided into subspecialties such as Imaging, Cardiovascular, Thoracic, and Ultrasound. \r\n\n |
| 5 | HUSCS | specimen collection site | \n \n Description: A location that plays the role of delivering services which may include collecting specimens and/or samples from patients for laboratory testing purposes, but does not perform any tests or analysis functions. \r\n\n |
| 5 | ICU | Intensive care unit | |
| 6 | PEDICU | Pediatric intensive care unit | |
| 7 | PEDNICU | Pediatric neonatal intensive care unit | |
| 5 | INPHARM | inpatient pharmacy | \n \n Description: A location that plays the role of delivering services which may include providing judicious, safe, efficacious, appropriate and cost effective use of medicines for treatment of patients for visits longer than one day. The distinction between inpatient pharmacies and retail (or outpatient) pharmacies is that they are part of a patient's continuity of care while staying in the hospital. \r\n\n |
| 5 | MBL | medical laboratory | \n \n Description: A location that plays the role of delivering services which include biochemistry, hematology, microbiology, immunochemistry, and toxicology. \r\n\n |
| 5 | NCCS | Neurology critical care and stroke unit | |
| 5 | NS | Neurosurgery unit | |
| 5 | OUTPHARM | outpatient pharmacy | \n \n Description: A location that plays the role of delivering services which may include providing judicious, safe, efficacious, appropriate and cost effective use of medicines for treatment of patients for outpatient visits and may also be used for discharge prescriptions. \r\n\n |
| 5 | PEDU | Pediatric unit | |
| 6 | PEDICU | ||
| 5 | PHU | Psychiatric hospital unit | \n (X12N 273R00000N) \r\n\n |
| 5 | RHU | Rehabilitation hospital unit | |
| 5 | SLEEP | Sleep disorders unit | \n (X12N 261QA1200N) \r\n\n |
| 4 | NCCF | Nursing or custodial care facility | |
| 5 | SNF | Skilled nursing facility | \n (X12N 314000000N) \r\n\n |
| 4 | OF | Outpatient facility | |
| 5 | ALL | Allergy clinic | |
| 5 | AMPUT | Amputee clinic | |
| 5 | BMTC | Bone marrow transplant clinic | |
| 5 | BREAST | Breast clinic | |
| 5 | CANC | Child and adolescent neurology clinic | |
| 5 | CAPC | Child and adolescent psychiatry clinic | |
| 5 | CARD | Ambulatory Health Care Facilities; Clinic/Center; Rehabilitation: Cardiac Facilities | |
| 6 | PEDCARD | Pediatric cardiology clinic | |
| 5 | COAG | Coagulation clinic | |
| 5 | CRS | Colon and rectal surgery clinic | |
| 5 | DERM | Dermatology clinic | |
| 5 | ENDO | Endocrinology clinic | |
| 6 | PEDE | Pediatric endocrinology clinic | |
| 5 | ENT | Otorhinolaryngology clinic | |
| 5 | FMC | Family medicine clinic | |
| 5 | GI | Gastroenterology clinic | |
| 6 | PEDGI | Pediatric gastroenterology clinic | |
| 5 | GIM | General internal medicine clinic | |
| 5 | GYN | Gynecology clinic | |
| 5 | HEM | Hematology clinic | |
| 6 | PEDHEM | Pediatric hematology clinic | |
| 5 | HTN | Hypertension clinic | |
| 5 | IEC | Impairment evaluation center | \n Focuses on assessing disability \r\n\n |
| 5 | INFD | Infectious disease clinic | |
| 6 | PEDID | Pediatric infectious disease clinic | |
| 5 | INV | Infertility clinic | |
| 5 | LYMPH | Lympedema clinic | |
| 5 | MGEN | Medical genetics clinic | |
| 5 | NEPH | Nephrology clinic | |
| 6 | PEDNEPH | Pediatric nephrology clinic | |
| 5 | NEUR | Neurology clinic | |
| 5 | OB | Obstetrics clinic | |
| 5 | OMS | Oral and maxillofacial surgery clinic | |
| 5 | ONCL | Medical oncology clinic | |
| 6 | PEDHO | Pediatric oncology clinic | |
| 5 | OPH | Opthalmology clinic | |
| 5 | OPTC | optometry clinic | \n \n Description: A location that plays the role of delivering services which may include examination, diagnosis, treatment, management, and prevention of diseases and disorders of the eye as well as prescribing and fitting appropriate corrective lenses (glasses or contact lenses) as needed. Optometry clinics may also provide tests for visual field screening, measuring intra-ocular pressure and ophthalmoscopy, as and when required. \r\n\n |
| 5 | ORTHO | Orthopedics clinic | |
| 6 | HAND | Hand clinic | |
| 5 | PAINCL | Pain clinic | \n (X12N 261QP3300N) \r\n\n |
| 5 | PC | Primary care clinic | \n (X12N 261QP2300N) \r\n\n |
| 5 | PEDC | Pediatrics clinic | |
| 6 | PEDCARD | ||
| 6 | PEDE | ||
| 6 | PEDGI | ||
| 6 | PEDHEM | ||
| 6 | PEDID | ||
| 6 | PEDNEPH | ||
| 6 | PEDHO | ||
| 6 | PEDRHEUM | Pediatric rheumatology clinic | |
| 5 | POD | Podiatry clinic | \n (X12N 261QP1100N) \r\n\n |
| 5 | PREV | Preventive medicine clinic | |
| 5 | PROCTO | Proctology clinic | |
| 5 | PROFF | Provider's Office | \n Location where healthcare service was delivered, identified as the healthcare provider's practice office. \r\n\n |
| 5 | PROS | Prosthodontics clinic | |
| 5 | PSI | Psychology clinic | |
| 5 | PSY | Psychiatry clinic | |
| 5 | RHEUM | Rheumatology clinic | |
| 6 | PEDRHEUM | ||
| 5 | SPMED | Sports medicine clinic | |
| 5 | SU | Surgery clinic | |
| 6 | PLS | Plastic surgery clinic | |
| 6 | URO | Urology clinic | |
| 5 | TR | Transplant clinic | |
| 5 | TRAVEL | Travel and geographic medicine clinic | |
| 5 | WND | Wound clinic | |
| 4 | RTF | Residential treatment facility | |
| 5 | PRC | Pain rehabilitation center | |
| 5 | SURF | Substance use rehabilitation facility | \n (X12N 324500000N) \r\n\n |
| 3 | (_DedicatedNonClinicalLocationRoleType) Abstract | \n A role of a place that further classifies a setting that is intended to house the provision of non-clinical services. \r\n\n | |
| 4 | DADDR | Delivery Address | \n Location address where medical supplies were transported to for use. \r\n\n |
| 4 | MOBL | Mobile Unit | \n Location (mobile) where healthcare service was delivered. \r\n\n |
| 5 | AMB | Ambulance | \n Location (mobile) where healthcare service was delivered, identified specifically as an ambulance. \r\n\n |
| 4 | PHARM | Pharmacy | \n Location where healthcare service was delivered, identified as a pharmacy. \r\n\n |
| 5 | INPHARM | ||
| 5 | OUTPHARM | ||
| 2 | (_IncidentalServiceDeliveryLocationRoleType) Abstract | ||
| 3 | ACC | accident site | \n Location of an accident where healthcare service was delivered, such as a roadside. \r\n\n |
| 3 | COMM | Community Location | \n Community location where healthcare is delivered. \r\n\n |
| 4 | CSC | community service center | \n \n Description: A location that plays the role of delivering services which may include providing front-line services to the population of a defined geographic area such as: healthcare services and social services, preventive or curative, rehabilitation or reintegration. \r\n\n |
| 3 | PTRES | Patient's Residence | \n location where healthcare was delivered which is the residence of the Patient. \r\n\n |
| 3 | SCHOOL | school | \n Location where healthcare service was delivered, identified as a school or educational facility. \r\n\n |
| 3 | UPC | underage protection center | \n \n Description: A location that plays the role of delivering services which may include: social emergency services required for a young person as required under any jurisdictional youth laws, child placement, and family mediation in the defined geographical area the SDL is responsible for. It may provide expertise in a judiciary setting on child custody, adoption and biological history research. \r\n\n |
| 3 | WORK | work site | \n Location where healthcare service was delivered, identified as a work place. \r\n\n |
| 1 | (_SpecimenRoleType) Abstract | ||
| 2 | C | Calibrator | \n A specimen used for initial calibration settings of an instrument \r\n\n |
| 2 | G | Group | \n A set of patient samples in which the individuals of the group may or may not be identified. \r\n\n |
| 2 | L | Pool | \n Aliquots of individual specimens combined to form a single specimen representing all of the included individuals. \r\n\n |
| 2 | P | Patient | \n A specimen that has been collected from a patient. \r\n\n |
| 2 | Q | Quality Control | \n A specimen specifically used to verify the sensitivity, specificity, accuracy or other perfomance parameter of a diagnostic test. \r\n\n |
| 3 | B | Blind | \n Quality Control specimen submitted to the lab whose identity and composition is not known to the lab. \r\n\n |
| 3 | E | Electronic QC | \n An electronically simulated QC specimen \r\n\n |
| 3 | F | Filler Proficiency | \n Specimen used for testing proficiency of an organization performing testing (how does this differ from O?) \r\n\n |
| 3 | O | Operator Proficiency | \n A specimen used for evaluation of operator proficiency (operator in what context?) \r\n\n |
| 3 | V | Verifying | \n A specimen used for periodic calibration checks of instruments \r\n\n |
| 2 | R | Replicate | \n A portion of an original patent sample that is tested at the same time as the original sample \r\n\n |
| 1 | CLAIM | claimant | \n A party that makes a claim for coverage under a policy. \r\n\n |
| 1 | communityLaboratory | Community Laboratory | |
| 1 | GT | Guarantor | \n An individual or organization that makes or gives a promise, assurance, pledge to pay or has paid the healthcare service provider. \r\n\n |
| 1 | homeHealth | Home Health | |
| 1 | laboratory | Laboratory | |
| 1 | pathologist | Pathologist | |
| 1 | PH | Policy Holder | \n Policy holder for the insurance policy. \r\n\n |
| 1 | phlebotomist | Phlebotomist | |
| 1 | PROG | program eligible | \n A party that meets the eligibility criteria for coverage under a program. \r\n\n |
| 1 | PT | Patient | \n The recipient for the service(s) and/or product(s) when they are not the covered party. \r\n\n |
| 1 | subject | Self | |
| 1 | thirdParty | Third Party | |
| 1 | DEP | ||
| 1 | DEPEN | dependent | \n A party covered under a policy based on association with a subscriber. \r\n\n |
| 1 | FM | Family Member | \n A member of the covered party's family. This could be the spouse, a parent, a grand parent, a sibling, etc. \r\n\n |
| 1 | INDIV | individual | \n A party covered under a policy as the policyholder. \r\n\n |
| 1 | NAMED | named insured | \n A party to an insurance policy to whom the insurer agrees to indemnify for losses, provides benefits for, or renders services. \r\n\n |
| 1 | PSYCHCF | ||
| 1 | SUBSCR | subscriber | \n A party covered under a policy based on association with a sponsor who is the policy holder, and whose association may provide for the eligibility of dependents for coverage \r\n\n |
Identifies types of dispensing events
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActPharmacySupplyTypehttp://terminology.hl7.org/CodeSystem/v3-ActCode| Code | Display | |
| _ActPharmacySupplyType | ActPharmacySupplyType | Identifies types of dispensing events |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_RouteByMethod) Abstract | \n Route of substance administration classified by administration method. \r\n\n | |
| 2 | SOAK | Immersion (soak) | \n Immersion (soak) \r\n\n |
| 2 | SHAMPOO | Shampoo | \n Shampoo \r\n\n |
| 2 | TRNSLING | Translingual | \n Translingual \r\n\n |
| 2 | PO | Swallow, oral | \n Swallow, oral \r\n\n |
| 2 | GARGLE | Gargle | \n Gargle \r\n\n |
| 2 | SUCK | Suck, oromucosal | \n Suck, oromucosal \r\n\n |
| 2 | (_Chew) Abstract | \n Chew \r\n\n | |
| 3 | CHEW | Chew, oral | \n Chew, oral \r\n\n |
| 2 | (_Diffusion) Abstract | \n Diffusion \r\n\n | |
| 3 | EXTCORPDIF | Diffusion, extracorporeal | \n Diffusion, extracorporeal \r\n\n |
| 3 | HEMODIFF | Diffusion, hemodialysis | \n Diffusion, hemodialysis \r\n\n |
| 3 | TRNSDERMD | Diffusion, transdermal | \n Diffusion, transdermal \r\n\n |
| 2 | (_Dissolve) Abstract | \n Dissolve \r\n\n | |
| 3 | DISSOLVE | Dissolve, oral | \n Dissolve, oral \r\n\n |
| 3 | SL | Dissolve, sublingual | \n Dissolve, sublingual \r\n\n |
| 2 | (_Douche) Abstract | \n Douche \r\n\n | |
| 3 | DOUCHE | Douche, vaginal | \n Douche, vaginal \r\n\n |
| 2 | (_ElectroOsmosisRoute) Abstract | \n Electro-osmosis \r\n\n | |
| 3 | ELECTOSMOS | Electro-osmosis | \n Electro-osmosis \r\n\n |
| 2 | (_Enema) Abstract | \n Enema \r\n\n | |
| 3 | ENEMA | Enema, rectal | \n Enema, rectal \r\n\n |
| 3 | RETENEMA | Enema, rectal retention | \n Enema, rectal retention \r\n\n |
| 2 | (_Flush) Abstract | \n Flush \r\n\n | |
| 3 | IVFLUSH | Flush, intravenous catheter | \n Flush, intravenous catheter \r\n\n |
| 2 | (_Implantation) Abstract | \n Implantation \r\n\n | |
| 3 | IDIMPLNT | Implantation, intradermal | \n Implantation, intradermal \r\n\n |
| 3 | IVITIMPLNT | Implantation, intravitreal | \n Implantation, intravitreal \r\n\n |
| 3 | SQIMPLNT | Implantation, subcutaneous | \n Implantation, subcutaneous \r\n\n |
| 2 | (_Infusion) Abstract | \n Infusion \r\n\n | |
| 3 | EPI | Infusion, epidural | \n Infusion, epidural \r\n\n |
| 3 | IA | Infusion, intraarterial catheter | \n Infusion, intraarterial catheter \r\n\n |
| 3 | IC | Infusion, intracardiac | \n Infusion, intracardiac \r\n\n |
| 3 | ICOR | Infusion, intracoronary | \n Infusion, intracoronary \r\n\n |
| 3 | IOSSC | Infusion, intraosseous, continuous | \n Infusion, intraosseous, continuous \r\n\n |
| 3 | IT | Infusion, intrathecal | \n Infusion, intrathecal \r\n\n |
| 3 | IV | Infusion, intravenous | \n Infusion, intravenous \r\n\n |
| 4 | IVC | Infusion, intravenous catheter | \n Infusion, intravenous catheter \r\n\n |
| 4 | IVCC | Infusion, intravenous catheter, continuous | \n Infusion, intravenous catheter, continuous \r\n\n |
| 4 | IVCI | Infusion, intravenous catheter, intermittent | \n Infusion, intravenous catheter, intermittent \r\n\n |
| 4 | PCA | Infusion, intravenous catheter, pca pump | \n Infusion, intravenous catheter, pca pump \r\n\n |
| 3 | IVASCINFUS | Infusion, intravascular | \n Infusion, intravascular \r\n\n |
| 3 | SQINFUS | Infusion, subcutaneous | \n Infusion, subcutaneous \r\n\n |
| 2 | (_Inhalation) Abstract | \n Inhalation \r\n\n | |
| 3 | IPINHL | Inhalation, respiratory | \n Inhalation, oral \r\n\n |
| 4 | ORIFINHL | Inhalation, oral intermittent flow | \n Inhalation, oral intermittent flow \r\n\n |
| 4 | REBREATH | Inhalation, oral rebreather mask | \n Inhalation, oral rebreather mask \r\n\n |
| 3 | IPPB | Inhalation, intermittent positive pressure breathing (ippb) | \n Inhalation, intermittent positive pressure breathing (ippb) \r\n\n |
| 3 | NASINHL | Inhalation, nasal | \n Inhalation, nasal \r\n\n |
| 4 | NASINHLC | Inhalation, nasal cannula | \n Inhalation, nasal, prongs \r\n\n |
| 3 | NEB | Inhalation, nebulization | \n Inhalation, nebulization \r\n\n |
| 4 | NASNEB | Inhalation, nebulization, nasal | \n Inhalation, nebulization, nasal \r\n\n |
| 4 | ORNEB | Inhalation, nebulization, oral | \n Inhalation, nebulization, oral \r\n\n |
| 3 | TRACH | Inhalation, tracheostomy | \n Inhalation, tracheostomy \r\n\n |
| 3 | VENT | Inhalation, ventilator | \n Inhalation, ventilator \r\n\n |
| 3 | VENTMASK | Inhalation, ventimask | \n Inhalation, ventimask \r\n\n |
| 2 | (_Injection) Abstract | \n Injection \r\n\n | |
| 3 | AMNINJ | Injection, amniotic fluid | \n Injection, amniotic fluid \r\n\n |
| 3 | BILINJ | Injection, biliary tract | \n Injection, biliary tract \r\n\n |
| 3 | CHOLINJ | Injection, for cholangiography | \n Injection, for cholangiography \r\n\n |
| 3 | CERVINJ | Injection, cervical | \n Injection, cervical \r\n\n |
| 3 | EPIDURINJ | Injection, epidural | \n Injection, epidural \r\n\n |
| 3 | EPIINJ | Injection, epidural, push | \n Injection, epidural, push \r\n\n |
| 3 | EPINJSP | Injection, epidural, slow push | \n Injection, epidural, slow push \r\n\n |
| 3 | EXTRAMNINJ | Injection, extra-amniotic | \n Injection, extra-amniotic \r\n\n |
| 3 | EXTCORPINJ | Injection, extracorporeal | \n Injection, extracorporeal \r\n\n |
| 3 | GBINJ | Injection, gastric button | \n Injection, gastric button \r\n\n |
| 3 | GINGINJ | Injection, gingival | \n Injection, gingival \r\n\n |
| 3 | BLADINJ | Injection, urinary bladder | \n Injection, urinary bladder \r\n\n |
| 3 | ENDOSININJ | Injection, endosinusial | \n Injection, endosinusial \r\n\n |
| 3 | HEMOPORT | Injection, hemodialysis port | \n Injection, hemodialysis port \r\n\n |
| 3 | IABDINJ | Injection, intra-abdominal | \n Injection, intra-abdominal \r\n\n |
| 3 | IAINJ | Injection, intraarterial | \n Injection, intraarterial \r\n\n |
| 4 | IAINJP | Injection, intraarterial, push | \n Injection, intraarterial, push \r\n\n |
| 4 | IAINJSP | Injection, intraarterial, slow push | \n Injection, intraarterial, slow push \r\n\n |
| 3 | IARTINJ | Injection, intraarticular | \n Injection, intraarticular \r\n\n |
| 3 | IBURSINJ | Injection, intrabursal | \n Injection, intrabursal \r\n\n |
| 3 | ICARDINJ | Injection, intracardiac | \n Injection, intracardiac \r\n\n |
| 4 | ICARDINJRP | Injection, intracardiac, rapid push | \n Injection, intracardiac, rapid push \r\n\n |
| 4 | ICARDINJSP | Injection, intracardiac, slow push | \n Injection, intracardiac, slow push \r\n\n |
| 4 | ICARINJP | Injection, intracardiac, push | \n Injection, intracardiac, push \r\n\n |
| 3 | ICARTINJ | Injection, intracartilaginous | \n Injection, intracartilaginous \r\n\n |
| 3 | ICAUDINJ | Injection, intracaudal | \n Injection, intracaudal \r\n\n |
| 3 | ICAVINJ | Injection, intracavernous | \n Injection, intracavernous \r\n\n |
| 3 | ICAVITINJ | Injection, intracavitary | \n Injection, intracavitary \r\n\n |
| 3 | ICEREBINJ | Injection, intracerebral | \n Injection, intracerebral \r\n\n |
| 3 | ICISTERNINJ | Injection, intracisternal | \n Injection, intracisternal \r\n\n |
| 3 | ICORONINJ | Injection, intracoronary | \n Injection, intracoronary \r\n\n |
| 4 | ICORONINJP | Injection, intracoronary, push | \n Injection, intracoronary, push \r\n\n |
| 3 | ICORPCAVINJ | Injection, intracorpus cavernosum | \n Injection, intracorpus cavernosum \r\n\n |
| 3 | IDINJ | Injection, intradermal | \n Injection, intradermal \r\n\n |
| 3 | IDISCINJ | Injection, intradiscal | \n Injection, intradiscal \r\n\n |
| 3 | IDUCTINJ | Injection, intraductal | \n Injection, intraductal \r\n\n |
| 3 | IDURINJ | Injection, intradural | \n Injection, intradural \r\n\n |
| 3 | IEPIDINJ | Injection, intraepidermal | \n Injection, intraepidermal \r\n\n |
| 3 | IEPITHINJ | Injection, intraepithelial | \n Injection, intraepithelial \r\n\n |
| 3 | ILESINJ | Injection, intralesional | \n Injection, intralesional \r\n\n |
| 3 | ILUMINJ | Injection, intraluminal | \n Injection, intraluminal \r\n\n |
| 3 | ILYMPJINJ | Injection, intralymphatic | \n Injection, intralymphatic \r\n\n |
| 3 | IM | Injection, intramuscular | \n Injection, intramuscular \r\n\n |
| 4 | IMD | Injection, intramuscular, deep | \n Injection, intramuscular, deep \r\n\n |
| 4 | IMZ | Injection, intramuscular, z track | \n Injection, intramuscular, z track \r\n\n |
| 3 | IMEDULINJ | Injection, intramedullary | \n Injection, intramedullary \r\n\n |
| 3 | INTERMENINJ | Injection, interameningeal | \n Injection, interameningeal \r\n\n |
| 3 | INTERSTITINJ | Injection, interstitial | \n Injection, interstitial \r\n\n |
| 3 | IOINJ | Injection, intraocular | \n Injection, intraocular \r\n\n |
| 3 | IOSSINJ | Injection, intraosseous | \n Injection, intraosseous \r\n\n |
| 3 | IOVARINJ | Injection, intraovarian | \n Injection, intraovarian \r\n\n |
| 3 | IPCARDINJ | Injection, intrapericardial | \n Injection, intrapericardial \r\n\n |
| 3 | IPERINJ | Injection, intraperitoneal | \n Injection, intraperitoneal \r\n\n |
| 3 | IPINJ | Injection, intrapulmonary | \n Injection, intrapulmonary \r\n\n |
| 3 | IPLRINJ | Injection, intrapleural | \n Injection, intrapleural \r\n\n |
| 3 | IPROSTINJ | Injection, intraprostatic | \n Injection, intraprostatic \r\n\n |
| 3 | IPUMPINJ | Injection, insulin pump | \n Injection, insulin pump \r\n\n |
| 3 | ISINJ | Injection, intraspinal | \n Injection, intraspinal \r\n\n |
| 3 | ISTERINJ | Injection, intrasternal | \n Injection, intrasternal \r\n\n |
| 3 | ISYNINJ | Injection, intrasynovial | \n Injection, intrasynovial \r\n\n |
| 3 | ITENDINJ | Injection, intratendinous | \n Injection, intratendinous \r\n\n |
| 3 | ITESTINJ | Injection, intratesticular | \n Injection, intratesticular \r\n\n |
| 3 | ITHORINJ | Injection, intrathoracic | \n Injection, intrathoracic \r\n\n |
| 3 | ITINJ | Injection, intrathecal | \n Injection, intrathecal \r\n\n |
| 3 | ITUBINJ | Injection, intratubular | \n Injection, intratubular \r\n\n |
| 3 | ITUMINJ | Injection, intratumor | \n Injection, intratumor \r\n\n |
| 3 | ITYMPINJ | Injection, intratympanic | \n Injection, intratympanic \r\n\n |
| 3 | IUINJ | Injection, intrauterine | \n Injection, intracervical (uterus) \r\n\n |
| 3 | IUINJC | Injection, intracervical (uterus) | \n Injection, intracervical (uterus) \r\n\n |
| 3 | IURETINJ | Injection, intraureteral, retrograde | \n Injection, intraureteral, retrograde \r\n\n |
| 3 | IVASCINJ | Injection, intravascular | \n Injection, intravascular \r\n\n |
| 3 | IVENTINJ | Injection, intraventricular (heart) | \n Injection, intraventricular (heart) \r\n\n |
| 3 | IVESINJ | Injection, intravesicle | \n Injection, intravesicle \r\n\n |
| 3 | IVINJ | Injection, intravenous | \n Injection, intravenous \r\n\n |
| 4 | IVINJBOL | Injection, intravenous, bolus | \n Injection, intravenous, bolus \r\n\n |
| 4 | IVPUSH | Injection, intravenous, push | \n Injection, intravenous, push \r\n\n |
| 4 | IVRPUSH | Injection, intravenous, rapid push | \n Injection, intravenous, rapid push \r\n\n |
| 4 | IVSPUSH | Injection, intravenous, slow push | \n Injection, intravenous, slow push \r\n\n |
| 3 | IVITINJ | Injection, intravitreal | \n Injection, intravitreal \r\n\n |
| 3 | PAINJ | Injection, periarticular | \n Injection, periarticular \r\n\n |
| 3 | PARENTINJ | Injection, parenteral | \n Injection, parenteral \r\n\n |
| 3 | PDONTINJ | Injection, periodontal | \n Injection, periodontal \r\n\n |
| 3 | PDPINJ | Injection, peritoneal dialysis port | \n Injection, peritoneal dialysis port \r\n\n |
| 3 | PDURINJ | Injection, peridural | \n Injection, peridural \r\n\n |
| 3 | PNINJ | Injection, perineural | \n Injection, perineural \r\n\n |
| 3 | PNSINJ | Injection, paranasal sinuses | \n Injection, paranasal sinuses \r\n\n |
| 3 | RBINJ | Injection, retrobulbar | \n Injection, retrobulbar \r\n\n |
| 3 | SCINJ | Injection, subconjunctival | \n Injection, subconjunctival \r\n\n |
| 3 | SLESINJ | Injection, sublesional | \n Injection, sublesional \r\n\n |
| 3 | SOFTISINJ | Injection, soft tissue | \n Injection, soft tissue \r\n\n |
| 3 | SQ | Injection, subcutaneous | \n Injection, subcutaneous \r\n\n |
| 3 | SUBARACHINJ | Injection, subarachnoid | \n Injection, subarachnoid \r\n\n |
| 3 | SUBMUCINJ | Injection, submucosal | \n Injection, submucosal \r\n\n |
| 3 | TRPLACINJ | Injection, transplacental | \n Injection, transplacental \r\n\n |
| 3 | TRTRACHINJ | Injection, transtracheal | \n Injection, transtracheal \r\n\n |
| 3 | URETHINJ | Injection, urethral | \n Injection, urethral \r\n\n |
| 3 | URETINJ | Injection, ureteral | \n Injection, ureteral \r\n\n |
| 2 | (_Insertion) Abstract | \n Insertion \r\n\n | |
| 3 | CERVINS | Insertion, cervical (uterine) | \n Insertion, cervical (uterine) \r\n\n |
| 3 | IOSURGINS | Insertion, intraocular, surgical | \n Insertion, intraocular, surgical \r\n\n |
| 3 | IU | Insertion, intrauterine | \n Insertion, intrauterine \r\n\n |
| 3 | LPINS | Insertion, lacrimal puncta | \n Insertion, lacrimal puncta \r\n\n |
| 3 | PR | Insertion, rectal | \n Insertion, rectal \r\n\n |
| 3 | SQSURGINS | Insertion, subcutaneous, surgical | \n Insertion, subcutaneous, surgical \r\n\n |
| 3 | URETHINS | Insertion, urethral | \n Insertion, urethral \r\n\n |
| 3 | VAGINSI | Insertion, vaginal | \n Insertion, vaginal \r\n\n |
| 2 | (_Instillation) Abstract | \n Instillation \r\n\n | |
| 3 | CECINSTL | Instillation, cecostomy | \n Instillation, cecostomy \r\n\n |
| 3 | EFT | Instillation, enteral feeding tube | \n Instillation, enteral feeding tube \r\n\n |
| 3 | ENTINSTL | Instillation, enteral | \n Instillation, enteral \r\n\n |
| 3 | GT | Instillation, gastrostomy tube | \n Instillation, gastrostomy tube \r\n\n |
| 3 | NGT | Instillation, nasogastric tube | \n Instillation, nasogastric tube \r\n\n |
| 3 | OGT | Instillation, orogastric tube | \n Instillation, orogastric tube \r\n\n |
| 3 | BLADINSTL | Instillation, urinary catheter | \n Instillation, urinary catheter \r\n\n |
| 3 | CAPDINSTL | Instillation, continuous ambulatory peritoneal dialysis port | \n Instillation, continuous ambulatory peritoneal dialysis port \r\n\n |
| 3 | CTINSTL | Instillation, chest tube | \n Instillation, chest tube \r\n\n |
| 3 | ETINSTL | Instillation, endotracheal tube | \n Instillation, endotracheal tube \r\n\n |
| 3 | GJT | Instillation, gastro-jejunostomy tube | \n Instillation, gastro-jejunostomy tube \r\n\n |
| 3 | IBRONCHINSTIL | Instillation, intrabronchial | \n Instillation, intrabronchial \r\n\n |
| 3 | IDUODINSTIL | Instillation, intraduodenal | \n Instillation, intraduodenal \r\n\n |
| 3 | IESOPHINSTIL | Instillation, intraesophageal | \n Instillation, intraesophageal \r\n\n |
| 3 | IGASTINSTIL | Instillation, intragastric | \n Instillation, intragastric \r\n\n |
| 3 | IILEALINJ | Instillation, intraileal | \n Instillation, intraileal \r\n\n |
| 3 | IOINSTL | Instillation, intraocular | \n Instillation, intraocular \r\n\n |
| 3 | ISININSTIL | Instillation, intrasinal | \n Instillation, intrasinal \r\n\n |
| 3 | ITRACHINSTIL | Instillation, intratracheal | \n Instillation, intratracheal \r\n\n |
| 3 | IUINSTL | Instillation, intrauterine | \n Instillation, intrauterine \r\n\n |
| 3 | JJTINSTL | Instillation, jejunostomy tube | \n Instillation, jejunostomy tube \r\n\n |
| 3 | LARYNGINSTIL | Instillation, laryngeal | \n Instillation, laryngeal \r\n\n |
| 3 | NASALINSTIL | Instillation, nasal | \n Instillation, nasal \r\n\n |
| 3 | NASOGASINSTIL | Instillation, nasogastric | \n Instillation, nasogastric \r\n\n |
| 3 | NTT | Instillation, nasotracheal tube | \n Instillation, nasotracheal tube \r\n\n |
| 3 | OJJ | Instillation, orojejunum tube | \n Instillation, orojejunum tube \r\n\n |
| 3 | OT | Instillation, otic | \n Instillation, otic \r\n\n |
| 3 | PDPINSTL | Instillation, peritoneal dialysis port | \n Instillation, peritoneal dialysis port \r\n\n |
| 3 | PNSINSTL | Instillation, paranasal sinuses | \n Instillation, paranasal sinuses \r\n\n |
| 3 | RECINSTL | Instillation, rectal | \n Instillation, rectal \r\n\n |
| 4 | RECTINSTL | Instillation, rectal tube | \n Instillation, rectal tube \r\n\n |
| 3 | SININSTIL | Instillation, sinus, unspecified | \n Instillation, sinus, unspecified \r\n\n |
| 3 | SOFTISINSTIL | Instillation, soft tissue | \n Instillation, soft tissue \r\n\n |
| 3 | TRACHINSTL | Instillation, tracheostomy | \n Instillation, tracheostomy \r\n\n |
| 3 | TRTYMPINSTIL | Instillation, transtympanic | \n Instillation, transtympanic \r\n\n |
| 3 | URETHINSTL | instillation, urethral | \n Instillation, urethral \r\n\n |
| 2 | (_IontophoresisRoute) Abstract | \n Iontophoresis \r\n\n | |
| 3 | IONTO | Topical application, iontophoresis | \n Topical application, iontophoresis \r\n\n |
| 2 | (_Irrigation) Abstract | \n Irrigation \r\n\n | |
| 3 | GUIRR | Irrigation, genitourinary | \n Irrigation, genitourinary \r\n\n |
| 3 | IGASTIRR | Irrigation, intragastric | \n Irrigation, intragastric \r\n\n |
| 3 | ILESIRR | Irrigation, intralesional | \n Irrigation, intralesional \r\n\n |
| 3 | IOIRR | Irrigation, intraocular | \n Irrigation, intraocular \r\n\n |
| 3 | BLADIRR | Irrigation, urinary bladder | \n Irrigation, urinary bladder \r\n\n |
| 4 | BLADIRRC | Irrigation, urinary bladder, continuous | \n Irrigation, urinary bladder, continuous \r\n\n |
| 4 | BLADIRRT | Irrigation, urinary bladder, tidal | \n Irrigation, urinary bladder, tidal \r\n\n |
| 3 | RECIRR | Irrigation, rectal | \n Irrigation, rectal \r\n\n |
| 2 | (_LavageRoute) Abstract | \n Lavage \r\n\n | |
| 3 | IGASTLAV | Lavage, intragastric | \n Lavage, intragastric \r\n\n |
| 2 | (_MucosalAbsorptionRoute) Abstract | \n Mucosal absorption \r\n\n | |
| 3 | IDOUDMAB | Mucosal absorption, intraduodenal | \n Mucosal absorption, intraduodenal \r\n\n |
| 3 | ITRACHMAB | Mucosal absorption, intratracheal | \n Mucosal absorption, intratracheal \r\n\n |
| 3 | SMUCMAB | Mucosal absorption, submucosal | \n Mucosal absorption, submucosal \r\n\n |
| 2 | (_Nebulization) Abstract | \n Nebulization \r\n\n | |
| 3 | ETNEB | Nebulization, endotracheal tube | \n Nebulization, endotracheal tube \r\n\n |
| 2 | (_Rinse) Abstract | \n Rinse \r\n\n | |
| 3 | DENRINSE | Rinse, dental | \n Rinse, dental \r\n\n |
| 3 | ORRINSE | Rinse, oral | \n Rinse, oral \r\n\n |
| 2 | (_SuppositoryRoute) Abstract | \n Suppository \r\n\n | |
| 3 | URETHSUP | Suppository, urethral | \n Suppository, urethral \r\n\n |
| 2 | (_Swish) Abstract | \n Swish \r\n\n | |
| 3 | SWISHSPIT | Swish and spit out, oromucosal | \n Swish and spit out, oromucosal \r\n\n |
| 3 | SWISHSWAL | Swish and swallow, oromucosal | \n Swish and swallow, oromucosal \r\n\n |
| 2 | (_TopicalAbsorptionRoute) Abstract | \n Topical absorption \r\n\n | |
| 3 | TTYMPTABSORP | Topical absorption, transtympanic | \n Topical absorption, transtympanic \r\n\n |
| 2 | (_TopicalApplication) Abstract | \n Topical application \r\n\n | |
| 3 | DRESS | Topical application, soaked dressing | \n Topical application, soaked dressing \r\n\n |
| 3 | IONTO | ||
| 3 | SWAB | Topical application, swab | \n Topical application, swab \r\n\n |
| 3 | TOPICAL | Topical | \n Topical \r\n\n |
| 3 | BUC | Topical application, buccal | \n Topical application, buccal \r\n\n |
| 3 | CERV | Topical application, cervical | \n Topical application, cervical \r\n\n |
| 3 | DEN | Topical application, dental | \n Topical application, dental \r\n\n |
| 3 | GIN | Topical application, gingival | \n Topical application, gingival \r\n\n |
| 3 | HAIR | Topical application, hair | \n Topical application, hair \r\n\n |
| 3 | ICORNTA | Topical application, intracorneal | \n Topical application, intracorneal \r\n\n |
| 3 | ICORONTA | Topical application, intracoronal (dental) | \n Topical application, intracoronal (dental) \r\n\n |
| 3 | IESOPHTA | Topical application, intraesophageal | \n Topical application, intraesophageal \r\n\n |
| 3 | IILEALTA | Topical application, intraileal | \n Topical application, intraileal \r\n\n |
| 3 | ILTOP | Topical application, intralesional | \n Topical application, intralesional \r\n\n |
| 3 | ILUMTA | Topical application, intraluminal | \n Topical application, intraluminal \r\n\n |
| 3 | IOTOP | Topical application, intraocular | \n Topical application, intraocular \r\n\n |
| 3 | LARYNGTA | Topical application, laryngeal | \n Topical application, laryngeal \r\n\n |
| 3 | MUC | Topical application, mucous membrane | \n Topical application, mucous membrane \r\n\n |
| 3 | NAIL | Topical application, nail | \n Topical application, nail \r\n\n |
| 3 | NASAL | Topical application, nasal | \n Topical application, nasal \r\n\n |
| 3 | OPTHALTA | Topical application, ophthalmic | \n Topical application, ophthalmic \r\n\n |
| 3 | ORALTA | Topical application, oral | \n Topical application, oral \r\n\n |
| 3 | ORMUC | Topical application, oromucosal | \n Topical application, oromucosal \r\n\n |
| 3 | OROPHARTA | Topical application, oropharyngeal | \n Topical application, oropharyngeal \r\n\n |
| 3 | PERIANAL | Topical application, perianal | \n Topical application, perianal \r\n\n |
| 3 | PERINEAL | Topical application, perineal | \n Topical application, perineal \r\n\n |
| 3 | PDONTTA | Topical application, periodontal | \n Topical application, periodontal \r\n\n |
| 3 | RECTAL | Topical application, rectal | \n Topical application, rectal \r\n\n |
| 3 | SCALP | Topical application, scalp | \n Topical application, scalp \r\n\n |
| 3 | OCDRESTA | Occlusive dressing technique | \n Occlusive dressing technique \r\n\n |
| 3 | SKIN | Topical application, skin | \n Topical application, skin \r\n\n |
| 3 | SUBCONJTA | Subconjunctival | \n Subconjunctival \r\n\n |
| 3 | TMUCTA | Topical application, transmucosal | \n Topical application, transmucosal \r\n\n |
| 3 | VAGINS | Topical application, vaginal | \n Insertion, vaginal \r\n\n |
| 2 | INSUF | Insufflation | \n Insufflation \r\n\n |
| 2 | TRNSDERM | Transdermal | \n Transdermal \r\n\n |
| 3 | TRNSDERMD | ||
| 1 | (_RouteBySite) Abstract | \n Route of substance administration classified by site. \r\n\n | |
| 2 | TRNSDERM | ||
| 2 | (_AmnioticFluidSacRoute) Abstract | \n Amniotic fluid sac \r\n\n | |
| 3 | AMNINJ | ||
| 2 | (_BiliaryRoute) Abstract | \n Biliary tract \r\n\n | |
| 3 | BILINJ | ||
| 3 | CHOLINJ | ||
| 2 | (_BodySurfaceRoute) Abstract | \n Body surface \r\n\n | |
| 3 | DRESS | ||
| 3 | ELECTOSMOS | ||
| 3 | IONTO | ||
| 3 | SOAK | ||
| 3 | SWAB | ||
| 3 | TOPICAL | ||
| 2 | (_BuccalMucosaRoute) Abstract | \n Buccal mucosa \r\n\n | |
| 3 | BUC | ||
| 2 | (_CecostomyRoute) Abstract | \n Cecostomy \r\n\n | |
| 3 | CECINSTL | ||
| 2 | (_CervicalRoute) Abstract | \n Cervix of the uterus \r\n\n | |
| 3 | CERV | ||
| 3 | CERVINJ | ||
| 3 | CERVINS | ||
| 3 | DEN | ||
| 3 | DENRINSE | ||
| 2 | (_EndocervicalRoute) Abstract | \n Endocervical \r\n\n | |
| 3 | AMNINJ | ||
| 3 | BILINJ | ||
| 2 | (_EnteralRoute) Abstract | \n Enteral \r\n\n | |
| 3 | EFT | ||
| 3 | ENTINSTL | ||
| 2 | (_EpiduralRoute) Abstract | \n Epidural \r\n\n | |
| 3 | EPI | ||
| 3 | EPIDURINJ | ||
| 3 | EPIINJ | ||
| 3 | EPINJSP | ||
| 2 | (_ExtraAmnioticRoute) Abstract | \n Extra-amniotic \r\n\n | |
| 3 | EXTRAMNINJ | ||
| 2 | (_ExtracorporealCirculationRoute) Abstract | \n Extracorporeal circulation \r\n\n | |
| 3 | EXTCORPDIF | ||
| 3 | EXTCORPINJ | ||
| 2 | (_GastricRoute) Abstract | \n Gastric \r\n\n | |
| 3 | GBINJ | ||
| 3 | GT | ||
| 3 | NGT | ||
| 3 | OGT | ||
| 2 | (_GenitourinaryRoute) Abstract | \n Genitourinary \r\n\n | |
| 3 | GUIRR | ||
| 2 | (_GingivalRoute) Abstract | \n Gingival \r\n\n | |
| 3 | GIN | ||
| 3 | GINGINJ | ||
| 2 | (_HairRoute) Abstract | \n Hair \r\n\n | |
| 3 | HAIR | ||
| 3 | SHAMPOO | ||
| 2 | (_InterameningealRoute) Abstract | \n Interameningeal \r\n\n | |
| 3 | INTERMENINJ | ||
| 2 | (_InterstitialRoute) Abstract | \n Interstitial \r\n\n | |
| 3 | INTERSTITINJ | ||
| 2 | (_IntraabdominalRoute) Abstract | \n Intra-abdominal \r\n\n | |
| 3 | IABDINJ | ||
| 2 | (_IntraarterialRoute) Abstract | \n Intra-arterial \r\n\n | |
| 3 | IA | ||
| 3 | IAINJ | ||
| 2 | (_IntraarticularRoute) Abstract | \n Intraarticular \r\n\n | |
| 3 | IARTINJ | ||
| 2 | (_IntrabronchialRoute) Abstract | \n Intrabronchial \r\n\n | |
| 3 | IBRONCHINSTIL | ||
| 2 | (_IntrabursalRoute) Abstract | \n Intrabursal \r\n\n | |
| 3 | IBURSINJ | ||
| 2 | (_IntracardiacRoute) Abstract | \n Intracardiac \r\n\n | |
| 3 | IC | ||
| 3 | ICARDINJ | ||
| 2 | (_IntracartilaginousRoute) Abstract | \n Intracartilaginous \r\n\n | |
| 3 | ICARTINJ | ||
| 2 | (_IntracaudalRoute) Abstract | \n Intracaudal \r\n\n | |
| 3 | ICAUDINJ | ||
| 2 | (_IntracavernosalRoute) Abstract | \n Intracavernosal \r\n\n | |
| 3 | ICAVINJ | ||
| 2 | (_IntracavitaryRoute) Abstract | \n Intracavitary \r\n\n | |
| 3 | ICAVITINJ | ||
| 2 | (_IntracerebralRoute) Abstract | \n Intracerebral \r\n\n | |
| 3 | ICEREBINJ | ||
| 2 | (_IntracervicalRoute) Abstract | \n Intracervical \r\n\n | |
| 3 | IUINJC | ||
| 2 | (_IntracisternalRoute) Abstract | \n Intracisternal \r\n\n | |
| 3 | ICISTERNINJ | ||
| 2 | (_IntracornealRoute) Abstract | \n Intracorneal \r\n\n | |
| 3 | ICORNTA | ||
| 2 | (_IntracoronalRoute) Abstract | \n Intracoronal (dental) \r\n\n | |
| 3 | ICORONTA | ||
| 2 | (_IntracoronaryRoute) Abstract | \n Intracoronary \r\n\n | |
| 3 | ICOR | ||
| 3 | ICORONINJ | ||
| 2 | (_IntracorpusCavernosumRoute) Abstract | \n Intracorpus cavernosum \r\n\n | |
| 3 | ICORPCAVINJ | ||
| 2 | (_IntradermalRoute) Abstract | \n Intradermal \r\n\n | |
| 3 | IDIMPLNT | ||
| 3 | IDINJ | ||
| 2 | (_IntradiscalRoute) Abstract | \n Intradiscal \r\n\n | |
| 3 | IDISCINJ | ||
| 2 | (_IntraductalRoute) Abstract | \n Intraductal \r\n\n | |
| 3 | IDUCTINJ | ||
| 2 | (_IntraduodenalRoute) Abstract | \n Intraduodenal \r\n\n | |
| 3 | IDUODINSTIL | ||
| 3 | IDOUDMAB | ||
| 2 | (_IntraduralRoute) Abstract | \n Intradural \r\n\n | |
| 3 | IDURINJ | ||
| 2 | (_IntraepidermalRoute) Abstract | \n Intraepidermal \r\n\n | |
| 3 | IEPIDINJ | ||
| 2 | (_IntraepithelialRoute) Abstract | \n Intraepithelial \r\n\n | |
| 3 | IEPITHINJ | ||
| 2 | (_IntraesophagealRoute) Abstract | \n Intraesophageal \r\n\n | |
| 3 | IESOPHINSTIL | ||
| 3 | IESOPHTA | ||
| 2 | (_IntragastricRoute) Abstract | \n Intragastric \r\n\n | |
| 3 | IGASTINSTIL | ||
| 3 | IGASTIRR | ||
| 3 | IGASTLAV | ||
| 2 | (_IntrailealRoute) Abstract | \n Intraileal \r\n\n | |
| 3 | IILEALINJ | ||
| 3 | IILEALTA | ||
| 2 | (_IntralesionalRoute) Abstract | \n Intralesional \r\n\n | |
| 3 | ILESINJ | ||
| 3 | ILESIRR | ||
| 3 | ILTOP | ||
| 2 | (_IntraluminalRoute) Abstract | \n Intraluminal \r\n\n | |
| 3 | ILUMINJ | ||
| 3 | ILUMTA | ||
| 2 | (_IntralymphaticRoute) Abstract | \n Intralymphatic \r\n\n | |
| 3 | ILYMPJINJ | ||
| 2 | (_IntramedullaryRoute) Abstract | \n Intramedullary \r\n\n | |
| 3 | IMEDULINJ | ||
| 2 | (_IntramuscularRoute) Abstract | \n Intramuscular \r\n\n | |
| 3 | IM | ||
| 2 | (_IntraocularRoute) Abstract | \n Intraocular \r\n\n | |
| 3 | IOINJ | ||
| 3 | IOSURGINS | ||
| 3 | IOINSTL | ||
| 3 | IOIRR | ||
| 3 | IOTOP | ||
| 2 | (_IntraosseousRoute) Abstract | \n Intraosseous \r\n\n | |
| 3 | IOSSC | ||
| 3 | IOSSINJ | ||
| 2 | (_IntraovarianRoute) Abstract | \n Intraovarian \r\n\n | |
| 3 | IOVARINJ | ||
| 2 | (_IntrapericardialRoute) Abstract | \n Intrapericardial \r\n\n | |
| 3 | IPCARDINJ | ||
| 2 | (_IntraperitonealRoute) Abstract | \n Intraperitoneal \r\n\n | |
| 3 | IPERINJ | ||
| 3 | PDPINJ | ||
| 3 | CAPDINSTL | ||
| 3 | PDPINSTL | ||
| 2 | (_IntrapleuralRoute) Abstract | \n Intrapleural \r\n\n | |
| 3 | IPLRINJ | ||
| 3 | CTINSTL | ||
| 2 | (_IntraprostaticRoute) Abstract | \n Intraprostatic \r\n\n | |
| 3 | IPROSTINJ | ||
| 2 | (_IntrapulmonaryRoute) Abstract | \n Intrapulmonary \r\n\n | |
| 3 | EXTCORPINJ | ||
| 3 | IPINJ | ||
| 2 | (_IntrasinalRoute) Abstract | \n Intrasinal \r\n\n | |
| 3 | ISININSTIL | ||
| 2 | (_IntraspinalRoute) Abstract | \n Intraspinal \r\n\n | |
| 3 | ISINJ | ||
| 2 | (_IntrasternalRoute) Abstract | \n Intrasternal \r\n\n | |
| 3 | ISTERINJ | ||
| 2 | (_IntrasynovialRoute) Abstract | \n Intrasynovial \r\n\n | |
| 3 | ISYNINJ | ||
| 2 | (_IntratendinousRoute) Abstract | \n Intratendinous \r\n\n | |
| 3 | ITENDINJ | ||
| 2 | (_IntratesticularRoute) Abstract | \n Intratesticular \r\n\n | |
| 3 | ITESTINJ | ||
| 2 | (_IntrathecalRoute) Abstract | \n Intrathecal \r\n\n | |
| 3 | IT | ||
| 3 | ITINJ | ||
| 2 | (_IntrathoracicRoute) Abstract | \n Intrathoracic \r\n\n | |
| 3 | ITHORINJ | ||
| 2 | (_IntratrachealRoute) Abstract | \n Intratracheal \r\n\n | |
| 3 | ITRACHINSTIL | ||
| 3 | ITRACHMAB | ||
| 2 | (_IntratubularRoute) Abstract | \n Intratubular \r\n\n | |
| 3 | ITUBINJ | ||
| 2 | (_IntratumorRoute) Abstract | \n Intratumor \r\n\n | |
| 3 | ITUMINJ | ||
| 2 | (_IntratympanicRoute) Abstract | \n Intratympanic \r\n\n | |
| 3 | ITYMPINJ | ||
| 2 | (_IntrauterineRoute) Abstract | \n Intrauterine \r\n\n | |
| 3 | IUINJ | ||
| 3 | IURETINJ | ||
| 3 | IU | ||
| 3 | IUINSTL | ||
| 2 | (_IntravascularRoute) Abstract | \n Intravascular \r\n\n | |
| 3 | HEMODIFF | ||
| 3 | IVASCINFUS | ||
| 3 | HEMOPORT | ||
| 3 | IVASCINJ | ||
| 2 | (_IntravenousRoute) Abstract | \n Intravenous \r\n\n | |
| 3 | IVFLUSH | ||
| 3 | IVINJ | ||
| 2 | (_IntraventricularRoute) Abstract | \n Intraventricular \r\n\n | |
| 3 | IVENTINJ | ||
| 2 | (_IntravesicleRoute) Abstract | \n Intravesicle \r\n\n | |
| 3 | IVESINJ | ||
| 2 | (_IntravitrealRoute) Abstract | \n Intravitreal \r\n\n | |
| 3 | IVITINJ | ||
| 2 | (_JejunumRoute) Abstract | \n Jejunum \r\n\n | |
| 3 | GJT | ||
| 3 | JJTINSTL | ||
| 3 | OJJ | ||
| 2 | (_LacrimalPunctaRoute) Abstract | \n Lacrimal puncta \r\n\n | |
| 3 | LPINS | ||
| 2 | (_LaryngealRoute) Abstract | \n Laryngeal \r\n\n | |
| 3 | LARYNGINSTIL | ||
| 3 | LARYNGTA | ||
| 2 | (_LingualRoute) Abstract | \n Lingual \r\n\n | |
| 3 | TRNSLING | ||
| 2 | (_MucousMembraneRoute) Abstract | \n Mucous membrane \r\n\n | |
| 3 | MUC | ||
| 2 | (_NailRoute) Abstract | \n Nail \r\n\n | |
| 3 | NAIL | ||
| 2 | (_NasalRoute) Abstract | \n Nasal \r\n\n | |
| 3 | NASINHL | ||
| 3 | NASALINSTIL | ||
| 3 | NASOGASINSTIL | ||
| 3 | NASAL | ||
| 2 | (_OphthalmicRoute) Abstract | \n Ophthalmic \r\n\n | |
| 3 | OPTHALTA | ||
| 2 | (_OralRoute) Abstract | \n Oral \r\n\n | |
| 3 | CHEW | ||
| 3 | DISSOLVE | ||
| 3 | IPINHL | ||
| 3 | ORALTA | ||
| 3 | ORRINSE | ||
| 3 | PO | ||
| 2 | (_OromucosalRoute) Abstract | \n Oromucosal \r\n\n | |
| 3 | GARGLE | ||
| 3 | ORMUC | ||
| 3 | SUCK | ||
| 3 | SWISHSPIT | ||
| 3 | SWISHSWAL | ||
| 2 | (_OropharyngealRoute) Abstract | \n Oropharyngeal \r\n\n | |
| 3 | OROPHARTA | ||
| 2 | (_OticRoute) Abstract | \n Otic \r\n\n | |
| 3 | OT | ||
| 2 | (_ParanasalSinusesRoute) Abstract | \n Paranasal sinuses \r\n\n | |
| 3 | PNSINJ | ||
| 3 | PNSINSTL | ||
| 2 | (_ParenteralRoute) Abstract | \n Parenteral \r\n\n | |
| 3 | PARENTINJ | ||
| 2 | (_PerianalRoute) Abstract | \n Perianal \r\n\n | |
| 3 | PERIANAL | ||
| 2 | (_PeriarticularRoute) Abstract | \n Periarticular \r\n\n | |
| 3 | PAINJ | ||
| 2 | (_PeriduralRoute) Abstract | \n Peridural \r\n\n | |
| 3 | PDURINJ | ||
| 2 | (_PerinealRoute) Abstract | \n Perineal \r\n\n | |
| 3 | PERINEAL | ||
| 2 | (_PerineuralRoute) Abstract | \n Perineural \r\n\n | |
| 3 | PNINJ | ||
| 2 | (_PeriodontalRoute) Abstract | \n Periodontal \r\n\n | |
| 3 | PDONTINJ | ||
| 3 | PDONTTA | ||
| 2 | (_PulmonaryRoute) Abstract | \n Pulmonary \r\n\n | |
| 3 | IPPB | ||
| 3 | VENT | ||
| 3 | VENTMASK | ||
| 3 | ETINSTL | ||
| 3 | NTT | ||
| 3 | ETNEB | ||
| 2 | (_RectalRoute) Abstract | \n Rectal \r\n\n | |
| 3 | ENEMA | ||
| 3 | RETENEMA | ||
| 3 | PR | ||
| 3 | RECINSTL | ||
| 3 | RECIRR | ||
| 3 | RECTAL | ||
| 2 | (_RespiratoryTractRoute) Abstract | \n Respiratory tract \r\n\n | |
| 3 | IPINHL | ||
| 2 | (_RetrobulbarRoute) Abstract | \n Retrobulbar \r\n\n | |
| 3 | RBINJ | ||
| 2 | (_ScalpRoute) Abstract | \n Scalp \r\n\n | |
| 3 | SCALP | ||
| 2 | (_SinusUnspecifiedRoute) Abstract | \n Sinus, unspecified \r\n\n | |
| 3 | ENDOSININJ | ||
| 3 | SININSTIL | ||
| 2 | (_SkinRoute) Abstract | \n Skin \r\n\n | |
| 3 | OCDRESTA | ||
| 3 | SKIN | ||
| 2 | (_SoftTissueRoute) Abstract | \n Soft tissue \r\n\n | |
| 3 | SOFTISINJ | ||
| 3 | SOFTISINSTIL | ||
| 2 | (_SubarachnoidRoute) Abstract | \n Subarachnoid \r\n\n | |
| 3 | SUBARACHINJ | ||
| 2 | (_SubconjunctivalRoute) Abstract | \n Subconjunctival \r\n\n | |
| 3 | SCINJ | ||
| 3 | SUBCONJTA | ||
| 2 | (_SubcutaneousRoute) Abstract | \n Subcutaneous \r\n\n | |
| 3 | SQIMPLNT | ||
| 3 | SQINFUS | ||
| 3 | IPUMPINJ | ||
| 3 | SQ | ||
| 3 | SQSURGINS | ||
| 2 | (_SublesionalRoute) Abstract | \n Sublesional \r\n\n | |
| 3 | SLESINJ | ||
| 2 | (_SublingualRoute) Abstract | \n Sublingual \r\n\n | |
| 3 | SL | ||
| 2 | (_SubmucosalRoute) Abstract | \n Submucosal \r\n\n | |
| 3 | SUBMUCINJ | ||
| 3 | SMUCMAB | ||
| 2 | (_TracheostomyRoute) Abstract | \n Tracheostomy \r\n\n | |
| 3 | TRACH | ||
| 3 | TRACHINSTL | ||
| 2 | (_TransmucosalRoute) Abstract | \n Transmucosal \r\n\n | |
| 3 | TMUCTA | ||
| 2 | (_TransplacentalRoute) Abstract | \n Transplacental \r\n\n | |
| 3 | TRPLACINJ | ||
| 2 | (_TranstrachealRoute) Abstract | \n Transtracheal \r\n\n | |
| 3 | TRTRACHINJ | ||
| 2 | (_TranstympanicRoute) Abstract | \n Transtympanic \r\n\n | |
| 3 | TRTYMPINSTIL | ||
| 3 | TTYMPTABSORP | ||
| 2 | (_UreteralRoute) Abstract | \n Ureteral \r\n\n | |
| 3 | URETINJ | ||
| 2 | (_UrethralRoute) Abstract | \n Urethral \r\n\n | |
| 3 | URETHINJ | ||
| 3 | URETHINS | ||
| 3 | URETHINSTL | ||
| 3 | URETHSUP | ||
| 2 | (_UrinaryBladderRoute) Abstract | \n Urinary bladder \r\n\n | |
| 3 | BLADINJ | ||
| 3 | BLADIRR | ||
| 2 | (_UrinaryTractRoute) Abstract | \n Urinary tract \r\n\n | |
| 3 | BLADINSTL | ||
| 2 | (_VaginalRoute) Abstract | \n Vaginal \r\n\n | |
| 3 | DOUCHE | ||
| 3 | VAGINSI | ||
| 3 | VAGINS | ||
| 2 | (_VitreousHumourRoute) Abstract | \n Vitreous humour \r\n\n | |
| 3 | IVITIMPLNT |
A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto\nbehavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children).
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a _RoleClassMutualRelationshiphttp://terminology.hl7.org/CodeSystem/v3-RoleClass| Code | Display | |
| _RoleClassMutualRelationship | RoleClassMutualRelationship | A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may be de facto behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children). |
Description:\nA task or action that a user may perform in a clinical information system.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActTaskCodeRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | M | Modified subscription | \n Modified subscription to a query server. \r\n\n |
| 1 | N | New subscription | \n New subscription to a query server. \r\n\n |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_ContextControlAdditive) Abstract | \n The association adds to the existing context associated with the Act. Both this association and any associations propagated from ancestor Acts are interpreted as being related to this Act. \r\n\n | |
| 2 | AN | additive, non-propagating | \n The association adds to the existing context associated with the Act, but will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Additive, Non-Propagating" it means that the author will be added to the set of author participations that have propagated from ancestor Acts for the purpose of this Act. However only the previously propagated authors will propagate to any child Acts that allow context to be propagated. \r\n\n |
| 2 | AP | additive, propagating | \n The association adds to the existing context associated with the Act, and will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Additive, Propagating" it means that the author will be added to the set of author participations that have propagated from ancestor Acts, and will itself propagate with the other authors to any child Acts that allow context to be propagated. \r\n\n |
| 1 | (_ContextControlNonPropagating) Abstract | \n The association applies only to the current Act and will not propagate to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd). \r\n\n | |
| 2 | AN | ||
| 2 | ON | overriding, non-propagating | \n The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. However, this overriding association will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Overriding, Non-Propagating" it means that the author will replace the set of author participations that have propagated from ancestor Acts. Furthermore, no author participations whatsoever will propagate to any child Acts that allow context to be propagated. \r\n\n |
| 1 | (_ContextControlOverriding) Abstract | \n The association adds to the existing context associated with the Act, but replaces associations propagated from ancestor Acts whose typeCodes are the same or more specific. \r\n\n | |
| 2 | ON | ||
| 2 | OP | overriding, propagating | \n The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. This overriding association will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Overriding, Propagating" it means that the author will replace the set of author participations that have propagated from ancestor Acts, and will itself be the only author to propagate to any child Acts that allow context to be propagated. \r\n\n |
| 1 | (_ContextControlPropagating) Abstract | \n The association propagates to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd). \r\n\n | |
| 2 | AP | ||
| 2 | OP |
Release Date: 2018-08-12
\r\nAn entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a TRANSRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nAn association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity with a (generally larger) scoping Entity.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a _RoleClassPartitivehttp://terminology.hl7.org/CodeSystem/v3-RoleClass| Code | Display | |
| _RoleClassPartitive | RoleClassPartitive | An association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity with a (generally larger) scoping Entity. |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_CalendarCycleOneLetter) Abstract Deprecated | ||
| 2 | CW | week (continuous) | |
| 2 | CY | year | |
| 2 | D | day of the month | |
| 2 | DW | day of the week (begins with Monday) | |
| 2 | H | hour of the day | |
| 2 | M | month of the year | |
| 2 | N | minute of the hour | |
| 2 | S | second of the minute | |
| 1 | (_CalendarCycleTwoLetter) Abstract Deprecated | ||
| 2 | CW | ||
| 2 | CY | ||
| 2 | D | ||
| 2 | DW | ||
| 2 | H | ||
| 2 | M | ||
| 2 | N | ||
| 2 | S | ||
| 2 | CD | day (continuous) | |
| 2 | CH | hour (continuous) | |
| 2 | CM | month (continuous) | |
| 2 | CN | minute (continuous) | |
| 2 | CS | second (continuous) | |
| 2 | DY | day of the year | |
| 2 | WY | week of the year | |
| 1 | WM | week of the month | \n The week with the month's first Thursday in it (analagous to the ISO 8601 definition for week of the year). \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_ActAccommodationReason) Abstract | \n Identifies the reason the patient is assigned to this accommodation type \r\n\n | |
| 2 | ACCREQNA | Accommodation Requested Not Available | \n Accommodation requested is not available. \r\n\n |
| 2 | FLRCNV | Floor Convenience | \n Accommodation is assigned for floor convenience. \r\n\n |
| 2 | MEDNEC | Medical Necessity | \n Required for medical reasons(s). \r\n\n |
| 2 | PAT | Patient request | \n The Patient requested the action \r\n\n |
| 1 | (_ActCoverageReason) Abstract | \n \n Description:Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties. \r\n\n | |
| 2 | (_EligibilityActReasonCode) Abstract | \n Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. \r\n\n \n Examples: A person is a claimant under an automobile insurance policy are client deceased & adopted client has been given a new policy identifier. A new employee is eligible for health insurance as an employment benefit. A person meets a government program eligibility criteria for financial, age or health status. \r\n\n | |
| 3 | (_ActIneligibilityReason) Abstract | \n Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy. \r\n\n Examples are client deceased & adopted client has been given a new policy identifier. \r\n\n | |
| 4 | COVSUS | coverage suspended | \n When a client has no contact with the health system for an extended period, coverage is suspended. Client will be reinstated to original start date upon proof of identification, residency etc. \r\n\n Example: Coverage may be suspended during a strike situation, when employer benefits for employees are not covered (i.e. not in effect). \r\n\n |
| 4 | DECSD | deceased | \n Client deceased. \r\n\n |
| 4 | REGERR | registered in error | \n Client was registered in error. \r\n\n |
| 3 | (_CoverageEligibilityReason) Abstract | \n Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. \r\n\n \n Examples: A person is a claimant under an automobile insurance policy are client deceased & adopted client has been given a new policy identifier. A new employee is eligible for health insurance as an employment benefit. A person meets a government program eligibility criteria for financial, age or health status. \r\n\n | |
| 4 | AGE | age eligibility | \n A person becomes eligible for a program based on age. \r\n\n \n Example: In the U.S., a person who is 65 years of age or older is eligible for Medicare. \r\n\n |
| 4 | CRIME | crime victim | \n A person becomes eligible for insurance or a program because of crime related health condition or injury. \r\n\n \n Example: A person is a claimant under the U.S. Crime Victims Compensation program. \r\n\n |
| 4 | DIS | disability | \n A person becomes a claimant under a disability income insurance policy or a disability rehabilitation program because of a health condition or injury which limits the person's ability to earn an income or function without institutionalization. \r\n\n |
| 4 | EMPLOY | employment benefit | \n A person becomes eligible for insurance provided as an employment benefit based on employment status. \r\n\n |
| 4 | FINAN | financial eligibility | \n A person becomes eligible for a program based on financial criteria. \r\n\n \n Example: A person whose family income is below a financial threshold for eligibility for Medicaid or SCHIP. \r\n\n |
| 4 | HEALTH | health status | \n A person becomes eligible for a program because of a qualifying health condition or injury. \r\n\n \n Examples: A person is determined to have a qualifying health conditions include pregnancy, HIV/AIDs, tuberculosis, end stage renal disease, breast or cervical cancer, or other condition requiring specialized health services, hospice, institutional or community based care provided under a program \r\n\n |
| 4 | MULTI | multiple criteria eligibility | \n A person becomes eligible for a program based on more than one criterion. \r\n\n \n Examples: In the U.S., a child whose familiy income meets Medicaid financial thresholds and whose age is less than 18 is eligible for the Early and Periodic Screening, Diagnostic, and Treatment program (EPSDT). A person whose family income meets Medicaid financial thresholds and whose age is 65 years or older is eligible for Medicaid and Medicare, and are referred to as dual eligibles. \r\n\n |
| 4 | PNC | property and casualty condition | \n A person becomes a claimant under a property and casualty insurance policy because of a related health condition or injury resulting from a circumstance covered under the terms of the policy. \r\n\n \n Example: A person is a claimant under a homeowners insurance policy because of an injury sustained on the policyholderaTMs premises. \r\n\n |
| 4 | STATUTORY | statutory eligibility | \n A person becomes eligible for a program based on statutory criteria. \r\n\n \n Examples: A person is a member of an indigenous group, a veteran of military service, or in the U.S., a recipient of adoption assistance and foster care under Title IV-E of the Social Security. \r\n\n |
| 4 | VEHIC | motor vehicle accident victim | \n A person becomes a claimant under a motor vehicle accident insurance because of a motor vehicle accident related health condition or injury. \r\n\n |
| 4 | WORK | work related | \n A person becomes eligible for insurance or a program because of a work related health condition or injury. \r\n\n \n Example: A person is a claimant under the U.S. Black Lung Program. \r\n\n |
| 1 | (_ActInformationManagementReason) Abstract | \n \n Description:The rationale or purpose for an act relating to information management, such as archiving information for the purpose of complying with an enterprise data retention policy. \r\n\n | |
| 2 | (_ActHealthInformationManagementReason) Abstract | \n \n Description:The rationale or purpose for an act relating to health information management, such as archiving information for the purpose of complying with an organization policy or jurisdictional law relating to data retention. \r\n\n | |
| 3 | (_ActConsentInformationAccessOverrideReason) Abstract | \n To perform one or more operations on information to which the patient has not consented as deemed necessary by authorized entities for providing care in the best interest of the patient; providing immediately needed health care for an emergent condition; or for protecting public or third party safety. \r\n\n \n Usage Notes: Used to convey the reason that a provider or other entity may or has accessed personal healthcare information. Typically, this involves overriding the subject's consent directives. \r\n\n | |
| 4 | OVRER | emergency treatment override | \n To perform one or more operations on information to which the patient has not consented by authorized entities for treating a condition which poses an immediate threat to the patient's health and which requires immediate medical intervention. \r\n\n \n Usage Notes: The patient is unable to provide consent, but the provider determines they have an urgent healthcare related reason to access the record. \r\n\n |
| 4 | OVRINCOMP | incompetency override | \n To perform one or more operations on information to which the patient has not consented because deemed incompetent to provide consent. \r\n\n \n Usage Note: Maps to v2 CON-16 Subject Competence Indicator (ID) 01791 Definition: Identifies whether the subject was deemed competent to provide consent. Refer to table HL7 Table 0136 - Yes/No Indicator and CON-23 Non-Subject Consenter Reason User-defined Table 0502 - Non-Subject Consenter Reason code NC "Subject is not competent to consent". \r\n\n |
| 4 | OVRPJ | professional judgment override | \n To perform one or more operations on information to which the patient declined to consent for providing health care. \r\n\n \n Usage Notes: The patient, while able to give consent, has not. However the provider believes it is in the patient's interest to access the record without patient consent. \r\n\n |
| 4 | OVRPS | public safety override | \n To perform one or more operations on information to which the patient has not consented for public safety reasons. \r\n\n \n Usage Notes: The patient, while able to give consent, has not. However, the provider believes that access to masked patient information is justified because of concerns related to public safety. \r\n\n |
| 4 | OVRTPS | third party safety override | \n To perform one or more operations on information to which the patient has not consented for third party safety. \r\n\n \n Usage Notes: The patient, while able to give consent, has not. However, the provider believes that access to masked patient information is justified because of concerns related to the health and safety of one or more third parties. \r\n\n |
| 3 | PurposeOfUse | purpose of use | \n Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. \r\n\n \n Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes. \r\n\n |
| 4 | HMARKT | healthcare marketing | \n To perform one or more operations on information for marketing services and products related to health care. \r\n\n |
| 4 | HOPERAT | healthcare operations | \n To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care. \r\n\n |
| 5 | CAREMGT | care management | \n To perform analytics, evaluation and other secondary uses of treatment and healthcare related information to manage the quality, efficacy, patient safety, population health, and cost effectiveness of healthcare delivery. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment. \r\n\n \n Usage Note: The concept of care management is narrower than the list of activities related to more general organizational objectives such as provider profiling, education of healthcare and non-healthcare professionals; insurance underwriting, premium rating, reinsurance; organizational legal, medical review, auditing, compliance and fraud and abuse detection; business planning, development, and restructuring; fund-raising; and customer service. \r\n\n \n Map: Maps to ISO 14265 Classification Term "Health service management and quality assurance" described as "To inform persons or processes responsible for determining the availability, quality, safety, equity and cost-effectiveness of health care services." \r\n\n There is a semantic gap in concepts. This classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity.\n \r\n\n |
| 5 | DONAT | donation | \n To perform one or more operations on information used for cadaveric organ, eye or tissue donation. \r\n\n |
| 5 | FRAUD | fraud | \n To perform one or more operations on information used for fraud detection and prevention processes. \r\n\n |
| 5 | GOV | government | \n To perform one or more operations on information used within government processes. \r\n\n |
| 5 | HACCRED | health accreditation | \n To perform one or more operations on information for conducting activities related to meeting accreditation criteria. \r\n\n |
| 5 | HCOMPL | health compliance | \n To perform one or more operations on information used for conducting activities required to meet a mandate. \r\n\n |
| 5 | HDECD | decedent | \n To perform one or more operations on information used for handling deceased patient matters. \r\n\n |
| 5 | HDIRECT | directory | \n To perform one or more operation operations on information used to manage a patient directory. \r\n\n \n Examples: \n \r\n\n \n facility\n enterprise\n payer\n health information exchange patient directory\n \n |
| 5 | HDM | healthcare delivery management | \n To perform one or more actions on information used for conducting administrative and contractual activities by or on behalf of organizational entities responsible for delivery of an individual's benefits in a healthcare program, health plan or insurance. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment.\n \r\n\n \n Usage Note: Examples of activities conducted under this purpose of use: provider profiling, risk adjustment, underwriting, fraud and abuse, quality improvement population health and care management. Aligns with HIPAA Operation POU minus coordination of care or other treatment related activities. Similar to the description in SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking. \r\n\n \n Map: Maps to ISO 14265 Classification Term "Administration of care for an individual subject of care" described as "To inform persons or processes responsible for enabling the availability of resources or funding or permissions for providing health care services to the subject of care." \r\n\n However, this classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity. \r\n\n |
| 5 | HLEGAL | legal | \n To perform one or more operations on information for conducting activities required by legal proceeding. \r\n\n |
| 5 | HOUTCOMS | health outcome measure | \n To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions. \r\n\n |
| 5 | HPRGRP | health program reporting | \n To perform one or more operations on information used for conducting activities to meet program accounting requirements. \r\n\n |
| 5 | HQUALIMP | health quality improvement | \n To perform one or more operations on information used for conducting administrative activities to improve health care quality. \r\n\n |
| 5 | HSYSADMIN | health system administration | \n To perform one or more operations on information to administer the electronic systems used for the delivery of health care. \r\n\n |
| 6 | LABELING | labeling | \n To perform one or more operations on information to assign, persist, and manage labels to healthcare data to characterize various aspects, such as its security classification, sensitivity, compartment, integrity, and provenance; applicable privacy, consent, security, provenance, and trust policies; and handling caveats such as purpose of use, obligations, and refrain policies. \r\n\n Label management includes classification of target data by constructing and binding of a label set per applicable policies, security policy information file semantics, and classification guides. Label management also includes process and procedures for subsequent revision of a label for, e.g., reclassification, downgrading classification, and declassification. \r\n\n Label revisions may be triggered by, e.g., expiry of classification period; changes in applicable policy, e.g., revocation of a consent directive; or changes in the governing policy domain in which the data is relocated or a copy of the data is sent. If a label is revised, an audit log should be kept and the provenance of the label changes should be tracked. \r\n\n |
| 6 | METAMGT | metadata management | \n To perform one or more operations on information to assign, persist, and manage metadata to healthcare data to characterize various aspects used for its indexing, discovery, retrieval, and processing by systems, applications, and end users. For example, master index identifier, media type, and location. \r\n\n |
| 5 | MEMADMIN | member administration | \n To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program. \r\n\n |
| 5 | MILCDM | military command | \n To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law. \r\n\n |
| 5 | PATADMIN | patient administration | \n To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient. \r\n\n |
| 5 | PATSFTY | patient safety | \n To perform one or more operations on information in processes related to ensuring the safety of health care. \r\n\n |
| 5 | PERFMSR | performance measure | \n To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions. \r\n\n |
| 5 | RECORDMGT | records management | \n To perform one or more operations on information used within the health records management process. \r\n\n |
| 5 | SYSDEV | system development | \n To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application. \r\n\n |
| 6 | HTEST | test health data | \n To perform one or more operations on information that is simulated or synthetic health data used for testing system capabilities outside of a production or operational system environment. \r\n\n \n Usage Note: Data marked with a HTEST security label enables an access control system to permit interfacing systems or end users provisioned with a clearance, which includes a HTEST purpose of use attribute, to test, verify, or validate that a system or application will operate in production as intended based on design specifications. \r\n\n |
| 5 | TRAIN | training | \n To perform one or more operations on information used in training and education. \r\n\n |
| 4 | HPAYMT | healthcare payment | \n To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care. \r\n\n |
| 5 | CLMATTCH | claim attachment | \n To perform one or more operations on information for provision of additional clinical evidence in support of a request for coverage or payment for health services. \r\n\n |
| 5 | COVAUTH | coverage authorization | \n To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services. \r\n\n |
| 5 | COVERAGE | coverage under policy or program | \n To perform one or more operations on information for conducting activities related to coverage under a program or policy. \r\n\n |
| 6 | ELIGDTRM | eligibility determination | \n To perform one or more operations on information used for conducting eligibility determination for coverage in a program or policy. May entail review of financial status or disability assessment. \r\n\n |
| 6 | ELIGVER | eligibility verification | \n To perform one or more operations on information used for conducting eligibility verification of coverage in a program or policy. May entail provider contacting coverage source (e.g., government health program such as workers compensation or health plan) for confirmation of enrollment, eligibility for specific services, and any applicable copays. \r\n\n |
| 6 | ENROLLM | enrollment | \n To perform one or more operations on information used for enrolling a covered party in a program or policy. May entail recording of covered party's and any dependent's demographic information and benefit choices. \r\n\n |
| 6 | MILDCRG | military discharge | \n To perform one or more operations on information for the process of releasing military personnel from their service obligations, which may include determining service merit, discharge benefits, and disability assessment. \r\n\n |
| 5 | REMITADV | remittance advice | \n To perform one or more operations on information about the amount remitted for a health care claim. \r\n\n |
| 4 | HRESCH | healthcare research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data iincludes basic and applied research such as biomedical, population origin or ancestry, translational research, and disease, discipline, specialty specific healthcare research and clinical trial research. \r\n\n |
| 5 | BIORCH | biomedical research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified biomedical basic or applied research. For example, research on rare plants to determine whether biologic properties may be useful for pharmaceutical development. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 5 | CLINTRCH | clinical trial research | \n To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge. \r\n\n |
| 6 | CLINTRCHNPC | clinical trial research without patient care | \n To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge without provision of patient care. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, a clinical trial conducted on laboratory specimens collected from a specified patient population. \r\n\n |
| 6 | CLINTRCHPC | clinical trial research with patient care | \n To perform one or more operations on information for conducting scientific investigations with patient care in accordance with clinical trial protocols to obtain health care knowledge. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, an "off-label" drug used for cancer therapy administer to a specified patient population. \r\n\n |
| 6 | PRECLINTRCH | preclinical trial research | \n To perform one or more operations on information in preparation for conducting scientific investigation to obtain health care knowledge, such as research on animals or review of patient health records, to determine the feasibility of a clinical trial study; assist with protocol design; or in preparation for institutional review board or ethics committee approval process. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. \r\n\n |
| 5 | DSRCH | disease specific healthcare research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified conditions, diagnosis, or disease healthcare research. For example, conducting cancer research by testing reaction of tumor cells to certain biologics. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 5 | POARCH | population origins or ancestry healthcare research | \n To perform one or more operations on information, including genealogical pedigrees, historical records, surveys, family health data, health records, and genetic information, for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to population origins and/or ancestry healthcare research. For example, gathering genetic specimens from a specific population in order to determine the ancestry and population origins of that group. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 5 | TRANSRCH | translational healthcare research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge related to evidence based medicine during the course of providing healthcare treatment. Sometimes referred to as "bench to bedside", which is the iterative feedback loop between healthcare research and clinical trials with input from information collected in the course of routine provision of healthcare. For example, by extending a patient encounter to conduct a survey related to a research topic such as attitudes about use of a wellness device that a patient agreed to use. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 4 | PATRQT | patient requested | \n To perform one or more operations on information in response to a patient's request. \r\n\n |
| 5 | FAMRQT | family requested | \n To perform one or more operations on information in response to a request by a family member authorized by the patient. \r\n\n |
| 5 | PWATRNY | power of attorney | \n To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative. \r\n\n |
| 5 | SUPNWK | support network | \n To perform one or more operations on information in response to a request by a person authorized by the patient. \r\n\n |
| 4 | PUBHLTH | public health | \n To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions. \r\n\n |
| 5 | DISASTER | disaster | \n To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone. \r\n\n |
| 5 | THREAT | threat | \n To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence. \r\n\n |
| 4 | TREAT | treatment | \n To perform one or more operations on information for provision of health care. \r\n\n |
| 5 | CLINTRL | clinical trial | \n To perform health care as part of the clinical trial protocol. \r\n\n |
| 5 | COC | coordination of care | \n To perform one or more actions on information in order to organize the provision and case management of an individual s healthcare, including: Monitoring a person's goals, needs, and preferences; acting as the communication link between two or more participants concerned with a person's health and wellness; organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person; and ensuring safe, appropriate, non-duplicative, and effective integrated care. \r\n\n \n Usage Note: Use when describing these functions: 1. Monitoring a person s goals, needs, and preferences. 2. Acting as the communication link between two or more participants concerned with a person's health and wellness. 3. Organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person. 4. Ensuring safe, appropriate, non-duplicative, and effective integrated care. \r\n\n The goal is to clearly differentiate this type of coordination of care from HIPAA Operations by specifying that these actions on information are undertaken in the provision of healthcare treatment. \r\n\n For similar uses of this concept, see SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking, which differentiates concepts of care coordination and case management for the provision of treatment as specifically distinct from activities related to health care delivery management and the operations of organizational entities involved in the delivery of healthcare. \r\n\n \n Map: Maps to ISO 14265 Classification Terms: "Support of care activities within the provider organisation for an individual subject of care" described as "To inform persons or processes enabling others to provide health care services to the subject of care." "Subject of Care Uses" described as "To inform the subject of care in support of his or her own interests." \r\n\n |
| 5 | ETREAT | Emergency Treatment | \n To perform one or more operations on information for provision of immediately needed health care for an emergent condition. \r\n\n |
| 6 | BTG | break the glass | \n To perform policy override operations on information for provision of immediately needed health care for an emergent condition affecting potential harm, death or patient safety by end users who are not provisioned for this purpose of use. Includes override of organizational provisioning policies and may include override of subject of care consent directive restricting access. \r\n\n \n Map: Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care."\nThe ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure. \r\n\n |
| 6 | ERTREAT | emergency room treatment | \n To perform one or more operations on information for provision of immediately needed health care for an emergent condition in an emergency room or similar emergent care context by end users provisioned for this purpose, which does not constitute as policy override such as in a "Break the Glass" purpose of use. \r\n\n Map:Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care." \r\n\n The ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure. \r\n\n There is a semantic gap in concepts. This classification term is described as activities to inform persons ? rather than the rationale for performing actions/operations on information related to the activity. \r\n\n |
| 5 | POPHLTH | population health | \n To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program. \r\n\n |
| 2 | (_ActInformationPrivacyReason) Abstract | \n \n Description:The rationale or purpose for an act relating to the management of personal information, such as disclosing personal tax information for the purpose of complying with a court order. \r\n\n | |
| 3 | MARKT | marketing | \n \n Description:\n \r\n\n |
| 3 | OPERAT | operations | \n \n Description:Administrative and contractual processes required to support an activity, product, or service \r\n\n |
| 4 | LEGAL | subpoena | \n \n Definition:To provide information as a result of a subpoena. \r\n\n |
| 4 | ACCRED | accreditation | \n \n Description:Operational activities conducted for the purposes of meeting of criteria defined by an accrediting entity for an activity, product, or service \r\n\n |
| 4 | COMPL | compliance | \n \n Description:Operational activities required to meet a mandate related to an activity, product, or service \r\n\n |
| 4 | ENADMIN | entity administration | \n \n Description:Operational activities conducted to administer information relating to entities involves with an activity, product, or service \r\n\n |
| 4 | OUTCOMS | outcome measure | \n \n Description:Operational activities conducted for the purposes of assessing the results of an activity, product, or service \r\n\n |
| 4 | PRGRPT | program reporting | \n \n Description:Operational activities conducted to meet program accounting requirements related to an activity, product, or service \r\n\n |
| 4 | QUALIMP | quality improvement | \n \n Description:Operational activities conducted for the purposes of improving the quality of an activity, product, or service \r\n\n |
| 4 | SYSADMN | system administration | \n \n Description:Operational activities conducted to administer the electronic systems used for an activity, product, or service \r\n\n |
| 3 | PAYMT | payment | \n \n Description:Administrative, financial, and contractual processes related to payment for an activity, product, or service \r\n\n |
| 3 | RESCH | research | \n \n Description:Investigative activities conducted for the purposes of obtaining knowledge \r\n\n |
| 3 | SRVC | service | \n \n Description:Provision of a service, product, or capability to an individual or organization \r\n\n |
| 1 | _ActInvalidReason | ActInvalidReason | \n \n Description: Types of reasons why a substance is invalid for use. \r\n\n |
| 2 | ADVSTORAGE | adverse storage condition | \n \n Description: Storage conditions caused the substance to be ineffective. \r\n\n |
| 3 | COLDCHNBRK | cold chain break | \n \n Description: Cold chain was not maintained for the substance. \r\n\n |
| 2 | EXPLOT | expired lot | \n \n Description: The lot from which the substance was drawn was expired. \r\n\n |
| 2 | OUTSIDESCHED | administered outside recommended schedule or practice | \n The substance was administered outside of the recommended schedule or practice. \r\n\n |
| 2 | PRODRECALL | product recall | \n \n Description: The substance was recalled by the manufacturer. \r\n\n |
| 1 | (_ActInvoiceCancelReason) Abstract | \n Domain specifies the codes used to describe reasons why a Provider is cancelling an Invoice or Invoice Grouping. \r\n\n | |
| 2 | INCCOVPTY | incorrect covered party as patient | \n The covered party (patient) specified with the Invoice is not correct. \r\n\n |
| 2 | INCINVOICE | incorrect billing | \n The billing information, specified in the Invoice Elements, is not correct. This could include incorrect costing for items included in the Invoice. \r\n\n |
| 2 | INCPOLICY | incorrect policy | \n The policy specified with the Invoice is not correct. For example, it may belong to another Adjudicator or Covered Party. \r\n\n |
| 2 | INCPROV | incorrect provider | \n The provider specified with the Invoice is not correct. \r\n\n |
| 1 | (_ActNoImmunizationReason) Abstract | \n A coded description of the reason for why a patient did not receive a scheduled immunization. \r\n\n (important for public health strategy \r\n\n | |
| 2 | IMMUNE | immunity | \n \n Definition:Testing has shown that the patient already has immunity to the agent targeted by the immunization. \r\n\n |
| 2 | MEDPREC | medical precaution | \n \n Definition:The patient currently has a medical condition for which the vaccine is contraindicated or for which precaution is warranted. \r\n\n |
| 2 | OSTOCK | product out of stock | \n \n Definition:There was no supply of the product on hand to perform the service. \r\n\n |
| 2 | PATOBJ | patient objection | \n \n Definition:The patient or their guardian objects to receiving the vaccine. \r\n\n |
| 2 | PHILISOP | philosophical objection | \n \n Definition:The patient or their guardian objects to receiving the vaccine because of philosophical beliefs. \r\n\n |
| 2 | RELIG | religious objection | \n \n Definition:The patient or their guardian objects to receiving the vaccine on religious grounds. \r\n\n |
| 2 | VACEFF | vaccine efficacy concerns | \n \n Definition:The intended vaccine has expired or is otherwise believed to no longer be effective. \r\n\n \n Example:Due to temperature exposure. \r\n\n |
| 2 | VACSAF | vaccine safety concerns | \n \n Definition:The patient or their guardian objects to receiving the vaccine because of concerns over its safety. \r\n\n |
| 1 | (_ActSupplyFulfillmentRefusalReason) Abstract | \n Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision. E.g. "Suspect fraud", "Possible abuse", "Contraindicated". \r\n\n (used when capturing 'refusal to fill' annotations) \r\n\n | |
| 2 | FRR01 | order stopped | \n \n Definition:The order has been stopped by the prescriber but this fact has not necessarily captured electronically. \r\n\n \n Example:A verbal stop, a fax, etc. \r\n\n |
| 2 | FRR02 | stale-dated order | \n \n Definition:Order has not been fulfilled within a reasonable amount of time, and may not be current. \r\n\n |
| 2 | FRR03 | incomplete data | \n \n Definition:Data needed to safely act on the order which was expected to become available independent of the order is not yet available \r\n\n \n Example:Lab results, diagnostic imaging, etc. \r\n\n |
| 2 | FRR04 | product unavailable | \n \n Definition:Product not available or manufactured. Cannot supply. \r\n\n |
| 2 | FRR05 | ethical/religious | \n \n Definition:The dispenser has ethical, religious or moral objections to fulfilling the order/dispensing the product. \r\n\n |
| 2 | FRR06 | unable to provide care | \n \n Definition:Fulfiller not able to provide appropriate care associated with fulfilling the order. \r\n\n \n Example:Therapy requires ongoing monitoring by fulfiller and fulfiller will be ending practice, leaving town, unable to schedule necessary time, etc. \r\n\n |
| 1 | (_ClinicalResearchEventReason) Abstract | \n \n Definition:Specifies the reason that an event occurred in a clinical research study. \r\n\n | |
| 2 | RET | retest | \n \n Definition:The event occurred so that a test or observation performed at a prior event could be performed again due to conditions set forth in the protocol. \r\n\n |
| 2 | SCH | scheduled | \n \n Definition:The event occurred due to it being scheduled in the research protocol. \r\n\n |
| 2 | TRM | termination | \n \n Definition:The event occurred in order to terminate the subject's participation in the study. \r\n\n |
| 2 | UNS | unscheduled | \n \n Definition:The event that occurred was initiated by a study participant (e.g. the subject or the investigator), and did not occur for protocol reasons. \r\n\n |
| 1 | (_ClinicalResearchObservationReason) Abstract | \n \n Definition:SSpecifies the reason that a test was performed or observation collected in a clinical research study. \r\n\n \n Note:This set of codes are not strictly reasons, but are used in the currently Normative standard. Future revisions of the specification will model these as ActRelationships and thes codes may subsequently be retired. Thus, these codes should not be used for new specifications. \r\n\n | |
| 2 | NPT | non-protocol | \n \n Definition:The observation or test was neither defined or scheduled in the study protocol. \r\n\n |
| 2 | PPT | per protocol | \n \n Definition:The observation or test occurred due to it being defined in the research protocol, and during an activity or event that was scheduled in the protocol. \r\n\n |
| 2 | UPT | per definition | \n \n :The observation or test occurred as defined in the research protocol, but at a point in time not specified in the study protocol. \r\n\n |
| 1 | (_CombinedPharmacyOrderSuspendReasonCode) Abstract | \n \n Description:Indicates why the prescription should be suspended. \r\n\n | |
| 2 | ALTCHOICE | try another treatment first | \n \n Description:This therapy has been ordered as a backup to a preferred therapy. This order will be released when and if the preferred therapy is unsuccessful. \r\n\n |
| 2 | CLARIF | prescription requires clarification | \n \n Description:Clarification is required before the order can be acted upon. \r\n\n |
| 2 | DRUGHIGH | drug level too high | \n \n Description:The current level of the medication in the patient's system is too high. The medication is suspended to allow the level to subside to a safer level. \r\n\n |
| 2 | HOSPADM | admission to hospital | \n \n Description:The patient has been admitted to a care facility and their community medications are suspended until hospital discharge. \r\n\n |
| 2 | LABINT | lab interference issues | \n \n Description:The therapy would interfere with a planned lab test and the therapy is being withdrawn until the test is completed. \r\n\n |
| 2 | NON-AVAIL | patient not-available | \n \n Description:Patient not available for a period of time due to a scheduled therapy, leave of absence or other reason. \r\n\n |
| 2 | PREG | parent is pregnant/breast feeding | \n \n Description:The patient is pregnant or breast feeding. The therapy will be resumed when the pregnancy is complete and the patient is no longer breastfeeding. \r\n\n |
| 2 | SALG | allergy | \n \n Description:The patient is believed to be allergic to a substance that is part of the therapy and the therapy is being temporarily withdrawn to confirm. \r\n\n |
| 2 | SDDI | drug interacts with another drug | \n \n Description:The drug interacts with a short-term treatment that is more urgently required. This order will be resumed when the short-term treatment is complete. \r\n\n |
| 2 | SDUPTHER | duplicate therapy | \n \n Description:Another short-term co-occurring therapy fulfills the same purpose as this therapy. This therapy will be resumed when the co-occuring therapy is complete. \r\n\n |
| 2 | SINTOL | suspected intolerance | \n \n Description:The patient is believed to have an intolerance to a substance that is part of the therapy and the therapy is being temporarily withdrawn to confirm. \r\n\n |
| 2 | SURG | patient scheduled for surgery | \n \n Description:The drug is contraindicated for patients receiving surgery and the patient is scheduled to be admitted for surgery in the near future. The drug will be resumed when the patient has sufficiently recovered from the surgery. \r\n\n |
| 2 | WASHOUT | waiting for old drug to wash out | \n \n Description:The patient was previously receiving a medication contraindicated with the current medication. The current medication will remain on hold until the prior medication has been cleansed from their system. \r\n\n |
| 1 | _ControlActNullificationReasonCode | ControlActNullificationReasonCode | \n \n Description:Identifies reasons for nullifying (retracting) a particular control act. \r\n\n |
| 2 | ALTD | altered decision | \n \n Description:The decision on which the recorded information was based was changed before the decision had an effect. \r\n\n \n Example:Aborted prescription before patient left office, released prescription before suspend took effect. \r\n\n |
| 2 | EIE | entered in error | \n \n Description:The information was recorded incorrectly or was recorded in the wrong record. \r\n\n |
| 2 | NORECMTCH | no record match | \n \n Description: There is no match for the record in the database. \r\n\n |
| 1 | (_ControlActNullificationRefusalReasonType) Abstract | \n \n Description: Reasons to refuse a transaction to be undone. \r\n\n | |
| 2 | INRQSTATE | in requested state | \n The record is already in the requested state. \r\n\n |
| 2 | NOMATCH | no match | \n \n Description: There is no match. \r\n\n |
| 3 | NORECMTCH | ||
| 3 | NOPRODMTCH | no product match | \n \n Description: There is no match for the product in the master file repository. \r\n\n |
| 3 | NOSERMTCH | no service match | \n \n Description: There is no match for the service in the master file repository. \r\n\n |
| 3 | NOVERMTCH | no version match | \n \n Description: There is no match for the record and version. \r\n\n |
| 2 | NOPERM | no permission | \n \n Description: There is no permission. \r\n\n |
| 3 | NOUSERPERM | no user permission | \n \n Definition:The user does not have permission \r\n\n |
| 3 | NOAGNTPERM | no agent permission | \n \n Description: The agent does not have permission. \r\n\n |
| 3 | NOUSRPERM | no user permission | \n \n Description: The user does not have permission. \r\n\n |
| 2 | WRNGVER | wrong version | \n \n Description: The record and version requested to update is not the current version. \r\n\n |
| 1 | (_ControlActReason) Abstract | \n Identifies why a specific query, request, or other trigger event occurred. \r\n\n | |
| 2 | (_MedicationOrderAbortReasonCode) Abstract | \n \n Description:Indicates the reason the medication order should be aborted. \r\n\n | |
| 3 | DISCONT | product discontinued | \n \n Description:The medication is no longer being manufactured or is otherwise no longer available. \r\n\n |
| 3 | INEFFECT | ineffective | \n \n Description:The therapy has been found to not have the desired therapeutic benefit on the patient. \r\n\n |
| 3 | MONIT | response to monitoring | \n \n Description:Monitoring the patient while taking the medication, the decision has been made that the therapy is no longer appropriate. \r\n\n |
| 3 | NOREQ | no longer required for treatment | \n \n Description:The underlying condition has been resolved or has evolved such that a different treatment is no longer needed. \r\n\n |
| 3 | NOTCOVER | not covered | \n \n Description:The product does not have (or no longer has) coverage under the patientaTMs insurance policy. \r\n\n |
| 3 | PREFUS | patient refuse | \n \n Description:The patient refused to take the product. \r\n\n |
| 3 | RECALL | product recalled | \n \n Description:The manufacturer or other agency has requested that stocks of a medication be removed from circulation. \r\n\n |
| 3 | REPLACE | change in order | \n \n Description:Item in current order is no longer in use as requested and a new one has/will be created to replace it. \r\n\n |
| 4 | DOSECHG | change in medication/dose | \n \n Description:The medication is being re-prescribed at a different dosage. \r\n\n |
| 3 | REPLACEFIX | error in order | \n \n Description:Current order was issued with incorrect data and a new order has/will be created to replace it. \r\n\n |
| 3 | UNABLE | unable to use | \n \n Description:<The patient is not (or is no longer) able to use the medication in a manner prescribed. \r\n\n \n Example:CanaTMt swallow. \r\n\n |
| 2 | (_MedicationOrderReleaseReasonCode) Abstract | \n \n Definition:A collection of concepts that indicate why the prescription should be released from suspended state. \r\n\n | |
| 3 | HOLDDONE | suspend reason no longer applies | \n \n Definition:The original reason for suspending the medication has ended. \r\n\n |
| 3 | HOLDINAP | suspend reason inappropriate | \n \n Definition:\n \r\n\n |
| 2 | (_ModifyPrescriptionReasonType) Abstract | \n Types of reason why a prescription is being changed. \r\n\n | |
| 3 | ADMINERROR | administrative error in order | \n Order was created with incorrect data and is changed to reflect the intended accuracy of the order. \r\n\n |
| 3 | CLINMOD | clinical modification | \n Order is changed based on a clinical reason. \r\n\n |
| 2 | _PharmacySupplyEventAbortReason | PharmacySupplyEventAbortReason | \n \n Definition:Identifies why the dispense event was not completed. \r\n\n |
| 3 | CONTRA | contraindication | \n \n Definition:Contraindication identified \r\n\n |
| 3 | FOABORT | order aborted | \n \n Definition:Order to be fulfilled was aborted \r\n\n |
| 3 | FOSUSP | order suspended | \n \n Definition:Order to be fulfilled was suspended \r\n\n |
| 3 | NOPICK | not picked up | \n \n Definition:Patient did not come to get medication \r\n\n |
| 3 | PATDEC | patient changed mind | \n \n Definition:Patient changed their mind regarding obtaining medication \r\n\n |
| 3 | QUANTCHG | change supply quantity | \n \n Definition:Patient requested a revised quantity of medication \r\n\n |
| 2 | (_PharmacySupplyEventStockReasonCode) Abstract | \n \n Definition:A collection of concepts that indicates the reason for a "bulk supply" of medication. \r\n\n | |
| 3 | FLRSTCK | floor stock | \n \n Definition:The bulk supply is issued to replenish a ward for local dispensing. (Includes both mobile and fixed-location ward stocks.) \r\n\n |
| 3 | LTC | long term care use | \n \n Definition:The bulk supply will be administered within a long term care facility. \r\n\n |
| 3 | OFFICE | office use | \n \n Definition:The bulk supply is intended for general clinician office use. \r\n\n |
| 3 | PHARM | pharmacy transfer | \n \n Definition:The bulk supply is being transferred to another dispensing facility to. \r\n\n \n Example:Alleviate a temporary shortage. \r\n\n |
| 3 | PROG | program use | \n \n Definition:The bulk supply is intended for dispensing according to a specific program. \r\n\n \n Example:Mass immunization. \r\n\n |
| 2 | (_PharmacySupplyRequestRenewalRefusalReasonCode) Abstract | \n \n Definition:A collection of concepts that identifies why a renewal prescription has been refused. \r\n\n | |
| 3 | DISCONT | ||
| 3 | ALREADYRX | new prescription exists | \n \n Definition:Patient has already been given a new (renewal) prescription. \r\n\n |
| 3 | FAMPHYS | family physician must authorize further fills | \n \n Definition:Request for further authorization must be done through patient's family physician. \r\n\n |
| 3 | MODIFY | modified prescription exists | \n \n Definition:Therapy has been changed and new prescription issued \r\n\n |
| 3 | NEEDAPMT | patient must make appointment | \n \n Definition:Patient must see prescriber prior to further fills. \r\n\n |
| 3 | NOTAVAIL | prescriber not available | \n \n Definition:Original prescriber is no longer available to prescribe and no other prescriber has taken responsibility for the patient. \r\n\n |
| 3 | NOTPAT | patient no longer in this practice | \n \n Definition:Patient no longer or has never been under this prescribers care. \r\n\n |
| 3 | ONHOLD | medication on hold | \n \n Definition:This medication is on hold. \r\n\n |
| 3 | PRNA | product not available | \n \n Description:This product is not available or manufactured. \r\n\n |
| 3 | STOPMED | prescriber stopped medication for patient | \n Renewing or original prescriber informed patient to stop using the medication. \r\n\n |
| 3 | TOOEARLY | too early | \n \n Definition:The patient should have medication remaining. \r\n\n |
| 2 | (_SupplyOrderAbortReasonCode) Abstract | \n \n Definition:A collection of concepts that indicates why the prescription should no longer be allowed to be dispensed (but can still administer what is already being dispensed). \r\n\n | |
| 3 | IMPROV | condition improved | \n \n Definition:The patient's medical condition has nearly abated. \r\n\n |
| 3 | INTOL | intolerance | \n \n Description:The patient has an intolerance to the medication. \r\n\n |
| 3 | NEWSTR | new strength | \n \n Definition:The current medication will be replaced by a new strength of the same medication. \r\n\n |
| 3 | NEWTHER | new therapy | \n \n Definition:A new therapy will be commenced when current supply exhausted. \r\n\n |
| 1 | (_GenericUpdateReasonCode) Abstract | \n \n Description:Identifies why a change is being made to a record. \r\n\n | |
| 2 | CHGDATA | information change | \n \n Description:Information has changed since the record was created. \r\n\n |
| 2 | FIXDATA | error correction | \n \n Description:Previously recorded information was erroneous and is being corrected. \r\n\n |
| 2 | MDATA | merge data | \n Information is combined into the record. \r\n\n |
| 2 | NEWDATA | new information | \n \n Description:New information has become available to supplement the record. \r\n\n |
| 2 | UMDATA | unmerge data | \n Information is separated from the record. \r\n\n |
| 1 | (_PatientProfileQueryReasonCode) Abstract | \n \n Definition:A collection of concepts identifying why the patient's profile is being queried. \r\n\n | |
| 2 | ADMREV | administrative review | \n \n Definition: To evaluate for service authorization, payment, reporting, or performance/outcome measures. \r\n\n |
| 2 | LEGAL | ||
| 2 | PATCAR | patient care | \n \n Definition:To obtain records as part of patient care. \r\n\n |
| 2 | PATREQ | patient request query | \n \n Definition:Patient requests information from their profile. \r\n\n |
| 2 | PRCREV | practice review | \n \n Definition:To evaluate the provider's current practice for professional-improvement reasons. \r\n\n |
| 2 | REGUL | regulatory review | \n \n Description:Review for the purpose of regulatory compliance. \r\n\n |
| 2 | RSRCH | research | \n \n Definition:To provide research data, as authorized by the patient. \r\n\n |
| 2 | VALIDATION | validation review | \n \n Description:To validate the patient's record. \r\n\n \n Example:Merging or unmerging records. \r\n\n |
| 1 | _PharmacySupplyRequestFulfillerRevisionRefusalReasonCode | PharmacySupplyRequestFulfillerRevisionRefusalReasonCode | \n \n Definition:Indicates why the request to transfer a prescription from one dispensing facility to another has been refused. \r\n\n |
| 2 | LOCKED | locked | \n \n Definition:The prescription may not be reassigned from the original pharmacy. \r\n\n |
| 2 | NOUSERPERM | ||
| 2 | UNKWNTARGET | unknown target | \n \n Definition:The target facility does not recognize the dispensing facility. \r\n\n |
| 1 | (_RefusalReasonCode) Abstract | \n \n Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action. \r\n\n | |
| 2 | NOMATCH | ||
| 2 | NOPERM | ||
| 1 | (_SchedulingActReason) Abstract | \n Reasons for cancelling or rescheduling an Appointment \r\n\n | |
| 2 | PAT | ||
| 2 | BLK | Unexpected Block (of Schedule) | \n The time slots previously allocated are now blocked and no longer available for booking Appointments \r\n\n |
| 2 | DEC | Patient Deceased | \n The Patient is deceased \r\n\n |
| 2 | FIN | No Financial Backing | \n Patient unable to pay and not covered by insurance \r\n\n |
| 2 | MED | Medical Status Altered | \n The medical condition of the Patient has changed \r\n\n |
| 2 | MTG | In an outside meeting | \n The Physician is in a meeting. For example, he/she may request administrative time to talk to family after appointment \r\n\n |
| 2 | PHY | Physician request | \n The Physician requested the action \r\n\n |
| 1 | _StatusRevisionRefusalReasonCode | StatusRevisionRefusalReasonCode | \n Indicates why the act revision (status update) is being refused. \r\n\n |
| 2 | NORECMTCH | ||
| 2 | INRQSTATE | ||
| 2 | NOUSERPERM | ||
| 2 | FILLED | fully filled | \n Ordered quantity has already been completely fulfilled. \r\n\n |
| 1 | _SubstanceAdministrationPermissionRefusalReasonCode | SubstanceAdministrationPermissionRefusalReasonCode | \n \n Definition:Indicates why the requested authorization to prescribe or dispense a medication has been refused. \r\n\n |
| 2 | NOUSERPERM | ||
| 2 | PATINELIG | patient not eligible | \n \n Definition:Patient not eligible for drug \r\n\n |
| 2 | PROTUNMET | protocol not met | \n \n Definition:Patient does not meet required protocol \r\n\n |
| 2 | PROVUNAUTH | provider not authorized | \n \n Definition:Provider is not authorized to prescribe or dispense \r\n\n |
| 1 | (_SubstanceAdminSubstitutionNotAllowedReason) Abstract | \n Reasons why substitution of a substance administration request is not permitted. \r\n\n | |
| 2 | PAT | ||
| 2 | ALGINT | allergy intolerance | \n \n Definition: Patient has had a prior allergic intolerance response to alternate product or one of its components. \r\n\n |
| 2 | COMPCON | compliance concern | \n \n Definition: Patient has compliance issues with medication such as differing appearance, flavor, size, shape or consistency. \r\n\n |
| 2 | THERCHAR | therapeutic characteristics | \n The prescribed product has specific clinical release or other therapeutic characteristics not shared by other substitutable medications. \r\n\n |
| 2 | TRIAL | clinical trial drug | \n \n Definition: The specific manufactured drug is part of a clinical trial. \r\n\n |
| 1 | (_SubstanceAdminSubstitutionReason) Abstract | ||
| 2 | CT | continuing therapy | \n Indicates that the decision to substitute or to not substitute was driven by a desire to maintain consistency with a pre-existing therapy. I.e. The performer provided the same item/service as had been previously provided rather than providing exactly what was ordered, or rather than substituting with a lower-cost equivalent. \r\n\n |
| 2 | FP | formulary policy | \n Indicates that the decision to substitute or to not substitute was driven by a policy expressed within the formulary. \r\n\n |
| 2 | OS | out of stock | \n In the case of 'substitution', indicates that the substitution occurred because the ordered item was not in stock. In the case of 'no substitution', indicates that a cheaper equivalent was not substituted because it was not in stock. \r\n\n |
| 2 | RR | regulatory requirement | \n Indicates that the decision to substitute or to not substitute was driven by a jurisdictional regulatory requirement mandating or prohibiting substitution. \r\n\n |
| 1 | (_TransferActReason) Abstract | \n The explanation for why a patient is moved from one location to another within the organization \r\n\n | |
| 2 | ER | Error | \n Moved to an error in placing the patient in the original location. \r\n\n |
| 2 | RQ | Request | \n Moved at the request of the patient. \r\n\n |
| 1 | (_ActBillableServiceReason) Abstract | \n \n Definition: This domain is used to document reasons for providing a billable service; the billable services may include both clinical services and social services. \r\n\n | |
| 2 | (_ActBillableClinicalServiceReason) Abstract | \n Reason for Clinical Service being performed. \r\n\n This domain excludes reasons specified by diagnosed conditions. \r\n\n Examples of values from this domain include duplicate therapy and fraudulent prescription. \r\n\n | |
| 1 | BONUS | ||
| 1 | CHD | Children only | \n \n Description:The level of coverage under the policy or program is available only to children \r\n\n |
| 1 | DEP | Dependents only | \n \n Description:The level of coverage under the policy or program is available only to a subscriber's dependents. \r\n\n |
| 1 | ECH | Employee and children | \n \n Description:The level of coverage under the policy or program is available to an employee and his or her children. \r\n\n |
| 1 | EDU | ||
| 1 | EMP | Employee only | \n \n Description:The level of coverage under the policy or program is available only to an employee. \r\n\n |
| 1 | ESP | Employee and spouse | \n \n Description:The level of coverage under the policy or program is available to an employee and his or her spouse. \r\n\n |
| 1 | FAM | Family | \n \n Description:The level of coverage under the policy or program is available to a subscriber's family. \r\n\n |
| 1 | IND | Individual | \n \n Description:The level of coverage under the policy or program is available to an individual. \r\n\n |
| 1 | INVOICE | ||
| 1 | PROA | ||
| 1 | RECOV | ||
| 1 | RETRO | ||
| 1 | SPC | Spouse and children | \n \n Description:The level of coverage under the policy or program is available to a subscriber's spouse and children \r\n\n |
| 1 | SPO | Spouse only | \n \n Description:The level of coverage under the policy or program is available only to a subscribers spouse \r\n\n |
| 1 | TRAN |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | I | Intact | \n Reproductively intact \r\n\n |
| 1 | N | Neutered | \n Reproductively neutered \r\n\n |
Supports communication of purpose of use at a general level.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActReason where concept is-a PurposeOfUseRelease Date: 2018-08-12
\r\nAny of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActMood where concept is-a _ActMoodPredicatehttp://terminology.hl7.org/CodeSystem/v3-ActMood| Code | Display | |
| _ActMoodPredicate | ActMoodPredicate | Definition: An act that expresses condition statements for other acts. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nIdentifies the kinds of observations that can be performed
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ObservationTypehttp://loinc.orgTypes of personal relationships between two living subjects. Example:\nParent, sibling, unrelated friend, neighbor
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleCode where concept is-a _PersonalRelationshipRoleTypehttp://terminology.hl7.org/CodeSystem/v3-RoleCode| Code | Display | |
| _PersonalRelationshipRoleType | PersonalRelationshipRoleType | PersonalRelationshipRoleType |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nA physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityClass where concept is-a PLCRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | XMLV1PR1 | XMLV1PR1 | \n XML ITS version 1 pre-release 1. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | A | Ascending | \n Ascending sequence order. \r\n\n |
| 1 | D | Descending | \n Descending sequence order. \r\n\n |
| 1 | N | None | \n No enforced sequence order. \r\n\n |
The described determiner is used to indicate that the given Entity is taken as a general description of a kind of thing that can be taken in whole, in part, or in multiples.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityDeterminer where concept is-a KINDRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | E | Excellent | |
| 1 | F | Fair | |
| 1 | G | Good | |
| 1 | P | Poor |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_AdministrableDrugForm) Abstract | ||
| 2 | APPFUL | Applicatorful | |
| 2 | DROP | Drops | |
| 3 | NDROP | Nasal Drops | |
| 3 | OPDROP | Ophthalmic Drops | |
| 3 | ORDROP | Oral Drops | |
| 3 | OTDROP | Otic Drops | |
| 2 | PUFF | Puff | |
| 2 | SCOOP | Scoops | |
| 2 | SPRY | Sprays | |
| 1 | (_DispensableDrugForm) Abstract | ||
| 2 | (_GasDrugForm) Abstract | \n Any elastic aeriform fluid in which the molecules are separated from one another and have free paths. \r\n\n | |
| 3 | GASINHL | Gas for Inhalation | |
| 2 | (_GasLiquidMixture) Abstract | ||
| 3 | AER | Aerosol | |
| 4 | BAINHL | Breath Activated Inhaler | |
| 4 | INHLSOL | Inhalant Solution | |
| 4 | MDINHL | Metered Dose Inhaler | |
| 4 | NASSPRY | Nasal Spray | |
| 3 | DERMSPRY | Dermal Spray | |
| 3 | FOAM | Foam | |
| 4 | FOAMAPL | Foam with Applicator | |
| 4 | RECFORM | Rectal foam | |
| 4 | VAGFOAM | Vaginal foam | |
| 5 | VAGFOAMAPL | Vaginal foam with applicator | |
| 3 | RECSPRY | Rectal Spray | |
| 3 | VAGSPRY | Vaginal Spray | |
| 2 | (_GasSolidSpray) Abstract | ||
| 3 | INHL | Inhalant | |
| 4 | BAINHLPWD | Breath Activated Powder Inhaler | |
| 4 | INHLPWD | Inhalant Powder | |
| 4 | MDINHLPWD | Metered Dose Powder Inhaler | |
| 4 | NASINHL | Nasal Inhalant | |
| 4 | ORINHL | Oral Inhalant | |
| 3 | PWDSPRY | Powder Spray | |
| 3 | SPRYADAPT | Spray with Adaptor | |
| 2 | (_Liquid) Abstract | \n A state of substance that is an intermediate one entered into as matter goes from solid to gas; liquids are also intermediate in that they have neither the orderliness of a crystal nor the randomness of a gas. (Note: This term should not be used to describe solutions, only pure chemicals in their liquid state.) \r\n\n | |
| 3 | LIQCLN | Liquid Cleanser | |
| 4 | LIQSOAP | Medicated Liquid Soap | |
| 4 | SHMP | Shampoo | \n A liquid soap or detergent used to clean the hair and scalp and is often used as a vehicle for dermatologic agents. \r\n\n |
| 3 | OIL | Oil | \n An unctuous, combustible substance which is liquid, or easily liquefiable, on warming, and is soluble in ether but insoluble in water. Such substances, depending on their origin, are classified as animal, mineral, or vegetable oils. \r\n\n |
| 4 | TOPOIL | Topical Oil | |
| 3 | SOL | Solution | \n A liquid preparation that contains one or more chemical substances dissolved, i.e., molecularly dispersed, in a suitable solvent or mixture of mutually miscible solvents. \r\n\n |
| 4 | DROP | ||
| 4 | IPSOL | Intraperitoneal Solution | |
| 4 | IRSOL | Irrigation Solution | \n A sterile solution intended to bathe or flush open wounds or body cavities; they're used topically, never parenterally. \r\n\n |
| 5 | DOUCHE | Douche | \n A liquid preparation, intended for the irrigative cleansing of the vagina, that is prepared from powders, liquid solutions, or liquid concentrates and contains one or more chemical substances dissolved in a suitable solvent or mutually miscible solvents. \r\n\n |
| 5 | ENEMA | Enema | \n A rectal preparation for therapeutic, diagnostic, or nutritive purposes. \r\n\n |
| 5 | OPIRSOL | Ophthalmic Irrigation Solution | |
| 4 | IVSOL | Intravenous Solution | |
| 4 | ORALSOL | Oral Solution | |
| 5 | ORDROP | ||
| 5 | ELIXIR | Elixir | \n A clear, pleasantly flavored, sweetened hydroalcoholic liquid containing dissolved medicinal agents; it is intended for oral use. \r\n\n |
| 5 | RINSE | Mouthwash/Rinse | \n An aqueous solution which is most often used for its deodorant, refreshing, or antiseptic effect. \r\n\n |
| 5 | SYRUP | Syrup | \n An oral solution containing high concentrations of sucrose or other sugars; the term has also been used to include any other liquid dosage form prepared in a sweet and viscid vehicle, including oral suspensions. \r\n\n |
| 4 | RECSOL | Rectal Solution | |
| 4 | TOPSOL | Topical Solution | |
| 5 | LIN | Liniment | \n A solution or mixture of various substances in oil, alcoholic solutions of soap, or emulsions intended for external application. \r\n\n |
| 5 | MUCTOPSOL | Mucous Membrane Topical Solution | |
| 5 | TINC | Tincture | |
| 2 | (_LiquidLiquidEmulsion) Abstract | \n A two-phase system in which one liquid is dispersed throughout another liquid in the form of small droplets. \r\n\n | |
| 3 | CRM | Cream | \n A semisolid dosage form containing one or more drug substances dissolved or dispersed in a suitable base; more recently, the term has been restricted to products consisting of oil-in-water emulsions or aqueous microcrystalline dispersions of long chain fatty acids or alcohols that are water washable and more cosmetically and aesthetically acceptable. \r\n\n |
| 4 | NASCRM | Nasal Cream | |
| 4 | OPCRM | Ophthalmic Cream | |
| 4 | ORCRM | Oral Cream | |
| 4 | OTCRM | Otic Cream | |
| 4 | RECCRM | Rectal Cream | |
| 4 | TOPCRM | Topical Cream | |
| 4 | VAGCRM | Vaginal Cream | |
| 5 | VAGCRMAPL | Vaginal Cream with Applicator | |
| 3 | LTN | Lotion | \n The term "lotion" has been used to categorize many topical suspensions, solutions and emulsions intended for application to the skin. \r\n\n |
| 4 | TOPLTN | Topical Lotion | |
| 3 | OINT | Ointment | \n A semisolid preparation intended for external application to the skin or mucous membranes. \r\n\n |
| 4 | NASOINT | Nasal Ointment | |
| 4 | OINTAPL | Ointment with Applicator | |
| 4 | OPOINT | Ophthalmic Ointment | |
| 4 | OTOINT | Otic Ointment | |
| 4 | RECOINT | Rectal Ointment | |
| 4 | TOPOINT | Topical Ointment | |
| 4 | VAGOINT | Vaginal Ointment | |
| 5 | VAGOINTAPL | Vaginal Ointment with Applicator | |
| 2 | (_LiquidSolidSuspension) Abstract | \n A liquid preparation which consists of solid particles dispersed throughout a liquid phase in which the particles are not soluble. \r\n\n | |
| 3 | GEL | Gel | \n A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid. \r\n\n |
| 4 | GELAPL | Gel with Applicator | |
| 4 | NASGEL | Nasal Gel | |
| 4 | OPGEL | Ophthalmic Gel | |
| 4 | OTGEL | Otic Gel | |
| 4 | TOPGEL | Topical Gel | |
| 4 | URETHGEL | Urethral Gel | |
| 4 | VAGGEL | Vaginal Gel | |
| 5 | VGELAPL | Vaginal Gel with Applicator | |
| 3 | PASTE | Paste | \n A semisolid dosage form that contains one or more drug substances intended for topical application. \r\n\n |
| 4 | PUD | Pudding | |
| 4 | TPASTE | Toothpaste | \n A paste formulation intended to clean and/or polish the teeth, and which may contain certain additional agents. \r\n\n |
| 3 | SUSP | Suspension | |
| 4 | ITSUSP | Intrathecal Suspension | |
| 4 | OPSUSP | Ophthalmic Suspension | |
| 4 | ORSUSP | Oral Suspension | |
| 5 | ERSUSP | Extended-Release Suspension | |
| 6 | ERSUSP12 | 12 Hour Extended-Release Suspension | |
| 6 | ERSUSP24 | 24 Hour Extended Release Suspension | |
| 4 | OTSUSP | Otic Suspension | |
| 4 | RECSUSP | Rectal Suspension | |
| 2 | (_SolidDrugForm) Abstract | ||
| 3 | BAR | Bar | |
| 4 | BARSOAP | Bar Soap | |
| 5 | MEDBAR | Medicated Bar Soap | |
| 4 | CHEWBAR | Chewable Bar | \n A solid dosage form usually in the form of a rectangle that is meant to be chewed. \r\n\n |
| 3 | BEAD | Beads | \n A solid dosage form in the shape of a small ball. \r\n\n |
| 3 | CAKE | Cake | |
| 3 | CEMENT | Cement | \n A substance that serves to produce solid union between two surfaces. \r\n\n |
| 3 | CRYS | Crystals | \n A naturally produced angular solid of definite form in which the ultimate units from which it is built up are systematically arranged; they are usually evenly spaced on a regular space lattice. \r\n\n |
| 3 | DISK | Disk | \n A circular plate-like organ or structure. \r\n\n |
| 3 | FLAKE | Flakes | |
| 3 | GRAN | Granules | \n A small particle or grain. \r\n\n |
| 3 | GUM | ChewingGum | \n A sweetened and flavored insoluble plastic material of various shapes which when chewed, releases a drug substance into the oral cavity. \r\n\n |
| 3 | PAD | Pad | |
| 4 | MEDPAD | Medicated Pad | |
| 3 | PATCH | Patch | \n A drug delivery system that contains an adhesived backing and that permits its ingredients to diffuse from some portion of it (e.g., the backing itself, a reservoir, the adhesive, or some other component) into the body from the external site where it is applied. \r\n\n |
| 4 | TPATCH | Transdermal Patch | |
| 5 | TPATH16 | 16 Hour Transdermal Patch | |
| 5 | TPATH24 | 24 Hour Transdermal Patch | |
| 5 | TPATH2WK | Biweekly Transdermal Patch | |
| 5 | TPATH72 | 72 Hour Transdermal Patch | |
| 5 | TPATHWK | Weekly Transdermal Patch | |
| 3 | PELLET | Pellet | \n A small sterile solid mass consisting of a highly purified drug (with or without excipients) made by the formation of granules, or by compression and molding. \r\n\n |
| 3 | PILL | Pill | \n A small, round solid dosage form containing a medicinal agent intended for oral administration. \r\n\n |
| 4 | CAP | Capsule | \n A solid dosage form in which the drug is enclosed within either a hard or soft soluble container or "shell" made from a suitable form of gelatin. \r\n\n |
| 5 | ORCAP | Oral Capsule | |
| 6 | ENTCAP | Enteric Coated Capsule | |
| 7 | ERENTCAP | Extended Release Enteric Coated Capsule | |
| 6 | ERCAP | Extended Release Capsule | \n A solid dosage form in which the drug is enclosed within either a hard or soft soluble container made from a suitable form of gelatin, and which releases a drug (or drugs) in such a manner to allow a reduction in dosing frequency as compared to that drug (or drugs) presented as a conventional dosage form. \r\n\n |
| 7 | ERENTCAP | ||
| 7 | ERCAP12 | 12 Hour Extended Release Capsule | |
| 7 | ERCAP24 | 24 Hour Extended Release Capsule | |
| 7 | ERECCAP | Extended Release Enteric Coated Capsule | \n \r\n\n Rationale: Duplicate of code ERENTCAP. Use code ERENTCAP instead. |
| 4 | TAB | Tablet | \n A solid dosage form containing medicinal substances with or without suitable diluents. \r\n\n |
| 5 | ORTAB | Oral Tablet | |
| 6 | BUCTAB | Buccal Tablet | |
| 7 | SRBUCTAB | Sustained Release Buccal Tablet | |
| 6 | CAPLET | Caplet | |
| 6 | CHEWTAB | Chewable Tablet | \n A solid dosage form containing medicinal substances with or without suitable diluents that is intended to be chewed, producing a pleasant tasting residue in the oral cavity that is easily swallowed and does not leave a bitter or unpleasant after-taste. \r\n\n |
| 6 | CPTAB | Coated Particles Tablet | |
| 6 | DISINTAB | Disintegrating Tablet | \n A solid dosage form containing medicinal substances which disintegrates rapidly, usually within a matter of seconds, when placed upon the tongue. \r\n\n |
| 6 | DRTAB | Delayed Release Tablet | |
| 6 | ECTAB | Enteric Coated Tablet | |
| 7 | ERECTAB | Extended Release Enteric Coated Tablet | |
| 6 | ERTAB | Extended Release Tablet | \n A solid dosage form containing a drug which allows at least a reduction in dosing frequency as compared to that drug presented in conventional dosage form. \r\n\n |
| 7 | ERECTAB | ||
| 7 | ERTAB12 | 12 Hour Extended Release Tablet | |
| 7 | ERTAB24 | 24 Hour Extended Release Tablet | |
| 6 | ORTROCHE | Lozenge/Oral Troche | \n A solid preparation containing one or more medicaments, usually in a flavored, sweetened base which is intended to dissolve or disintegrate slowly in the mouth. \r\n\n |
| 6 | SLTAB | Sublingual Tablet | |
| 5 | VAGTAB | Vaginal Tablet | |
| 3 | POWD | Powder | \n An intimate mixture of dry, finely divided drugs and/or chemicals that may be intended for internal or external use. \r\n\n |
| 4 | TOPPWD | Topical Powder | |
| 5 | RECPWD | Rectal Powder | |
| 5 | VAGPWD | Vaginal Powder | |
| 3 | SUPP | Suppository | \n A solid body of various weights and shapes, adapted for introduction into the rectal, vaginal, or urethral orifice of the human body; they usually melt, soften, or dissolve at body temperature. \r\n\n |
| 4 | RECSUPP | Rectal Suppository | |
| 4 | URETHSUPP | Urethral suppository | |
| 4 | VAGSUPP | Vaginal Suppository | |
| 3 | SWAB | Swab | \n A wad of absorbent material usually wound around one end of a small stick and used for applying medication or for removing material from an area. \r\n\n |
| 4 | MEDSWAB | Medicated swab | |
| 3 | WAFER | Wafer | \n A thin slice of material containing a medicinal agent. \r\n\n |
Release Date: 2018-08-12
\r\nCorresponds to the Entity class
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-EntityClass where concept is-a ENTRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | baseline | baseline | |
| 1 | bottom | bottom | |
| 1 | middle | middle | |
| 1 | top | top |
Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-Confidentiality| Code | Display | |
| U | unrestricted | Definition: Privacy metadata indicating that the information is not classified as sensitive. \n \n Examples: Includes publicly available information, e.g., business name, phone, email or physical address. \n \n Usage Note: This metadata indicates that the receiver has no obligation to consider additional policies when making access control decisions. Note that in some jurisdictions, personally identifiable information must be protected as confidential, so it would not be appropriate to assign a confidentiality code of "unrestricted" to that information even if it is publicly available. |
| L | low | Definition: Privacy metadata indicating that the information has been de-identified, and there are mitigating circumstances that prevent re-identification, which minimize risk of harm from unauthorized disclosure. The information requires protection to maintain low sensitivity. \n \n Examples: Includes anonymized, pseudonymized, or non-personally identifiable information such as HIPAA limited data sets. \n \n Map: No clear map to ISO 13606-4 Sensitivity Level (1) Care Management: RECORD_COMPONENTs that might need to be accessed by a wide range of administrative staff to manage the subject of care's access to health services. \n \n Usage Note: This metadata indicates the receiver may have an obligation to comply with a data use agreement. |
| M | moderate | Definition: Privacy metadata indicating moderately sensitive information, which presents moderate risk of harm if disclosed without authorization. \n \n Examples: Includes allergies of non-sensitive nature used inform food service; health information a patient authorizes to be used for marketing, released to a bank for a health credit card or savings account; or information in personal health record systems that are not governed under health privacy laws. \n \n Map: Partial Map to ISO 13606-4 Sensitivity Level (2) Clinical Management: Less sensitive RECORD_COMPONENTs that might need to be accessed by a wider range of personnel not all of whom are actively caring for the patient (e.g. radiology staff). \n \n Usage Note: This metadata indicates that the receiver may be obligated to comply with the receiver's terms of use or privacy policies. |
| N | normal | Definition: Privacy metadata indicating that the information is typical, non-stigmatizing health information, which presents typical risk of harm if disclosed without authorization. \n \n Examples: In the US, this includes what HIPAA identifies as the minimum necessary protected health information (PHI) given a covered purpose of use (treatment, payment, or operations). Includes typical, non-stigmatizing health information disclosed in an application for health, workers compensation, disability, or life insurance. \n \n Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations. \n \n Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable jurisdictional privacy law or disclosure authorization. |
| R | restricted | Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a high risk to the information subject if disclosed without authorization. May be pre-empted by jurisdictional law, e.g., for public health reporting or emergency treatment. \n \n Examples: Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual, e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer. \n \n Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations.. \n \n Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable, prevailing (default) jurisdictional privacy law or disclosure authorization.. |
| V | very restricted | . Privacy metadata indicating that the information is extremely sensitive and likely stigmatizing health information that presents a very high risk if disclosed without authorization. This information must be kept in the highest confidence. \n \n Examples: Includes information about a victim of abuse, patient requested information sensitivity, and taboo subjects relating to health status that must be discussed with the patient by an attending provider before sharing with the patient. May also include information held under legal lock ? or attorney-client privilege \n \n Map: This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject. \n \n Usage Note: This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nSpecifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion| Code | Display | |
| AU | authenticated | A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual. |
| DI | dictated | A completion status in which information has been orally recorded but not yet transcribed. |
| DO | documented | A completion status in which document content, other than dictation, has been received but has not been translated into the final electronic format. Examples include paper documents, whether hand-written or typewritten, and intermediate electronic forms, such as voice to text. |
| LA | legally authenticated | A completion status in which a document has been signed manually or electronically by the individual who is legally responsible for that document. This is the most mature state in the workflow progression. |
| UC | unsigned completed document | A completion status where the document is complete and there is no expectation that the document will be signed. |
Release Date: 2018-08-12
\r\nAn intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActMood where concept is-a INTRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_OrganizationNamePartQualifier) Abstract | ||
| 2 | AC | academic | \n Indicates that a prefix like "Dr." or a suffix like "M.D." or "Ph.D." is an academic title. \r\n\n |
| 2 | AD | adopted | \n The name the person was given at the time of adoption. \r\n\n |
| 2 | BR | birth | \n A name that a person had shortly after being born. Usually for family names but may be used to mark given names at birth that may have changed later. \r\n\n |
| 2 | CL | callme | \n A callme name is (usually a given name) that is preferred when a person is directly addressed. \r\n\n |
| 2 | IN | initial | \n Indicates that a name part is just an initial. Initials do not imply a trailing period since this would not work with non-Latin scripts. Initials may consist of more than one letter, e.g., "Ph." could stand for "Philippe" or "Th." for "Thomas". \r\n\n |
| 2 | LS | Legal status | \n For organizations a suffix indicating the legal status, e.g., "Inc.", "Co.", "AG", "GmbH", "B.V." "S.A.", "Ltd." etc. \r\n\n |
| 2 | NB | nobility | \n In Europe and Asia, there are still people with nobility titles (aristocrats). German "von" is generally a nobility title, not a mere voorvoegsel. Others are "Earl of" or "His Majesty King of..." etc. Rarely used nowadays, but some systems do keep track of this. \r\n\n |
| 2 | PR | professional | \n Primarily in the British Imperial culture people tend to have an abbreviation of their professional organization as part of their credential suffices. \r\n\n |
| 2 | SP | spouse | \n The name assumed from the partner in a marital relationship (hence the "SP"). Usually the spouse's family name. Note that no inference about gender can be made from the existence of spouse names. \r\n\n |
| 2 | TITLE | title | \n Indicates that a prefix or a suffix is a title that applies to the whole name, not just the adjacent name part. \r\n\n |
| 2 | VV | voorvoegsel | \n A Dutch "voorvoegsel" is something like "van" or "de" that might have indicated nobility in the past but no longer so. Similar prefixes exist in other languages such as Spanish, French or Portugese. \r\n\n |
| 1 | (PharmaceuticalEntityNamePartQualifiers) Abstract | \n \n Description: Medication Name Parts are a means of specifying a range of acceptable "official" forms of the name of a product. They are used as patterns against which input name strings may be matched for automatic identification of products from input text reports. While they cover the concepts held under "doseForm" or "route" or "strength" the name parts are not the same and do not fit into a controlled vocabulary in the same way. By specifying up to 8 name parts a much larger range of possible names can be generated. \r\n\n | |
| 2 | CON | container name | \n \n Description: This refers to the container if present in the medicinal product name. \r\n\n EXAMPLES: \r\n\n \n \n For Optaflu suspension for injection in pre-filled syringe Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season): pre-filled syringe \r\n\n \n \n |
| 2 | DEV | device name | \n \n Description: This refers to the qualifiers in the name for devices and is at the moment mainly applicable to insulins and inhalation products. \r\n\n EXAMPLES: \r\n\n \n \n For the medicinal product Actrapid FlexPen 100 IU/ml Solution for injection Subcutaneous use: FlexPen. \r\n\n \n \n |
| 2 | FLAV | FlavorName | \n \n Description: This refers to a flavor of the medicinal product if present in the medicinal product name. \r\n\n \n Examples:\n \r\n\n \n For 'CoughCure Linctus Orange Flavor', the flavor part is "Orange"\n For 'Wonderdrug Syrup Cherry Flavor', the flavor part is "Cherry"\n \n |
| 2 | FORMUL | FormulationPartName | \n \n Description: This refers to the formulation of the medicinal product if present in the medicinal product name. \r\n\n \n Examples:\n \r\n\n \n For 'SpecialMed Sugar Free Cough Syrup', the formulation name part is "Sugar Free"\n For 'QuickCure Gluten-free Bulk Fibre', the formulation name part is "gluten-free"\n \n |
| 2 | FRM | form name | \n \n Description: This refers to the pharmaceutical form/ if present in the medicinal product name. \r\n\n EXAMPLES: \r\n\n \n \n For Agenerase 50 mg soft capsules: Soft Capsules \r\n\n \n \n For Ludiomil 25mg-Filmtabletten: Filmtabletten \r\n\n \n \n For Optaflu suspension for injection in pre-filled syringe Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season): suspension for injection \r\n\n \n \n |
| 2 | INV | invented name | \n \n Description: This refers to the product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name and, if appropriate, whether it is intended e.g. for babies, children or adults. \r\n\n EXAMPLES: \r\n\n \n \n Agenerase \r\n\n \n \n Optaflu \r\n\n \n \n Ludiomil \r\n\n \n \n |
| 2 | POPUL | TargetPopulationName | \n \n Description: This refers to the target population for the medicinal product if present in the medicinal product name \r\n\n \n Examples:\n \r\n\n \n For 'Broncho-Drug 3.5 mg-capsules for children', the target population part is "children"\n For 'Adult Chesty Cough Syrup', the target population part is "adult"\n \n |
| 2 | SCI | scientific name | \n \n Description: This refers to the product common or scientific name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name. \r\n\n EXAMPLES: \r\n\n \n \n For Agenerase: N/A \r\n\n \n \n For Optaflu: Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season) \r\n\n \n \n For Ludiomil: N/A \r\n\n \n \n |
| 2 | STR | strength name | \n \n Description: This refers to the strength if present in the medicinal product name. The use of decimal points should be accommodated if required. \r\n\n EXAMPLES: \r\n\n \n \n For Agenerase 50 mg soft capsules: 50mg \r\n\n \n \n For Ludiomil 25mg-Filmtabletten: 25 mg \r\n\n \n \n For Optaflu suspension for injection in pre-filled syringe Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season): N/A \r\n\n \n \n |
| 2 | TIME | TimeOrPeriodName | \n \n Description: This refers to a time or time period that may be specified in the text of the medicinal product name \r\n\n \n Example:\n \r\n\n \n For an influenza vaccine 'Drug-FLU season 2008/2009', the time/period part is "2008/2009 season"\n \n |
| 2 | TMK | trademark name | \n \n Description: This refers to trademark/company element if present in the medicinal product name. \r\n\n EXAMPLES: \r\n\n \n \n for Insulin Human Winthrop Comb 15: Winthrop \r\n\n \n \n |
| 2 | USE | intended use name | \n \n Description: This refers to the intended use if present in the medicinal product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.\n \r\n\n \n Examples:\n \r\n\n \n For 'Drug-BI Caplets - Heartburn Relief', the intended use part is: "Heartburn Relief"\n For 'Medicine Honey Syrup for Soothing Coughs' the intended use part is "Soothing Coughs"\n \n |
| 1 | (_PersonNamePartQualifier) Abstract | ||
| 2 | IN | ||
| 2 | TITLE | ||
| 2 | (_PersonNamePartAffixTypes) Abstract | ||
| 3 | AC | ||
| 3 | NB | ||
| 3 | PR | ||
| 3 | VV | ||
| 2 | (_PersonNamePartChangeQualifier) Abstract | ||
| 3 | AD | ||
| 3 | BR | ||
| 3 | SP | ||
| 2 | (_PersonNamePartMiscQualifier) Abstract | ||
| 3 | CL |
Release Date: 2018-08-12
\r\nDefinition:\nSet of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActCoverageTypeCodeDefinition:\nThe type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActConsentTypeCorresponds to the Role class
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a ROLAn association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a _RoleClassPassivehttp://terminology.hl7.org/CodeSystem/v3-RoleClass| Code | Display | |
| _RoleClassPassive | RoleClassPassive | An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity. |
ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _ActConsentDirectiveTarget that is substantially present in the service and which is directly affected by the service action (includes consumed material, devices, etc.).
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ParticipationType where concept is-a DIRThis is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a PERTRelease Date: 2018-08-12
\r\nSupply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a SPLYRelease Date: 2018-08-12
\r\nTypes of security policies that further specify the ActClassPolicy value set. Examples:\nencrypt prohibit redisclosure without consent directive
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a SecurityPolicyA relationship between two entities that is formally recognized, frequently by a contract or similar agreement.
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-RoleClass where concept is-a _RoleClassRelationshipFormalhttp://terminology.hl7.org/CodeSystem/v3-RoleClass| Code | Display | |
| _RoleClassRelationshipFormal | RoleClassRelationshipFormal | A relationship between two entities that is formally recognized, frequently by a contract or similar agreement. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nSpecifies the state change of a target Act, using ActStatus codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".
\nThis value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/v3-ActStatus| Code | Display | |
| aborted | aborted | The Act has been terminated prior to the originally intended completion. |
| cancelled | cancelled | The Act has been abandoned before activation. |
| completed | completed | An Act that has terminated normally after all of its constituents have been performed. |
| new | new | An Act that is in the preparatory stages and may not yet be acted upon |
| nullified | nullified | This Act instance was created in error and has been 'removed' and is treated as though it never existed. A record is retained for audit purposes only. |
| obsolete | obsolete | This Act instance has been replaced by a new instance. |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | ESGN | Expressed signed | |
| 1 | ESP | Expressed spoken | |
| 1 | EWR | Expressed written | |
| 1 | RSGN | Received signed | |
| 1 | RSP | Received spoken | |
| 1 | RWR | Received written |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | GEL | Gel | \n A gelatinous type of separator material. \r\n\n |
| 1 | NONE | None | \n No separator material is present in the container. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | M | Modified subscription | \n Modified subscription to a query server. \r\n\n |
| 1 | N | New subscription | \n New subscription to a query server. \r\n\n |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_AdministrableDrugForm) Abstract | ||
| 2 | APPFUL | Applicatorful | |
| 2 | DROP | Drops | |
| 3 | NDROP | Nasal Drops | |
| 3 | OPDROP | Ophthalmic Drops | |
| 3 | ORDROP | Oral Drops | |
| 3 | OTDROP | Otic Drops | |
| 2 | PUFF | Puff | |
| 2 | SCOOP | Scoops | |
| 2 | SPRY | Sprays | |
| 1 | (_DispensableDrugForm) Abstract | ||
| 2 | (_GasDrugForm) Abstract | \n Any elastic aeriform fluid in which the molecules are separated from one another and have free paths. \r\n\n | |
| 3 | GASINHL | Gas for Inhalation | |
| 2 | (_GasLiquidMixture) Abstract | ||
| 3 | AER | Aerosol | |
| 4 | BAINHL | Breath Activated Inhaler | |
| 4 | INHLSOL | Inhalant Solution | |
| 4 | MDINHL | Metered Dose Inhaler | |
| 4 | NASSPRY | Nasal Spray | |
| 3 | DERMSPRY | Dermal Spray | |
| 3 | FOAM | Foam | |
| 4 | FOAMAPL | Foam with Applicator | |
| 4 | RECFORM | Rectal foam | |
| 4 | VAGFOAM | Vaginal foam | |
| 5 | VAGFOAMAPL | Vaginal foam with applicator | |
| 3 | RECSPRY | Rectal Spray | |
| 3 | VAGSPRY | Vaginal Spray | |
| 2 | (_GasSolidSpray) Abstract | ||
| 3 | INHL | Inhalant | |
| 4 | BAINHLPWD | Breath Activated Powder Inhaler | |
| 4 | INHLPWD | Inhalant Powder | |
| 4 | MDINHLPWD | Metered Dose Powder Inhaler | |
| 4 | NASINHL | Nasal Inhalant | |
| 4 | ORINHL | Oral Inhalant | |
| 3 | PWDSPRY | Powder Spray | |
| 3 | SPRYADAPT | Spray with Adaptor | |
| 2 | (_Liquid) Abstract | \n A state of substance that is an intermediate one entered into as matter goes from solid to gas; liquids are also intermediate in that they have neither the orderliness of a crystal nor the randomness of a gas. (Note: This term should not be used to describe solutions, only pure chemicals in their liquid state.) \r\n\n | |
| 3 | LIQCLN | Liquid Cleanser | |
| 4 | LIQSOAP | Medicated Liquid Soap | |
| 4 | SHMP | Shampoo | \n A liquid soap or detergent used to clean the hair and scalp and is often used as a vehicle for dermatologic agents. \r\n\n |
| 3 | OIL | Oil | \n An unctuous, combustible substance which is liquid, or easily liquefiable, on warming, and is soluble in ether but insoluble in water. Such substances, depending on their origin, are classified as animal, mineral, or vegetable oils. \r\n\n |
| 4 | TOPOIL | Topical Oil | |
| 3 | SOL | Solution | \n A liquid preparation that contains one or more chemical substances dissolved, i.e., molecularly dispersed, in a suitable solvent or mixture of mutually miscible solvents. \r\n\n |
| 4 | DROP | ||
| 4 | IPSOL | Intraperitoneal Solution | |
| 4 | IRSOL | Irrigation Solution | \n A sterile solution intended to bathe or flush open wounds or body cavities; they're used topically, never parenterally. \r\n\n |
| 5 | DOUCHE | Douche | \n A liquid preparation, intended for the irrigative cleansing of the vagina, that is prepared from powders, liquid solutions, or liquid concentrates and contains one or more chemical substances dissolved in a suitable solvent or mutually miscible solvents. \r\n\n |
| 5 | ENEMA | Enema | \n A rectal preparation for therapeutic, diagnostic, or nutritive purposes. \r\n\n |
| 5 | OPIRSOL | Ophthalmic Irrigation Solution | |
| 4 | IVSOL | Intravenous Solution | |
| 4 | ORALSOL | Oral Solution | |
| 5 | ORDROP | ||
| 5 | ELIXIR | Elixir | \n A clear, pleasantly flavored, sweetened hydroalcoholic liquid containing dissolved medicinal agents; it is intended for oral use. \r\n\n |
| 5 | RINSE | Mouthwash/Rinse | \n An aqueous solution which is most often used for its deodorant, refreshing, or antiseptic effect. \r\n\n |
| 5 | SYRUP | Syrup | \n An oral solution containing high concentrations of sucrose or other sugars; the term has also been used to include any other liquid dosage form prepared in a sweet and viscid vehicle, including oral suspensions. \r\n\n |
| 4 | RECSOL | Rectal Solution | |
| 4 | TOPSOL | Topical Solution | |
| 5 | LIN | Liniment | \n A solution or mixture of various substances in oil, alcoholic solutions of soap, or emulsions intended for external application. \r\n\n |
| 5 | MUCTOPSOL | Mucous Membrane Topical Solution | |
| 5 | TINC | Tincture | |
| 2 | (_LiquidLiquidEmulsion) Abstract | \n A two-phase system in which one liquid is dispersed throughout another liquid in the form of small droplets. \r\n\n | |
| 3 | CRM | Cream | \n A semisolid dosage form containing one or more drug substances dissolved or dispersed in a suitable base; more recently, the term has been restricted to products consisting of oil-in-water emulsions or aqueous microcrystalline dispersions of long chain fatty acids or alcohols that are water washable and more cosmetically and aesthetically acceptable. \r\n\n |
| 4 | NASCRM | Nasal Cream | |
| 4 | OPCRM | Ophthalmic Cream | |
| 4 | ORCRM | Oral Cream | |
| 4 | OTCRM | Otic Cream | |
| 4 | RECCRM | Rectal Cream | |
| 4 | TOPCRM | Topical Cream | |
| 4 | VAGCRM | Vaginal Cream | |
| 5 | VAGCRMAPL | Vaginal Cream with Applicator | |
| 3 | LTN | Lotion | \n The term "lotion" has been used to categorize many topical suspensions, solutions and emulsions intended for application to the skin. \r\n\n |
| 4 | TOPLTN | Topical Lotion | |
| 3 | OINT | Ointment | \n A semisolid preparation intended for external application to the skin or mucous membranes. \r\n\n |
| 4 | NASOINT | Nasal Ointment | |
| 4 | OINTAPL | Ointment with Applicator | |
| 4 | OPOINT | Ophthalmic Ointment | |
| 4 | OTOINT | Otic Ointment | |
| 4 | RECOINT | Rectal Ointment | |
| 4 | TOPOINT | Topical Ointment | |
| 4 | VAGOINT | Vaginal Ointment | |
| 5 | VAGOINTAPL | Vaginal Ointment with Applicator | |
| 2 | (_LiquidSolidSuspension) Abstract | \n A liquid preparation which consists of solid particles dispersed throughout a liquid phase in which the particles are not soluble. \r\n\n | |
| 3 | GEL | Gel | \n A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid. \r\n\n |
| 4 | GELAPL | Gel with Applicator | |
| 4 | NASGEL | Nasal Gel | |
| 4 | OPGEL | Ophthalmic Gel | |
| 4 | OTGEL | Otic Gel | |
| 4 | TOPGEL | Topical Gel | |
| 4 | URETHGEL | Urethral Gel | |
| 4 | VAGGEL | Vaginal Gel | |
| 5 | VGELAPL | Vaginal Gel with Applicator | |
| 3 | PASTE | Paste | \n A semisolid dosage form that contains one or more drug substances intended for topical application. \r\n\n |
| 4 | PUD | Pudding | |
| 4 | TPASTE | Toothpaste | \n A paste formulation intended to clean and/or polish the teeth, and which may contain certain additional agents. \r\n\n |
| 3 | SUSP | Suspension | |
| 4 | ITSUSP | Intrathecal Suspension | |
| 4 | OPSUSP | Ophthalmic Suspension | |
| 4 | ORSUSP | Oral Suspension | |
| 5 | ERSUSP | Extended-Release Suspension | |
| 6 | ERSUSP12 | 12 Hour Extended-Release Suspension | |
| 6 | ERSUSP24 | 24 Hour Extended Release Suspension | |
| 4 | OTSUSP | Otic Suspension | |
| 4 | RECSUSP | Rectal Suspension | |
| 2 | (_SolidDrugForm) Abstract | ||
| 3 | BAR | Bar | |
| 4 | BARSOAP | Bar Soap | |
| 5 | MEDBAR | Medicated Bar Soap | |
| 4 | CHEWBAR | Chewable Bar | \n A solid dosage form usually in the form of a rectangle that is meant to be chewed. \r\n\n |
| 3 | BEAD | Beads | \n A solid dosage form in the shape of a small ball. \r\n\n |
| 3 | CAKE | Cake | |
| 3 | CEMENT | Cement | \n A substance that serves to produce solid union between two surfaces. \r\n\n |
| 3 | CRYS | Crystals | \n A naturally produced angular solid of definite form in which the ultimate units from which it is built up are systematically arranged; they are usually evenly spaced on a regular space lattice. \r\n\n |
| 3 | DISK | Disk | \n A circular plate-like organ or structure. \r\n\n |
| 3 | FLAKE | Flakes | |
| 3 | GRAN | Granules | \n A small particle or grain. \r\n\n |
| 3 | GUM | ChewingGum | \n A sweetened and flavored insoluble plastic material of various shapes which when chewed, releases a drug substance into the oral cavity. \r\n\n |
| 3 | PAD | Pad | |
| 4 | MEDPAD | Medicated Pad | |
| 3 | PATCH | Patch | \n A drug delivery system that contains an adhesived backing and that permits its ingredients to diffuse from some portion of it (e.g., the backing itself, a reservoir, the adhesive, or some other component) into the body from the external site where it is applied. \r\n\n |
| 4 | TPATCH | Transdermal Patch | |
| 5 | TPATH16 | 16 Hour Transdermal Patch | |
| 5 | TPATH24 | 24 Hour Transdermal Patch | |
| 5 | TPATH2WK | Biweekly Transdermal Patch | |
| 5 | TPATH72 | 72 Hour Transdermal Patch | |
| 5 | TPATHWK | Weekly Transdermal Patch | |
| 3 | PELLET | Pellet | \n A small sterile solid mass consisting of a highly purified drug (with or without excipients) made by the formation of granules, or by compression and molding. \r\n\n |
| 3 | PILL | Pill | \n A small, round solid dosage form containing a medicinal agent intended for oral administration. \r\n\n |
| 4 | CAP | Capsule | \n A solid dosage form in which the drug is enclosed within either a hard or soft soluble container or "shell" made from a suitable form of gelatin. \r\n\n |
| 5 | ORCAP | Oral Capsule | |
| 6 | ENTCAP | Enteric Coated Capsule | |
| 7 | ERENTCAP | Extended Release Enteric Coated Capsule | |
| 6 | ERCAP | Extended Release Capsule | \n A solid dosage form in which the drug is enclosed within either a hard or soft soluble container made from a suitable form of gelatin, and which releases a drug (or drugs) in such a manner to allow a reduction in dosing frequency as compared to that drug (or drugs) presented as a conventional dosage form. \r\n\n |
| 7 | ERENTCAP | ||
| 7 | ERCAP12 | 12 Hour Extended Release Capsule | |
| 7 | ERCAP24 | 24 Hour Extended Release Capsule | |
| 7 | ERECCAP | Extended Release Enteric Coated Capsule | \n \r\n\n Rationale: Duplicate of code ERENTCAP. Use code ERENTCAP instead. |
| 4 | TAB | Tablet | \n A solid dosage form containing medicinal substances with or without suitable diluents. \r\n\n |
| 5 | ORTAB | Oral Tablet | |
| 6 | BUCTAB | Buccal Tablet | |
| 7 | SRBUCTAB | Sustained Release Buccal Tablet | |
| 6 | CAPLET | Caplet | |
| 6 | CHEWTAB | Chewable Tablet | \n A solid dosage form containing medicinal substances with or without suitable diluents that is intended to be chewed, producing a pleasant tasting residue in the oral cavity that is easily swallowed and does not leave a bitter or unpleasant after-taste. \r\n\n |
| 6 | CPTAB | Coated Particles Tablet | |
| 6 | DISINTAB | Disintegrating Tablet | \n A solid dosage form containing medicinal substances which disintegrates rapidly, usually within a matter of seconds, when placed upon the tongue. \r\n\n |
| 6 | DRTAB | Delayed Release Tablet | |
| 6 | ECTAB | Enteric Coated Tablet | |
| 7 | ERECTAB | Extended Release Enteric Coated Tablet | |
| 6 | ERTAB | Extended Release Tablet | \n A solid dosage form containing a drug which allows at least a reduction in dosing frequency as compared to that drug presented in conventional dosage form. \r\n\n |
| 7 | ERECTAB | ||
| 7 | ERTAB12 | 12 Hour Extended Release Tablet | |
| 7 | ERTAB24 | 24 Hour Extended Release Tablet | |
| 6 | ORTROCHE | Lozenge/Oral Troche | \n A solid preparation containing one or more medicaments, usually in a flavored, sweetened base which is intended to dissolve or disintegrate slowly in the mouth. \r\n\n |
| 6 | SLTAB | Sublingual Tablet | |
| 5 | VAGTAB | Vaginal Tablet | |
| 3 | POWD | Powder | \n An intimate mixture of dry, finely divided drugs and/or chemicals that may be intended for internal or external use. \r\n\n |
| 4 | TOPPWD | Topical Powder | |
| 5 | RECPWD | Rectal Powder | |
| 5 | VAGPWD | Vaginal Powder | |
| 3 | SUPP | Suppository | \n A solid body of various weights and shapes, adapted for introduction into the rectal, vaginal, or urethral orifice of the human body; they usually melt, soften, or dissolve at body temperature. \r\n\n |
| 4 | RECSUPP | Rectal Suppository | |
| 4 | URETHSUPP | Urethral suppository | |
| 4 | VAGSUPP | Vaginal Suppository | |
| 3 | SWAB | Swab | \n A wad of absorbent material usually wound around one end of a small stick and used for applying medication or for removing material from an area. \r\n\n |
| 4 | MEDSWAB | Medicated swab | |
| 3 | WAFER | Wafer | \n A thin slice of material containing a medicinal agent. \r\n\n |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_OrganizationNamePartQualifier) Abstract | ||
| 2 | AC | academic | \n Indicates that a prefix like "Dr." or a suffix like "M.D." or "Ph.D." is an academic title. \r\n\n |
| 2 | AD | adopted | \n The name the person was given at the time of adoption. \r\n\n |
| 2 | BR | birth | \n A name that a person had shortly after being born. Usually for family names but may be used to mark given names at birth that may have changed later. \r\n\n |
| 2 | CL | callme | \n A callme name is (usually a given name) that is preferred when a person is directly addressed. \r\n\n |
| 2 | IN | initial | \n Indicates that a name part is just an initial. Initials do not imply a trailing period since this would not work with non-Latin scripts. Initials may consist of more than one letter, e.g., "Ph." could stand for "Philippe" or "Th." for "Thomas". \r\n\n |
| 2 | LS | Legal status | \n For organizations a suffix indicating the legal status, e.g., "Inc.", "Co.", "AG", "GmbH", "B.V." "S.A.", "Ltd." etc. \r\n\n |
| 2 | NB | nobility | \n In Europe and Asia, there are still people with nobility titles (aristocrats). German "von" is generally a nobility title, not a mere voorvoegsel. Others are "Earl of" or "His Majesty King of..." etc. Rarely used nowadays, but some systems do keep track of this. \r\n\n |
| 2 | PR | professional | \n Primarily in the British Imperial culture people tend to have an abbreviation of their professional organization as part of their credential suffices. \r\n\n |
| 2 | SP | spouse | \n The name assumed from the partner in a marital relationship (hence the "SP"). Usually the spouse's family name. Note that no inference about gender can be made from the existence of spouse names. \r\n\n |
| 2 | TITLE | title | \n Indicates that a prefix or a suffix is a title that applies to the whole name, not just the adjacent name part. \r\n\n |
| 2 | VV | voorvoegsel | \n A Dutch "voorvoegsel" is something like "van" or "de" that might have indicated nobility in the past but no longer so. Similar prefixes exist in other languages such as Spanish, French or Portugese. \r\n\n |
| 1 | (PharmaceuticalEntityNamePartQualifiers) Abstract | \n \n Description: Medication Name Parts are a means of specifying a range of acceptable "official" forms of the name of a product. They are used as patterns against which input name strings may be matched for automatic identification of products from input text reports. While they cover the concepts held under "doseForm" or "route" or "strength" the name parts are not the same and do not fit into a controlled vocabulary in the same way. By specifying up to 8 name parts a much larger range of possible names can be generated. \r\n\n | |
| 2 | CON | container name | \n \n Description: This refers to the container if present in the medicinal product name. \r\n\n EXAMPLES: \r\n\n \n \n For Optaflu suspension for injection in pre-filled syringe Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season): pre-filled syringe \r\n\n \n \n |
| 2 | DEV | device name | \n \n Description: This refers to the qualifiers in the name for devices and is at the moment mainly applicable to insulins and inhalation products. \r\n\n EXAMPLES: \r\n\n \n \n For the medicinal product Actrapid FlexPen 100 IU/ml Solution for injection Subcutaneous use: FlexPen. \r\n\n \n \n |
| 2 | FLAV | FlavorName | \n \n Description: This refers to a flavor of the medicinal product if present in the medicinal product name. \r\n\n \n Examples:\n \r\n\n \n For 'CoughCure Linctus Orange Flavor', the flavor part is "Orange"\n For 'Wonderdrug Syrup Cherry Flavor', the flavor part is "Cherry"\n \n |
| 2 | FORMUL | FormulationPartName | \n \n Description: This refers to the formulation of the medicinal product if present in the medicinal product name. \r\n\n \n Examples:\n \r\n\n \n For 'SpecialMed Sugar Free Cough Syrup', the formulation name part is "Sugar Free"\n For 'QuickCure Gluten-free Bulk Fibre', the formulation name part is "gluten-free"\n \n |
| 2 | FRM | form name | \n \n Description: This refers to the pharmaceutical form/ if present in the medicinal product name. \r\n\n EXAMPLES: \r\n\n \n \n For Agenerase 50 mg soft capsules: Soft Capsules \r\n\n \n \n For Ludiomil 25mg-Filmtabletten: Filmtabletten \r\n\n \n \n For Optaflu suspension for injection in pre-filled syringe Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season): suspension for injection \r\n\n \n \n |
| 2 | INV | invented name | \n \n Description: This refers to the product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name and, if appropriate, whether it is intended e.g. for babies, children or adults. \r\n\n EXAMPLES: \r\n\n \n \n Agenerase \r\n\n \n \n Optaflu \r\n\n \n \n Ludiomil \r\n\n \n \n |
| 2 | POPUL | TargetPopulationName | \n \n Description: This refers to the target population for the medicinal product if present in the medicinal product name \r\n\n \n Examples:\n \r\n\n \n For 'Broncho-Drug 3.5 mg-capsules for children', the target population part is "children"\n For 'Adult Chesty Cough Syrup', the target population part is "adult"\n \n |
| 2 | SCI | scientific name | \n \n Description: This refers to the product common or scientific name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name. \r\n\n EXAMPLES: \r\n\n \n \n For Agenerase: N/A \r\n\n \n \n For Optaflu: Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season) \r\n\n \n \n For Ludiomil: N/A \r\n\n \n \n |
| 2 | STR | strength name | \n \n Description: This refers to the strength if present in the medicinal product name. The use of decimal points should be accommodated if required. \r\n\n EXAMPLES: \r\n\n \n \n For Agenerase 50 mg soft capsules: 50mg \r\n\n \n \n For Ludiomil 25mg-Filmtabletten: 25 mg \r\n\n \n \n For Optaflu suspension for injection in pre-filled syringe Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season): N/A \r\n\n \n \n |
| 2 | TIME | TimeOrPeriodName | \n \n Description: This refers to a time or time period that may be specified in the text of the medicinal product name \r\n\n \n Example:\n \r\n\n \n For an influenza vaccine 'Drug-FLU season 2008/2009', the time/period part is "2008/2009 season"\n \n |
| 2 | TMK | trademark name | \n \n Description: This refers to trademark/company element if present in the medicinal product name. \r\n\n EXAMPLES: \r\n\n \n \n for Insulin Human Winthrop Comb 15: Winthrop \r\n\n \n \n |
| 2 | USE | intended use name | \n \n Description: This refers to the intended use if present in the medicinal product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.\n \r\n\n \n Examples:\n \r\n\n \n For 'Drug-BI Caplets - Heartburn Relief', the intended use part is: "Heartburn Relief"\n For 'Medicine Honey Syrup for Soothing Coughs' the intended use part is "Soothing Coughs"\n \n |
| 1 | (_PersonNamePartQualifier) Abstract | ||
| 2 | IN | ||
| 2 | TITLE | ||
| 2 | (_PersonNamePartAffixTypes) Abstract | ||
| 3 | AC | ||
| 3 | NB | ||
| 3 | PR | ||
| 3 | VV | ||
| 2 | (_PersonNamePartChangeQualifier) Abstract | ||
| 3 | AD | ||
| 3 | BR | ||
| 3 | SP | ||
| 2 | (_PersonNamePartMiscQualifier) Abstract | ||
| 3 | CL |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | SEQL | sequence | \n \n Description:A transmission relationship indicating that the source transmission follows the target transmission. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_ActAccommodationReason) Abstract | \n Identifies the reason the patient is assigned to this accommodation type \r\n\n | |
| 2 | ACCREQNA | Accommodation Requested Not Available | \n Accommodation requested is not available. \r\n\n |
| 2 | FLRCNV | Floor Convenience | \n Accommodation is assigned for floor convenience. \r\n\n |
| 2 | MEDNEC | Medical Necessity | \n Required for medical reasons(s). \r\n\n |
| 2 | PAT | Patient request | \n The Patient requested the action \r\n\n |
| 1 | (_ActCoverageReason) Abstract | \n \n Description:Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties. \r\n\n | |
| 2 | (_EligibilityActReasonCode) Abstract | \n Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. \r\n\n \n Examples: A person is a claimant under an automobile insurance policy are client deceased & adopted client has been given a new policy identifier. A new employee is eligible for health insurance as an employment benefit. A person meets a government program eligibility criteria for financial, age or health status. \r\n\n | |
| 3 | (_ActIneligibilityReason) Abstract | \n Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy. \r\n\n Examples are client deceased & adopted client has been given a new policy identifier. \r\n\n | |
| 4 | COVSUS | coverage suspended | \n When a client has no contact with the health system for an extended period, coverage is suspended. Client will be reinstated to original start date upon proof of identification, residency etc. \r\n\n Example: Coverage may be suspended during a strike situation, when employer benefits for employees are not covered (i.e. not in effect). \r\n\n |
| 4 | DECSD | deceased | \n Client deceased. \r\n\n |
| 4 | REGERR | registered in error | \n Client was registered in error. \r\n\n |
| 3 | (_CoverageEligibilityReason) Abstract | \n Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. \r\n\n \n Examples: A person is a claimant under an automobile insurance policy are client deceased & adopted client has been given a new policy identifier. A new employee is eligible for health insurance as an employment benefit. A person meets a government program eligibility criteria for financial, age or health status. \r\n\n | |
| 4 | AGE | age eligibility | \n A person becomes eligible for a program based on age. \r\n\n \n Example: In the U.S., a person who is 65 years of age or older is eligible for Medicare. \r\n\n |
| 4 | CRIME | crime victim | \n A person becomes eligible for insurance or a program because of crime related health condition or injury. \r\n\n \n Example: A person is a claimant under the U.S. Crime Victims Compensation program. \r\n\n |
| 4 | DIS | disability | \n A person becomes a claimant under a disability income insurance policy or a disability rehabilitation program because of a health condition or injury which limits the person's ability to earn an income or function without institutionalization. \r\n\n |
| 4 | EMPLOY | employment benefit | \n A person becomes eligible for insurance provided as an employment benefit based on employment status. \r\n\n |
| 4 | FINAN | financial eligibility | \n A person becomes eligible for a program based on financial criteria. \r\n\n \n Example: A person whose family income is below a financial threshold for eligibility for Medicaid or SCHIP. \r\n\n |
| 4 | HEALTH | health status | \n A person becomes eligible for a program because of a qualifying health condition or injury. \r\n\n \n Examples: A person is determined to have a qualifying health conditions include pregnancy, HIV/AIDs, tuberculosis, end stage renal disease, breast or cervical cancer, or other condition requiring specialized health services, hospice, institutional or community based care provided under a program \r\n\n |
| 4 | MULTI | multiple criteria eligibility | \n A person becomes eligible for a program based on more than one criterion. \r\n\n \n Examples: In the U.S., a child whose familiy income meets Medicaid financial thresholds and whose age is less than 18 is eligible for the Early and Periodic Screening, Diagnostic, and Treatment program (EPSDT). A person whose family income meets Medicaid financial thresholds and whose age is 65 years or older is eligible for Medicaid and Medicare, and are referred to as dual eligibles. \r\n\n |
| 4 | PNC | property and casualty condition | \n A person becomes a claimant under a property and casualty insurance policy because of a related health condition or injury resulting from a circumstance covered under the terms of the policy. \r\n\n \n Example: A person is a claimant under a homeowners insurance policy because of an injury sustained on the policyholderaTMs premises. \r\n\n |
| 4 | STATUTORY | statutory eligibility | \n A person becomes eligible for a program based on statutory criteria. \r\n\n \n Examples: A person is a member of an indigenous group, a veteran of military service, or in the U.S., a recipient of adoption assistance and foster care under Title IV-E of the Social Security. \r\n\n |
| 4 | VEHIC | motor vehicle accident victim | \n A person becomes a claimant under a motor vehicle accident insurance because of a motor vehicle accident related health condition or injury. \r\n\n |
| 4 | WORK | work related | \n A person becomes eligible for insurance or a program because of a work related health condition or injury. \r\n\n \n Example: A person is a claimant under the U.S. Black Lung Program. \r\n\n |
| 1 | (_ActInformationManagementReason) Abstract | \n \n Description:The rationale or purpose for an act relating to information management, such as archiving information for the purpose of complying with an enterprise data retention policy. \r\n\n | |
| 2 | (_ActHealthInformationManagementReason) Abstract | \n \n Description:The rationale or purpose for an act relating to health information management, such as archiving information for the purpose of complying with an organization policy or jurisdictional law relating to data retention. \r\n\n | |
| 3 | (_ActConsentInformationAccessOverrideReason) Abstract | \n To perform one or more operations on information to which the patient has not consented as deemed necessary by authorized entities for providing care in the best interest of the patient; providing immediately needed health care for an emergent condition; or for protecting public or third party safety. \r\n\n \n Usage Notes: Used to convey the reason that a provider or other entity may or has accessed personal healthcare information. Typically, this involves overriding the subject's consent directives. \r\n\n | |
| 4 | OVRER | emergency treatment override | \n To perform one or more operations on information to which the patient has not consented by authorized entities for treating a condition which poses an immediate threat to the patient's health and which requires immediate medical intervention. \r\n\n \n Usage Notes: The patient is unable to provide consent, but the provider determines they have an urgent healthcare related reason to access the record. \r\n\n |
| 4 | OVRINCOMP | incompetency override | \n To perform one or more operations on information to which the patient has not consented because deemed incompetent to provide consent. \r\n\n \n Usage Note: Maps to v2 CON-16 Subject Competence Indicator (ID) 01791 Definition: Identifies whether the subject was deemed competent to provide consent. Refer to table HL7 Table 0136 - Yes/No Indicator and CON-23 Non-Subject Consenter Reason User-defined Table 0502 - Non-Subject Consenter Reason code NC "Subject is not competent to consent". \r\n\n |
| 4 | OVRPJ | professional judgment override | \n To perform one or more operations on information to which the patient declined to consent for providing health care. \r\n\n \n Usage Notes: The patient, while able to give consent, has not. However the provider believes it is in the patient's interest to access the record without patient consent. \r\n\n |
| 4 | OVRPS | public safety override | \n To perform one or more operations on information to which the patient has not consented for public safety reasons. \r\n\n \n Usage Notes: The patient, while able to give consent, has not. However, the provider believes that access to masked patient information is justified because of concerns related to public safety. \r\n\n |
| 4 | OVRTPS | third party safety override | \n To perform one or more operations on information to which the patient has not consented for third party safety. \r\n\n \n Usage Notes: The patient, while able to give consent, has not. However, the provider believes that access to masked patient information is justified because of concerns related to the health and safety of one or more third parties. \r\n\n |
| 3 | PurposeOfUse | purpose of use | \n Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. \r\n\n \n Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes. \r\n\n |
| 4 | HMARKT | healthcare marketing | \n To perform one or more operations on information for marketing services and products related to health care. \r\n\n |
| 4 | HOPERAT | healthcare operations | \n To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care. \r\n\n |
| 5 | CAREMGT | care management | \n To perform analytics, evaluation and other secondary uses of treatment and healthcare related information to manage the quality, efficacy, patient safety, population health, and cost effectiveness of healthcare delivery. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment. \r\n\n \n Usage Note: The concept of care management is narrower than the list of activities related to more general organizational objectives such as provider profiling, education of healthcare and non-healthcare professionals; insurance underwriting, premium rating, reinsurance; organizational legal, medical review, auditing, compliance and fraud and abuse detection; business planning, development, and restructuring; fund-raising; and customer service. \r\n\n \n Map: Maps to ISO 14265 Classification Term "Health service management and quality assurance" described as "To inform persons or processes responsible for determining the availability, quality, safety, equity and cost-effectiveness of health care services." \r\n\n There is a semantic gap in concepts. This classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity.\n \r\n\n |
| 5 | DONAT | donation | \n To perform one or more operations on information used for cadaveric organ, eye or tissue donation. \r\n\n |
| 5 | FRAUD | fraud | \n To perform one or more operations on information used for fraud detection and prevention processes. \r\n\n |
| 5 | GOV | government | \n To perform one or more operations on information used within government processes. \r\n\n |
| 5 | HACCRED | health accreditation | \n To perform one or more operations on information for conducting activities related to meeting accreditation criteria. \r\n\n |
| 5 | HCOMPL | health compliance | \n To perform one or more operations on information used for conducting activities required to meet a mandate. \r\n\n |
| 5 | HDECD | decedent | \n To perform one or more operations on information used for handling deceased patient matters. \r\n\n |
| 5 | HDIRECT | directory | \n To perform one or more operation operations on information used to manage a patient directory. \r\n\n \n Examples: \n \r\n\n \n facility\n enterprise\n payer\n health information exchange patient directory\n \n |
| 5 | HDM | healthcare delivery management | \n To perform one or more actions on information used for conducting administrative and contractual activities by or on behalf of organizational entities responsible for delivery of an individual's benefits in a healthcare program, health plan or insurance. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment.\n \r\n\n \n Usage Note: Examples of activities conducted under this purpose of use: provider profiling, risk adjustment, underwriting, fraud and abuse, quality improvement population health and care management. Aligns with HIPAA Operation POU minus coordination of care or other treatment related activities. Similar to the description in SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking. \r\n\n \n Map: Maps to ISO 14265 Classification Term "Administration of care for an individual subject of care" described as "To inform persons or processes responsible for enabling the availability of resources or funding or permissions for providing health care services to the subject of care." \r\n\n However, this classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity. \r\n\n |
| 5 | HLEGAL | legal | \n To perform one or more operations on information for conducting activities required by legal proceeding. \r\n\n |
| 5 | HOUTCOMS | health outcome measure | \n To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions. \r\n\n |
| 5 | HPRGRP | health program reporting | \n To perform one or more operations on information used for conducting activities to meet program accounting requirements. \r\n\n |
| 5 | HQUALIMP | health quality improvement | \n To perform one or more operations on information used for conducting administrative activities to improve health care quality. \r\n\n |
| 5 | HSYSADMIN | health system administration | \n To perform one or more operations on information to administer the electronic systems used for the delivery of health care. \r\n\n |
| 6 | LABELING | labeling | \n To perform one or more operations on information to assign, persist, and manage labels to healthcare data to characterize various aspects, such as its security classification, sensitivity, compartment, integrity, and provenance; applicable privacy, consent, security, provenance, and trust policies; and handling caveats such as purpose of use, obligations, and refrain policies. \r\n\n Label management includes classification of target data by constructing and binding of a label set per applicable policies, security policy information file semantics, and classification guides. Label management also includes process and procedures for subsequent revision of a label for, e.g., reclassification, downgrading classification, and declassification. \r\n\n Label revisions may be triggered by, e.g., expiry of classification period; changes in applicable policy, e.g., revocation of a consent directive; or changes in the governing policy domain in which the data is relocated or a copy of the data is sent. If a label is revised, an audit log should be kept and the provenance of the label changes should be tracked. \r\n\n |
| 6 | METAMGT | metadata management | \n To perform one or more operations on information to assign, persist, and manage metadata to healthcare data to characterize various aspects used for its indexing, discovery, retrieval, and processing by systems, applications, and end users. For example, master index identifier, media type, and location. \r\n\n |
| 5 | MEMADMIN | member administration | \n To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program. \r\n\n |
| 5 | MILCDM | military command | \n To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law. \r\n\n |
| 5 | PATADMIN | patient administration | \n To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient. \r\n\n |
| 5 | PATSFTY | patient safety | \n To perform one or more operations on information in processes related to ensuring the safety of health care. \r\n\n |
| 5 | PERFMSR | performance measure | \n To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions. \r\n\n |
| 5 | RECORDMGT | records management | \n To perform one or more operations on information used within the health records management process. \r\n\n |
| 5 | SYSDEV | system development | \n To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application. \r\n\n |
| 6 | HTEST | test health data | \n To perform one or more operations on information that is simulated or synthetic health data used for testing system capabilities outside of a production or operational system environment. \r\n\n \n Usage Note: Data marked with a HTEST security label enables an access control system to permit interfacing systems or end users provisioned with a clearance, which includes a HTEST purpose of use attribute, to test, verify, or validate that a system or application will operate in production as intended based on design specifications. \r\n\n |
| 5 | TRAIN | training | \n To perform one or more operations on information used in training and education. \r\n\n |
| 4 | HPAYMT | healthcare payment | \n To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care. \r\n\n |
| 5 | CLMATTCH | claim attachment | \n To perform one or more operations on information for provision of additional clinical evidence in support of a request for coverage or payment for health services. \r\n\n |
| 5 | COVAUTH | coverage authorization | \n To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services. \r\n\n |
| 5 | COVERAGE | coverage under policy or program | \n To perform one or more operations on information for conducting activities related to coverage under a program or policy. \r\n\n |
| 6 | ELIGDTRM | eligibility determination | \n To perform one or more operations on information used for conducting eligibility determination for coverage in a program or policy. May entail review of financial status or disability assessment. \r\n\n |
| 6 | ELIGVER | eligibility verification | \n To perform one or more operations on information used for conducting eligibility verification of coverage in a program or policy. May entail provider contacting coverage source (e.g., government health program such as workers compensation or health plan) for confirmation of enrollment, eligibility for specific services, and any applicable copays. \r\n\n |
| 6 | ENROLLM | enrollment | \n To perform one or more operations on information used for enrolling a covered party in a program or policy. May entail recording of covered party's and any dependent's demographic information and benefit choices. \r\n\n |
| 6 | MILDCRG | military discharge | \n To perform one or more operations on information for the process of releasing military personnel from their service obligations, which may include determining service merit, discharge benefits, and disability assessment. \r\n\n |
| 5 | REMITADV | remittance advice | \n To perform one or more operations on information about the amount remitted for a health care claim. \r\n\n |
| 4 | HRESCH | healthcare research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data iincludes basic and applied research such as biomedical, population origin or ancestry, translational research, and disease, discipline, specialty specific healthcare research and clinical trial research. \r\n\n |
| 5 | BIORCH | biomedical research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified biomedical basic or applied research. For example, research on rare plants to determine whether biologic properties may be useful for pharmaceutical development. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 5 | CLINTRCH | clinical trial research | \n To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge. \r\n\n |
| 6 | CLINTRCHNPC | clinical trial research without patient care | \n To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge without provision of patient care. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, a clinical trial conducted on laboratory specimens collected from a specified patient population. \r\n\n |
| 6 | CLINTRCHPC | clinical trial research with patient care | \n To perform one or more operations on information for conducting scientific investigations with patient care in accordance with clinical trial protocols to obtain health care knowledge. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, an "off-label" drug used for cancer therapy administer to a specified patient population. \r\n\n |
| 6 | PRECLINTRCH | preclinical trial research | \n To perform one or more operations on information in preparation for conducting scientific investigation to obtain health care knowledge, such as research on animals or review of patient health records, to determine the feasibility of a clinical trial study; assist with protocol design; or in preparation for institutional review board or ethics committee approval process. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. \r\n\n |
| 5 | DSRCH | disease specific healthcare research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified conditions, diagnosis, or disease healthcare research. For example, conducting cancer research by testing reaction of tumor cells to certain biologics. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 5 | POARCH | population origins or ancestry healthcare research | \n To perform one or more operations on information, including genealogical pedigrees, historical records, surveys, family health data, health records, and genetic information, for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to population origins and/or ancestry healthcare research. For example, gathering genetic specimens from a specific population in order to determine the ancestry and population origins of that group. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 5 | TRANSRCH | translational healthcare research | \n To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge related to evidence based medicine during the course of providing healthcare treatment. Sometimes referred to as "bench to bedside", which is the iterative feedback loop between healthcare research and clinical trials with input from information collected in the course of routine provision of healthcare. For example, by extending a patient encounter to conduct a survey related to a research topic such as attitudes about use of a wellness device that a patient agreed to use. May be used in combination with clinical trial and other healthcare research purposes of use. \r\n\n |
| 4 | PATRQT | patient requested | \n To perform one or more operations on information in response to a patient's request. \r\n\n |
| 5 | FAMRQT | family requested | \n To perform one or more operations on information in response to a request by a family member authorized by the patient. \r\n\n |
| 5 | PWATRNY | power of attorney | \n To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative. \r\n\n |
| 5 | SUPNWK | support network | \n To perform one or more operations on information in response to a request by a person authorized by the patient. \r\n\n |
| 4 | PUBHLTH | public health | \n To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions. \r\n\n |
| 5 | DISASTER | disaster | \n To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone. \r\n\n |
| 5 | THREAT | threat | \n To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence. \r\n\n |
| 4 | TREAT | treatment | \n To perform one or more operations on information for provision of health care. \r\n\n |
| 5 | CLINTRL | clinical trial | \n To perform health care as part of the clinical trial protocol. \r\n\n |
| 5 | COC | coordination of care | \n To perform one or more actions on information in order to organize the provision and case management of an individual s healthcare, including: Monitoring a person's goals, needs, and preferences; acting as the communication link between two or more participants concerned with a person's health and wellness; organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person; and ensuring safe, appropriate, non-duplicative, and effective integrated care. \r\n\n \n Usage Note: Use when describing these functions: 1. Monitoring a person s goals, needs, and preferences. 2. Acting as the communication link between two or more participants concerned with a person's health and wellness. 3. Organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person. 4. Ensuring safe, appropriate, non-duplicative, and effective integrated care. \r\n\n The goal is to clearly differentiate this type of coordination of care from HIPAA Operations by specifying that these actions on information are undertaken in the provision of healthcare treatment. \r\n\n For similar uses of this concept, see SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking, which differentiates concepts of care coordination and case management for the provision of treatment as specifically distinct from activities related to health care delivery management and the operations of organizational entities involved in the delivery of healthcare. \r\n\n \n Map: Maps to ISO 14265 Classification Terms: "Support of care activities within the provider organisation for an individual subject of care" described as "To inform persons or processes enabling others to provide health care services to the subject of care." "Subject of Care Uses" described as "To inform the subject of care in support of his or her own interests." \r\n\n |
| 5 | ETREAT | Emergency Treatment | \n To perform one or more operations on information for provision of immediately needed health care for an emergent condition. \r\n\n |
| 6 | BTG | break the glass | \n To perform policy override operations on information for provision of immediately needed health care for an emergent condition affecting potential harm, death or patient safety by end users who are not provisioned for this purpose of use. Includes override of organizational provisioning policies and may include override of subject of care consent directive restricting access. \r\n\n \n Map: Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care."\nThe ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure. \r\n\n |
| 6 | ERTREAT | emergency room treatment | \n To perform one or more operations on information for provision of immediately needed health care for an emergent condition in an emergency room or similar emergent care context by end users provisioned for this purpose, which does not constitute as policy override such as in a "Break the Glass" purpose of use. \r\n\n Map:Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care." \r\n\n The ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure. \r\n\n There is a semantic gap in concepts. This classification term is described as activities to inform persons ? rather than the rationale for performing actions/operations on information related to the activity. \r\n\n |
| 5 | POPHLTH | population health | \n To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program. \r\n\n |
| 2 | (_ActInformationPrivacyReason) Abstract | \n \n Description:The rationale or purpose for an act relating to the management of personal information, such as disclosing personal tax information for the purpose of complying with a court order. \r\n\n | |
| 3 | MARKT | marketing | \n \n Description:\n \r\n\n |
| 3 | OPERAT | operations | \n \n Description:Administrative and contractual processes required to support an activity, product, or service \r\n\n |
| 4 | LEGAL | subpoena | \n \n Definition:To provide information as a result of a subpoena. \r\n\n |
| 4 | ACCRED | accreditation | \n \n Description:Operational activities conducted for the purposes of meeting of criteria defined by an accrediting entity for an activity, product, or service \r\n\n |
| 4 | COMPL | compliance | \n \n Description:Operational activities required to meet a mandate related to an activity, product, or service \r\n\n |
| 4 | ENADMIN | entity administration | \n \n Description:Operational activities conducted to administer information relating to entities involves with an activity, product, or service \r\n\n |
| 4 | OUTCOMS | outcome measure | \n \n Description:Operational activities conducted for the purposes of assessing the results of an activity, product, or service \r\n\n |
| 4 | PRGRPT | program reporting | \n \n Description:Operational activities conducted to meet program accounting requirements related to an activity, product, or service \r\n\n |
| 4 | QUALIMP | quality improvement | \n \n Description:Operational activities conducted for the purposes of improving the quality of an activity, product, or service \r\n\n |
| 4 | SYSADMN | system administration | \n \n Description:Operational activities conducted to administer the electronic systems used for an activity, product, or service \r\n\n |
| 3 | PAYMT | payment | \n \n Description:Administrative, financial, and contractual processes related to payment for an activity, product, or service \r\n\n |
| 3 | RESCH | research | \n \n Description:Investigative activities conducted for the purposes of obtaining knowledge \r\n\n |
| 3 | SRVC | service | \n \n Description:Provision of a service, product, or capability to an individual or organization \r\n\n |
| 1 | _ActInvalidReason | ActInvalidReason | \n \n Description: Types of reasons why a substance is invalid for use. \r\n\n |
| 2 | ADVSTORAGE | adverse storage condition | \n \n Description: Storage conditions caused the substance to be ineffective. \r\n\n |
| 3 | COLDCHNBRK | cold chain break | \n \n Description: Cold chain was not maintained for the substance. \r\n\n |
| 2 | EXPLOT | expired lot | \n \n Description: The lot from which the substance was drawn was expired. \r\n\n |
| 2 | OUTSIDESCHED | administered outside recommended schedule or practice | \n The substance was administered outside of the recommended schedule or practice. \r\n\n |
| 2 | PRODRECALL | product recall | \n \n Description: The substance was recalled by the manufacturer. \r\n\n |
| 1 | (_ActInvoiceCancelReason) Abstract | \n Domain specifies the codes used to describe reasons why a Provider is cancelling an Invoice or Invoice Grouping. \r\n\n | |
| 2 | INCCOVPTY | incorrect covered party as patient | \n The covered party (patient) specified with the Invoice is not correct. \r\n\n |
| 2 | INCINVOICE | incorrect billing | \n The billing information, specified in the Invoice Elements, is not correct. This could include incorrect costing for items included in the Invoice. \r\n\n |
| 2 | INCPOLICY | incorrect policy | \n The policy specified with the Invoice is not correct. For example, it may belong to another Adjudicator or Covered Party. \r\n\n |
| 2 | INCPROV | incorrect provider | \n The provider specified with the Invoice is not correct. \r\n\n |
| 1 | (_ActNoImmunizationReason) Abstract | \n A coded description of the reason for why a patient did not receive a scheduled immunization. \r\n\n (important for public health strategy \r\n\n | |
| 2 | IMMUNE | immunity | \n \n Definition:Testing has shown that the patient already has immunity to the agent targeted by the immunization. \r\n\n |
| 2 | MEDPREC | medical precaution | \n \n Definition:The patient currently has a medical condition for which the vaccine is contraindicated or for which precaution is warranted. \r\n\n |
| 2 | OSTOCK | product out of stock | \n \n Definition:There was no supply of the product on hand to perform the service. \r\n\n |
| 2 | PATOBJ | patient objection | \n \n Definition:The patient or their guardian objects to receiving the vaccine. \r\n\n |
| 2 | PHILISOP | philosophical objection | \n \n Definition:The patient or their guardian objects to receiving the vaccine because of philosophical beliefs. \r\n\n |
| 2 | RELIG | religious objection | \n \n Definition:The patient or their guardian objects to receiving the vaccine on religious grounds. \r\n\n |
| 2 | VACEFF | vaccine efficacy concerns | \n \n Definition:The intended vaccine has expired or is otherwise believed to no longer be effective. \r\n\n \n Example:Due to temperature exposure. \r\n\n |
| 2 | VACSAF | vaccine safety concerns | \n \n Definition:The patient or their guardian objects to receiving the vaccine because of concerns over its safety. \r\n\n |
| 1 | (_ActSupplyFulfillmentRefusalReason) Abstract | \n Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision. E.g. "Suspect fraud", "Possible abuse", "Contraindicated". \r\n\n (used when capturing 'refusal to fill' annotations) \r\n\n | |
| 2 | FRR01 | order stopped | \n \n Definition:The order has been stopped by the prescriber but this fact has not necessarily captured electronically. \r\n\n \n Example:A verbal stop, a fax, etc. \r\n\n |
| 2 | FRR02 | stale-dated order | \n \n Definition:Order has not been fulfilled within a reasonable amount of time, and may not be current. \r\n\n |
| 2 | FRR03 | incomplete data | \n \n Definition:Data needed to safely act on the order which was expected to become available independent of the order is not yet available \r\n\n \n Example:Lab results, diagnostic imaging, etc. \r\n\n |
| 2 | FRR04 | product unavailable | \n \n Definition:Product not available or manufactured. Cannot supply. \r\n\n |
| 2 | FRR05 | ethical/religious | \n \n Definition:The dispenser has ethical, religious or moral objections to fulfilling the order/dispensing the product. \r\n\n |
| 2 | FRR06 | unable to provide care | \n \n Definition:Fulfiller not able to provide appropriate care associated with fulfilling the order. \r\n\n \n Example:Therapy requires ongoing monitoring by fulfiller and fulfiller will be ending practice, leaving town, unable to schedule necessary time, etc. \r\n\n |
| 1 | (_ClinicalResearchEventReason) Abstract | \n \n Definition:Specifies the reason that an event occurred in a clinical research study. \r\n\n | |
| 2 | RET | retest | \n \n Definition:The event occurred so that a test or observation performed at a prior event could be performed again due to conditions set forth in the protocol. \r\n\n |
| 2 | SCH | scheduled | \n \n Definition:The event occurred due to it being scheduled in the research protocol. \r\n\n |
| 2 | TRM | termination | \n \n Definition:The event occurred in order to terminate the subject's participation in the study. \r\n\n |
| 2 | UNS | unscheduled | \n \n Definition:The event that occurred was initiated by a study participant (e.g. the subject or the investigator), and did not occur for protocol reasons. \r\n\n |
| 1 | (_ClinicalResearchObservationReason) Abstract | \n \n Definition:SSpecifies the reason that a test was performed or observation collected in a clinical research study. \r\n\n \n Note:This set of codes are not strictly reasons, but are used in the currently Normative standard. Future revisions of the specification will model these as ActRelationships and thes codes may subsequently be retired. Thus, these codes should not be used for new specifications. \r\n\n | |
| 2 | NPT | non-protocol | \n \n Definition:The observation or test was neither defined or scheduled in the study protocol. \r\n\n |
| 2 | PPT | per protocol | \n \n Definition:The observation or test occurred due to it being defined in the research protocol, and during an activity or event that was scheduled in the protocol. \r\n\n |
| 2 | UPT | per definition | \n \n :The observation or test occurred as defined in the research protocol, but at a point in time not specified in the study protocol. \r\n\n |
| 1 | (_CombinedPharmacyOrderSuspendReasonCode) Abstract | \n \n Description:Indicates why the prescription should be suspended. \r\n\n | |
| 2 | ALTCHOICE | try another treatment first | \n \n Description:This therapy has been ordered as a backup to a preferred therapy. This order will be released when and if the preferred therapy is unsuccessful. \r\n\n |
| 2 | CLARIF | prescription requires clarification | \n \n Description:Clarification is required before the order can be acted upon. \r\n\n |
| 2 | DRUGHIGH | drug level too high | \n \n Description:The current level of the medication in the patient's system is too high. The medication is suspended to allow the level to subside to a safer level. \r\n\n |
| 2 | HOSPADM | admission to hospital | \n \n Description:The patient has been admitted to a care facility and their community medications are suspended until hospital discharge. \r\n\n |
| 2 | LABINT | lab interference issues | \n \n Description:The therapy would interfere with a planned lab test and the therapy is being withdrawn until the test is completed. \r\n\n |
| 2 | NON-AVAIL | patient not-available | \n \n Description:Patient not available for a period of time due to a scheduled therapy, leave of absence or other reason. \r\n\n |
| 2 | PREG | parent is pregnant/breast feeding | \n \n Description:The patient is pregnant or breast feeding. The therapy will be resumed when the pregnancy is complete and the patient is no longer breastfeeding. \r\n\n |
| 2 | SALG | allergy | \n \n Description:The patient is believed to be allergic to a substance that is part of the therapy and the therapy is being temporarily withdrawn to confirm. \r\n\n |
| 2 | SDDI | drug interacts with another drug | \n \n Description:The drug interacts with a short-term treatment that is more urgently required. This order will be resumed when the short-term treatment is complete. \r\n\n |
| 2 | SDUPTHER | duplicate therapy | \n \n Description:Another short-term co-occurring therapy fulfills the same purpose as this therapy. This therapy will be resumed when the co-occuring therapy is complete. \r\n\n |
| 2 | SINTOL | suspected intolerance | \n \n Description:The patient is believed to have an intolerance to a substance that is part of the therapy and the therapy is being temporarily withdrawn to confirm. \r\n\n |
| 2 | SURG | patient scheduled for surgery | \n \n Description:The drug is contraindicated for patients receiving surgery and the patient is scheduled to be admitted for surgery in the near future. The drug will be resumed when the patient has sufficiently recovered from the surgery. \r\n\n |
| 2 | WASHOUT | waiting for old drug to wash out | \n \n Description:The patient was previously receiving a medication contraindicated with the current medication. The current medication will remain on hold until the prior medication has been cleansed from their system. \r\n\n |
| 1 | _ControlActNullificationReasonCode | ControlActNullificationReasonCode | \n \n Description:Identifies reasons for nullifying (retracting) a particular control act. \r\n\n |
| 2 | ALTD | altered decision | \n \n Description:The decision on which the recorded information was based was changed before the decision had an effect. \r\n\n \n Example:Aborted prescription before patient left office, released prescription before suspend took effect. \r\n\n |
| 2 | EIE | entered in error | \n \n Description:The information was recorded incorrectly or was recorded in the wrong record. \r\n\n |
| 2 | NORECMTCH | no record match | \n \n Description: There is no match for the record in the database. \r\n\n |
| 1 | (_ControlActNullificationRefusalReasonType) Abstract | \n \n Description: Reasons to refuse a transaction to be undone. \r\n\n | |
| 2 | INRQSTATE | in requested state | \n The record is already in the requested state. \r\n\n |
| 2 | NOMATCH | no match | \n \n Description: There is no match. \r\n\n |
| 3 | NORECMTCH | ||
| 3 | NOPRODMTCH | no product match | \n \n Description: There is no match for the product in the master file repository. \r\n\n |
| 3 | NOSERMTCH | no service match | \n \n Description: There is no match for the service in the master file repository. \r\n\n |
| 3 | NOVERMTCH | no version match | \n \n Description: There is no match for the record and version. \r\n\n |
| 2 | NOPERM | no permission | \n \n Description: There is no permission. \r\n\n |
| 3 | NOUSERPERM | no user permission | \n \n Definition:The user does not have permission \r\n\n |
| 3 | NOAGNTPERM | no agent permission | \n \n Description: The agent does not have permission. \r\n\n |
| 3 | NOUSRPERM | no user permission | \n \n Description: The user does not have permission. \r\n\n |
| 2 | WRNGVER | wrong version | \n \n Description: The record and version requested to update is not the current version. \r\n\n |
| 1 | (_ControlActReason) Abstract | \n Identifies why a specific query, request, or other trigger event occurred. \r\n\n | |
| 2 | (_MedicationOrderAbortReasonCode) Abstract | \n \n Description:Indicates the reason the medication order should be aborted. \r\n\n | |
| 3 | DISCONT | product discontinued | \n \n Description:The medication is no longer being manufactured or is otherwise no longer available. \r\n\n |
| 3 | INEFFECT | ineffective | \n \n Description:The therapy has been found to not have the desired therapeutic benefit on the patient. \r\n\n |
| 3 | MONIT | response to monitoring | \n \n Description:Monitoring the patient while taking the medication, the decision has been made that the therapy is no longer appropriate. \r\n\n |
| 3 | NOREQ | no longer required for treatment | \n \n Description:The underlying condition has been resolved or has evolved such that a different treatment is no longer needed. \r\n\n |
| 3 | NOTCOVER | not covered | \n \n Description:The product does not have (or no longer has) coverage under the patientaTMs insurance policy. \r\n\n |
| 3 | PREFUS | patient refuse | \n \n Description:The patient refused to take the product. \r\n\n |
| 3 | RECALL | product recalled | \n \n Description:The manufacturer or other agency has requested that stocks of a medication be removed from circulation. \r\n\n |
| 3 | REPLACE | change in order | \n \n Description:Item in current order is no longer in use as requested and a new one has/will be created to replace it. \r\n\n |
| 4 | DOSECHG | change in medication/dose | \n \n Description:The medication is being re-prescribed at a different dosage. \r\n\n |
| 3 | REPLACEFIX | error in order | \n \n Description:Current order was issued with incorrect data and a new order has/will be created to replace it. \r\n\n |
| 3 | UNABLE | unable to use | \n \n Description:<The patient is not (or is no longer) able to use the medication in a manner prescribed. \r\n\n \n Example:CanaTMt swallow. \r\n\n |
| 2 | (_MedicationOrderReleaseReasonCode) Abstract | \n \n Definition:A collection of concepts that indicate why the prescription should be released from suspended state. \r\n\n | |
| 3 | HOLDDONE | suspend reason no longer applies | \n \n Definition:The original reason for suspending the medication has ended. \r\n\n |
| 3 | HOLDINAP | suspend reason inappropriate | \n \n Definition:\n \r\n\n |
| 2 | (_ModifyPrescriptionReasonType) Abstract | \n Types of reason why a prescription is being changed. \r\n\n | |
| 3 | ADMINERROR | administrative error in order | \n Order was created with incorrect data and is changed to reflect the intended accuracy of the order. \r\n\n |
| 3 | CLINMOD | clinical modification | \n Order is changed based on a clinical reason. \r\n\n |
| 2 | _PharmacySupplyEventAbortReason | PharmacySupplyEventAbortReason | \n \n Definition:Identifies why the dispense event was not completed. \r\n\n |
| 3 | CONTRA | contraindication | \n \n Definition:Contraindication identified \r\n\n |
| 3 | FOABORT | order aborted | \n \n Definition:Order to be fulfilled was aborted \r\n\n |
| 3 | FOSUSP | order suspended | \n \n Definition:Order to be fulfilled was suspended \r\n\n |
| 3 | NOPICK | not picked up | \n \n Definition:Patient did not come to get medication \r\n\n |
| 3 | PATDEC | patient changed mind | \n \n Definition:Patient changed their mind regarding obtaining medication \r\n\n |
| 3 | QUANTCHG | change supply quantity | \n \n Definition:Patient requested a revised quantity of medication \r\n\n |
| 2 | (_PharmacySupplyEventStockReasonCode) Abstract | \n \n Definition:A collection of concepts that indicates the reason for a "bulk supply" of medication. \r\n\n | |
| 3 | FLRSTCK | floor stock | \n \n Definition:The bulk supply is issued to replenish a ward for local dispensing. (Includes both mobile and fixed-location ward stocks.) \r\n\n |
| 3 | LTC | long term care use | \n \n Definition:The bulk supply will be administered within a long term care facility. \r\n\n |
| 3 | OFFICE | office use | \n \n Definition:The bulk supply is intended for general clinician office use. \r\n\n |
| 3 | PHARM | pharmacy transfer | \n \n Definition:The bulk supply is being transferred to another dispensing facility to. \r\n\n \n Example:Alleviate a temporary shortage. \r\n\n |
| 3 | PROG | program use | \n \n Definition:The bulk supply is intended for dispensing according to a specific program. \r\n\n \n Example:Mass immunization. \r\n\n |
| 2 | (_PharmacySupplyRequestRenewalRefusalReasonCode) Abstract | \n \n Definition:A collection of concepts that identifies why a renewal prescription has been refused. \r\n\n | |
| 3 | DISCONT | ||
| 3 | ALREADYRX | new prescription exists | \n \n Definition:Patient has already been given a new (renewal) prescription. \r\n\n |
| 3 | FAMPHYS | family physician must authorize further fills | \n \n Definition:Request for further authorization must be done through patient's family physician. \r\n\n |
| 3 | MODIFY | modified prescription exists | \n \n Definition:Therapy has been changed and new prescription issued \r\n\n |
| 3 | NEEDAPMT | patient must make appointment | \n \n Definition:Patient must see prescriber prior to further fills. \r\n\n |
| 3 | NOTAVAIL | prescriber not available | \n \n Definition:Original prescriber is no longer available to prescribe and no other prescriber has taken responsibility for the patient. \r\n\n |
| 3 | NOTPAT | patient no longer in this practice | \n \n Definition:Patient no longer or has never been under this prescribers care. \r\n\n |
| 3 | ONHOLD | medication on hold | \n \n Definition:This medication is on hold. \r\n\n |
| 3 | PRNA | product not available | \n \n Description:This product is not available or manufactured. \r\n\n |
| 3 | STOPMED | prescriber stopped medication for patient | \n Renewing or original prescriber informed patient to stop using the medication. \r\n\n |
| 3 | TOOEARLY | too early | \n \n Definition:The patient should have medication remaining. \r\n\n |
| 2 | (_SupplyOrderAbortReasonCode) Abstract | \n \n Definition:A collection of concepts that indicates why the prescription should no longer be allowed to be dispensed (but can still administer what is already being dispensed). \r\n\n | |
| 3 | IMPROV | condition improved | \n \n Definition:The patient's medical condition has nearly abated. \r\n\n |
| 3 | INTOL | intolerance | \n \n Description:The patient has an intolerance to the medication. \r\n\n |
| 3 | NEWSTR | new strength | \n \n Definition:The current medication will be replaced by a new strength of the same medication. \r\n\n |
| 3 | NEWTHER | new therapy | \n \n Definition:A new therapy will be commenced when current supply exhausted. \r\n\n |
| 1 | (_GenericUpdateReasonCode) Abstract | \n \n Description:Identifies why a change is being made to a record. \r\n\n | |
| 2 | CHGDATA | information change | \n \n Description:Information has changed since the record was created. \r\n\n |
| 2 | FIXDATA | error correction | \n \n Description:Previously recorded information was erroneous and is being corrected. \r\n\n |
| 2 | MDATA | merge data | \n Information is combined into the record. \r\n\n |
| 2 | NEWDATA | new information | \n \n Description:New information has become available to supplement the record. \r\n\n |
| 2 | UMDATA | unmerge data | \n Information is separated from the record. \r\n\n |
| 1 | (_PatientProfileQueryReasonCode) Abstract | \n \n Definition:A collection of concepts identifying why the patient's profile is being queried. \r\n\n | |
| 2 | ADMREV | administrative review | \n \n Definition: To evaluate for service authorization, payment, reporting, or performance/outcome measures. \r\n\n |
| 2 | LEGAL | ||
| 2 | PATCAR | patient care | \n \n Definition:To obtain records as part of patient care. \r\n\n |
| 2 | PATREQ | patient request query | \n \n Definition:Patient requests information from their profile. \r\n\n |
| 2 | PRCREV | practice review | \n \n Definition:To evaluate the provider's current practice for professional-improvement reasons. \r\n\n |
| 2 | REGUL | regulatory review | \n \n Description:Review for the purpose of regulatory compliance. \r\n\n |
| 2 | RSRCH | research | \n \n Definition:To provide research data, as authorized by the patient. \r\n\n |
| 2 | VALIDATION | validation review | \n \n Description:To validate the patient's record. \r\n\n \n Example:Merging or unmerging records. \r\n\n |
| 1 | _PharmacySupplyRequestFulfillerRevisionRefusalReasonCode | PharmacySupplyRequestFulfillerRevisionRefusalReasonCode | \n \n Definition:Indicates why the request to transfer a prescription from one dispensing facility to another has been refused. \r\n\n |
| 2 | LOCKED | locked | \n \n Definition:The prescription may not be reassigned from the original pharmacy. \r\n\n |
| 2 | NOUSERPERM | ||
| 2 | UNKWNTARGET | unknown target | \n \n Definition:The target facility does not recognize the dispensing facility. \r\n\n |
| 1 | (_RefusalReasonCode) Abstract | \n \n Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action. \r\n\n | |
| 2 | NOMATCH | ||
| 2 | NOPERM | ||
| 1 | (_SchedulingActReason) Abstract | \n Reasons for cancelling or rescheduling an Appointment \r\n\n | |
| 2 | PAT | ||
| 2 | BLK | Unexpected Block (of Schedule) | \n The time slots previously allocated are now blocked and no longer available for booking Appointments \r\n\n |
| 2 | DEC | Patient Deceased | \n The Patient is deceased \r\n\n |
| 2 | FIN | No Financial Backing | \n Patient unable to pay and not covered by insurance \r\n\n |
| 2 | MED | Medical Status Altered | \n The medical condition of the Patient has changed \r\n\n |
| 2 | MTG | In an outside meeting | \n The Physician is in a meeting. For example, he/she may request administrative time to talk to family after appointment \r\n\n |
| 2 | PHY | Physician request | \n The Physician requested the action \r\n\n |
| 1 | _StatusRevisionRefusalReasonCode | StatusRevisionRefusalReasonCode | \n Indicates why the act revision (status update) is being refused. \r\n\n |
| 2 | NORECMTCH | ||
| 2 | INRQSTATE | ||
| 2 | NOUSERPERM | ||
| 2 | FILLED | fully filled | \n Ordered quantity has already been completely fulfilled. \r\n\n |
| 1 | _SubstanceAdministrationPermissionRefusalReasonCode | SubstanceAdministrationPermissionRefusalReasonCode | \n \n Definition:Indicates why the requested authorization to prescribe or dispense a medication has been refused. \r\n\n |
| 2 | NOUSERPERM | ||
| 2 | PATINELIG | patient not eligible | \n \n Definition:Patient not eligible for drug \r\n\n |
| 2 | PROTUNMET | protocol not met | \n \n Definition:Patient does not meet required protocol \r\n\n |
| 2 | PROVUNAUTH | provider not authorized | \n \n Definition:Provider is not authorized to prescribe or dispense \r\n\n |
| 1 | (_SubstanceAdminSubstitutionNotAllowedReason) Abstract | \n Reasons why substitution of a substance administration request is not permitted. \r\n\n | |
| 2 | PAT | ||
| 2 | ALGINT | allergy intolerance | \n \n Definition: Patient has had a prior allergic intolerance response to alternate product or one of its components. \r\n\n |
| 2 | COMPCON | compliance concern | \n \n Definition: Patient has compliance issues with medication such as differing appearance, flavor, size, shape or consistency. \r\n\n |
| 2 | THERCHAR | therapeutic characteristics | \n The prescribed product has specific clinical release or other therapeutic characteristics not shared by other substitutable medications. \r\n\n |
| 2 | TRIAL | clinical trial drug | \n \n Definition: The specific manufactured drug is part of a clinical trial. \r\n\n |
| 1 | (_SubstanceAdminSubstitutionReason) Abstract | ||
| 2 | CT | continuing therapy | \n Indicates that the decision to substitute or to not substitute was driven by a desire to maintain consistency with a pre-existing therapy. I.e. The performer provided the same item/service as had been previously provided rather than providing exactly what was ordered, or rather than substituting with a lower-cost equivalent. \r\n\n |
| 2 | FP | formulary policy | \n Indicates that the decision to substitute or to not substitute was driven by a policy expressed within the formulary. \r\n\n |
| 2 | OS | out of stock | \n In the case of 'substitution', indicates that the substitution occurred because the ordered item was not in stock. In the case of 'no substitution', indicates that a cheaper equivalent was not substituted because it was not in stock. \r\n\n |
| 2 | RR | regulatory requirement | \n Indicates that the decision to substitute or to not substitute was driven by a jurisdictional regulatory requirement mandating or prohibiting substitution. \r\n\n |
| 1 | (_TransferActReason) Abstract | \n The explanation for why a patient is moved from one location to another within the organization \r\n\n | |
| 2 | ER | Error | \n Moved to an error in placing the patient in the original location. \r\n\n |
| 2 | RQ | Request | \n Moved at the request of the patient. \r\n\n |
| 1 | (_ActBillableServiceReason) Abstract | \n \n Definition: This domain is used to document reasons for providing a billable service; the billable services may include both clinical services and social services. \r\n\n | |
| 2 | (_ActBillableClinicalServiceReason) Abstract | \n Reason for Clinical Service being performed. \r\n\n This domain excludes reasons specified by diagnosed conditions. \r\n\n Examples of values from this domain include duplicate therapy and fraudulent prescription. \r\n\n | |
| 1 | BONUS | ||
| 1 | CHD | Children only | \n \n Description:The level of coverage under the policy or program is available only to children \r\n\n |
| 1 | DEP | Dependents only | \n \n Description:The level of coverage under the policy or program is available only to a subscriber's dependents. \r\n\n |
| 1 | ECH | Employee and children | \n \n Description:The level of coverage under the policy or program is available to an employee and his or her children. \r\n\n |
| 1 | EDU | ||
| 1 | EMP | Employee only | \n \n Description:The level of coverage under the policy or program is available only to an employee. \r\n\n |
| 1 | ESP | Employee and spouse | \n \n Description:The level of coverage under the policy or program is available to an employee and his or her spouse. \r\n\n |
| 1 | FAM | Family | \n \n Description:The level of coverage under the policy or program is available to a subscriber's family. \r\n\n |
| 1 | IND | Individual | \n \n Description:The level of coverage under the policy or program is available to an individual. \r\n\n |
| 1 | INVOICE | ||
| 1 | PROA | ||
| 1 | RECOV | ||
| 1 | RETRO | ||
| 1 | SPC | Spouse and children | \n \n Description:The level of coverage under the policy or program is available to a subscriber's spouse and children \r\n\n |
| 1 | SPO | Spouse only | \n \n Description:The level of coverage under the policy or program is available only to a subscribers spouse \r\n\n |
| 1 | TRAN |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_ContextControlAdditive) Abstract | \n The association adds to the existing context associated with the Act. Both this association and any associations propagated from ancestor Acts are interpreted as being related to this Act. \r\n\n | |
| 2 | AN | additive, non-propagating | \n The association adds to the existing context associated with the Act, but will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Additive, Non-Propagating" it means that the author will be added to the set of author participations that have propagated from ancestor Acts for the purpose of this Act. However only the previously propagated authors will propagate to any child Acts that allow context to be propagated. \r\n\n |
| 2 | AP | additive, propagating | \n The association adds to the existing context associated with the Act, and will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Additive, Propagating" it means that the author will be added to the set of author participations that have propagated from ancestor Acts, and will itself propagate with the other authors to any child Acts that allow context to be propagated. \r\n\n |
| 1 | (_ContextControlNonPropagating) Abstract | \n The association applies only to the current Act and will not propagate to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd). \r\n\n | |
| 2 | AN | ||
| 2 | ON | overriding, non-propagating | \n The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. However, this overriding association will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Overriding, Non-Propagating" it means that the author will replace the set of author participations that have propagated from ancestor Acts. Furthermore, no author participations whatsoever will propagate to any child Acts that allow context to be propagated. \r\n\n |
| 1 | (_ContextControlOverriding) Abstract | \n The association adds to the existing context associated with the Act, but replaces associations propagated from ancestor Acts whose typeCodes are the same or more specific. \r\n\n | |
| 2 | ON | ||
| 2 | OP | overriding, propagating | \n The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. This overriding association will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Overriding, Propagating" it means that the author will replace the set of author participations that have propagated from ancestor Acts, and will itself be the only author to propagate to any child Acts that allow context to be propagated. \r\n\n |
| 1 | (_ContextControlPropagating) Abstract | \n The association propagates to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd). \r\n\n | |
| 2 | AP | ||
| 2 | OP |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_CalendarCycleOneLetter) Abstract Deprecated | ||
| 2 | CW | week (continuous) | |
| 2 | CY | year | |
| 2 | D | day of the month | |
| 2 | DW | day of the week (begins with Monday) | |
| 2 | H | hour of the day | |
| 2 | M | month of the year | |
| 2 | N | minute of the hour | |
| 2 | S | second of the minute | |
| 1 | (_CalendarCycleTwoLetter) Abstract Deprecated | ||
| 2 | CW | ||
| 2 | CY | ||
| 2 | D | ||
| 2 | DW | ||
| 2 | H | ||
| 2 | M | ||
| 2 | N | ||
| 2 | S | ||
| 2 | CD | day (continuous) | |
| 2 | CH | hour (continuous) | |
| 2 | CM | month (continuous) | |
| 2 | CN | minute (continuous) | |
| 2 | CS | second (continuous) | |
| 2 | DY | day of the year | |
| 2 | WY | week of the year | |
| 1 | WM | week of the month | \n The week with the month's first Thursday in it (analagous to the ISO 8601 definition for week of the year). \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | baseline | baseline | |
| 1 | bottom | bottom | |
| 1 | middle | middle | |
| 1 | top | top |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_AffiliationRoleType) Abstract | \n Concepts characterizing the type of association formed by player and scoper when there is a recognized Affiliate role by which the two parties are related. \r\n\n \n Examples: Business Partner, Business Associate, Colleague \r\n\n | |
| 2 | (_AgentRoleType) Abstract | \n Parties that may or should contribute or have contributed to an Act. \r\n\n | |
| 3 | AMENDER | amender | \n An entity which corrected, edited, or amended pre-existing information. \r\n\n |
| 3 | CLASSIFIER | classifier | \n An individual authorized to assign an original classification to information, including compilations of unclassified information, based on a determination that the information requires protection against unauthorized disclosure. The individual marks the information with immutable, computable, and human readable security labels in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded, downgraded, used in derivative classification, or declassified] in a manner that preserves the overridden original classification binding and provenance. \r\n\n |
| 3 | CONSENTER | consenter | \n An entity or an entity's delegatee who is the grantee in an agreement such as a consent for services, advanced directive, or a privacy consent directive in accordance with jurisdictional, organizational, or patient policy. \r\n\n |
| 3 | CONSWIT | consent witness | \n An entity which has witnessed and attests to observing another entity being counseled about an agreement such as a consent for services, advanced directive, or a privacy consent directive. \r\n\n |
| 3 | COPART | co-participant | \n An entity which participates in the generation of and attest to veracity of content, but is not an author or coauthor. For example a surgeon who is required by institutional, regulatory, or legal rules to sign an operative report, but who was not involved in the authorship of that report. \r\n\n |
| 3 | DECLASSIFIER | declassifier | \n An individual which is authorized to declassify information based on a determination that the information no longer requires protection against unauthorized disclosure. The individual marks the information being declassified using computable and human readable security labels indicating that this is copy of previously classified information is unclassified in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded or used in derivative classification] in a manner that preserves the overridden original classification binding and provenance. \r\n\n |
| 3 | DELEGATEE | delegatee | \n A party to whom some right or authority is granted by a delegator. \r\n\n |
| 3 | DELEGATOR | delegator | \n A party that grants all or some portion its right or authority to another party. \r\n\n |
| 3 | DOWNGRDER | downgrader | \n An individual authorized to lower the classification level of labeled content and provide rationale for doing so as directed by a classification guide. \r\n\n |
| 3 | DRIVCLASSIFIER | derivative classifier | \n An individual who is only authorized to classify reproduced, extracted, or summarized classified information, or compile classified and unclassified information by applying classification markings derived from source material or as directed by a classification guide. \r\n\n |
| 3 | GRANTEE | grantee | \n An entity which accepts certain rights or authority from a grantor. \r\n\n |
| 3 | GRANTOR | grantor | \n An entity which agrees to confer certain rights or authority to a grantee. \r\n\n |
| 3 | INTPRTER | interpreter | \n An entity which converts spoken or written language into the language of key participants in an event such as when a provider is obtaining a patient's consent to treatment or permission to disclose information. \r\n\n |
| 3 | REVIEWER | reviewer | \n An entity authorized to filter information according to approved criteria. \r\n\n |
| 3 | VALIDATOR | validator | \n An entity authorized to validate information for inclusion in a record. \r\n\n |
| 2 | (_CoverageSponsorRoleType) Abstract | \n \n Description:Codes that indicate a specific type of sponsor. Used when the sponsor's role is only either as a fully insured sponsor or only as a self-insured sponsor. NOTE: Where a sponsor may be either, use the SponsorParticipationFunction.code (fully insured or self insured) to indicate the type of responsibility. (CO6-0057) \r\n\n | |
| 3 | FULLINS | Fully insured coverage sponsor | \n \n Description:An employer or organization that contracts with an underwriter to assumes the financial risk and administrative responsibility for coverage of health services for covered parties. \r\n\n |
| 3 | SELFINS | Self insured coverage sponsor | \n \n Description:An employer or organization that assumes the financial risk and administrative responsibility for coverage of health services for covered parties. \r\n\n |
| 2 | (_PayorRoleType) Abstract | \n \n Description:PayorRoleType for a particular type of policy or program benefit package or plan where more detail about the coverage administration role of the Payor is required. The functions performed by a Payor qualified by a PayorRoleType may be specified by the PayorParticpationFunction value set. \r\n\n \n Examples:A Payor that is a TPA may administer a managed care plan without underwriting the risk. \r\n\n | |
| 3 | ENROLBKR | Enrollment Broker | \n \n Description:A payor that is responsible for functions related to the enrollment of covered parties. \r\n\n |
| 3 | TPA | Third party administrator | \n \n Description:Third party administrator (TPA) is a payor organization that processes health care claims without carrying insurance risk. Third party administrators are prominent players in the managed care industry and have the expertise and capability to administer all or a portion of the claims process. They are normally contracted by a health insurer or self-insuring companies to administer services, including claims administration, premium collection, enrollment and other administrative activities. \r\n\n Self-insured employers often contract with third party administrator to handle their insurance functions. Insurance companies oftentimes outsource the claims, utilization review or membership functions to a TPA. Sometimes TPAs only manage provider networks, only claims or only utilization review. \r\n\n While some third-party administrators may operate as units of insurance companies, they are often independent. However, hospitals or provider organizations desiring to set up their own health plans will often outsource certain responsibilities to TPAs. TPAs may perform one or several payor functions, specified by the PayorParticipationFunction value set, such as provider management, enrollment, utilization management, and fee for service claims adjudication management. \r\n\n |
| 3 | UMO | Utilization management organization | \n \n Description:A payor that is responsible for review and case management of health services covered under a policy or program. \r\n\n |
| 2 | RESPRSN | responsible party | \n The role played by a party who has legal responsibility for another party. \r\n\n |
| 3 | EXCEST | executor of estate | \n The role played by a person acting as the estate executor for a deceased subscriber or policyholder who was the responsible party \r\n\n |
| 3 | GUADLTM | guardian ad lidem | \n The role played by a person appointed by the court to look out for the best interests of a minor child during the course of legal proceedings. \r\n\n |
| 3 | GUARD | guardian | \n The role played by a person or institution legally empowered with responsibility for the care of a ward. \r\n\n |
| 3 | POWATT | power of attorney | \n A relationship between two people in which one person authorizes another to act for him in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts. \r\n\n |
| 4 | DPOWATT | durable power of attorney | \n A relationship between two people in which one person authorizes another, usually a family member or relative, to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned. Unlike ordinary powers of attorney, durable powers can survive for long periods of time, and again, unlike standard powers of attorney, durable powers can continue after incompetency. \r\n\n |
| 4 | HPOWATT | healthcare power of attorney | \n A relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that continues (by its terms) to be effective even though the grantor has become mentally incompetent after signing the document. \r\n\n |
| 4 | SPOWATT | special power of attorney | \n A relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned. \r\n\n |
| 1 | (_AssignedRoleType) Abstract | ||
| 2 | (_AssignedNonPersonLivingSubjectRoleType) Abstract | \n \n Description:A role type that is used to further qualify a non-person subject playing a role where the role class attribute is set to RoleClass AssignedEntity \r\n\n | |
| 3 | ASSIST | Assistive non-person living subject | \n \n Description:Dogs trained to assist the ill or physically challenged. \r\n\n |
| 3 | BIOTH | Biotherapeutic non-person living subject | \n \n Description:Animals, including fish and insects, and microorganisms which may participate as assigned entities in biotherapies. \r\n\n |
| 4 | ANTIBIOT | Antibiotic | \n \n Description:Non-person living subject used as antibiotic. \r\n\n \n Examples:Bacteriophage, is a virus that infects bacteria. \r\n\n |
| 4 | DEBR | Debridement | \n \n Description:Maggots raised for biodebridement. \r\n\n \n Discussion: Maggot Debridement Therapy is the medical use of live maggots for cleaning non-healing wounds. \r\n\n \n Examples:Removal of burnt skin. \r\n\n |
| 3 | CCO | Clinical Companion | \n \n Description:Companion animals, such as dogs, cats, and rabbits, which may be provided to patients to improve general mood, decrease depression and loneliness, and distract from stress-inducing concerns to improve quality of life. \r\n\n |
| 3 | SEE | Seeing | \n \n Description:Dogs trained to assist persons who are seeing impaired or blind. \r\n\n |
| 3 | SNIFF | Sniffing | \n \n Description:Dogs trained or having the ability to detect imminent seizures or cancers in humans, probably as a result of volatile chemical (odors) given off by the malignancy of the host. \r\n\n |
| 1 | (_CertifiedEntityType) Abstract | \n Defines types of certifications for all entities \r\n\n | |
| 1 | _CitizenRoleType | CitizenRoleType | \n A role type used to qualify a person's legal status within a country or nation. \r\n\n |
| 2 | CAS | asylum seeker | \n A person who has fled his or her home country to find a safe place elsewhere. \r\n\n |
| 3 | CASM | single minor asylum seeker | \n A person who is someone of below legal age who has fled his or her home country, without his or her parents, to find a safe place elsewhere at time of categorization. \r\n\n |
| 2 | CN | national | \n A person who is legally recognized as a member of a nation or country, with associated rights and obligations. \r\n\n |
| 2 | CNRP | non-country member without residence permit | \n A foreigner who is present in a country (which is foreign to him/her) unlawfully or without the country's authorization (may be called an illegal alien). \r\n\n |
| 3 | CNRPM | non-country member minor without residence permit | \n A person who is below legal age present in a country, without his or her parents, (which is foreign to him/her) unlawfully or without the country's authorization. \r\n\n |
| 2 | CPCA | permit card applicant | \n A non-country member admitted to the territory of a nation or country as a non-resident for an explicit purpose. \r\n\n |
| 2 | CRP | non-country member with residence permit | \n A foreigner who is a resident of the country but does not have citizenship. \r\n\n |
| 3 | CRPM | non-country member minor with residence permit | \n A person who is a resident below legal age of the country without his or her parents and does not have citizenship. \r\n\n |
| 1 | (_ContactRoleType) Abstract | \n Types of contact for Role code "CON" \r\n\n | |
| 2 | (_AdministrativeContactRoleType) Abstract | \n A contact role used for business and/or administrative purposes. \r\n\n | |
| 3 | BILL | Billing Contact | \n A contact role used to identify a person within a Provider organization that can be contacted for billing purposes (e.g. about the content of the Invoice). \r\n\n |
| 3 | ORG | organizational contact | \n A contact for an organization for administrative purposes. Contact role specifies a person acting as a liason for the organization. \r\n\n Example: HR Department representative. \r\n\n |
| 3 | PAYOR | Payor Contact | \n A contact role used to identify a person within a Payor organization to whom this communication is addressed. \r\n\n |
| 2 | ECON Deprecated | emergency contact | \n A contact designated for contact in emergent situations. \r\n\n |
| 2 | NOK Deprecated | next of kin | \n Played by an individual who is designated as the next of kin for another individual which scopes the role. \r\n\n |
| 1 | (_IdentifiedEntityType) Abstract | \n \n Definition: A code representing the type of identifier that has been assigned to the identified entity (IDENT). \r\n\n \n Examples: Example values include Social Insurance Number, Product Catalog ID, Product Model Number. \r\n\n | |
| 2 | (_LocationIdentifiedEntityRoleCode) Abstract | \n \n Description:Describes types of identifiers other than the primary location registry identifier for a service delivery location. Identifiers may be assigned by a local service delivery organization, a formal body capable of accrediting the location for the capability to provide specific services or the identifier may be assigned at a jurisdictional level. \r\n\n | |
| 3 | ACHFID | accreditation location identifier | \n \n Description:Identifier assigned to a location by the organization responsible for accrediting the location. \r\n\n |
| 3 | JURID | jurisdiction location identifier | \n \n Description:Identifier assigned to a location by a jurisdiction. \r\n\n |
| 3 | LOCHFID | local location identifier | \n \n Description:Identifier assigned to a location by a local party (which could be the facility itself or organization overseeing a group of facilities). \r\n\n |
| 1 | (_LivingSubjectProductionClass) Abstract | \n Code indicating the primary use for which a living subject is bred or grown \r\n\n | |
| 2 | BF | Beef | \n Cattle used for meat production \r\n\n |
| 2 | BL | Broiler | \n Chickens raised for meat \r\n\n |
| 2 | BR | Breeder | \n Breeding/genetic stock \r\n\n |
| 2 | CO | Companion | \n Companion animals \r\n\n |
| 2 | DA | Dairy | \n Milk production \r\n\n |
| 2 | DR | Draft | \n Draft animals \r\n\n |
| 2 | DU | Dual | \n Dual purpose. Defined purposes based on species and breed \r\n\n |
| 2 | FI | Fiber | \n Animals raised for their fur, hair or skins \r\n\n |
| 2 | LY | Layer | \n Chickens raised for egg production \r\n\n |
| 2 | MT | Meat | \n Animals raised for meat production \r\n\n |
| 2 | MU | Multiplier | \n Poultry flocks used for chick/poult production \r\n\n |
| 2 | PL | Pleasure | \n Animals rasied for recreation \r\n\n |
| 2 | RC | Racing | \n Animals raised for racing perfomance \r\n\n |
| 2 | SH | Show | \n Animals raised for shows \r\n\n |
| 2 | VL | Veal | \n Cattle raised for veal meat production. Implicit is the husbandry method. \r\n\n |
| 2 | WL | Wool | \n Sheep, goats and other mammals raised for their fiber \r\n\n |
| 2 | WO | Working | \n Animals used to perform work \r\n\n |
| 1 | (_MedicationGeneralizationRoleType) Abstract | \n Identifies the specific hierarchical relationship between the playing and scoping medications. \r\n\n \n Examples: Generic, Generic Formulation, Therapeutic Class, etc. \r\n\n | |
| 2 | DC | therapeutic class | \n \n Description:A categorization of medicinal products by their therapeutic properties and/or main therapeutic use. \r\n\n |
| 2 | GD | generic drug | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients independent of strength, and form. \r\n\n The scoping entity identifies a unique combination of medicine ingredients; sometimes referred to as "ingredient set". \r\n\n |
| 3 | GDF | generic drug form | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients and dose form, independent of strength of the ingredients. The scoping entity identifies a unique combination of medicine ingredients in a specific dose form. \r\n\n |
| 3 | GDS | generic drug strength | \n Relates a manufactured drug product to the non-proprietary (generic) representation of is ingredients with their strength. The scoping entity identifies a unique combination of medicine ingredients with their strength. \r\n\n |
| 3 | GDSF | generic drug strength form | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients with their strength in a specific dose form. The scoping entity identifies a unique combination of medicine ingredients with their strength in a single dose form. \r\n\n |
| 2 | MGDSF | manufactured drug strength form | \n Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients with their strength in a specific dose form. The scoping entity identifies a unique combination of medicine ingredients with their strength in a single dose form. \r\n\n |
| 1 | (_MemberRoleType) Abstract | \n Types of membership for Role code "MBR" \r\n\n | |
| 2 | TRB | Tribal Member | \n A person who is a member of a tribe. \r\n\n |
| 1 | (_PersonalRelationshipRoleType) Abstract | ||
| 2 | FAMMEMB | family member | \n A relationship between two people characterizing their "familial" relationship \r\n\n |
| 3 | CHILD | child | \n The player of the role is a child of the scoping entity. \r\n\n |
| 4 | CHLDADOPT | adopted child | \n The player of the role is a child taken into a family through legal means and raised by the scoping person (parent) as his or her own child. \r\n\n |
| 5 | DAUADOPT | adopted daughter | \n The player of the role is a female child taken into a family through legal means and raised by the scoping person (parent) as his or her own child. \r\n\n |
| 5 | SONADOPT | adopted son | \n The player of the role is a male child taken into a family through legal means and raised by the scoping person (parent) as his or her own child. \r\n\n |
| 4 | CHLDFOST | foster child | \n The player of the role is a child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties. \r\n\n |
| 5 | DAUFOST | foster daughter | \n The player of the role is a female child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties. \r\n\n |
| 5 | SONFOST | foster son | \n The player of the role is a male child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties. \r\n\n |
| 4 | DAUC | daughter | \n \n Description: The player of the role is a female child (of any type) of scoping entity (parent) \r\n\n |
| 5 | DAUADOPT | ||
| 5 | DAUFOST | ||
| 5 | DAU | natural daughter | \n The player of the role is a female offspring of the scoping entity (parent). \r\n\n |
| 5 | STPDAU | stepdaughter | \n The player of the role is a daughter of the scoping person's spouse by a previous union. \r\n\n |
| 4 | NCHILD | natural child | \n The player of the role is an offspring of the scoping entity as determined by birth. \r\n\n |
| 5 | DAU | ||
| 5 | SON | natural son | \n The player of the role is a male offspring of the scoping entity (parent). \r\n\n |
| 4 | SONC | son | \n \n Description: The player of the role is a male child (of any type) of scoping entity (parent) \r\n\n |
| 5 | SONADOPT | ||
| 5 | SONFOST | ||
| 5 | SON | ||
| 5 | STPSON | stepson | \n The player of the role is a son of the scoping person's spouse by a previous union. \r\n\n |
| 4 | STPCHLD | step child | \n The player of the role is a child of the scoping person's spouse by a previous union. \r\n\n |
| 5 | STPDAU | ||
| 5 | STPSON | ||
| 3 | EXT | extended family member | \n \n Description: A family member not having an immediate genetic or legal relationship e.g. Aunt, cousin, great grandparent, grandchild, grandparent, niece, nephew or uncle. \r\n\n |
| 4 | AUNT | aunt | \n The player of the role is a sister of the scoping person's mother or father. \r\n\n |
| 5 | MAUNT | maternal aunt | \n \n Description:The player of the role is a biological sister of the scoping person's biological mother. \r\n\n |
| 5 | PAUNT | paternal aunt | \n \n Description:The player of the role is a biological sister of the scoping person's biological father. \r\n\n |
| 4 | COUSN | cousin | \n The player of the role is a relative of the scoping person descended from a common ancestor, such as a \tgrandparent, by two or more steps in a diverging line. \r\n\n |
| 5 | MCOUSN | maternal cousin | \n \n Description:The player of the role is a biological relative of the scoping person descended from a common ancestor on the player's mother's side, such as a grandparent, by two or more steps in a diverging line. \r\n\n |
| 5 | PCOUSN | paternal cousin | \n \n Description:The player of the role is a biological relative of the scoping person descended from a common ancestor on the player's father's side, such as a grandparent, by two or more steps in a diverging line. \r\n\n |
| 4 | GGRPRN | great grandparent | \n The player of the role is a parent of the scoping person's grandparent. \r\n\n |
| 5 | GGRFTH | great grandfather | \n The player of the role is the father of the scoping person's grandparent. \r\n\n |
| 6 | MGGRFTH | maternal great-grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological mother's parent. \r\n\n |
| 6 | PGGRFTH | paternal great-grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological father's parent. \r\n\n |
| 5 | GGRMTH | great grandmother | \n The player of the role is the mother of the scoping person's grandparent. \r\n\n |
| 6 | MGGRMTH | maternal great-grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological mother's parent. \r\n\n |
| 6 | PGGRMTH | paternal great-grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological father's parent. \r\n\n |
| 5 | MGGRPRN | maternal great-grandparent | \n \n Description:The player of the role is a biological parent of the scoping person's biological mother's parent. \r\n\n |
| 6 | MGGRFTH | ||
| 6 | MGGRMTH | ||
| 5 | PGGRPRN | paternal great-grandparent | \n \n Description:The player of the role is a biological parent of the scoping person's biological father's parent. \r\n\n |
| 6 | PGGRFTH | ||
| 6 | PGGRMTH | ||
| 4 | GRNDCHILD | grandchild | \n The player of the role is a child of the scoping person's son or daughter. \r\n\n |
| 5 | GRNDDAU | granddaughter | \n The player of the role is a daughter of the scoping person's son or daughter. \r\n\n |
| 5 | GRNDSON | grandson | \n The player of the role is a son of the scoping person's son or daughter. \r\n\n |
| 4 | GRPRN | grandparent | \n The player of the role is a parent of the scoping person's mother or father. \r\n\n |
| 5 | GRFTH | grandfather | \n The player of the role is the father of the scoping person's mother or father. \r\n\n |
| 6 | MGRFTH | maternal grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological mother. \r\n\n |
| 6 | PGRFTH | paternal grandfather | \n \n Description:The player of the role is the biological father of the scoping person's biological father. \r\n\n |
| 5 | GRMTH | grandmother | \n The player of the role is the mother of the scoping person's mother or father. \r\n\n |
| 6 | MGRMTH | maternal grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological mother. \r\n\n |
| 6 | PGRMTH | paternal grandmother | \n \n Description:The player of the role is the biological mother of the scoping person's biological father. \r\n\n |
| 5 | MGRPRN | maternal grandparent | \n \n Description:The player of the role is the biological parent of the scoping person's biological mother. \r\n\n |
| 6 | MGRFTH | ||
| 6 | MGRMTH | ||
| 5 | PGRPRN | paternal grandparent | \n \n Description:The player of the role is the biological parent of the scoping person's biological father. \r\n\n |
| 6 | PGRFTH | ||
| 6 | PGRMTH | ||
| 4 | INLAW | inlaw | \n A relationship between an individual and a member of their spousal partner's immediate family. \r\n\n |
| 5 | CHLDINLAW | child-in-law | \n The player of the role is the spouse of scoping person's child. \r\n\n |
| 6 | DAUINLAW | daughter in-law | \n The player of the role is the wife of scoping person's son. \r\n\n |
| 6 | SONINLAW | son in-law | \n The player of the role is the husband of scoping person's daughter. \r\n\n |
| 5 | PRNINLAW | parent in-law | \n The player of the role is the parent of scoping person's husband or wife. \r\n\n |
| 6 | FTHINLAW | father-in-law | \n The player of the role is the father of the scoping person's husband or wife. \r\n\n |
| 6 | MTHINLAW | mother-in-law | \n The player of the role is the mother of the scoping person's husband or wife. \r\n\n |
| 5 | SIBINLAW | sibling in-law | \n The player of the role is: (1) a sibling of the scoping person's spouse, or (2) the spouse of the scoping person's sibling, or (3) the spouse of a sibling of the scoping person's spouse. \r\n\n |
| 6 | BROINLAW | brother-in-law | \n The player of the role is: (1) a brother of the scoping person's spouse, or (2) the husband of the scoping person's sister, or (3) the husband of a sister of the scoping person's spouse. \r\n\n |
| 6 | SISINLAW | sister-in-law | \n The player of the role is: (1) a sister of the scoping person's spouse, or (2) the wife of the scoping person's brother, or (3) the wife of a brother of the scoping person's spouse. \r\n\n |
| 4 | NIENEPH | niece/nephew | \n The player of the role is a child of scoping person's brother or sister or of the brother or sister of the \tscoping person's spouse. \r\n\n |
| 5 | NEPHEW | nephew | \n The player of the role is a son of the scoping person's brother or sister or of the brother or sister of the \tscoping person's spouse. \r\n\n |
| 5 | NIECE | niece | \n The player of the role is a daughter of the scoping person's brother or sister or of the brother or sister of the \tscoping person's spouse. \r\n\n |
| 4 | UNCLE | uncle | \n The player of the role is a brother of the scoping person's mother or father. \r\n\n |
| 5 | MUNCLE | maternal uncle | \n \n Description:The player of the role is a biological brother of the scoping person's biological mother. \r\n\n |
| 5 | PUNCLE | paternal uncle | \n \n Description:The player of the role is a biological brother of the scoping person's biological father. \r\n\n |
| 3 | PRN | parent | \n The player of the role is one who begets, gives birth to, or nurtures and raises the scoping entity (child). \r\n\n |
| 4 | ADOPTP | adoptive parent | \n The player of the role (parent) has taken the scoper (child) into their family through legal means and raises them as his or her own child. \r\n\n |
| 5 | ADOPTF | adoptive father | \n The player of the role (father) is a male who has taken the scoper (child) into their family through legal means and raises them as his own child. \r\n\n |
| 5 | ADOPTM | adoptive mother | \n The player of the role (father) is a female who has taken the scoper (child) into their family through legal means and raises them as her own child. \r\n\n |
| 4 | FTH | father | \n The player of the role is a male who begets or raises or nurtures the scoping entity (child). \r\n\n |
| 5 | ADOPTF | ||
| 5 | FTHFOST | foster father | \n The player of the role (parent) who is a male state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary. \r\n\n The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child. \r\n\n |
| 5 | NFTH | natural father | \n The player of the role is a male who begets the scoping entity (child). \r\n\n |
| 6 | NFTHF | natural father of fetus | \n Indicates the biologic male parent of a fetus. \r\n\n |
| 5 | STPFTH | stepfather | \n The player of the role is the husband of scoping person's mother and not the scoping person's natural father. \r\n\n |
| 4 | MTH | mother | \n The player of the role is a female who conceives, gives birth to, or raises and nurtures the scoping entity (child). \r\n\n |
| 5 | ADOPTM | ||
| 5 | GESTM | gestational mother | \n The player is a female whose womb carries the fetus of the scoper. Generally used when the gestational mother and natural mother are not the same. \r\n\n |
| 5 | MTHFOST | foster mother | \n The player of the role (parent) who is a female state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary. \r\n\n The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child. \r\n\n |
| 5 | NMTH | natural mother | \n The player of the role is a female who conceives or gives birth to the scoping entity (child). \r\n\n |
| 6 | NMTHF | natural mother of fetus | \n The player is the biologic female parent of the scoping fetus. \r\n\n |
| 5 | STPMTH | stepmother | \n The player of the role is the wife of scoping person's father and not the scoping person's natural mother. \r\n\n |
| 4 | NPRN | natural parent | |
| 5 | NFTH | ||
| 5 | NMTH | ||
| 4 | PRNFOST | foster parent | \n The player of the role (parent) who is a state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary. \r\n\n The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child. \r\n\n |
| 5 | FTHFOST | ||
| 5 | MTHFOST | ||
| 4 | STPPRN | step parent | \n The player of the role is the spouse of the scoping person's parent and not the scoping person's natural parent. \r\n\n |
| 5 | STPFTH | ||
| 5 | STPMTH | ||
| 3 | SIB | sibling | \n The player of the role shares one or both parents in common with the scoping entity. \r\n\n |
| 4 | BRO | brother | \n The player of the role is a male sharing one or both parents in common with the scoping entity. \r\n\n |
| 5 | HBRO | half-brother | \n The player of the role is a male related to the scoping entity by sharing only one biological parent. \r\n\n |
| 5 | NBRO | natural brother | \n The player of the role is a male having the same biological parents as the scoping entity. \r\n\n |
| 6 | TWINBRO | twin brother | \n The scoper was carried in the same womb as the male player and shares common biological parents. \r\n\n |
| 7 | FTWINBRO | fraternal twin brother | \n The scoper was carried in the same womb as the male player and shares common biological parents but is the product of a distinct egg/sperm pair. \r\n\n |
| 7 | ITWINBRO | identical twin brother | \n The male scoper is an offspring of the same egg-sperm pair as the male player. \r\n\n |
| 5 | STPBRO | stepbrother | \n The player of the role is a son of the scoping person's stepparent. \r\n\n |
| 4 | HSIB | half-sibling | \n The player of the role is related to the scoping entity by sharing only one biological parent. \r\n\n |
| 5 | HBRO | ||
| 5 | HSIS | half-sister | \n The player of the role is a female related to the scoping entity by sharing only one biological parent. \r\n\n |
| 4 | NSIB | natural sibling | \n The player of the role has both biological parents in common with the scoping entity. \r\n\n |
| 5 | NBRO | ||
| 5 | NSIS | natural sister | \n The player of the role is a female having the same biological parents as the scoping entity. \r\n\n |
| 6 | TWINSIS | twin sister | \n The scoper was carried in the same womb as the female player and shares common biological parents. \r\n\n |
| 7 | FTWINSIS | fraternal twin sister | \n The scoper was carried in the same womb as the female player and shares common biological parents but is the product of a distinct egg/sperm pair. \r\n\n |
| 7 | ITWINSIS | identical twin sister | \n The female scoper is an offspring of the same egg-sperm pair as the female player. \r\n\n |
| 5 | TWIN | twin | \n The scoper and player were carried in the same womb and shared common biological parents. \r\n\n |
| 6 | TWINBRO | ||
| 6 | TWINSIS | ||
| 6 | FTWIN | fraternal twin | \n The scoper and player were carried in the same womb and share common biological parents but are the product of distinct egg/sperm pairs. \r\n\n |
| 7 | FTWINBRO | ||
| 7 | FTWINSIS | ||
| 6 | ITWIN | identical twin | \n The scoper and player are offspring of the same egg-sperm pair. \r\n\n |
| 7 | ITWINBRO | ||
| 7 | ITWINSIS | ||
| 4 | SIS | sister | \n The player of the role is a female sharing one or both parents in common with the scoping entity. \r\n\n |
| 5 | HSIS | ||
| 5 | NSIS | ||
| 5 | STPSIS | stepsister | \n The player of the role is a daughter of the scoping person's stepparent. \r\n\n |
| 4 | STPSIB | step sibling | \n The player of the role is a child of the scoping person's stepparent. \r\n\n |
| 5 | STPBRO | ||
| 5 | STPSIS | ||
| 3 | SIGOTHR | significant other | \n A person who is important to one's well being; especially a spouse or one in a similar relationship. (The player is the one who is important) \r\n\n |
| 4 | DOMPART | domestic partner | \n The player of the role cohabits with the scoping person but is not the scoping person's spouse. \r\n\n |
| 4 | FMRSPS | former spouse | \n Player of the role was previously joined to the scoping person in marriage and this marriage is now dissolved and inactive. \r\n\n \n Usage Note: This is significant to indicate as some jurisdictions have different legal requirements for former spouse to access the patient's record, from a general friend. \r\n\n |
| 4 | SPS | spouse | \n The player of the role is a marriage partner of the scoping person. \r\n\n |
| 5 | HUSB | husband | \n The player of the role is a man joined to a woman (scoping person) in marriage. \r\n\n |
| 5 | WIFE | wife | \n The player of the role is a woman joined to a man (scoping person) in marriage. \r\n\n |
| 2 | FRND | unrelated friend | \n The player of the role is a person who is known, liked, and trusted by the scoping person. \r\n\n |
| 2 | NBOR | neighbor | \n The player of the role lives near or next to the \tscoping person. \r\n\n |
| 2 | ONESELF | self | \n The relationship that a person has with his or her self. \r\n\n |
| 2 | ROOM | Roommate | \n One who shares living quarters with the subject. \r\n\n |
| 1 | (_PolicyOrProgramCoverageRoleType) Abstract | \n \n Description: A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria. \r\n\n Eligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law. These criteria may be: \r\n\n \n \n The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage \r\n\n \n \n May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent \r\n\n \n \n May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits. \r\n\n \n \n \n Discussion: The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role. For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead. \r\n\n In summary, the coded concepts in the Abstract Value Set "CoveredPartyRoleType" can be "post-coordinated" with the "RoleClassCoveredParty" Abstract Value Set. Decoupling these concepts is intended to support an expansive range of covered party concepts and their semantic comparability. \r\n\n | |
| 2 | (_CoverageRoleType) Abstract | \n Role recognized through the issuance of insurance coverage to an identified covered party who has this relationship with the policy holder such as the policy holder themselves (self), spouse, child, etc \r\n\n | |
| 3 | FAMDEP | family dependent | \n The player of the role is dependent of the scoping entity. \r\n\n |
| 3 | HANDIC | handicapped dependent | \n Covered party is a dependent of the policy holder with a physical or mental disability causing a disadvantage that makes independent achievement unusually difficult. \r\n\n |
| 3 | INJ | injured plaintiff | \n Covered party is an injured party with a legal claim for compensation against a policy holder under an insurance policy. \r\n\n |
| 3 | SELF | self | \n Covered party is the policy holder. Also known as the subscriber. \r\n\n |
| 3 | SPON | sponsored dependent | \n Covered party is an individual that the policy holder has assumed responsibility for, such as foster child or legal ward. \r\n\n |
| 3 | STUD | student | \n Covered party to an insurance policy has coverage through full-time or part-time attendance at a recognized educational institution as defined by a particular insurance policy. \r\n\n |
| 4 | FSTUD | full-time student | \n Covered party to an insurance policy has coverage through full-time attendance at a recognized educational institution as defined by a particular insurance policy. \r\n\n |
| 4 | PSTUD | part-time student | \n Covered party to an insurance policy has coverage through part-time attendance at a recognized educational institution as defined by a particular insurance policy. \r\n\n |
| 3 | ADOPT | adopted child | \n A child taken into one's family through legal means and raised as one's own child. \r\n\n |
| 3 | GCHILD | grandchild | \n A child of one's son or daughter. \r\n\n |
| 3 | GPARNT | grandparent | \n parent of a parent of the subject. \r\n\n |
| 3 | NAT | natural child | \n A child as determined by birth. \r\n\n |
| 3 | NIENE | niece/nephew | \n A child of one's brother or sister or of the brother or sister of one's spouse. \r\n\n |
| 3 | PARNT | parent | \n One that begets or brings forth offspring or a person who brings up and cares for for another (Webster's Collegiate Dictionary) \r\n\n |
| 3 | SPSE | spouse | \n A marriage partner; a husband or wife. \r\n\n |
| 3 | STEP | step child | \n A child receiving parental care and nurture from a person who is related to them through marriage to their parent. \r\n\n |
| 2 | (_CoveredPartyRoleType) Abstract | \n A role recognized through the eligibility of an identified living subject for benefits covered under an insurance policy or a program. Eligibility as a covered party may be conditioned on a relationship with (1) the policy holder such as the policy holder who is covered as an individual under a poliy or as a party sponsored for coverage by the policy holder. \r\n\n \n Example:An employee as a subscriber; or (2) on being scoped another covered party such as the subscriber, as in the case of a dependent. \r\n\n \n Discussion: The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". Other codes in the Abstract Value Set CoveredPartyRoleType domain can be "post-coordinated" with the EligiblePartyRoleType codes to denote comparable concepts. Decoupling the concepts is intended to support a wider range of concepts and semantic comparability of coded concepts. \r\n\n | |
| 3 | (_ClaimantCoveredPartyRoleType) Abstract | \n \n DescriptionA role recognized through the eligibility of a party play a claimant for benefits covered or provided under an insurance policy. \r\n\n | |
| 4 | CRIMEVIC | crime victim | \n \n Description: A person playing the role of program eligible under a program based on allegations of being the victim of a crime. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is "program eligible" and the person's status as a crime victim meets jurisdictional or program criteria. \r\n\n |
| 4 | INJWKR | injured worker | \n \n Description: A person playing the role of program eligible under a workers compensation program based on the filing of work-related injury claim. \r\n\n \n Discussion: This CoveredPartyRoleType.code is used when the CoveredPartyRole class code is either "program eligible", a "named insured", and "individual insured", or "dependent", and the person's status as differently abled or "handicapped" meets jurisdictional, policy, or program criteria. \r\n\n |
| 3 | (_DependentCoveredPartyRoleType) Abstract | \n \n Description: A role recognized through the eligibility of a party to play a dependent for benefits covered or provided under a health insurance policy because of an association with the subscriber that is recognized by the policy underwriter. \r\n\n | |
| 4 | COCBEN | continuity of coverage beneficiary | \n \n Description: A person playing the role of an individual insured with continuity of coverage under a policy which is being terminated based on loss of original status that was the basis for coverage. Criteria for qualifying for continuity of coverage may be set by law. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a continuity of coverage beneficiary meets jurisdictional or policy criteria. \r\n\n |
| 4 | DIFFABL | differently abled | \n \n Description: A person playing the role of program eligible under a program based on meeting criteria for health or functional limitation set by law or by the program. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible", "named insured", "individual insured", or "dependent", and the person's status as differently abled meets jurisdictional, policy, or program criteria. \r\n\n |
| 4 | WARD | ward | \n \n Description: A person, who is a minor or is deemed incompetent, who plays the role of a program eligible where eligibility for coverage is based on meeting program eligibility criteria for status as a ward of a court or jurisdiction. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is a "claimant", "program eligible", a "named insured", an "individual Insured" or a "dependent", and the person's status as a ward meets program or policy criteria. In the case of a ward covered under a program providing financial or health benefits, a governmental agency may take temporary custody of a minor or incompetent for his/her protection and care, e.g., if the ward is suffering from neglect or abuse, or has been in trouble with the law. \r\n\n |
| 3 | (_IndividualInsuredPartyRoleType) Abstract | \n A role recognized through the eligibility of a party to play an individual insured for benefits covered or provided under an insurance policy where the party is also the policy holder. \r\n\n | |
| 4 | COCBEN | ||
| 4 | RETIREE | retiree | \n \n Description: A person playing the role of an individual insured under a policy based on meeting criteria for the employment status of retired set by law or the policy. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a retiree meets jurisdictional or policy criteria. \r\n\n |
| 3 | (_ProgramEligiblePartyRoleType) Abstract | \n \n Description:A role recognized through the eligibility of a party to play a program eligible for benefits covered or provided under a program. \r\n\n | |
| 4 | CRIMEVIC | ||
| 4 | INJWKR | ||
| 4 | DIFFABL | ||
| 4 | WARD | ||
| 4 | INDIG | member of an indigenous people | \n \n Description: A person playing the role of program eligible under a program based on aboriginal ancestry or as a member of an aboriginal community. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is "program eligible" and the person's status as a member of an indigenous people meets jurisdictional or program criteria. \r\n\n |
| 4 | MIL | military | \n \n Definition: A person playing the role of program eligible under a program based on military status. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a member of the military meets jurisdictional or program criteria \r\n\n |
| 5 | ACTMIL | active duty military | \n \n Description: A person playing the role of program eligible under a program based on active military status. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the persons status as active duty military meets jurisdictional or program criteria. \r\n\n |
| 5 | RETMIL | retired military | \n \n Description: A person playing the role of program eligible under a program based on retired military status. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the persons status as retired military meets jurisdictional or program criteria. \r\n\n |
| 5 | VET | veteran | \n \n Description: A person playing the role of program eligible under a program based on status as a military veteran. \r\n\n \n Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the persons status as a veteran meets jurisdictional or program criteria. \r\n\n |
| 3 | (_SubscriberCoveredPartyRoleType) Abstract | \n \n Description: A role recognized through the eligibility of a party to play a subscriber for benefits covered or provided under a health insurance policy. \r\n\n | |
| 4 | COCBEN | ||
| 4 | RETIREE | ||
| 4 | MIL | ||
| 1 | (_ResearchSubjectRoleBasis) Abstract | \n Specifies the administrative functionality within a formal experimental design for which the ResearchSubject role was established. Examples: screening - role is used for pre-enrollment evaluation portion of the design; enrolled - role is used for subjects admitted to the active treatment portion of the design. \r\n\n | |
| 2 | ERL | enrollment | \n \n Definition:The specific role being played by a research subject participating in the active treatment or primary data collection portion of a research study. \r\n\n |
| 2 | SCN | screening | \n \n Definition:The specific role being played by a research subject participating in the pre-enrollment evaluation portion of a research study. \r\n\n |
| 1 | (_ServiceDeliveryLocationRoleType) Abstract | \n A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered. \r\n\n | |
| 2 | (_DedicatedServiceDeliveryLocationRoleType) Abstract | \n A role of a place that further classifies a setting that is intended to house the provision of services. \r\n\n | |
| 3 | (_DedicatedClinicalLocationRoleType) Abstract | \n A role of a place that further classifies the clinical setting (e.g., cardiology clinic, primary care clinic, rehabilitation hospital, skilled nursing facility) in which care is delivered during an encounter. \r\n\n | |
| 4 | DX | Diagnostics or therapeutics unit | \n A practice setting where diagnostic procedures or therapeutic interventions are performed \r\n\n |
| 5 | CVDX | Cardiovascular diagnostics or therapeutics unit | \n A practice setting where cardiovascular diagnostic procedures or therapeutic interventions are performed (e.g., cardiac catheterization lab, echocardiography suite) \r\n\n |
| 6 | CATH | Cardiac catheterization lab | |
| 6 | ECHO | Echocardiography lab | |
| 5 | GIDX | Gastroenterology diagnostics or therapeutics lab | \n A practice setting where GI procedures (such as endoscopies) are performed \r\n\n |
| 6 | ENDOS | Endoscopy lab | \n (X12N 261QD0000N) \r\n\n |
| 5 | RADDX | Radiology diagnostics or therapeutics unit | \n A practice setting where radiology services (diagnostic or therapeutic) are provided (X12N 261QR0200N) \r\n\n |
| 6 | RADO | Radiation oncology unit | \n (X12N 261QX0203N) \r\n\n |
| 6 | RNEU | Neuroradiology unit | |
| 4 | HOSP | Hospital | \n An acute care institution that provides medical, surgical, or psychiatric care and treatment for the sick or the injured. \r\n\n |
| 5 | CHR | Chronic Care Facility | \n (1) A hospital including a physical plant and personnel that provides multidisciplinary diagnosis and treatment for diseases that have one or more of the following characteristics: is permanent; leaves residual disability; is caused by nonreversible pathological alteration; requires special training of the patient for rehabilitation; and/or may be expected to require a long period of supervision or care. In addition, patients require the safety, security, and shelter of these specialized inpatient or partial hospitalization settings. (2) A hospital that provides medical and skilled nursing services to patients with long-term illnesses who are not in an acute phase but who require an intensity of services not available in nursing homes \r\n\n |
| 5 | GACH | Hospitals; General Acute Care Hospital | \n (X12N 282N00000N) \r\n\n |
| 5 | MHSP | Military Hospital | \n A health care facility operated by the Department of Defense or other military operation. \r\n\n |
| 5 | PSYCHF | Psychatric Care Facility | \n Healthcare facility that cares for patients with psychiatric illness(s). \r\n\n |
| 5 | RH | Rehabilitation hospital | \n (X12N 283X00000N) \r\n\n |
| 6 | RHAT | addiction treatment center | \n \n Description: A location that plays the role of delivering services which may include life training and/or social support to people with addictions. \r\n\n |
| 6 | RHII | intellectual impairment center | \n \n Description: A location that plays the role of delivering services which may include adaptation, rehabilitation and social integration services for people with intellectual and/or pervasive development disorders such as autism or severe behaviour disorder. \r\n\n |
| 6 | RHMAD | parents with adjustment difficulties center | \n \n Description: A location that plays the role of delivering services which may social support services for adolescents who are pregnant or have child and are experiencing adaptation issues/difficulties in their current or eventual parenting role. \r\n\n |
| 6 | RHPI | physical impairment center | \n \n Description: A location that plays the role of delivering services which may include adaptation, rehabilitation and social integration services for people with physical impairments. \r\n\n |
| 7 | RHPIH | physical impairment - hearing center | \n \n Description: A location that plays the role of delivering services for people with hearing impairments. \r\n\n |
| 7 | RHPIMS | physical impairment - motor skills center | \n \n Description: A location that plays the role of delivering services for people with motor skill impairments. \r\n\n |
| 7 | RHPIVS | physical impairment - visual skills center | \n \n Description: A location that plays the role of delivering services for people with visual skill impairments. \r\n\n |
| 6 | RHYAD | youths with adjustment difficulties center | \n \n Description: A location that plays the role of delivering services which may include life training and/or social support services for the adaption, rehabilitation and social integration of youths with adjustment difficulties. \r\n\n |
| 4 | HU | Hospital unit | |
| 5 | BMTU | Bone marrow transplant unit | |
| 5 | CCU | Coronary care unit | |
| 5 | CHEST | Chest unit | \n A specialty unit in hospital that focuses on chronic respirator patients and pulmonary failure \r\n\n |
| 5 | EPIL | Epilepsy unit | |
| 5 | ER | Emergency room | \n The section of a health care facility for providing rapid treatment to victims of sudden illness or trauma. \r\n\n |
| 6 | ETU | Emergency trauma unit | |
| 5 | HD | Hemodialysis unit | |
| 5 | HLAB | hospital laboratory | \n \n Description: A location that plays the role of delivering services which may include tests done based on clinical specimens to get health information about a patient as pertaining to the diagnosis, treatment and prevention of disease. Hospital laboratories may be further divided into specialized units such as Anatomic Pathology, Microbiology, and Biochemistry. \r\n\n |
| 6 | INLAB | inpatient laboratory | \n \n Description: A location that plays the role of delivering services which may include tests are done on clinical specimens to get health information about a patient pertaining to the diagnosis, treatment, and prevention of disease for a hospital visit longer than one day. \r\n\n |
| 6 | OUTLAB | outpatient laboratory | \n \n Description: A location that plays the role of delivering services which may include tests are done on clinical specimens to get health information about a patient pertaining to the diagnosis, treatment, and prevention of disease for same day visits. \r\n\n |
| 5 | HRAD | radiology unit | \n \n Description: A location that plays the role of delivering services which may include the branch of medicine that uses ionizing and non-ionizing radiation to diagnose and treat diseases. The radiology unit may be further divided into subspecialties such as Imaging, Cardiovascular, Thoracic, and Ultrasound. \r\n\n |
| 5 | HUSCS | specimen collection site | \n \n Description: A location that plays the role of delivering services which may include collecting specimens and/or samples from patients for laboratory testing purposes, but does not perform any tests or analysis functions. \r\n\n |
| 5 | ICU | Intensive care unit | |
| 6 | PEDICU | Pediatric intensive care unit | |
| 7 | PEDNICU | Pediatric neonatal intensive care unit | |
| 5 | INPHARM | inpatient pharmacy | \n \n Description: A location that plays the role of delivering services which may include providing judicious, safe, efficacious, appropriate and cost effective use of medicines for treatment of patients for visits longer than one day. The distinction between inpatient pharmacies and retail (or outpatient) pharmacies is that they are part of a patient's continuity of care while staying in the hospital. \r\n\n |
| 5 | MBL | medical laboratory | \n \n Description: A location that plays the role of delivering services which include biochemistry, hematology, microbiology, immunochemistry, and toxicology. \r\n\n |
| 5 | NCCS | Neurology critical care and stroke unit | |
| 5 | NS | Neurosurgery unit | |
| 5 | OUTPHARM | outpatient pharmacy | \n \n Description: A location that plays the role of delivering services which may include providing judicious, safe, efficacious, appropriate and cost effective use of medicines for treatment of patients for outpatient visits and may also be used for discharge prescriptions. \r\n\n |
| 5 | PEDU | Pediatric unit | |
| 6 | PEDICU | ||
| 5 | PHU | Psychiatric hospital unit | \n (X12N 273R00000N) \r\n\n |
| 5 | RHU | Rehabilitation hospital unit | |
| 5 | SLEEP | Sleep disorders unit | \n (X12N 261QA1200N) \r\n\n |
| 4 | NCCF | Nursing or custodial care facility | |
| 5 | SNF | Skilled nursing facility | \n (X12N 314000000N) \r\n\n |
| 4 | OF | Outpatient facility | |
| 5 | ALL | Allergy clinic | |
| 5 | AMPUT | Amputee clinic | |
| 5 | BMTC | Bone marrow transplant clinic | |
| 5 | BREAST | Breast clinic | |
| 5 | CANC | Child and adolescent neurology clinic | |
| 5 | CAPC | Child and adolescent psychiatry clinic | |
| 5 | CARD | Ambulatory Health Care Facilities; Clinic/Center; Rehabilitation: Cardiac Facilities | |
| 6 | PEDCARD | Pediatric cardiology clinic | |
| 5 | COAG | Coagulation clinic | |
| 5 | CRS | Colon and rectal surgery clinic | |
| 5 | DERM | Dermatology clinic | |
| 5 | ENDO | Endocrinology clinic | |
| 6 | PEDE | Pediatric endocrinology clinic | |
| 5 | ENT | Otorhinolaryngology clinic | |
| 5 | FMC | Family medicine clinic | |
| 5 | GI | Gastroenterology clinic | |
| 6 | PEDGI | Pediatric gastroenterology clinic | |
| 5 | GIM | General internal medicine clinic | |
| 5 | GYN | Gynecology clinic | |
| 5 | HEM | Hematology clinic | |
| 6 | PEDHEM | Pediatric hematology clinic | |
| 5 | HTN | Hypertension clinic | |
| 5 | IEC | Impairment evaluation center | \n Focuses on assessing disability \r\n\n |
| 5 | INFD | Infectious disease clinic | |
| 6 | PEDID | Pediatric infectious disease clinic | |
| 5 | INV | Infertility clinic | |
| 5 | LYMPH | Lympedema clinic | |
| 5 | MGEN | Medical genetics clinic | |
| 5 | NEPH | Nephrology clinic | |
| 6 | PEDNEPH | Pediatric nephrology clinic | |
| 5 | NEUR | Neurology clinic | |
| 5 | OB | Obstetrics clinic | |
| 5 | OMS | Oral and maxillofacial surgery clinic | |
| 5 | ONCL | Medical oncology clinic | |
| 6 | PEDHO | Pediatric oncology clinic | |
| 5 | OPH | Opthalmology clinic | |
| 5 | OPTC | optometry clinic | \n \n Description: A location that plays the role of delivering services which may include examination, diagnosis, treatment, management, and prevention of diseases and disorders of the eye as well as prescribing and fitting appropriate corrective lenses (glasses or contact lenses) as needed. Optometry clinics may also provide tests for visual field screening, measuring intra-ocular pressure and ophthalmoscopy, as and when required. \r\n\n |
| 5 | ORTHO | Orthopedics clinic | |
| 6 | HAND | Hand clinic | |
| 5 | PAINCL | Pain clinic | \n (X12N 261QP3300N) \r\n\n |
| 5 | PC | Primary care clinic | \n (X12N 261QP2300N) \r\n\n |
| 5 | PEDC | Pediatrics clinic | |
| 6 | PEDCARD | ||
| 6 | PEDE | ||
| 6 | PEDGI | ||
| 6 | PEDHEM | ||
| 6 | PEDID | ||
| 6 | PEDNEPH | ||
| 6 | PEDHO | ||
| 6 | PEDRHEUM | Pediatric rheumatology clinic | |
| 5 | POD | Podiatry clinic | \n (X12N 261QP1100N) \r\n\n |
| 5 | PREV | Preventive medicine clinic | |
| 5 | PROCTO | Proctology clinic | |
| 5 | PROFF | Provider's Office | \n Location where healthcare service was delivered, identified as the healthcare provider's practice office. \r\n\n |
| 5 | PROS | Prosthodontics clinic | |
| 5 | PSI | Psychology clinic | |
| 5 | PSY | Psychiatry clinic | |
| 5 | RHEUM | Rheumatology clinic | |
| 6 | PEDRHEUM | ||
| 5 | SPMED | Sports medicine clinic | |
| 5 | SU | Surgery clinic | |
| 6 | PLS | Plastic surgery clinic | |
| 6 | URO | Urology clinic | |
| 5 | TR | Transplant clinic | |
| 5 | TRAVEL | Travel and geographic medicine clinic | |
| 5 | WND | Wound clinic | |
| 4 | RTF | Residential treatment facility | |
| 5 | PRC | Pain rehabilitation center | |
| 5 | SURF | Substance use rehabilitation facility | \n (X12N 324500000N) \r\n\n |
| 3 | (_DedicatedNonClinicalLocationRoleType) Abstract | \n A role of a place that further classifies a setting that is intended to house the provision of non-clinical services. \r\n\n | |
| 4 | DADDR | Delivery Address | \n Location address where medical supplies were transported to for use. \r\n\n |
| 4 | MOBL | Mobile Unit | \n Location (mobile) where healthcare service was delivered. \r\n\n |
| 5 | AMB | Ambulance | \n Location (mobile) where healthcare service was delivered, identified specifically as an ambulance. \r\n\n |
| 4 | PHARM | Pharmacy | \n Location where healthcare service was delivered, identified as a pharmacy. \r\n\n |
| 5 | INPHARM | ||
| 5 | OUTPHARM | ||
| 2 | (_IncidentalServiceDeliveryLocationRoleType) Abstract | ||
| 3 | ACC | accident site | \n Location of an accident where healthcare service was delivered, such as a roadside. \r\n\n |
| 3 | COMM | Community Location | \n Community location where healthcare is delivered. \r\n\n |
| 4 | CSC | community service center | \n \n Description: A location that plays the role of delivering services which may include providing front-line services to the population of a defined geographic area such as: healthcare services and social services, preventive or curative, rehabilitation or reintegration. \r\n\n |
| 3 | PTRES | Patient's Residence | \n location where healthcare was delivered which is the residence of the Patient. \r\n\n |
| 3 | SCHOOL | school | \n Location where healthcare service was delivered, identified as a school or educational facility. \r\n\n |
| 3 | UPC | underage protection center | \n \n Description: A location that plays the role of delivering services which may include: social emergency services required for a young person as required under any jurisdictional youth laws, child placement, and family mediation in the defined geographical area the SDL is responsible for. It may provide expertise in a judiciary setting on child custody, adoption and biological history research. \r\n\n |
| 3 | WORK | work site | \n Location where healthcare service was delivered, identified as a work place. \r\n\n |
| 1 | (_SpecimenRoleType) Abstract | ||
| 2 | C | Calibrator | \n A specimen used for initial calibration settings of an instrument \r\n\n |
| 2 | G | Group | \n A set of patient samples in which the individuals of the group may or may not be identified. \r\n\n |
| 2 | L | Pool | \n Aliquots of individual specimens combined to form a single specimen representing all of the included individuals. \r\n\n |
| 2 | P | Patient | \n A specimen that has been collected from a patient. \r\n\n |
| 2 | Q | Quality Control | \n A specimen specifically used to verify the sensitivity, specificity, accuracy or other perfomance parameter of a diagnostic test. \r\n\n |
| 3 | B | Blind | \n Quality Control specimen submitted to the lab whose identity and composition is not known to the lab. \r\n\n |
| 3 | E | Electronic QC | \n An electronically simulated QC specimen \r\n\n |
| 3 | F | Filler Proficiency | \n Specimen used for testing proficiency of an organization performing testing (how does this differ from O?) \r\n\n |
| 3 | O | Operator Proficiency | \n A specimen used for evaluation of operator proficiency (operator in what context?) \r\n\n |
| 3 | V | Verifying | \n A specimen used for periodic calibration checks of instruments \r\n\n |
| 2 | R | Replicate | \n A portion of an original patent sample that is tested at the same time as the original sample \r\n\n |
| 1 | CLAIM | claimant | \n A party that makes a claim for coverage under a policy. \r\n\n |
| 1 | communityLaboratory | Community Laboratory | |
| 1 | GT | Guarantor | \n An individual or organization that makes or gives a promise, assurance, pledge to pay or has paid the healthcare service provider. \r\n\n |
| 1 | homeHealth | Home Health | |
| 1 | laboratory | Laboratory | |
| 1 | pathologist | Pathologist | |
| 1 | PH | Policy Holder | \n Policy holder for the insurance policy. \r\n\n |
| 1 | phlebotomist | Phlebotomist | |
| 1 | PROG | program eligible | \n A party that meets the eligibility criteria for coverage under a program. \r\n\n |
| 1 | PT | Patient | \n The recipient for the service(s) and/or product(s) when they are not the covered party. \r\n\n |
| 1 | subject | Self | |
| 1 | thirdParty | Third Party | |
| 1 | DEP | ||
| 1 | DEPEN | dependent | \n A party covered under a policy based on association with a subscriber. \r\n\n |
| 1 | FM | Family Member | \n A member of the covered party's family. This could be the spouse, a parent, a grand parent, a sibling, etc. \r\n\n |
| 1 | INDIV | individual | \n A party covered under a policy as the policyholder. \r\n\n |
| 1 | NAMED | named insured | \n A party to an insurance policy to whom the insurer agrees to indemnify for losses, provides benefits for, or renders services. \r\n\n |
| 1 | PSYCHCF | ||
| 1 | SUBSCR | subscriber | \n A party covered under a policy based on association with a sponsor who is the policy holder, and whose association may provide for the eligibility of dependents for coverage \r\n\n |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | XMLV1PR1 | XMLV1PR1 | \n XML ITS version 1 pre-release 1. \r\n\n |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_GeneticObservationInterpretation) Abstract | \n Codes that specify interpretation of genetic analysis, such as "positive", "negative", "carrier", "responsive", etc. \r\n\n | |
| 2 | CAR | Carrier | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n |
| 2 | Carrier Deprecated | Carrier | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n \n \n Deprecation Comment: \n This code is currently the same string as the print name for this concept and is inconsistent with the conventions being used for the other codes in the coding system, as it is a full word with initial capitalization, rather than an all upper case mnemonic. The recommendation from OO is to deprecate the code "Carrier" and to add "CAR" as the new active code representation for this concept. \r\n\n |
| 1 | (_ObservationInterpretationChange) Abstract | \n Interpretations of change of quantity and/or severity. At most one of B or W and one of U or D allowed. \r\n\n | |
| 2 | B | Better | \n The current result or observation value has improved compared to the previous result or observation value (the change is significant as defined in the respective test procedure). \r\n\n [Note: This can be applied to quantitative or qualitative observations.] \r\n\n |
| 2 | D | Significant change down | \n The current result has decreased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure). \r\n\n |
| 2 | U | Significant change up | \n The current result has increased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure). \r\n\n |
| 2 | W | Worse | \n The current result or observation value has degraded compared to the previous result or observation value (the change is significant as defined in the respective test procedure). \r\n\n [Note: This can be applied to quantitative or qualitative observations.] \r\n\n |
| 1 | (_ObservationInterpretationExceptions) Abstract | \n Technical exceptions resulting in the inability to provide an interpretation. At most one allowed. Does not imply normality or severity. \r\n\n | |
| 2 | < | Off scale low | \n The result is below the minimum detection limit (the test procedure or equipment is the limiting factor). \r\n\n Synonyms: Below analytical limit, low off scale. \r\n\n |
| 2 | > | Off scale high | \n The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor). \r\n\n Synonyms: Above analytical limit, high off scale. \r\n\n |
| 2 | AC Deprecated | Anti-complementary substances present | \n A valid result cannot be obtained for the specified component / analyte due to the presence of anti-complementary substances in the sample. \r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. \r\n\n |
| 2 | IE | Insufficient evidence | \n There is insufficient evidence that the species in question is a good target for therapy with the drug. A categorical interpretation is not possible. \r\n\n [Note: A MIC with "IE" and/or a comment may be reported (without an accompanying S, I or R-categorization).] \r\n\n |
| 2 | QCF Deprecated | Quality control failure | \n A result cannot be considered valid for the specified component / analyte or organism due to failure in the quality control testing component. \r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. \r\n\n |
| 2 | TOX Deprecated | Cytotoxic substance present | \n A valid result cannot be obtained for the specified organism or cell line due to the presence of cytotoxic substances in the sample or culture. \r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. \r\n\n |
| 1 | (_ObservationInterpretationNormality) Abstract | \n Interpretation of normality or degree of abnormality (including critical or "alert" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed. \r\n\n | |
| 2 | A | Abnormal | \n The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure). \r\n\n [Note: Typically applies to non-numeric results.] \r\n\n |
| 3 | AA | Critical abnormal | \n The result or observation value is outside a reference range or expected norm at a level at which immediate action should be considered for patient safety (as defined for the respective test procedure). \r\n\n [Note: Typically applies to non-numeric results. Analogous to critical/panic limits for numeric results.] \r\n\n |
| 4 | HH | Critical high | \n The result for a quantitative observation is above a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure). \r\n\n Synonym: Above upper panic limits. \r\n\n |
| 4 | LL | Critical low | \n The result for a quantitative observation is below a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure). \r\n\n Synonym: Below lower panic limits. \r\n\n |
| 3 | H | High | \n The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure). \r\n\n Synonym: Above high normal \r\n\n |
| 4 | H> Deprecated | Significantly high | A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'H' and 'HH'.] \r\n\n \n Deprecation Comment: The code 'H>' is being deprecated in order to align with the use of the code 'HU' for "Very high" in V2 Table 0078 "Interpretation Codes". \r\n\n [Note: The use of code 'H>' is non-preferred, as this code is deprecated and on track to be retired; use code 'HU' instead. \r\n\n |
| 5 | HH | ||
| 4 | HU | Significantly high | \n A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician. \r\n\n |
| 5 | HH | ||
| 3 | L | Low | \n The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure). \r\n\n Synonym: Below low normal \r\n\n |
| 4 | L< Deprecated | Significantly low | A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'L' and 'LL'.] \r\n\n \n Deprecation Comment: The code 'L<' is being deprecated in order to align with the use of the code 'LU' for "Very low" in V2 Table 0078 "Interpretation Codes". \r\n\n [Note: The use of code 'L<' is non-preferred, as this code is deprecated and on track to be retired; use code 'LU' instead. \r\n\n |
| 5 | LL | ||
| 4 | LU | Significantly low | \n A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician. \r\n\n |
| 5 | LL | ||
| 2 | N | Normal | \n The result or observation value is within the reference range or expected norm (as defined for the respective test procedure). \r\n\n [Note: Applies to numeric or non-numeric results.] \r\n\n |
| 1 | (_ObservationInterpretationSusceptibility) Abstract | \n Interpretations of anti-microbial susceptibility testing results (microbiology). At most one allowed. \r\n\n | |
| 2 | IE | ||
| 2 | I | Intermediate | \n Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with uncertain therapeutic effect. Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)\nProjects: ISO 20776-1, ISO 20776-2 \r\n\n [Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.] \r\n\n [Note 2: This class of susceptibility implies that an infection due to the isolate can be appropriately treated in body sites where the drugs are physiologically concentrated or when a high dosage of drug can be used.] \r\n\n [Note 3: This class also indicates a "buffer zone," to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.] \r\n\n [Note 4: These breakpoints can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).] \r\n\n |
| 2 | MS Deprecated | moderately susceptible | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n \n \n Deprecation Comment: \n This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012). \r\n\n |
| 2 | NCL | No CLSI defined breakpoint | \n Use when not enough clinical trial data published by the Clinical and Laboratory Standards Institutes (CLSI) is available to establish the breakpoints for susceptible / intermediate and resistant. \r\n\n |
| 2 | NS | Non-susceptible | \n A category used for isolates for which only a susceptible interpretive criterion has been designated because of the absence or rare occurrence of resistant strains. Isolates that have MICs above or zone diameters below the value indicated for the susceptible breakpoint should be reported as non-susceptible. \r\n\n NOTE 1: An isolate that is interpreted as non-susceptible does not necessarily mean that the isolate has a resistance mechanism. It is possible that isolates with MICs above the susceptible breakpoint that lack resistance mechanisms may be encountered within the wild-type distribution subsequent to the time the susceptible-only breakpoint is set. \r\n\n NOTE 2: For strains yielding results in the "nonsusceptible" category, organism identification and antimicrobial susceptibility test results should be confirmed. \r\n\n Synonym: decreased susceptibility. \r\n\n |
| 2 | R | Resistant | \n Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic failure.\nReference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) \nProjects: ISO 20776-1, ISO 20776-2 \r\n\n [Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.] \r\n\n [Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).] \r\n\n |
| 3 | SYN-R | Synergy - resistant | \n A category for isolates where the bacteria (e.g. enterococci) are not susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent). This is predictive that this combination therapy will not be effective. \r\n\n \n Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside. \r\n\n \n Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found. \r\n\n |
| 2 | S | Susceptible | \n Bacterial strain inhibited by in vitro concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic success.\nReference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)\nSynonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2 \r\n\n [Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.] \r\n\n [Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).] \r\n\n |
| 3 | SDD | Susceptible-dose dependent | \n A category that includes isolates with antimicrobial agent minimum inhibitory concentrations (MICs) that approach usually attainable blood and tissue levels and for which response rates may be lower than for susceptible isolates. \r\n\n Reference: CLSI document M44-A2 2009 "Method for antifungal disk diffusion susceptibility testing of yeasts; approved guideline - second edition" - page 2. \r\n\n |
| 3 | SYN-S | Synergy - susceptible | \n A category for isolates where the bacteria (e.g. enterococci) are susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent). This is predictive that this combination therapy will be effective. \r\n\n \n Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside. \r\n\n \n Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found. \r\n\n |
| 2 | VS Deprecated | very susceptible | \n The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder. \r\n\n \n \n Deprecation Comment: \n This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012). \r\n\n |
| 1 | EX | outside threshold | \n The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.\n \r\n\n Example: A positive result on a Hepatitis screening test.\n Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects.\nThese concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes.\nMembers of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held. \r\n\n |
| 2 | HX | above high threshold | \n The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.\n \r\n\n Example: A positive result on a Hepatitis screening test.\n Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held. \r\n\n |
| 2 | LX | below low threshold | \n The numeric observation/test result is interpreted as being below the low threshold value for a particular protocol within which the result is being reported. \r\n\n Example: A Total White Blood Cell Count falling below a protocol-defined threshold value of 3000/mm^3\n Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held. \r\n\n |
| 1 | HM Deprecated | Hold for Medical Review | \n Hold for Medical Review \r\n\n \n Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 "Interpretation Codes." \r\n\n |
| 1 | (ObservationInterpretationDetection) Abstract | \n Interpretations of the presence or absence of a component / analyte or organism in a test or of a sign in a clinical observation. In keeping with laboratory data processing practice, these concepts provide a categorical interpretation of the "meaning" of the quantitative value for the same observation. \r\n\n | |
| 2 | IND | Indeterminate | \n The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure. \r\n\n \n Usage Note: For example, if the specimen was degraded, poorly processed, or was missing the required anatomic structures, then "indeterminate" (i.e. "cannot be determined") is the appropriate response, not "equivocal". \r\n\n |
| 3 | E | Equivocal | \n The test or procedure was successfully performed, but the results are borderline and can neither be declared positive / negative nor detected / not detected according to the current established criteria. \r\n\n |
| 2 | NEG | Negative | \n An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure. \r\n\n [Note: Negative does not necessarily imply the complete absence of the specified item.] \r\n\n |
| 3 | ND | Not detected | \n The presence of the specified component / analyte, organism or clinical sign could not be determined within the limit of detection of the performed test or procedure. \r\n\n |
| 2 | POS | Positive | \n A presence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure. \r\n\n |
| 3 | DET | Detected | \n The measurement of the specified component / analyte, organism or clinical sign above the limit of detection of the performed test or procedure. \r\n\n |
| 1 | (ObservationInterpretationExpectation) Abstract | \n Interpretation of the observed result taking into account additional information (contraindicators) about the patient's situation. Concepts in this category are mutually exclusive, i.e., at most one is allowed. \r\n\n | |
| 2 | EXP | Expected | \n This result has been evaluated in light of known contraindicators. Once those contraindicators have been taken into account the result is determined to be "Expected" (e.g., presence of drugs in a patient that is taking prescription medication for pain management). \r\n\n |
| 2 | UNE | Unexpected | \n This result has been evaluated in light of known contraindicators. Once those contraindicators have been taken into account the result is determined to be "Unexpected" (e.g., presence of non-prescribed drugs in a patient that is taking prescription medication for pain management). \r\n\n |
| 1 | OBX Deprecated | Interpretation qualifiers in separate OBX segments | \n Interpretation qualifiers in separate OBX segments \r\n\n \n Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 "Interpretation Codes." \r\n\n |
| 1 | (ReactivityObservationInterpretation) Abstract | \n Interpretations of the presence and level of reactivity of the specified component / analyte with the reagent in the performed laboratory test. \r\n\n | |
| 2 | NR | Non-reactive | \n An absence finding used to indicate that the specified component / analyte did not react measurably with the reagent. \r\n\n |
| 2 | RR | Reactive | \n A presence finding used to indicate that the specified component / analyte reacted with the reagent above the reliably measurable limit of the performed test. \r\n\n |
| 3 | WR | Weakly reactive | \n A weighted presence finding used to indicate that the specified component / analyte reacted with the reagent, but below the reliably measurable limit of the performed test. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_MaterialEntityClassType) Abstract | \n Types of Material for EntityClass "MAT" \r\n\n | |
| 2 | (_ContainerEntityType) Abstract | \n Material intended to hold another material for purpose of storage or transport. \r\n\n | |
| 3 | PKG | Package | \n A material intended to hold other materials for purposes of storage or transportation \r\n\n |
| 4 | (_NonRigidContainerEntityType) Abstract | \n A container having dimensions that adjust somewhat based on the amount and shape of the material placed within it. \r\n\n | |
| 5 | BAG | Bag | \n A pouched or pendulous container. \r\n\n |
| 5 | PACKT | Packet | \n A paper \r\n\n |
| 5 | PCH | Pouch | \n A small bag or container made of a soft material. \r\n\n |
| 5 | SACH | Sachet | \n A small bag or packet containing a small portion of a substance. \r\n\n |
| 4 | (_RigidContainerEntityType) Abstract | \n A container having a fixed and inflexible dimensions and volume \r\n\n | |
| 5 | (_IndividualPackageEntityType) Abstract | \n Container intended to contain sufficient material for only one use. \r\n\n | |
| 6 | AMP | Ampule | \n A small sealed glass container that holds a measured amount of a medicinal substance. \r\n\n |
| 6 | MINIM | Minim | \n Individually dosed ophthalmic solution. One time eye dropper dispenser. \r\n\n |
| 6 | NEBAMP | Nebuamp | \n Individually dosed inhalation solution. \r\n\n |
| 6 | OVUL | Ovule | \n A container either glass or plastic and a narrow neck, for storing liquid. \r\n\n |
| 5 | (_MultiUseContainerEntityType) Abstract | \n A container intended to contain sufficient material for more than one use. (I.e. Material is intended to be removed from the container at more than one discrete time period.) \r\n\n | |
| 6 | BOT | Bottle | \n A container, typically rounded, either glass or plastic with a narrow neck and capable of storing liquid. \r\n\n |
| 7 | BOTA | Amber Bottle | \n A bottle of yellow to brown color. Used to store light-sensitive materials \r\n\n |
| 7 | BOTD | Dropper Bottle | \n A bottle with a cap designed to release the contained liquid in droplets of a specific size. \r\n\n |
| 7 | BOTG | Glass Bottle | \n A bottle made of glass \r\n\n |
| 7 | BOTP | Plastic Bottle | \n A bottle made of plastic \r\n\n |
| 8 | BOTPLY | Polyethylene Bottle | \n A bottle made of polyethylene \r\n\n |
| 6 | BOX | Box | \n A 6-sided container commonly made from paper or cardboard used for solid forms. \r\n\n |
| 6 | CAN | Can | \n A metal container in which a material is hermetically sealed to enable storage over long periods. \r\n\n |
| 6 | CART | Cartridge | \n A sealed container of liquid or powder intended to be loaded into a device. \r\n\n |
| 6 | CNSTR | Canister | \n A pressurized metal container holding a substance released as a spray or aerosol. \r\n\n |
| 6 | JAR | Jar | \n A container of glass, earthenware, plastic, etc. Top of the container has a diameter of similar size to the diameter of the container as a whole \r\n\n |
| 6 | JUG | Jug | \n A deep vessel for holding liquids, with a handle and often with a spout or lip shape for pouring. \r\n\n |
| 6 | TIN | Tin | \n A lidded container made of thin sheet metal. \r\n\n |
| 6 | TUB | Tub | \n An open flat bottomed round container. \r\n\n |
| 6 | TUBE | Tube | \n A long hollow rigid or flexible cylinder. Material is extruded by squeezing the container. \r\n\n |
| 6 | VIAL | Vial | \n A small cylindrical glass for holding liquid medicines. \r\n\n |
| 5 | BLSTRPK | Blister Pack | \n A bubblepack. Medications sealed individually, separated into doses. \r\n\n |
| 6 | CARD | Card | \n A bubble pack card. Multiple individual/separated doses. \r\n\n |
| 4 | COMPPKG | Compliance Package | \n A container intended to contain sufficient material for more than one use, but grouped or organized to provide individual access to sufficient material for a single use. Often used to ensure that the proper type and amount of material is consumed/expended for each use. \r\n\n |
| 5 | BLSTRPK | ||
| 5 | DIALPK | Dial Pack | \n Rotatable dispenser. Eg. Birth control package. \r\n\n |
| 5 | DISK | Disk | \n Object that is thin, flat, and circular. Doses of medication often contained in bubbles on the disk. \r\n\n |
| 5 | DOSET | Dosette | \n Special packaging that will help patients take their medications on a regular basis. \r\n\n |
| 5 | STRIP | Strip | \n A continuous strip of plastic sectioned into individual pouches, each one containing the quantity of 1 or more medications intended to be administered at a specific time \r\n\n |
| 4 | KIT | Kit | \n A container for a diverse collection of products intended to be used together for some purpose (e.g. Medicinal kits often contain a syringe, a needle and the injectable medication). \r\n\n |
| 5 | SYSTM | System | \n A kit in which the components are interconnected. \r\n\n |
| 2 | (_MedicalDevice) Abstract | \n A device with direct or indirect therapeutic purpose. Values for EntityCode when EntityClass = "DEV" \r\n\n | |
| 3 | (_AccessMedicalDevice) Abstract | \n A device used to allow access to a part of a body \r\n\n | |
| 4 | LINE | Line | \n A hollow tube used to administer a substance into a vein, artery or body cavity \r\n\n |
| 5 | IALINE | Intra-arterial Line | \n A line used to administer a substance into an artery \r\n\n |
| 5 | IVLINE | Intraveneous Line | \n A line used to administer a substance into a vein \r\n\n |
| 3 | (_AdministrationMedicalDevice) Abstract | \n A device intended to administer a substance to a subject \r\n\n | |
| 4 | (_InjectionMedicalDevice) Abstract | \n A device intended to administer liquid into a subject via a \r\n\n | |
| 5 | AINJ | AutoInjector | \n Automatically injects medication. \r\n\n |
| 5 | PEN | Pen | \n A device which can contain a cartridge for injection purposes. Eg. Insulin pen. \r\n\n |
| 5 | SYR | Syringe | \n A barrel with a plunger. \r\n\n |
| 4 | APLCTR | Applicator | \n A device used to apply a liquid or powder to a surface. \r\n\n |
| 4 | INH | Inhaler | \n A small device used for inhaling medicine in the form of a vapour or gas in order to ease a respiratory condition such as asthma or to relieve nasal congestion. \r\n\n |
| 5 | DSKS | Diskus | \n The device used to inhale the doses of medication contained in the disk form. \r\n\n |
| 5 | DSKUNH | Diskhaler | \n The device used to inhale the doses of medication contained in the disk form. \r\n\n |
| 5 | TRBINH | Turbuhaler | \n Asthma medication delivery device. \r\n\n |
| 4 | PMP | Pump | \n A device that is used to raise, compress, or transfer liquids or gases and is operated by a piston or similar mechanism. \r\n\n |
| 2 | (_SpecimenAdditiveEntity) Abstract | \n Set of codes related to specimen additives \r\n\n | |
| 3 | ACDA | ACD Solution A | \n ACD Solution A of trisodium citrate, 22.0g/L; citric acid, 8.0 g/L; and dextrose 24.5 g/L. Used in Blood banking and histocompatibilty testing \r\n\n |
| 3 | ACDB | ACD Solution B | \n ACD Solution B of trisodium citrate, 13.2g/L; citric acid, 4.8 g/L; and dextrose 14.7 g/L. Used in Blood banking and histocompatibilty testing. \r\n\n |
| 3 | ACET | Acetic Acid | \n 50% V/V acetic acid in water. Used as a urine preservative \r\n\n |
| 3 | AMIES | Amies transport medium | \n Sodium Chloride 3.0g, Potassium Chloride 0.2g, Calcium Chloride 0.1g, Magnesium Chloride 0.1g, Monopotassium Phosphate 0.2g, Disodium Phosphate 1.15g, Sodium Thiogly collate 1.0g, Distilled Water 1 liter \r\n\n |
| 3 | BACTM | Bacterial Transport medium | \n Any medium used to maintain bacterial viability (e.g. Stuart's, Cary-Blair, Amies) \r\n\n |
| 3 | BF10 | Buffered 10% formalin | \n Formaldehyde 4% w/v; methyl alcohol 1% w/v; phosphate buffering salts. Tissue preservative \r\n\n |
| 3 | BOR | Boric Acid | \n Powdered boric acid (usually 10 g) added to 24-hour urine collections as a preservative. \r\n\n |
| 3 | BOUIN | Bouin's solution | \n Picric acid, saturated aqueous solution (750.0 ml), 37-40% formalin (250.0 ml), glacial acetic acid (50.0 ml). Tissue preservative. \r\n\n |
| 3 | BSKM | Buffered skim milk | \n 50% skim milk in 0.01 M phosphate-buffered saline. Maintain virus viability \r\n\n |
| 3 | C32 | 3.2% Citrate | \n A 3.2% solution of Sodium Citrate in water. Used as a blood preservative \r\n\n |
| 3 | C38 | 3.8% Citrate | \n A 3.8% solution of Sodium Citrate in water. Used as a blood preservative \r\n\n |
| 3 | CARS | Carson's Modified 10% formalin | \n A modification of buffered 10% formalin used as a general tissue preservative. \r\n\n |
| 3 | CARY | Cary Blair Medium | \n Sodium Thioglycollate 1.5 g, Disodium Hydrogen Phosphate 1.1 g, Sodium Chloride 5.0 g, Calcium Chloride 0.09 g, Agar 5.0 g, per Liter of Water \r\n\n |
| 3 | CHLTM | Chlamydia transport medium | \n Any of a number of non-nutritive buffered media used to maintain Chlamydia viability during transportation to the laboratory \r\n\n |
| 3 | CTAD | CTAD | \n Buffered tri-sodium citrate solution with theophylline, adenosine and dipyridamole \r\n\n |
| 3 | EDTK15 | Potassium/K EDTA 15% | \n Potassium EDTA 15% solution in water \r\n\n |
| 3 | EDTK75 | Potassium/K EDTA 7.5% | \n Potassium EDTA 7.5% solution in water \r\n\n |
| 3 | EDTN | Sodium/Na EDTA | \n Sodium fluoride and Disodium EDTA \r\n\n |
| 3 | ENT | Enteric bacteria transport medium | \n Any of a number of non-nutritive buffered media used to maintain enteric bacterial viability during transportation to the laboratory \r\n\n |
| 3 | F10 | 10% Formalin | \n A 10% v/v solution in water of formalin( a 37% solution of formaldehyde and water). Used for tissue preservation. \r\n\n |
| 3 | FDP | Thrombin NIH; soybean trypsin inhibitor | \n Thrombin plus soybean trypsin inhibitor. For use in identifying fibrn degredation products. \r\n\n |
| 3 | FL10 | Sodium Fluoride, 10mg | \n Sodium fluoride, 10mg added as a urine preservative. \r\n\n |
| 3 | FL100 | Sodium Fluoride, 100mg | \n Sodium fluoride, 100mg added as a urine preservative. \r\n\n |
| 3 | HCL6 | 6N HCL | \n A solution of HCl containing 6moles of hydrogen ion/L. Used as a Urine Preservative. \r\n\n |
| 3 | HEPA | Ammonium heparin | \n Ammonium heparin \r\n\n |
| 3 | HEPL | Lithium/Li Heparin | \n Lithium heparin salt \r\n\n |
| 3 | HEPN | Sodium/Na Heparin | \n Sodium heparin salt \r\n\n |
| 3 | HNO3 | Nitric Acid | \n 6N Nitric acid used to preserve urine for heavy metal analysis. \r\n\n |
| 3 | JKM | Jones Kendrick Medium | \n A transport medium formulated to maintain Bordetella pertussis viability. \r\n\n |
| 3 | KARN | Karnovsky's fixative | \n 5% Glutaraldehyde, 4% Formaldehyde in 0.08M buffer. Tissue preservation \r\n\n |
| 3 | KOX | Potassium Oxalate | \n Potassium oxalate and sodium fluoride in a 1.25:1 ratio \r\n\n |
| 3 | LIA | Lithium iodoacetate | \n Iodoacetate lithium salt \r\n\n |
| 3 | M4 | M4 | \n Modified Hank's balanced salt solution supplemented with bovine serum albumin, gelatin, sucrose and glutamic acid. It is buffered to pH 7.3+ or - 0.2 with HEPES buffer. Phenol red is used to indicate pH. Vancomycin, Amphotericin B and Colistin are used to \r\n\n |
| 3 | M4RT | M4-RT | \n Modified Hank's balanced salt solution supplemented with bovine serum albumin, gelatin, sucrose and glutamic acid. It is buffered to pH 7.3+ or - 0.2 with Hepes buffer. Phenol red is used to indicate pH. Gentamicin and amphotericin B are used to inhibit c \r\n\n |
| 3 | M5 | M5 | \n Modified Hank's balanced salt solution supplemented with protein stabilizers, sucrose and glutamic acid. It is buffered to pH 7.3+ or - 0.2 with Hepes buffer. Phenol red is used to indicate pH. Vancomycin, Amphotericin B and Colistin are used to inhibit c \r\n\n |
| 3 | MICHTM | Michel's transport medium | \n 1M potassium citrate, pH 7.0 2.5 ml, 0.1M magnesium sulfate 5.0 ml, 0.1M N-ethyl malemide 5.0 ml, dH2O 87.5 ml, ammonium sulfate 55gm. Preserve antigens for Immunofluorescence procedures \r\n\n |
| 3 | MMDTM | MMD transport medium | \n A buffered medium with ammonium sulfate added to preserve antigens for Immunofluorescence procedures \r\n\n |
| 3 | NAF | Sodium Fluoride | \n Sodium fluoride \r\n\n |
| 3 | NONE | None | \n No additive. Specifically identifes the specimen as having no additives. \r\n\n |
| 3 | PAGE | Page's Saline | \n 0.12 g NaCl, 0.004 g MgSO, 0.004 g, CaCl, 0.142 g Na2HPO4 and 0.136 g KH2PO4 per liter of distilled water. Maintain Acanthaoemba viability. \r\n\n |
| 3 | PHENOL | Phenol | \n Phenol. Urine preservative \r\n\n |
| 3 | PVA | Polyvinylalcohol | \n Polyvinyl alcohol \r\n\n |
| 3 | RLM | Reagan Lowe Medium | \n A transport medium formulated to maintain Bordetella pertussis viability. \r\n\n |
| 3 | SILICA | Siliceous earth | \n Diatomaceous earth. For glucose determination blood samples \r\n\n |
| 3 | SPS | Sodium polyanethol sulfonate 0.35% in 0.85% sodium chloride | \n Sodium polyanethol sulfonate in saline. Anticomplementary and antiphagocytic properties. Used in blood culture collection. \r\n\n |
| 3 | SST | Serum Separator Tube | \n Polymer separator gel with clot activator \r\n\n |
| 3 | STUTM | Stuart transport medium | \n Sodium Glycerophosphate 10.0g, Calcium Chloride 0.1g, Mercaptoacetic Acid 1.0ml, Distilled Water 1 liter \r\n\n |
| 3 | THROM | Thrombin | \n Thrombin. Accelerates clotting. \r\n\n |
| 3 | THYMOL | Thymol | \n 2-Isopropyl-5-methyl phenol. A preservative for 24 Hr Urine samples \r\n\n |
| 3 | THYO | Thyoglycolate broth | \n A nutritive medium with a reducing agent (sodium thioglycolate) which, due to a chemical reaction, removes oxygen from the broth. \r\n\n |
| 3 | TOLU | Toluene | \n Also known as Methylbenzene; Toluol; Phenylmethane. A preservative for 24 Hr Urine samples \r\n\n |
| 3 | URETM | Ureaplasma transport medium | \n A buffered salt solution with antifungal agents added for the collection and transport of Ureaplasma specimens. \r\n\n |
| 3 | VIRTM | Viral Transport medium | \n Sucrose 74.6g, Potassium hydrogenphosphate 0.52g, L-glutamic acid 0.72g, Bovine serum albumin 5.0g, Gentamicin 50mg, Potassium dihydrogenphosphate 1.25g, L-15 medium 9.9L, Water to 10L. Maintain Virus viability. \r\n\n |
| 3 | WEST | Buffered Citrate | \n 3.8% Citrate buffered to a pH of 5.5 for Westergren Sedimentation Rate \r\n\n |
| 2 | BLDPRD | Blood Product | \n A manufactured product that is produced from the raw blood oi a donor with the intention of using it in a recipient transfusion. \r\n\n |
| 2 | VCCNE | Vaccine | \n A Type of medicine that creates an immune protection without the recipient experiencing the disease. \r\n\n |
| 2 | (_DrugEntity) Abstract | \n A substance whose therapeutic effect is produced by chemical action within the body. \r\n\n | |
| 3 | (_ClinicalDrug) Abstract | \n Any substance or mixture of substances manufactured, sold or represented for use in: (a) the diagnosis, treatment, mitigation or prevention of a disease, disorder, abnormal physical state, or its symptoms, in human beings or animals; (b) restoring, correcting or modifying organic functions in human beings or animals. \r\n\n | |
| 1 | (_NonDrugAgentEntity) Abstract | \n Indicates types of allergy and intolerance agents which are non-drugs. (E.g. foods, latex, etc.) \r\n\n | |
| 2 | NDA01 | egg | |
| 2 | NDA02 | fish | |
| 2 | NDA03 | lactose | |
| 2 | NDA04 | peanut | |
| 2 | NDA05 | soy | |
| 2 | NDA06 | sulfites | |
| 2 | NDA07 | wheat or gluten | |
| 2 | NDA08 | isocyanates | |
| 2 | NDA09 | solvents | |
| 2 | NDA10 | oils | |
| 2 | NDA11 | venoms | |
| 2 | NDA12 | latex | |
| 2 | NDA13 | shellfish | |
| 2 | NDA14 | strawberries | |
| 2 | NDA15 | tomatoes | |
| 2 | NDA16 | dust | |
| 2 | NDA17 | dust mites | |
| 1 | (_OrganizationEntityType) Abstract | \n Further classifies entities of classCode ORG. \r\n\n | |
| 2 | HHOLD | household | \n The group of persons who occupy a single housing unit. \r\n\n |
| 2 | NAT | NationEntityType | \n Codes identifying nation states. Allows for finer grained specification of Entity with classcode <= NAT \r\n\n \n Example:ISO3166 country codes. \r\n\n |
| 2 | RELIG | religious institution | \n An organization that provides religious rites of worship. \r\n\n |
| 1 | (_PlaceEntityType) Abstract | \n Types of places for EntityClass "PLC" \r\n\n | |
| 2 | BED | Bed Location | \n The location of a bed \r\n\n |
| 2 | BLDG | Building Location | \n The location of a building \r\n\n |
| 2 | FLOOR | Floor Location | \n The location of a floor of a building \r\n\n |
| 2 | ROOM | Room Location | \n The location of a room \r\n\n |
| 2 | WING | Wing Location | \n The location of a wing of a building (e.g. East Wing). The same room number for the same floor number can be distinguished by wing number in some situations \r\n\n |
| 1 | (_ResourceGroupEntityType) Abstract | \n Codes to characterize a Resource Group using categories that typify its membership and/or function \r\n\n . \r\n\n \n Example: PractitionerGroup \r\n\n | |
| 2 | PRAC | PractitionerGroup |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | GEL | Gel | \n A gelatinous type of separator material. \r\n\n |
| 1 | NONE | None | \n No separator material is present in the container. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | center | center | |
| 1 | char | char | |
| 1 | justify | justify | |
| 1 | left | left | |
| 1 | right | right |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | above | above | |
| 1 | below | below | |
| 1 | border | border | |
| 1 | box | box | |
| 1 | hsides | hsides | |
| 1 | lhs | lhs | |
| 1 | rhs | rhs | |
| 1 | void | void | |
| 1 | vsides | vsides |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | all | all | |
| 1 | cols | cols | |
| 1 | groups | groups | |
| 1 | none | none | |
| 1 | rows | rows |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | E | emergency | |
| 1 | LD | labor and delivery | |
| 1 | NB | newborn |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_ActAccountCode) Abstract | \n An account represents a grouping of financial transactions that are tracked and reported together with a single balance. \t \tExamples of account codes (types) are Patient billing accounts (collection of charges), Cost centers; Cash. \r\n\n | |
| 2 | ACCTRECEIVABLE | account receivable | \n An account for collecting charges, reversals, adjustments and payments, including deductibles, copayments, coinsurance (financial transactions) credited or debited to the account receivable account for a patient's encounter. \r\n\n |
| 2 | CASH | Cash | |
| 2 | CC | credit card | \n \n Description: Types of advance payment to be made on a plastic card usually issued by a financial institution used of purchasing services and/or products. \r\n\n |
| 3 | AE | American Express | |
| 3 | DN | Diner's Club | |
| 3 | DV | Discover Card | |
| 3 | MC | Master Card | |
| 3 | V | Visa | |
| 2 | PBILLACCT | patient billing account | \n An account representing charges and credits (financial transactions) for a patient's encounter. \r\n\n |
| 1 | (_ActAdjudicationCode) Abstract | \n Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results. \r\n\n | |
| 2 | (_ActAdjudicationGroupCode) Abstract | \n Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals). \r\n\n | |
| 3 | CONT | contract | \n Transaction counts and value totals by Contract Identifier. \r\n\n |
| 3 | DAY | day | \n Transaction counts and value totals for each calendar day within the date range specified. \r\n\n |
| 3 | LOC | location | \n Transaction counts and value totals by service location (e.g clinic). \r\n\n |
| 3 | MONTH | month | \n Transaction counts and value totals for each calendar month within the date range specified. \r\n\n |
| 3 | PERIOD | period | \n Transaction counts and value totals for the date range specified. \r\n\n |
| 3 | PROV | provider | \n Transaction counts and value totals by Provider Identifier. \r\n\n |
| 3 | WEEK | week | \n Transaction counts and value totals for each calendar week within the date range specified. \r\n\n |
| 3 | YEAR | year | \n Transaction counts and value totals for each calendar year within the date range specified. \r\n\n |
| 2 | AA | adjudicated with adjustments | \n The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges). \r\n\n Also includes the concept 'Adjudicate as zero' and items not covered under a particular Policy. \r\n\n Invoice element can be reversed (nullified). \r\n\n Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). \r\n\n |
| 3 | ANF | adjudicated with adjustments and no financial impact | \n The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges) without changing the amount. \r\n\n Invoice element can be reversed (nullified). \r\n\n Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). \r\n\n |
| 2 | AR | adjudicated as refused | \n The invoice element has passed through the adjudication process but payment is refused due to one or more reasons. \r\n\n Includes items such as patient not covered, or invoice element is not constructed according to payer rules (e.g. 'invoice submitted too late'). \r\n\n If one invoice element line item in the invoice element structure is rejected, the remaining line items may not be adjudicated and the complete group is treated as rejected. \r\n\n A refused invoice element can be forwarded to the next payer (for Coordination of Benefits) or modified and resubmitted to refusing payer. \r\n\n Invoice element cannot be reversed (nullified) as there is nothing to reverse. \r\n\n Recommend that the invoice element is not saved for DUR (Drug Utilization Reporting). \r\n\n |
| 2 | AS | adjudicated as submitted | \n The invoice element was/will be paid exactly as submitted, without financial adjustment(s). \r\n\n If the dollar amount stays the same, but the billing codes have been amended or financial adjustments have been applied through the adjudication process, the invoice element is treated as "Adjudicated with Adjustment". \r\n\n If information items are included in the adjudication results that do not affect the monetary amounts paid, then this is still Adjudicated as Submitted (e.g. 'reached Plan Maximum on this Claim'). \r\n\n Invoice element can be reversed (nullified). \r\n\n Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). \r\n\n |
| 1 | (_ActAdjudicationResultActionCode) Abstract | \n Actions to be carried out by the recipient of the Adjudication Result information. \r\n\n | |
| 2 | DISPLAY | Display | \n The adjudication result associated is to be displayed to the receiver of the adjudication result. \r\n\n |
| 2 | FORM | Print on Form | \n The adjudication result associated is to be printed on the specified form, which is then provided to the covered party. \r\n\n |
| 1 | (_ActBillableModifierCode) Abstract | \n \n Definition:An identifying modifier code for healthcare interventions or procedures. \r\n\n | |
| 2 | CPTM | CPT modifier codes | \n \n Description:CPT modifier codes are found in Appendix A of CPT 2000 Standard Edition. \r\n\n |
| 2 | HCPCSA | HCPCS Level II and Carrier-assigned | \n \n Description:HCPCS Level II (HCFA-assigned) and Carrier-assigned (Level III) modifiers are reported in Appendix A of CPT 2000 Standard Edition and in the Medicare Bulletin. \r\n\n |
| 1 | (_ActBillingArrangementCode) Abstract | \n The type of provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider, over a specified period. \r\n\n | |
| 2 | BLK | block funding | \n A billing arrangement where a Provider charges a lump sum to provide a prescribed group (volume) of services to a single patient which occur over a period of time. Services included in the block may vary. \r\n\n This billing arrangement is also known as Program of Care for some specific Payors and Program Fees for other Payors. \r\n\n |
| 2 | CAP | capitation funding | \n A billing arrangement where the payment made to a Provider is determined by analyzing one or more demographic attributes about the persons/patients who are enrolled with the Provider (in their practice). \r\n\n |
| 2 | CONTF | contract funding | \n A billing arrangement where a Provider charges a lump sum to provide a particular volume of one or more interventions/procedures or groups of interventions/procedures. \r\n\n |
| 2 | FINBILL | financial | \n A billing arrangement where a Provider charges for non-clinical items. This includes interest in arrears, mileage, etc. Clinical content is not \tincluded in Invoices submitted with this type of billing arrangement. \r\n\n |
| 2 | ROST | roster funding | \n A billing arrangement where funding is based on a list of individuals registered as patients of the Provider. \r\n\n |
| 2 | SESS | sessional funding | \n A billing arrangement where a Provider charges a sum to provide a group (volume) of interventions/procedures to one or more patients within a defined period of time, typically on the same date. Interventions/procedures included in the session may vary. \r\n\n |
| 2 | FFS | fee for service | \n A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product. \r\n\n Fee for Service is used when an individual intervention/procedure/event is used for billing purposes. In other words, fees are associated with the intervention/procedure/event. For example, a specific CCI (Canadian Classification of Interventions) code has an associated fee and is used for billing purposes. \r\n\n |
| 3 | FFPS | first fill, part fill, partial strength | \n A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets) \r\n\n |
| 3 | FFCS | first fill complete, partial strength | \n A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | TFS | trial fill partial strength | \n A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 1 | (_ActBoundedROICode) Abstract | \n Type of bounded ROI. \r\n\n | |
| 2 | ROIFS | fully specified ROI | \n A fully specified bounded Region of Interest (ROI) delineates a ROI in which only those dimensions participate that are specified by boundary criteria, whereas all other dimensions are excluded. For example a ROI to mark an episode of "ST elevation" in a subset of the EKG leads V2, V3, and V4 would include 4 boundaries, one each for time, V2, V3, and V4. \r\n\n |
| 2 | ROIPS | partially specified ROI | \n A partially specified bounded Region of Interest (ROI) specifies a ROI in which at least all values in the dimensions specified by the boundary criteria participate. For example, if an episode of ventricular fibrillations (VFib) is observed, it usually doesn't make sense to exclude any EKG leads from the observation and the partially specified ROI would contain only one boundary for time indicating the time interval where VFib was observed. \r\n\n |
| 1 | (_ActCareProvisionCode) Abstract | \n \n Description:The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care. \r\n\n | |
| 2 | (_ActCredentialedCareCode) Abstract | \n \n Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements. \r\n\n \n Example:Hospital license; physician license; clinic accreditation. \r\n\n | |
| 3 | (_ActCredentialedCareProvisionPersonCode) Abstract | \n \n Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing individuals. \r\n\n | |
| 4 | CACC | certified anatomic pathology and clinical pathology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CAIC | certified allergy and immunology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CAMC | certified aerospace medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CANC | certified anesthesiology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CAPC | certified anatomic pathology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CBGC | certified clinical biochemical genetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCCC | certified clinical cytogenetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCGC | certified clinical genetics (M.D.) care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCPC | certified clinical pathology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CCSC | certified colon and rectal surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CDEC | certified dermatology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CDRC | certified diagnostic radiology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CEMC | certified emergency medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CFPC | certified family practice care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CIMC | certified internal medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CMGC | certified clinical molecular genetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CNEC | certified neurology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board \r\n\n |
| 4 | CNMC | certified nuclear medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CNQC | certified neurology with special qualifications in child neurology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CNSC | certified neurological surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COGC | certified obstetrics and gynecology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COMC | certified occupational medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COPC | certified ophthalmology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COSC | certified orthopaedic surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | COTC | certified otolaryngology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPEC | certified pediatrics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPGC | certified Ph.D. medical genetics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPHC | certified public health and general preventive medicine care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPRC | certified physical medicine and rehabilitation care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPSC | certified plastic surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CPYC | certified psychiatry care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CROC | certified radiation oncology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CRPC | certified radiological physics care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CSUC | certified surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CTSC | certified thoracic surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CURC | certified urology care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | CVSC | certified vascular surgery care | \n \n Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. \r\n\n |
| 4 | LGPC | licensed general physician care | \n \n Description:Scope of responsibility taken-on for physician care of a patient as defined by a governmental licensing agency. \r\n\n |
| 3 | (_ActCredentialedCareProvisionProgramCode) Abstract | \n \n Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing programs within organizations. \r\n\n | |
| 4 | AALC | accredited assisted living care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | AAMC | accredited ambulatory care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ABHC | accredited behavioral health care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ACAC | accredited critical access hospital care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ACHC | accredited hospital care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | AHOC | accredited home care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | ALTC | accredited long term care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | AOSC | accredited office-based surgery care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. \r\n\n |
| 4 | CACS | certified acute coronary syndrome care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CAMI | certified acute myocardial infarction care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CAST | certified asthma care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CBAR | certified bariatric surgery care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CCAD | certified coronary artery disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CCAR | certified cardiac care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CDEP | certified depression care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CDGD | certified digestive/gastrointestinal disorders care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CDIA | certified diabetes care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CEPI | certified epilepsy care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CFEL | certified frail elderly care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CHFC | certified heart failure care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CHRO | certified high risk obstetrics care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CHYP | certified hyperlipidemia care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CMIH | certified migraine headache care | \n \n Description:. \r\n\n |
| 4 | CMSC | certified multiple sclerosis care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | COJR | certified orthopedic joint replacement care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CONC | certified oncology care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | COPD | certified chronic obstructive pulmonary disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CORT | certified organ transplant care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CPAD | certified parkinsons disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CPND | certified pneumonia disease care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CPST | certified primary stroke center care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSDM | certified stroke disease management care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSIC | certified sickle cell care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSLD | certified sleep disorders care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CSPT | certified spine treatment care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CTBU | certified trauma/burn center care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CVDC | certified vascular diseases care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CWMA | certified wound management care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 4 | CWOH | certified women's health care | \n \n Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. \r\n\n |
| 2 | (_ActEncounterCode) Abstract | \n Domain provides codes that qualify the ActEncounterClass (ENC) \r\n\n | |
| 3 | AMB | ambulatory | \n A comprehensive term for health care provided in a healthcare facility (e.g. a practitioneraTMs office, clinic setting, or hospital) on a nonresident basis. The term ambulatory usually implies that the patient has come to the location and is not assigned to a bed. Sometimes referred to as an outpatient encounter. \r\n\n |
| 3 | EMER | emergency | \n A patient encounter that takes place at a dedicated healthcare service delivery location where the patient receives immediate evaluation and treatment, provided until the patient can be discharged or responsibility for the patient's care is transferred elsewhere (for example, the patient could be admitted as an inpatient or transferred to another facility.) \r\n\n |
| 3 | FLD | field | \n A patient encounter that takes place both outside a dedicated service delivery location and outside a patient's residence. Example locations might include an accident site and at a supermarket. \r\n\n |
| 3 | HH | home health | \n Healthcare encounter that takes place in the residence of the patient or a designee \r\n\n |
| 3 | IMP | inpatient encounter | \n A patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients generally stay at least overnight and provided with room, board, and continuous nursing service. \r\n\n |
| 4 | ACUTE | inpatient acute | \n An acute inpatient encounter. \r\n\n |
| 4 | NONAC | inpatient non-acute | \n Any category of inpatient encounter except 'acute' \r\n\n |
| 3 | OBSENC | observation encounter | \n An encounter where the patient usually will start in different encounter, such as one in the emergency department (EMER) but then transition to this type of encounter because they require a significant period of treatment and monitoring to determine whether or not their condition warrants an inpatient admission or discharge. In the majority of cases the decision about admission or discharge will occur within a time period determined by local, regional or national regulation, often between 24 and 48 hours. \r\n\n |
| 3 | PRENC | pre-admission | \n A patient encounter where patient is scheduled or planned to receive service delivery in the future, and the patient is given a pre-admission account number. When the patient comes back for subsequent service, the pre-admission encounter is selected and is encapsulated into the service registration, and a new account number is generated. \r\n\n \n Usage Note: This is intended to be used in advance of encounter types such as ambulatory, inpatient encounter, virtual, etc. \r\n\n |
| 3 | SS | short stay | \n An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours. \r\n\n |
| 3 | VR | virtual | \n A patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone conference, email exchange, robotic surgery, and televideo conference. \r\n\n |
| 2 | (_ActMedicalServiceCode) Abstract | \n General category of medical service provided to the patient during their encounter. \r\n\n | |
| 3 | ALC | Alternative Level of Care | \n Provision of Alternate Level of Care to a patient in an acute bed. Patient is waiting for placement in a long-term care facility and is unable to return home. \r\n\n |
| 3 | CARD | Cardiology | \n Provision of diagnosis and treatment of diseases and disorders affecting the heart \r\n\n |
| 3 | CHR | Chronic | \n Provision of recurring care for chronic illness. \r\n\n |
| 3 | DNTL | Dental | \n Provision of treatment for oral health and/or dental surgery. \r\n\n |
| 3 | DRGRHB | Drug Rehab | \n Provision of treatment for drug abuse. \r\n\n |
| 3 | GENRL | General | \n General care performed by a general practitioner or family doctor as a responsible provider for a patient. \r\n\n |
| 3 | MED | Medical | \n Provision of diagnostic and/or therapeutic treatment. \r\n\n |
| 3 | OBS | Obstetrics | \n Provision of care of women during pregnancy, childbirth and immediate postpartum period. Also known as Maternity. \r\n\n |
| 3 | ONC | Oncology | \n Provision of treatment and/or diagnosis related to tumors and/or cancer. \r\n\n |
| 3 | PALL | Palliative | \n Provision of care for patients who are living or dying from an advanced illness. \r\n\n |
| 3 | PED | Pediatrics | \n Provision of diagnosis and treatment of diseases and disorders affecting children. \r\n\n |
| 3 | PHAR | Pharmaceutical | \n Pharmaceutical care performed by a pharmacist. \r\n\n |
| 3 | PHYRHB | Physical Rehab | \n Provision of treatment for physical injury. \r\n\n |
| 3 | PSYCH | Psychiatric | \n Provision of treatment of psychiatric disorder relating to mental illness. \r\n\n |
| 3 | SURG | Surgical | \n Provision of surgical treatment. \r\n\n |
| 1 | (_ActClaimAttachmentCategoryCode) Abstract | \n \n Description: Coded types of attachments included to support a healthcare claim. \r\n\n | |
| 2 | AUTOATTCH | auto attachment | \n \n Description: Automobile Information Attachment \r\n\n |
| 2 | DOCUMENT | document | \n \n Description: Document Attachment \r\n\n |
| 2 | HEALTHREC | health record | \n \n Description: Health Record Attachment \r\n\n |
| 2 | IMG | image attachment | \n \n Description: Image Attachment \r\n\n |
| 2 | LABRESULTS | lab results | \n \n Description: Lab Results Attachment \r\n\n |
| 2 | MODEL | model | \n \n Description: Digital Model Attachment \r\n\n |
| 2 | WIATTCH | work injury report attachment | \n \n Description: Work Injury related additional Information Attachment \r\n\n |
| 2 | XRAY | x-ray | \n \n Description: Digital X-Ray Attachment \r\n\n |
| 1 | (_ActConsentType) Abstract | \n \n Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research. \r\n\n | |
| 2 | ICOL | information collection | \n \n Definition: Consent to have healthcare information collected in an electronic health record. This entails that the information may be used in analysis, modified, updated. \r\n\n |
| 2 | IDSCL | information disclosure | \n \n Definition: Consent to have collected healthcare information disclosed. \r\n\n |
| 2 | INFA | information access | \n \n Definition: Consent to access healthcare information. \r\n\n |
| 3 | INFAO | access only | \n \n Definition: Consent to access or "read" only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way. This level ensures that data which is masked or to which access is restricted will not be. \r\n\n \n Example: Opened and then emailed or screen printed for use outside of the consent directive purpose. \r\n\n |
| 3 | INFASO | access and save only | \n \n Definition: Consent to access and save only, which entails that access to the saved copy will remain locked. \r\n\n |
| 2 | IRDSCL | information redisclosure | \n \n Definition: Information re-disclosed without the patient's consent. \r\n\n |
| 2 | RESEARCH | research information access | \n \n Definition: Consent to have healthcare information in an electronic health record accessed for research purposes. \r\n\n |
| 3 | RSDID | de-identified information access | \n \n Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes, but without consent to re-identify the information under any circumstance. \r\n\n |
| 3 | RSREID | re-identifiable information access | \n \n Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent. \r\n\n \n Example:: Where there is a need to inform the subject of potential health issues. \r\n\n |
| 1 | (_ActContainerRegistrationCode) Abstract | \n Constrains the ActCode to the domain of Container Registration \r\n\n | |
| 2 | ID | Identified | \n Used by one system to inform another that it has received a container. \r\n\n |
| 2 | IP | In Position | \n Used by one system to inform another that the container is in position for specimen transfer (e.g., container removal from track, pipetting, etc.). \r\n\n |
| 2 | L | Left Equipment | \n Used by one system to inform another that the container has been released from that system. \r\n\n |
| 2 | M | Missing | \n Used by one system to inform another that the container did not arrive at its next expected location. \r\n\n |
| 2 | O | In Process | \n Used by one system to inform another that the specific container is being processed by the equipment. It is useful as a response to a query about Container Status, when the specific step of the process is not relevant. \r\n\n |
| 2 | R | Process Completed | \n Status is used by one system to inform another that the processing has been completed, but the container has not been released from that system. \r\n\n |
| 2 | X | Container Unavailable | \n Used by one system to inform another that the container is no longer available within the scope of the system (e.g., tube broken or discarded). \r\n\n |
| 1 | (_ActControlVariable) Abstract | \n An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure. \r\n\n Control variables are forms of observations because just as with clinical observations, the Observation.code determines the parameter and the Observation.value assigns the value. While control variables sometimes can be observed (by noting the control settings or an actually measured feedback loop) they are not primary observations, in the sense that a control variable without a primary act is of no use (e.g., it makes no sense to record a blood pressure position without recording a blood pressure, whereas it does make sense to record a systolic blood pressure without a diastolic blood pressure). \r\n\n | |
| 2 | AUTO | auto-repeat permission | \n Specifies whether or not automatic repeat testing is to be initiated on specimens. \r\n\n |
| 2 | ENDC | endogenous content | \n A baseline value for the measured test that is inherently contained in the diluent. In the calculation of the actual result for the measured test, this baseline value is normally considered. \r\n\n |
| 2 | REFLEX | reflex permission | \n Specifies whether or not further testing may be automatically or manually initiated on specimens. \r\n\n |
| 1 | (_ActCoverageConfirmationCode) Abstract | \n Response to an insurance coverage eligibility query or authorization request. \r\n\n | |
| 2 | (_ActCoverageAuthorizationConfirmationCode) Abstract | \n Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside. \r\n\n | |
| 3 | AUTH | Authorized | \n Authorization approved and funds have been set aside to pay for specified healthcare service(s) and/or product(s) within defined criteria for the authorization. \r\n\n |
| 3 | NAUTH | Not Authorized | \n Authorization for specified healthcare service(s) and/or product(s) denied. \r\n\n |
| 2 | (_ActCoverageEligibilityConfirmationCode) Abstract | \n Indication of eligibility coverage for healthcare service(s) and/or product(s). \r\n\n | |
| 3 | ELG | Eligible | \n Insurance coverage is in effect for healthcare service(s) and/or product(s). \r\n\n |
| 3 | NELG | Not Eligible | \n Insurance coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility. \r\n\n |
| 1 | (_ActCoverageLimitCode) Abstract | \n Criteria that are applicable to the authorized coverage. \r\n\n | |
| 2 | (_ActCoverageQuantityLimitCode) Abstract | \n Maximum amount paid or maximum number of services/products covered; or maximum amount or number covered during a specified time period under the policy or program. \r\n\n | |
| 3 | COVPRD | coverage period | \n Codes representing the time period during which coverage is available; or financial participation requirements are in effect. \r\n\n |
| 3 | LFEMX | life time maximum | \n \n Definition: Maximum amount paid by payer or covered party; or maximum number of services or products covered under the policy or program during a covered party's lifetime. \r\n\n |
| 3 | NETAMT | Net Amount | \n Maximum net amount that will be covered for the product or service specified. \r\n\n |
| 3 | PRDMX | period maximum | \n \n Definition: Maximum amount paid by payer or covered party; or maximum number of services/products covered under the policy or program by time period specified by the effective time on the act. \r\n\n |
| 3 | UNITPRICE | Unit Price | \n Maximum unit price that will be covered for the authorized product or service. \r\n\n |
| 3 | UNITQTY | Unit Quantity | \n Maximum number of items that will be covered of the product or service specified. \r\n\n |
| 2 | COVMX | coverage maximum | \n \n Definition: Codes representing the maximum coverate or financial participation requirements. \r\n\n |
| 3 | LFEMX | ||
| 3 | PRDMX | ||
| 2 | (_ActCoveredPartyLimitCode) Abstract | \n Codes representing the types of covered parties that may receive covered benefits under a policy or program. \r\n\n | |
| 1 | (_ActCoverageTypeCode) Abstract | \n \n Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties. \r\n\n | |
| 2 | (_ActInsurancePolicyCode) Abstract | \n Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs. \r\n\n | |
| 3 | EHCPOL | extended healthcare | \n Private insurance policy that provides coverage in addition to other policies (e.g. in addition to a Public Healthcare insurance policy). \r\n\n |
| 3 | HSAPOL | health spending account | \n Insurance policy that provides for an allotment of funds replenished on a periodic (e.g. annual) basis. The use of the funds under this policy is at the \tdiscretion of the covered party. \r\n\n |
| 3 | AUTOPOL | automobile | \n Insurance policy for injuries sustained in an automobile accident. Will also typically covered non-named parties to the policy, such as pedestrians \tand passengers. \r\n\n |
| 4 | COL | collision coverage policy | \n \n Definition: An automobile insurance policy under which the insurance company will cover the cost of damages to an automobile owned by the named insured that are caused by accident or intentionally by another party. \r\n\n |
| 4 | UNINSMOT | uninsured motorist policy | \n \n Definition: An automobile insurance policy under which the insurance company will indemnify a loss for which another motorist is liable if that motorist is unable to pay because he or she is uninsured. Coverage under the policy applies to bodily injury damages only. Injuries to the covered party caused by a hit-and-run driver are also covered. \r\n\n |
| 3 | PUBLICPOL | public healthcare | \n Insurance policy funded by a public health system such as a provincial or national health plan. Examples include BC MSP (British Columbia \tMedical Services Plan) OHIP (Ontario Health Insurance Plan), NHS (National Health Service). \r\n\n |
| 4 | DENTPRG | dental program | \n \n Definition: A public or government health program that administers and funds coverage for dental care to assist program eligible who meet financial and health status criteria. \r\n\n |
| 4 | DISEASEPRG | public health program | \n \n Definition: A public or government health program that administers and funds coverage for health and social services to assist program eligible who meet financial and health status criteria related to a particular disease. \r\n\n \n Example: Reproductive health, sexually transmitted disease, and end renal disease programs. \r\n\n |
| 5 | CANPRG | women's cancer detection program | \n \n Definition: A program that provides low-income, uninsured, and underserved women access to timely, high-quality screening and diagnostic services, to detect breast and cervical cancer at the earliest stages. \r\n\n \n Example: To improve women's access to screening for breast and cervical cancers, Congress passed the Breast and Cervical Cancer Mortality Prevention Act of 1990, which guided CDC in creating the National Breast and Cervical Cancer Early Detection Program (NBCCEDP), which provides access to critical breast and cervical cancer screening services for underserved women in the United States. An estimated 7 to 10% of U.S. women of screening age are eligible to receive NBCCEDP services. Federal guidelines establish an eligibility baseline to direct services to uninsured and underinsured women at or below 250% of federal poverty level; ages 18 to 64 for cervical screening; ages 40 to 64 for breast screening. \r\n\n |
| 5 | ENDRENAL | end renal program | \n \n Definition: A public or government program that administers publicly funded coverage of kidney dialysis and kidney transplant services. \r\n\n Example: In the U.S., the Medicare End-stage Renal Disease program (ESRD), the National Kidney Foundation (NKF) American Kidney Fund (AKF) The Organ Transplant Fund. \r\n\n |
| 5 | HIVAIDS | HIV-AIDS program | \n \n Definition: Government administered and funded HIV-AIDS program for beneficiaries meeting financial and health status criteria. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. \r\n\n \n Example: In the U.S., the Ryan White program, which is administered by the Health Resources and Services Administration. \r\n\n |
| 4 | MANDPOL | mandatory health program | |
| 4 | MENTPRG | mental health program | \n \n Definition: Government administered and funded mental health program for beneficiaries meeting financial and mental health status criteria. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. \r\n\n \n Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA). \r\n\n |
| 4 | SAFNET | safety net clinic program | \n \n Definition: Government administered and funded program to support provision of care to underserved populations through safety net clinics. \r\n\n \n Example: In the U.S., safety net providers such as federally qualified health centers (FQHC) receive funding under PHSA Section 330 grants administered by the Health Resources and Services Administration. \r\n\n |
| 4 | SUBPRG | substance use program | \n \n Definition: Government administered and funded substance use program for beneficiaries meeting financial, substance use behavior, and health status criteria. Beneficiaries may be required to enroll as a result of legal proceedings. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. \r\n\n \n Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA). \r\n\n |
| 4 | SUBSIDIZ | subsidized health program | \n \n Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n |
| 5 | SUBSIDMC | subsidized managed care program | \n \n Definition: A government health program that provides coverage through managed care contracts for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n \n Discussion: The structure and business processes for underwriting and administering a subsidized managed care program is further specified by the Underwriter and Payer Role.class and Role.code. \r\n\n |
| 5 | SUBSUPP | subsidized supplemental health program | \n \n Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria for a supplemental health policy or program such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n \n Example: Supplemental health coverage program may cover the cost of a health program or policy financial participations, such as the copays and the premiums, and may provide coverage for services in addition to those covered under the supplemented health program or policy. In the U.S., Medicaid programs may pay the premium for a covered party who is also covered under the Medicare program or a private health policy. \r\n\n \n Discussion: The structure and business processes for underwriting and administering a subsidized supplemental retiree health program is further specified by the Underwriter and Payer Role.class and Role.code. \r\n\n |
| 3 | WCBPOL | worker's compensation | \n Insurance policy for injuries sustained in the work place or in the course of employment. \r\n\n |
| 2 | (_ActInsuranceTypeCode) Abstract | \n \n Definition: Set of codes indicating the type of insurance policy. Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions. The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly. A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss. An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer. A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured. \r\n\n \n Discussion: In contrast to programs, an insurance policy has one or more policy holders, who own the policy. The policy holder may be the covered party, a relative of the covered party, a partnership, or a corporation, e.g., an employer. A subscriber of a self-insured health insurance policy is a policy holder. A subscriber of an employer sponsored health insurance policy is holds a certificate of coverage, but is not a policy holder; the policy holder is the employer. See CoveredRoleType. \r\n\n | |
| 3 | AUTOPOL | ||
| 3 | (_ActHealthInsuranceTypeCode) Abstract | \n \n Definition: Set of codes indicating the type of health insurance policy that covers health services provided to covered parties. A health insurance policy is a written contract for insurance between the insurance company and the policyholder, and contains pertinent facts about the policy owner (the policy holder), the health insurance coverage, the insured subscribers and dependents, and the insurer. Health insurance is typically administered in accordance with a plan, which specifies (1) the type of health services and health conditions that will be covered under what circumstances (e.g., exclusion of a pre-existing condition, service must be deemed medically necessary; service must not be experimental; service must provided in accordance with a protocol; drug must be on a formulary; service must be prior authorized; or be a referral from a primary care provider); (2) the type and affiliation of providers (e.g., only allopathic physicians, only in network, only providers employed by an HMO); (3) financial participations required of covered parties (e.g., co-pays, coinsurance, deductibles, out-of-pocket); and (4) the manner in which services will be paid (e.g., under indemnity or fee-for-service health plans, the covered party typically pays out-of-pocket and then file a claim for reimbursement, while health plans that have contractual relationships with providers, i.e., network providers, typically do not allow the providers to bill the covered party for the cost of the service until after filing a claim with the payer and receiving reimbursement). \r\n\n | |
| 4 | DENTAL | dental care policy | \n \n Definition: A health insurance policy that that covers benefits for dental services. \r\n\n |
| 4 | DISEASE | disease specific policy | \n \n Definition: A health insurance policy that covers benefits for healthcare services provided for named conditions under the policy, e.g., cancer, diabetes, or HIV-AIDS. \r\n\n |
| 4 | DRUGPOL | drug policy | \n \n Definition: A health insurance policy that covers benefits for prescription drugs, pharmaceuticals, and supplies. \r\n\n |
| 4 | EHCPOL | ||
| 4 | HIP | health insurance plan policy | \n \n Definition: A health insurance policy that covers healthcare benefits by protecting covered parties from medical expenses arising from health conditions, sickness, or accidental injury as well as preventive care. Health insurance policies explicitly exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy. \r\n\n \n Discussion: Health insurance policies are offered by health insurance plans that typically reimburse providers for covered services on a fee-for-service basis, that is, a fee that is the allowable amount that a provider may charge. This is in contrast to managed care plans, which typically prepay providers a per-member/per-month amount or capitation as reimbursement for all covered services rendered. Health insurance plans include indemnity and healthcare services plans. \r\n\n |
| 4 | HSAPOL | ||
| 4 | LTC | long term care policy | \n \n Definition: An insurance policy that covers benefits for long-term care services people need when they no longer can care for themselves. This may be due to an accident, disability, prolonged illness or the simple process of aging. Long-term care services assist with activities of daily living including: \r\n\n \n \n Help at home with day-to-day activities, such as cooking, cleaning, bathing and dressing \r\n\n \n \n Care in the community, such as in an adult day care facility \r\n\n \n \n Supervised care provided in an assisted living facility \r\n\n \n \n Skilled care provided in a nursing home \r\n\n \n \n |
| 4 | MCPOL | managed care policy | \n \n Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment. Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program. Employees may be required to pay premiums toward the cost of coverage as well. \r\n\n Managed care policies specifically exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy. \r\n\n \n Discussion: Managed care policies are offered by managed care plans that contract with selected providers or health care organizations to provide comprehensive health care at a discount to covered parties and coordinate the financing and delivery of health care. Managed care uses medical protocols and procedures agreed on by the medical profession to be cost effective, also known as medical practice guidelines. Providers are typically reimbursed for covered services by a capitated amount on a per member per month basis that may reflect difference in the health status and level of services anticipated to be needed by the member. \r\n\n |
| 5 | POS | point of service policy | \n \n Definition: A policy for a health plan that has features of both an HMO and a FFS plan. Like an HMO, a POS plan encourages the use its HMO network to maintain discounted fees with participating providers, but recognizes that sometimes covered parties want to choose their own provider. The POS plan allows a covered party to use providers who are not part of the HMO network (non-participating providers). However, there is a greater cost associated with choosing these non-network providers. A covered party will usually pay deductibles and coinsurances that are substantially higher than the payments when he or she uses a plan provider. Use of non-participating providers often requires the covered party to pay the provider directly and then to file a claim for reimbursement, like in an FFS plan. \r\n\n |
| 5 | HMO | health maintenance organization policy | \n \n Definition: A policy for a health plan that provides coverage for health care only through contracted or employed physicians and hospitals located in particular geographic or service areas. HMOs emphasize prevention and early detection of illness. Eligibility to enroll in an HMO is determined by where a covered party lives or works. \r\n\n |
| 5 | PPO | preferred provider organization policy | \n \n Definition: A network-based, managed care plan that allows a covered party to choose any health care provider. However, if care is received from a "preferred" (participating in-network) provider, there are generally higher benefit coverage and lower deductibles. \r\n\n |
| 4 | MENTPOL | mental health policy | \n \n Definition: A health insurance policy that covers benefits for mental health services and prescriptions. \r\n\n |
| 4 | POS | ||
| 4 | SUBPOL | substance use policy | \n \n Definition: A health insurance policy that covers benefits for substance use services. \r\n\n |
| 4 | VISPOL | vision care policy | \n \n Definition: Set of codes for a policy that provides coverage for health care expenses arising from vision services. \r\n\n A health insurance policy that covers benefits for vision care services, prescriptions, and products. \r\n\n |
| 3 | DIS | disability insurance policy | \n \n Definition: An insurance policy that provides a regular payment to compensate for income lost due to the covered party's inability to work because of illness or injury. \r\n\n |
| 3 | EWB | employee welfare benefit plan policy | \n \n Definition: An insurance policy under a benefit plan run by an employer or employee organization for the purpose of providing benefits other than pension-related to employees and their families. Typically provides health-related benefits, benefits for disability, disease or unemployment, or day care and scholarship benefits, among others. An employer sponsored health policy includes coverage of health care expenses arising from sickness or accidental injury, coverage for on-site medical clinics or for dental or vision benefits, which are typically provided under a separate policy. Coverage excludes health care expenses covered by accident or disability, workers' compensation, liability or automobile insurance. \r\n\n |
| 3 | FLEXP | flexible benefit plan policy | \n \n Definition: An insurance policy that covers qualified benefits under a Flexible Benefit plan such as group medical insurance, long and short term disability income insurance, group term life insurance for employees only up to $50,000 face amount, specified disease coverage such as a cancer policy, dental and/or vision insurance, hospital indemnity insurance, accidental death and dismemberment insurance, a medical expense reimbursement plan and a dependent care reimbursement plan. \r\n\n \n Discussion: See UnderwriterRoleTypeCode flexible benefit plan which is defined as a benefit plan that allows employees to choose from several life, health, disability, dental, and other insurance plans according to their individual needs. Also known as cafeteria plans. Authorized under Section 125 of the Revenue Act of 1978. \r\n\n |
| 3 | LIFE | life insurance policy | \n \n Definition: A policy under which the insurer agrees to pay a sum of money upon the occurrence of the covered partys death. In return, the policyholder agrees to pay a stipulated amount called a premium at regular intervals. Life insurance indemnifies the beneficiary for the loss of the insurable interest that a beneficiary has in the life of a covered party. For persons related by blood, a substantial interest established through love and affection, and for all other persons, a lawful and substantial economic interest in having the life of the insured continue. An insurable interest is required when purchasing life insurance on another person. Specific exclusions are often written into the contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion. \r\n\n \n Discussion:A life insurance policy may be used by the covered party as a source of health care coverage in the case of a viatical settlement, which is the sale of a life insurance policy by the policy owner, before the policy matures. Such a sale, at a price discounted from the face amount of the policy but usually in excess of the premiums paid or current cash surrender value, provides the seller an immediate cash settlement. Generally, viatical settlements involve insured individuals with a life expectancy of less than two years. In countries without state-subsidized healthcare and high healthcare costs (e.g. United States), this is a practical way to pay extremely high health insurance premiums that severely ill people face. Some people are also familiar with life settlements, which are similar transactions but involve insureds with longer life expectancies (two to fifteen years). \r\n\n |
| 4 | ANNU | annuity policy | \n \n Definition: A policy that, after an initial premium or premiums, pays out a sum at pre-determined intervals. \r\n\n For example, a policy holder may pay $10,000, and in return receive $150 each month until he dies; or $1,000 for each of 14 years or death benefits if he dies before the full term of the annuity has elapsed. \r\n\n |
| 4 | TLIFE | term life insurance policy | \n \n Definition: Life insurance under which the benefit is payable only if the insured dies during a specified period. If an insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing. \r\n\n |
| 4 | ULIFE | universal life insurance policy | \n \n Definition: Life insurance under which the benefit is payable upon the insuredaTMs death or diagnosis of a terminal illness. If an insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing \r\n\n |
| 3 | PNC | property and casualty insurance policy | \n \n Definition: A type of insurance that covers damage to or loss of the policyholderaTMs property by providing payments for damages to property damage or the injury or death of living subjects. The terms "casualty" and "liability" insurance are often used interchangeably. Both cover the policyholder's legal liability for damages caused to other persons and/or their property. \r\n\n |
| 3 | REI | reinsurance policy | \n \n Definition: An agreement between two or more insurance companies by which the risk of loss is proportioned. Thus the risk of loss is spread and a disproportionately large loss under a single policy does not fall on one insurance company. Acceptance by an insurer, called a reinsurer, of all or part of the risk of loss of another insurance company. \r\n\n \n Discussion: Reinsurance is a means by which an insurance company can protect itself against the risk of losses with other insurance companies. Individuals and corporations obtain insurance policies to provide protection for various risks (hurricanes, earthquakes, lawsuits, collisions, sickness and death, etc.). Reinsurers, in turn, provide insurance to insurance companies. \r\n\n For example, an HMO may purchase a reinsurance policy to protect itself from losing too much money from one insured's particularly expensive health care costs. An insurance company issuing an automobile liability policy, with a limit of $100,000 per accident may reinsure its liability in excess of $10,000. A fire insurance company which issues a large policy generally reinsures a portion of the risk with one or several other companies. Also called risk control insurance or stop-loss insurance.\n \r\n\n |
| 3 | SURPL | surplus line insurance policy | \n \n Definition: \n \r\n\n \n \n A risk or part of a risk for which there is no normal insurance market available. \r\n\n \n \n Insurance written by unauthorized insurance companies. Surplus lines insurance is insurance placed with unauthorized insurance companies through licensed surplus lines agents or brokers. \r\n\n \n \n |
| 3 | UMBRL | umbrella liability insurance policy | \n \n Definition: A form of insurance protection that provides additional liability coverage after the limits of your underlying policy are reached. An umbrella liability policy also protects you (the insured) in many situations not covered by the usual liability policies. \r\n\n |
| 2 | (_ActProgramTypeCode) Abstract | \n \n Definition: A set of codes used to indicate coverage under a program. A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight. Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation. Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds. \r\n\n \n Discussion: Programs do not have policy holders or subscribers. Program eligibles are enrolled based on health status, statutory eligibility, financial status, or age. Program eligibles who are covered parties under the program may be referred to as members, beneficiaries, eligibles, or recipients. Programs risk are underwritten by not for profit organizations such as governmental entities, and the beneficiaries typically do not pay for any or some portion of the cost of coverage. See CoveredPartyRoleType. \r\n\n | |
| 3 | PUBLICPOL | ||
| 3 | WCBPOL | ||
| 3 | CHAR | charity program | \n \n Definition: A program that covers the cost of services provided directly to a beneficiary who typically has no other source of coverage without charge. \r\n\n |
| 3 | CRIME | crime victim program | \n \n Definition: A program that covers the cost of services provided to crime victims for injuries or losses related to the occurrence of a crime. \r\n\n |
| 3 | EAP | employee assistance program | \n \n Definition: An employee assistance program is run by an employer or employee organization for the purpose of providing benefits and covering all or part of the cost for employees to receive counseling, referrals, and advice in dealing with stressful issues in their lives. These may include substance abuse, bereavement, marital problems, weight issues, or general wellness issues. The services are usually provided by a third-party, rather than the company itself, and the company receives only summary statistical data from the service provider. Employee's names and services received are kept confidential. \r\n\n |
| 3 | GOVEMP | government employee health program | \n \n Definition: A set of codes used to indicate a government program that is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health and financial status. Government programs are established or permitted by legislation with provisions for ongoing government oversight. Regulation mandates the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency is charged with implementing the program in accordance to the regulation \r\n\n \n Example: Federal employee health benefit program in the U.S. \r\n\n |
| 3 | HIRISK | high risk pool program | \n \n Definition: A government program that provides health coverage to individuals who are considered medically uninsurable or high risk, and who have been denied health insurance due to a serious health condition. In certain cases, it also applies to those who have been quoted very high premiums a" again, due to a serious health condition. The pool charges premiums for coverage. Because the pool covers high-risk people, it incurs a higher level of claims than premiums can cover. The insurance industry pays into the pool to make up the difference and help it remain viable. \r\n\n |
| 3 | IND | indigenous peoples health program | \n \n Definition: Services provided directly and through contracted and operated indigenous peoples health programs. \r\n\n \n Example: Indian Health Service in the U.S. \r\n\n |
| 3 | MILITARY | military health program | \n \n Definition: A government program that provides coverage for health services to military personnel, retirees, and dependents. A covered party who is a subscriber can choose from among Fee-for-Service (FFS) plans, and their Preferred Provider Organizations (PPO), or Plans offering a Point of Service (POS) Product, or Health Maintenance Organizations. \r\n\n \n Example: In the U.S., TRICARE, CHAMPUS. \r\n\n |
| 3 | RETIRE | retiree health program | \n \n Definition: A government mandated program with specific eligibility requirements based on premium contributions made during employment, length of employment, age, and employment status, e.g., being retired, disabled, or a dependent of a covered party under this program. Benefits typically include ambulatory, inpatient, and long-term care, such as hospice care, home health care and respite care. \r\n\n |
| 3 | SOCIAL | social service program | \n \n Definition: A social service program funded by a public or governmental entity. \r\n\n \n Example: Programs providing habilitation, food, lodging, medicine, transportation, equipment, devices, products, education, training, counseling, alteration of living or work space, and other resources to persons meeting eligibility criteria. \r\n\n |
| 3 | VET | veteran health program | \n \n Definition: Services provided directly and through contracted and operated veteran health programs. \r\n\n |
| 1 | (_ActDetectedIssueManagementCode) Abstract | \n Codes dealing with the management of Detected Issue observations \r\n\n | |
| 2 | (_ActAdministrativeDetectedIssueManagementCode) Abstract | \n Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains. \r\n\n | |
| 3 | (_AuthorizationIssueManagementCode) Abstract | ||
| 4 | EMAUTH | emergency authorization override | \n Used to temporarily override normal authorization rules to gain access to data in a case of emergency. Use of this override code will typically be monitored, and a procedure to verify its proper use may be triggered when used. \r\n\n |
| 5 | 21 | authorization confirmed | \n \n Description: Indicates that the permissions have been externally verified and the request should be processed. \r\n\n |
| 2 | 1 | Therapy Appropriate | \n Confirmed drug therapy appropriate \r\n\n |
| 3 | 19 | Consulted Supplier | \n Consulted other supplier/pharmacy, therapy confirmed \r\n\n |
| 3 | 2 | Assessed Patient | \n Assessed patient, therapy is appropriate \r\n\n |
| 3 | 22 | appropriate indication or diagnosis | \n \n Description: The patient has the appropriate indication or diagnosis for the action to be taken. \r\n\n |
| 3 | 23 | prior therapy documented | \n \n Description: It has been confirmed that the appropriate pre-requisite therapy has been tried. \r\n\n |
| 3 | 3 | Patient Explanation | \n Patient gave adequate explanation \r\n\n |
| 3 | 4 | Consulted Other Source | \n Consulted other supply source, therapy still appropriate \r\n\n |
| 3 | 5 | Consulted Prescriber | \n Consulted prescriber, therapy confirmed \r\n\n |
| 4 | 6 | Prescriber Declined Change | \n Consulted prescriber and recommended change, prescriber declined \r\n\n |
| 3 | 7 | Interacting Therapy No Longer Active/Planned | \n Concurrent therapy triggering alert is no longer on-going or planned \r\n\n |
| 2 | 14 | Supply Appropriate | \n Confirmed supply action appropriate \r\n\n |
| 3 | 15 | Replacement | \n Patient's existing supply was lost/wasted \r\n\n |
| 3 | 16 | Vacation Supply | \n Supply date is due to patient vacation \r\n\n |
| 3 | 17 | Weekend Supply | \n Supply date is intended to carry patient over weekend \r\n\n |
| 3 | 18 | Leave of Absence | \n Supply is intended for use during a leave of absence from an institution. \r\n\n |
| 3 | 20 | additional quantity on separate dispense | \n \n Description: Supply is different than expected as an additional quantity has been supplied in a separate dispense. \r\n\n |
| 2 | 8 | Other Action Taken | \n Order is performed as issued, but other action taken to mitigate potential adverse effects \r\n\n |
| 3 | 10 | Provided Patient Education | \n Provided education or training to the patient on appropriate therapy use \r\n\n |
| 3 | 11 | Added Concurrent Therapy | \n Instituted an additional therapy to mitigate potential negative effects \r\n\n |
| 3 | 12 | Temporarily Suspended Concurrent Therapy | \n Suspended existing therapy that triggered interaction for the duration of this therapy \r\n\n |
| 3 | 13 | Stopped Concurrent Therapy | \n Aborted existing therapy that triggered interaction. \r\n\n |
| 3 | 9 | Instituted Ongoing Monitoring Program | \n Arranged to monitor patient for adverse effects \r\n\n |
| 1 | (_ActExposureCode) Abstract | \n Concepts that identify the type or nature of exposure interaction. Examples include "household", "care giver", "intimate partner", "common space", "common substance", etc. to further describe the nature of interaction. \r\n\n | |
| 2 | CHLDCARE | Day care - Child care Interaction | \n \n Description: Exposure participants' interaction occurred in a child care setting \r\n\n |
| 2 | CONVEYNC | Common Conveyance Interaction | \n \n Description: An interaction where the exposure participants traveled in/on the same vehicle (not necessarily concurrently, e.g. both are passengers of the same plane, but on different flights of that plane). \r\n\n |
| 2 | HLTHCARE | Health Care Interaction - Not Patient Care | \n \n Description: Exposure participants' interaction occurred during the course of health care delivery or in a health care delivery setting, but did not involve the direct provision of care (e.g. a janitor cleaning a patient's hospital room). \r\n\n |
| 2 | HOMECARE | Care Giver Interaction | \n \n Description: Exposure interaction occurred in context of one providing care for the other, i.e. a babysitter providing care for a child, a home-care aide providing assistance to a paraplegic. \r\n\n |
| 2 | HOSPPTNT | Hospital Patient Interaction | \n \n Description: Exposure participants' interaction occurred when both were patients being treated in the same (acute) health care delivery facility. \r\n\n |
| 2 | HOSPVSTR | Hospital Visitor Interaction | \n \n Description: Exposure participants' interaction occurred when one visited the other who was a patient being treated in a health care delivery facility. \r\n\n |
| 2 | HOUSEHLD | Household Interaction | \n \n Description: Exposure interaction occurred in context of domestic interaction, i.e. both participants reside in the same household. \r\n\n |
| 2 | INMATE | Inmate Interaction | \n \n Description: Exposure participants' interaction occurred in the course of one or both participants being incarcerated at a correctional facility \r\n\n |
| 2 | INTIMATE | Intimate Interaction | \n \n Description: Exposure interaction was intimate, i.e. participants are intimate companions (e.g. spouses, domestic partners). \r\n\n |
| 2 | LTRMCARE | Long Term Care Facility Interaction | \n \n Description: Exposure participants' interaction occurred in the course of one or both participants being resident at a long term care facility (second participant may be a visitor, worker, resident or a physical place or object within the facility). \r\n\n |
| 2 | PLACE | Common Space Interaction | \n \n Description: An interaction where the exposure participants were both present in the same location/place/space. \r\n\n |
| 2 | PTNTCARE | Health Care Interaction - Patient Care | \n \n Description: Exposure participants' interaction occurred during the course of health care delivery by a provider (e.g. a physician treating a patient in her office). \r\n\n |
| 2 | SCHOOL2 | School Interaction | \n \n Description: Exposure participants' interaction occurred in an academic setting (e.g., participants are fellow students, or student and teacher). \r\n\n |
| 2 | SOCIAL2 | Social/Extended Family Interaction | \n \n Description: An interaction where the exposure participants are social associates or members of the same extended family \r\n\n |
| 2 | SUBSTNCE | Common Substance Interaction | \n \n Description: An interaction where the exposure participants shared or co-used a common substance (e.g. drugs, needles, or common food item). \r\n\n |
| 2 | TRAVINT | Common Travel Interaction | \n \n Description: An interaction where the exposure participants traveled together in/on the same vehicle/trip (e.g. concurrent co-passengers). \r\n\n |
| 2 | WORK2 | Work Interaction | \n \n Description: Exposure interaction occurred in a work setting, i.e. participants are co-workers. \r\n\n |
| 1 | (_ActFinancialTransactionCode) Abstract | ||
| 2 | CHRG | Standard Charge | \n A type of transaction that represents a charge for a service or product. Expressed in monetary terms. \r\n\n |
| 2 | REV | Standard Charge Reversal | \n A type of transaction that represents a reversal of a previous charge for a service or product. Expressed in monetary terms. It has the opposite effect of a standard charge. \r\n\n |
| 1 | (_ActIncidentCode) Abstract | \n Set of codes indicating the type of incident or accident. \r\n\n | |
| 2 | MVA | Motor vehicle accident | \n Incident or accident as the result of a motor vehicle accident \r\n\n |
| 2 | SCHOOL | School Accident | \n Incident or accident is the result of a school place accident. \r\n\n |
| 2 | SPT | Sporting Accident | \n Incident or accident is the result of a sporting accident. \r\n\n |
| 2 | WPA | Workplace accident | \n Incident or accident is the result of a work place accident \r\n\n |
| 1 | (_ActInformationAccessCode) Abstract | \n \n Description: The type of health information to which the subject of the information or the subject's delegate consents or dissents. \r\n\n | |
| 2 | ACADR | adverse drug reaction access | \n \n Description: Provide consent to collect, use, disclose, or access adverse drug reaction information for a patient. \r\n\n |
| 2 | ACALL | all access | \n \n Description: Provide consent to collect, use, disclose, or access all information for a patient. \r\n\n |
| 2 | ACALLG | allergy access | \n \n Description: Provide consent to collect, use, disclose, or access allergy information for a patient. \r\n\n |
| 2 | ACCONS | informational consent access | \n \n Description: Provide consent to collect, use, disclose, or access informational consent information for a patient. \r\n\n |
| 2 | ACDEMO | demographics access | \n \n Description: Provide consent to collect, use, disclose, or access demographics information for a patient. \r\n\n |
| 2 | ACDI | diagnostic imaging access | \n \n Description: Provide consent to collect, use, disclose, or access diagnostic imaging information for a patient. \r\n\n |
| 2 | ACIMMUN | immunization access | \n \n Description: Provide consent to collect, use, disclose, or access immunization information for a patient. \r\n\n |
| 2 | ACLAB | lab test result access | \n \n Description: Provide consent to collect, use, disclose, or access lab test result information for a patient. \r\n\n |
| 2 | ACMED | medication access | \n \n Description: Provide consent to collect, use, disclose, or access medical condition information for a patient. \r\n\n |
| 2 | ACMEDC | medical condition access | \n \n Definition: Provide consent to view or access medical condition information for a patient. \r\n\n |
| 2 | ACMEN | mental health access | \n \n Description:Provide consent to collect, use, disclose, or access mental health information for a patient. \r\n\n |
| 2 | ACOBS | common observations access | \n \n Description: Provide consent to collect, use, disclose, or access common observation information for a patient. \r\n\n |
| 2 | ACPOLPRG | policy or program information access | \n \n Description: Provide consent to collect, use, disclose, or access coverage policy or program for a patient. \r\n\n |
| 2 | ACPROV | provider information access | \n \n Description: Provide consent to collect, use, disclose, or access provider information for a patient. \r\n\n |
| 2 | ACPSERV | professional service access | \n \n Description: Provide consent to collect, use, disclose, or access professional service information for a patient. \r\n\n |
| 2 | ACSUBSTAB | substance abuse access | \n \n Description:Provide consent to collect, use, disclose, or access substance abuse information for a patient. \r\n\n |
| 1 | (_ActInformationAccessContextCode) Abstract | \n Concepts conveying the context in which authorization given under jurisdictional law, by organizational policy, or by a patient consent directive permits the collection, access, use or disclosure of specified patient health information. \r\n\n | |
| 2 | INFAUT | authorized information transfer | \n Authorization to collect, access, use, or disclose specified patient health information in accordance with jurisdictional law, organizational policy, or a patient's consent directive, which may be implied, deemed, opt-in, opt-out, or explicit. \r\n\n |
| 3 | INFCON | after explicit consent | \n Authorization to collect, access, use, or disclose specified patient health information as explicitly consented to by the subject of the information or the subject's representative. \r\n\n |
| 2 | INFCRT | only on court order | \n Authorization to collect, access, use, or disclose specified patient health information in accordance with judicial system protocol, such as in the case of a subpoena or court order. \r\n\n |
| 2 | INFDNG | only if danger to others | \n Authorization to collect, access, use, or disclose specified patient health information where deemed necessary to avert potential danger to other persons in accordance with jurisdictional law, organizational policy, or standards of practice. For example, disclosure about a person threatening violence. \r\n\n |
| 2 | INFEMER | only in an emergency | \n Authorization to collect, access, use, or disclose specified patient health information in accordance with emergency information transfer protocol dictated by jurisdictional law, organization policy, or standards of practice. For example, sharing of health information during disaster response. \r\n\n |
| 2 | INFPWR | only if public welfare risk | \n Authorization to collect, access, use, or disclose specified patient health information necessary to avert potential public welfare risk in accordance with jurisdictional law, organizational policy, or standards of practice. For example, reporting that a person is a victim of abuse or demonstrating suicidal tendencies. \r\n\n |
| 2 | INFREG | regulatory information transfer | \n Authorization to collect, access, use, or disclose specified patient health information for public health, welfare, and safety purposes in accordance with jurisdictional law, organizational policy, or standards of practice. For example, public health reporting of notifiable conditions. \r\n\n |
| 1 | (_ActInformationCategoryCode) Abstract | \n \n Definition:Indicates the set of information types which may be manipulated or referenced, such as for recommending access restrictions. \r\n\n | |
| 2 | ALLCAT | all categories | \n \n Description: All patient information. \r\n\n |
| 2 | ALLGCAT | allergy category | \n \n Definition:All information pertaining to a patient's allergy and intolerance records. \r\n\n |
| 2 | ARCAT | adverse drug reaction category | \n \n Description: All information pertaining to a patient's adverse drug reactions. \r\n\n |
| 2 | COBSCAT | common observation category | \n \n Definition:All information pertaining to a patient's common observation records (height, weight, blood pressure, temperature, etc.). \r\n\n |
| 2 | DEMOCAT | demographics category | \n \n Definition:All information pertaining to a patient's demographics (such as name, date of birth, gender, address, etc). \r\n\n |
| 2 | DICAT | diagnostic image category | \n \n Definition:All information pertaining to a patient's diagnostic image records (orders & results). \r\n\n |
| 2 | IMMUCAT | immunization category | \n \n Definition:All information pertaining to a patient's vaccination records. \r\n\n |
| 2 | LABCAT | lab test category | \n \n Description: All information pertaining to a patient's lab test records (orders & results) \r\n\n |
| 2 | MEDCCAT | medical condition category | \n \n Definition:All information pertaining to a patient's medical condition records. \r\n\n |
| 2 | MENCAT | mental health category | \n \n Description: All information pertaining to a patient's mental health records. \r\n\n |
| 2 | PSVCCAT | professional service category | \n \n Definition:All information pertaining to a patient's professional service records (such as smoking cessation, counseling, medication review, mental health). \r\n\n |
| 2 | RXCAT | medication category | \n \n Definition:All information pertaining to a patient's medication records (orders, dispenses and other active medications). \r\n\n |
| 1 | (_ActInvoiceElementCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n | |
| 2 | (_ActInvoiceAdjudicationPaymentCode) Abstract | \n Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee and other cost elements such as bonus, retroactive adjustment and transaction fees. \r\n\n | |
| 3 | (_ActInvoiceAdjudicationPaymentGroupCode) Abstract | \n Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc. \r\n\n | |
| 4 | ALEC | alternate electronic | \n Payment initiated by the payor as the result of adjudicating a submitted invoice that arrived to the payor from an electronic source that did not provide a conformant set of HL7 messages (e.g. web claim submission). \r\n\n |
| 4 | BONUS | bonus | \n Bonus payments based on performance, volume, etc. as agreed to by the payor. \r\n\n |
| 4 | CFWD | carry forward adjusment | \n An amount still owing to the payor but the payment is 0$ and this cannot be settled until a future payment is made. \r\n\n |
| 4 | EDU | education fees | \n Fees deducted on behalf of a payee for tuition and continuing education. \r\n\n |
| 4 | EPYMT | early payment fee | \n Fees deducted on behalf of a payee for charges based on a shorter payment frequency (i.e. next day versus biweekly payments. \r\n\n |
| 4 | GARN | garnishee | \n Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee. \r\n\n |
| 4 | INVOICE | submitted invoice | \n Payment is based on a payment intent for a previously submitted Invoice, based on formal adjudication results.. \r\n\n |
| 4 | PINV | paper invoice | \n Payment initiated by the payor as the result of adjudicating a paper (original, may have been faxed) invoice. \r\n\n |
| 4 | PPRD | prior period adjustment | \n An amount that was owed to the payor as indicated, by a carry forward adjusment, in a previous payment advice \r\n\n |
| 4 | PROA | professional association deduction | \n Professional association fee that is collected by the payor from the practitioner/provider on behalf of the association \r\n\n |
| 4 | RECOV | recovery | \n Retroactive adjustment such as fee rate adjustment due to contract negotiations. \r\n\n |
| 4 | RETRO | retro adjustment | \n Bonus payments based on performance, volume, etc. as agreed to by the payor. \r\n\n |
| 4 | TRAN | transaction fee | \n Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee. \r\n\n |
| 3 | (_ActInvoiceAdjudicationPaymentSummaryCode) Abstract | \n Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee, etc. \r\n\n | |
| 4 | CONT | ||
| 4 | DAY | ||
| 4 | LOC | ||
| 4 | MONTH | ||
| 4 | PERIOD | ||
| 4 | PROV | ||
| 4 | WEEK | ||
| 4 | YEAR | ||
| 4 | INVTYPE | invoice type | \n Transaction counts and value totals by invoice type (e.g. RXDINV - Pharmacy Dispense) \r\n\n |
| 4 | PAYEE | payee | \n Transaction counts and value totals by each instance of an invoice payee. \r\n\n |
| 4 | PAYOR | payor | \n Transaction counts and value totals by each instance of an invoice payor. \r\n\n |
| 4 | SENDAPP | sending application | \n Transaction counts and value totals by each instance of a messaging application on a single processor. It is a registered identifier known to the receivers. \r\n\n |
| 2 | (_ActInvoiceDetailCode) Abstract | \n Codes representing a service or product that is being invoiced (billed). The code can represent such concepts as "office visit", "drug X", "wheelchair" and other billable items such as taxes, service charges and discounts. \r\n\n | |
| 3 | (_ActInvoiceDetailClinicalProductCode) Abstract | \n An identifying data string for healthcare products. \r\n\n | |
| 4 | UNSPSC | United Nations Standard Products and Services Classification | \n \n Description:United Nations Standard Products and Services Classification, managed by Uniform Code Council (UCC): www.unspsc.org \r\n\n |
| 3 | (_ActInvoiceDetailDrugProductCode) Abstract | \n An identifying data string for A substance used as a medication or in the preparation of medication. \r\n\n | |
| 4 | GTIN | Global Trade Item Number | \n \n Description:Global Trade Item Number is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council). \r\n\n |
| 4 | UPC | Universal Product Code | \n \n Description:Universal Product Code is one of a wide variety of bar code languages widely used in the United States and Canada for items in stores. \r\n\n |
| 3 | (_ActInvoiceDetailGenericCode) Abstract | \n The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments. \r\n\n | |
| 4 | (_ActInvoiceDetailGenericAdjudicatorCode) Abstract | \n The billable item codes to identify adjudicator specified components to the total billing of a claim. \r\n\n | |
| 5 | COIN | coinsurance | \n That portion of the eligible charges which a covered party must pay for each service and/or product. It is a percentage of the eligible amount for the service/product that is typically charged after the covered party has met the policy deductible. This amount represents the covered party's coinsurance that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. \r\n\n |
| 5 | COPAYMENT | patient co-pay | \n That portion of the eligible charges which a covered party must pay for each service and/or product. It is a defined amount per service/product of the eligible amount for the service/product. This amount represents the covered party's copayment that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. \r\n\n |
| 5 | DEDUCTIBLE | deductible | \n That portion of the eligible charges which a covered party must pay in a particular period (e.g. annual) before the benefits are payable by the adjudicator. This amount represents the covered party's deductible that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. \r\n\n |
| 5 | PAY | payment | \n The guarantor, who may be the patient, pays the entire charge for a service. Reasons for such action may include: there is no insurance coverage for the service (e.g. cosmetic surgery); the patient wishes to self-pay for the service; or the insurer denies payment for the service due to contractual provisions such as the need for prior authorization. \r\n\n |
| 5 | SPEND | spend down | \n That total amount of the eligible charges which a covered party must periodically pay for services and/or products prior to the Medicaid program providing any coverage. This amount represents the covered party's spend down that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results \r\n\n |
| 5 | COINS | co-insurance | \n The covered party pays a percentage of the cost of covered services. \r\n\n |
| 4 | (_ActInvoiceDetailGenericModifierCode) Abstract | \n The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee. \r\n\n | |
| 5 | AFTHRS | non-normal hours | \n Premium paid on service fees in compensation for practicing outside of normal working hours. \r\n\n |
| 5 | ISOL | isolation allowance | \n Premium paid on service fees in compensation for practicing in a remote location. \r\n\n |
| 5 | OOO | out of office | \n Premium paid on service fees in compensation for practicing at a location other than normal working location. \r\n\n |
| 4 | (_ActInvoiceDetailGenericProviderCode) Abstract | \n The billable item codes to identify provider supplied charges or changes to the total billing of a claim. \r\n\n | |
| 5 | CANCAPT | cancelled appointment | \n A charge to compensate the provider when a patient cancels an appointment with insufficient time for the provider to make another appointment with another patient. \r\n\n |
| 5 | DSC | discount | \n A reduction in the amount charged as a percentage of the amount. For example a 5% discount for volume purchase. \r\n\n |
| 5 | ESA | extraordinary service assessment | \n A premium on a service fee is requested because, due to extenuating circumstances, the service took an extraordinary amount of time or supplies. \r\n\n |
| 5 | FFSTOP | fee for service top off | \n Under agreement between the parties (payor and provider), a guaranteed level of income is established for the provider over a specific, pre-determined period of time. The normal course of business for the provider is submission of fee-for-service claims. Should the fee-for-service income during the specified period of time be less than the agreed to amount, a top-up amount is paid to the provider equal to the difference between the fee-for-service total and the guaranteed income amount for that period of time. The details of the agreement may specify (or not) a requirement for repayment to the payor in the event that the fee-for-service income exceeds the guaranteed amount. \r\n\n |
| 5 | FNLFEE | final fee | \n Anticipated or actual final fee associated with treating a patient. \r\n\n |
| 5 | FRSTFEE | first fee | \n Anticipated or actual initial fee associated with treating a patient. \r\n\n |
| 5 | MARKUP | markup or up-charge | \n An increase in the amount charged as a percentage of the amount. For example, 12% markup on product cost. \r\n\n |
| 5 | MISSAPT | missed appointment | \n A charge to compensate the provider when a patient does not show for an appointment. \r\n\n |
| 5 | PERFEE | periodic fee | \n Anticipated or actual periodic fee associated with treating a patient. For example, expected billing cycle such as monthly, quarterly. The actual period (e.g. monthly, quarterly) is specified in the unit quantity of the Invoice Element. \r\n\n |
| 5 | PERMBNS | performance bonus | \n The amount for a performance bonus that is being requested from a payor for the performance of certain services (childhood immunizations, influenza immunizations, mammograms, pap smears) on a sliding scale. That is, for 90% of childhood immunizations to a maximum of $2200/yr. An invoice is created at the end of the service period (one year) and a code is submitted indicating the percentage achieved and the dollar amount claimed. \r\n\n |
| 5 | RESTOCK | restocking fee | \n A charge is requested because the patient failed to pick up the item and it took an amount of time to return it to stock for future use. \r\n\n |
| 5 | TRAVEL | travel | \n A charge to cover the cost of travel time and/or cost in conjuction with providing a service or product. It may be charged per kilometer or per hour based on the effective agreement. \r\n\n |
| 5 | URGENT | urgent | \n Premium paid on service fees in compensation for providing an expedited response to an urgent situation. \r\n\n |
| 4 | (_ActInvoiceDetailTaxCode) Abstract | \n The billable item codes to identify modifications to a billable item charge by a tax factor applied to the amount. As for example 7% provincial sales tax. \r\n\n | |
| 5 | FST | federal sales tax | \n Federal tax on transactions such as the Goods and Services Tax (GST) \r\n\n |
| 5 | HST | harmonized sales Tax | \n Joint Federal/Provincial Sales Tax \r\n\n |
| 5 | PST | provincial/state sales tax | \n Tax levied by the provincial or state jurisdiction such as Provincial Sales Tax \r\n\n |
| 3 | (_ActInvoiceDetailPreferredAccommodationCode) Abstract | \n An identifying data string for medical facility accommodations. \r\n\n | |
| 4 | (_ActEncounterAccommodationCode) Abstract | \n Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type. \r\n\n | |
| 5 | (_HL7AccommodationCode) Abstract | \n \n Description:Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type. \r\n\n | |
| 6 | I | Isolation | \n Accommodations used in the care of diseases that are transmitted through casual contact or respiratory transmission. \r\n\n |
| 6 | P | Private | \n Accommodations in which there is only 1 bed. \r\n\n |
| 6 | S | Suite | \n Uniquely designed and elegantly decorated accommodations with many amenities available for an additional charge. \r\n\n |
| 6 | SP | Semi-private | \n Accommodations in which there are 2 beds. \r\n\n |
| 6 | W | Ward | \n Accommodations in which there are 3 or more beds. \r\n\n |
| 3 | (_ActInvoiceDetailClinicalServiceCode) Abstract | \n An identifying data string for healthcare procedures. \r\n\n | |
| 2 | (_ActInvoiceGroupCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. \r\n\n | |
| 3 | (_ActInvoiceInterGroupCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. \r\n\n The domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice. \r\n\n | |
| 4 | CPNDDRGING | compound drug invoice group | \n A grouping of invoice element groups and details including the ones specifying the compound ingredients being invoiced. It may also contain generic detail items such as markup. \r\n\n |
| 4 | CPNDINDING | compound ingredient invoice group | \n A grouping of invoice element details including the one specifying an ingredient drug being invoiced. It may also contain generic detail items such as tax or markup. \r\n\n |
| 4 | CPNDSUPING | compound supply invoice group | \n A grouping of invoice element groups and details including the ones specifying the compound supplies being invoiced. It may also contain generic detail items such as markup. \r\n\n |
| 4 | DRUGING | drug invoice group | \n A grouping of invoice element details including the one specifying the drug being invoiced. It may also contain generic detail items such as markup. \r\n\n |
| 4 | FRAMEING | frame invoice group | \n A grouping of invoice element details including the ones specifying the frame fee and the frame dispensing cost that are being invoiced. \r\n\n |
| 4 | LENSING | lens invoice group | \n A grouping of invoice element details including the ones specifying the lens fee and the lens dispensing cost that are being invoiced. \r\n\n |
| 4 | PRDING | product invoice group | \n A grouping of invoice element details including the one specifying the product (good or supply) being invoiced. It may also contain generic detail items such as tax or discount. \r\n\n |
| 3 | (_ActInvoiceRootGroupCode) Abstract | \n Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. \r\n\n Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. \r\n\n Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is only specified for the root (top level) invoice element group for an Invoice. \r\n\n | |
| 4 | CPINV | clinical product invoice | \n Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s). \r\n\n For example, a crutch or a wheelchair. \r\n\n |
| 4 | CSINV | clinical service invoice | \n Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services. \r\n\n [1] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service. \r\n\n For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization). \r\n\n [2] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services. The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together. \r\n\n For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together. \r\n\n [3] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time. \r\n\n For example, the same Chiropractic adjustment (service or treatment) delivered on 3 separate occasions over a period of time at the discretion of the provider (e.g. month). \r\n\n |
| 4 | CSPINV | clinical service and product | \n A clinical Invoice Grouping consisting of one or more services and one or more product. Billing for these service(s) and product(s) are supported by multiple clinical billable events (acts). \r\n\n All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. \r\n\n For example , a brace (product) invoiced together with the fitting (service). \r\n\n |
| 4 | FININV | financial invoice | \n Invoice Grouping without clinical justification. These will not require identification of participants and associations from a clinical context such as patient and provider. \r\n\n Examples are interest charges and mileage. \r\n\n |
| 4 | OHSINV | oral health service | \n A clinical Invoice Grouping consisting of one or more oral health services. Billing for these service(s) are supported by multiple clinical billable events (acts). \r\n\n All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. \r\n\n |
| 4 | PAINV | preferred accommodation invoice | \n HealthCare facility preferred accommodation invoice. \r\n\n |
| 4 | RXCINV | Rx compound invoice | \n Pharmacy dispense invoice for a compound. \r\n\n |
| 4 | RXDINV | Rx dispense invoice | \n Pharmacy dispense invoice not involving a compound \r\n\n |
| 4 | SBFINV | sessional or block fee invoice | \n Clinical services invoice where the Invoice Group contains one billable item for multiple clinical services in one or more sessions. \r\n\n |
| 4 | VRXINV | vision dispense invoice | \n Vision dispense invoice for up to 2 lens (left and right), frame and optional discount. Eye exams are invoiced as a clinical service invoice. \r\n\n |
| 1 | (_ActInvoiceElementSummaryCode) Abstract | \n Identifies the different types of summary information that can be reported by queries dealing with Statement of Financial Activity (SOFA). The summary information is generally used to help resolve balance discrepancies between providers and payors. \r\n\n | |
| 2 | (_InvoiceElementAdjudicated) Abstract | \n Total counts and total net amounts adjudicated for all Invoice Groupings that were adjudicated within a time period based on the adjudication date of the Invoice Grouping. \r\n\n | |
| 3 | ADNFPPELAT | adjud. nullified prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFPPELCT | adjud. nullified prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFPPMNAT | adjud. nullified prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNFPPMNCT | adjud. nullified prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNFSPELAT | adjud. nullified same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFSPELCT | adjud. nullified same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | ADNFSPMNAT | adjud. nullified same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNFSPMNCT | adjud. nullified same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. \r\n\n |
| 3 | ADNPPPELAT | adjud. non-payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPPPELCT | adjud. non-payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPPPMNAT | adjud. non-payee payable prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADNPPPMNCT | adjud. non-payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADNPSPELAT | adjud. non-payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPSPELCT | adjud. non-payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | ADNPSPMNAT | adjud. non-payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADNPSPMNCT | adjud. non-payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | ADPPPPELAT | adjud. payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPPPELCT | adjud. payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPPPMNAT | adjud. payee payable prior-period manual amout | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADPPPPMNCT | adjud. payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADPPSPELAT | adjud. payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPSPELCT | adjud. payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | ADPPSPMNAT | adjud. payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADPPSPMNCT | adjud. payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | ADRFPPELAT | adjud. refused prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFPPELCT | adjud. refused prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFPPMNAT | adjud. refused prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 3 | ADRFPPMNCT | adjud. refused prior-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 3 | ADRFSPELAT | adjud. refused same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFSPELCT | adjud. refused same-period electronic count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted electronically. \r\n\n |
| 3 | ADRFSPMNAT | adjud. refused same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 3 | ADRFSPMNCT | adjud. refused same-period manual count | \n Identifies the total number of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted manually. \r\n\n |
| 2 | (_InvoiceElementPaid) Abstract | \n Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date. \r\n\n | |
| 3 | PDNFPPELAT | paid nullified prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFPPELCT | paid nullified prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFPPMNAT | paid nullified prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNFPPMNCT | paid nullified prior-period manual count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNFSPELAT | paid nullified same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFSPELCT | paid nullified same-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently cancelled in the specified period and submitted electronically. \r\n\n |
| 3 | PDNFSPMNAT | paid nullified same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNFSPMNCT | paid nullified same-period manual count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. \r\n\n |
| 3 | PDNPPPELAT | paid non-payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPPPELCT | paid non-payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPPPMNAT | paid non-payee payable prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDNPPPMNCT | paid non-payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDNPSPELAT | paid non-payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPSPELCT | paid non-payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. \r\n\n |
| 3 | PDNPSPMNAT | paid non-payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDNPSPMNCT | paid non-payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. \r\n\n |
| 3 | PDPPPPELAT | paid payee payable prior-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPPPELCT | paid payee payable prior-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPPPMNAT | paid payee payable prior-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | PDPPPPMNCT | paid payee payable prior-period manual count | \n Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | PDPPSPELAT | paid payee payable same-period electronic amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPSPELCT | paid payee payable same-period electronic count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. \r\n\n |
| 3 | PDPPSPMNAT | paid payee payable same-period manual amount | \n Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 3 | PDPPSPMNCT | paid payee payable same-period manual count | \n Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. \r\n\n |
| 2 | (_InvoiceElementSubmitted) Abstract | \n Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included. \r\n\n | |
| 3 | SBBLELAT | submitted billed electronic amount | \n Identifies the total net amount billed for all submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBBLELCT | submitted billed electronic count | \n Identifies the total number of submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBNFELAT | submitted nullified electronic amount | \n Identifies the total net amount billed for all submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBNFELCT | submitted cancelled electronic count | \n Identifies the total number of submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included. \r\n\n |
| 3 | SBPDELAT | submitted pending electronic amount | \n Identifies the total net amount billed for all submitted Invoice Groupings that are pended or held by the payor, within a time period and submitted electronically. Adjudicated invoice elements are not included. \r\n\n |
| 3 | SBPDELCT | submitted pending electronic count | \n Identifies the total number of submitted Invoice Groupings that are pended or held by the payor, within a time period and submitted electronically. Adjudicated invoice elements are not included. \r\n\n |
| 1 | (_ActInvoiceOverrideCode) Abstract | \n Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results. \r\n\n | |
| 2 | COVGE | coverage problem | \n Insurance coverage problems have been encountered. Additional explanation information to be supplied. \r\n\n |
| 2 | EFORM | electronic form to follow | \n Electronic form with supporting or additional information to follow. \r\n\n |
| 2 | FAX | fax to follow | \n Fax with supporting or additional information to follow. \r\n\n |
| 2 | GFTH | good faith indicator | \n The medical service was provided to a patient in good faith that they had medical coverage, although no evidence of coverage was available before service was rendered. \r\n\n |
| 2 | LATE | late invoice | \n Knowingly over the payor's published time limit for this invoice possibly due to a previous payor's delays in processing. Additional reason information will be supplied. \r\n\n |
| 2 | MANUAL | manual review | \n Manual review of the invoice is requested. Additional information to be supplied. This may be used in the case of an appeal. \r\n\n |
| 2 | OOJ | out of jurisdiction | \n The medical service and/or product was provided to a patient that has coverage in another jurisdiction. \r\n\n |
| 2 | ORTHO | orthodontic service | \n The service provided is required for orthodontic purposes. If the covered party has orthodontic coverage, then the service may be paid. \r\n\n |
| 2 | PAPER | paper documentation to follow | \n Paper documentation (or other physical format) with supporting or additional information to follow. \r\n\n |
| 2 | PIE | public insurance exhausted | \n Public Insurance has been exhausted. Invoice has not been sent to Public Insuror and therefore no Explanation Of Benefits (EOB) is provided with this Invoice submission. \r\n\n |
| 2 | PYRDELAY | delayed by a previous payor | \n Allows provider to explain lateness of invoice to a subsequent payor. \r\n\n |
| 2 | REFNR | referral not required | \n Rules of practice do not require a physician's referral for the provider to perform a billable service. \r\n\n |
| 2 | REPSERV | repeated service | \n The same service was delivered within a time period that would usually indicate a duplicate billing. However, the repeated service is a medical \tnecessity and therefore not a duplicate. \r\n\n |
| 2 | UNRELAT | unrelated service | \n The service provided is not related to another billed service. For example, 2 unrelated services provided on the same day to the same patient which may normally result in a refused payment for one of the items. \r\n\n |
| 2 | VERBAUTH | verbal authorization | \n The provider has received a verbal permission from an authoritative source to perform the service or supply the item being invoiced. \r\n\n |
| 1 | (_ActListCode) Abstract | \n Provides codes associated with ActClass value of LIST (working list) \r\n\n | |
| 2 | (_ActObservationList) Abstract | ||
| 3 | CARELIST | care plan | \n List of acts representing a care plan. The acts can be in a varierty of moods including event (EVN) to record acts that have been carried out as part of the care plan. \r\n\n |
| 3 | CONDLIST | condition list | \n List of condition observations. \r\n\n |
| 4 | INTOLIST | intolerance list | \n List of intolerance observations. \r\n\n |
| 4 | PROBLIST | problem list | \n List of problem observations. \r\n\n |
| 4 | RISKLIST | risk factors | \n List of risk factor observations. \r\n\n |
| 3 | GOALLIST | goal list | \n List of observations in goal mood. \r\n\n |
| 2 | (_ActTherapyDurationWorkingListCode) Abstract | \n Codes used to identify different types of 'duration-based' working lists. Examples include "Continuous/Chronic", "Short-Term" and "As-Needed". \r\n\n | |
| 3 | (_ActMedicationTherapyDurationWorkingListCode) Abstract | \n \n Definition:A collection of concepts that identifies different types of 'duration-based' mediation working lists. \r\n\n \n Examples:"Continuous/Chronic" "Short-Term" and "As Needed" \r\n\n | |
| 4 | ACU | short term/acute | \n \n Definition:A list of medications which the patient is only expected to consume for the duration of the current order or limited set of orders and which is not expected to be renewed. \r\n\n |
| 4 | CHRON | continuous/chronic | \n \n Definition:A list of medications which are expected to be continued beyond the present order and which the patient should be assumed to be taking unless explicitly stopped. \r\n\n |
| 4 | ONET | one time | \n \n Definition:A list of medications which the patient is intended to be administered only once. \r\n\n |
| 4 | PRN | as needed | \n \n Definition:A list of medications which the patient will consume intermittently based on the behavior of the condition for which the medication is indicated. \r\n\n |
| 2 | MEDLIST | medication list | \n List of medications. \r\n\n |
| 3 | CURMEDLIST | current medication list | \n List of current medications. \r\n\n |
| 3 | DISCMEDLIST | discharge medication list | \n List of discharge medications. \r\n\n |
| 3 | HISTMEDLIST | medication history | \n Historical list of medications. \r\n\n |
| 1 | (_ActMonitoringProtocolCode) Abstract | \n Identifies types of monitoring programs \r\n\n | |
| 2 | CTLSUB | Controlled Substance | \n A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction. \r\n\n |
| 2 | INV | investigational | \n \n Definition:A monitoring program that focuses on a drug which is under investigation and has not received regulatory approval for the condition being investigated \r\n\n |
| 2 | LU | limited use | \n \n Description:A drug that can be prescribed (and reimbursed) only if it meets certain criteria. \r\n\n |
| 2 | OTC | non prescription medicine | \n Medicines designated in this way may be supplied for patient use without a prescription. The exact form of categorisation will vary in different realms. \r\n\n |
| 2 | RX | prescription only medicine | \n Some form of prescription is required before the related medicine can be supplied for a patient. The exact form of regulation will vary in different realms. \r\n\n |
| 2 | SA | special authorization | \n \n Definition:A drug that requires prior approval (to be reimbursed) before being dispensed \r\n\n |
| 2 | SAC | special access | \n \n Description:A drug that requires special access permission to be prescribed and dispensed. \r\n\n |
| 1 | (_ActNonObservationIndicationCode) Abstract | \n \n Description:Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms. \r\n\n | |
| 2 | IND01 | imaging study requiring contrast | \n \n Description:Contrast agent required for imaging study. \r\n\n |
| 2 | IND02 | colonoscopy prep | \n \n Description:Provision of prescription or direction to consume a product for purposes of bowel clearance in preparation for a colonoscopy. \r\n\n |
| 2 | IND03 | prophylaxis | \n \n Description:Provision of medication as a preventative measure during a treatment or other period of increased risk. \r\n\n |
| 2 | IND04 | surgical prophylaxis | \n \n Description:Provision of medication during pre-operative phase; e.g., antibiotics before dental surgery or bowel prep before colon surgery. \r\n\n |
| 2 | IND05 | pregnancy prophylaxis | \n \n Description:Provision of medication for pregnancy --e.g., vitamins, antibiotic treatments for vaginal tract colonization, etc. \r\n\n |
| 1 | (_ActObservationVerificationType) Abstract | \n Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity. \r\n\n \n Examples:\n \r\n\n \n \n Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program \r\n\n \n \n Verification of record - e.g., person has record in an immunization registry \r\n\n \n \n Verification of enumeration - e.g. NPI \r\n\n \n \n Verification of Board Certification - provider specific \r\n\n \n \n Verification of Certification - e.g. JAHCO, NCQA, URAC \r\n\n \n \n Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria \r\n\n \n \n Verification of Provider Credentials \r\n\n \n \n Verification of no adverse findings - e.g. on National Provider Data Bank, Health Integrity Protection Data Base (HIPDB) \r\n\n \n \n | |
| 2 | VFPAPER | verify paper | \n \n Definition:Indicates that the paper version of the record has, should be or is being verified against the electronic version. \r\n\n |
| 1 | (_ActPaymentCode) Abstract | \n Code identifying the method or the movement of payment instructions. \r\n\n Codes are drawn from X12 data element 591 (PaymentMethodCode) \r\n\n | |
| 2 | ACH | Automated Clearing House | \n Automated Clearing House (ACH). \r\n\n |
| 2 | CHK | Cheque | \n A written order to a bank to pay the amount specified from funds on deposit. \r\n\n |
| 2 | DDP | Direct Deposit | \n Electronic Funds Transfer (EFT) deposit into the payee's bank account \r\n\n |
| 2 | NON | Non-Payment Data | \n Non-Payment Data. \r\n\n |
| 1 | (_ActPharmacySupplyType) Abstract | \n Identifies types of dispensing events \r\n\n | |
| 2 | DF | Daily Fill | \n A fill providing sufficient supply for one day \r\n\n |
| 2 | EM | Emergency Supply | \n A supply action where there is no 'valid' order for the supplied medication. E.g. Emergency vacation supply, weekend supply (when prescriber is unavailable to provide a renewal prescription) \r\n\n |
| 3 | SO | Script Owing | \n An emergency supply where the expectation is that a formal order authorizing the supply will be provided at a later date. \r\n\n |
| 2 | FF | First Fill | \n The initial fill against an order. (This includes initial fills against refill orders.) \r\n\n |
| 3 | FFS | ||
| 3 | FFC | First Fill - Complete | \n A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets). \r\n\n |
| 4 | FFCS | ||
| 3 | FFP | First Fill - Part Fill | \n A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) \r\n\n |
| 3 | FFPS | ||
| 3 | FFSS | first fill, partial strength | \n A first fill where the strength supplied is less than the ordered strength. (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 4 | FFPS | ||
| 4 | FFCS | ||
| 4 | TFS | ||
| 3 | TF | Trial Fill | \n A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance. \r\n\n |
| 4 | TFS | ||
| 2 | FS | Floor stock | \n A supply action to restock a smaller more local dispensary. \r\n\n |
| 2 | MS | Manufacturer Sample | \n A supply of a manufacturer sample \r\n\n |
| 2 | RF | Refill | \n A fill against an order that has already been filled (or partially filled) at least once. \r\n\n |
| 3 | DF | ||
| 3 | UD | Unit Dose | \n A supply action that provides sufficient material for a single dose. \r\n\n |
| 3 | RFC | Refill - Complete | \n A refill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets.) \r\n\n |
| 4 | RFCS | refill complete partial strength | \n A refill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets.) and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | RFF | Refill (First fill this facility) | \n The first fill against an order that has already been filled at least once at another facility. \r\n\n |
| 4 | RFFS | refill partial strength (first fill this facility) | \n The first fill against an order that has already been filled at least once at another facility and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | RFP | Refill - Part Fill | \n A refill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) \r\n\n |
| 4 | RFPS | refill part fill partial strength | \n A refill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | RFS | refill partial strength | \n A fill against an order that has already been filled (or partially filled) at least once and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 3 | TB | Trial Balance | \n A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided. \r\n\n |
| 4 | TBS | trial balance partial strength | \n A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). \r\n\n |
| 2 | UD | ||
| 2 | UDE | unit dose equivalent | \n A supply action that provides sufficient material for a single dose via multiple products. E.g. 2 50mg tablets for a 100mg unit dose. \r\n\n |
| 1 | (_ActPolicyType) Abstract | \n \n Description:Types of policies that further specify the ActClassPolicy value set. \r\n\n | |
| 2 | (_ActPrivacyPolicy) Abstract | \n A policy deeming certain information to be private to an individual or organization. \r\n\n \n Definition: A mandate, obligation, requirement, rule, or expectation relating to privacy. \r\n\n \n Discussion: ActPrivacyPolicyType codes support the designation of the 1..* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor. 1..* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode. Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates. \r\n\n \n Usage Note: Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced. \r\n\n | |
| 3 | (_ActConsentDirective) Abstract | \n Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. \r\n\n \n Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context, and are considered closely related or synonymous from a legal perspective. \r\n\n \n Examples: \n \r\n\n \n Healthcare Privacy Consent Directive permitting or restricting in whole or part the collection, access, use, and disclosure of health information, and any associated handling caveats.\n Healthcare Medical Consent Directive to receive medical procedures after being informed of risks and benefits, thereby reducing the grantee's liability.\n Research Informed Consent for participation in clinical trials and disclosure of health information after being informed of risks and benefits, thereby reducing the grantee's liability.\n Substitute decision maker delegation in which the grantee assumes responsibility to act on behalf of the grantor.\n Contracts in which the agreement requires assent/dissent by the grantor of terms offered by a grantee, a consumer opts out of an "award" system for use of a retailer's marketing or credit card vendor's point collection cards in exchange for allowing purchase tracking and profiling.\n A mobile device or App privacy policy and terms of service to which a user must agree in whole or in part in order to utilize the service.\n Agreements between a client and an authorization server or between an authorization server and a resource operator and/or resource owner permitting or restricting e.g., collection, access, use, and disclosure of information, and any associated handling caveats.\n \n | |
| 4 | EMRGONLY | emergency only | \n This general consent directive specifically limits disclosure of health information for purpose of emergency treatment. Additional parameters may further limit the disclosure to specific users, roles, duration, types of information, and impose uses obligations. \r\n\n \n Definition: Opt-in to disclosure of health information for emergency only consent directive. \r\n\n |
| 4 | GRANTORCHOICE | grantor choice | \n A grantor's terms of agreement to which a grantee may assent or dissent, and which may include an opportunity for a grantee to request restrictions or extensions. \r\n\n \n Comment: A grantor typically is able to stipulate preferred terms of agreement when the grantor has control over the topic of the agreement, which a grantee must accept in full or may be offered an opportunity to extend or restrict certain terms. \r\n\n \n Usage Note: If the grantor's term of agreement must be accepted in full, then this is considered "basic consent". If a grantee is offered an opportunity to extend or restrict certain terms, then the agreement is considered "granular consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A PHR account holder [grantor] may require any PHR user [grantee] to accept the terms of agreement in full, or may permit a PHR user to extend or restrict terms selected by the account holder or requested by the PHR user.\n Non-healthcare: The owner of a resource server [grantor] may require any authorization server [grantee] to meet authorization requirements stipulated in the grantor's terms of agreement. \n \n |
| 4 | IMPLIED | implied consent | \n A grantor's presumed assent to the grantee's terms of agreement is based on the grantor's behavior, which may result from not expressly assenting to the consent directive offered, or from having no right to assent or dissent offered by the grantee. \r\n\n \n Comment: Implied or "implicit" consent occurs when the behavior of the grantor is understood by a reasonable person to signal agreement to the grantee's terms. \r\n\n \n Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered "basic consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient schedules an appointment with a provider, and either does not take the opportunity to expressly assent or dissent to the provider's consent directive, does not have an opportunity to do so, as in the case where emergency care is required, or simply behaves as though the patient [grantor] agrees to the rights granted to the provider [grantee] in an implicit consent directive.\n An injured and unconscious patient is deemed to have assented to emergency treatment by those permitted to do so under jurisdictional laws, e.g., Good Samaritan laws.\n Non-healthcare: Upon receiving a driver's license, the driver is deemed to have assented without explicitly consenting to undergoing field sobriety tests.\n A corporation that does business in a foreign nation is deemed to have deemed to have assented without explicitly consenting to abide by that nation's laws.\n \n |
| 4 | IMPLIEDD | implied consent with opportunity to dissent | \n A grantor's presumed assent to the grantee's terms of agreement, which is based on the grantor's behavior, and includes a right to dissent to certain terms. \r\n\n \n Comment: A grantor assenting to the grantee's terms of agreement may or may not exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent. \r\n\n \n Usage Note: Implied or "implicit" consent with an "opportunity to dissent" occurs when the grantor's behavior is understood by a reasonable person to signal assent to the grantee's terms of agreement whether the grantor requests or the grantee approves further restrictions, is considered "granular consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare Examples: A healthcare provider deems a patient's assent to disclosure of health information to family members and friends, but offers an opportunity or permits the patient to dissent to such disclosures.\n A health information exchanges deems a patient to have assented to disclosure of health information for treatment purposes, but offers the patient an opportunity to dissents to disclosure to particular provider organizations.\n Non-healthcare Examples: A bank deems a banking customer's assent to specified collection, access, use, or disclosure of financial information as a requirement of holding a bank account, but provides the user an opportunity to limit third-party collection, access, use or disclosure of that information for marketing purposes.\n \n |
| 4 | NOCONSENT | no consent | \n No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement. \r\n\n \n Comment: A "No Consent" policy scheme provides no opportunity for accommodation of an individual's preferences, and may not comply with Fair Information Practice Principles [FIPP] by enabling the data subject to object, access collected information, correct errors, or have accounting of disclosures. \r\n\n \n Usage Note: The grantee's terms of agreement, may be available to the grantor by reviewing the grantee's privacy policies, but there is no notice by which a grantor is apprised of the policy directly or able to acknowledge. \r\n\n \n Examples: \n \r\n\n \n Healthcare: Without notification or an opportunity to assent or dissent, a patient's health information is automatically included in and available (often according to certain rules) through a health information exchange. Note that this differs from implied consent, where the patient is assumed to have consented.\n Without notification or an opportunity to assent or dissent, a patient's health information is collected, accessed, used, or disclosed for research, public health, security, fraud prevention, court order, or law enforcement.\n Non-healthcare: Without notification or an opportunity to assent or dissent, a consumer's healthcare or non-healthcare internet searches are aggregated for secondary uses such as behavioral tracking and profiling.\n Without notification or an opportunity to assent or dissent, a consumer's location and activities in a shopping mall are tracked by RFID tags on purchased items.\n \n |
| 4 | NOPP | notice of privacy practices | \n Acknowledgement of custodian notice of privacy practices. \r\n\n \n Usage Notes: This type of consent directive acknowledges a custodian's notice of privacy practices including its permitted collection, access, use and disclosure of health information to users and for purposes of use specified. \r\n\n |
| 4 | OPTIN | opt-in | \n A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. \r\n\n \n Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. \r\n\n \n Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered "basic consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient [grantor] signs a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies.\n Non-healthcare: An employee [grantor] signs an employer's [grantee's] non-disclosure and non-compete agreement.\n \n |
| 4 | OPTINR | opt-in with restrictions | \n A grantor's assent to the grantee's terms of an agreement with an opportunity for to dissent to certain grantor or grantee selected terms. \r\n\n \n Comment: A grantor dissenting to the grantee's terms of agreement may or may not exercise a right to assent to grantor's pre-approved restrictions or to grantee's selected terms to which a grantor may dissent. \r\n\n \n Usage Note: Opt-in with restrictions is considered "granular consent" because the grantor has an opportunity to narrow the permissions sought by the grantee. \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient assent to grantee's consent directive terms for collection, access, use, or disclosure of health information, and dissents to disclosure to certain recipients as allowed by the provider's pre-approved restriction list.\n Non-Healthcare: A cell phone user assents to the cell phone's privacy practices and terms of use, but dissents from location tracking by turning off the cell phone's tracking capability.\n \n |
| 4 | OPTOUT | op-out | \n A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms. \r\n\n \n Comment: Rejection of a grantee's terms of agreement pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. \r\n\n \n Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered "basic consent". \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient [grantor] declines to sign a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, revocation policies, and consequences of not assenting.\n Non-healthcare: An employee [grantor] refuses to sign an employer's [grantee's] agreement not to join unions or participate in a strike where state law protects employee's collective bargaining rights.\n A citizen [grantor] refuses to enroll in mandatory government [grantee] health insurance based on religious beliefs, which is an exemption.\n \n |
| 4 | OPTOUTE | opt-out with exceptions | \n A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms. \r\n\n \n Comment: A rejection of a grantee's terms of agreement while assenting to certain permissions sought by the grantee or requesting approval of additional grantor terms. \r\n\n \n Usage Note: Opt-out with exceptions is considered a "granular consent" because the grantor has an opportunity to accept certain permissions sought by the grantee or request additional grantor terms, while rejecting other grantee terms. \r\n\n \n Examples: \n \r\n\n \n Healthcare: A patient [grantor] dissents to a health information exchange consent directive with the exception of disclosure based on a limited "time to live" shared secret [e.g., a token or password], which the patient can give to a provider when seeking care.\n Non-healthcare: A social media user [grantor] dissents from public access to their account, but assents to access to a circle of friends.\n \n |
| 3 | (_ActPrivacyLaw) Abstract | \n A jurisdictional mandate, regulation, obligation, requirement, rule, or expectation deeming certain information to be private to an individual or organization, which is imposed on: \r\n\n \n The activity of a governed party\n The behavior of a governed party\n The manner in which an act is executed by a governed party\n \n | |
| 4 | _ActUSPrivacyLaw | _ActUSPrivacyLaw | \n \n Definition: A jurisdictional mandate in the U.S. relating to privacy. \r\n\n \n Usage Note: ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1. \r\n\n |
| 5 | 42CFRPart2 | 42 CFR Part2 | \n 42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program. \r\n\n \n Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 5 | CommonRule | Common Rule | \n U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements. \r\n\n \n Definition: U.S. federal laws governing research-related privacy policies. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. \r\n\n |
| 5 | HIPAANOPP | HIPAA notice of privacy practices | \n The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law. \r\n\n \n Definition: Notification of HIPAA Privacy Practices. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. \r\n\n |
| 5 | HIPAAPsyNotes | HIPAA psychotherapy notes | \n The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes. \r\n\n \n Definition: Authorization that must be obtained for disclosure of psychotherapy notes. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 5 | HIPAASelfPay | HIPAA self-pay | \n Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan. \r\n\n \n Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full. \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 5 | Title38Section7332 | Title 38 Section 7332 | \n Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfil the duties of the contract; and researchers who provide assurances that the information will not be identified in any report. This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes. \r\n\n \n Definition: Title 38 Part 1 - Section 1.462 Confidentiality restrictions. \r\n\n (a) General. The patient records to which Sections 1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b). \r\n\n \n Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. \r\n\n |
| 3 | (_InformationSensitivityPolicy) Abstract | \n A mandate, obligation, requirement, rule, or expectation characterizing the value or importance of a resource and may include its vulnerability. (Based on ISO7498-2:1989. Note: The vulnerability of personally identifiable sensitive information may be based on concerns that the unauthorized disclosure may result in social stigmatization or discrimination.) Description: Types of Sensitivity policy that apply to Acts or Roles. A sensitivity policy is adopted by an enterprise or group of enterprises (a 'policy domain') through a formal data use agreement that stipulates the value, importance, and vulnerability of information. A sensitivity code representing a sensitivity policy may be associated with criteria such as categories of information or sets of information identifiers (e.g., a value set of clinical codes or branch in a code system hierarchy). These criteria may in turn be used for the Policy Decision Point in a Security Engine. A sensitivity code may be used to set the confidentiality code used on information about Acts and Roles to trigger the security mechanisms required to control how security principals (i.e., a person, a machine, a software application) may act on the information (e.g., collection, access, use, or disclosure). Sensitivity codes are never assigned to the transport or business envelope containing patient specific information being exchanged outside of a policy domain as this would disclose the information intended to be protected by the policy. When sensitive information is exchanged with others outside of a policy domain, the confidentiality code on the transport or business envelope conveys the receiver's responsibilities and indicates the how the information is to be safeguarded without unauthorized disclosure of the sensitive information. This ensures that sensitive information is treated by receivers as the sender intends, accomplishing interoperability without point to point negotiations. \r\n\n \n Usage Note: Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an employee's sensitivity code would make little sense for use outside of a policy domain. 'Taboo' would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable InformationSensitivityPolicy Act.code may be useful in some scenarios if used in combination with a sensitivity identifier and/or Act.title. \r\n\n | |
| 4 | (_ActInformationSensitivityPolicy) Abstract | \n Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." \r\n\n \n Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. \r\n\n | |
| 5 | ETH | substance abuse information sensitivity | \n Policy for handling alcohol or drug-abuse information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to alcohol or drug-abuse information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | GDIS | genetic disease information sensitivity | \n Policy for handling genetic disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to genetic disease information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | HIV | HIV/AIDS information sensitivity | \n Policy for handling HIV or AIDS information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to HIV or AIDS information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | MST | military sexual trauma information sensitivity | \n Policy for handling information related to sexual assault or repeated, threatening sexual harassment that occurred while the patient was in the military, which is afforded heightened confidentiality. \r\n\n Access control concerns for military sexual trauma is based on the patient being subject to control by a higher ranking military perpetrator and/or censure by others within the military unit. Due to the relatively unfettered access to healthcare information by higher ranking military personnel and those who have command over the patient, there is a need to sequester this information outside of the typical controls on access to military health records. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 5 | SCA | sickle cell anemia information sensitivity | \n Policy for handling sickle cell disease information, which is afforded heightened confidentiality. Information handling protocols are based on organizational policies related to sickle cell disease information, which is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then the Act valued with this ActCode should be associated with an Act valued with any applicable laws from the ActPrivacyLaw code system. \r\n\n |
| 5 | SDV | sexual assault, abuse, or domestic violence information sensitivity | \n Policy for handling sexual assault, abuse, or domestic violence information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexual assault, abuse, or domestic violence information that is deemed sensitive. \r\n\n SDV code covers violence perpetrated by related and non-related persons. This code should be specific to physical and mental trauma caused by a related person only. The access control concerns are keeping the patient safe from the perpetrator who may have an abusive psychological control over the patient, may be stalking the patient, or may try to manipulate care givers into allowing the perpetrator to make contact with the patient. The definition needs to be clarified. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | SEX | sexuality and reproductive health information sensitivity | \n Policy for handling sexuality and reproductive health information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexuality and reproductive health information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | SPI | specially protected information sensitivity | \n Policy for handling information deemed specially protected by law or policy including substance abuse, substance use, psychiatric, mental health, behavioral health, and cognitive disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 6 | BH | behavioral health information sensitivity | \n Policy for handling information related to behavioral and emotional disturbances affecting social adjustment and physical health, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 7 | COGN | cognitive disability information sensitivity | \n Policy for handling information related to cognitive disability disorders and conditions caused by these disorders, which are afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n Examples may include dementia, traumatic brain injury, attention deficit, hearing and visual disability such as dyslexia and other disorders and related conditions which impair learning and self-sufficiency. However, the cognitive disabilities to which this term may apply versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. \r\n\n |
| 7 | DVD | developmental disability information sensitivity | \n Policy for handling information related to developmental disability disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n A diverse group of chronic conditions that are due to mental or physical impairments impacting activities of daily living, self-care, language acuity, learning, mobility, independent living and economic self-sufficiency. Examples may include Down syndrome and Autism spectrum. However, the developmental disabilities to which this term applies versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. \r\n\n |
| 7 | EMOTDIS | emotional disturbance information sensitivity | \n Policy for handling information related to emotional disturbance disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n Typical used to characterize behavioral and mental health issues of adolescents where the disorder may be temporarily diagnosed in order to avoid the potential and unnecessary stigmatizing diagnoses of disorder long term. \r\n\n |
| 6 | MH | mental health information sensitivity | \n Policy for handling information related to psychological disorders, which is afforded heightened confidentiality. Mental health information may be deemed specifically sensitive and distinct from physical health, substance use disorders, and behavioral disabilities and disorders in some jurisdictions. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 6 | PSY | psychiatry disorder information sensitivity | \n Policy for handling psychiatry psychiatric disorder information, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 6 | PSYTHPN | psychotherapy note information sensitivity | \n Policy for handling psychotherapy note information, which is afforded heightened confidentiality. \r\n\n \n Usage Note: In some jurisdiction, disclosure of psychotherapy notes requires patient consent. \r\n\n If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 6 | SUD | substance use disorder information sensitivity | \n Policy for handling information related to alcohol or drug use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 7 | ETHUD | alcohol use disorder information sensitivity | \n Policy for handling information related to alcohol use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 7 | OPIOIDUD | opioid use disorder information sensitivity | \n Policy for handling information related to opioid use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 5 | STD | sexually transmitted disease information sensitivity | \n Policy for handling sexually transmitted disease information, which will be afforded heightened confidentiality.\n Information handling protocols based on organizational policies related to sexually transmitted disease information that is deemed sensitive. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | TBOO | taboo | \n Policy for handling information not to be initially disclosed or discussed with patient except by a physician assigned to patient in this case. Information handling protocols based on organizational policies related to sensitive patient information that must be initially discussed with the patient by an attending physician before being disclosed to the patient. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n \n Open Issue: This definition conflates a rule and a characteristic, and there may be a similar issue with ts sibling codes. \r\n\n |
| 5 | VIO | violence information sensitivity | \n Policy for handling information related to harm by violence, which is afforded heightened confidentiality. Harm by violence is perpetrated by an unrelated person. \r\n\n Access control concerns for information about mental or physical harm resulting from violence caused by an unrelated person may include manipulation of care givers or access to records that enable the perpetrator contact or locate the patient, but the perpetrator will likely not have established abusive psychological control over the patient. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n |
| 5 | SICKLE | sickle cell | \n Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." \r\n\n \n Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. \r\n\n |
| 4 | (_EntitySensitivityPolicyType) Abstract | \n Types of sensitivity policies that may apply to a sensitive attribute on an Entity. \r\n\n \n Usage Note: EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute. May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." \r\n\n | |
| 5 | DEMO | all demographic information sensitivity | \n Policy for handling all demographic information about an information subject, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to all demographic about an information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | DOB | date of birth information sensitivity | \n Policy for handling information related to an information subject's date of birth, which will be afforded heightened confidentiality.Policies may govern sensitivity of information related to an information subject's date of birth, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | GENDER | gender and sexual orientation information sensitivity | \n Policy for handling information related to an information subject's gender and sexual orientation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's gender and sexual orientation, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | LIVARG | living arrangement information sensitivity | \n Policy for handling information related to an information subject's living arrangement, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's living arrangement, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | MARST | marital status information sensitivity | \n Policy for handling information related to an information subject's marital status, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's marital status, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | RACE | race information sensitivity | \n Policy for handling information related to an information subject's race, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's race, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | REL | religion information sensitivity | \n Policy for handling information related to an information subject's religious affiliation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's religion, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | (_RoleInformationSensitivityPolicy) Abstract | \n Types of sensitivity policies that apply to Roles. \r\n\n \n Usage Notes: RoleSensitivity codes are used to bind information to a Role.confidentialityCode per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." \r\n\n | |
| 5 | B | business information sensitivity | \n Policy for handling trade secrets such as financial information or intellectual property, which will be afforded heightened confidentiality. Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. \r\n\n \n Usage Notes: No patient related information may ever be of this confidentiality level. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | EMPL | employer information sensitivity | \n Policy for handling information related to an employer which is deemed classified to protect an employee who is the information subject, and which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to an employer, such as law enforcement or national security, the identity of which could impact the privacy, well-being, or safety of an information subject who is an employee. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | LOCIS | location information sensitivity | \n Policy for handling information related to the location of the information subject, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to the location of the information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 5 | SSP | sensitive service provider information sensitivity | \n Policy for handling information related to a provider of sensitive services, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to providers who deliver sensitive healthcare services in order to protect the privacy, well-being, and safety of the provider and of patients receiving sensitive services. \r\n\n \n Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | ADOL | adolescent information sensitivity | \n Policy for handling information related to an adolescent, which will be afforded heightened confidentiality per applicable organizational or jurisdictional policy. An enterprise may have a policy that requires that adolescent patient information be provided heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n \n Usage Note: For use within an enterprise in which an adolescent is the information subject. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | CEL | celebrity information sensitivity | \n Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality. Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n \n Usage Note: For use within an enterprise in which the information subject is deemed a celebrity or very important person. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | DIA | diagnosis information sensitivity | \n Policy for handling information related to a diagnosis, health condition or health problem, which will be afforded heightened confidentiality. Diagnostic, health condition or health problem related information may be deemed sensitive by organizational policy, and require heightened confidentiality. \r\n\n \n Usage Note: For use within an enterprise that provides heightened confidentiality to diagnostic, health condition or health problem related information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | DRGIS | drug information sensitivity | \n Policy for handling information related to a drug, which will be afforded heightened confidentiality. Drug information may be deemed sensitive by organizational policy, and require heightened confidentiality. \r\n\n \n Usage Note: For use within an enterprise that provides heightened confidentiality to drug information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 4 | EMP | employee information sensitivity | \n Policy for handling information related to an employee, which will be afforded heightened confidentiality. When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n \n Usage Note: Policy for handling information related to an employee, which will be afforded heightened confidentiality. Description: When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. \r\n\n |
| 4 | PDS | patient default information sensitivity | \n Policy for specially protecting information reported by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive for another reason.) For example information reported by the patient about another person, e.g., a family member, may be deemed sensitive by default. Organizational policy may allow the sensitivity tag to be cleared on patient's request. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. \r\n\n For example, VA deems employee information sensitive by default. Information about a patient who is being stalked or a victim of abuse or violence may be deemed sensitive by default per a provider organization's policies. \r\n\n |
| 4 | PHY | physician requested information sensitivity | \n Policy for handling information about a patient, which a physician or other licensed healthcare provider deems sensitive. Once tagged by the provider, this may trigger alerts for follow up actions according to organizational policy or jurisdictional law. \r\n\n \n Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a physician as sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n Use cases in which this code could be used are, e.g., in systems that lack the ability to automatically detect sensitive information and must rely on manual tagging; a system that lacks an applicable sensitivity tag, or for ad hoc situations where criticality of the situation requires that the tagging be done immediately by the provider before coding or transcription of consult notes can be completed, e.g., upon detection of a patient with suicidal tendencies or potential for violence. \r\n\n |
| 4 | PRS | patient requested information sensitivity | \n Policy for specially protecting information reported by or about a patient, which the patient deems sensitive, and the patient requests that collection, access, use, or disclosure of that information be restricted. For example, a minor patient may request that information about reproductive health not be disclosed to the patient's family or to particular providers and payers. \r\n\n \n Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. \r\n\n |
| 3 | COMPT | compartment | \n This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. \r\n\n Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk." \r\n\n |
| 4 | ACOCOMPT | accountable care organization compartment | \n A group of health care entities, which may include health care providers, care givers, hospitals, facilities, health plans, and other health care constituents who coordinate care for reimbursement based on quality metrics for improving outcomes and lowering costs, and may be authorized to access the consumer's health information because of membership in that group. \r\n\n Security Compartment Labels assigned to a consumer's information use in accountable care workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a an accountable care workflow who is requesting access to that information \r\n\n |
| 4 | CTCOMPT | care team compartment | \n Care coordination across participants in a care plan requires sharing of a healthcare consumer's information specific to that workflow. A care team member should only have access to that information while participating in that workflow or for other authorized uses. \r\n\n Security Compartment Labels assigned to a consumer's information use in care coordination workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a care team member workflow who is requesting access to that information \r\n\n |
| 4 | FMCOMPT | financial management compartment | \n Financial management department members who have access to healthcare consumer information as part of a patient account, billing and claims workflows. \r\n\n Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a financial management workflow who is requesting access to that information. \r\n\n |
| 4 | HRCOMPT | human resource compartment | \n A security category label field value, which indicates that access and use of an IT resource is restricted to members of human resources department or workflow. \r\n\n |
| 4 | LRCOMPT | legitimate relationship compartment | \n Providers and care givers who have an established relationship per criteria determined by policy are considered to have an established care provision relations with a healthcare consumer, and may be authorized to access the consumer's health information because of that relationship. Providers and care givers should only have access to that information while participating in legitimate relationship workflows or for other authorized uses. \r\n\n Security Compartment Labels assigned to a consumer's information use in legitimate relationship workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a legitimate relationship workflow who is requesting access to that information. \r\n\n |
| 4 | PACOMPT | patient administration compartment | \n Patient administration members who have access to healthcare consumer information as part of a patient administration workflows. \r\n\n Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a patient administration workflow who is requesting access to that information. \r\n\n |
| 4 | RESCOMPT | research project compartment | \n A security category label field value, which indicates that access and use of an IT resource is restricted to members of a research project. \r\n\n |
| 4 | RMGTCOMPT | records management compartment | \n A security category label field value, which indicates that access and use of an IT resource is restricted to members of records management department or workflow. \r\n\n |
| 2 | (ActTrustPolicyType) Abstract | \n A mandate, obligation, requirement, rule, or expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions. \r\n\n Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). \r\n\n Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain's trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. [Based on ISO IEC 10181-1 and NIST SP 800-63-2] \r\n\n For example, identity proofing , level of assurance, and Trust Framework. \r\n\n | |
| 3 | TRSTACCRD | trust accreditation | \n Type of security metadata about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. \r\n\n |
| 3 | TRSTAGRE | trust agreement | \n Type of security metadata about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] \r\n\n |
| 3 | TRSTASSUR | trust assurance | \n Type of security metadata about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. \r\n\n |
| 3 | TRSTCERT | trust certificate | \n Type of security metadata about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] \r\n\n |
| 3 | TRSTFWK | trust framework | \n Type of security metadata about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative] \r\n\n |
| 3 | TRSTMEC | trust mechanism | \n Type of security metadata about a security architecture system component that supports enforcement of security policies. \r\n\n |
| 2 | COVPOL | benefit policy | \n \n Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed on benefit coverage under a policy or program by a sponsor, underwriter or payor on: \r\n\n \n \n The activity of another party \r\n\n \n \n The behavior of another party \r\n\n \n \n The manner in which an act is executed \r\n\n \n \n \n Examples:A clinical protocol imposed by a payer to which a provider must adhere in order to be paid for providing the service. A formulary from which a provider must select prescribed drugs in order for the patient to incur a lower copay. \r\n\n |
| 2 | SecurityPolicy | security policy | \n Types of security policies that further specify the ActClassPolicy value set. \r\n\n \n Examples:\n \r\n\n \n obligation to encrypt\n refrain from redisclosure without consent\n \n |
| 3 | AUTHPOL | authorization policy | \n Authorisation policies are essentially security policies related to access-control and specify what activities a subject is permitted or forbidden to do, to a set of target objects. They are designed to protect target objects so are interpreted by access control agents or the run-time systems at the target system. \r\n\n A positive authorisation policy defines the actions that a subject is permitted to perform on a target. A negative authorisation policy specifies the actions that a subject is forbidden to perform on a target. Positive authorisation policies may also include filters to transform the parameters associated with their actions. (Based on PONDERS) \r\n\n |
| 4 | ACCESSCONSCHEME | access control scheme | \n An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies. \r\n\n \n Usage Note: Access control schemes are the type of access control policy, which is comprised of access control policy rules concerning the provision of the access control service. \r\n\n There are two categories of access control policies, rule-based and identity-based, which are identified in CCITT Rec. X.800 aka ISO 7498-2. Rule-based access control policies are intended to apply to all access requests by any initiator on any target in a security domain. Identity-based access control policies are based on rules specific to an individual initiator, a group of initiators, entities acting on behalf of initiators, or originators acting in a specific role. Context can modify rule-based or identity-based access control policies. Context rules may define the entire policy in effect. Real systems will usually employ a combination of these policy types; if a rule-based policy is used, then an identity-based policy is usually in effect also. \r\n\n An access control scheme may be based on access control lists, capabilities, labels, and context or a combination of these. An access control scheme is a component of an access control mechanism or "service") along with the supporting mechanisms required by that scheme to provide access control decision information (ADI) supplied by the scheme to the access decision facility (ADF also known as a PDP). (Based on ISO/IEC 10181-3:1996) \r\n\n \n Examples: \n \r\n\n \n Attribute Based Access Control (ABAC)\n Discretionary Access Control (DAC)\n History Based Access Control (HBAC)\n Identity Based Access Control (IBAC)\n Mandatory Access Control (MAC)\n Organization Based Access Control (OrBAC)\n Relationship Based Access Control (RelBac)\n Responsibility Based Access Control (RespBAC)\n Risk Adaptable Access Control (RAdAC)\n > |
| 3 | DELEPOL | delegation policy | \n Delegation policies specify which actions subjects are allowed to delegate to others. A delegation policy thus specifies an authorisation to delegate. Subjects must already possess the access rights to be delegated. \r\n\n Delegation policies are aimed at subjects delegating rights to servers or third parties to perform actions on their behalf and are not meant to be the means by which security administrators would assign rights to subjects. A negative delegation policy identifies what delegations are forbidden. \r\n\n A Delegation policy specifies the authorisation policy from which delegated rights are derived, the grantors, which are the entities which can delegate these access rights, and the grantees, which are the entities to which the access rights can be delegated. There are two types of delegation policy, positive and negative. (Based on PONDERS) \r\n\n |
| 3 | ObligationPolicy | obligation policy | \n Conveys the mandated workflow action that an information custodian, receiver, or user must perform. \r\n\n \n Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision. \r\n\n |
| 4 | ANONY | anonymize | \n Custodian system must remove any information that could result in identifying the information subject. \r\n\n |
| 4 | AOD | accounting of disclosure | \n Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested. \r\n\n |
| 4 | AUDIT | audit | \n Custodian system must monitor systems to ensure that all users are authorized to operate on information objects. \r\n\n |
| 4 | AUDTR | audit trail | \n Custodian system must monitor and maintain retrievable log for each user and operation on information. \r\n\n |
| 4 | CPLYCC | comply with confidentiality code | \n Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target. \r\n\n |
| 4 | CPLYCD | comply with consent directive | \n Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives. \r\n\n |
| 4 | CPLYJPP | comply with jurisdictional privacy policy | \n Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information. \r\n\n |
| 4 | CPLYOPP | comply with organizational privacy policy | \n Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information. \r\n\n |
| 4 | CPLYOSP | comply with organizational security policy | \n Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information. \r\n\n |
| 4 | CPLYPOL | comply with policy | \n Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information. \r\n\n |
| 4 | DECLASSIFYLABEL | declassify security label | \n Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 4 | DEID | deidentify | \n Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. \r\n\n |
| 4 | DELAU | delete after use | \n Custodian system must remove target information from access after use. \r\n\n |
| 4 | DOWNGRDLABEL | downgrade security label | \n Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 4 | DRIVLABEL | derive security label | \n Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 4 | ENCRYPT | encrypt | \n Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. \r\n\n \r\n\n \n Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.) \r\n\n |
| 5 | ENCRYPTR | encrypt at rest | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage. \r\n\n |
| 5 | ENCRYPTT | encrypt in transit | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means. \r\n\n |
| 5 | ENCRYPTU | encrypt in use | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user. \r\n\n |
| 4 | HUAPRV | human approval | \n Custodian system must require human review and approval for permission requested. \r\n\n |
| 4 | LABEL | assign security label | \n Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. \r\n\n \n Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes. \r\n\n |
| 4 | MASK | mask | \n Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret". \r\n\n |
| 4 | MINEC | minimum necessary | \n Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. \r\n\n \n Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use. \r\n\n |
| 4 | PERSISTLABEL | persist security label | \n Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. \r\n\n |
| 4 | PRIVMARK | privacy mark | \n Custodian must create and/or maintain human readable security label tags as required by policy. \r\n\n Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label." \r\n\n |
| 4 | PSEUD | pseudonymize | \n Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject. \r\n\n |
| 4 | REDACT | redact | \n Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users. \r\n\n |
| 4 | UPGRDLABEL | upgrade security label | \n Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. \r\n\n |
| 3 | RefrainPolicy | refrain policy | \n Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. \r\n\n \r\n\n \n Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc. \r\n\n |
| 4 | NOAUTH | no disclosure without subject authorization | \n Prohibition on disclosure without information subject's authorization. \r\n\n |
| 4 | NOCOLLECT | no collection | \n Prohibition on collection or storage of the information. \r\n\n |
| 4 | NODSCLCD | no disclosure without consent directive | \n Prohibition on disclosure without organizational approved patient restriction. \r\n\n |
| 4 | NODSCLCDS | no disclosure without information subject's consent directive | \n Prohibition on disclosure without a consent directive from the information subject. \r\n\n |
| 4 | NOINTEGRATE | no integration | \n Prohibition on Integration into other records. \r\n\n |
| 4 | NOLIST | no unlisted entity disclosure | \n Prohibition on disclosure except to entities on specific access list. \r\n\n |
| 4 | NOMOU | no disclosure without MOU | \n Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU). \r\n\n |
| 4 | NOORGPOL | no disclosure without organizational authorization | \n Prohibition on disclosure without organizational authorization. \r\n\n |
| 4 | NOPAT | no disclosure to patient, family or caregivers without attending provider's authorization | \n Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. \r\n\n \n Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. \r\n\n Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. \r\n\n FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. \r\n\n \n displayName: Document non visible par le patient\n codingScheme: 1.2.250.1.213.1.1.4.13\n \n French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone). \r\n\n |
| 4 | NOPERSISTP | no collection beyond purpose of use | \n Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited. \r\n\n |
| 4 | NORDSCLCD | no redisclosure without consent directive | \n Prohibition on redisclosure without patient consent directive. \r\n\n |
| 4 | NORDSCLCDS | no redisclosure without information subject's consent directive | \n Prohibition on redisclosure without a consent directive from the information subject. \r\n\n |
| 4 | NORDSCLW | no disclosure without jurisdictional authorization | \n Prohibition on disclosure without authorization under jurisdictional law. \r\n\n |
| 4 | NORELINK | no relinking | \n Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked. \r\n\n |
| 4 | NOREUSE | no reuse beyond purpose of use | \n Prohibition on use of the information beyond the purpose of use initially authorized. \r\n\n |
| 4 | NOVIP | no unauthorized VIP disclosure | \n Prohibition on disclosure except to principals with access permission to specific VIP information. \r\n\n |
| 4 | ORCON | no disclosure without originator authorization | \n Prohibition on disclosure except as permitted by the information originator. \r\n\n |
| 1 | (_ActProductAcquisitionCode) Abstract | \n The method that a product is obtained for use by the subject of the supply act (e.g. patient). Product examples are consumable or durable goods. \r\n\n | |
| 2 | LOAN | Loan | \n Temporary supply of a product without transfer of ownership for the product. \r\n\n |
| 3 | RENT | Rent | \n Temporary supply of a product with financial compensation, without transfer of ownership for the product. \r\n\n |
| 2 | TRANSFER | Transfer | \n Transfer of ownership for a product. \r\n\n |
| 3 | SALE | Sale | \n Transfer of ownership for a product for financial compensation. \r\n\n |
| 1 | (_ActSpecimenTransportCode) Abstract | \n Transportation of a specimen. \r\n\n | |
| 2 | SREC | specimen received | \n \n Description:Specimen has been received by the participating organization/department. \r\n\n |
| 2 | SSTOR | specimen in storage | \n \n Description:Specimen has been placed into storage at a participating location. \r\n\n |
| 2 | STRAN | specimen in transit | \n \n Description:Specimen has been put in transit to a participating receiver. \r\n\n |
| 1 | (_ActSpecimenTreatmentCode) Abstract | \n Set of codes related to specimen treatments \r\n\n | |
| 2 | ACID | Acidification | \n The lowering of specimen pH through the addition of an acid \r\n\n |
| 2 | ALK | Alkalization | \n The act rendering alkaline by impregnating with an alkali; a conferring of alkaline qualities. \r\n\n |
| 2 | DEFB | Defibrination | \n The removal of fibrin from whole blood or plasma through physical or chemical means \r\n\n |
| 2 | FILT | Filtration | \n The passage of a liquid through a filter, accomplished by gravity, pressure or vacuum (suction). \r\n\n |
| 2 | LDLP | LDL Precipitation | |
| 2 | NEUT | Neutralization | \n The act or process by which an acid and a base are combined in such proportions that the resulting compound is neutral. \r\n\n |
| 2 | RECA | Recalcification | \n The addition of calcium back to a specimen after it was removed by chelating agents \r\n\n |
| 2 | UFIL | Ultrafiltration | \n The filtration of a colloidal substance through a semipermeable medium that allows only the passage of small molecules. \r\n\n |
| 1 | (_ActSubstanceAdministrationCode) Abstract | \n \n Description: Describes the type of substance administration being performed. This should not be used to carry codes for identification of products. Use an associated role or entity to carry such information. \r\n\n | |
| 2 | DRUG | Drug therapy | \n The introduction of a drug into a subject with the intention of altering its biologic state with the intent of improving its health status. \r\n\n |
| 2 | FD | food | \n \n Description: The introduction of material into a subject with the intent of providing nutrition or other dietary supplements (e.g. minerals or vitamins). \r\n\n |
| 2 | IMMUNIZ | Immunization | \n The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents. \r\n\n |
| 3 | BOOSTER | Booster Immunization | \n An additional immunization administration within a series intended to bolster or enhance immunity. \r\n\n |
| 3 | INITIMMUNIZ | Initial Immunization | \n The first immunization administration in a series intended to produce immunity \r\n\n |
| 1 | (_ActTaskCode) Abstract | \n \n Description: A task or action that a user may perform in a clinical information system (e.g., medication order entry, laboratory test results review, problem list entry). \r\n\n | |
| 2 | OE | order entry task | \n A clinician creates a request for a service to be performed for a given patient. \r\n\n |
| 3 | LABOE | laboratory test order entry task | \n A clinician creates a request for a laboratory test to be done for a given patient. \r\n\n |
| 3 | MEDOE | medication order entry task | \n A clinician creates a request for the administration of one or more medications to a given patient. \r\n\n |
| 2 | PATDOC | patient documentation task | \n A person enters documentation about a given patient. \r\n\n |
| 3 | ALLERLREV | allergy list review | \n \n Description: A person reviews a list of known allergies of a given patient. \r\n\n |
| 3 | CLINNOTEE | clinical note entry task | \n A clinician enters a clinical note about a given patient \r\n\n |
| 4 | DIAGLISTE | diagnosis list entry task | \n A clinician enters a diagnosis for a given patient. \r\n\n |
| 4 | DISCHINSTE | discharge instruction entry | \n A person provides a discharge instruction to a patient. \r\n\n |
| 4 | DISCHSUME | discharge summary entry task | \n A clinician enters a discharge summary for a given patient. \r\n\n |
| 4 | PATEDUE | patient education entry | \n A person provides a patient-specific education handout to a patient. \r\n\n |
| 4 | PATREPE | pathology report entry task | \n A pathologist enters a report for a given patient. \r\n\n |
| 4 | PROBLISTE | problem list entry task | \n A clinician enters a problem for a given patient. \r\n\n |
| 4 | RADREPE | radiology report entry task | \n A radiologist enters a report for a given patient. \r\n\n |
| 3 | IMMLREV | immunization list review | \n \n Description: A person reviews a list of immunizations due or received for a given patient. \r\n\n |
| 3 | REMLREV | reminder list review | \n \n Description: A person reviews a list of health care reminders for a given patient. \r\n\n |
| 4 | WELLREMLREV | wellness reminder list review | \n \n Description: A person reviews a list of wellness or preventive care reminders for a given patient. \r\n\n |
| 2 | PATINFO | patient information review task | \n A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record. \r\n\n |
| 3 | ALLERLE | allergy list entry | \n \n Description: A person enters a known allergy for a given patient. \r\n\n |
| 3 | CDSREV | clinical decision support intervention review | \n A person reviews a recommendation/assessment provided automatically by a clinical decision support application for a given patient. \r\n\n |
| 3 | CLINNOTEREV | clinical note review task | \n A person reviews a clinical note of a given patient. \r\n\n |
| 4 | DISCHSUMREV | discharge summary review task | \n A person reviews a discharge summary of a given patient. \r\n\n |
| 3 | DIAGLISTREV | diagnosis list review task | \n A person reviews a list of diagnoses of a given patient. \r\n\n |
| 3 | IMMLE | immunization list entry | \n \n Description: A person enters an immunization due or received for a given patient. \r\n\n |
| 3 | LABRREV | laboratory results review task | \n A person reviews a list of laboratory results of a given patient. \r\n\n |
| 3 | MICRORREV | microbiology results review task | \n A person reviews a list of microbiology results of a given patient. \r\n\n |
| 4 | MICROORGRREV | microbiology organisms results review task | \n A person reviews organisms of microbiology results of a given patient. \r\n\n |
| 4 | MICROSENSRREV | microbiology sensitivity test results review task | \n A person reviews the sensitivity test of microbiology results of a given patient. \r\n\n |
| 3 | MLREV | medication list review task | \n A person reviews a list of medication orders submitted to a given patient \r\n\n |
| 4 | MARWLREV | medication administration record work list review task | \n A clinician reviews a work list of medications to be administered to a given patient. \r\n\n |
| 3 | OREV | orders review task | \n A person reviews a list of orders submitted to a given patient. \r\n\n |
| 3 | PATREPREV | pathology report review task | \n A person reviews a pathology report of a given patient. \r\n\n |
| 3 | PROBLISTREV | problem list review task | \n A person reviews a list of problems of a given patient. \r\n\n |
| 3 | RADREPREV | radiology report review task | \n A person reviews a radiology report of a given patient. \r\n\n |
| 3 | REMLE | reminder list entry | \n \n Description: A person enters a health care reminder for a given patient. \r\n\n |
| 4 | WELLREMLE | wellness reminder list entry | \n \n Description: A person enters a wellness or preventive care reminder for a given patient. \r\n\n |
| 3 | RISKASSESS | risk assessment instrument task | \n A person reviews a Risk Assessment Instrument report of a given patient. \r\n\n |
| 4 | FALLRISK | falls risk assessment instrument task | \n A person reviews a Falls Risk Assessment Instrument report of a given patient. \r\n\n |
| 1 | (_ActTransportationModeCode) Abstract | \n Characterizes how a transportation act was or will be carried out. \r\n\n \n Examples: Via private transport, via public transit, via courier. \r\n\n | |
| 2 | (_ActPatientTransportationModeCode) Abstract | \n Definition: Characterizes how a patient was or will be transported to the site of a patient encounter. \r\n\n \n Examples: Via ambulance, via public transit, on foot. \r\n\n | |
| 3 | AFOOT | pedestrian transport | |
| 3 | AMBT | ambulance transport | |
| 4 | AMBAIR | fixed-wing ambulance transport | |
| 4 | AMBGRND | ground ambulance transport | |
| 4 | AMBHELO | helicopter ambulance transport | |
| 3 | LAWENF | law enforcement transport | |
| 3 | PRVTRN | private transport | |
| 3 | PUBTRN | public transport | |
| 1 | (_ObservationType) Abstract | \n Identifies the kinds of observations that can be performed \r\n\n | |
| 2 | (_ActSpecObsCode) Abstract | \n Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation \r\n\n | |
| 3 | ARTBLD | ActSpecObsArtBldCode | \n Describes the artificial blood identifier that is associated with the specimen. \r\n\n |
| 3 | DILUTION | ActSpecObsDilutionCode | \n An observation that reports the dilution of a sample. \r\n\n |
| 4 | AUTO-HIGH | Auto-High Dilution | \n The dilution of a sample performed by automated equipment. The value is specified by the equipment \r\n\n |
| 4 | AUTO-LOW | Auto-Low Dilution | \n The dilution of a sample performed by automated equipment. The value is specified by the equipment \r\n\n |
| 4 | PRE | Pre-Dilution | \n The dilution of the specimen made prior to being loaded onto analytical equipment \r\n\n |
| 4 | RERUN | Rerun Dilution | \n The value of the dilution of a sample after it had been analyzed at a prior dilution value \r\n\n |
| 3 | EVNFCTS | ActSpecObsEvntfctsCode | \n Domain provides codes that qualify the ActLabObsEnvfctsCode domain. (Environmental Factors) \r\n\n |
| 3 | INTFR | ActSpecObsInterferenceCode | \n An observation that relates to factors that may potentially cause interference with the observation \r\n\n |
| 4 | FIBRIN | Fibrin | \n The Fibrin Index of the specimen. In the case of only differentiating between Absent and Present, recommend using 0 and 1 \r\n\n |
| 4 | HEMOLYSIS | Hemolysis | \n An observation of the hemolysis index of the specimen in g/L \r\n\n |
| 4 | ICTERUS | Icterus | \n An observation that describes the icterus index of the specimen. It is recommended to use mMol/L of bilirubin \r\n\n |
| 4 | LIPEMIA | Lipemia | \n An observation used to describe the Lipemia Index of the specimen. It is recommended to use the optical turbidity at 600 nm (in absorbance units). \r\n\n |
| 3 | VOLUME | ActSpecObsVolumeCode | \n An observation that reports the volume of a sample. \r\n\n |
| 4 | AVAILABLE | Available Volume | \n The available quantity of specimen. This is the current quantity minus any planned consumption (e.g., tests that are planned) \r\n\n |
| 4 | CONSUMPTION | Consumption Volume | \n The quantity of specimen that is used each time the equipment uses this substance \r\n\n |
| 4 | CURRENT | Current Volume | \n The current quantity of the specimen, i.e., initial quantity minus what has been actually used. \r\n\n |
| 4 | INITIAL | Initial Volume | \n The initial quantity of the specimen in inventory \r\n\n |
| 2 | (_AnnotationType) Abstract | ||
| 3 | _ActPatientAnnotationType | ActPatientAnnotationType | \n \n Description:Provides a categorization for annotations recorded directly against the patient . \r\n\n |
| 4 | ANNDI | diagnostic image note | \n \n Description:A note that is specific to a patient's diagnostic images, either historical, current or planned. \r\n\n |
| 4 | ANNGEN | general note | \n \n Description:A general or uncategorized note. \r\n\n |
| 4 | ANNIMM | immunization note | A note that is specific to a patient's immunizations, either historical, current or planned. |
| 4 | ANNLAB | laboratory note | \n \n Description:A note that is specific to a patient's laboratory results, either historical, current or planned. \r\n\n |
| 4 | ANNMED | medication note | \n \n Description:A note that is specific to a patient's medications, either historical, current or planned. \r\n\n |
| 2 | (_GeneticObservationType) Abstract | \n \n Description: None provided \r\n\n | |
| 3 | GENE | gene | \n \n Description: A DNA segment that contributes to phenotype/function. In the absence of demonstrated function a gene may be characterized by sequence, transcription or homology \r\n\n |
| 2 | _ImmunizationObservationType | ImmunizationObservationType | \n \n Description: Observation codes which describe characteristics of the immunization material. \r\n\n |
| 3 | OBSANTC | antigen count | \n \n Description: Indicates the valid antigen count. \r\n\n |
| 3 | OBSANTV | antigen validity | \n \n Description: Indicates whether an antigen is valid or invalid. \r\n\n |
| 2 | (_IndividualCaseSafetyReportType) Abstract | \n A code that is used to indicate the type of case safety report received from sender. The current code example reference is from the International Conference on Harmonisation (ICH) Expert Workgroup guideline on Clinical Safety Data Management: Data Elements for Transmission of Individual Case Safety Reports. The unknown/unavailable option allows the transmission of information from a secondary sender where the initial sender did not specify the type of report. \r\n\n Example concepts include: Spontaneous, Report from study, Other. \r\n\n | |
| 3 | PAT_ADV_EVNT | patient adverse event | Indicates that the ICSR is describing problems that a patient experienced after receiving a vaccine product. |
| 3 | VAC_PROBLEM | vaccine product problem | Indicates that the ICSR is describing a problem with the actual vaccine product such as physical defects (cloudy, particulate matter) or inability to confer immunity. |
| 2 | (_LOINCObservationActContextAgeType) Abstract | \n \n Definition:The set of LOINC codes for the act of determining the period of time that has elapsed since an entity was born or created. \r\n\n | |
| 3 | 21611-9 | age patient qn est | \n \n Definition:Estimated age. \r\n\n |
| 3 | 21612-7 | age patient qn reported | \n \n Definition:Reported age. \r\n\n |
| 3 | 29553-5 | age patient qn calc | \n \n Definition:Calculated age. \r\n\n |
| 3 | 30525-0 | age patient qn definition | \n \n Definition:General specification of age with no implied method of determination. \r\n\n |
| 3 | 30972-4 | age at onset of adverse event | \n \n Definition:Age at onset of associated adverse event; no implied method of determination. \r\n\n |
| 2 | (_MedicationObservationType) Abstract | ||
| 3 | REP_HALF_LIFE | representative half-life | \n \n Description:This observation represents an 'average' or 'expected' half-life typical of the product. \r\n\n |
| 3 | SPLCOATING | coating | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, indicating whether it has one or more coatings such as sugar coating, film coating, or enteric coating. Only coatings to the external surface or the dosage form should be considered (for example, coatings to individual pellets or granules inside a capsule or tablet are excluded from consideration). \r\n\n \n Constraints: The Observation.value must be a Boolean (BL) with true for the presence or false for the absence of one or more coatings on a solid dosage form. \r\n\n |
| 3 | SPLCOLOR | color | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the color or colors that most predominantly define the appearance of the dose form. SPLCOLOR is not an FDA specification for the actual color of solid dosage forms or the names of colors that can appear in labeling. \r\n\n \n Constraints: The Observation.value must be a single coded value or a list of multiple coded values, specifying one or more distinct colors that approximate of the color(s) of distinct areas of the solid dosage form, such as the different sides of a tablet or one-part capsule, or the different halves of a two-part capsule. Bands on banded capsules, regardless of the color, are not considered when assigning an SPLCOLOR. Imprints on the dosage form, regardless of their color are not considered when assigning an SPLCOLOR. If more than one color exists on a particular side or half, then the most predominant color on that side or half is recorded. If the gelatin capsule shell is colorless and transparent, use the predominant color of the contents that appears through the colorless and transparent capsule shell. Colors can include: Black;Gray;White;Red;Pink;Purple;Green;Yellow;Orange;Brown;Blue;Turquoise. \r\n\n |
| 3 | SPLIMAGE | image | \n \n Description: A characteristic representing a single file reference that contains two or more views of the same dosage form of the product; in most cases this should represent front and back views of the dosage form, but occasionally additional views might be needed in order to capture all of the important physical characteristics of the dosage form. Any imprint and/or symbol should be clearly identifiable, and the viewer should not normally need to rotate the image in order to read it. Images that are submitted with SPL should be included in the same directory as the SPL file. \r\n\n |
| 3 | SPLIMPRINT | imprint | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the alphanumeric text that appears on the solid dosage form, including text that is embossed, debossed, engraved or printed with ink. The presence of other non-textual distinguishing marks or symbols is recorded by SPLSYMBOL. \r\n\n \n Examples: Included in SPLIMPRINT are alphanumeric text that appears on the bands of banded capsules and logos and other symbols that can be interpreted as letters or numbers. \r\n\n \n Constraints: The Observation.value must be of type Character String (ST). Excluded from SPLIMPRINT are internal and external cut-outs in the form of alphanumeric text and the letter 'R' with a circle around it (when referring to a registered trademark) and the letters 'TM' (when referring to a 'trade mark'). To record text, begin on either side or part of the dosage form. Start at the top left and progress as one would normally read a book. Enter a semicolon to show separation between words or line divisions. \r\n\n |
| 3 | SPLSCORING | scoring | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the number of equal pieces that the solid dosage form can be divided into using score line(s). \r\n\n \n Example: One score line creating two equal pieces is given a value of 2, two parallel score lines creating three equal pieces is given a value of 3. \r\n\n \n Constraints: Whether three parallel score lines create four equal pieces or two intersecting score lines create two equal pieces using one score line and four equal pieces using both score lines, both have the scoring value of 4. Solid dosage forms that are not scored are given a value of 1. Solid dosage forms that can only be divided into unequal pieces are given a null-value with nullFlavor other (OTH). \r\n\n |
| 3 | SPLSHAPE | shape | \n \n Description: A characteristic of an oral solid dosage form of a medicinal product, specifying the two dimensional representation of the solid dose form, in terms of the outside perimeter of a solid dosage form when the dosage form, resting on a flat surface, is viewed from directly above, including slight rounding of corners. SPLSHAPE does not include embossing, scoring, debossing, or internal cut-outs. SPLSHAPE is independent of the orientation of the imprint and logo. Shapes can include: Triangle (3 sided); Square; Round; Semicircle; Pentagon (5 sided); Diamond; Double circle; Bullet; Hexagon (6 sided); Rectangle; Gear; Capsule; Heptagon (7 sided); Trapezoid; Oval; Clover; Octagon (8 sided); Tear; Freeform. \r\n\n |
| 3 | SPLSIZE | size | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the longest single dimension of the solid dosage form as a physical quantity in the dimension of length (e.g., 3 mm). The length is should be specified in millimeters and should be rounded to the nearest whole millimeter. \r\n\n \n Example: SPLSIZE for a rectangular shaped tablet is the length and SPLSIZE for a round shaped tablet is the diameter. \r\n\n |
| 3 | SPLSYMBOL | symbol | \n \n Definition: A characteristic of an oral solid dosage form of a medicinal product, to describe whether or not the medicinal product has a mark or symbol appearing on it for easy and definite recognition. Score lines, letters, numbers, and internal and external cut-outs are not considered marks or symbols. See SPLSCORING and SPLIMPRINT for these characteristics. \r\n\n \n Constraints: The Observation.value must be a Boolean (BL) with <u>true</u> indicating the presence and <u>false</u> for the absence of marks or symbols. \r\n\n \n Example: \n \r\n\n |
| 2 | (_ObservationIssueTriggerCodedObservationType) Abstract | \n Distinguishes the kinds of coded observations that could be the trigger for clinical issue detection. These are observations that are not measurable, but instead can be defined with codes. Coded observation types include: Allergy, Intolerance, Medical Condition, Pregnancy status, etc. \r\n\n | |
| 3 | (_CaseTransmissionMode) Abstract | \n Code for the mechanism by which disease was acquired by the living subject involved in the public health case. Includes sexually transmitted, airborne, bloodborne, vectorborne, foodborne, zoonotic, nosocomial, mechanical, dermal, congenital, environmental exposure, indeterminate. \r\n\n | |
| 4 | AIRTRNS | airborne transmission | \n Communication of an agent from a living subject or environmental source to a living subject through indirect contact via oral or nasal inhalation. \r\n\n |
| 4 | ANANTRNS | animal to animal transmission | \n Communication of an agent from one animal to another proximate animal. \r\n\n |
| 4 | ANHUMTRNS | animal to human transmission | \n Communication of an agent from an animal to a proximate person. \r\n\n |
| 4 | BDYFLDTRNS | body fluid contact transmission | \n Communication of an agent from one living subject to another living subject through direct contact with any body fluid. \r\n\n |
| 4 | BLDTRNS | blood borne transmission | \n Communication of an agent to a living subject through direct contact with blood or blood products whether the contact with blood is part of a therapeutic procedure or not. \r\n\n |
| 4 | DERMTRNS | transdermal transmission | \n Communication of an agent from a living subject or environmental source to a living subject via agent migration through intact skin. \r\n\n |
| 4 | ENVTRNS | environmental exposure transmission | \n Communication of an agent from an environmental surface or source to a living subject by direct contact. \r\n\n |
| 4 | FECTRNS | fecal-oral transmission | \n Communication of an agent from a living subject or environmental source to a living subject through oral contact with material contaminated by person or animal fecal material. \r\n\n |
| 4 | FOMTRNS | fomite transmission | \n Communication of an agent from an non-living material to a living subject through direct contact. \r\n\n |
| 4 | FOODTRNS | food-borne transmission | \n Communication of an agent from a food source to a living subject via oral consumption. \r\n\n |
| 4 | HUMHUMTRNS | human to human transmission | \n Communication of an agent from a person to a proximate person. \r\n\n |
| 4 | INDTRNS | indeterminate disease transmission mode | \n Communication of an agent to a living subject via an undetermined route. \r\n\n |
| 4 | LACTTRNS | lactation transmission | \n Communication of an agent from one living subject to another living subject through direct contact with mammalian milk or colostrum. \r\n\n |
| 4 | NOSTRNS | nosocomial transmission | \n Communication of an agent from any entity to a living subject while the living subject is in the patient role in a healthcare facility. \r\n\n |
| 4 | PARTRNS | parenteral transmission | \n Communication of an agent from a living subject or environmental source to a living subject where the acquisition of the agent is not via the alimentary canal. \r\n\n |
| 4 | PLACTRNS | transplacental transmission | \n Communication of an agent from a living subject to the progeny of that living subject via agent migration across the maternal-fetal placental membranes while in utero. \r\n\n |
| 4 | SEXTRNS | sexual transmission | \n Communication of an agent from one living subject to another living subject through direct contact with genital or oral tissues as part of a sexual act. \r\n\n |
| 4 | TRNSFTRNS | transfusion transmission | \n Communication of an agent from one living subject to another living subject through direct contact with blood or blood products where the contact with blood is part of a therapeutic procedure. \r\n\n |
| 4 | VECTRNS | vector-borne transmission | \n Communication of an agent from a living subject acting as a required intermediary in the agent transmission process to a recipient living subject via direct contact. \r\n\n |
| 4 | WATTRNS | water-borne transmission | \n Communication of an agent from a contaminated water source to a living subject whether the water is ingested as a food or not. The route of entry of the water may be through any bodily orifice. \r\n\n |
| 2 | _ObservationQualityMeasureAttribute | ObservationQualityMeasureAttribute | \n Codes used to define various metadata aspects of a health quality measure. \r\n\n |
| 3 | AGGREGATE | aggregate measure observation | \n Indicates that the observation is carrying out an aggregation calculation, contained in the value element. \r\n\n |
| 3 | CMPMSRMTH | composite measure method | \n Indicates what method is used in a quality measure to combine the component measure results included in an composite measure. \r\n\n |
| 3 | CMPMSRSCRWGHT | component measure scoring weight | \n An attribute of a quality measure describing the weight this component measure score is to carry in determining the overall composite measure final score. The value is real value greater than 0 and less than 1.0. Each component measure score will be multiplied by its CMPMSRSCRWGHT and then summed with the other component measures to determine the final overall composite measure score. The sum across all CMPMSRSCRWGHT values within a single composite measure SHALL be 1.0. The value assigned is scoped to the composite measure referencing this component measure only. \r\n\n |
| 3 | COPY | copyright | \n Identifies the organization(s) who own the intellectual property represented by the eMeasure. \r\n\n |
| 3 | CRS | clinical recommendation statement | \n Summary of relevant clinical guidelines or other clinical recommendations supporting this eMeasure. \r\n\n |
| 3 | DEF | definition | \n Description of individual terms, provided as needed. \r\n\n |
| 3 | DISC | disclaimer | \n Disclaimer information for the eMeasure. \r\n\n |
| 3 | FINALDT | finalized date/time | \n The timestamp when the eMeasure was last packaged in the Measure Authoring Tool. \r\n\n |
| 3 | GUIDE | guidance | \n Used to allow measure developers to provide additional guidance for implementers to understand greater specificity than could be provided in the logic for data criteria. \r\n\n |
| 3 | IDUR | improvement notation | \n Information on whether an increase or decrease in score is the preferred result \n(e.g., a higher score indicates better quality OR a lower score indicates better quality OR quality is within a range). \n \r\n\n |
| 3 | ITMCNT | items counted | \n Describes the items counted by the measure (e.g., patients, encounters, procedures, etc.) \r\n\n |
| 3 | KEY | keyword | \n A significant word that aids in discoverability. \r\n\n |
| 3 | MEDT | measurement end date | \n The end date of the measurement period. \r\n\n |
| 3 | MSD | measurement start date | \n The start date of the measurement period. \r\n\n |
| 3 | MSRADJ | risk adjustment | \n The method of adjusting for clinical severity and conditions present at the start of care that can influence patient outcomes for making valid comparisons of outcome measures across providers. Indicates whether an eMeasure is subject to the statistical process for reducing, removing, or clarifying the influences of confounding factors to allow more useful comparisons. \r\n\n |
| 3 | MSRAGG | rate aggregation | \n Describes how to combine information calculated based on logic in each of several populations into one summarized result. It can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure. (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). \r\n\n \n Open Issue: The description does NOT align well with the definition used in the HQMF specfication; correct the MSGAGG definition, and the possible distinction of MSRAGG as a child of AGGREGATE. \r\n\n |
| 3 | MSRIMPROV | health quality measure improvement notation | \n Information on whether an increase or decrease in score is the preferred result. This should reflect information on which way is better, an increase or decrease in score. \r\n\n |
| 3 | MSRJUR | jurisdiction | \n The list of jurisdiction(s) for which the measure applies. \r\n\n |
| 3 | MSRRPTR | reporter type | \n Type of person or organization that is expected to report the issue. \r\n\n |
| 3 | MSRRPTTIME | timeframe for reporting | \n The maximum time that may elapse following completion of the measure until the measure report must be sent to the receiver. \r\n\n |
| 3 | MSRSCORE | measure scoring | \n Indicates how the calculation is performed for the eMeasure \n(e.g., proportion, continuous variable, ratio) \r\n\n |
| 3 | MSRSET | health quality measure care setting | \n Location(s) in which care being measured is rendered \r\n\n Usage Note: MSRSET is used rather than RoleCode because the setting applies to what is being measured, as opposed to participating directly in the health quality measure documantion itself). \r\n\n |
| 3 | MSRTOPIC | health quality measure topic type | \n \r\n\n |
| 3 | MSRTP | measurement period | \n The time period for which the eMeasure applies. \r\n\n |
| 3 | MSRTYPE | measure type | \n Indicates whether the eMeasure is used to examine a process or an outcome over time \n(e.g., Structure, Process, Outcome). \r\n\n |
| 3 | RAT | rationale | \n Succinct statement of the need for the measure. Usually includes statements pertaining to Importance criterion: impact, gap in care and evidence. \r\n\n |
| 3 | REF | reference | \n Identifies bibliographic citations or references to clinical practice guidelines, sources of evidence, or other relevant materials supporting the intent and rationale of the eMeasure. \r\n\n |
| 3 | SDE | supplemental data elements | \n Comparison of results across strata can be used to show where disparities exist or where there is a need to expose differences in results. For example, Centers for Medicare & Medicaid Services (CMS) in the U.S. defines four required Supplemental Data Elements (payer, ethnicity, race, and gender), which are variables used to aggregate data into various subgroups. Additional supplemental data elements required for risk adjustment or other purposes of data aggregation can be included in the Supplemental Data Element section. \r\n\n |
| 3 | STRAT | stratification | \n Describes the strata for which the measure is to be evaluated. There are three examples of reasons for stratification based on existing work. These include: (1) evaluate the measure based on different age groupings within the population described in the measure (e.g., evaluate the whole [age 14-25] and each sub-stratum [14-19] and [20-25]); (2) evaluate the eMeasure based on either a specific condition, a specific discharge location, or both; (3) evaluate the eMeasure based on different locations within a facility (e.g., evaluate the overall rate for all intensive care units and also some strata include additional findings [specific birth weights for neonatal intensive care units]). \r\n\n |
| 3 | TRANF | transmission format | \n Can be a URL or hyperlinks that link to the transmission formats that are specified for a particular reporting program. \r\n\n |
| 3 | USE | notice of use | \n Usage notes. \r\n\n |
| 2 | (_ObservationSequenceType) Abstract | ||
| 3 | TIME_ABSOLUTE | absolute time sequence | \n A sequence of values in the "absolute" time domain. This is the same time domain that all HL7 timestamps use. It is time as measured by the Gregorian calendar \r\n\n |
| 3 | TIME_RELATIVE | relative time sequence | \n A sequence of values in a "relative" time domain. The time is measured relative to the earliest effective time in the Observation Series containing this sequence. \r\n\n |
| 2 | (_ObservationSeriesType) Abstract | ||
| 3 | (_ECGObservationSeriesType) Abstract | ||
| 4 | REPRESENTATIVE_BEAT | ECG representative beat waveforms | \n This Observation Series type contains waveforms of a "representative beat" (a.k.a. "median beat" or "average beat"). The waveform samples are measured in relative time, relative to the beginning of the beat as defined by the Observation Series effective time. The waveforms are not directly acquired from the subject, but rather algorithmically derived from the "rhythm" waveforms. \r\n\n |
| 4 | RHYTHM | ECG rhythm waveforms | \n This Observation type contains ECG "rhythm" waveforms. The waveform samples are measured in absolute time (a.k.a. "subject time" or "effective time"). These waveforms are usually "raw" with some minimal amount of noise reduction and baseline filtering applied. \r\n\n |
| 2 | _PatientImmunizationRelatedObservationType | PatientImmunizationRelatedObservationType | \n \n Description: Reporting codes that are related to an immunization event. \r\n\n |
| 3 | CLSSRM | classroom | \n \n Description: The class room associated with the patient during the immunization event. \r\n\n |
| 3 | GRADE | grade | \n \n Description: The school grade or level the patient was in when immunized. \r\n\n |
| 3 | SCHL | school | \n \n Description: The school the patient attended when immunized. \r\n\n |
| 3 | SCHLDIV | school division | \n \n Description: The school division or district associated with the patient during the immunization event. \r\n\n |
| 3 | TEACHER | teacher | \n \n Description: The patient's teacher when immunized. \r\n\n |
| 2 | (_PopulationInclusionObservationType) Abstract | \n Observation types for specifying criteria used to assert that a subject is included in a particular population. \r\n\n | |
| 3 | DENEX | denominator exclusions | \n Criteria which specify subjects who should be removed from the eMeasure population and denominator before determining if numerator criteria are met. Denominator exclusions are used in proportion and ratio measures to help narrow the denominator. \r\n\n |
| 3 | DENEXCEP | denominator exceptions | \n Criteria which specify the removal of a subject, procedure or unit of measurement from the denominator, only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories: \r\n\n \n Medical reasons\n Patient (or subject) reasons\n System reasons\n \n |
| 3 | DENOM | denominator | \n Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). The denominator can be the same as the initial population, or it may be a subset of the initial population to further constrain it for the purpose of the eMeasure. Different measures within an eMeasure set may have different denominators. Continuous Variable eMeasures do not have a denominator, but instead define a measure population. \r\n\n |
| 3 | IPOP | initial population | \n Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). \r\n\n |
| 4 | IPPOP | initial patient population | \n Criteria for specifying the patients to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). Details often include information based upon specific age groups, diagnoses, diagnostic and procedure codes, and enrollment periods. \r\n\n |
| 3 | MSROBS | measure observation | \n Defines the observation to be performed for each patient or event in the measure population. Measure observations for each case in the population are aggregated to determine the overall measure score for the population. \r\n\n \n Examples: \n \r\n\n \n the median time from arrival in the Emergency Room to departure\n the median time from decision to admit to a hospital to the actual admission for Emergency Room patients\n \n |
| 3 | MSRPOPL | measure population | \n Criteria for specifying\nthe measure population as a narrative description (e.g., all patients seen in the Emergency Department during the measurement period). This is used only in continuous variable eMeasures. \r\n\n |
| 3 | MSRPOPLEX | measure population exclusions | \n Criteria for specifying subjects who should be removed from the eMeasure's Initial Population and Measure Population. Measure Population Exclusions are used in Continuous Variable measures to help narrow the Measure Population before determining the value(s) of the continuous variable(s). \r\n\n |
| 3 | NUMER | numerator | \n Criteria for specifying the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator for proportion measures, or related to (but not directly derived from) the denominator for ratio measures (e.g., a numerator listing the number of central line blood stream infections and a denominator indicating the days per thousand of central line usage in a specific time period). \r\n\n |
| 3 | NUMEX | numerator exclusions | \n Criteria for specifying instances that should not be included in the numerator data. (e.g., if the number of central line blood stream infections per 1000 catheter days were to exclude infections with a specific bacterium, that bacterium would be listed as a numerator exclusion). Numerator Exclusions are used only in ratio eMeasures. \r\n\n |
| 2 | (_PreferenceObservationType) Abstract | \n Types of observations that can be made about Preferences. \r\n\n | |
| 3 | PREFSTRENGTH | preference strength | \n An observation about how important a preference is to the target of the preference. \r\n\n |
| 2 | ADVERSE_REACTION | Adverse Reaction | \n Indicates that the observation is of an unexpected negative occurrence in the subject suspected to result from the subject's exposure to one or more agents. Observation values would be the symptom resulting from the reaction. \r\n\n |
| 2 | ASSERTION | Assertion | \n \n Description:Refines classCode OBS to indicate an observation in which observation.value contains a finding or other nominalized statement, where the encoded information in Observation.value is not altered by Observation.code. For instance, observation.code="ASSERTION" and observation.value="fracture of femur present" is an assertion of a clinical finding of femur fracture. \r\n\n |
| 2 | CASESER | case seriousness criteria | \n \n Definition:An observation that provides a characterization of the level of harm to an investigation subject as a result of a reaction or event. \r\n\n |
| 2 | CDIO | case disease imported observation | \n An observation that states whether the disease was likely acquired outside the jurisdiction of observation, and if so, the nature of the inter-jurisdictional relationship. \r\n\n \n OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it. \r\n\n |
| 2 | CRIT | criticality | \n A clinical judgment as to the worst case result of a future exposure (including substance administration). When the worst case result is assessed to have a life-threatening or organ system threatening potential, it is considered to be of high criticality. \r\n\n |
| 2 | CTMO | case transmission mode observation | \n An observation that states the mechanism by which disease was acquired by the living subject involved in the public health case. \r\n\n \n OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it. \r\n\n |
| 2 | DX | ObservationDiagnosisTypes | \n Includes all codes defining types of indications such as diagnosis, symptom and other indications such as contrast agents for lab tests. \r\n\n |
| 3 | ADMDX | admitting diagnosis | \n Admitting diagnosis are the diagnoses documented for administrative purposes as the basis for a hospital admission. \r\n\n |
| 3 | DISDX | discharge diagnosis | \n Discharge diagnosis are the diagnoses documented for administrative purposes as the time of hospital discharge. \r\n\n |
| 3 | INTDX | intermediate diagnosis | \n Intermediate diagnoses are those diagnoses documented for administrative purposes during the course of a hospital stay. \r\n\n |
| 3 | NOI | nature of injury | \n The type of injury that the injury coding specifies. \r\n\n |
| 2 | GISTIER | GIS tier | \n \n Description: Accuracy determined as per the GIS tier code system. \r\n\n |
| 2 | HHOBS | household situation observation | \n Indicates that the observation is of a person s living situation in a household including the household composition and circumstances. \r\n\n |
| 2 | ISSUE | detected issue | \n There is a clinical issue for the therapy that makes continuation of the therapy inappropriate. \r\n\n \n Open Issue: The definition of this code does not correctly represent the concept space of its specializations (children) \r\n\n |
| 3 | (_ActAdministrativeDetectedIssueCode) Abstract | \n Identifies types of detectyed issues for Act class "ALRT" for the administrative and patient administrative acts domains. \r\n\n | |
| 4 | (_ActAdministrativeAuthorizationDetectedIssueCode) Abstract | ||
| 5 | NAT | Insufficient authorization | \n The requesting party has insufficient authorization to invoke the interaction. \r\n\n |
| 5 | SUPPRESSED | record suppressed | \n \n Description: One or more records in the query response have been suppressed due to consent or privacy restrictions. \r\n\n |
| 5 | VALIDAT | validation issue | \n \n Description:The specified element did not pass business-rule validation. \r\n\n |
| 6 | KEY204 | Unknown key identifier | \n The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient. \r\n\n |
| 6 | KEY205 | Duplicate key identifier | \n The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.). \r\n\n |
| 6 | COMPLY | Compliance Alert | \n There may be an issue with the patient complying with the intentions of the proposed therapy \r\n\n |
| 7 | DUPTHPY | Duplicate Therapy Alert | \n The proposed therapy appears to duplicate an existing therapy \r\n\n |
| 8 | DUPTHPCLS | duplicate therapeutic alass alert | \n \n Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy, though the specific mechanisms of action vary. \r\n\n |
| 8 | DUPTHPGEN | duplicate generic alert | \n \n Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy and uses the same mechanisms of action as the existing therapy. \r\n\n |
| 7 | ABUSE | commonly abused/misused alert | \n \n Description:The proposed therapy is frequently misused or abused and therefore should be used with caution and/or monitoring. \r\n\n |
| 7 | FRAUD | potential fraud | \n \n Description:The request is suspected to have a fraudulent basis. \r\n\n |
| 7 | PLYDOC | Poly-orderer Alert | \n A similar or identical therapy was recently ordered by a different practitioner. \r\n\n |
| 7 | PLYPHRM | Poly-supplier Alert | \n This patient was recently supplied a similar or identical therapy from a different pharmacy or supplier. \r\n\n |
| 6 | DOSE | Dosage problem | \n Proposed dosage instructions for therapy differ from standard practice. \r\n\n |
| 7 | DOSECOND | dosage-condition alert | \n \n Description:Proposed dosage is inappropriate due to patient's medical condition. \r\n\n |
| 7 | DOSEDUR | Dose-Duration Alert | \n Proposed length of therapy differs from standard practice. \r\n\n |
| 8 | DOSEDURH | Dose-Duration High Alert | \n Proposed length of therapy is longer than standard practice \r\n\n |
| 9 | DOSEDURHIND | Dose-Duration High for Indication Alert | \n Proposed length of therapy is longer than standard practice for the identified indication or diagnosis \r\n\n |
| 8 | DOSEDURL | Dose-Duration Low Alert | \n Proposed length of therapy is shorter than that necessary for therapeutic effect \r\n\n |
| 9 | DOSEDURLIND | Dose-Duration Low for Indication Alert | \n Proposed length of therapy is shorter than standard practice for the identified indication or diagnosis \r\n\n |
| 7 | DOSEH | High Dose Alert | \n Proposed dosage exceeds standard practice \r\n\n |
| 8 | DOSEHINDA | High Dose for Age Alert | \n Proposed dosage exceeds standard practice for the patient's age \r\n\n |
| 8 | DOSEHIND | High Dose for Indication Alert | |
| 8 | DOSEHINDSA | High Dose for Height/Surface Area Alert | \n Proposed dosage exceeds standard practice for the patient's height or body surface area \r\n\n |
| 8 | DOSEHINDW | High Dose for Weight Alert | \n Proposed dosage exceeds standard practice for the patient's weight \r\n\n |
| 7 | DOSEIVL | Dose-Interval Alert | \n Proposed dosage interval/timing differs from standard practice \r\n\n |
| 8 | DOSEIVLIND | Dose-Interval for Indication Alert | \n Proposed dosage interval/timing differs from standard practice for the identified indication or diagnosis \r\n\n |
| 7 | DOSEL | Low Dose Alert | \n Proposed dosage is below suggested therapeutic levels \r\n\n |
| 8 | DOSELINDA | Low Dose for Age Alert | \n Proposed dosage is below suggested therapeutic levels for the patient's age \r\n\n |
| 8 | DOSELIND | Low Dose for Indication Alert | |
| 8 | DOSELINDSA | Low Dose for Height/Surface Area Alert | \n Proposed dosage is below suggested therapeutic levels for the patient's height or body surface area \r\n\n |
| 8 | DOSELINDW | Low Dose for Weight Alert | \n Proposed dosage is below suggested therapeutic levels for the patient's weight \r\n\n |
| 7 | MDOSE | maximum dosage reached | \n \n Description:The maximum quantity of this drug allowed to be administered within a particular time-range (month, year, lifetime) has been reached or exceeded. \r\n\n |
| 6 | OBSA | Observation Alert | \n Proposed therapy may be inappropriate or contraindicated due to conditions or characteristics of the patient \r\n\n |
| 7 | AGE | Age Alert | \n Proposed therapy may be inappropriate or contraindicated due to patient age \r\n\n |
| 8 | ADALRT | adult alert | \n Proposed therapy is outside of the standard practice for an adult patient. \r\n\n |
| 8 | DOSEHINDA | ||
| 8 | DOSELINDA | ||
| 8 | GEALRT | geriatric alert | \n Proposed therapy is outside of standard practice for a geriatric patient. \r\n\n |
| 8 | PEALRT | pediatric alert | \n Proposed therapy is outside of the standard practice for a pediatric patient. \r\n\n |
| 7 | COND | Condition Alert | \n Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis \r\n\n |
| 8 | HGHT | ||
| 8 | LACT | Lactation Alert | \n Proposed therapy may be inappropriate or contraindicated when breast-feeding \r\n\n |
| 8 | PREG | Pregnancy Alert | \n Proposed therapy may be inappropriate or contraindicated during pregnancy \r\n\n |
| 8 | WGHT | ||
| 7 | CREACT | common reaction alert | \n \n Description:Proposed therapy may be inappropriate or contraindicated because of a common but non-patient specific reaction to the product. \r\n\n \n Example:There is no record of a specific sensitivity for the patient, but the presence of the sensitivity is common and therefore caution is warranted. \r\n\n |
| 7 | GEN | Genetic Alert | \n Proposed therapy may be inappropriate or contraindicated due to patient genetic indicators. \r\n\n |
| 7 | GEND | Gender Alert | \n Proposed therapy may be inappropriate or contraindicated due to patient gender. \r\n\n |
| 7 | LAB | Lab Alert | \n Proposed therapy may be inappropriate or contraindicated due to recent lab test results \r\n\n |
| 7 | REACT | Reaction Alert | \n Proposed therapy may be inappropriate or contraindicated based on the potential for a patient reaction to the proposed product \r\n\n |
| 8 | ALGY | Allergy Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to the proposed product. (Allergies are immune based reactions.) \r\n\n |
| 8 | INT | Intolerance Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to the proposed product. (Intolerances are non-immune based sensitivities.) \r\n\n |
| 7 | RREACT | Related Reaction Alert | \n Proposed therapy may be inappropriate or contraindicated because of a potential patient reaction to a cross-sensitivity related product. \r\n\n |
| 8 | RALG | Related Allergy Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to a cross-sensitivity related product. (Allergies are immune based reactions.) \r\n\n |
| 8 | RAR | Related Prior Reaction Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded prior adverse reaction to a cross-sensitivity related product. \r\n\n |
| 8 | RINT | Related Intolerance Alert | \n Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to a cross-sensitivity related product. (Intolerances are non-immune based sensitivities.) \r\n\n |
| 6 | BUS | business constraint violation | \n \n Description:A local business rule relating multiple elements has been violated. \r\n\n |
| 6 | CODE_INVAL | code is not valid | \n \n Description:The specified code is not valid against the list of codes allowed for the element. \r\n\n |
| 7 | CODE_DEPREC | code has been deprecated | \n \n Description:The specified code has been deprecated and should no longer be used. Select another code from the code system. \r\n\n |
| 6 | FORMAT | invalid format | \n \n Description:The element does not follow the formatting or type rules defined for the field. \r\n\n |
| 6 | ILLEGAL | illegal | \n \n Description:The request is missing elements or contains elements which cause it to not meet the legal standards for actioning. \r\n\n |
| 6 | LEN_RANGE | length out of range | \n \n Description:The length of the data specified falls out of the range defined for the element. \r\n\n |
| 7 | LEN_LONG | length is too long | \n \n Description:The length of the data specified is greater than the maximum length defined for the element. \r\n\n |
| 7 | LEN_SHORT | length is too short | \n \n Description:The length of the data specified is less than the minimum length defined for the element. \r\n\n |
| 6 | MISSCOND | conditional element missing | \n \n Description:The specified element must be specified with a non-null value under certain conditions. In this case, the conditions are true but the element is still missing or null. \r\n\n |
| 6 | MISSMAND | mandatory element missing | \n \n Description:The specified element is mandatory and was not included in the instance. \r\n\n |
| 6 | NODUPS | duplicate values are not permitted | \n \n Description:More than one element with the same value exists in the set. Duplicates not permission in this set in a set. \r\n\n |
| 6 | NOPERSIST | element will not be persisted | \n \n Description: Element in submitted message will not persist in data storage based on detected issue. \r\n\n |
| 6 | REP_RANGE | repetitions out of range | \n \n Description:The number of repeating elements falls outside the range of the allowed number of repetitions. \r\n\n |
| 7 | MAXOCCURS | repetitions above maximum | \n \n Description:The number of repeating elements is above the maximum number of repetitions allowed. \r\n\n |
| 7 | MINOCCURS | repetitions below minimum | \n \n Description:The number of repeating elements is below the minimum number of repetitions allowed. \r\n\n |
| 4 | (_ActAdministrativeRuleDetectedIssueCode) Abstract | ||
| 5 | KEY204 | ||
| 5 | KEY205 | ||
| 5 | KEY206 | non-matching identification | \n \n Description: Metadata associated with the identification (e.g. name or gender) does not match the identification being verified. \r\n\n |
| 5 | OBSOLETE | obsolete record returned | \n \n Description: One or more records in the query response have a status of 'obsolete'. \r\n\n |
| 3 | (_ActSuppliedItemDetectedIssueCode) Abstract | \n Identifies types of detected issues regarding the administration or supply of an item to a patient. \r\n\n | |
| 4 | (_AdministrationDetectedIssueCode) Abstract | \n Administration of the proposed therapy may be inappropriate or contraindicated as proposed \r\n\n | |
| 5 | (_AppropriatenessDetectedIssueCode) Abstract | ||
| 6 | (_InteractionDetectedIssueCode) Abstract | ||
| 7 | FOOD | Food Interaction Alert | \n Proposed therapy may interact with certain foods \r\n\n |
| 7 | TPROD | Therapeutic Product Alert | \n Proposed therapy may interact with an existing or recent therapeutic product \r\n\n |
| 8 | DRG | Drug Interaction Alert | \n Proposed therapy may interact with an existing or recent drug therapy \r\n\n |
| 8 | NHP | Natural Health Product Alert | \n Proposed therapy may interact with existing or recent natural health product therapy \r\n\n |
| 8 | NONRX | Non-Prescription Interaction Alert | \n Proposed therapy may interact with a non-prescription drug (e.g. alcohol, tobacco, Aspirin) \r\n\n |
| 6 | OBSA | ||
| 6 | PREVINEF | previously ineffective | \n \n Definition:The same or similar treatment has previously been attempted with the patient without achieving a positive effect. \r\n\n |
| 5 | COMPLY | ||
| 5 | DACT | drug action detected issue | \n \n Description:Proposed therapy may be contraindicated or ineffective based on an existing or recent drug therapy. \r\n\n |
| 5 | DOSE | ||
| 5 | DUPTHPY | ||
| 5 | TIME | timing detected issue | \n \n Description:Proposed therapy may be inappropriate or ineffective based on the proposed start or end time. \r\n\n |
| 6 | ALRTENDLATE | end too late alert | \n \n Definition:Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy. \r\n\n |
| 6 | ALRTSTRTLATE | start too late alert | \n \n Definition:Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition. \r\n\n |
| 5 | (_TimingDetectedIssueCode) Abstract | \n Proposed therapy may be inappropriate or ineffective based on the proposed start or end time. \r\n\n | |
| 6 | ENDLATE | End Too Late Alert | \n Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy \r\n\n |
| 6 | STRTLATE | Start Too Late Alert | \n Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition \r\n\n |
| 4 | (_SupplyDetectedIssueCode) Abstract | \n Supplying the product at this time may be inappropriate or indicate compliance issues with the associated therapy \r\n\n | |
| 5 | ALLDONE | already performed | \n \n Definition:The requested action has already been performed and so this request has no effect \r\n\n |
| 5 | FULFIL | fulfillment alert | \n \n Definition:The therapy being performed is in some way out of alignment with the requested therapy. \r\n\n |
| 6 | NOTACTN | no longer actionable | \n \n Definition:The status of the request being fulfilled has changed such that it is no longer actionable. This may be because the request has expired, has already been completely fulfilled or has been otherwise stopped or disabled. (Not used for 'suspended' orders.) \r\n\n |
| 6 | NOTEQUIV | not equivalent alert | \n \n Definition:The therapy being performed is not sufficiently equivalent to the therapy which was requested. \r\n\n |
| 7 | NOTEQUIVGEN | not generically equivalent alert | \n \n Definition:The therapy being performed is not generically equivalent (having the identical biological action) to the therapy which was requested. \r\n\n |
| 7 | NOTEQUIVTHER | not therapeutically equivalent alert | \n \n Definition:The therapy being performed is not therapeutically equivalent (having the same overall patient effect) to the therapy which was requested. \r\n\n |
| 6 | TIMING | event timing incorrect alert | \n \n Definition:The therapy is being performed at a time which diverges from the time the therapy was requested \r\n\n |
| 7 | INTERVAL | outside requested time | \n \n Definition:The therapy action is being performed outside the bounds of the time period requested \r\n\n |
| 7 | MINFREQ | too soon within frequency based on the usage | \n \n Definition:The therapy action is being performed too soon after the previous occurrence based on the requested frequency \r\n\n |
| 5 | HELD | held/suspended alert | \n \n Definition:There should be no actions taken in fulfillment of a request that has been held or suspended. \r\n\n |
| 5 | TOOLATE | Refill Too Late Alert | \n The patient is receiving a subsequent fill significantly later than would be expected based on the amount previously supplied and the therapy dosage instructions \r\n\n |
| 5 | TOOSOON | Refill Too Soon Alert | \n The patient is receiving a subsequent fill significantly earlier than would be expected based on the amount previously supplied and the therapy dosage instructions \r\n\n |
| 4 | HISTORIC | record recorded as historical | \n \n Description: While the record was accepted in the repository, there is a more recent version of a record of this type. \r\n\n |
| 4 | PATPREF | violates stated preferences | \n \n Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. \r\n\n |
| 5 | PATPREFALT | violates stated preferences, alternate available | \n \n Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. An alternate therapy meeting those constraints is available. \r\n\n |
| 2 | KSUBJ | knowledge subject | Categorization of types of observation that capture the main clinical knowledge subject which may be a medication, a laboratory test, a disease. |
| 2 | KSUBT | knowledge subtopic | Categorization of types of observation that capture a knowledge subtopic which might be treatment, etiology, or prognosis. |
| 2 | OINT | intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to an agent. \r\n\n |
| 3 | ALG | Allergy | \n Hypersensitivity to an agent caused by an immunologic response to an initial exposure \r\n\n |
| 4 | DALG | Drug Allergy | \n An allergy to a pharmaceutical product. \r\n\n |
| 4 | EALG | Environmental Allergy | \n An allergy to a substance other than a drug or a food. E.g. Latex, pollen, etc. \r\n\n |
| 4 | FALG | Food Allergy | \n An allergy to a substance generally consumed for nutritional purposes. \r\n\n |
| 3 | DINT | Drug Intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to a drug. \r\n\n |
| 4 | DALG | ||
| 4 | DNAINT | Drug Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 3 | EINT | Environmental Intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to environmental conditions. \r\n\n |
| 4 | EALG | ||
| 4 | ENAINT | Environmental Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 3 | FINT | Food Intolerance | \n Hypersensitivity resulting in an adverse reaction upon exposure to food. \r\n\n |
| 4 | FALG | ||
| 4 | FNAINT | Food Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 3 | NAINT | Non-Allergy Intolerance | \n Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure \r\n\n |
| 4 | DNAINT | ||
| 4 | ENAINT | ||
| 4 | FNAINT | ||
| 2 | SEV | Severity Observation | \n A subjective evaluation of the seriousness or intensity associated with another observation. \r\n\n |
| 2 | (_FDALabelData) Abstract | \n FDA label data \r\n\n | |
| 3 | FDACOATING | coating | \n FDA label coating \r\n\n |
| 3 | FDACOLOR | color | \n FDA label color \r\n\n |
| 3 | FDAIMPRINTCD | imprint code | \n FDA label imprint code \r\n\n |
| 3 | FDALOGO | logo | \n FDA label logo \r\n\n |
| 3 | FDASCORING | scoring | \n FDA label scoring \r\n\n |
| 3 | FDASHAPE | shape | \n FDA label shape \r\n\n |
| 3 | FDASIZE | size | \n FDA label size \r\n\n |
| 1 | (_ROIOverlayShape) Abstract | \n Shape of the region on the object being referenced \r\n\n | |
| 2 | CIRCLE | circle | \n A circle defined by two (column,row) pairs. The first point is the center of the circle and the second point is a point on the perimeter of the circle. \r\n\n |
| 2 | ELLIPSE | ellipse | \n An ellipse defined by four (column,row) pairs, the first two points specifying the endpoints of the major axis and the second two points specifying the endpoints of the minor axis. \r\n\n |
| 2 | POINT | point | \n A single point denoted by a single (column,row) pair, or multiple points each denoted by a (column,row) pair. \r\n\n |
| 2 | POLY | polyline | \n A series of connected line segments with ordered vertices denoted by (column,row) pairs; if the first and last vertices are the same, it is a closed polygon. \r\n\n |
| 1 | C | corrected | \n \n Description:Indicates that result data has been corrected. \r\n\n |
| 1 | DIET | Diet | \n Code set to define specialized/allowed diets \r\n\n |
| 2 | BR | breikost (GE) | \n A diet exclusively composed of oatmeal, semolina, or rice, to be extremely easy to eat and digest. \r\n\n |
| 2 | DM | diabetes mellitus diet | \n A diet that uses carbohydrates sparingly. Typically with a restriction in daily energy content (e.g. 1600-2000 kcal). \r\n\n |
| 2 | FAST | fasting | \n No enteral intake of foot or liquids whatsoever, no smoking. Typically 6 to 8 hours before anesthesia. \r\n\n |
| 2 | FORMULA | formula diet | \n A diet consisting of a formula feeding, either for an infant or an adult, to provide nutrition either orally or through the gastrointestinal tract via tube, catheter or stoma. \r\n\n |
| 2 | GF | gluten free | \n Gluten free diet for celiac disease. \r\n\n |
| 2 | LF | low fat | \n A diet low in fat, particularly to patients with hepatic diseases. \r\n\n |
| 2 | LP | low protein | \n A low protein diet for patients with renal failure. \r\n\n |
| 2 | LQ | liquid | \n A strictly liquid diet, that can be fully absorbed in the intestine, and therefore may not contain fiber. Used before enteral surgeries. \r\n\n |
| 2 | LS | low sodium | \n A diet low in sodium for patients with congestive heart failure and/or renal failure. \r\n\n |
| 2 | N | normal diet | \n A normal diet, i.e. no special preparations or restrictions for medical reasons. This is notwithstanding any preferences the patient might have regarding special foods, such as vegetarian, kosher, etc. \r\n\n |
| 2 | NF | no fat | \n A no fat diet for acute hepatic diseases. \r\n\n |
| 2 | PAF | phenylalanine free | \n Phenylketonuria diet. \r\n\n |
| 2 | PAR | parenteral | \n Patient is supplied with parenteral nutrition, typically described in terms of i.v. medications. \r\n\n |
| 2 | RD | reduction diet | \n A diet that seeks to reduce body fat, typically low energy content (800-1600 kcal). \r\n\n |
| 2 | SCH | schonkost (GE) | \n A diet that avoids ingredients that might cause digestion problems, e.g., avoid excessive fat, avoid too much fiber (cabbage, peas, beans). \r\n\n |
| 2 | SUPPLEMENT | nutritional supplement | \n A diet that is not intended to be complete but is added to other diets. \r\n\n |
| 2 | T | tea only | \n This is not really a diet, since it contains little nutritional value, but is essentially just water. Used before coloscopy examinations. \r\n\n |
| 2 | VLI | low valin, leucin, isoleucin | \n Diet with low content of the amino-acids valin, leucin, and isoleucin, for "maple syrup disease." \r\n\n |
| 1 | DRUGPRG | drug program | \n \n Definition: A public or government health program that administers and funds coverage for prescription drugs to assist program eligible who meet financial and health status criteria. \r\n\n |
| 1 | F | final | \n \n Description:Indicates that a result is complete. No further results are to come. This maps to the 'complete' state in the observation result status code. \r\n\n |
| 1 | PRLMN | preliminary | \n \n Description:Indicates that a result is incomplete. There are further results to come. This maps to the 'active' state in the observation result status code. \r\n\n |
| 1 | (SECOBS) Abstract | \n An observation identifying security metadata about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used to name security labels. \r\n\n \n Rationale: According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator's clearance to the target's security label. All of the following must be true for authorization to be granted: \r\n\n \n The security policy identifiers shall be identical\n The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and \n For each security category in the target label, there shall be a security category of the same type in the initiator's clearance and the initiator's classification level shall dominate that of the target.\n \n \n Examples: SecurityObservationType security label fields include: \r\n\n \n Confidentiality classification\n Compartment category\n Sensitivity category\n Security mechanisms used to ensure data integrity or to perform authorized data transformation\n Indicators of an IT resource completeness, veracity, reliability, trustworthiness, or provenance.\n \n \n Usage Note: SecurityObservationType codes designate security label field types, which are valued with an applicable SecurityObservationValue code as the "security label tag". \r\n\n | |
| 2 | SECCATOBS | security category observation | \n Type of security metadata observation made about the category of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security category metadata is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone." \r\n\n \n Rationale: A security category observation supports requirement to specify the type of IT resource to facilitate application of appropriate levels of information security according to a range of levels of impact or consequences that might result from the unauthorized disclosure, modification, or use of the information or information system. A resource is assigned to a specific category of information (e.g., privacy, medical, proprietary, financial, investigative, contractor sensitive, security management) defined by an organization or in some instances, by a specific law, Executive Order, directive, policy, or regulation. [FIPS 199] \r\n\n \n Examples: Types of security categories include: \r\n\n \n Compartment: A division of data into isolated blocks with separate security controls for the purpose of reducing risk. (ISO 2382-8). A security label tag that "segments" an IT resource by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Classification System) \n Sensitivity: The characteristic of an IT resource which implies its value or importance and may include its vulnerability. (ISO 7492-2) Privacy metadata for information perceived as undesirable to share. (HL7 Healthcare Classification System)\n \n |
| 2 | SECCLASSOBS | security classification observation | \n Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection." Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure. \r\n\n \n Rationale: A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue. This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality. \r\n\n \n Examples: Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal. Intelligence community examples include top secret, secret, and confidential. \r\n\n \n Usage Note: Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObservationValue code as the "security label tag". \r\n\n |
| 2 | SECCONOBS | security control observation | \n Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security control metadata convey instructions to users and receivers for secure distribution, transmission, and storage; dictate obligations or mandated actions; specify any action prohibited by refrain policy such as dissemination controls; and stipulate the permissible purpose of use of an IT resource. \r\n\n \n Rationale: A security control observation supports requirement to specify applicable management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. [FIPS 199] \r\n\n \n Examples: Types of security control metadata include: \r\n\n \n handling caveats\n dissemination controls\n obligations\n refrain policies\n purpose of use constraints\n \n |
| 2 | SECINTOBS | security integrity observation | \n Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. \r\n\n \n Rationale: A security integrity observation supports the requirement to guard against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. (44 U.S.C., SEC. 3542) \r\n\n \n Examples: Types of security integrity metadata include: \r\n\n \n Integrity status, which indicates the completeness or workflow status of an IT resource (data, information object, service, or system capability)\n Integrity confidence, which indicates the reliability and trustworthiness of an IT resource\n Integrity control, which indicates pertinent handling caveats, obligations, refrain policies, and purpose of use for the resource\n Data integrity, which indicate the security mechanisms used to ensure that the accuracy and consistency are preserved regardless of changes made (ISO/IEC DIS 2382-8)\n Alteration integrity, which indicate the security mechanisms used for authorized transformations of the resource\n Integrity provenance, which indicates the entity responsible for a report or assertion relayed "second-hand" about an IT resource\n \n |
| 3 | SECALTINTOBS | security alteration integrity observation | \n Type of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource. \r\n\n \n Examples: Types of security alteration integrity observation metadata, which may value the observation with a code used to indicate the mechanism used for authorized transformation of an IT resource, including: \r\n\n \n translation\n syntactic transformation\n semantic mapping\n redaction\n masking\n pseudonymization\n anonymization\n \n |
| 3 | SECDATINTOBS | security data integrity observation | \n Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency. Data integrity is defined by ISO 22600-23.3.21 as: "The property that data has not been altered or destroyed in an unauthorized manner", and by ISO/IEC 2382-8: The property of data whose accuracy and consistency are preserved regardless of changes made." \r\n\n \n Examples: Types of security data integrity observation metadata, which may value the observation, include cryptographic hash function and digital signature. \r\n\n |
| 3 | SECINTCONOBS | security integrity confidence observation | \n Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. \r\n\n \n Examples: Types of security integrity confidence observation metadata, which may value the observation, include highly reliable, uncertain reliability, and not reliable. \r\n\n \n Usage Note: A security integrity confidence observation on an Act may indicate that a valued Act.uncertaintycode attribute has been overridden by the entity responsible for ascribing the SecurityIntegrityConfidenceObservationValue. This supports the business requirements for increasing or decreasing the assessment of the reliability or trustworthiness of an IT resource based on parameters beyond the original assignment of an Act statement level of uncertainty. \r\n\n |
| 3 | (SECINTPRVOBS) Abstract | \n Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness of an IT resource in terms of workflow status such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure. Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness. \r\n\n \n Examples: Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: \r\n\n \n completeness or workflow status, such as authentication\n the entity responsible for original authoring or informing about an IT resource\n the entity responsible for a report or assertion about an IT resource relayed second-hand ?\n the entity responsible for excerpting, transforming, or compiling an IT resource\n \n | |
| 4 | SECINTPRVABOBS | security integrity provenance asserted by observation | \n Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource. The asserting entity may not be the original informant about the resource. \r\n\n \n Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including: \r\n\n \n assertions about an IT resource by a patient\n assertions about an IT resource by a clinician\n assertions about an IT resource by a device\n \n |
| 4 | SECINTPRVRBOBS | security integrity provenance reported by observation | \n Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource. The reporting entity may not be the original author of the resource. \r\n\n \n Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include: \r\n\n \n reports about an IT resource by a patient\n reports about an IT resource by a clinician\n reports about an IT resource by a device\n \n |
| 3 | SECINTSTOBS | security integrity status observation | \n Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Indicates the completeness of an IT resource in terms of workflow status, which may impact users that are authorized to access and use the resource. \r\n\n \n Examples: Types of security integrity status observation metadata, which may value the observation, include codes from the HL7 DocumentCompletion code system such as legally authenticated, in progress, and incomplete. \r\n\n |
| 2 | (SECTRSTOBS) Abstract | \n An observation identifying trust metadata about an IT resource (data, information object, service, or system capability), which may be used as a trust attribute to populate a computable trust policy, trust credential, trust assertion, or trust label field in a security label or trust policy, which are principally used for authentication, authorization, and access control decisions. \r\n\n | |
| 3 | TRSTACCRDOBS | trust accreditation observation | \n Type of security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. \r\n\n |
| 3 | TRSTAGREOBS | trust agreement observation | \n Type of security metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] \r\n\n |
| 3 | TRSTCERTOBS | trust certificate observation | \n Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] \r\n\n \n For example,\n \r\n\n \n A Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. For example, a particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.\n A Certificate Practice Statement (CSP), which is a statement of the practices which an Authority employs in issuing and managing certificates. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.]\n \n |
| 3 | TRSTFWKOBS | trust framework observation | \n Type of security metadata observation made about a complete set of contracts, regulations or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative] \r\n\n |
| 3 | TRSTLOAOBS | trust assurance observation | \n Type of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. \r\n\n |
| 3 | TRSTMECOBS | trust mechanism observation | \n Type of security metadata observation made about a security architecture system component that supports enforcement of security policies. \r\n\n |
| 1 | SUBSIDFFS | subsidized fee for service program | \n \n Definition: A government health program that provides coverage on a fee for service basis for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. \r\n\n \n Discussion: The structure and business processes for underwriting and administering a subsidized fee for service program is further specified by the Underwriter and Payer Role.class and Role.code. \r\n\n |
| 1 | WRKCOMP | (workers compensation program | \n \n Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment. Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program. Employees may be required to pay premiums toward the cost of coverage as well. \r\n\n |
| 1 | (_ActProcedureCode) Abstract | \n An identifying code for healthcare interventions/procedures. \r\n\n | |
| 2 | (_ActBillableServiceCode) Abstract | \n \n Definition: An identifying code for billable services, as opposed to codes for similar services used to identify them for functional purposes. \r\n\n | |
| 1 | (_HL7DefinedActCodes) Abstract | \n Domain provides the root for HL7-defined detailed or rich codes for the Act classes. \r\n\n | |
| 1 | COPAY | ||
| 1 | DEDUCT | ||
| 1 | DOSEIND | ||
| 1 | PRA | ||
| 1 | STORE Deprecated | Storage | \n The act of putting something away for safe keeping. The "something" may be physical object such as a specimen, or information, such as observations regarding a specimen. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | D | Deferred | \n Query response is deferred. \r\n\n |
| 1 | I | Immediate | \n Query response is immediate. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | col | col | |
| 1 | colgroup | colgroup | |
| 1 | row | row | |
| 1 | rowgroup | rowgroup |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (BindingRealms) Abstract | \n \n Description: Concepts that can be used as Binding Realms when creating Binding Statements. These codes are permitted to appear in the InfrastructureRoot.realmCode attribute. \r\n\n | |
| 2 | (AffiliateRealms) Abstract | \n \n Description: Realm codes for official HL7 organizational bodies. This includes both the HL7 International organization as well as all recognized international affiliates (past and present). These groups have the ability to bind vocabulary and develop artifacts. As well, they have the ability to have "ownership" over other binding realms and namespace realms via the owningAffiliate property of those other realm codes. \r\n\n | |
| 3 | AR | Argentina | \n \n Description: Realm code for use of Argentina \r\n\n |
| 3 | AT | Austria | \n \n Description: Realm code for use of Austria \r\n\n |
| 3 | AU | Australia | \n \n Description: Realm code for use of Australia \r\n\n |
| 3 | BR | Brazil | \n \n Description: Realm code for use of Brazil \r\n\n |
| 3 | CA | Canada | \n \n Description: Realm code for use of Canada \r\n\n |
| 3 | CH | Switzerland | \n \n Description: Realm code for use of Switzerland \r\n\n |
| 3 | CL | Chile | \n \n Description: Realm code for use of Chile \r\n\n |
| 3 | CN | China | \n \n Description: Realm code for use of China \r\n\n |
| 3 | CO | Columbia | \n \n Description: Realm code for use of Localized Version \r\n\n |
| 3 | CZ | Czech Republic | \n \n Description: Realm code for use of Czech Republic \r\n\n |
| 3 | DE | Germany | \n \n Description: Realm code for use of Germany \r\n\n |
| 3 | DK | Denmark | \n \n Description: Realm code for use of Denmark \r\n\n |
| 3 | ES | Spain | \n \n Description: Realm code for use of Spain \r\n\n |
| 3 | FI | Finland | \n \n Description: Realm code for use of Finland \r\n\n |
| 3 | FR | France | \n \n Description: Realm code for use of France \r\n\n |
| 3 | GR | Greece | \n \n Description: Realm code for use of Greece \r\n\n |
| 3 | HR | Croatia | \n \n Description: Realm code for use of Croatia \r\n\n |
| 3 | IE | Ireland | \n \n Description: Realm code for use of Ireland \r\n\n |
| 3 | IN | India | \n \n Description: Realm code for use of India \r\n\n |
| 3 | IT | Italy | \n \n Description: Realm code for use of Italy \r\n\n |
| 3 | JP | Japan | \n \n Description: Realm code for use of Japan \r\n\n |
| 3 | KR | Korea | \n \n Description: Realm code for use of Korea \r\n\n |
| 3 | LT | Lithuania | \n \n Description: Realm code for use of Lithuania \r\n\n |
| 3 | MX | Mexico | \n \n Description: Realm code for use of Mexico \r\n\n |
| 3 | NL | The Netherlands | \n \n Description: Realm code for use of The Netherlands \r\n\n |
| 3 | NZ | New Zealand | \n \n Description: Realm code for use of New Zealand \r\n\n |
| 3 | RO | Romania | \n \n Description: Realm code for use of Romania \r\n\n |
| 3 | RU | Russian Federation | \n \n Description: Realm code for use of Russian Federation \r\n\n |
| 3 | SE | Sweden | \n \n Description: Realm code for use of Sweden \r\n\n |
| 3 | SG | Singapore | \n \n Description: Realm code for use of Localized Version \r\n\n |
| 3 | SOA | Southern Africa | \n \n Description: Realm code for use of Southern Africa \r\n\n |
| 3 | TR | Turkey | \n \n Description: Realm code for use of Turkey \r\n\n |
| 3 | TW | Taiwan | \n \n Description: Realm code for use of Taiwan \r\n\n |
| 3 | UK | United Kingdom | \n \n Description: Realm code for use of United Kingdom \r\n\n |
| 3 | US | United States of America | \n \n Description: Realm code for use of United States of America \r\n\n |
| 3 | UV | Universal | \n \n Description: Realm code for use of Universal realm or context, used in every instance \r\n\n |
| 3 | UY | Uruguay | \n \n Description: Realm code for use of Uruguay \r\n\n |
| 2 | C1 | Unclassified Realm | \n \n Description: Realm code for use of Unclassified Realm \r\n\n |
| 2 | GB | Great Britain | \n \n Description: Realm code for use of Great Britain \r\n\n |
| 2 | R1 | Representative Realm | \n \n Description: Realm code for use of Representative Realm \r\n\n |
| 2 | X1 | Example Realm | \n \n Description: Realm code for use of Example Realm \r\n\n |
| 1 | (NamespaceRealms) Abstract | \n \n Description: Codes that can be used in the "realm" portion of HL7 v3 artifact identifiers. \r\n\n | |
| 2 | AffiliateRealms | ||
| 2 | GB | ||
| 2 | ZZ | Localized Version | \n \n Description: An artifact created for local use only. This realm namespace has no owning affiliate. Its use is uncontrolled, i.e. anyone can create artifacts using this realm namespace. Because of this, there is a significant likelihood of artifact identifier collisions. Implementers are encouraged to register their artifacts under an affiliate owned and controlled namespace to avoid such collision problems where possible. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | (_RouteByMethod) Abstract | \n Route of substance administration classified by administration method. \r\n\n | |
| 2 | SOAK | Immersion (soak) | \n Immersion (soak) \r\n\n |
| 2 | SHAMPOO | Shampoo | \n Shampoo \r\n\n |
| 2 | TRNSLING | Translingual | \n Translingual \r\n\n |
| 2 | PO | Swallow, oral | \n Swallow, oral \r\n\n |
| 2 | GARGLE | Gargle | \n Gargle \r\n\n |
| 2 | SUCK | Suck, oromucosal | \n Suck, oromucosal \r\n\n |
| 2 | (_Chew) Abstract | \n Chew \r\n\n | |
| 3 | CHEW | Chew, oral | \n Chew, oral \r\n\n |
| 2 | (_Diffusion) Abstract | \n Diffusion \r\n\n | |
| 3 | EXTCORPDIF | Diffusion, extracorporeal | \n Diffusion, extracorporeal \r\n\n |
| 3 | HEMODIFF | Diffusion, hemodialysis | \n Diffusion, hemodialysis \r\n\n |
| 3 | TRNSDERMD | Diffusion, transdermal | \n Diffusion, transdermal \r\n\n |
| 2 | (_Dissolve) Abstract | \n Dissolve \r\n\n | |
| 3 | DISSOLVE | Dissolve, oral | \n Dissolve, oral \r\n\n |
| 3 | SL | Dissolve, sublingual | \n Dissolve, sublingual \r\n\n |
| 2 | (_Douche) Abstract | \n Douche \r\n\n | |
| 3 | DOUCHE | Douche, vaginal | \n Douche, vaginal \r\n\n |
| 2 | (_ElectroOsmosisRoute) Abstract | \n Electro-osmosis \r\n\n | |
| 3 | ELECTOSMOS | Electro-osmosis | \n Electro-osmosis \r\n\n |
| 2 | (_Enema) Abstract | \n Enema \r\n\n | |
| 3 | ENEMA | Enema, rectal | \n Enema, rectal \r\n\n |
| 3 | RETENEMA | Enema, rectal retention | \n Enema, rectal retention \r\n\n |
| 2 | (_Flush) Abstract | \n Flush \r\n\n | |
| 3 | IVFLUSH | Flush, intravenous catheter | \n Flush, intravenous catheter \r\n\n |
| 2 | (_Implantation) Abstract | \n Implantation \r\n\n | |
| 3 | IDIMPLNT | Implantation, intradermal | \n Implantation, intradermal \r\n\n |
| 3 | IVITIMPLNT | Implantation, intravitreal | \n Implantation, intravitreal \r\n\n |
| 3 | SQIMPLNT | Implantation, subcutaneous | \n Implantation, subcutaneous \r\n\n |
| 2 | (_Infusion) Abstract | \n Infusion \r\n\n | |
| 3 | EPI | Infusion, epidural | \n Infusion, epidural \r\n\n |
| 3 | IA | Infusion, intraarterial catheter | \n Infusion, intraarterial catheter \r\n\n |
| 3 | IC | Infusion, intracardiac | \n Infusion, intracardiac \r\n\n |
| 3 | ICOR | Infusion, intracoronary | \n Infusion, intracoronary \r\n\n |
| 3 | IOSSC | Infusion, intraosseous, continuous | \n Infusion, intraosseous, continuous \r\n\n |
| 3 | IT | Infusion, intrathecal | \n Infusion, intrathecal \r\n\n |
| 3 | IV | Infusion, intravenous | \n Infusion, intravenous \r\n\n |
| 4 | IVC | Infusion, intravenous catheter | \n Infusion, intravenous catheter \r\n\n |
| 4 | IVCC | Infusion, intravenous catheter, continuous | \n Infusion, intravenous catheter, continuous \r\n\n |
| 4 | IVCI | Infusion, intravenous catheter, intermittent | \n Infusion, intravenous catheter, intermittent \r\n\n |
| 4 | PCA | Infusion, intravenous catheter, pca pump | \n Infusion, intravenous catheter, pca pump \r\n\n |
| 3 | IVASCINFUS | Infusion, intravascular | \n Infusion, intravascular \r\n\n |
| 3 | SQINFUS | Infusion, subcutaneous | \n Infusion, subcutaneous \r\n\n |
| 2 | (_Inhalation) Abstract | \n Inhalation \r\n\n | |
| 3 | IPINHL | Inhalation, respiratory | \n Inhalation, oral \r\n\n |
| 4 | ORIFINHL | Inhalation, oral intermittent flow | \n Inhalation, oral intermittent flow \r\n\n |
| 4 | REBREATH | Inhalation, oral rebreather mask | \n Inhalation, oral rebreather mask \r\n\n |
| 3 | IPPB | Inhalation, intermittent positive pressure breathing (ippb) | \n Inhalation, intermittent positive pressure breathing (ippb) \r\n\n |
| 3 | NASINHL | Inhalation, nasal | \n Inhalation, nasal \r\n\n |
| 4 | NASINHLC | Inhalation, nasal cannula | \n Inhalation, nasal, prongs \r\n\n |
| 3 | NEB | Inhalation, nebulization | \n Inhalation, nebulization \r\n\n |
| 4 | NASNEB | Inhalation, nebulization, nasal | \n Inhalation, nebulization, nasal \r\n\n |
| 4 | ORNEB | Inhalation, nebulization, oral | \n Inhalation, nebulization, oral \r\n\n |
| 3 | TRACH | Inhalation, tracheostomy | \n Inhalation, tracheostomy \r\n\n |
| 3 | VENT | Inhalation, ventilator | \n Inhalation, ventilator \r\n\n |
| 3 | VENTMASK | Inhalation, ventimask | \n Inhalation, ventimask \r\n\n |
| 2 | (_Injection) Abstract | \n Injection \r\n\n | |
| 3 | AMNINJ | Injection, amniotic fluid | \n Injection, amniotic fluid \r\n\n |
| 3 | BILINJ | Injection, biliary tract | \n Injection, biliary tract \r\n\n |
| 3 | CHOLINJ | Injection, for cholangiography | \n Injection, for cholangiography \r\n\n |
| 3 | CERVINJ | Injection, cervical | \n Injection, cervical \r\n\n |
| 3 | EPIDURINJ | Injection, epidural | \n Injection, epidural \r\n\n |
| 3 | EPIINJ | Injection, epidural, push | \n Injection, epidural, push \r\n\n |
| 3 | EPINJSP | Injection, epidural, slow push | \n Injection, epidural, slow push \r\n\n |
| 3 | EXTRAMNINJ | Injection, extra-amniotic | \n Injection, extra-amniotic \r\n\n |
| 3 | EXTCORPINJ | Injection, extracorporeal | \n Injection, extracorporeal \r\n\n |
| 3 | GBINJ | Injection, gastric button | \n Injection, gastric button \r\n\n |
| 3 | GINGINJ | Injection, gingival | \n Injection, gingival \r\n\n |
| 3 | BLADINJ | Injection, urinary bladder | \n Injection, urinary bladder \r\n\n |
| 3 | ENDOSININJ | Injection, endosinusial | \n Injection, endosinusial \r\n\n |
| 3 | HEMOPORT | Injection, hemodialysis port | \n Injection, hemodialysis port \r\n\n |
| 3 | IABDINJ | Injection, intra-abdominal | \n Injection, intra-abdominal \r\n\n |
| 3 | IAINJ | Injection, intraarterial | \n Injection, intraarterial \r\n\n |
| 4 | IAINJP | Injection, intraarterial, push | \n Injection, intraarterial, push \r\n\n |
| 4 | IAINJSP | Injection, intraarterial, slow push | \n Injection, intraarterial, slow push \r\n\n |
| 3 | IARTINJ | Injection, intraarticular | \n Injection, intraarticular \r\n\n |
| 3 | IBURSINJ | Injection, intrabursal | \n Injection, intrabursal \r\n\n |
| 3 | ICARDINJ | Injection, intracardiac | \n Injection, intracardiac \r\n\n |
| 4 | ICARDINJRP | Injection, intracardiac, rapid push | \n Injection, intracardiac, rapid push \r\n\n |
| 4 | ICARDINJSP | Injection, intracardiac, slow push | \n Injection, intracardiac, slow push \r\n\n |
| 4 | ICARINJP | Injection, intracardiac, push | \n Injection, intracardiac, push \r\n\n |
| 3 | ICARTINJ | Injection, intracartilaginous | \n Injection, intracartilaginous \r\n\n |
| 3 | ICAUDINJ | Injection, intracaudal | \n Injection, intracaudal \r\n\n |
| 3 | ICAVINJ | Injection, intracavernous | \n Injection, intracavernous \r\n\n |
| 3 | ICAVITINJ | Injection, intracavitary | \n Injection, intracavitary \r\n\n |
| 3 | ICEREBINJ | Injection, intracerebral | \n Injection, intracerebral \r\n\n |
| 3 | ICISTERNINJ | Injection, intracisternal | \n Injection, intracisternal \r\n\n |
| 3 | ICORONINJ | Injection, intracoronary | \n Injection, intracoronary \r\n\n |
| 4 | ICORONINJP | Injection, intracoronary, push | \n Injection, intracoronary, push \r\n\n |
| 3 | ICORPCAVINJ | Injection, intracorpus cavernosum | \n Injection, intracorpus cavernosum \r\n\n |
| 3 | IDINJ | Injection, intradermal | \n Injection, intradermal \r\n\n |
| 3 | IDISCINJ | Injection, intradiscal | \n Injection, intradiscal \r\n\n |
| 3 | IDUCTINJ | Injection, intraductal | \n Injection, intraductal \r\n\n |
| 3 | IDURINJ | Injection, intradural | \n Injection, intradural \r\n\n |
| 3 | IEPIDINJ | Injection, intraepidermal | \n Injection, intraepidermal \r\n\n |
| 3 | IEPITHINJ | Injection, intraepithelial | \n Injection, intraepithelial \r\n\n |
| 3 | ILESINJ | Injection, intralesional | \n Injection, intralesional \r\n\n |
| 3 | ILUMINJ | Injection, intraluminal | \n Injection, intraluminal \r\n\n |
| 3 | ILYMPJINJ | Injection, intralymphatic | \n Injection, intralymphatic \r\n\n |
| 3 | IM | Injection, intramuscular | \n Injection, intramuscular \r\n\n |
| 4 | IMD | Injection, intramuscular, deep | \n Injection, intramuscular, deep \r\n\n |
| 4 | IMZ | Injection, intramuscular, z track | \n Injection, intramuscular, z track \r\n\n |
| 3 | IMEDULINJ | Injection, intramedullary | \n Injection, intramedullary \r\n\n |
| 3 | INTERMENINJ | Injection, interameningeal | \n Injection, interameningeal \r\n\n |
| 3 | INTERSTITINJ | Injection, interstitial | \n Injection, interstitial \r\n\n |
| 3 | IOINJ | Injection, intraocular | \n Injection, intraocular \r\n\n |
| 3 | IOSSINJ | Injection, intraosseous | \n Injection, intraosseous \r\n\n |
| 3 | IOVARINJ | Injection, intraovarian | \n Injection, intraovarian \r\n\n |
| 3 | IPCARDINJ | Injection, intrapericardial | \n Injection, intrapericardial \r\n\n |
| 3 | IPERINJ | Injection, intraperitoneal | \n Injection, intraperitoneal \r\n\n |
| 3 | IPINJ | Injection, intrapulmonary | \n Injection, intrapulmonary \r\n\n |
| 3 | IPLRINJ | Injection, intrapleural | \n Injection, intrapleural \r\n\n |
| 3 | IPROSTINJ | Injection, intraprostatic | \n Injection, intraprostatic \r\n\n |
| 3 | IPUMPINJ | Injection, insulin pump | \n Injection, insulin pump \r\n\n |
| 3 | ISINJ | Injection, intraspinal | \n Injection, intraspinal \r\n\n |
| 3 | ISTERINJ | Injection, intrasternal | \n Injection, intrasternal \r\n\n |
| 3 | ISYNINJ | Injection, intrasynovial | \n Injection, intrasynovial \r\n\n |
| 3 | ITENDINJ | Injection, intratendinous | \n Injection, intratendinous \r\n\n |
| 3 | ITESTINJ | Injection, intratesticular | \n Injection, intratesticular \r\n\n |
| 3 | ITHORINJ | Injection, intrathoracic | \n Injection, intrathoracic \r\n\n |
| 3 | ITINJ | Injection, intrathecal | \n Injection, intrathecal \r\n\n |
| 3 | ITUBINJ | Injection, intratubular | \n Injection, intratubular \r\n\n |
| 3 | ITUMINJ | Injection, intratumor | \n Injection, intratumor \r\n\n |
| 3 | ITYMPINJ | Injection, intratympanic | \n Injection, intratympanic \r\n\n |
| 3 | IUINJ | Injection, intrauterine | \n Injection, intracervical (uterus) \r\n\n |
| 3 | IUINJC | Injection, intracervical (uterus) | \n Injection, intracervical (uterus) \r\n\n |
| 3 | IURETINJ | Injection, intraureteral, retrograde | \n Injection, intraureteral, retrograde \r\n\n |
| 3 | IVASCINJ | Injection, intravascular | \n Injection, intravascular \r\n\n |
| 3 | IVENTINJ | Injection, intraventricular (heart) | \n Injection, intraventricular (heart) \r\n\n |
| 3 | IVESINJ | Injection, intravesicle | \n Injection, intravesicle \r\n\n |
| 3 | IVINJ | Injection, intravenous | \n Injection, intravenous \r\n\n |
| 4 | IVINJBOL | Injection, intravenous, bolus | \n Injection, intravenous, bolus \r\n\n |
| 4 | IVPUSH | Injection, intravenous, push | \n Injection, intravenous, push \r\n\n |
| 4 | IVRPUSH | Injection, intravenous, rapid push | \n Injection, intravenous, rapid push \r\n\n |
| 4 | IVSPUSH | Injection, intravenous, slow push | \n Injection, intravenous, slow push \r\n\n |
| 3 | IVITINJ | Injection, intravitreal | \n Injection, intravitreal \r\n\n |
| 3 | PAINJ | Injection, periarticular | \n Injection, periarticular \r\n\n |
| 3 | PARENTINJ | Injection, parenteral | \n Injection, parenteral \r\n\n |
| 3 | PDONTINJ | Injection, periodontal | \n Injection, periodontal \r\n\n |
| 3 | PDPINJ | Injection, peritoneal dialysis port | \n Injection, peritoneal dialysis port \r\n\n |
| 3 | PDURINJ | Injection, peridural | \n Injection, peridural \r\n\n |
| 3 | PNINJ | Injection, perineural | \n Injection, perineural \r\n\n |
| 3 | PNSINJ | Injection, paranasal sinuses | \n Injection, paranasal sinuses \r\n\n |
| 3 | RBINJ | Injection, retrobulbar | \n Injection, retrobulbar \r\n\n |
| 3 | SCINJ | Injection, subconjunctival | \n Injection, subconjunctival \r\n\n |
| 3 | SLESINJ | Injection, sublesional | \n Injection, sublesional \r\n\n |
| 3 | SOFTISINJ | Injection, soft tissue | \n Injection, soft tissue \r\n\n |
| 3 | SQ | Injection, subcutaneous | \n Injection, subcutaneous \r\n\n |
| 3 | SUBARACHINJ | Injection, subarachnoid | \n Injection, subarachnoid \r\n\n |
| 3 | SUBMUCINJ | Injection, submucosal | \n Injection, submucosal \r\n\n |
| 3 | TRPLACINJ | Injection, transplacental | \n Injection, transplacental \r\n\n |
| 3 | TRTRACHINJ | Injection, transtracheal | \n Injection, transtracheal \r\n\n |
| 3 | URETHINJ | Injection, urethral | \n Injection, urethral \r\n\n |
| 3 | URETINJ | Injection, ureteral | \n Injection, ureteral \r\n\n |
| 2 | (_Insertion) Abstract | \n Insertion \r\n\n | |
| 3 | CERVINS | Insertion, cervical (uterine) | \n Insertion, cervical (uterine) \r\n\n |
| 3 | IOSURGINS | Insertion, intraocular, surgical | \n Insertion, intraocular, surgical \r\n\n |
| 3 | IU | Insertion, intrauterine | \n Insertion, intrauterine \r\n\n |
| 3 | LPINS | Insertion, lacrimal puncta | \n Insertion, lacrimal puncta \r\n\n |
| 3 | PR | Insertion, rectal | \n Insertion, rectal \r\n\n |
| 3 | SQSURGINS | Insertion, subcutaneous, surgical | \n Insertion, subcutaneous, surgical \r\n\n |
| 3 | URETHINS | Insertion, urethral | \n Insertion, urethral \r\n\n |
| 3 | VAGINSI | Insertion, vaginal | \n Insertion, vaginal \r\n\n |
| 2 | (_Instillation) Abstract | \n Instillation \r\n\n | |
| 3 | CECINSTL | Instillation, cecostomy | \n Instillation, cecostomy \r\n\n |
| 3 | EFT | Instillation, enteral feeding tube | \n Instillation, enteral feeding tube \r\n\n |
| 3 | ENTINSTL | Instillation, enteral | \n Instillation, enteral \r\n\n |
| 3 | GT | Instillation, gastrostomy tube | \n Instillation, gastrostomy tube \r\n\n |
| 3 | NGT | Instillation, nasogastric tube | \n Instillation, nasogastric tube \r\n\n |
| 3 | OGT | Instillation, orogastric tube | \n Instillation, orogastric tube \r\n\n |
| 3 | BLADINSTL | Instillation, urinary catheter | \n Instillation, urinary catheter \r\n\n |
| 3 | CAPDINSTL | Instillation, continuous ambulatory peritoneal dialysis port | \n Instillation, continuous ambulatory peritoneal dialysis port \r\n\n |
| 3 | CTINSTL | Instillation, chest tube | \n Instillation, chest tube \r\n\n |
| 3 | ETINSTL | Instillation, endotracheal tube | \n Instillation, endotracheal tube \r\n\n |
| 3 | GJT | Instillation, gastro-jejunostomy tube | \n Instillation, gastro-jejunostomy tube \r\n\n |
| 3 | IBRONCHINSTIL | Instillation, intrabronchial | \n Instillation, intrabronchial \r\n\n |
| 3 | IDUODINSTIL | Instillation, intraduodenal | \n Instillation, intraduodenal \r\n\n |
| 3 | IESOPHINSTIL | Instillation, intraesophageal | \n Instillation, intraesophageal \r\n\n |
| 3 | IGASTINSTIL | Instillation, intragastric | \n Instillation, intragastric \r\n\n |
| 3 | IILEALINJ | Instillation, intraileal | \n Instillation, intraileal \r\n\n |
| 3 | IOINSTL | Instillation, intraocular | \n Instillation, intraocular \r\n\n |
| 3 | ISININSTIL | Instillation, intrasinal | \n Instillation, intrasinal \r\n\n |
| 3 | ITRACHINSTIL | Instillation, intratracheal | \n Instillation, intratracheal \r\n\n |
| 3 | IUINSTL | Instillation, intrauterine | \n Instillation, intrauterine \r\n\n |
| 3 | JJTINSTL | Instillation, jejunostomy tube | \n Instillation, jejunostomy tube \r\n\n |
| 3 | LARYNGINSTIL | Instillation, laryngeal | \n Instillation, laryngeal \r\n\n |
| 3 | NASALINSTIL | Instillation, nasal | \n Instillation, nasal \r\n\n |
| 3 | NASOGASINSTIL | Instillation, nasogastric | \n Instillation, nasogastric \r\n\n |
| 3 | NTT | Instillation, nasotracheal tube | \n Instillation, nasotracheal tube \r\n\n |
| 3 | OJJ | Instillation, orojejunum tube | \n Instillation, orojejunum tube \r\n\n |
| 3 | OT | Instillation, otic | \n Instillation, otic \r\n\n |
| 3 | PDPINSTL | Instillation, peritoneal dialysis port | \n Instillation, peritoneal dialysis port \r\n\n |
| 3 | PNSINSTL | Instillation, paranasal sinuses | \n Instillation, paranasal sinuses \r\n\n |
| 3 | RECINSTL | Instillation, rectal | \n Instillation, rectal \r\n\n |
| 4 | RECTINSTL | Instillation, rectal tube | \n Instillation, rectal tube \r\n\n |
| 3 | SININSTIL | Instillation, sinus, unspecified | \n Instillation, sinus, unspecified \r\n\n |
| 3 | SOFTISINSTIL | Instillation, soft tissue | \n Instillation, soft tissue \r\n\n |
| 3 | TRACHINSTL | Instillation, tracheostomy | \n Instillation, tracheostomy \r\n\n |
| 3 | TRTYMPINSTIL | Instillation, transtympanic | \n Instillation, transtympanic \r\n\n |
| 3 | URETHINSTL | instillation, urethral | \n Instillation, urethral \r\n\n |
| 2 | (_IontophoresisRoute) Abstract | \n Iontophoresis \r\n\n | |
| 3 | IONTO | Topical application, iontophoresis | \n Topical application, iontophoresis \r\n\n |
| 2 | (_Irrigation) Abstract | \n Irrigation \r\n\n | |
| 3 | GUIRR | Irrigation, genitourinary | \n Irrigation, genitourinary \r\n\n |
| 3 | IGASTIRR | Irrigation, intragastric | \n Irrigation, intragastric \r\n\n |
| 3 | ILESIRR | Irrigation, intralesional | \n Irrigation, intralesional \r\n\n |
| 3 | IOIRR | Irrigation, intraocular | \n Irrigation, intraocular \r\n\n |
| 3 | BLADIRR | Irrigation, urinary bladder | \n Irrigation, urinary bladder \r\n\n |
| 4 | BLADIRRC | Irrigation, urinary bladder, continuous | \n Irrigation, urinary bladder, continuous \r\n\n |
| 4 | BLADIRRT | Irrigation, urinary bladder, tidal | \n Irrigation, urinary bladder, tidal \r\n\n |
| 3 | RECIRR | Irrigation, rectal | \n Irrigation, rectal \r\n\n |
| 2 | (_LavageRoute) Abstract | \n Lavage \r\n\n | |
| 3 | IGASTLAV | Lavage, intragastric | \n Lavage, intragastric \r\n\n |
| 2 | (_MucosalAbsorptionRoute) Abstract | \n Mucosal absorption \r\n\n | |
| 3 | IDOUDMAB | Mucosal absorption, intraduodenal | \n Mucosal absorption, intraduodenal \r\n\n |
| 3 | ITRACHMAB | Mucosal absorption, intratracheal | \n Mucosal absorption, intratracheal \r\n\n |
| 3 | SMUCMAB | Mucosal absorption, submucosal | \n Mucosal absorption, submucosal \r\n\n |
| 2 | (_Nebulization) Abstract | \n Nebulization \r\n\n | |
| 3 | ETNEB | Nebulization, endotracheal tube | \n Nebulization, endotracheal tube \r\n\n |
| 2 | (_Rinse) Abstract | \n Rinse \r\n\n | |
| 3 | DENRINSE | Rinse, dental | \n Rinse, dental \r\n\n |
| 3 | ORRINSE | Rinse, oral | \n Rinse, oral \r\n\n |
| 2 | (_SuppositoryRoute) Abstract | \n Suppository \r\n\n | |
| 3 | URETHSUP | Suppository, urethral | \n Suppository, urethral \r\n\n |
| 2 | (_Swish) Abstract | \n Swish \r\n\n | |
| 3 | SWISHSPIT | Swish and spit out, oromucosal | \n Swish and spit out, oromucosal \r\n\n |
| 3 | SWISHSWAL | Swish and swallow, oromucosal | \n Swish and swallow, oromucosal \r\n\n |
| 2 | (_TopicalAbsorptionRoute) Abstract | \n Topical absorption \r\n\n | |
| 3 | TTYMPTABSORP | Topical absorption, transtympanic | \n Topical absorption, transtympanic \r\n\n |
| 2 | (_TopicalApplication) Abstract | \n Topical application \r\n\n | |
| 3 | DRESS | Topical application, soaked dressing | \n Topical application, soaked dressing \r\n\n |
| 3 | IONTO | ||
| 3 | SWAB | Topical application, swab | \n Topical application, swab \r\n\n |
| 3 | TOPICAL | Topical | \n Topical \r\n\n |
| 3 | BUC | Topical application, buccal | \n Topical application, buccal \r\n\n |
| 3 | CERV | Topical application, cervical | \n Topical application, cervical \r\n\n |
| 3 | DEN | Topical application, dental | \n Topical application, dental \r\n\n |
| 3 | GIN | Topical application, gingival | \n Topical application, gingival \r\n\n |
| 3 | HAIR | Topical application, hair | \n Topical application, hair \r\n\n |
| 3 | ICORNTA | Topical application, intracorneal | \n Topical application, intracorneal \r\n\n |
| 3 | ICORONTA | Topical application, intracoronal (dental) | \n Topical application, intracoronal (dental) \r\n\n |
| 3 | IESOPHTA | Topical application, intraesophageal | \n Topical application, intraesophageal \r\n\n |
| 3 | IILEALTA | Topical application, intraileal | \n Topical application, intraileal \r\n\n |
| 3 | ILTOP | Topical application, intralesional | \n Topical application, intralesional \r\n\n |
| 3 | ILUMTA | Topical application, intraluminal | \n Topical application, intraluminal \r\n\n |
| 3 | IOTOP | Topical application, intraocular | \n Topical application, intraocular \r\n\n |
| 3 | LARYNGTA | Topical application, laryngeal | \n Topical application, laryngeal \r\n\n |
| 3 | MUC | Topical application, mucous membrane | \n Topical application, mucous membrane \r\n\n |
| 3 | NAIL | Topical application, nail | \n Topical application, nail \r\n\n |
| 3 | NASAL | Topical application, nasal | \n Topical application, nasal \r\n\n |
| 3 | OPTHALTA | Topical application, ophthalmic | \n Topical application, ophthalmic \r\n\n |
| 3 | ORALTA | Topical application, oral | \n Topical application, oral \r\n\n |
| 3 | ORMUC | Topical application, oromucosal | \n Topical application, oromucosal \r\n\n |
| 3 | OROPHARTA | Topical application, oropharyngeal | \n Topical application, oropharyngeal \r\n\n |
| 3 | PERIANAL | Topical application, perianal | \n Topical application, perianal \r\n\n |
| 3 | PERINEAL | Topical application, perineal | \n Topical application, perineal \r\n\n |
| 3 | PDONTTA | Topical application, periodontal | \n Topical application, periodontal \r\n\n |
| 3 | RECTAL | Topical application, rectal | \n Topical application, rectal \r\n\n |
| 3 | SCALP | Topical application, scalp | \n Topical application, scalp \r\n\n |
| 3 | OCDRESTA | Occlusive dressing technique | \n Occlusive dressing technique \r\n\n |
| 3 | SKIN | Topical application, skin | \n Topical application, skin \r\n\n |
| 3 | SUBCONJTA | Subconjunctival | \n Subconjunctival \r\n\n |
| 3 | TMUCTA | Topical application, transmucosal | \n Topical application, transmucosal \r\n\n |
| 3 | VAGINS | Topical application, vaginal | \n Insertion, vaginal \r\n\n |
| 2 | INSUF | Insufflation | \n Insufflation \r\n\n |
| 2 | TRNSDERM | Transdermal | \n Transdermal \r\n\n |
| 3 | TRNSDERMD | ||
| 1 | (_RouteBySite) Abstract | \n Route of substance administration classified by site. \r\n\n | |
| 2 | TRNSDERM | ||
| 2 | (_AmnioticFluidSacRoute) Abstract | \n Amniotic fluid sac \r\n\n | |
| 3 | AMNINJ | ||
| 2 | (_BiliaryRoute) Abstract | \n Biliary tract \r\n\n | |
| 3 | BILINJ | ||
| 3 | CHOLINJ | ||
| 2 | (_BodySurfaceRoute) Abstract | \n Body surface \r\n\n | |
| 3 | DRESS | ||
| 3 | ELECTOSMOS | ||
| 3 | IONTO | ||
| 3 | SOAK | ||
| 3 | SWAB | ||
| 3 | TOPICAL | ||
| 2 | (_BuccalMucosaRoute) Abstract | \n Buccal mucosa \r\n\n | |
| 3 | BUC | ||
| 2 | (_CecostomyRoute) Abstract | \n Cecostomy \r\n\n | |
| 3 | CECINSTL | ||
| 2 | (_CervicalRoute) Abstract | \n Cervix of the uterus \r\n\n | |
| 3 | CERV | ||
| 3 | CERVINJ | ||
| 3 | CERVINS | ||
| 3 | DEN | ||
| 3 | DENRINSE | ||
| 2 | (_EndocervicalRoute) Abstract | \n Endocervical \r\n\n | |
| 3 | AMNINJ | ||
| 3 | BILINJ | ||
| 2 | (_EnteralRoute) Abstract | \n Enteral \r\n\n | |
| 3 | EFT | ||
| 3 | ENTINSTL | ||
| 2 | (_EpiduralRoute) Abstract | \n Epidural \r\n\n | |
| 3 | EPI | ||
| 3 | EPIDURINJ | ||
| 3 | EPIINJ | ||
| 3 | EPINJSP | ||
| 2 | (_ExtraAmnioticRoute) Abstract | \n Extra-amniotic \r\n\n | |
| 3 | EXTRAMNINJ | ||
| 2 | (_ExtracorporealCirculationRoute) Abstract | \n Extracorporeal circulation \r\n\n | |
| 3 | EXTCORPDIF | ||
| 3 | EXTCORPINJ | ||
| 2 | (_GastricRoute) Abstract | \n Gastric \r\n\n | |
| 3 | GBINJ | ||
| 3 | GT | ||
| 3 | NGT | ||
| 3 | OGT | ||
| 2 | (_GenitourinaryRoute) Abstract | \n Genitourinary \r\n\n | |
| 3 | GUIRR | ||
| 2 | (_GingivalRoute) Abstract | \n Gingival \r\n\n | |
| 3 | GIN | ||
| 3 | GINGINJ | ||
| 2 | (_HairRoute) Abstract | \n Hair \r\n\n | |
| 3 | HAIR | ||
| 3 | SHAMPOO | ||
| 2 | (_InterameningealRoute) Abstract | \n Interameningeal \r\n\n | |
| 3 | INTERMENINJ | ||
| 2 | (_InterstitialRoute) Abstract | \n Interstitial \r\n\n | |
| 3 | INTERSTITINJ | ||
| 2 | (_IntraabdominalRoute) Abstract | \n Intra-abdominal \r\n\n | |
| 3 | IABDINJ | ||
| 2 | (_IntraarterialRoute) Abstract | \n Intra-arterial \r\n\n | |
| 3 | IA | ||
| 3 | IAINJ | ||
| 2 | (_IntraarticularRoute) Abstract | \n Intraarticular \r\n\n | |
| 3 | IARTINJ | ||
| 2 | (_IntrabronchialRoute) Abstract | \n Intrabronchial \r\n\n | |
| 3 | IBRONCHINSTIL | ||
| 2 | (_IntrabursalRoute) Abstract | \n Intrabursal \r\n\n | |
| 3 | IBURSINJ | ||
| 2 | (_IntracardiacRoute) Abstract | \n Intracardiac \r\n\n | |
| 3 | IC | ||
| 3 | ICARDINJ | ||
| 2 | (_IntracartilaginousRoute) Abstract | \n Intracartilaginous \r\n\n | |
| 3 | ICARTINJ | ||
| 2 | (_IntracaudalRoute) Abstract | \n Intracaudal \r\n\n | |
| 3 | ICAUDINJ | ||
| 2 | (_IntracavernosalRoute) Abstract | \n Intracavernosal \r\n\n | |
| 3 | ICAVINJ | ||
| 2 | (_IntracavitaryRoute) Abstract | \n Intracavitary \r\n\n | |
| 3 | ICAVITINJ | ||
| 2 | (_IntracerebralRoute) Abstract | \n Intracerebral \r\n\n | |
| 3 | ICEREBINJ | ||
| 2 | (_IntracervicalRoute) Abstract | \n Intracervical \r\n\n | |
| 3 | IUINJC | ||
| 2 | (_IntracisternalRoute) Abstract | \n Intracisternal \r\n\n | |
| 3 | ICISTERNINJ | ||
| 2 | (_IntracornealRoute) Abstract | \n Intracorneal \r\n\n | |
| 3 | ICORNTA | ||
| 2 | (_IntracoronalRoute) Abstract | \n Intracoronal (dental) \r\n\n | |
| 3 | ICORONTA | ||
| 2 | (_IntracoronaryRoute) Abstract | \n Intracoronary \r\n\n | |
| 3 | ICOR | ||
| 3 | ICORONINJ | ||
| 2 | (_IntracorpusCavernosumRoute) Abstract | \n Intracorpus cavernosum \r\n\n | |
| 3 | ICORPCAVINJ | ||
| 2 | (_IntradermalRoute) Abstract | \n Intradermal \r\n\n | |
| 3 | IDIMPLNT | ||
| 3 | IDINJ | ||
| 2 | (_IntradiscalRoute) Abstract | \n Intradiscal \r\n\n | |
| 3 | IDISCINJ | ||
| 2 | (_IntraductalRoute) Abstract | \n Intraductal \r\n\n | |
| 3 | IDUCTINJ | ||
| 2 | (_IntraduodenalRoute) Abstract | \n Intraduodenal \r\n\n | |
| 3 | IDUODINSTIL | ||
| 3 | IDOUDMAB | ||
| 2 | (_IntraduralRoute) Abstract | \n Intradural \r\n\n | |
| 3 | IDURINJ | ||
| 2 | (_IntraepidermalRoute) Abstract | \n Intraepidermal \r\n\n | |
| 3 | IEPIDINJ | ||
| 2 | (_IntraepithelialRoute) Abstract | \n Intraepithelial \r\n\n | |
| 3 | IEPITHINJ | ||
| 2 | (_IntraesophagealRoute) Abstract | \n Intraesophageal \r\n\n | |
| 3 | IESOPHINSTIL | ||
| 3 | IESOPHTA | ||
| 2 | (_IntragastricRoute) Abstract | \n Intragastric \r\n\n | |
| 3 | IGASTINSTIL | ||
| 3 | IGASTIRR | ||
| 3 | IGASTLAV | ||
| 2 | (_IntrailealRoute) Abstract | \n Intraileal \r\n\n | |
| 3 | IILEALINJ | ||
| 3 | IILEALTA | ||
| 2 | (_IntralesionalRoute) Abstract | \n Intralesional \r\n\n | |
| 3 | ILESINJ | ||
| 3 | ILESIRR | ||
| 3 | ILTOP | ||
| 2 | (_IntraluminalRoute) Abstract | \n Intraluminal \r\n\n | |
| 3 | ILUMINJ | ||
| 3 | ILUMTA | ||
| 2 | (_IntralymphaticRoute) Abstract | \n Intralymphatic \r\n\n | |
| 3 | ILYMPJINJ | ||
| 2 | (_IntramedullaryRoute) Abstract | \n Intramedullary \r\n\n | |
| 3 | IMEDULINJ | ||
| 2 | (_IntramuscularRoute) Abstract | \n Intramuscular \r\n\n | |
| 3 | IM | ||
| 2 | (_IntraocularRoute) Abstract | \n Intraocular \r\n\n | |
| 3 | IOINJ | ||
| 3 | IOSURGINS | ||
| 3 | IOINSTL | ||
| 3 | IOIRR | ||
| 3 | IOTOP | ||
| 2 | (_IntraosseousRoute) Abstract | \n Intraosseous \r\n\n | |
| 3 | IOSSC | ||
| 3 | IOSSINJ | ||
| 2 | (_IntraovarianRoute) Abstract | \n Intraovarian \r\n\n | |
| 3 | IOVARINJ | ||
| 2 | (_IntrapericardialRoute) Abstract | \n Intrapericardial \r\n\n | |
| 3 | IPCARDINJ | ||
| 2 | (_IntraperitonealRoute) Abstract | \n Intraperitoneal \r\n\n | |
| 3 | IPERINJ | ||
| 3 | PDPINJ | ||
| 3 | CAPDINSTL | ||
| 3 | PDPINSTL | ||
| 2 | (_IntrapleuralRoute) Abstract | \n Intrapleural \r\n\n | |
| 3 | IPLRINJ | ||
| 3 | CTINSTL | ||
| 2 | (_IntraprostaticRoute) Abstract | \n Intraprostatic \r\n\n | |
| 3 | IPROSTINJ | ||
| 2 | (_IntrapulmonaryRoute) Abstract | \n Intrapulmonary \r\n\n | |
| 3 | EXTCORPINJ | ||
| 3 | IPINJ | ||
| 2 | (_IntrasinalRoute) Abstract | \n Intrasinal \r\n\n | |
| 3 | ISININSTIL | ||
| 2 | (_IntraspinalRoute) Abstract | \n Intraspinal \r\n\n | |
| 3 | ISINJ | ||
| 2 | (_IntrasternalRoute) Abstract | \n Intrasternal \r\n\n | |
| 3 | ISTERINJ | ||
| 2 | (_IntrasynovialRoute) Abstract | \n Intrasynovial \r\n\n | |
| 3 | ISYNINJ | ||
| 2 | (_IntratendinousRoute) Abstract | \n Intratendinous \r\n\n | |
| 3 | ITENDINJ | ||
| 2 | (_IntratesticularRoute) Abstract | \n Intratesticular \r\n\n | |
| 3 | ITESTINJ | ||
| 2 | (_IntrathecalRoute) Abstract | \n Intrathecal \r\n\n | |
| 3 | IT | ||
| 3 | ITINJ | ||
| 2 | (_IntrathoracicRoute) Abstract | \n Intrathoracic \r\n\n | |
| 3 | ITHORINJ | ||
| 2 | (_IntratrachealRoute) Abstract | \n Intratracheal \r\n\n | |
| 3 | ITRACHINSTIL | ||
| 3 | ITRACHMAB | ||
| 2 | (_IntratubularRoute) Abstract | \n Intratubular \r\n\n | |
| 3 | ITUBINJ | ||
| 2 | (_IntratumorRoute) Abstract | \n Intratumor \r\n\n | |
| 3 | ITUMINJ | ||
| 2 | (_IntratympanicRoute) Abstract | \n Intratympanic \r\n\n | |
| 3 | ITYMPINJ | ||
| 2 | (_IntrauterineRoute) Abstract | \n Intrauterine \r\n\n | |
| 3 | IUINJ | ||
| 3 | IURETINJ | ||
| 3 | IU | ||
| 3 | IUINSTL | ||
| 2 | (_IntravascularRoute) Abstract | \n Intravascular \r\n\n | |
| 3 | HEMODIFF | ||
| 3 | IVASCINFUS | ||
| 3 | HEMOPORT | ||
| 3 | IVASCINJ | ||
| 2 | (_IntravenousRoute) Abstract | \n Intravenous \r\n\n | |
| 3 | IVFLUSH | ||
| 3 | IVINJ | ||
| 2 | (_IntraventricularRoute) Abstract | \n Intraventricular \r\n\n | |
| 3 | IVENTINJ | ||
| 2 | (_IntravesicleRoute) Abstract | \n Intravesicle \r\n\n | |
| 3 | IVESINJ | ||
| 2 | (_IntravitrealRoute) Abstract | \n Intravitreal \r\n\n | |
| 3 | IVITINJ | ||
| 2 | (_JejunumRoute) Abstract | \n Jejunum \r\n\n | |
| 3 | GJT | ||
| 3 | JJTINSTL | ||
| 3 | OJJ | ||
| 2 | (_LacrimalPunctaRoute) Abstract | \n Lacrimal puncta \r\n\n | |
| 3 | LPINS | ||
| 2 | (_LaryngealRoute) Abstract | \n Laryngeal \r\n\n | |
| 3 | LARYNGINSTIL | ||
| 3 | LARYNGTA | ||
| 2 | (_LingualRoute) Abstract | \n Lingual \r\n\n | |
| 3 | TRNSLING | ||
| 2 | (_MucousMembraneRoute) Abstract | \n Mucous membrane \r\n\n | |
| 3 | MUC | ||
| 2 | (_NailRoute) Abstract | \n Nail \r\n\n | |
| 3 | NAIL | ||
| 2 | (_NasalRoute) Abstract | \n Nasal \r\n\n | |
| 3 | NASINHL | ||
| 3 | NASALINSTIL | ||
| 3 | NASOGASINSTIL | ||
| 3 | NASAL | ||
| 2 | (_OphthalmicRoute) Abstract | \n Ophthalmic \r\n\n | |
| 3 | OPTHALTA | ||
| 2 | (_OralRoute) Abstract | \n Oral \r\n\n | |
| 3 | CHEW | ||
| 3 | DISSOLVE | ||
| 3 | IPINHL | ||
| 3 | ORALTA | ||
| 3 | ORRINSE | ||
| 3 | PO | ||
| 2 | (_OromucosalRoute) Abstract | \n Oromucosal \r\n\n | |
| 3 | GARGLE | ||
| 3 | ORMUC | ||
| 3 | SUCK | ||
| 3 | SWISHSPIT | ||
| 3 | SWISHSWAL | ||
| 2 | (_OropharyngealRoute) Abstract | \n Oropharyngeal \r\n\n | |
| 3 | OROPHARTA | ||
| 2 | (_OticRoute) Abstract | \n Otic \r\n\n | |
| 3 | OT | ||
| 2 | (_ParanasalSinusesRoute) Abstract | \n Paranasal sinuses \r\n\n | |
| 3 | PNSINJ | ||
| 3 | PNSINSTL | ||
| 2 | (_ParenteralRoute) Abstract | \n Parenteral \r\n\n | |
| 3 | PARENTINJ | ||
| 2 | (_PerianalRoute) Abstract | \n Perianal \r\n\n | |
| 3 | PERIANAL | ||
| 2 | (_PeriarticularRoute) Abstract | \n Periarticular \r\n\n | |
| 3 | PAINJ | ||
| 2 | (_PeriduralRoute) Abstract | \n Peridural \r\n\n | |
| 3 | PDURINJ | ||
| 2 | (_PerinealRoute) Abstract | \n Perineal \r\n\n | |
| 3 | PERINEAL | ||
| 2 | (_PerineuralRoute) Abstract | \n Perineural \r\n\n | |
| 3 | PNINJ | ||
| 2 | (_PeriodontalRoute) Abstract | \n Periodontal \r\n\n | |
| 3 | PDONTINJ | ||
| 3 | PDONTTA | ||
| 2 | (_PulmonaryRoute) Abstract | \n Pulmonary \r\n\n | |
| 3 | IPPB | ||
| 3 | VENT | ||
| 3 | VENTMASK | ||
| 3 | ETINSTL | ||
| 3 | NTT | ||
| 3 | ETNEB | ||
| 2 | (_RectalRoute) Abstract | \n Rectal \r\n\n | |
| 3 | ENEMA | ||
| 3 | RETENEMA | ||
| 3 | PR | ||
| 3 | RECINSTL | ||
| 3 | RECIRR | ||
| 3 | RECTAL | ||
| 2 | (_RespiratoryTractRoute) Abstract | \n Respiratory tract \r\n\n | |
| 3 | IPINHL | ||
| 2 | (_RetrobulbarRoute) Abstract | \n Retrobulbar \r\n\n | |
| 3 | RBINJ | ||
| 2 | (_ScalpRoute) Abstract | \n Scalp \r\n\n | |
| 3 | SCALP | ||
| 2 | (_SinusUnspecifiedRoute) Abstract | \n Sinus, unspecified \r\n\n | |
| 3 | ENDOSININJ | ||
| 3 | SININSTIL | ||
| 2 | (_SkinRoute) Abstract | \n Skin \r\n\n | |
| 3 | OCDRESTA | ||
| 3 | SKIN | ||
| 2 | (_SoftTissueRoute) Abstract | \n Soft tissue \r\n\n | |
| 3 | SOFTISINJ | ||
| 3 | SOFTISINSTIL | ||
| 2 | (_SubarachnoidRoute) Abstract | \n Subarachnoid \r\n\n | |
| 3 | SUBARACHINJ | ||
| 2 | (_SubconjunctivalRoute) Abstract | \n Subconjunctival \r\n\n | |
| 3 | SCINJ | ||
| 3 | SUBCONJTA | ||
| 2 | (_SubcutaneousRoute) Abstract | \n Subcutaneous \r\n\n | |
| 3 | SQIMPLNT | ||
| 3 | SQINFUS | ||
| 3 | IPUMPINJ | ||
| 3 | SQ | ||
| 3 | SQSURGINS | ||
| 2 | (_SublesionalRoute) Abstract | \n Sublesional \r\n\n | |
| 3 | SLESINJ | ||
| 2 | (_SublingualRoute) Abstract | \n Sublingual \r\n\n | |
| 3 | SL | ||
| 2 | (_SubmucosalRoute) Abstract | \n Submucosal \r\n\n | |
| 3 | SUBMUCINJ | ||
| 3 | SMUCMAB | ||
| 2 | (_TracheostomyRoute) Abstract | \n Tracheostomy \r\n\n | |
| 3 | TRACH | ||
| 3 | TRACHINSTL | ||
| 2 | (_TransmucosalRoute) Abstract | \n Transmucosal \r\n\n | |
| 3 | TMUCTA | ||
| 2 | (_TransplacentalRoute) Abstract | \n Transplacental \r\n\n | |
| 3 | TRPLACINJ | ||
| 2 | (_TranstrachealRoute) Abstract | \n Transtracheal \r\n\n | |
| 3 | TRTRACHINJ | ||
| 2 | (_TranstympanicRoute) Abstract | \n Transtympanic \r\n\n | |
| 3 | TRTYMPINSTIL | ||
| 3 | TTYMPTABSORP | ||
| 2 | (_UreteralRoute) Abstract | \n Ureteral \r\n\n | |
| 3 | URETINJ | ||
| 2 | (_UrethralRoute) Abstract | \n Urethral \r\n\n | |
| 3 | URETHINJ | ||
| 3 | URETHINS | ||
| 3 | URETHINSTL | ||
| 3 | URETHSUP | ||
| 2 | (_UrinaryBladderRoute) Abstract | \n Urinary bladder \r\n\n | |
| 3 | BLADINJ | ||
| 3 | BLADIRR | ||
| 2 | (_UrinaryTractRoute) Abstract | \n Urinary tract \r\n\n | |
| 3 | BLADINSTL | ||
| 2 | (_VaginalRoute) Abstract | \n Vaginal \r\n\n | |
| 3 | DOUCHE | ||
| 3 | VAGINSI | ||
| 3 | VAGINS | ||
| 2 | (_VitreousHumourRoute) Abstract | \n Vitreous humour \r\n\n | |
| 3 | IVITIMPLNT |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | ART | act relationship type | \n \n Description: A directed association between a source Act and a target Act. \r\n\n \n Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute) \r\n\n |
| 2 | (_ActClassTemporallyPertains) Abstract | ||
| 2 | (_ActRelationshipAccounting) Abstract | \n Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. \r\n\n | |
| 3 | (_ActRelationshipCostTracking) Abstract | \n Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. \r\n\n | |
| 4 | CHRG | has charge | \n A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service. \r\n\n The financial transaction will define the charge (bill) for delivery or performance of the service. \r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. \r\n\n |
| 4 | COST | has cost | \n A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service. \r\n\n The financial transaction will define the cost of delivery or performance of the service. \r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. \r\n\n |
| 3 | (_ActRelationshipPosting) Abstract | \n Expresses values for describing the relationship between a FinancialTransaction and an Account. \r\n\n | |
| 4 | CREDIT | has credit | \n A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance. \r\n\n |
| 4 | DEBIT | has debit | \n A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance. \r\n\n |
| 2 | (_ActRelationshipConditional) Abstract | \n Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred \r\n\n | |
| 3 | CIND | has contra-indication | \n A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used. \r\n\n |
| 3 | PRCN | has pre-condition | \n A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable. \r\n\n |
| 3 | RSON | has reason | \n \n Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication. \r\n\n \n Discussion: In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship. \r\n\n |
| 4 | BLOCK | blocks | \n \n Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring. \r\n\n |
| 4 | DIAG | diagnoses | \n \n Description: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 4 | IMM | immunization against | \n \n Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease) \r\n\n |
| 5 | ACTIMM | active immunization against | \n \n Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease) \r\n\n |
| 5 | PASSIMM | passive immunization against | \n \n Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease). \r\n\n |
| 4 | MITGT | mitigates | \n The source act removes or lessens the occurrence or effect of the target act. \r\n\n |
| 5 | RCVY | recovers | \n \n Definition: The source act is performed to recover from the effects of the target act. \r\n\n |
| 4 | PRYLX | prophylaxis of | \n \n Description: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 4 | TREAT | treats | \n \n Description: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 5 | ADJUNCT | adjunctive treatment | \n \n Description: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified. \r\n\n |
| 5 | MTREAT | maintenance treatment | \n \n Description: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n |
| 5 | PALLTREAT | palliates | \n \n Description: The source act is intended to provide palliation for the effects of the target act. \r\n\n |
| 5 | SYMP | symptomatic relief | \n \n Description: The source act is intented to provide symptomatic relief for the effects of the target act. \r\n\n |
| 3 | TRIG | has trigger | \n A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified. \r\n\n \n Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded. \r\n\n |
| 2 | (_ActRelationshipTemporallyPertains) Abstract | \n Abstract collector for ActRelationhsip types that relate two acts by their timing. \r\n\n | |
| 3 | (_ActRelationshipTemporallyPertainsApproximates) Abstract | \n Abstract collector for ActRelationship types that relate two acts by their approximate timing. \r\n\n | |
| 4 | ENE | ends near end | \n A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is ENS \r\n\n |
| 5 | ECW | ends concurrent with | \n A relationship in which the source act's effective time ends with the end of the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 6 | CONCURRENT | concurrent with | \n A relationship in which the source act's effective time is the same as the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 6 | SBSECWE | starts before start of, ends with | \n The source Act starts before the start of the target Act, and ends with the target Act. \r\n\n \n UsageNote: Inverse code is SASECWE\n \r\n\n |
| 4 | ENS | ends near start | \n A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is ENE \r\n\n |
| 5 | ECWS | ends concurrent with start of | \n The source Act ends when the target act starts (i.e. if we say "ActOne ECWS ActTwo", it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SCWE\n \r\n\n |
| 4 | SNE | starts near end | \n A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is SNS \r\n\n |
| 5 | SCWE | starts concurrent with end of | \n The source Act starts when the target act ends (i.e. if we say "ActOne SCWE ActTwo", it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SBSECWS\n \r\n\n |
| 4 | SNS | starts near start | \n A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is SNE \r\n\n |
| 5 | SCW | starts concurrent with | \n A relationship in which the source act's effective time starts with the start of the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 6 | CONCURRENT | ||
| 6 | SCWSEBE | starts with. ends before end of | \n The source Act starts with.the target Act and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SCWSEAE\n \r\n\n |
| 6 | SCWSEAE | starts with, ends after end of | The source Act starts with the target Act, and ends after the end of the target Act. |
| 3 | EAS | ends after start of | \n A relationship in which the source act ends after the target act starts. \r\n\n \n UsageNote: Inverse code is SBE\n \r\n\n |
| 4 | EAE | ends after end of | \n A relationship in which the source act ends after the target act ends. \r\n\n \n UsageNote: Inverse code is EBE\n \r\n\n |
| 5 | SASEAE | starts after start of, ends after end of | \n The source Act starts after start of the target Act and ends after end of the target Act. \r\n\n \n UsageNote: Inverse code is SBSEBE\n \r\n\n |
| 6 | SBEEAE | contains end of | \n The source Act contains the end of the target Act. \r\n\n \n UsageNote: Inverse code is EDU\n \r\n\n |
| 7 | SASSBEEAS | start after start of, contains end of | \n The source Act start after the start of the target Act, and contains the end of the target Act. \r\n\n \n UsageNote: Inverse code is SBSEASEBE\n \r\n\n |
| 7 | SBSEAE | contains time of | \n The source Act contains the time of the target Act. \r\n\n \n UsageNote: Inverse code is DURING\n \r\n\n |
| 7 | SCWSEAE | ||
| 6 | SASSBEEAS | ||
| 4 | SAS | starts after start of | \n The source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SBS\n \r\n\n |
| 5 | SASEAE | ||
| 5 | SAE | starts after end of | \n A relationship in which the source act starts after the target act ends. \r\n\n \n UsageNote: Inverse code is EBS\n \r\n\n |
| 5 | DURING | occurs during | \n A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBSEAE\n \r\n\n |
| 5 | SASECWE | starts after start of, ends with | \n The source Act starts after start of the target Act, and ends with the target Act. \r\n\n \n UsageNote: Inverse code is SBSECWE\n \r\n\n |
| 3 | EASORECWS | ends after or concurrent with start of | \n A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EBSORECWS \r\n\n |
| 4 | EAS | ||
| 4 | EAEORECW | ends after or concurrent with end of | \n A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EBEORECW \r\n\n |
| 5 | EAE | ||
| 5 | ECW | ||
| 4 | ECWS | ||
| 3 | INDEPENDENT | independent of time of | \n The source Act is independent of the time of the target Act. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 3 | SAEORSCWE | starts after or concurrent with end of | \n A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SBEORSCWE \r\n\n |
| 4 | SCWE | ||
| 4 | SAE | ||
| 3 | SASORSCW | starts after or concurrent with start of | \n A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SBSORSCW \r\n\n |
| 4 | SAS | ||
| 4 | SCW | ||
| 3 | SBEORSCWE | starts before or concurrent with end of | \n A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SAEORSCWE \r\n\n |
| 4 | OVERLAP | overlaps with | \n A relationship in which the source act's effective time overlaps the target act's effective time in any way. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n |
| 5 | ECW | ||
| 5 | EDU | ends during | \n A relationship in which the source act ends within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBEEAE\n \r\n\n |
| 6 | SBSEASEBE | contains start of, ends before end of | \n The source Act contains the start of the target Act, and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SASSBEEAS\n \r\n\n |
| 6 | SCWSEBE | ||
| 5 | SBEEAE | ||
| 5 | SBSEAS | contains start of | \n The source Act contains the start of the target Act. \r\n\n \n UsageNote: Inverse code is SDU\n \r\n\n |
| 6 | SBSECWE | ||
| 6 | SBSEASEBE | ||
| 6 | SBSEAE | ||
| 5 | SCW | ||
| 5 | SCWE | ||
| 5 | SDU | starts during | \n A relationship in which the source act starts within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBSEAS\n \r\n\n |
| 6 | SASSBEEAS | ||
| 4 | SBE | starts before end of | The source Act starts before the end of the target Act (i.e. if we say "ActOne SBE ActTwo", it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is EAS\n \r\n\n |
| 5 | EBE | ends before end of | The source Act ends before the end of the target Act (i.e. if we say "ActOne EBE ActTwo", it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is EAE\n \r\n\n |
| 6 | SBSEBE | starts before start of, ends before end of | \n The source Act starts before the start of the target Act, and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SASEAE\n \r\n\n |
| 7 | SBSEASEBE | ||
| 7 | EBSORECWS | ends before or concurrent with start of | \n A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EASORECWS \r\n\n |
| 8 | ECWS | ||
| 8 | EBS | ends before start of | \n A relationship in which the source act ends before the target act starts. \r\n\n \n UsageNote: Inverse code is SAE\n \r\n\n |
| 5 | SBSEASEBE | ||
| 5 | SCWSEBE | ||
| 5 | EBEORECW | ends before or concurrent with end of | \n A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EAEORECW \r\n\n |
| 6 | ECW | ||
| 6 | EBE | ||
| 5 | SBSORSCW | starts before or concurrent with start of | \n A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is SASORSCW \r\n\n |
| 6 | SCW | ||
| 6 | SBS | starts before start of | \n A relationship in which the source act begins before the target act begins. \r\n\n \n UsageNote: Inverse code is SAS\n \r\n\n |
| 7 | SBSEBE | ||
| 7 | SBSEAS | ||
| 2 | AUTH | authorized by | \n A relationship in which the target act authorizes or certifies the source act. \r\n\n |
| 2 | CAUS | is etiology for | \n \n Description: An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act. \r\n\n \n Examples:\n \r\n\n \n a growth of Staphylococcus aureus may be considered the cause of an abscess\n contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced\n lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed\n \n |
| 2 | COMP | has component | \n The target act is a component of the source act, with no semantics regarding composition or aggregation implied. \r\n\n |
| 3 | CTRLV | has control variable | \n A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation. \r\n\n |
| 3 | MBR | has member | \n The target Acts are aggregated by the source Act. Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source. \r\n\n \n UsageNotes: This explicitly represents the conventional notion of aggregation. The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts). \r\n\n It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST\n \r\n\n |
| 4 | STEP | has step | \n A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently. \r\n\n \n UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode. \r\n\n \n OpenIssue: Need Additional guidelines on when each approach should be used. \r\n\n |
| 5 | ARR | arrival | \n The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act. \r\n\n |
| 5 | DEP | departure | \n The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act. \r\n\n |
| 3 | PART | has part | \n The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act. \r\n\n \n UsageNote: In UML 1.1, this is a "composition" defined as: \n "A form of aggregation with strong ownership and coincident lifetime as part of the whole. Parts with non-fixed multiplicity may be created after the composite itself, but once created they live and die with it (i.e., they share lifetimes). Such parts can also be explicitly removed before the death of the composite. Composition may be recursive."\n \r\n\n |
| 2 | COVBY | covered by | \n A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy. \r\n\n |
| 2 | DRIV | is derived from | \n Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts. \r\n\n |
| 2 | ELNK | episodeLink | \n Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter. \r\n\n |
| 2 | EVID | provides evidence for | \n Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc. \r\n\n \n Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies. \r\n\n |
| 2 | EXACBY | exacerbated by | \n \n Description:The source act is aggravated by the target act. (Example "chest pain" EXACBY "exercise") \r\n\n |
| 2 | EXPL | has explanation | \n This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition. \r\n\n |
| 2 | INTF | interfered by | \n the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act. \r\n\n \n UsageNote: This provides the semantics to document barriers to care \r\n\n |
| 2 | ITEMSLOC | items located | \n Items located \r\n\n |
| 2 | LIMIT | limited by | \n A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood. \r\n\n |
| 2 | META | has metadata | \n \n Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act. \r\n\n \n Constraint: Source act must have either a mood code that is not "EVN" (event) or its "isCriterion" attribute must set to "true". Target act must be an Act with a mood code of EVN and with isCriterionInd attribute set to "true". \r\n\n |
| 2 | MFST | is manifestation of | \n An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation. \r\n\n |
| 2 | NAME | assigns name | \n Used to assign a "name" to a condition thread. Source is a condition node, target can be any service. \r\n\n |
| 2 | OUTC | has outcome | \n An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called "post-conditional".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment. \r\n\n |
| 3 | (_ActRelationsipObjective) Abstract | \n The target act is a desired outcome of the source act. Source is any act (typically an intervention). Target must be an observation in criterion mood. \r\n\n | |
| 4 | OBJC | has continuing objective | \n A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood. \r\n\n |
| 4 | OBJF | has final objective | \n A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood. \r\n\n |
| 3 | GOAL | has goal | \n A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood. \r\n\n |
| 3 | RISK | has risk | \n A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed. \r\n\n |
| 2 | PERT | has pertinent information | \n This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays. \r\n\n |
| 2 | PREV | has previous instance | \n A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services. \r\n\n |
| 2 | REFR | refers to | \n A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee. \r\n\n |
| 3 | USE | uses | \n Indicates that the source act makes use of (or will make use of) the information content of the target act. \r\n\n \n UsageNotes: A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate. \r\n\n \n Rationale: There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference. \r\n\n |
| 2 | REFV | has reference values | \n Reference ranges are essentially descriptors of a class of result values assumed to be "normal", "abnormal", or "critical." Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results. \r\n\n |
| 2 | RELVBY | relieved by | \n \n Description:The source act is wholly or partially alleviated by the target act. (Example "chest pain" RELVBY "sublingual nitroglycerin administration") \r\n\n |
| 2 | SEQL | is sequel | \n An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation. \r\n\n |
| 3 | APND | is appendage | \n An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered. \r\n\n |
| 3 | BSLN | has baseline | \n Indicates that the target observation(s) provide an initial reference for the source observation or observation group. \r\n\n \n UsageConstraints: Both source and target must be Observations or specializations thereof. \r\n\n |
| 3 | COMPLY | complies with | \n \n Description:The source act complies with, adheres to, conforms to, or is permissible under (in whole or in part) the policy, contract, agreement, law, conformance criteria, certification guidelines or requirement conveyed by the target act. \r\n\n Examples for compliance relationships are: audits of adherence with a security policy, certificate of conformance to system certification requirements, or consent directive in compliance with or permissible under a privacy policy. \r\n\n |
| 3 | DOC | documents | \n The source act documents the target act. \r\n\n |
| 3 | FLFS | fulfills | \n The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act. \r\n\n |
| 4 | OCCR | occurrence | \n The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the "completion track" but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa). \r\n\n |
| 4 | OREF | references order | \n Relates either an appointment request or an appointment to the order for the service being scheduled. \r\n\n |
| 4 | SCH | schedules request | \n Associates a specific time (and associated resources) with a scheduling request or other intent. \r\n\n |
| 3 | GEN | has generalization | \n The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic). \r\n\n |
| 3 | GEVL | evaluates (goal) | \n A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a "goal distance" (e.g., goal to observation) can be "calculated" and need not be sent explicitly. \r\n\n |
| 3 | INST | instantiates (master) | \n Used to capture the link between a potential service ("master" or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master's defaults. \r\n\n |
| 3 | MOD | modifies | \n Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target). \r\n\n \n Usage:The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead. \r\n\n Name from source to target = "modifiesPrior" \r\n\n Name from target to source = "modifiesByNew" \r\n\n |
| 3 | MTCH | matches (trigger) | \n A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is "observation of pain" and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger. \r\n\n |
| 3 | OPTN | has option | \n A relationship between a source Act that provides more detailed properties to the target Act. \r\n\n The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements. \r\n\n The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements. \r\n\n Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. \r\n\n |
| 3 | RCHAL | re-challenge | \n \n Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated. \r\n\n |
| 3 | REV | reverses | \n A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. \r\n\n Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction. \r\n\n Constraints: the "completion track" mood of the target Act must be equally or more "actual" than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT. \r\n\n |
| 3 | RPLC | replaces | \n A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type. \r\n\n |
| 3 | SUCC | succeeds | \n \n Definition: A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act. \r\n\n |
| 3 | UPDT | updates (condition) | \n A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread. \r\n\n |
| 3 | XCRPT | Excerpts | \n The source is an excerpt from the target. \r\n\n |
| 4 | VRXCRPT | Excerpt verbatim | \n The source is a direct quote from the target. \r\n\n |
| 3 | XFRM | transformation | \n Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.) \r\n\n |
| 2 | SPRT | has support | \n Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post). \r\n\n |
| 3 | SPRTBND | has bounded support | \n A specialization of "has support" (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the "ST elevation" observation -- the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general "has support" relation is used. Likewise, if a ROI on an image defines the true bounds of a "1st degree burn", the relation "has bounded support" is used; but if the ROI only points to the approximate area of the burn, the general "has support" relation is used. \r\n\n |
| 2 | SUBJ | has subject | \n Relates an Act to its subject Act that the first Act is primarily concerned with. \r\n\n Examples \r\n\n \n \n The first Act may be a ControlAct manipulating the subject Act \r\n\n \n \n The first act is a region of interest (ROI) that defines a region within the subject Act. \r\n\n \n \n The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. \r\n\n \n \n Constraints \r\n\n An Act may have multiple subject acts. \r\n\n Rationale \r\n\n The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship. \r\n\n |
| 3 | QUALF | has qualifier | \n The target observation qualifies (refines) the semantics of the source observation. \r\n\n \n UsageNote: This is not intended to replace concept refinement and qualification via vocabulary. It is used when there are multiple components which together provide the complete understanding of the source Act. \r\n\n |
| 2 | SUMM | summarized by | \n An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period. \r\n\n |
| 2 | VALUE | has value | \n \n Description:Indicates that the target Act represents the result of the source observation Act. \r\n\n \n FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified \r\n\n \n UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute. For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation. \r\n\n The valueNegationInd attribute on the source Act has the same semantics of "negated finding" when it applies to the target of a VALUE ActRelationship as it does to the value attribute. On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding. Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd. \r\n\n \n OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation. \r\n\n |
| 1 | CURE | curative indication | |
| 1 | CURE.ADJ | adjunct curative indication | |
| 1 | MTGT.ADJ | adjunct mitigation | |
| 1 | RACT | ||
| 1 | SUGG |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | ESGN | Expressed signed | |
| 1 | ESP | Expressed spoken | |
| 1 | EWR | Expressed written | |
| 1 | RSGN | Received signed | |
| 1 | RSP | Received spoken | |
| 1 | RWR | Received written |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | NI | NoInformation | \n \n Description:The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value. \r\n\n |
| 2 | INV | invalid | \n \n Description:The value as represented in the instance is not a member of the set of permitted data values in the constrained value domain of a variable. \r\n\n |
| 3 | DER | derived | \n \n Description:An actual value may exist, but it must be derived from the provided information (usually an EXPR generic data type extension will be used to convey the derivation expressionexpression . \r\n\n |
| 3 | OTH | other | \n \n Description:The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). \r\n\n \n Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. \r\n\n With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. \r\n\n |
| 4 | NINF | negative infinity | \n Negative infinity of numbers. \r\n\n |
| 4 | PINF | positive infinity | \n Positive infinity of numbers. \r\n\n |
| 3 | UNC | un-encoded | \n \n Description: The actual value has not yet been encoded within the approved value domain. \r\n\n \n Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM. \r\n\n \n Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. \r\n\n Data type properties such as original text and translations may be present when this null flavor is included. \r\n\n |
| 2 | MSK | masked | \n There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information. \r\n\n Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail. \r\n\n |
| 2 | NA | not applicable | \n Known to have no proper value (e.g., last menstrual period for a male). \r\n\n |
| 2 | UNK | unknown | \n \n Description:A proper value is applicable, but not known. \r\n\n \n Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: \r\n\n \n Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown')\n Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)\n \n |
| 3 | ASKU | asked but unknown | \n Information was sought but not found (e.g., patient was asked but didn't know) \r\n\n |
| 4 | NAV | temporarily unavailable | \n Information is not available at this time but it is expected that it will be available later. \r\n\n |
| 3 | NASK | not asked | \n This information has not been sought (e.g., patient was not asked) \r\n\n |
| 3 | NAVU | Not available | \n Information is not available at this time (with no expectation regarding whether it will or will not be available in the future). \r\n\n |
| 4 | NAV | ||
| 3 | QS | Sufficient Quantity | \n \n Description:The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. e.g. 'Add 10mg of ingredient X, 50mg of ingredient Y, and sufficient quantity of water to 100mL.' The null flavor would be used to express the quantity of water. \r\n\n |
| 3 | TRC | trace | \n The content is greater than zero, but too small to be quantified. \r\n\n |
| 1 | NP | not present | \n Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default, or no-information (NI) as the default of all defaults. \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | E | Excellent | |
| 1 | F | Fair | |
| 1 | G | Good | |
| 1 | P | Poor |
Release Date: 2018-08-12
\r\n| Level | Code | Display | Definition |
| 1 | I | Intact | \n Reproductively intact \r\n\n |
| 1 | N | Neutered | \n Reproductively neutered \r\n\n |
Release Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\nRelease Date: 2018-08-12
\r\n