# Concepts

Code: I
Display: Reference
Definition:
This row represents a reference to a previously defined type. Such a reference means that, in a given message, the message element instance for the current row is identical to the message element instance that instantiates the referred row.


Code: N
Display: New type
Definition:
New type. This row starts the definition of a new message element type. The subordinate rows beneath it compose the definition of the type. Each of these subordinate rows has the name of the message element type being defined in the In Message Element Type column. That name will be the same one that is in the Of Message Element Type of this row.


Code: R
Display: Recursive
Definition:
This row represents the recursive reuse of the message element type within which is appears. See 10.3.3.3.


Code: assoc
Display: Association Row
Definition:
Identifies an association leading from the "class" (or association) that is most directly above this row


Code: class
Display: HMD root class
Definition:
Identifies "class" in the HMD. There is only one class entry in a Hierarchical Message Definition. This is the root class for the message.


Code: hmd
Display: HMD identifier
Definition:
Always the first row of the table, identifies the particular Hierarchical Message Definition in the nomenclature of the HL7 Repository.


Code: stc
Display: Subtype constraint
Definition:
This row corresponds to a subcomponent of the row above; it would not normally be included in an HMD, but it is included in order to be able to state a constraint on the subtype. This is explained in 10.2.2.4.


Code: rmim
Display: RMIM identifier
Definition:
Always the first row of the table, identifies the particular Refined Message Information Model in the nomenclature of the HL7 Repository


Code: stc
Display: Subtype constraint
Definition:
This row corresponds to a subcomponent of the row above; it would not normally be included in an Refined Message Information Model, but it is included in order to be able to state a constraint on the subtype. This is explained in 10.2.2.4.


Code: 0
Display: Message accepted
Definition:
Success. Optional, as in version 2.x the AA conveys success. Used for systems that must always return a status code.


Code: 103
Display: Table value not found
Definition:
The value received for a common HL7 or user defined table was not found to match allowable table values.


Code: 204
Display: Unknown key identifier
Definition:
The identifier for a patient, order, etc. was not found. Occurs for transactions other than additions.


Code: 205
Display: Duplicate key identifier
Definition:
The identifier for a patient, order, etc. already exists. Occurs in response to addition transactions (e.g. new Admit, new Order, etc.).


Code: H
Display: home address
Definition:
A communication address at a home, attempted contacts for business purposes might intrude privacy and chances are one will contact family or other household members instead of the person one wishes to call. Typically used with urgent cases, or if no other contacts are available.


Code: TMP
Display: temporary address
Definition:
A temporary address, may be good for visit or mailing. Note that an address history can provide more detailed information.


Code: DIR
Display: Direct
Definition:
Indicates a work place address or telecommunication address that reaches the individual or organization directly without intermediaries. For phones, often referred to as a 'private line'.


Code: PUB
Display: Public
Definition:
Indicates a work place address or telecommunication address that is a 'standard' address which may reach a reception service, mail-room, or other intermediary prior to the target entity.


Code: RD
Display: Records
Definition:
Used where number of records or instances of items in the query response result set has limitations.


Code: AS
Display: answering service
Definition:
An automated answering machine used for less urgent cases and if the main purpose of contact is to leave a message or access an automated announcement.


Code: EC
Display: emergency contact
Definition:
A contact specifically designated to be used for emergencies. This is the first choice in emergencies, independent of any other use codes.


Code: MC
Display: mobile contact
Definition:
A telecommunication device that moves and stays with its owner. May have characteristics of all other use codes, suitable for urgent matters, not the first choice for routine business.


Code: _Extensibility
Display: Extensibility
Definition:
The extensibility of coding determines whether or not extensions are allowed in the domain of a coded attribute.


Code: CWE
Display: Coded With Extensions
Definition:
The coded attribute allows local codes or user entered text to be sent when the concept that the user would like to express is not a member of the defined value set. If the concept that the user wants to express is represented by a code in the standard value set, the standard code must be sent. The local code can be sent in addition to the standard code if desired. Only if the concept that the user wants to express is NOT represented by a standard code, can a solitary local code be sent.


Code: _RealmOfUse
Display: RealmOfUse
Definition:
The jurisdiction or realm within which the domain will be used. A realm might be a country, a group of countries, a region of the world, or an organization.


Code: UV
Display: Universal
Definition:
The root or universal HL7 jurisdiction or realm from which all subsequent specializations are derived.


Code: att
Display: Clinical Attachments
Definition:
Clinical Attachments Workgroup (inactive since mid-2018; work subsumed by Structured Documents and Financial Management).  Retained for backwards-compatibility only.


Code: claims
Display: Payer/Provider Information Exchange Work Group
Definition:
Payer/Provider Information Exchange Work Group (http://www.hl7.org/Special/committees/claims/index.cfm)


Code: AcknowledgmentMessageType
Display: AcknowledgmentMessageType
Definition:
Identifies the the kind of information specified in the acknowledgement message. Options are: Error, Warning or Information.


Code: ActAppointmentType
Display: ActAppointmentType
Definition:
**Description:** Types of acts that can be scheduled.

**Examples:**

 *  Follow-up appointment
 *  New referral appointment
 *  Consultation appointment
 *  Specimen Collection appointment
 *  Procedure appointment


Code: ActClassExposure
Display: ActClassExposure
Definition:
**Description:**The interaction of entities whereupon a subject entity is brought into proximity to a physical, chemical or biological agent. This includes intended exposure (e.g. administering a drug product) as well as accidental or environmental exposure. (Note: This class deals only with proximity and not the effectiveness of the exposure, i.e. not all exposed will suffer actual harm or benefit.)

**Examples:**Exposure to radiation, drug administration, inhalation of peanut aerosol or viral particles.


Code: ImagingSubjectOrientation
Display: ImagingSubjectOrientation
Definition:
A code specifying qualitatively the spatial relation between imaged object and imaging film or detector.


Code: SubjectBodyPosition
Display: SubjectBodyPosition
Definition:
Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc. ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted.


Code: ActCode
Display: ActCode
Definition:
The table that provides the detailed or rich codes for the Act classes.

*Open Issue:* The hierarchy has issues and several of the existing domains may be moved under this new one; this must be examined and a proposal to clean up the hierarncy in the near future is needed

*Open Issue:* The description of this domain seems odd and may be a leftover from long ago and needs improvement.


Code: ActAccountType
Display: ActAccountType
Definition:
**Description:** Types of representation groupings of financial transactions that are tracked and reported together with a single balance.

*Examples:* 

 *  Patient billing accounts
 *  Cost center
 *  Cash


Code: ActAdjudicationType
Display: ActAdjudicationType
Definition:
**Description:** Types of 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.

*Examples:* 

 *  adjudicated with adjustments
 *  adjudicated as refused
 *  adjudicated as submitted


Code: ActAdjudicationInformationCode
Display: ActAdjudicationInformationCode
Definition:
Explanatory codes that provide information derived by an Adjudicator during the course of adjudicating an Invoice. Codes from this domain are purely information and do not materially affect the adjudicated Invoice. That is, codes do not impact or explain financial adjustments to an Invoice.

A companion domain (ActAdjudicationReason) includes information reasons which have a financial impact on an Invoice (claim).

Example adjudication information code is 54540 - Patient has reached Plan Maximum for current year.

Codes from this domain further rationalizes ActAdjudicationCodes (e.g. AA - Adjudicated with Adjustment), which are used to describe the process of adjudicating an Invoice.


Code: ActCareProvisionRequestType
Display: ActCareProvisionRequestType
Definition:
**Description:**Concepts identifying different types of referral requests. These concepts identify the general type of care or category of services requested. They are not used to represent the indication or diagnosis which triggered the need for the referral. E.g. Anger management service, Intensive Care service, Orthodontics service.


Code: ActCredentialedCareProvisionProgramCode
Display: ActCredentialedCareProvisionProgramCode
Definition:
**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.


Code: ActEncounterType
Display: ActEncounterType
Definition:
Concepts representing types of patient encounter such as ambulatory encounter, inpatient encounter or emergency encounter.


Code: ActEncounterInpatientType
Display: ActEncounterInpatientType
Definition:
**Definition:**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.


Code: ActEncounterCode
Display: ActEncounterCode
Definition:
Concepts representing types of patient encounter such as ambulatory encounter, inpatient encounter or emergency encounter.  Note that this code is a synonym of ActEncounterType, and follows the original naming conventions for v3 Concept Domains, and is as published in the CDA R2 base; the naming conventions were corrected in later revisions of V3, but is kept here for backwards compatibility for the CDA R2 base.


Code: ActCodeProcessStep
Display: ActCodeProcessStep
Definition:
**Description:** Codes for general process steps.

**Examples:**

 *  lab process steps
 *  diagnostic imaging process steps
 *  etc. *(Missing third example)*


Code: ActObservationVerificationCode
Display: ActObservationVerificationCode
Definition:
The act of verifying an observations. The subject act related to the observation verification (act relationship SUBJ) must be an observation (OBS)


Code: ActSpecimenLabelCode
Display: ActSpecimenLabelCode
Definition:
The act of printing a specimen label. The printing of a label for a specimen container is a significant act in the workflow for collecting specimens.


Code: ActSpecimenManifestCode
Display: ActSpecimenManifestCode
Definition:
The act of adding a specimen to a transportation manifest. For example a laboratory will pack together in a carton all the specimens to be shipped to a reference lab. An electronic manifest showing all the specimens in the shippment is communicated to the reference lab.


Code: LabResultReportingProcessStepCode
Display: LabResultReportingProcessStepCode
Definition:
**Definition:**Used to identify if a lab result is reported as preliminary, final, or corrected. Provides a consistent way to distinguish the business or reporting status of the lab result.


Code: ActCognitiveProfessionalServiceCode
Display: ActCognitiveProfessionalServiceCode
Definition:
Denotes the specific service that has been performed. This is obtained from the professional service catalog pertaining to the discipline of the health service provider. Professional services are generally cognitive in nature and exclude surgical procedures. E.g. Provided training, Provided drug therapy review, Gave smoking-cessation counseling, etc.


Code: ActFinancialParticipationConsentType
Display: ActFinancialParticipationConsentType
Definition:
**Description:**The type of financial participation consent directive.

**Examples:** The Advanced Beneficiary Notice that Medicare patients consent or dissent to prior to receiving health services in the U.S. \\ Current values include consent to financial responsibility (1) if the service is not deemed medically necessary; (2) will self pay for a service; or (3) requests that payer be billed.


Code: ActInformationAccessCode
Display: ActInformationAccessCode
Definition:
**Description:** The type of health information to which the subject of the information or the subject&\#039;s delegate consents or dissents.

**Examples:**

 *  allergy information
 *  medication information
 *  professional services information


Code: AdvanceBeneficiaryNoticeType
Display: AdvanceBeneficiaryNoticeType
Definition:
**Description:**

Represents types of consent that patient must sign prior to receipt of service, which is required for billing purposes.

**Examples:**

 *  Advanced beneficiary medically necessity notice.
 *  Advanced beneficiary agreement to pay notice.
 *  Advanced beneficiary requests payer billed.


Code: ActContractType
Display: ActContractType
Definition:
An agreement of obligation between two or more parties that is subject to contractual law and enforcement.

*Examples:* approvals granted by a regulatory agency; contracts measured in financial terms; insurance coverage contracts.


Code: ActFinancialContractType
Display: ActFinancialContractType
Definition:
A type of Act representing a contract whose value is measured in monetary terms.

**Examples:**

 *  insurance policy
 *  providercontract
 *  billing arrangement


Code: ActCoveredPartyLimitCode
Display: ActCoveredPartyLimitCode
Definition:
Codes representing the types of covered parties that may receive covered benefits under a policy or program.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActCoveragePartyLimitGroupCode
Display: ActCoveragePartyLimitGroupCode
Definition:
Codes representing the level of coverage provided under the policy or program in terms of the types of entities that may play covered parties based on their personal relationships or employment status.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActInsurancePolicyType
Display: ActInsurancePolicyType
Definition:
**Description:** Types of insurance coverage legal documentation to cover healthcare costs.

*Examples:* 

 *  Automobile
 *  Extended healthcare
 *  Worker's compensation


Code: ActFinancialTransactionType
Display: ActFinancialTransactionType
Definition:
A type of Act representing any transaction between two accounts whose value is measured in monetary terms.

**Examples:**

 *  patient account transaction
 *  encounter accounttransaction
 *  cost center transaction


Code: ActBillingArrangementType
Display: ActBillingArrangementType
Definition:
**Description:** Types of provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider for one or more occurrence or over a specified period.

*Examples:* 

 *  Contract
 *  Rostering
 *  Capitation


Code: ActDataOperationType
Display: ActDataOperationType
Definition:
**Description:** Types of operations that may be performed on objects. Here, objects are broadly understood as information system-related entities (e.g., devices, files, records, tables, processes, programs, domains) containing or receiving information.

**Examples:**

 *  Create
 *  Update
 *  Delete

*Open Issue:* This is too restrictive to deal with what CBCC wants.


Code: ActDataAccessOperationType
Display: ActDataAccessOperationType
Definition:
**Description:** Types of operations that may accomplish access of information. Here, objects are broadly understood as information system-related entities (e.g., devices, files, records, tables, processes, programs, domains) containing or receiving information.

**Examples:**

 *  Query
 *  Search
 *  Transport
 *  Send
 *  Receive


Code: ActDataCollectionOperationType
Display: ActDataCollectionOperationType
Definition:
**Description:** Types of operations that may accomplish collection or related management of information. Here, objects are broadly understood as information system-related entities (e.g., devices, files, records, tables, processes, programs, domains) containing or receiving information.

**Examples:**

 *  Create
 *  Store
 *  Archive


Code: ActDataDisclosureOperationType
Display: ActDataDisclosureOperationType
Definition:
**Description:** Types of operations that may accomplish disclosure of information. Here, objects are broadly understood as information system-related entities (e.g., devices, files, records, tables, processes, programs, domains) containing or receiving information.

**Examples:**

 *  Disclose
 *  Forward
 *  Publish


Code: ActDataUseOperationType
Display: ActDataUseOperationType
Definition:
**Description:** Types of operations that may accomplish usage of information. Here, objects are broadly understood as information system-related entities (e.g., devices, files, records, tables, processes, programs, domains) containing or receiving information.

**Examples:**

 *  Activate
 *  Release
 *  Execute Read
 *  Display
 *  Update
 *  Append
 *  Amend


Code: ActDetectedIssueManagementType
Display: ActDetectedIssueManagementType
Definition:
**Description:** Issue management types that dealing with detected issue observations.

*Rationale:* Allows for consistent specification and interpretation of issue management.


Code: ActDisciplinaryActionCode
Display: ActDisciplinaryActionCode
Definition:
Includes coded types of actions that can be taken by a supervising entity in response to inappropriate action (or inaction) on the part of a supervised entity.


Code: ActEventCategoryWorkingListType
Display: ActEventCategoryWorkingListType
Definition:
**Description:** List of broad catagorizations of clinical event records.

**Examples:**

 *  Allergies
 *  Drugs
 *  Referrals


Code: ActCommonCodedClinicalObservationCategoryListType
Display: ActCommonCodedClinicalObservationCategoryListType
Definition:
**Description:**Lists of high-level categorizations for clinical coded observations that do not require numeric values with a specific unit of measure.

**Examples:**

 *  Symptoms
 *  History
 *  Observations


Code: ActSimpleMeasurableClinicalObservationCategoryListType
Display: ActSimpleMeasurableClinicalObservationCategoryListType
Definition:
**Description:** of high-level categorization for clinical non-laboratory and non-diagnostic image measured observations with numeric values and specific units of measure.

**Examples:**

 *  Vital Signs
 *  Physiological Measurements
 *  Procedure Results


Code: ActEventCriteriaType
Display: ActEventCriteriaType
Definition:
**Description:** Describes types of criteria used when making observations, conducting procedures, and substance administrations.

**Examples:**

 *  medications
 *  immunizations


Code: ActProcedureEventCriteriaType
Display: ActProcedureEventCriteriaType
Definition:
**Description:** of procedure used for evaluating a precondition, goal, or trigger.

**Examples:**

 *  some radiology procedures
 *  respiratory therapy
 *  physical therapy


Code: ActSubstanceAdministrationEventCriteriaType
Display: ActSubstanceAdministrationEventCriteriaType
Definition:
**Description:** Type of substance administration used for evaluating a precondition, goal, or trigger.

**Examples:**

 *  other substance administrations
 *  respiratory therapy
 *  immunizations


Code: ObservationEventCriteriaType
Display: ObservationEventCriteriaType
Definition:
**Description:** of observation used for evaluating a precondition, goal, or trigger.

**Examples:**

 *  age-based criteria
 *  diagnostic-based criteria
 *  simple observation-based criteria (vital signs)


Code: ObservationEventLabCriteriaType
Display: ObservationEventLabCriteriaType
Definition:
**Description:** Type of observation used in lab for evaluating reference ranges.

**Examples:**

 *  age-based criteria
 *  sex-based criteria
 *  condition-based criteria


Code: ActPatientSafetyIncidentCode
Display: ActPatientSafetyIncidentCode
Definition:
**Definition:** A code specifying the particular kind of Patient Safety Incident that the Incident class instance represents.

**Examples:**"Medication incident", "slips, trips and falls incident".The actual value set for the domain will be determined by each (realm) implementation, whose Patient Safety terminology will be specific, although probably linked to the WHO Patient Safety Taxonomy that is currently under development

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActInvoiceDetailClinicalServiceCode
Display: ActInvoiceDetailClinicalServiceCode
Definition:
An identifying data string for healthcare procedures.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: CPT4
Display: CPT4
Definition:
**Description:**Physicians Current Procedural Terminology (CPT) Manual is a listing of descriptive terms and identifying codes for reporting medical services and procedures performed by physicians. Available for the AMA at the address listed for CPT above. These codes are found in Appendix A of CPT 2000 Standard Edition. (CPT 2000 Standard Edition, American Medical Association, Chicago, IL).

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: HCPCS
Display: HCPCS
Definition:
**Description:**Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes are procedure identifying codes. HCPCS is Health Care Finance AdministrationaTMs (HFCA) coding scheme to group procedures performed for payment to providers. contains codes for medical equipment, injectable drugs, transportation services, and other services not found in CPT4.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ICD10PCS
Display: ICD10PCS
Definition:
**Description:**International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS) are procedure identifying codes. ICD-10-PCS describes the classification of inpatient procedures for statistical purposes.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ICD9PCS
Display: ICD9PCS
Definition:
**Description:**International Classification of Diseases, 9th Revision, Procedure Coding System (ICD-9-PCS) are procedure identifying codes. ICD-9-PCS describes the classification of inpatient procedures for statistical purposes.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActInvoiceDetailTaxType
Display: ActInvoiceDetailTaxType
Definition:
**Description:** Types of tax associated with billable services or products.

*Examples:* 

 *  Provincial or State sales tax
 *  Harmonized sales tax
 *  Federal sales tax


Code: HCPCSAccommodationCode
Display: HCPCSAccommodationCode
Definition:
**Description:**External value set for accommodation types used in the U.S. Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) including modifiers.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActInvoiceElementSummaryType
Display: ActInvoiceElementSummaryType
Definition:
**Description:** 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.

*Examples:* 

 *  number and total value of payable items;
 *  number and value of same period nullify items;
 *  number and value of prior nullify;
 *  number of non-payable nullify items;
 *  number of pending items;
 *  number of rejected items;
 *  number of adjudicated to zero items;
 *  reimbursement items (e.g., pay patient)
 *  Adjudicated non-payee payable prior-period electronic amount
 *  Adjudicated nullified prior-period electronic amount
 *  Adjudicated refused prior-period electronic amount


Code: ActInvoiceAdjudicationPaymentSummaryType
Display: ActInvoiceAdjudicationPaymentSummaryType
Definition:
**Description:** Types of 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.


Code: ActInvoiceGroupType
Display: ActInvoiceGroupType
Definition:
**Description:** Types 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 its immediate children invoice elements.

*Examples:* 

 *  CPINV - Clinical product invoice
 *  CSINV- Clinical service invoice
 *  RXDINV - Drug invoice
 *  RXCINV - Compound invoice
 *  CSPINV - Combined service and clinical product invoice


Code: ActInvoiceOverrideType
Display: ActInvoiceOverrideType
Definition:
**Description:** Types of 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.

*Examples:* 

 *  Re-bill for the professional fee
 *  Good faith override
 *  Wasted Drug


Code: ActProcedureCategoryList
Display: ActProcedureCategoryList
Definition:
**Description:**Describes the high level classification of professional services for grouping.

**Examples:**Education, Counseling, Surgery, etc.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActMedicationTherapyDurationWorkingListCode
Display: ActMedicationTherapyDurationWorkingListCode
Definition:
**Definition:**A collection of concepts that identifies different types of 'duration-based' mediation working lists.

**Examples:**"Continuous/Chronic" "Short-Term" and "As Needed"


Code: ActMonitoringProtocolType
Display: ActMonitoringProtocolType
Definition:
**Description:** Identifies types of monitoring programs such as tracking specified medication prescribing e.g. narcotic(s), identifying investigational studies or identifying programs regarding reimbursement or prescribing privileges.


Code: ActPrivacyPolicyType
Display: ActPrivacyPolicyType
Definition:
**Description:**Types of privacy policies that further specify the ActClassPolicy value set e.g. override policy, minor's rights to mask sensitive information policy, opt-in, opt-out policy.


Code: ActConsentDirectiveType
Display: ActConsentDirectiveType
Definition:
**Description:**Specifies the type of consent directive indicated by an ActClassPolicy e.g., a 3rd party authorization to disclose or consent for a substitute decision maker (SDM) or a notice of privacy policy. Sibling to ActPrivacyPolicyType and Child of ActPolicyType.


Code: ActSensitivityPrivacyPolicyType
Display: ActSensitivityPrivacyPolicyType
Definition:
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.


Code: ActEntityInformationSensitivityPrivacyPolicyType
Display: ActEntityInformationSensitivityPrivacyPolicyType
Definition:
**Description:** Types of Sensitivity policies that may apply to a sensitive attribute on an Entity.


Code: ActObligationSecurityPolicyType
Display: ActObligationSecurityPolicyType
Definition:
Conveys the mandated workflow action that an information custodian, receiver, or user must perform.

*Usage Note:* 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.


Code: ActRefrainSecurityPolicyType
Display: ActRefrainSecurityPolicyType
Definition:
Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances.

*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.


Code: ActTrustPolicyType
Display: ActTrustPolicyType
Definition:
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.

Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability).

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\]

For example, identity proofing level of assurance and Trust Framework.


Code: ActPreferenceType
Display: ActPreferenceType
Definition:
Concepts representing a type of preference that can be specified.

**Examples:** 

 *  Food
 *  Drug
 *  Vegetarian
 *  Sweets


Code: ActProcedureCode
Display: ActProcedureCode
Definition:
**Description:** An identifying code for healthcare interventions/procedures.

**Examples:**

 *  immunization
 *  appendectomy
 *  physiotherapy


Code: ActBillableServiceCode
Display: ActBillableServiceCode
Definition:
**Definition:** An identifying code for billable services, as opposed to codes for similar services used to identify them for functional purposes.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActBillableTreatmentPlanCode
Display: ActBillableTreatmentPlanCode
Definition:
*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActMedicalBillableServiceCode
Display: ActMedicalBillableServiceCode
Definition:
**Definition:** An identifying code for billable medical services, as opposed to codes for similar services to identify them for clinical purposes.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActNonMedicalBillableServiceCode
Display: ActNonMedicalBillableServiceCode
Definition:
**Definition:** An identifying code for billable services that are not medical procedures, such as social services or governmental program services.

**Example:** Building a wheelchair ramp, help with groceries, giving someone a ride, etc.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActMolecularInteractionType
Display: ActMolecularInteractionType
Definition:
Chemical reactions in the widest sense of the word.

*Examples:* Transcription (creating mRNA from a DNA gene), translation (creating a protein from mRNA), cleavage (hydrolysis of a peptide), substitution (replacing an element or residue with another, such as in glycosylation, phosphorylation), addition (adding a residue to a double bond), receptor binding.


Code: ActOralHealthProcedureCode
Display: ActOralHealthProcedureCode
Definition:
**Description:**An identifying code for oral health interventions/procedures.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActOrderableProcedureCode
Display: ActOrderableProcedureCode
Definition:
**Description:** Concept domain which includes those ActProcedureCodes which are appropriate for ordering.

**Examples:**

 *  physical therapies
 *  excisions
 *  surgery


Code: ActProductReconstitutionType
Display: ActProductReconstitutionType
Definition:
DESCRIPTION

Identifies the nature (or type) of transformation that a (medicinal) product may undergo, prior to its administration to a patient.

**Examples:**

 *  Dilution
 *  Dissolution
 *  Suspension


Code: ActProfessionalServiceCode
Display: ActProfessionalServiceCode
Definition:
**Description:** Denotes the specific professional service that has been performed. This is obtained from the professional service catalog pertaining to the discipline of the health service provider.

**Examples:**

 *  adjustment of hearing aid
 *  excision of skin lesion
 *  stitching skin lacerations


Code: ActSpecimenCollectionProcedureType
Display: ActSpecimenCollectionProcedureType
Definition:
**Description:** Used to further classify the type of specimen collection procedure being documented.

**Examples:**

 *  Venipuncture
 *  Swab
 *  Biopsy


Code: ActSubstanceAdministrationCode
Display: ActSubstanceAdministrationCode
Definition:
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.


Code: ActSubstanceAdministrationImmunizationCode
Display: ActSubstanceAdministrationImmunizationCode
Definition:
The introduction of ??? with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents.


Code: SubstanceAdministrationActCode
Display: SubstanceAdministrationActCode
Definition:
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.  Note that this code is a synonym of ActSubstanceAdministrationCode, and follows the original naming conventions for v3 Concept Domains, and is as published in the CDA R2 base; the naming conventions were corrected in later revisions of V3, but is kept here for backwards compatibility for the CDA R2 base.


Code: ActSubstanceDerivationType
Display: ActSubstanceDerivationType
Definition:
Acts of producing a substance by processing input material in any way thus deriving the product substance from the inputs

*Examples:* Fermentation, filtration, separation, extraction, or any complex procedure involving multiple such steps.

*UsageNotes:* This domain may involve molecular interactions as components, but substance derivation - even if implementing a single defined reaction on the molecular level - implies not only that reaction but the methods and devices by which to induce that reaction.


Code: ActSubstanceExtractionCode
Display: ActSubstanceExtractionCode
Definition:
**Description:** In addition to the class code, further defines the type of substance extraction.

**Examples:**

 *  excision
 *  surgical
 *  passive


Code: ActBloodDonationType
Display: ActBloodDonationType
Definition:
**Description:** Defines the type of blood donation.

**Examples:**

 *  autologous
 *  directed
 *  volunteer


Code: NutritionModificationType
Display: NutritionModificationType
Definition:
Concepts that are used to convey modifications to the food or serving utensils that should be given in a diet order. These can be derived from patient allergies, intolerances, or preferences. They can also be specific to the order and not have any relationship to the allergies, intolerances, or preferences.

**Examples:** 

 *  Vegetarian
 *  Liquids separate from solids
 *  Small Portions
 *  disposable utensils (for psych or isolation rooms)


Code: DietTextureModificationType
Display: DietTextureModificationType
Definition:
A set of concepts that identifies any texture modifications that should be made to a diet order.

**Examples:** 

 *  Pudding Thick
 *  Pureed
 *  Easy to Chew


Code: ActProductApprovalType
Display: ActProductApprovalType
Definition:
**Description:** An approval granted to a product by a regulatory agency or other government body.

**Examples:**

 *  Approval to sell
 *  Approval to initiate clinical trial
 *  Approval to market (i.e., advertise)


Code: ActProductApprovalApplicationType
Display: ActProductApprovalApplicationType
Definition:
**Description:** A type of application made in order to obtain a product approval from a regulatory agency or other government body.

**Examples:**

 *  Application for new approval
 *  Application for renewal of approval
 *  Application for variation of approval


Code: ActProductApprovalProcessType
Display: ActProductApprovalProcessType
Definition:
**Description:** A type of approval process by which a product approval is obtained from a regulatory agency or other government body.

**Examples:**

 *  Centralized process approval
 *  Mutual recognition process approval
 *  National process approval


Code: ActReactionActionTakenType
Display: ActReactionActionTakenType
Definition:
**Description:** A type of act that indicates the action taken by a practitioner or other responsible party in response to the reaction/event that is reported in the ICSR.

**Examples:**

 *  failing device replaced
 *  medication stopped
 *  medication dose adjusted


Code: ActRecordOrganizerType
Display: ActRecordOrganizerType
Definition:
**Description:** A code further classifying the type of record organizer. Used with the ActClassRecordOrganizer ActClass concept domain.

**Examples:**

 *  CDA R2
 *  
 *  Electrolytes Battery
 *  Specimen Cluster


Code: ActCompositionType
Display: ActCompositionType
Definition:
A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians.

*Examples:* document; authentication unit; transmission unit.


Code: ActContextOfUseType
Display: ActContextOfUseType
Definition:
Identifies the heading under which a document is to appear in a pre-defined, pro forma table of contents for a collection of documents within a regulatory category.

**Examples:**

 *  m1-1-forms (eCTD module 1, forms)
 *  m1-1-1-fda-form-1571 (eCTD. Module 1, specific FDA form)
 *  m3-2-s-drug-substance (eCTD module 3, section 2, drug substance by substance)

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActKeywordsType
Display: ActKeywordsType
Definition:
Codes for additional metadata to be assigned to document or context of use instances to organize a group of documents within the same table of contents heading. These external code systems specify the category or type of keyword (e.g. Species) and the applicable values.

**Examples:**

 *  Species code system
 *  Species code
 *  Sponsor's manufacturing site code system

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActRegulatoryCategoryType
Display: ActRegulatoryCategoryType
Definition:
Identifies the regulatory processes and/or submission contents specified in law or practice for a particular realm used to organize submitted materials.

**Examples:**

 *  Application Type: NDA
 *  Submission Type: Efficacy Supplement
 *  Submission Unit Type: Amendment

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActFinancialSupportingAttachmentCode
Display: ActFinancialSupportingAttachmentCode
Definition:
**Description:**Identifies the type of document that was attached to support the processing of claims, adjudication decision determination or extensions to coverage.


Code: ActClaimAttachmentCode
Display: ActClaimAttachmentCode
Definition:
**Description:**Contrains the type of attachment (document, XRAY, bit map image, etc.) included to support a healthcare claim. Vocabulary bound to this domain should be a specification for the type of document (i.e. WCB First Report of Acccident - Form 8).


Code: ActSpecialAuthorizationAttachmentCode
Display: ActSpecialAuthorizationAttachmentCode
Definition:
**Description:**Identifies the type of document that is used to support a request which requires special authorization. Example values in this concept domain could be: coverage extensions, step therapy, medical report, lab result, etc.


Code: ActICSRDocumentType
Display: ActICSRDocumentType
Definition:
**Description:** A type of document that has information related to the investigation of an adverse event or product problem report.

**Examples:**

 *  Autopsy report
 *  toxicology report
 *  clinical journal article


Code: ActIdentityDocumentCode
Display: ActIdentityDocumentCode
Definition:
Code identifying the type of identification document (e.g. passport, drivers license)

**Implementation Note:**The proposal called for a domain, but a code was also provided. When codes are available for the value set the code IDENTDOC (identity document) will be used as the headcode for the specializable value set.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActInformRequestType
Display: ActInformRequestType
Definition:
**Description:** Information type for which a provider is requesting routing of health information. This could include messaging of results or documents especially in the context of a specific service delivery location.

**Examples:**

 *  Diagnostic Image Interpretations
 *  Lab Test Results
 *  Electrocardiogram Reports


Code: ActMedicationDocumentCode
Display: ActMedicationDocumentCode
Definition:
Indicates the types of documents that can be associated with a medication or group of medications.

*Examples include:* Patient monographs, Provider monographs, Drug protocols, etc.


Code: ActProductDocumentationType
Display: ActProductDocumentationType
Definition:
**Description:** 

A type of documentation that is used to convey information about a product or an aspect of its life as a product - ranging from production to disposition.

**Examples:**

 *  Bill of lading
 *  product label
 *  Report of Product Disposal


Code: ActRPSDocumentType
Display: ActRPSDocumentType
Definition:
Identifies the document type from a regulator-defined set of codes similar to the ICH-defined File Tags used on clinical study documents in an eCTD.

**Examples:**

 *  Pre-clinical study report
 *  Study report
 *  Sample CRF

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActSpecialAuthorizationCode
Display: ActSpecialAuthorizationCode
Definition:
**Description:**Constrains vocabulary to that which describes the type of documents that can be attached to a financial transaction such as a Special Authorization Request.

Example values under this concept domain could be: drug, device, service, etc.


Code: ActGrouperType
Display: ActGrouperType
Definition:
**Description:** Further defines the type of grouping of orders or events. This concept domain is intended to be used with the GROUPER Act class code.

**Examples:**

 *  requisition
 *  pre-coordinated order set
 *  custom order set


Code: ActICSRRecordOrganizerType
Display: ActICSRRecordOrganizerType
Definition:
**Description:** A type of concept that is used within adverse event and product problem reporting to organize data - often clinical in nature - provided for an investigative subject or other party within the scope of the investigation.

**Examples:**

 *  Medical history
 *  previous drug reactions
 *  immunization history


Code: ActRecordContainerType
Display: ActRecordContainerType
Definition:
**Description:** Container of clinical statements. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or "container tree".

*Examples:*  category; document section; document body.


Code: ActRegistryCode
Display: ActRegistryCode
Definition:
This is the domain of registry types. Examples include Master Patient Registry, Staff Registry, Employee Registry, Tumor Registry.


Code: ActRPSRegulatoryPolicy
Display: ActRPSRegulatoryPolicy
Definition:
Identifies different classes of regulatory policy that can be applied within a Regulated Product Submission.

*Usage Note:* This Domain is used to administratively group its subdomains specifically for usage in the RPS model, and is not intended to participate in any binidngs.


Code: ActRegulatoryStatusType
Display: ActRegulatoryStatusType
Definition:
Identifies a temporary or final legal status assigned to a submission by a particular regulatory realm based on the laws and practices of the realm.

**Examples:**

 *  Active (as authorized by section abc)
 *  Approved (under section xyz)
 *  Withdrawn (under section pqr)

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActRPSProductCategoryType
Display: ActRPSProductCategoryType
Definition:
Identifies the legal or administrative category assigned to a regulated product that determines or influences the way in which its submission is reviewed.

**Examples:**

 *  New active ingredients
 *  New ethical combination drug
 *  New administrative route

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActRPSReviewTimeType
Display: ActRPSReviewTimeType
Definition:
Identifies the time period in which a submission of a given type is to be reviewed as established by law or practice in the particular regulatory realm.

**Examples:**

 *  30 days, reduced time
 *  60 days, regular time
 *  90 days, extended time

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ActServiceDeliveryLocationServiceType
Display: ActServiceDeliveryLocationServiceType
Definition:
**Description:**Concepts representing the categorization of health services available at a particular delivery location site.

**Examples:**

 *  anesthetic service
 *  colonoscopy service
 *  orthopedic service


Code: ActServiceEventType
Display: ActServiceEventType
Definition:
Concepts identifying the general type of care or category of services being documented.

**Examples:** 

 *  Colonoscopy
 *  appendectomy
 *  laboratory test


Code: ActSubstanceAdminSubstitutionCode
Display: ActSubstanceAdminSubstitutionCode
Definition:
**Definition:**Identifies the types of substitution that may be permitted when ordering a medication, as well as those which have actually occurred during the act of dispensing.


Code: ActSupplyType
Display: ActSupplyType
Definition:
**Description:** Further defines the type of supply for order or distribution.

**Examples:**

 *  central supply
 *  materials management
 *  nurse station supply


Code: ActProductAcquisitionType
Display: ActProductAcquisitionType
Definition:
**Description:** Financial Acquisition Terms: categorizations of acquisition terms for a product.

Types of method a product can be obtained for use by the subject of the supply act (e.g. patient). Product examples are consumable or durable goods.

*Examples:* 

 *  Loan
 *  Rent
 *  Sale


Code: ActProductLifeCycleEventType
Display: ActProductLifeCycleEventType
Definition:
**Description:** A type of activity that takes place during the life of a product as it moves from the point of production to the point of consumption, use, or disposition (most notably in the case of contaminated products). It will be possible for concepts at different levels of granularity to be included.

**Examples:**

 *  Manufacture
 *  paint
 *  wholesale
 *  dispose


Code: OralDietSupplyType
Display: OralDietSupplyType
Definition:
Concepts representing diets that can be taken via the mouth.

**Examples:** 

 *  General
 *  Pureed
 *  Easy to Chew


Code: ActTaskCode
Display: ActTaskCode
Definition:
**Description:** A task or action that a user may perform in a clinical information system

**Examples:**

 *  medication order entry
 *  laboratory test results review
 *  problem list entry


Code: AdverseEventProductRelatedInvestigationType
Display: AdverseEventProductRelatedInvestigationType
Definition:
**Description:** Different types that are used to organize and classify product related investigations.

**Examples:**

 *  Original source investigation
 *  Secondary party investigation
 *  Report to regulatory authority


Code: DEADrugSchedule
Display: DEADrugSchedule
Definition:
DEA schedule for a drug.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: HL7TriggerEventCode
Display: HL7TriggerEventCode
Definition:
The trigger event referenced by the Control Act instance. Values are drawn from the available trigger events used in the release of HL7 identified by the versionCode.


Code: LaboratoryTriggerEventType
Display: LaboratoryTriggerEventType
Definition:
**Description:** Trigger events associated with laboratory results.

**Examples:**

 *  Lab result activate
 *  Lab result complete
 *  Lab result abort


Code: SpecimenProcessTriggerEventType
Display: SpecimenProcessTriggerEventType
Definition:
**Description:** Trigger events associated with specimen process steps.

**Examples:**

 *  Specimen process step activate
 *  Specimen process step complete
 *  Specimen process step abort


Code: ImmunizationForecastStatus
Display: ImmunizationForecastStatus
Definition:
Used to represent the patient's status with respect to their immunization guideline as of an evaluation date.


Code: ManufacturerActivityActType
Display: ManufacturerActivityActType
Definition:
**Description:** The activity of businesses operating in the manufacture and distribution of products.

**Examples:**

 *  manufacture
 *  repack
 *  import


Code: MarketingActivityActType
Display: MarketingActivityActType
Definition:
**Description:** The broad activity of businesses operating in the distribution of products, the general act of making a product available to the public.

**Examples:**

 *  Marketing, (this is required as a singleton value set, as there may be no other use case for this than to distinguish one Act of handling products from other Acts, such as manufacturing.)


Code: ActDetectedIssueCode
Display: ActDetectedIssueCode
Definition:
**Definition:**Identifies what type of issue detected during occurrence of an act (e.g. unrecognized identifiers, drug-drug contraindications, drug-allergy alerts).

**Examples:**

 *  High dosage alert
 *  Conditional element missing
 *  Timing detected issue


Code: ActFinancialDetectedIssueCode
Display: ActFinancialDetectedIssueCode
Definition:
Identifies types of detected issues for Act class "ALRT" for the financial acts domain.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ClinicalActionDetectedIssueCode
Display: ClinicalActionDetectedIssueCode
Definition:
Identifies types of issues detected regarding the performance of a clinical action on a patient.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: MedicationIssueTypeCode
Display: MedicationIssueTypeCode
Definition:
**Description:** Any type of issue that identifies a potential adverse situation that would or might occur with the described substance administration.

**Examples:**

 *  adverse effect
 *  drug interaction
 *  drug-food interaction


Code: DrugActionDetectedIssueCode
Display: DrugActionDetectedIssueCode
Definition:
Proposed therapy may be contraindicated or ineffective based on an existing or recent drug therapy

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActPrivilegeCategorization
Display: ActPrivilegeCategorization
Definition:
An Act which characterizes a Privilege can have additional observations to provide a finer definition of the requested or conferred privilege. This domain describes the categories under which this additional information is classified.


Code: ActPrivilegeCategorizationType
Display: ActPrivilegeCategorizationType
Definition:
This domain includes observations used to characterize a privilege, under which this additional information is classified.

*Examples:*A privilege to prescribe drugs has a RESTRICTION that excludes prescribing narcotics; a surgical procedure privilege has a PRE-CONDITION that it requires prior Board approval.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActSecurityObjectCode
Display: ActSecurityObjectCode
Definition:
**Description:**An access control object used to manage permissions and capabilities of users within information systems. (See HL7 RBAC specification fo examples of thes objects.)

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: AdverseSubstanceAdministrationEventActionTakenType
Display: AdverseSubstanceAdministrationEventActionTakenType
Definition:
**Definition:** Indicates the class of actions taken with regard to a substance administration related adverse event. This characterization offers a judgment of the practitioner"s response to the patient"s problem.

**Examples:** Example values include dose withdrawn, dose reduced, dose not changed.

**NOTE:** The concept domain is currently supported by a value set created by the International Conference on Harmonization

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: CommonClinicalObservationType
Display: CommonClinicalObservationType
Definition:
Used in a patient care message to report and query simple clinical (non-lab) observations.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: CommonCodedClinicalObservationType
Display: CommonCodedClinicalObservationType
Definition:
**Description:** Identifies the type for a clinical observation whose value is expressed as a code.

**Examples:**

 *  Home support level
 *  Tumor staging
 *  abdominal pain characteristic


Code: CommonCodedClinicalObservationComponentType
Display: CommonCodedClinicalObservationComponentType
Definition:
**Description:** Represents the components of a coded clinical observation.

**Examples:**

 *  ability to articulate
 *  ability to chop food
 *  ability to crouch


Code: CultureObservationType
Display: CultureObservationType
Definition:
**Description:**To be used to code and identify the Microbiology laboratory orderable and resultable observation question.

**Examples:**

 *  Urine; Culture
 *  Deep Wound; Aerobic Culture
 *  Microscopic Examination; Gram Stain


Code: OrganismIdentificationObservationType
Display: OrganismIdentificationObservationType
Definition:
**Description:**To be used to code and identify the Microbiology laboratory observation code that relates to the microorganism identification.

**Examples:**

 *  Bacteria identified
 *  Bacteria identified in tissue
 *  Fungus identified


Code: DeviceCharacteristicObservationType
Display: DeviceCharacteristicObservationType
Definition:
Identifies characteristics (physical, visual, clinical) that may be observed for a particular device or device type.

**Examples:**

 *  Height
 *  Sterility
 *  External diameter


Code: DiagnosticImageReportObservationType
Display: DiagnosticImageReportObservationType
Definition:
Identifies the type of diagnostic image report.

**Examples:**

 *  Echocardiogram Report
 *  Ultrasound Report
 *  Nuclear Medicine Imaging Report


Code: DiseaseCategorizationObservationType
Display: DiseaseCategorizationObservationType
Definition:
**Description:** An observation that categorizes an existing observation of a disease, symptom or condition.

*Usage Note:* The act being categorized should be an observation of a disease, symptom or condition; the categorizing act should be an observation of the category of that disease, symptom or condition, and the relationship between the two acts should be a "has generalization" relationship.

**Examples:**

 *  \[Observation of\] "thrombocytopenia" is categorized as an observation of "Haematologic system" category
 *  \[Observation of\] "duodenal ulcer" is categorized as an observation of "Gastro-intestinal system" category
 *  \[Observation of\] "eczema" is categorized as an observation of "Dermatologic system" category


Code: ECGControlVariable
Display: ECGControlVariable
Definition:
Identifies types of observations about the parameters required for acquisition and processing of ECG data.

**Examples:** 

 *  item byte order
 *  sample rate
 *  displayed sweep rate


Code: EventFrequencyObservationType
Display: EventFrequencyObservationType
Definition:
**Description:** Identifies types of observations that describe or categorize an observation in terms of the frequency of the observed event occurring.

**Examples:**

 *  Very common
 *  Uncommon
 *  Rare


Code: FDALabelData
Display: FDALabelData
Definition:
FDA label data

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: FinancialClinicalSupportingObservationType
Display: FinancialClinicalSupportingObservationType
Definition:
**Description:**Describes the supporting information for financial transactions such as a Special Authorization Request.

Example values under this concept domain could be: height, weight, duration of disease, site of fistula, etc.

This concept domain is intended to be used as part of a code/value pair within a generic structure that would convey ANY sort of information or proof of criteria that is needed to support a special authorization request.


Code: ICSRContextualObservationType
Display: ICSRContextualObservationType
Definition:
**Description:** A type of observation on an investigative subject or a related entity that might be collected to provide the medical and social context for an adverse event report.

**Examples:**

 *  Diagnosis
 *  laboratory result
 *  autopsy determined cause of death


Code: ImmunizationForecastDate
Display: ImmunizationForecastDate
Definition:
Specifies the type of date that is specified in an immunization forecast. The immunization forecast defines the schedule for a vaccine based on variables like the subject's age, the type of vaccine, and the supply unit. The immunization forecast may involve multiple administrations in a series or just one administration. Each of the administrations has one or more recommended dates.

**Examples:** 

 *  Earliest recommended date
 *  Recommended date
 *  Latest acceptable date
 *  Overdue date (date after which to start sending reminders)


Code: IndividualCaseSafetyReportType
Display: IndividualCaseSafetyReportType
Definition:
Types of case safety report received from sender. The current code example reference is from the International Conference on Harmonization (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.


Code: ICSR_InvestigationAssessmentActType
Display: ICSR_InvestigationAssessmentActType
Definition:
**Description:** Concepts that define the primary orientation of a product related investigation.

**Examples:**

 *  Product defect
 *  adverse event


Code: IndividualCaseSafetyReportCriteria
Display: IndividualCaseSafetyReportCriteria
Definition:
**Description:** Includes those concepts that are provided to justify the fact that an adverse event or product problem is required to be reported in an expedited fashion.


Code: IndividualCaseSafetyReportProductCharacteristic
Display: IndividualCaseSafetyReportProductCharacteristic
Definition:
**Description:** Includes relevant pieces of information about a product or its process of creation. The vocabulary domain is used to characterize products when they are cited in adverse event or product problem reports.

**Examples:**Weight, color, dimensions.


Code: IsolateObservationType
Display: IsolateObservationType
Definition:
**Description:**To be used in the message when there is a requirement to communicate a result observation code that relates to a specific isolate.

**Examples:**

 *  Colony count
 *  Colony count; Viability count FDA method
 *  Growth rate; Visual method


Code: KnowledgeSubjectObservationType
Display: KnowledgeSubjectObservationType
Definition:
Categorization of types of observation that capture the main clinical knowledge subject which may be a medication, a laboratory test, a disease.


Code: KnowledgeSubTopicObservationType
Display: KnowledgeSubTopicObservationType
Definition:
Categorization of types of observation that capture a knowledge subtopic which might be treatment, etiology, or prognosis.


Code: MedicationSafetyReportObservationType
Display: MedicationSafetyReportObservationType
Definition:
**Description:** Identifies types of observations about the Safety Reports required for a particular medication.

**Examples:**

 *  \[Observation of\] International Birth Date
 *  \[Observation of\] Data Lock Point
 *  \[Observation of\] Frequency of Safety Report Submission


Code: PhysicalCharacteristicsMedicationObservationType
Display: PhysicalCharacteristicsMedicationObservationType
Definition:
Identifies physical characteristics that may be observed for a particular medicinal product or medicinal product package of types thereof.

**Examples:**

 *  Height
 *  Imprint
 *  Shape
 *  Color


Code: ObservationActAgeGroupType
Display: ObservationActAgeGroupType
Definition:
**Description:**To allow queries to specify useful information about the age of the patient without disclosing possible protected health information.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationAllergyTestCode
Display: ObservationAllergyTestCode
Definition:
**Description:**Dianostic procedures ordered or performed to evaluate whether a sensitivity to a substance is present. This test may be associated with specimen collection and/or substance administration challenge actiivities.

**Example:**Skin tests and eosinophilia evaluations.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationAllergyTestType
Display: ObservationAllergyTestType
Definition:
Indicates the type of allergy test performed or to be performed. E.g. the specific antibody or skin test performed

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationCaseStatusType
Display: ObservationCaseStatusType
Definition:
**Description:** A code used to further identify the type of case status observation. Used with the OBS ActClass.

**Examples:**

 *  Clinical status
 *  Administrative status
 *  Reporting status


Code: ObservationCausalityAssessmentType
Display: ObservationCausalityAssessmentType
Definition:
**Description:**A kind of observation that allows a Secondary Observation (source act) to assert (at various levels of probability) that the target act of the association (which may be of any type of act) is implicated in the etiology of another observation that is named as the subject of the Secondary Observation

**Example:**Causality assertions where an accident is the cause of a symptom; predisposition assertions where the genetic state plus environmental factors are implicated in the development of a disease; reaction assertions where a substance exposure is associated with a finding of wheezing.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationCoordinateAxisType
Display: ObservationCoordinateAxisType
Definition:
**Description:** Identifies the individual coordinate in the coordinate system inclusive of any transformations or projections.

**Examples:** meridian, range, township, longitude, latitude, lot, block, etc.


Code: ObservationDosageDefinitionPreconditionType
Display: ObservationDosageDefinitionPreconditionType
Definition:
**Definition:**

The set of observation type concepts that can be used to express pre-conditions to a particular dosage definition.

Rationale: Used to constrain the set of observations to those related to the applicability of a dosage, such as height, weight, age, pregnancy, liver function, kidney function, etc. For example, in drug master-file type records indicating when a specified dose is applicable.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationIndicationType
Display: ObservationIndicationType
Definition:
Includes all codes defining types of indications such as diagnosis, symptom and other indications such as contrast agents for lab tests

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationIntoleranceType
Display: ObservationIntoleranceType
Definition:
**Description:** Types of sensitivity caused by an exposure to a substance which results in an abnormal immunologic or non-immunologic response.

**Examples:** 

 *  Food allergy
 *  Environmental allergy
 *  Fod intolerance


Code: ObservationInvestigationType
Display: ObservationInvestigationType
Definition:
**Description:**  Used to further classify the type of investigation being documented. This concept domain is intended to be used with the INVSTG Act class code.

**Examples:**

 *  Public health case investigation
 *  Safety investigation
 *  Surveillance investigation


Code: ObservationIssueTriggerMeasuredObservationType
Display: ObservationIssueTriggerMeasuredObservationType
Definition:
Distinguishes between the kinds of measurable observations that could be the trigger for clinical issue detection. Measurable observation types include: Lab Results, Height, Weight.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationLabReportType
Display: ObservationLabReportType
Definition:
**Description:** A set of codes specifying the type of Laboratory Report.

**Examples:**

 *  Hematology reports
 *  Chemistry reports
 *  Blood gas reports


Code: ObservationOrderableType
Display: ObservationOrderableType
Definition:
**Description:** Identifies the type of observations that can be ordered.

**Examples:**

 *  lab tests
 *  diagnostic imaging
 *  device summary


Code: ObservationOrderableLabType
Display: ObservationOrderableLabType
Definition:
**Description:** Identifies the ordered lab test. Also known as the lab order code or test code.

**Examples:**

 *  red blood cell count
 *  components of a chemistry panel
 *  microbiology sensitivity testing


Code: ObservationOutbreakExtentType
Display: ObservationOutbreakExtentType
Definition:
**Description:** A code used to further identify the type of Outbreak Extent Observation. Used with the OBS ActClass.

**Examples:**

 *  Geographic extent
 *  Jurisdictional extent


Code: ObservationPublicHealthCaseType
Display: ObservationPublicHealthCaseType
Definition:
**Definition:**Identifies the kinds of public health cases. Used only with the CASE Act class code.

Examples of types of public health cases includes reportable disease cases, radiation exposure cases and chemical exposure cases.


Code: ObservationPublicHealthOutbreakType
Display: ObservationPublicHealthOutbreakType
Definition:
**Description:** 

Used to further classify the type of Outbreak being documented. This concept domain is intended to be used with the OUTB Act class code.

**Examples:**

 *  Epidemic
 *  Pandemic
 *  Endemic


Code: ObservationQualityMeasureAttributeType
Display: ObservationQualityMeasureAttributeType
Definition:
Codes used to define various metadata aspects of a health quality measure (specialization of ActClass "OBS").


Code: ObservationQueryMatchType
Display: ObservationQueryMatchType
Definition:
**Definition:** An observation related to a query response.

**Example:**The degree of match or match weight returned by a matching algorithm in a response to a query.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ObservationResultableType
Display: ObservationResultableType
Definition:
**Description:** Identifies the type of observation that can be resulted. There are some labs which are not ordered and are performed and resulted when the outcome of an ordered test meets some criteria.

**Examples:**

 *  outcomes of lab tests
 *  device summary
 *  therapeutic drug level testing


Code: ObservationResultableLabType
Display: ObservationResultableLabType
Definition:
**Description:** The type of lab observation being resulted. There are some lab tests which are not ordered and are performed and resulted when the outcome of an ordered test meets some criteria.

**Examples:**

 *  red blood cell count
 *  results of micro sensitivity testing
 *  *Missing third example*


Code: ObservationVisionPrescriptionType
Display: ObservationVisionPrescriptionType
Definition:
**Definition:** Identifies the type of Vision Prescription Observation that is being described.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: PatientCharacteristicObservationType
Display: PatientCharacteristicObservationType
Definition:
Indicates the type of characteristics a patient should have for a given therapy to be appropriate. E.g. Weight, Age, certain lab values, etc.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: PopulationInclusionObservationType
Display: PopulationInclusionObservationType
Definition:
Observation types for specifying criteria used to assert that a subject is included in a particular population.

**Examples:** 

 *  denominator
 *  numerator
 *  initial population


Code: PrescriptionObservationType
Display: PrescriptionObservationType
Definition:
Observations specific to a particular prescription to express concepts that cannot be expressed via other modeling approaches.

*Examples:*  "Patient Medication On Hand Quantity", "Patient Medication On Hand Days Supply", "Patient Expected Supply Run-out Date", "Percentage Dispensed".


Code: SecurityObservationType
Display: SecurityObservationType
Definition:
Type of security metadata observation made about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used in security labels.

*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:

 *  The security policy identifiers shall be identical,
 *  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
 *  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.

*Usage Note:* SecurityObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the securty label tag set "SecurityObservationValue" value set.


Code: SecurityCategoryObservationType
Display: SecurityCategoryObservationType
Definition:
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."

*Rationale:* A security category observation supports the requirement to specify the type of IT resource in order to facilitate application of appropriate levels of security according to a range of levels of impact or consequences that might result form 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 188\]

**Examples:** Types of security categories include:

 *  Compartment: A division of data into isolated blocks with separate security controls for the purpose of reducing risk. (ISO 2382-8). Security label metadata 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)
 *  Sensitivity: The characteristic of a 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)

*Usage Note:* SecurityCategoryObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tage set "SecurityCategoryObservatonValue" value set.

Codes may be drawn from the union of the following value sets: V:PrivacyPolicyType, V:ActPrivacyLaw, V:ActConsentDirective, V:InformationSensitivityPolicy, V:ActInformationSensitivityPolicy, V:RoleInformationSensitivityPolicy, EntitySensitivityPolicy, and V:ActConsentType. Could be bound R1 to a V:ActUSPrivacyPolicy in a future US Realm.


Code: SecurityClassificationObservationType
Display: SecurityClassificationObservationType
Definition:
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 harm to an individual that could result from unauthorized disclosure.

**Examples:** Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal. Intelligence community examples include top secret, security, and confidential.

*Usage Note:* SecurityClassificationObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityClassificationObservationValue" value set.

Note that an Act or Role may be associated with an Observation coded as SecurityClassificationObservationType with a SecurityClassificationObservationValue coded with a confidentiality code from V:Confidentiality Code to indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for assigning 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.


Code: SecurityControlObservationType
Display: SecurityControlObservationType
Definition:
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.

**Examples:** Types of security control metadata include handling:

 *  caveats
 *  dissemination controls
 *  obligations
 *  refrain policies
 *  purpose of use constraints

*Usage Note:* SecurityControlObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityControlObservationValue" value set. Codes may be drawn from the union of the following value sets: V:SecurityPolicy, V:ObligationiPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurposeOfUse.


Code: SecurityIntegrityObservationType
Display: SecurityIntegrityObservationType
Definition:
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.

*Rationale:* Integrity security label fields support integrity models such as the Biba Integrity Model, the Lipner Full Integrity Model, and the Clar-Wilson Model. The value in the integrity label field indicates the degree of confidence that may be placed in the data and also indicates which measures the data requires for protection from modification and destruction.

**Examples:** Types of security integrity observation metadata, which may value the observation include:

 *  Integrity status, which indicates the completeness or workflow status of a resource (data, information object, service, or system capability);
 *  Integrity confidence, which indicates the reliability and trustworthiness of the resource;
 *  Integrity control, which indicates pertinent handling caveats, obligations, refrain policies, and purpose of use for the resource;
 *  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);
 *  Alteration integrity, which indicate the security mechanisms used for authorized transformations of the resource;
 *  Integrity provenance, which indicates the second-hand origins of a reported or asserted resource.

*Usage Note:* SecurityIntegrityObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityIntegrityObservationValue" value set.


Code: SecurityAlterationIntegrityObservationType
Display: SecurityAlterationIntegrityObservationType
Definition:
Type of security metadata observation made about the alteration integrity of an altered IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformation of the resource.

**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, include:

 *  translation
 *  syntactic transformation
 *  semantic mapping
 *  redaction
 *  masking
 *  pseudonymization
 *  anonymization

*Usage Note:* SecurityAlterationIntegrityObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityAlterationIntegrityObservationValue" value set, which convey the mechanism used for authorized transformation of an IT resource.


Code: SecurityDataIntegrityObservationType
Display: SecurityDataIntegrityObservationType
Definition:
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."

*Rationale:* In accordance with the HL7 RM-ES EHR-FM Profile Standard: The validity of a patient record entry requires an indelible statement (e.g., attestation or electronic signature) by the author(s) of completeness, accuracy, and affirmation that the record cannot be repudiated, assigning each author to his/her actual contributed content.

**Examples:** Types of security data integrity observation metadata, which may value the observation, include:

 *  cryptographic hash function
 *  digital signature

*Usage Note:* SecurityDataIntegrityObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityIntegrityConfidenceObservationValue" value set.


Code: SecurityIntegrityConfidenceObservationType
Display: SecurityIntegrityConfidenceObservationType
Definition:
Type of security metadata observation made about the integrity confidence of an IT resource (data, information object,service, or system capability) that indicates the reliability or trustworthiness of a resource, which may be used to make access control decisions.

**Examples:** Types of security integrity confidence observation metadata, which may value the observation, include:

 *  highly reliable
 *  uncertain reliability
 *  not reliable

*Usage Note:* A security integrity confidence observation on an Act may indicated that a valued Act.uncertainty attribute has been overridden by the entity responsible for assigning 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.uncertaintyCode.


Code: SecurityIntegrityProvenanceObservationType
Display: SecurityIntegrityProvenanceObservationType
Definition:
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 and workflow status of an IT resource, such as create, modify, append, amend, suspend, archive, and delete; 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.

**Examples:** Types of security integrity provenance observation metadata, which may value the observation with a code used to indicate provenance, include the entity responsible for a report or assertion relayed "second-hand" about an IT resource.

*Usage Note:* SecurityIntegrityProvenanceObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityIntegrityProvenanceObservationValue" value set.


Code: SecurityIntegrityProvenanceAssertedByObservationType
Display: SecurityIntegrityProvenanceAssertedByObservationType
Definition:
Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the entity responsible for an assertion relayed "second-hand" about an IT resource.

*Rationale:* In accordance with HL7 RM-ES EHR-FM Profile at IN:1.8: If more than one author contributed to the EHR content, then the system shall provide the ability to associate and maintain all authors/contributors with their content.

**Examples:** Types of security integrity provenance asserted by observation metadata, which may value the observation, include assertions about an IT resource by a patient, a clinician, or a device.

*Usage Note:* SecurityIntegrityProvenanceAssertedByObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityIntegrityProvenanceAssertedByObservationValue" value set.


Code: SecurityIntegrityProvenanceReportedByObservationType
Display: SecurityIntegrityProvenanceReportedByObservationType
Definition:
Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the entity responsible for a report relayed "second-hand" about an IT resource.

*Rationale:* In accordance with HL7 RM-ES EHR-FM Profile at IN:1.8: If more than one author contributed to the EHR content, then the system shall provide the ability to associate and maintain all authors/contributors with their content.

**Examples:** Types of security integrity provenance observation metadata, which may value the observation with a code used to indicate provenance, include reports about an IT resource by a patient, a clinician, or a device.

*Usage Note:* SecurityIntegrityProvenanceReportedByObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityIntegrityProvenanceReportedByObservationValue" value set.


Code: SecurityIntegrityStatusObservationType
Display: SecurityIntegrityStatusObservationType
Definition:
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 or workflow status of an IT resource, which may impact which users that are authorized to access and use the resource.

*Rationale:* In accordance with the HL7 RM-ES Profile Standard: The validity of a patient record entry requires an indelible statement (e.g., attestation or electronic signature) by the author(s) of completeness, accuracy, and affirmation that the record cannot be repudiated, assigning each author to his/her actual contributed content.

**Examples:** Types of security integrity status observation metadata, which may value the observation, include codes from the HL7 DocumentCompletion value set such as:

 *  legally authenticated
 *  in progress
 *  incomplete

*Usage Note:* SecurityIntegrityStatusObservationType concept domain designates a code system used to name a security label field type that may be valued with a "security label tag" such as a code from the security label tag set "SecurityIntegrityStatusObservationValue" concept domain, which may be valued with coded concepts from the HL7 DocumentCompletion value set.


Code: SecurityTrustAssuranceObservationType
Display: SecurityTrustAssuranceObservationType
Definition:
Type of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.


Code: SecurityTrustMechanismObservationType
Display: SecurityTrustMechanismObservationType
Definition:
Type of security metadata observation made about a security architecture system component that supports enforcement of security policies.


Code: SeverityObservationType
Display: SeverityObservationType
Definition:
Categorization of types of observation that capture the interpretation of the result of a laboratory test in terms of normality.


Code: SimpleMeasurableClinicalObservationType
Display: SimpleMeasurableClinicalObservationType
Definition:
Types of measurement observations typically performed in a clinical (non-lab) setting. E.g. Height, Weight, Blood-pressure

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: SimpleMeasurableClinicalObservationComponentType
Display: SimpleMeasurableClinicalObservationComponentType
Definition:
**Description:** Represents the components of a measured clinical observation.

**Examples:**

 *  the systolic and diastolic components of a blood pressure
 *  24-hour urine output
 *  ARAC gene


Code: SubstanceCharacteristicObservationType
Display: SubstanceCharacteristicObservationType
Definition:
Distinguishing traits, qualities, or properties given about substances, including chemical structure (as encapsulated data in SMILES, MolFile, InChi), nucleic acid sequence, amino acid sequence, molecular sum formula; molecular mass; stereochemistry and optical activity properties; viscosity; pH, pKa, catalytic activity, etc.


Code: SusceptibilityBatteryType
Display: SusceptibilityBatteryType
Definition:
**Description:**Ensures consistent coding of the susceptibility battery or panel.

**Examples:**

 *  Bacterial susceptibility panel
 *  Fungal susceptibility panel
 *  Mycobacterial susceptibility panel
 *  Viral susceptibility panel


Code: SusceptibilityObservationType
Display: SusceptibilityObservationType
Definition:
**Description:**Ensures consistent coding of antimicrobial information in the Microbiology lab message.

**Examples:**

 *  Ciprofloxacin; Disk Diffusion (Kirby-Bauer)
 *  Vancomycin
 *  Tetracycline; Minimum Inhibitory Concentration


Code: ResearchStudyType
Display: ResearchStudyType
Definition:
**Description:** Different types of research studies that may be conducted and reported on.

**Examples:**

 *  Observational
 *  Investigational


Code: TriggerEventID
Display: TriggerEventID
Definition:
**Description:** Trigger Event ID as published in the standard.

***Deprecation Comment:*** This Domain has been deprecated as the Domain HL7TriggerEventCode is being used instead, along with its subDomains. Please update designs that refer to this Domain and instead refer to the appropriate Domain in the HL7TriggerEventCode hierarchy.


Code: ActContextLevel
Display: ActContextLevel
Definition:
**Description:** Code specifying the level within a hierarchical Act composition structure and the kind of contextual information attached to composite Acts ("containers") and propagated to component Acts within those containers. The levelCode signifies the position within such a containment hierarchy and the applicable constraints.

*Examples:* The "extract level" and the "folder level" must contain data about a single individual, whereas the "multiple subject level" may contain data about multiple individuals. While "extract" can originate from multiple sources, a "folder" should originate from a single source. The "composition" level usually has a single author.

*Constraints:* The constraints applicable to a particular level may include differing requirements for participations (e.g. patient, source organization, author or other signatory), relationships to or inclusion of other Acts, documents or use of templates. The constraints pertaining to a level may also specify the permissible levels that may be contained as components of that level. Several nested levels with the same levelCode may be permitted, prohibited (or limited). Instance of the next subordinate level are usually permitted within any level but some levels may be omitted from a model and it may be permissible to skip several layers.

*Discussion:* The levelCode concepts have been defined to meet specific health record transfer requirements. While these concepts are known to be applicable to some other types of transactions, they are not intended to a be a complete closed list. Options exist for other sets of orthogonal levels where required to meet a business purpose (e.g. a multiple patient communication may be subdivided by a super-ordinate level of subject areas).


Code: ActMood
Display: ActMood
Definition:
A code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command, possibility, goal, etc.

*Constraints:* An Act-instance must have one and only one moodCode value.

The moodCode of a single Act-instance never changes. Mood is not state.

To describe the progression of a business activity from defined to planned to executed, etc. one must instantiate different Act-instances in the different moods and link them using ActRelationship of general type "sequel". (See ActRelationship.type.)

*Discussion:* The Act.moodCode includes the following notions: (1) event, i.e., factual description of an actions that occurred; (2) definition of possible actions and action plans (the master file layer); (3) intent, i.e., an action plan instantiated for a patient as a care plan or order; (4) goal, i.e., an desired outcome attached to patient problems and plans; and (5) criterion, i.e., a predicate used as

The Act.moodCode modifies the meaning of the Act class in a controlled way, just as in natural language, grammatical form of a verb modify the meaning of a sentence in defined ways. For example, if the mood is factual (event,) then the entire act object represents a known fact. If the mood expresses a plan (intent,) the entire act object represents the expectation of what should be done. The mood does not change the meaning of individual act properties in peculiar ways.

Since the mood code is a determining factor for the meaning of an entire Act object, the mood must always be known. This means, whenever an act object is instantiated, the mood attribute must be assigned to a valid code, and the mood assignment can not change throughout the lifetime of an act object.

As the meaning of an act object is factored in the mood code, the mood code affects the interpretation of the entire Act object and with it every property (attributes and associations.) Note that the mood code affects the interpretation of the act object, and the meaning of the act object in turn determines the meaning of the attributes. However, the mood code does not arbitrarily change the meaning of individual attributes.

*Inert vs. descriptive properties of Acts:* Acts have two kinds of act properties, inert and descriptive properties. Inert properties are not affected by the mood, descriptive properties follow the mood of the object. For example, there is an identifier attribute Act.id, which gives a unique identification to an act object. Being a unique identifier for the object is in no way dependent on the mood of the act object. Therefore, the "interpretation" of the Act.id attribute is inert with respect to the act object's mood.

By contrast, most of the Act class' attributes are descriptive for what the Act statement expresses. Descriptive properties of the Act class give answer to the questions who, whom, where, with what, how and when the action is done. The questions who, whom, with what, and where are answered by Participatons, while how and when is answered by descriptive attributes and ActRelationships. The interpretation of a descriptive attribute is aligned to the interpretation of the entire act object, and controlled by the mood.

*Examples:* To illustrate the effect of mood code, consider a "blood glucose" observation:

The DEFINITION mood specifies the Act of "obtaining blood glucose". Participations describe in general the characteristics of the people who must be involved in the act, and the required objects, e.g., specimen, facility, equipment, etc. involved. The Observation.value specifies the absolute domain (range) of the observation (e.g., 15-500 mg/dl.)

In INTENT mood the author of the intent expresses the intent that he or someone else "should obtain blood glucose". The participations are the people actually or supposedly involved in the intended act, especially the author of the intent or any individual assignments for group intents, and the objects actually or supposedly involved in the act (e.g., specimen sent, equipment requirements, etc.) The Observation.value is usually not specified, since the intent is not to measure blood glucose, not to measure blood glucose in a specific range. (But compare with GOAL below.)

In ORDER mood, a kind of intent, the author requests to "please obtain blood glucose". The Participations are the people actually and supposedly involved in the act, especially the placer and the designated filler, and the objects actually or supposedly involved in the act (e.g., specimen sent, equipment requirements, etc.) The Observation.value is usually not specified, since the order is not to measure blood glucose in a specific range.

In EVENT mood, the author states that "blood glucose was obtained". Participations are the people actually involved in the act, and the objects actually involved (e.g., specimen, facilities, equipment.) The Observation.value is the value actually obtained (e.g., 80 mg/dL, or <15 mg/dL.)

In event-CRITERION mood, an author considers a certain class of "obtaining blood glucose" possibly with a certain value (range) as outcome. The Participations constrain the criterion, for instance, to a particular patient. The Observation.value is the range in which the criterion would hold (e.g. > 180 mg/dL or 200?300 mg/dL.)

In GOAL mood (a kind of criterion) the author states that "our goal is to be able to obtain blood glucose with the given value (range)". The Participations are similar to intents, especially the author of the goal and the patient for whom the goal is made. The Observation.value is the range which defined when the goal is met (e.g. 80?120 mg/dl.)

*Rationale:* The notion of "mood" is borrowed from natural language grammar, the mood of a verb (lat. modus verbi).

The notion of mood also resembles the various extensions of the logic of facts in modal logic and logic with modalities, where the moodCode specifies the modality (fact, possibility, intention, goal, etc.) under which the Act-statement is judged as appropriate or defective.


Code: ActReason
Display: ActReason
Definition:
A code specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably representable as an ActRelationship of type "has reason" linking to another Act.

*Examples:* Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".

Discussion

Most reasons for acts can be clearly expressed by linking the new Act to another prior Act using an ActRelationship of type "has reason". This simply states that the prior Act is a reason for the new Act (see ActRelationship.) The prior act can then be a specific existing act or a textual explanation. This works for most cases, and the more specific the reason data is, the more should this reason ActRelationship be used instead of the reasonCode.

The reasonCode remains as a place for common reasons that are not related to a prior Act or any other condition expressed in Acts. Indicators that something was required by law or was on the request of a patient etc. may qualify. However, if that piece of legislation, regulation, or the contract or the patient request can be represented as an Act (and they usually can), the reasonCode should not be used.


Code: ActAdjudicationReason
Display: ActAdjudicationReason
Definition:
Explanatory codes that describe reasons why an Adjudicator has financially adjusted an invoice (claim).

A companion domain (ActAdjudicationInformationCode) includes information reasons which do not have a financial impact on an invoice (claim).

Example adjudication reason code is AA-CLAIM-0011 - Only Basic Procedure/Test Eligible.

Codes from this domain further rationalizes ActAdjudicationCodes (e.g. AA - Adjudicated with Adjustment), which are used to describe the process of adjudicating an invoice. For AS - Adjudicated as Submitted, there should be no specification of ActAdjudicationReason codes, as there are no financial adjustments against the invoice.


Code: ActBillableServiceReason
Display: ActBillableServiceReason
Definition:
**Definition:** This domain is used to document reasons for providing a billable service; the billable services may include both clinical services and social services.


Code: ActBillableClinicalServiceReason
Display: ActBillableClinicalServiceReason
Definition:
**Description:** May be sent to indicate one or more reasons for the performance of a billable clinical service or product, and not related or specified by a diagnosis.

*Examples:*

 *  Duplicate Therapy
 *  Care protocol
 *  Insurance requirement


Code: MedicallyNecessaryDuplicateProcedureReason
Display: MedicallyNecessaryDuplicateProcedureReason
Definition:
**Definition:** This domain is used to document why the procedure is a duplicate of one ordered/charged previously for the same patient within the same date of service and has been determined to be medically necessary.

**Example:** A doctor needs a different view in a chest X-Ray.


Code: ActBillableNonClinicalServiceReason
Display: ActBillableNonClinicalServiceReason
Definition:
**Description:** Maybe sent to indicate one or more reasons for the performance of a non clinical service or product, and not related or specified by diagnosis.

*Examples:*

 *  Fraudulent prescription
 *  Patient's preference
 *  Physiotherapy equipment


Code: NonClinicalDuplicateServiceReason
Display: NonClinicalDuplicateServiceReason
Definition:
**Description:** A duplicate non-clinical service or product is being re-billed.

*Examples:*

 *  Duplicate transportation required for physician visit
 *  Wrong size of a product
 *  Rebuilding wheel chair ramp due to a weather condition


Code: ActCoverageLevelRasonCode
Display: ActCoverageLevelRasonCode
Definition:
**Description:**Represents the reason for the level of coverage provided under the policy or program in terms of the types of entities that may play covered parties based on their personal relationships or employment status.


Code: ActCoverageProviderReason
Display: ActCoverageProviderReason
Definition:
**Description:**Identifies the reason or rationale for coverage of a service or product based on characteristics of the provider, e.g., contractual relationship to payor, such as in or out-of-network; relationship of the covered party to the provider.

**Example:**In closed managed care plan, a covered party is assigned a primary care provider who provides primary care services and authorizes referrals and ancillary and non-primary care services.


Code: ActCoverageServiceReason
Display: ActCoverageServiceReason
Definition:
**Description:**Identifies the reason or rationale for coverage of a service or product based on clinical efficacy criteria or practices prescribed by the payor.


Code: CoverageExclusionReason
Display: CoverageExclusionReason
Definition:
**Description:**Identifies the reason or rationale for coverage of a service or product based on coverage exclusions related the risk of adverse selection by covered parties.


Code: CoverageFinancialParticipationReason
Display: CoverageFinancialParticipationReason
Definition:
**Description:**Identifies the reason or rationale for coverage of a service or product based on financial participation responsibilities of the covered party.


Code: CoverageLimitationReason
Display: CoverageLimitationReason
Definition:
**Description:**Identifies the reason or rationale for limitations on the coverage of a service or product based on coverage contract provisions.

**Example:**The maximum cost per unit; or the maximum number of units per period, which is typically the policy or program effective time.


Code: EligibilityActReasonCode
Display: EligibilityActReasonCode
Definition:
Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam.

*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.


Code: CoverageEligibilityReason
Display: CoverageEligibilityReason
Definition:
Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam.

*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.


Code: ActInformationManagementReason
Display: ActInformationManagementReason
Definition:
**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.


Code: ActHealthInformationManagementReason
Display: ActHealthInformationManagementReason
Definition:
**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.


Code: ActConsentInformationAccessOverrideReason
Display: ActConsentInformationAccessOverrideReason
Definition:
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.

*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.


Code: ActHealthInformationPrivacyReason
Display: ActHealthInformationPrivacyReason
Definition:
**Description:** 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.


Code: ActHealthInformationPurposeOfUseReason
Display: ActHealthInformationPurposeOfUseReason
Definition:
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.

*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.


Code: ActInformationAccessOverrideReason
Display: ActInformationAccessOverrideReason
Definition:
**Description:** Use to convey the reason that a provider may or has accessed personal healthcare information. Typically, this involves overriding the subject's consent directives.


Code: ActInformationPrivacyReason
Display: ActInformationPrivacyReason
Definition:
**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.


Code: ActPreferenceReason
Display: ActPreferenceReason
Definition:
Reasons why a preference has been specified.

**Examples:** 

 *  Side Effects
 *  Religious
 *  Request


Code: ActRPSRelatedApplicationReason
Display: ActRPSRelatedApplicationReason
Definition:
Identifies the reason for citing a related application.

**Examples:**

 *  Data protection period expiry reference
 *  Bioequivalence reference
 *  Drug Master File reference

*Usage Note:* This usage is confined to a specific set of requirements related to regulatory documents in the context of RPS documents.


Code: ControlActReason
Display: ControlActReason
Definition:
**Description:** Indicates the motivation, cause or rationale of an Act which results in a trigger event.


Code: ControlActNullificationRefusalReasonType
Display: ControlActNullificationRefusalReasonType
Definition:
**Description:** Indicates why a specific transaction which was requested to be undone; was not undone.


Code: ControlActReasonConditionNullify
Display: ControlActReasonConditionNullify
Definition:
Indicates why the ConditionaTMs status was changed to Nullified. *Examples* administrative error, diagnostic error.


Code: PharmacySupplyEventStockReasonCode
Display: PharmacySupplyEventStockReasonCode
Definition:
**Definition:**A collection of concepts that indicates the reason for a "bulk supply" of medication.


Code: SupplyOrderAbortReasonCode
Display: SupplyOrderAbortReasonCode
Definition:
Indicates why the prescription should no longer be allowed to be dispensed (but can still administer what already has been dispensed).

*UsageNote:* This is typically used in the scenario where the prescription allows for repeats or refills.


Code: NonPerformanceReasonCode
Display: NonPerformanceReasonCode
Definition:
The reason the action was not performed, e.g. why the medication was not taken. If an action was not performed, it is often clinically important to know why the action was not taken.

*Examples:*Patient refused, clinically inappropriate, absolute contraindication etc.


Code: ReasonForNotEvaluatingDevice
Display: ReasonForNotEvaluatingDevice
Definition:
Code assigned to indicate the rationale for not performing an evaluation investigation on a device for which a defect has been reported.

Examples include: device received in a condition that made analysis impossible, device evaluation anticipated but not yet begun, device not made by company.


Code: ReferralReasonCode
Display: ReferralReasonCode
Definition:
The reason a referral was made.

*Examples:*Specialized Medical Assistance, Other Care Requirements.


Code: RefusalReasonCode
Display: RefusalReasonCode
Definition:
**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.


Code: SafetyInvestigationReportReasonType
Display: SafetyInvestigationReportReasonType
Definition:
**Description:** Possible reasons generating a report providing information developed during the investigation of an adverse event or a product problem.

**Examples:**

 *  Correction
 *  Additional information/Follow-up
 *  Response to regulatory agency request


Code: SubstanceAdminSubstitutionReason
Display: SubstanceAdminSubstitutionReason
Definition:
Indicates the reason for substitution when substitution occurs, or reason for non-substitution when substitution is expected.


Code: SubstanceAdministrationNoSubstitutionReason
Display: SubstanceAdministrationNoSubstitutionReason
Definition:
Indicates the reason for non-substitution when substitution was expected.

**Examples:**

 *  prescriber request
 *  patient request
 *  continuing therapy (where this latter means that the prescribed item was not substituted, even though "policy" implied it should be, so as not to change from the item that the patient had previously received)


Code: SubstanceAdministrationPerformedSubstitutionReason
Display: SubstanceAdministrationPerformedSubstitutionReason
Definition:
Indicates the reason for substitution when substitution has occurred.

**Examples:**

 *  formulary policy
 *  regulatory requirement
 *  out of stock (where this latter means that the prescribed item was out of stock and an equivalent product was substituted)


Code: UpdateRefusalReasonCode
Display: UpdateRefusalReasonCode
Definition:
**Description:** Identifies why a request to update to 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.


Code: HumanSubstanceAdministrationSite
Display: HumanSubstanceAdministrationSite
Definition:
**Description:** The set of body locations to or through which a substance or product may be administered.

**Examples:**

 *  buttock
 *  left upper arm
 *  bilateral eyes


Code: AttentionLineValue
Display: AttentionLineValue
Definition:
**Definition:**The domain of possible values used as the value of attention line specifications in AttentionLine directives.


Code: CaseDetectionMethod
Display: CaseDetectionMethod
Definition:
Code for the method by which the public health department was made aware of the case. Includes provider report, patient self-referral, laboratory report, case or outbreak investigation, contact investigation, active surveillance, routine physical, prenatal testing, perinatal testing, prison entry screening, occupational disease surveillance, medical record review, etc.


Code: CompliancePackageEntityType
Display: CompliancePackageEntityType
Definition:
**Definition:**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.


Code: Confidentiality
Display: Confidentiality
Definition:
Types of privacy metadata classifying an IT resource (data, information object, service, or system capability) according to its level of sensitivity, which is based on an analysis of applicable privacy policies and the risk of financial, reputational, or other harm to an individual or entity that could result if made available or disclosed to unauthorized individuals, entities, or processes.

*Usage Note:* Confidentiality codes may be used in security labels and privacy markings to classify IT resources based on sensitivity to indicate the obligation of a custodian or receiver to ensure that the protected resource is not made available or disclosed to individuals, entities, or processes (security principals) unless authorized per applicable policies. Confidentiality codes may also be used in the clearances of initiators requesting access to protected resources.

*Map:* Definition aligns with ISO 7498-2:1989 - Confidentiality is the property that information is not made available or disclosed to unauthorized individuals, entities, or processes.


Code: ContextControl
Display: ContextControl
Definition:
Identifies the control codes that are used to manage the propagation and scope of a particular ActRelationship or Participation within a set of Acts.


Code: EducationLevel
Display: EducationLevel
Definition:
**Description:** Highest level of education a person has achieved.

**Examples:**

 *  Elementary School
 *  College or baccalaureate degree complete
 *  High School

*Rationale:* These are levels, not numeric years


Code: EmployeeJob
Display: EmployeeJob
Definition:
A code specifying the job performed by the employee for the employer. For example, accountant, programmer analyst, patient care associate, staff nurse, etc.


Code: EmployeeOccupationCode
Display: EmployeeOccupationCode
Definition:
Industry and/or jurisdictional classification system for kind-of-work performed by an employee.

Occupation codes are intended primarily as work descriptions that are suitable for a multitude of public uses e.g., job matching, employment counseling, occupational and career guidance, and labor market information services.


Code: EmployeeSalaryType
Display: EmployeeSalaryType
Definition:
A value representing the method used by an employer to compute an employee's salary or wages.

*Examples:* Hourly, annual, commission


Code: EmploymentStatus
Display: EmploymentStatus
Definition:
A code used to define the employment status of the insured individual identified in UB-92 FL 58. UB-92 Form locator 64:Employment Status Code of the Insured. Can be used with Employee\_Employer\_statusCode in HL7. Values include Employed Full Time, Employed Part Time, Not Employed, Retired, On Active Military Duty


Code: EncounterAcuity
Display: EncounterAcuity
Definition:
A code depicting the acuity (complexity of patient care, resource intensiveness of the patient care) of a patient's medical condition upon arrival. Values may be derived from formal acuity coding schemes such as RBS.


Code: EncounterDischargeDisposition
Display: EncounterDischargeDisposition
Definition:
A code indicating patient status as of the ending service date of the period covered on this bill, as reported in FL6, Statement Covers Period. Values such as: Discharged to home or self care; Discharged/transferred to SNF, Discharged/transferred to an intermediate care facility (ICF); Expired; Hospice-medical facility. NUBC Form Locator 22


Code: EncounterReferralSource
Display: EncounterReferralSource
Definition:
A code used to define the place or organization responsible for the patient immediately prior to their admission; for example, in the United States, as this is identified in UB-92 Form Locator 20, Source of Adm(ission).


Code: LivingSubjectEntityType
Display: LivingSubjectEntityType
Definition:
Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject).

*Examples:* persons, animals, trees .


Code: AnimalEntityType
Display: AnimalEntityType
Definition:
**Description:** A categorizing and grouping mechanism for different types of animal in order to support treatment and reporting. The categories are expected to correspond to a single animal species, or to a related group of species.

**Examples:**

 *  Dog
 *  Reptile
 *  Deer


Code: ContainerEntityType
Display: ContainerEntityType
Definition:
**Definition:**An object used to hold other entities.

**Examples:**

 *  Test tube
 *  Shoe box
 *  Drinking glass


Code: HolderEntityType
Display: HolderEntityType
Definition:
**Description:** Holders are containers that hold other containers or holders.

**Examples:**

 *  Tube rack
 *  Specimen carrier
 *  Tray


Code: DeviceGenericType
Display: DeviceGenericType
Definition:
Includes the set of codes used to identify a device that may be referred to in an ICSR report. Example code set reference is the FDA Center for Devices and Radiological Health product code list.

Example product codes include: FOZ = Catheter, Intravascular, Therapeutic, short-term less than 30 days, MOP = Rotator, Prosthetic Heart Valve.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: DrugEntity
Display: DrugEntity
Definition:
A substance whose therapeutic effect is produced by chemical action within the body.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ClinicalDrug
Display: ClinicalDrug
Definition:
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.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActiveIngredientDrugEntityType
Display: ActiveIngredientDrugEntityType
Definition:
Any substance which, when combined with other ingredients, delivers all or part of the therapeutic benefit associated with a medication.

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ActiveMoitySubstanceType
Display: ActiveMoitySubstanceType
Definition:
A molecular structure (molecule or part of a molecule) which is the part of the molecule causing the intended pharmacological action. The value set for ActiveMoietySubstanceType may often be a subset of a SubstanceType value set. Candidate value sets are subsets of ChEBI, PubChem CID, CAS Number, InChi Key, and UNII.

**Examples:**

 *  Metoprolol (without the succinate or tartrate)
 *  Amoxicillin (anhydrous)
 *  Heparin (ion, without the matching Na or K cation)


Code: ManufacturedDrug
Display: ManufacturedDrug
Definition:
Identifies a drug or the use of a drug as produced by a specific manufacturer

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: PackagedDrugProductEntity
Display: PackagedDrugProductEntity
Definition:
A drug product identified at the level of the package in which it is commonly distributed. Code systems such as UPC (Universal Product Code), NDC (National Drug Code), GTIN(Global Trade Item Number) might be bound to this domain in a given realm.


Code: ExposureAgentEntityType
Display: ExposureAgentEntityType
Definition:
Indicates the material to which the patient was exposed which is believed to be related to the adverse reaction

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: ManufacturedMaterialEntityType
Display: ManufacturedMaterialEntityType
Definition:
An Entity or combination of Entities transformed for a particular purpose by a manufacturing process.

*Examples:* Processed food products, disposable syringes, chemistry analyzer, saline for infusion


Code: EntityDeviceType
Display: EntityDeviceType
Definition:
A type of manufactured material used in an activity, without being substantially changed through that activity.


Code: EntityDeviceTrackingTagType
Display: EntityDeviceTrackingTagType
Definition:
**Description:**The specific kind of location-tracking tag.

Examples:

 *  RFID
 *  WiFi
 *  Infrared


Code: FeedingDeviceType
Display: FeedingDeviceType
Definition:
A manufactured material that is used during the nutrition process but is not changed via the process.

**Examples:** 

 *  Disposable Utensils
 *  Plate Guard
 *  Sippy Cup


Code: MicroorganismEntityType
Display: MicroorganismEntityType
Definition:
**Description:**To be used to identify a microorganism when required by an act.

**Examples:**

 *  Escherichia coli
 *  Caulimoviridae
 *  Pseudomonas aeruginosa


Code: NutritionalMaterialType
Display: NutritionalMaterialType
Definition:
A material that is used to provide nutritional value.

**Examples:** 

 *  Food
 *  Formula
 *  Supplements


Code: FoodType
Display: FoodType
Definition:
Concepts that identify raw, cooked or edible substances or ingredients that are intended for consumption by humans or animals to supply nourishment.

**Examples:** 

 *  Orange
 *  Meat
 *  Milk


Code: NutritionalFormulaType
Display: NutritionalFormulaType
Definition:
Concepts that identify a type of natural or manufactured food product, typically liquid or powder mixed with water, for complete or supplemental feeding.

**Examples:** 

 *  Milk-based
 *  Breast-milk
 *  Soy-based
 *  Peptide-based
 *  Elemental


Code: NutritionalSupplementType
Display: NutritionalSupplementType
Definition:
Concepts that identify a type of natural or manufactured food product used to provide additional nutrients or nourishment replacements beyond those consumed in the normal diet.

**Examples:** 

 *  High-calorie
 *  High-protein
 *  Clear liquid
 *  Oral electrolyte Replacement


Code: NutrientType
Display: NutrientType
Definition:
Concepts that identify the component source substance (e.g., chemical compound class and/or element) that supply nourishment by providing energy or metabolic support.

**Examples:** 

 *  Carbohydrates
 *  Protein
 *  Fat
 *  Calcium
 *  Vitamin D
 *  Fiber


Code: PackagedProductEntityType
Display: PackagedProductEntityType
Definition:
**Description:** Identifies products such as (1) the GS1 (was UPC and EAN); (2) the U.S., the National Drug Code, which is the U.S. version of what is internationally named the (3) "Medicinal Product Identifier" (MPID). For device products such product code is also known as the "Unique Device Identifier" and may or may not use the GS1 system of product codes. In local contexts the product code can come from local coding systems also, as long as it is a code that denotes to a description of a manufactured product.

**Examples:** 

 *  0049-3980-41 (NDC for Geodon Roerig 80 mg capsules 10 capsules x 8 blister packs in a carton)


Code: ProductEntityType
Display: ProductEntityType
Definition:
An identifying data string for healthcare products.

Example code sets include Healthcare Common Procedure Coding System (HCPCS) and Universal Product Code (UPC).


Code: ProductIngredientSubstanceEntityType
Display: ProductIngredientSubstanceEntityType
Definition:
**Description:** A type of substance that is used as an ingredient within a product.

**Examples:**

 *  Morphine
 *  wheat germ
 *  calcium


Code: SpecimenAdditiveEntityType
Display: SpecimenAdditiveEntityType
Definition:
**Definition:**Materials introduced to a specimen. These additives may be introduced in order to preserve, maintain or enhance the particular nature or component of the specimen.

**Examples:**

 *  Ammonium heparin
 *  Boric Acid
 *  Phenol


Code: SpecimenEntityType
Display: SpecimenEntityType
Definition:
**Description:** A specimen is defined as a physical entity that is an individual, a group, an item, or a part representative of a larger group, class or whole that is the target of an observation or analysis for the purpose of drawing conclusions about the group, class, or whole. This can be used to code a component of the specimen that the observation diagnosis relates to. Note that any physical entity in the universe has the potential to become a specimen.

**Examples:**

 *  Blood
 *  Water
 *  Animal cadaver


Code: HumanLabSpecimenEntityType
Display: HumanLabSpecimenEntityType
Definition:
**Description:** To be used to code the anatomic component of the human-sourced specimen that the lab observation relates to.

**Examples:**

 *  Endometrial biopsy
 *  Thyroid fine needle aspirate
 *  Urine


Code: ManufacturedMaterialSpecimenEntityType
Display: ManufacturedMaterialSpecimenEntityType
Definition:
**Description:** A specimen that is manufactured or a specimen from a manufactured material. This may be a quality control specimen or a manufactured substance.

**Examples:**

 *  Quality control specimen
 *  Aspirin
 *  Breakfast sausage


Code: VaccineType
Display: VaccineType
Definition:
Types of manufactured material that when administered are intended to confer protection against specific disease(s).


Code: OrganizationEntityType
Display: OrganizationEntityType
Definition:
Further classifies entities of EntityClass ORG.

**Examples:**

 *  HL7 workgroup
 *  corporation
 *  fraternal organization


Code: IndividualCaseSafetyReportSenderType
Display: IndividualCaseSafetyReportSenderType
Definition:
A code that is used to indicate the type of organization which is originating and sending the ICSR. 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.

Example concepts are: Pharmaceutical Company, Regulatory Authority, Health Professional, Regional Pharmacovigilence Center, World Health Organization Collaborating Center for International Drug Monitoring.


Code: PlaceEntityType
Display: PlaceEntityType
Definition:
A physical 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.

*Examples:* dam; city; state.


Code: TerritoryEntityType
Display: TerritoryEntityType
Definition:
**Description:** A territorial entity that may be cited as the body over which an agency exercises jurisdiction, or which defines a sphere in which a party has a particular responsibility.

**Examples:**

 *  United States
 *  New York
 *  European Union


Code: EntityNamePartQualifier
Display: EntityNamePartQualifier
Definition:
**Description:** The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records.


Code: Ethnicity
Display: Ethnicity
Definition:
In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both.

*OpenIssue:* This concept domain definition does not align with current vocabulary practices and is much too US-centric to be appropriate as a "universal" domain.


Code: HL7UpdateMode
Display: HL7UpdateMode
Definition:
The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.

**Open Issue:**  From April 2008 harmonization: "Definition needs to be modified. Make contents to HL7 content mode code system match contents in this table" Clear that this needs to be revisited.


Code: IndustryClassificationSystem
Display: IndustryClassificationSystem
Definition:
North American Industry Classification System(NAICS) for the United States, a new economic classification system that replaces the 1987 Standard Industrial Classification (SIC) for statistical purposes. NAICS is a system for classifying establishments by type of economic activity. Its purposes are: (1) to facilitate the collection, tabulation, presentation, and analysis of data relating to establishments, and (2) to promote uniformity and comparability in the presentation of statistical data describing the economy. NAICS will be used by Federal statistical agencies that collect or publish data by industry. http://www.census.gov/epcd/www/naicsusr.html


Code: InvoiceElementModifier
Display: InvoiceElementModifier
Definition:
Designates a modifier to the code attribute to provide additional information about the invoice element.

*Examples:* Isolation allowance; After-hours service

*Rationale:* This is not pre-coordinated into the CD attribute because the modifier code set may not be specifically designed for use with the Act.code code set. This violates the constraint for using the 'modifier' property that the modifier code set must be defined as part of, or specifically for the base code set.


Code: ListOwnershipLevel
Display: ListOwnershipLevel
Definition:
A dynamic list of individual instances of Act which reflect the needs of an individual worker, team of workers, or an organization to view roups of Acts for clinical or administrative reasons.

*Discussion:* The grouped Acts are related to the WorkingList via an ActRelationship of type 'COMP' component).

*Examples:* Problem lists, goal lists, allergy lists, to-do lists, etc.

*Design note:* This physical class contains but a single attribute, other than those that it inherits from Act. Use of that attribute in the design of RIM-based static models has been **DEPRECATED** in HL7 RIM Harmonization, effective November 2005. This action was based on ecommendations from the Patient Care Technical Committee.

As a consequence, this class will cease to be shown as a physical class in the RIM, once the attribute is retired. Nevertheless, use of this class via an Act.classCode value of 'LIST' is entirely appropriate so long as only the attibutes inherited from Act are used.


Code: LivingSubjectLanguageTypes
Display: LivingSubjectLanguageTypes
Definition:
Types of language sourced from an entity that is a living subject.

*Usage Note:* Intended to be used for CD or CV data types. Use HumanLanguage concept domain to convey languages represented in ED.Language or other CS data types.


Code: MaterialForm
Display: MaterialForm
Definition:
This identifies the physical state, nature or manifestation of the material.

*Usage Notes:* When the Material class is specialised to Manufactured Material, which it is to routinely to describe Medicinal products and ingredient Substances, and to Containers and Devices, the Material Form attribute is used more explicitly to describe the form and manifestation of these types of concepts - for example for medicinal products, the formCode describes their dose form (tablet, ointment); and for containers, it is their physical type (box, carton, vial).

Examples:

 *  Powder
 *  Liquid
 *  Gas


Code: ContainerForm
Display: ContainerForm
Definition:
Describes the nature (or type) of the container.

**Examples:**

 *  Carton
 *  Bottle
 *  Vial

**DesignNote:**The material of the container should be separately specified (e.g. the "cardboard" part of cardboard carton or the "glass" part of glass vial should be described elsewhere).

**OpenIssue:**This usage of material form is used in Common Product Model,but it is at variance of what has been done in Specimen where the same information is captured in the Entity.code values. These differences need further study.


Code: DoseForm
Display: DoseForm
Definition:
**Description:**The physical manifestation "entity" that contains the active and/or inactive ingredients that deliver a dose of medicine (i.e., drug). The key defining characteristics of the dose form can be the state of matter, delivery method, release characteristics, and the administration site or route for which the product is formulated. (Derived from ISO IDMP specification, and SNOMED CT).

**Examples:**

 *  Tablet
 *  Capsule
 *  Oral solution


Code: AdministrableDrugForm
Display: AdministrableDrugForm
Definition:
Indicates the form in which the drug product should be administered.

This element only needs to be specified when (a) the form in which the drug is measured for dispensing differs from the form in which the drug is administered; and (b) the form in which the quantity of the administered drug being administered is not expressed as a discrete measured mass or volume, e.g. the dose is to be measured in "number of actuations."


Code: AdministratableDrugForm
Display: AdministratableDrugForm
Definition:
Indicates the form in which the drug product should be administered.

This element only needs to be specified when (a) the form in which the drug is measured for dispensing differs from the form in which the drug is administered; and (b) the form in which the quantity of the administered drug being administered is not expressed as a discrete measured mass or volume, e.g. the dose is to be measured in "number of actuations." Note that this code is a synonym of AdministrableDrugForm, and is the original misspelling as published in the CDA R2 base; the spelling was corrected in later revisions of V3, but is kept here for backwards compatibility.


Code: CombinedDoseForm
Display: CombinedDoseForm
Definition:
The description of this is: "Identifies, as a single concept, a combination dose form description for those products that contain two or more manufactured items in a single authorized product".

*Usage Notes:* This element needs only to be specified when the product entity describes a complete product that contains two or more manufactured items (sometimes called a combination product or a kit product); it should not be valued for (normal) products which consist of a single manufactured item with a single dose form. The combined dose form describes the orderable (manufactured) dose form of each manufactured item and (if appropriate, separately) the administrable dose form of the pharmaceutical product (as in example one below).

**Examples:** 

 *  Powder and solvent for solution for injection
 *  Pessary and vaginal cream
 *  Tablets and capsules


Code: OrderableDrugForm
Display: OrderableDrugForm
Definition:
**Description:**Indicates the form in which the drug product must be, or has been manufactured, or extemporaneous/magistral prepared .


Code: ObservationInterpretation
Display: ObservationInterpretation
Definition:
The domain of possible values for a categorical assessment of an observation value.

 *Discussion:*  These interpretation codes are sometimes called "abnormal flags", however, the judgment of normalcy is just one of the common rough interpretations, and is often not relevant. For example, the susceptibility interpretations are not about "normalcy", and for any observation of a pathologic condition, it does not make sense to state the normalcy, since pathologic conditions are never considered "normal."


Code: GeneticObservationInterpretation
Display: GeneticObservationInterpretation
Definition:
Concepts that specify interpretation of genetic analysis.

**Examples:** 

 *  positive
 *  negative
 *  carrier
 *  responsive


Code: ObservationInterpretationChange
Display: ObservationInterpretationChange
Definition:
Interpretations of change of quantity and/or severity.

**Examples:** 

 *  better
 *  worse
 *  increased


Code: ObservationInterpretationDetected
Display: ObservationInterpretationDetected
Definition:
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, this provides a categorical interpretation of the "meaning" of the quantitative value for the same observation.


Code: ObservationInterpretationExceptions
Display: ObservationInterpretationExceptions
Definition:
Technical exceptions resulting in the inability to provide an interpretation, such as "off scale". Does not include normality or severity.


Code: ObservationInterpretationExpectation
Display: ObservationInterpretationExpectation
Definition:
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.


Code: ObservationInterpretationNormality
Display: ObservationInterpretationNormality
Definition:
Interpretations 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.


Code: ObservationMethod
Display: ObservationMethod
Definition:
A code that provides additional detail about the means or technique used to ascertain the observation.

*Examples:* Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.

*Constraints:* In all observations the method is already partially specified by the Act.code. In this case, the methodCode NEED NOT be used at all. The methodCode MAY still be used to identify this method more clearly in addition to what is implied from the Act.code. However, an information consumer system or process SHOULD NOT depend on this methodCode information for method detail that is implied by the Act.code.

If the methodCode is used to express method detail that is also implied by the Act.code, the methodCode MUST NOT be in conflict with the implied method of the Act.code.

*Discussion:* In all observations the method is already partially specified by simply knowing the kind of observation (observation definition, Act.code) and this implicit information about the method does not need to be specified in Observation.methodCode. Particularly, most LOINC codes are defined for specific methods as long as the method makes a practical difference in interpretation. For example, the difference between susceptibility studies using the "minimal inhibitory concentration" (MIC) or the "agar diffusion method" (Kirby-Baur) are specifically assigned to different LOINC codes. The methodCode therefore is only an additional qualifier to specify what may not be known already from the Act.code.

Also, some variances in methods may be tied to the particular device used. The methodCode should not be used to identify the specific device or test-kit material used in the observation. Such information about devices or test-kits should be associated with the observation as "device" participations.


Code: AllergyTestObservationMethod
Display: AllergyTestObservationMethod
Definition:
**Description:**Provides additional methodology information not present in the associated AllergyTestCode term.


Code: CommonClinicalObservationMethod
Display: CommonClinicalObservationMethod
Definition:
**Description:**Used in a patient care message to value simple clinical (non-lab) observation methods, such as found in SOAP (subjective, objective, assessment, plan) progress notes: subjective section (used for history from patient and other informants); objective section (used for physical exam, lab, and other common results), and assessment section (used for the clinicians assessment of the implications of subjective and objective sections).


Code: GeneticObservationMethod
Display: GeneticObservationMethod
Definition:
A code that provides additional detail about the means or technique used to ascertain the genetic analysis. Example, PCR, Micro Array.


Code: SusceptibilityObservationMethodType
Display: SusceptibilityObservationMethodType
Definition:
**Description:**

**Examples:**

 *  Disk Diffusion (Kirby-Bauer)
 *  Minimum Inhibitory Concentration
 *  Viral Genotype Susceptibility
 *  Gradient Strip (E-Strip)


Code: CaseDiseaseImported
Display: CaseDiseaseImported
Definition:
Code that indicates whether the disease was likely acquired outside the jurisdiction of observation, and if so, the nature of the inter-jurisdictional relationship. Possible values include not imported, imported from another country, imported from another state, imported from another jurisdiction, and insufficient information to determine.


Code: CaseTransmissionMode
Display: CaseTransmissionMode
Definition:
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.

OpenIssue: Consider moving this attribute to Observation.


Code: CommonClinicalObservationAssertionValue
Display: CommonClinicalObservationAssertionValue
Definition:
**Definition:** The non-laboratory, non-DI (diagnostic imaging) coded observation if no value is also required to convey the full meaning of the observation. This may be a single concept code or a complex expression.


Code: CommonClinicalObservationComponentValue
Display: CommonClinicalObservationComponentValue
Definition:
**Description:** Represents observations for components of a clinical observation whose value is expressed as a code.

**Examples:**

 *  results for individual components of an APGAR score
 *  aberrant
 *  ABO incompatibility reaction


Code: CommonClinicalObservationResultValue
Display: CommonClinicalObservationResultValue
Definition:
**Definition:** The non-laboratory, non-diagnostic imaging coded result of the coded observable or "question" represented by the paired concept from the the NonLabDICodedObservationType domain.

\]

**Examples:**An APGAR result, a functional assessment, etc. The value must not require a specific unit of measure.


Code: CoverageChemicalDependencyValue
Display: CoverageChemicalDependencyValue
Definition:
**Definition:** The category of addiction used for coverage purposes that may refer to a substance, the consumption of which may result in physical or emotional harm.


Code: CoverageItemLimitObservationValue
Display: CoverageItemLimitObservationValue
Definition:
**Description:**Coded observation values for types or instances of items for which coverage is provided under a policy or program, e.g., a type of vehicle or a named work of art.


Code: CoverageLocationLimitObservationValue
Display: CoverageLocationLimitObservationValue
Definition:
**Description:**Coded observation values for types or instances of locations for which coverage is provided under a policy or program, e.g., in the covered party home, in state or in the country.


Code: CriticalityObservationValue
Display: CriticalityObservationValue
Definition:
Values that represent a clinical judgment as to the worst case result of a future exposure (including substance administration).

**Examples:** 

 *  High criticality
 *  Low criticality
 *  Unable to assess criticality


Code: CultureObservationValue
Display: CultureObservationValue
Definition:
**Description:**Used to code and identify the Microbiology laboratory result value when a result is reported.

**Examples:**

 *  Gram Positive Rods
 *  Epithelial Cells
 *  Polymorphonuclear Leukocyte


Code: FinancialClinicalSupportingObservationValue
Display: FinancialClinicalSupportingObservationValue
Definition:
**Description:**Contains the supporting information values for financial transactions such as a Special Authorization Request.

This concept domain is intended to be used as the "value" part of a code/value pair within a generic structure that would convey any sort of information or proof of criteria that is needed to support a special authorization request. For example:

One wishes to convey a patient's DSM IV diagnosis to support a special authorization request. One code/value pair is used:

ActSupportingInformationCode1 = DSM IV Diagnosis, value= 315.4


Code: GISPositionAccuracyTierCode
Display: GISPositionAccuracyTierCode
Definition:
**Description:** Categorizes the accuracy of spatial data assignment utilizing a variety of tools for capturing coordinates including digitizers, geocoding software and global positioning system devices.


Code: IndicationValue
Display: IndicationValue
Definition:
Indicates the specific observation result which is the reason for the action (prescription, lab test, etc.). E.g. Headache, Ear infection, planned diagnostic image (requiring contrast agent), etc.


Code: OtherIndicationValue
Display: OtherIndicationValue
Definition:
Indicates an observed reason for a medical action other than an indication or symptom. E.g. Need for a contrast agent prior to a diagnostic image, need for anesthesia prior to surgery, etc.


Code: SymptomValue
Display: SymptomValue
Definition:
Indicates an observed abnormality in the patientaTMs condition, but does not assert causation. E.g. Runny nose, swelling, flaky skin, etc.


Code: IndividualCaseSafetyReportValueDomains
Display: IndividualCaseSafetyReportValueDomains
Definition:
This domain is established as a parent to a variety of value domains being defined to support the communication of Individual Case Safety Reports to regulatory bodies. Arguably, this aggregation is not taxonomically pure, but the grouping will facilitate the management of these domains.


Code: CaseSeriousnessCriteria
Display: CaseSeriousnessCriteria
Definition:
A code that provides information on the overall effect or outcome of the adverse reaction/adverse event reported in the ICSR. Note the criterion applies to the case as a whole and not to an individual reaction.

Example concepts are: death, disability, hospitalization, congenital anomaly/ birth defect, and other medically important condition.


Code: DeviceManufacturerEvaluationInterpretation
Display: DeviceManufacturerEvaluationInterpretation
Definition:
A code set that includes codes that are used to characterize the outcome of the device evaluation process. The code defines the manufacturer's conclusions following the evaluation.

Examples include: inadequate alarms, device maintenance contributed to event, device failed just prior to use, user error caused event


Code: DeviceManufacturerEvaluationMethod
Display: DeviceManufacturerEvaluationMethod
Definition:
Code assigned to indicate a relevant fact within the context of the evaluation of a reported product. There are a number of concept types including the status of the evaluation, the type of evaluation findings, and the type of activity carried out as part of the evaluation process.

Examples include: Actual device involved in incident was evaluated, electrical tests performed, visual examination.


Code: DeviceManufacturerEvaluationResult
Display: DeviceManufacturerEvaluationResult
Definition:
Code assigned to indicate an outcome of the manufacturer's investigation of a product for which a defect has been reported.

Examples include:.component/subassembly failure: air cleaner, computer-, imaging system-, microprocessor-controlled device problem: cache memory, design -- not fail safe.


Code: PertinentReactionRelatedness
Display: PertinentReactionRelatedness
Definition:
A code to capture the reporter's assessment of the extent to which the reaction is related to the suspect product reported in the ICSR.

Example concepts include: related, not related, possibly related and unlikely related.


Code: ProductCharacterization
Display: ProductCharacterization
Definition:
A code that characterizes the role that the primary reporter felt that the suspect intervention -- either a substance administration or a device related procedure - played in the incident being reported. This code will capture the primary reporter's assessment of the role that the suspect product played in the incident reported in the ICSR.

Examples include: Suspect, Concomitant, Interacting, Re-challenge.


Code: SubjectReaction
Display: SubjectReaction
Definition:
A code to capture the kind of reaction that was suffered by the investigated subject, and that is being reported in the ICSR. At this point, SNOMED or MedDRA have been suggested as code systems to be used for providing this information.

Example concepts include hives, swelling, rash, anaphylactic shock.


Code: SubjectReactionEmphasis
Display: SubjectReactionEmphasis
Definition:
Code that captures the emphasis that the reporter placed on this reaction.

Examples include: highlighted by the reporter, NOT serious, Not highlighted by the reporter, NOT serious, Highlighted by the reporter, SERIOUS, Not highlighted by the reporter, SERIOUS.


Code: SubjectReactionOutcome
Display: SubjectReactionOutcome
Definition:
Code that captures the type of outcome from an individual outcome of a reaction to the suspect product reported in the ICSR.

Examples include: Recovered/resolved. Recovering/resolving, Not recovered/not resolved, Recovered/resolved with sequelae, Fatal.


Code: IntoleranceValue
Display: IntoleranceValue
Definition:
Codes identifying pariticular groupings of allergens and other agents which cause allergies and intolerances. E.g. the drug, allergen group, food or environmental agent which triggers the intolerance


Code: IsolateObservationValue
Display: IsolateObservationValue
Definition:
**Description:**Used to code and identify the Isolate observation result value when a coded result is reported.

**Examples:**

 *  Heavy growth
 *  Scant growth
 *  Moderate growth


Code: IssueTriggerObservationValue
Display: IssueTriggerObservationValue
Definition:
The combined domain for different types of coded observation issue triggers, such as diagnoses, allergies, etc.


Code: KnowledgeSubjectObservationValue
Display: KnowledgeSubjectObservationValue
Definition:
Observation values that document the types of observations belonging to the domain KnowledgeSubjectObservationType.


Code: KnowledgeSubTopicObservationValue
Display: KnowledgeSubTopicObservationValue
Definition:
Observation values that document the types of observations belonging to the domain KnowledgeSubTopicObservationType.


Code: LabResultObservationValue
Display: LabResultObservationValue
Definition:
**Description:** Used to code and identify the laboratory result value when a coded result is reported.

**Examples:** 

 *  Sickle cell trait
 *  Hereditary Spherocytosis
 *  Deficiency of butyryl-CoA dehydrogenase


Code: MeasureAttributeObservationValue
Display: MeasureAttributeObservationValue
Definition:
Observation values used for various types of coded measure attributes in a health quality measure (eMeasure).


Code: MeasureAttributeItemsCountedObservationValue
Display: MeasureAttributeItemsCountedObservationValue
Definition:
Observation values used for an items counted measure attribute in a health quality measure (eMeasure).


Code: MeasureAttributeJurisdictionObservationValue
Display: MeasureAttributeJurisdictionObservationValue
Definition:
Observation values used for a jurisdiction measure attribute in a health quality measure (eMeasure).

**Examples:** 

 *  ISO Country codes
 *  State and County codes
 *  FIPS value sets of postal codes
 *  districts
 *  regions


Code: MeasureAttributeReporterTypeObservationValue
Display: MeasureAttributeReporterTypeObservationValue
Definition:
Observation values used for a reporter type measure attribute in a health quality measure (eMeasure).

**Examples:** 

 *  Laboratory
 *  Healthcare Providers
 *  Hospitals
 *  Healthcare facilities that are NOT hospitals
 *  Schools
 *  Pharmacists
 *  Veterinary lab
 *  Veterinarian
 *  Prison/Jail
 *  Institutions
 *  Employers


Code: MeasureAttributeServiceDeliveryLocationObservationValue
Display: MeasureAttributeServiceDeliveryLocationObservationValue
Definition:
Observation values used for a service delivery location measure attribute in a health quality measure (eMeasure).


Code: ObservationMeasureScoring
Display: ObservationMeasureScoring
Definition:
Observation values used to indicate the type of scoring (e.g. proportion, ratio) used by a health quality measure.


Code: ObservationMeasureType
Display: ObservationMeasureType
Definition:
Observation values used to indicate whether a health quality measure is used to sample a process or outcome over time.


Code: ObservationCaseStatusValue
Display: ObservationCaseStatusValue
Definition:
**Description:** A code used to identify the status of a case. Used with the OBS ActClass.

**Examples:**

 *  Suspect
 *  Confirmed
 *  Probable


Code: ObservationCriteriaValue
Display: ObservationCriteriaValue
Definition:
**Description:**Type of coded observation values in evaluating reference ranges.

**Examples:**

 *  Surgically transgendered transsexual, female-to-male
 *  AIDS-associated disorder
 *  Asian race


Code: ObservationOutbreakExtentValue
Display: ObservationOutbreakExtentValue
Definition:
**Description:** A code used to identify the extent of an outbreak. Used with the OBS.

**Examples:**

 *  Local
 *  Regional
 *  National


Code: ObservationPopulationInclusionType
Display: ObservationPopulationInclusionType
Definition:
Observation values used to assert that a subject falls into a particular population.

**Examples:**

 *  Included in denominator
 *  Included in numerator


Code: PreferenceStrengthObservationValue
Display: PreferenceStrengthObservationValue
Definition:
Values that indicate how important a preference is to the target of the reporter.

**Examples:** 

 *  Very Important
 *  Important
 *  Suggested


Code: PublicHealthCaseObservationValue
Display: PublicHealthCaseObservationValue
Definition:
**Description:** The PublicHealthCaseObservationValue is used to identify the primary condition or disease associated with a Public Health Case.. This concept domain is intended to be used with the CASE Act class code and the ObservationInvestigationType ActCode concept domain.

**Examples:**

 *  Tuberculosis
 *  Lyme Disease
 *  SARS
 *  Lung Cancer


Code: OutbreakObservationValue
Display: OutbreakObservationValue
Definition:
**Description:** The OutbreakObservationValue is used to identify the primary condition or disease associated with an Outbreak. This concept domain is intended to be used with the OUTB Act class code and the ObservationPublicHealthOutbreakType ActCode concept domain.

**Examples:**

 *  Tuberculosis
 *  Lyme Disease
 *  SARS


Code: SecurityObservationValue
Display: SecurityObservationValue
Definition:
Observation values used to indicate security observation metadata.

**Examples:** 

 *  Codes conveying the classification of an IT resource, such as confidentiality codes
 *  Codes conveying privacy law, sensitivity, and consent directive types governing an IT resource
 *  Codes conveying dissemination controls, handling caveats, purpose of use, refrain policies, and obligations to which an IT resource custodian or receiver must comply.
 *  Codes conveying an IT resource completeness, veracity, reliability, trustworthiness, and provenance
 *  Codes conveying the mechanism used to preserve the accuracy and consistency of an IT resource such as a digital signature and a cryptographic hash function
 *  Codes conveying the mechanism used to make authorized alterations of an IT resource, such as translation, masking, and anonymization

*Usage Note:* SecurityObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityObservationType code. \[FIPS 188\]


Code: SecurityCategoryObservationValue
Display: SecurityCategoryObservationValue
Definition:
Security observation values used to indicate security category metadata.

**Examples:** Codes conveying the category of an IT resource such as:

 *  applicable privacy policy
 *  sensitivity
 *  consent directive type

*Usage Note:* SecurityCategoryObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityCategoryObservationType code. \[FIPS 188\]


Code: SecurityClassificationObservationValue
Display: SecurityClassificationObservationValue
Definition:
Security observation values used to indicate security classification metadata.

**Examples:** Codes conveying the classification of an IT resource, such as confidentiality codes.

*Usage Note:* SecurityClassificationObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityClassificationObservationType code. \[FIPS 188\]


Code: SecurityControlObservationValue
Display: SecurityControlObservationValue
Definition:
Security observation values used to indicate security control metadata.

**Examples:** Codes conveying dissemination controls, handling caveats, purpose of use, and obligations to which an IT resource custodian or receiver must comply.

*Usage Note:* SecurityControlObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityControlObservationType code. \[FIPS 188\]


Code: SecurityIntegrityObservationValue
Display: SecurityIntegrityObservationValue
Definition:
Security observation values used to indicate security integrity metadata.

**Examples:** Codes conveying an IT resource:

 *  veracity
 *  reliability
 *  trustworthiness
 *  provenance

*Usage Note:* SecurityIntegrityObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityIntegrityObservationType code. \[FIPS 188\]


Code: SecurityAlterationIntegrityObservationValue
Display: SecurityAlterationIntegrityObservationValue
Definition:
Security observation values used to indicate security alteration integrity metadata.

**Examples:** Codes conveying the mechanisms used to make authorized alteration of an IT resource, such as:

 *  translation
 *  masking
 *  anonymization

*Usage Note:* SecurityAlterationIntegrityObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityAlterationIntegrityObservationType code. \[FIPS 188\]


Code: SecurityDataIntegrityObservationValue
Display: SecurityDataIntegrityObservationValue
Definition:
Security observation values used to indicate security data integrity metadata.

**Examples:** Codes conveying the mechanisms used to preserve the accuracy and consistency of an IT resource such as:

 *  a digital signature
 *  a cryptographic hash function

*Usage Note:* SecurityDataIntegrityObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityDataIntegrityObservationType code. \[FIPS 188\]


Code: SecurityIntegrityConfidenceObservationValue
Display: SecurityIntegrityConfidenceObservationValue
Definition:
Security observation values used to indicate security integrity confidence metadata.

**Examples:** Codes conveying the level of veracity, reliability, and trustworthiness of an IT resource.

*Usage Note:* Codes conveying the level of veracity, reliability, and trustworthiness of an IT resource.


Code: SecurityIntegrityProvenanceObservationValue
Display: SecurityIntegrityProvenanceObservationValue
Definition:
Security observation values used to indicate security alteration integrity metadata.

**Examples:** Codes conveying the provenance of an IT resource such as the entity responsible for a report or assertion relayed "second-hand" about an IT resource.

*Usage Note:* SecurityIntegrityProvenanceObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityIntegrityProvenanceObservationType code. \[FIPS 188\]


Code: SecurityIntegrityProvenanceAssertedByObservationValue
Display: SecurityIntegrityProvenanceAssertedByObservationValue
Definition:
Security observation values used to indicate security integrity provenance asserted by metadata.

**Examples:** Codes conveying the provenance metadata about the entity asserting an IT resource.

*Usage Note:* SecurityIntegrityProvenanceAssertedByObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityIntegrityProvenanceAssertedByObservationType code. \[FIPS 188\]


Code: SecurityIntegrityProvenanceReportedByObservationValue
Display: SecurityIntegrityProvenanceReportedByObservationValue
Definition:
Security observation values used to indicate security integrity provenance reported by metadata.

**Examples:** Codes conveying the provenance metadata about the entity reporting an IT resource.

*Usage Note:* SecurityIntegrityProvenanceReportedByObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityIntegrityProvenanceReportedByObservationType code. \[FIPS 188\]


Code: SecurityIntegrityStatusObservationValue
Display: SecurityIntegrityStatusObservationValue
Definition:
Security observation values used to indicate security integrity status metadata.

**Examples:** Codes conveying the completeness of an IT resource in terms of workflow status such as:

 *  authenticated
 *  legally authenticated
 *  in progress

*Usage Note:* SecurityIntegrityStatusObservationValue codes are members of a security label "tag set" used to populate or "tag" a security label field named by the associated SecurityIntegrityStatusObservationType code. \[FIPS 188\]


Code: SecurityTrustObservationValue
Display: SecurityTrustObservationValue
Definition:
Observation value used to indicate aspects of trust policy applicable to an IT resource (data, information object, service, or system capability).

For example, applicable trust framework, policy, or mechanisms.

*Usage Note:* Security trust metadata values may be used as the trust attribute value populating a computable trust policy, trust credential, trust assertion, or trust label field in a security label and principally used for authentication, authorization, and access control decisions.

SecurityTrustObservationValue may be used as a trust attribute value populating a computable trust policy, trust credential, trust assertion, or trust label field in a security label with trust observation values. The valued trust attributes may be used for used for authentication, authorization, and access control decisions. These may also be used to negotiate trust relationships, adjudicate or bridge trust policies, and to specify requirements for participation in a Trust Domain or for asserting compliance with a Trust Framework.


Code: SecurityTrustAccreditationObservationValue
Display: SecurityTrustAccreditationObservationValue
Definition:
Values for 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.

For example, DirectTrust, Kantara Initiative, Open Identity


Code: SecurityTrustAgreementObservationValue
Display: SecurityTrustAgreementObservationValue
Definition:
Values for security metadata observation made about security requirements with which a security domain must comply. \[ISO IEC 10181-1\] Conveys the agreement of an asserter to comply with jurisdictional, community, or contractual (security domains) codes of conduct which an information custodian requires as a condition of authorizing collection, access, use or disclosure.

For example, DURSA, DIRECT Applicability Statement, HIPAA Covered Entity and Business Associate Agreement, and FTC PHR Vendor, Related Entity, and third party agreements.


Code: SecurityTrustAssuranceObservationValue
Display: SecurityTrustAssuranceObservationValue
Definition:
Values for security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.

For example, authentication, identity proofing, and non-repudiation level of assurance.


Code: SecurityTrustCertificateObservationValue
Display: SecurityTrustCertificateObservationValue
Definition:
Values for 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\]

For example, a single use certificate, dual use certificate, digital signature certificate.


Code: SecurityTrustFrameworkObservationValue
Display: SecurityTrustFrameworkObservationValue
Definition:
Values for 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\]

For example, FICAM, DirectTrust, and HITRUST.


Code: SecurityTrustMechanismObservationValue
Display: SecurityTrustMechanismObservationValue
Definition:
Values for security metadata observation made about a security architecture system component that supports enforcement of security policies.

For example, Digital signature, authorization scheme, and certificate token.


Code: SeverityObservationValue
Display: SeverityObservationValue
Definition:
**Description:** An indication of the seriousness of the subject's condition or issue.

**Examples:** 

 *  Mild
 *  Moderate
 *  Severe


Code: SusceptibilityObservationValue
Display: SusceptibilityObservationValue
Definition:
**Description:**Used to code and identify the Susceptibility Observation result value when a coded result is reported.

**Examples:**

 *  Susceptible
 *  Resistant
 *  Moderately susceptible


Code: ParameterItemSemanticsType
Display: ParameterItemSemanticsType
Definition:
A code indicating the name of a parameter item. ParameterItem classes are defined in the RIM as name-value pairs and this domain provides the name part of the ParameterItem.

**Examples:** Patient Name, Drug Code, Order Effective Date


Code: ConsultantParticipationFunction
Display: ConsultantParticipationFunction
Definition:
**Description:** Identifies functions appropriate to consultant participations.

**Examples:**

 *  cardiologist
 *  anesthetist
 *  dietician


Code: MolecularInteractionFunction
Display: MolecularInteractionFunction
Definition:
Specific functiona that a participant may have in a molecular interaction.

*Examples:* Receptor, allosteric inhibitor, co-factor, catalyst, co-enzyme, competitive inhibitor, etc.


Code: PerformerParticipationFunction
Display: PerformerParticipationFunction
Definition:
**Description:** Identifies functions appropriate to performer participations.

**Examples:**

 *  surgeon
 *  lab technician
 *  janitor


Code: ParticipationType
Display: ParticipationType
Definition:
A code specifying the kind of Participation or involvement the Entity playing the Role associated with the Participation has with regard to the associated Act.

*Constraints:* The Participant.typeCode contains only categories that have crisp semantic relevance in the scope of HL7. It is a coded attribute without exceptions and no alternative coding systems allowed.


Code: ProcedureMethod
Display: ProcedureMethod
Definition:
**Description:**A concept whose description/definition provides additional detail about the means or technique used for the procedure.

**Examples:**

 *  neuromuscular reeducation
 *  functional activity
 *  Laparoscopic Gastric Bypass Roux-en-Y


Code: BloodDonationProcedureMethod
Display: BloodDonationProcedureMethod
Definition:
**Description:** Specific method used to extract the blood from the donor subject.

**Examples:** *No examples supplied with proposal.*


Code: EnteralAdministrationMethodType
Display: EnteralAdministrationMethodType
Definition:
A concept that conveys how a material will be administered enterally.

**Examples:** 

 *  Continuous Tube Feeding
 *  Gravity Drip
 *  Bolus Feeding


Code: QueryRequestLimit
Display: QueryRequestLimit
Definition:
Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application


Code: Race
Display: Race
Definition:
In the United States, federal standards for classifying data on race determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define race, and they recognize the absence of an anthropological or scientific basis for racial classification. Instead, the federal standards acknowledge that race is a social-political construct in which an individual's own identification with one more race categories is preferred to observer identification. The standards use a variety of features to define five minimum race categories. Among these features are descent from "the original peoples" of a specified region or nation. The minimum race categories are American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. The federal standards stipulate that race data need not be limited to the five minimum categories, but any expansion must be collapsible to those categories.

*OpenIssue:* This concept domain definition does not align with current vocabulary practices and is much too US-centric to be appropriate as a "universal" domain.


Code: AssocativeRoleType
Display: AssocativeRoleType
Definition:
A general association between two entities that is neither partitive nor ontological.

*Examples:* affiliate; agent; birthplace.


Code: MutualRelationshipRoleType
Display: MutualRelationshipRoleType
Definition:
**Description:**Concepts which further characterizing the type of mutual relationships. Used only with the abstract code\_RoleClassMutualRelationship.


Code: AgentRoleType
Display: AgentRoleType
Definition:
An entity (player) that acts or is authorized to act on behalf of another entity (scoper).

*Examples:* next of kin; assigned entity; contact.


Code: AdministrativeContactRoleType
Display: AdministrativeContactRoleType
Definition:
**Description:**Indicates the role an entity (player) is playing as the appropriate contact on behalf of another entity (scoper).


Code: AssignedRoleType
Display: AssignedRoleType
Definition:
**Description:** A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClass AssignedEntity. The suggested values from V2.x include clinic receptionist, referral agent, staff physician, courtesy physician, resident, physician assistant, physical therapist, psychiatrist, psychologist, pharmacist, registered nurse, licensed practical nurse, licensed vocational nurse, nurse practitioner, etc.

**Examples:**

 *  Janitor
 *  Chief of Staff
 *  Referral Agent
 *  Security Guard
 *  ICU Runner
 *  Visiting professor

*Open Issue:* There needs to be work undertaken to clean up the hierarchy under this Domain as there seems to be some muddling between D:ProductLifecycleAssginedRoleType and D:ClinicalOrganizationRoleType and this new D:AssignedNonLivingSubjectRoleType. There may be other issues that need improvement in this hierarchy, and there may be some issue with the corresponding hierarchy in the code system. (identified in 11/2014 cycle)


Code: AssignedNonLivingSubjectRoleType
Display: AssignedNonLivingSubjectRoleType
Definition:
A role type that is used to further qualify an inanimate subject playing a role where the playing entity acts or is authorized to act on behalf of a scoping entity.

**Examples:** 

 *  Assistive device for impaired or challenged person
 *  Non-living entities that may participate as assigned therapeutic agents
 *  Entities that may be provided to patients to improve general mood, decrease depression and loneliness, and distract from stress-inducing concerns to improve quality of life.


Code: ProvenanceAssignedDeviceRoleType
Display: ProvenanceAssignedDeviceRoleType
Definition:
A role type, which indicates the type of device that authors or in some manner contributes to the generation, management, and/or transmission of health information, the use of which may be tracked for purposes of determining the provenance of health information. The playing device acts or is authorized to act on behalf of a scoping entity..

**Examples:** 

 *  Patient selected home monitoring device e.g., to detect and report falls
 *  Provider selected medication adherence monitoring, reporting, and alerting device
 *  Provider designated EKG measuring and reporting device


Code: AssignedNonPersonLivingSubjectRoleType
Display: AssignedNonPersonLivingSubjectRoleType
Definition:
**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

*Open Issue:* The definition should be modified to clarify the fact that it is a living non-person subject. (AK 11/2014 cycle)


Code: ClinicalOrganizationRoleType
Display: ClinicalOrganizationRoleType
Definition:
A role of an organization that further classifies the clincial responsibility for the healthcare care delivered during an encounter. E.g. cardiology service, pediatric service, nursing services.


Code: GrantorRoleType
Display: GrantorRoleType
Definition:
**Description:** The specific kinds of roles that issue information privacy grants that permit or prohibit potential actions on information artifacts.

**Examples:**

 *  Parent
 *  Legal Guardian
 *  Health Information Exchange


Code: GrantorOrganizationRoleType
Display: GrantorOrganizationRoleType
Definition:
**Description:** The specific kinds of organizational roles that issue information privacy grants that permit or prohibit potential actions on information artifacts.

**Examples:**

 *  Clearinghouse
 *  Billing Service
 *  Health Information Exchange


Code: GrantorPersonRoleType
Display: GrantorPersonRoleType
Definition:
**Description:** The specific kinds of person roles that issue information privacy grants that permit or prohibit potential actions on information artifacts.

**Examples:**

 *  Self
 *  Parent
 *  Legal Guardian


Code: DeviceOperatorType
Display: DeviceOperatorType
Definition:
Indicates the type of person that is responsible for operating the device related to the incident reported in ICSR.

Examples include: Physician, Nurse, Medical Technician, Respiratory Technician.


Code: HealthcareProviderRoleType
Display: HealthcareProviderRoleType
Definition:
A role type that is used to categorize an entity that delivers health care in an expected and professional manner to a subject in need of health care services.

**Examples:**

 *  Registered Nurse
 *  Physician
 *  Custodial Care Clinic


Code: ICSRReportingRoleType
Display: ICSRReportingRoleType
Definition:
**Description:** A role that is played by a party which is involved in the process originating or managing reports of adverse events or product problems.

**Examples:**

 *  Marketing Authorization Holder
 *  Regulatory Agency
 *  Healthcare Practitioner


Code: PersonalAndLegalAssignedRoleType
Display: PersonalAndLegalAssignedRoleType
Definition:
A "personal and legal" assigned relationship records the role of a person in relation to another person, or a person to himself or herself. These concepts are to be used when recording relationships based on personal or family ties or through legal assignment of responsibility.


Code: ProductLifecycleAssignedRoleType
Display: ProductLifecycleAssignedRoleType
Definition:
A code specifying a type of responsibility that an entity may take on with respect the lifecycle of a product.

**Examples:**

 *  Manufacturer
 *  Distributor
 *  Retailer


Code: ContactRoleType
Display: ContactRoleType
Definition:
**Description:** A role type that is used to further qualify or describe the role of the contact person or organization.

**Examples:**

 *  Legal representative
 *  Primary contact
 *  Alternative contact


Code: GuardianRoleType
Display: GuardianRoleType
Definition:
Qualify the holder or scope of a guardianship relationship over a living subject.

**Examples:**

 *  Guardianship held jointly by separated parents
 *  Guardianship held jointly by parent and another person
 *  Natural guardian
 *  Special guardian
 *  Guardian of property


Code: ProductSafetyReportPartyRoleType
Display: ProductSafetyReportPartyRoleType
Definition:
**Description:**Captures the different roles that are recorded to characterize the qualifications or stations in life of persons or organizations who participate as senders or as receivers of adverse event or product problem reports.

**Example:**Example values may include: physician, healthcare facility, attorney, family member, regulatory agency. Initial effort to find defined concepts for this value set will focus on the HIPAA provider taxonomy.


Code: FormalRelationshipRoleType
Display: FormalRelationshipRoleType
Definition:
A relationship between two entities that is formally recognized, frequently by a contract or similar agreement.

*Examples:* agent; guarantor; patient.


Code: AffiliationRoleType
Display: AffiliationRoleType
Definition:
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.

*Examples:* Business Partner, Business Associate, Colleague


Code: StudentRoleType
Display: StudentRoleType
Definition:
Type of role attendance the covered party has at a recognized educational institution as defined by a particular insurance policy.


Code: EmployeeRoleType
Display: EmployeeRoleType
Definition:
**Description:** A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClass Employee. This specifies the relationship the staff person has with the institution for whom he/she provides services.

**Examples:**

 *  Employee
 *  Volunteer
 *  Consultant


Code: InvestigatedSubjectRoleType
Display: InvestigatedSubjectRoleType
Definition:
**Description:** A code further classifying the type of investigated subject role. Used with the INVSBJ role class code.

**Examples:**

 *  Case subject
 *  Suspect
 *  Person of interest


Code: QualifiedRoleType
Display: QualifiedRoleType
Definition:
**Description:** A category to which a person can be assigned on the basis of professional qualification, experience, and/or job assignment.

**Examples:**

 *  Physician
 *  Registered Nurse
 *  Product Quality Manager


Code: PractitionerCertifiedEntityType
Display: PractitionerCertifiedEntityType
Definition:
Defines types of certifications for practitioners

*OpenIssue:* This concept domain should be reviewed to determine whether it needs a "ConceptualSpaceForClassCode" property to link to a RIM classCode.


Code: PersonalRelationshipRoleType
Display: PersonalRelationshipRoleType
Definition:
**Description:** Types of personal relationships between two living subjects.

**Examples:**

 *  Parent
 *  sibling
 *  unrelated friend
 *  neighbor


Code: FamilyMemberRelationshipRoleType
Display: FamilyMemberRelationshipRoleType
Definition:
The type of familial relationship between a living subject and another living subject.

**Examples:**

 *  Father
 *  Mother
 *  Uncle


Code: PassiveRoleType
Display: PassiveRoleType
Definition:
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.

*Examples:* birthplace; owned entity; used entity.


Code: IncidentalServiceDeliveryLocationRoleType
Display: IncidentalServiceDeliveryLocationRoleType
Definition:
Types of locations,that are not designed for the purpose of providing health care services but where care provision takes place.

**Examples:**

 *  Accident site
 *  Patient's residence
 *  School
 *  Work site


Code: IdentifiedEntityType
Display: IdentifiedEntityType
Definition:
**Definition:** A code representing the type of identifier that has been assigned to the identified entity (IDENT).

**Examples:** Example values include Social Insurance Number, Product Catalog ID, Product Model Number.


Code: PersonIdentifierRoleType
Display: PersonIdentifierRoleType
Definition:
Types of identifiers for persons.

**Examples:** 

 *  Social insurance number
 *  Passport number
 *  Drivers license number
 *  Jurisdiction health number


Code: SpecimenIdentifierRoleType
Display: SpecimenIdentifierRoleType
Definition:
**Description:** A role by which one can communicate additional identifiers for a specimen.

**Examples:**

 *  specimen identifier
 *  accession identifier
 *  container identifier


Code: MolecularBondRoleType
Display: MolecularBondRoleType
Definition:
The nature of the bonds by which two molecular parts may be connected.

*Examples:* (1) simple bonds such as, single bond, double bond, triple bond, (2) specialized bonds such as peptide bond, disulfide bond, etc., (3) weak bonds such as van-der-Waals, chelate, and ion-associations.


Code: MolecularFeatureRoleType
Display: MolecularFeatureRoleType
Definition:
The generalization of molecular parts (partitive role) and molecular bonds (associative role), or possibly any other role type used for the expression of structural molecular features.

*Examples:* (1) acetyl group (a moiety), (2) disulfide bond (a bond), (3) O-linked glycosylation (a moiety).


Code: ProductProcessingOrganizationRoleType
Display: ProductProcessingOrganizationRoleType
Definition:
**Description:** Indicates the role that an organization takes in the process by which a product goes from an original manufacturer to the eventual consumer.

**Examples:**Manufacturer, re-processor

**Note:**These two values are currently used in adverse event and product problem reporting.


Code: ProductRegulatoryServicesLocationRoleType
Display: ProductRegulatoryServicesLocationRoleType
Definition:
**Description:** Provides the description of the role of a place in terms of its provision of services and functions in the product regulatory domain.

**Examples:**

 *  pharmacovigilance masterfile location
 *  COSHH (Control of Substances Hazardous to Health) masterfile location
 *  regulatory dossier storage location
 *  batch release masterfile location


Code: DistributedMaterialRoleType
Display: DistributedMaterialRoleType
Definition:
**Description:**Codes that further characterize the distribution of a material. Used only with the DST (distributed material) role classCode.

**Examples:**Intensive distribution, Selective distribution and Exclusive distribution.


Code: ManufacturedProductRoleType
Display: ManufacturedProductRoleType
Definition:
**Description:**A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClass ManufacturedProduct.


Code: VisionProductRoleType
Display: VisionProductRoleType
Definition:
**Description:**A role type that is used to further qualify an entity playing a role where the role is that of a vision product such as lenses, frames, etc.


Code: RegulatedProductRoleType
Display: RegulatedProductRoleType
Definition:
**Description:**Codes that further characterize a regulated product role. Used only with the RGPR (regulated product) role classCode.

**Example:** Regulated drug and regulated device.


Code: RetailedMaterialRoleType
Display: RetailedMaterialRoleType
Definition:
**Description:**Codes that further characterize the association of a material playing the role of a retailed material to the scoper which retails the material. Used only with the RET (retailed material) role classCode.

**Examples:** Department store, Self-service and Online.


Code: TheraputicAgentRoleType
Display: TheraputicAgentRoleType
Definition:
**Description:**Codes that further characterize the Theraputic Agent as a manufactured product. Used only with the THER (therapeutic agent) role classCode.

**Examples:** Generic and Brand name.


Code: WarrantedProductRoleType
Display: WarrantedProductRoleType
Definition:
**Description:**Codes that further characterize a warranted product role. Used only with the WRTE (warranted product) role classCode.

**Example:** Express warranty, Implied Warranty and Lifetime Warranty.


Code: ProvenancePassiveDeviceRoleType
Display: ProvenancePassiveDeviceRoleType
Definition:
A role type, which indicates the type of device that in some manner contributes to the generation, management, and/or transmission of health information, the use of which may be tracked for purposes of determining the provenance of health information. The playing device is passive in these roles in the sense that the device is not authorized to act on behalf of a scoping entity.

**Examples:** 

 *  Software that aggregates pre-existing content to facilitate the authorship of a new artifact by an assigned entity
 *  Software that translates pre-existing content to facilitate the management of that content by an assigned entity
 *  Software that transmits content to facilitate the exchange of that content by an assigned entity
 *  Privacy protective software that facilitates privacy protection and security enforcement by filtering health information and applying protections such as de-identification, masking, or redaction, and privacy marking.


Code: TerritorialAuthorityRoleType
Display: TerritorialAuthorityRoleType
Definition:
**Description:** Concepts which further characterizing the type of territorial authority. Used only with the TERR (territorial authority) role classCode.

**Example:** public health authority, judicial authority and national authority.


Code: ICSRParticipantRoleQualificationType
Display: ICSRParticipantRoleQualificationType
Definition:
**Description:**Different types of qualification that could be applicable for a party involved in sending or receiving a case safety report, providing the original notification or report of an adverse event or product problem.

**Examples:**

 *  Physician
 *  Veterinarian
 *  Lawyer
 *  Member of the public


Code: IDMPRoleCodeType
Display: IDMPRoleCodeType
Definition:
Defines elements of the IDMP model, whether concepts defined by role, or relationships between concepts defined by role, that cannot otherwise easily be distinguished within the Common Product Model structures and associated vocabulary. This domain is a collector for the different types of semantics associated with the IDMP role concept spaces.


Code: IDMPProductType
Display: IDMPProductType
Definition:
Provides a set of values for defining the type of Pharmaceutical Product that is related to a PhPID. This in turn determines the type of information that may be conveyed when using the Common Product Model as a vehicle for IDMP model data.

**Examples:**

 *  Chemical Type
 *  Radionuclides (radioactive) Type
 *  Biological Substance


Code: IDMPRelationType
Display: IDMPRelationType
Definition:
Provides a set of values for defining the relationship between different concepts when using the Common Product Model as a vehicle for IDMP model data

**Examples:**

 *  Medicinal identifier
 *  Pharmaceutical identifier
 *  Underlying pharmaceutical concept identifier


Code: OntologicalRoleType
Display: OntologicalRoleType
Definition:
A relationship in which the scoping Entity defines or specifies what the playing Entity is. Thus, the player's "being" (Greek: ontos) is specified.

*Examples:* sameness; instance; generalization.


Code: EquivalenceEvaluationRoleType
Display: EquivalenceEvaluationRoleType
Definition:
A code specifying in what way two products are considered equivalent. One example for a value set in the US can be found in U.S. FDA "Orange Book" at the FDA website but the concept is universal and not a U.S. only issue.

**Examples:**

 *  No known or suspected bioequivalence problems
 *  Potential bioequivalence problems have been resolved with evidence supporting bioequivalence
 *  Bioequivalence problems have not been fully resolved


Code: PartitiveRoleType
Display: PartitiveRoleType
Definition:
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.

*Examples:* part; member; ingredient.


Code: LocatedEntityRoleType
Display: LocatedEntityRoleType
Definition:
**Description:** Constrains the concepts used to further characterize the association between an entity and itaTMs location. Used only with the LOCE (located entity) role classCode.

**Example:** home, business and vacation home.


Code: MemberRoleType
Display: MemberRoleType
Definition:
A classification for further qualifying an entity playing a Member RoleClass.

*Examples:* 

 *  tribal member
 *  elected member
 *  *ex officio* member
 *  part-time member


Code: PartRoleType
Display: PartRoleType
Definition:
**Description:** Concepts which further characterizing the association two Entities where the playing Entity (the part) is a component of the whole (scoper). Used only with the PART (part) role classCode.

Example: Body part, organization part and moiety.


Code: MolecularPartRoleType
Display: MolecularPartRoleType
Definition:
The senses in which a molecule may be conceptually or actually divided into parts.

*Examples:* 

1.  sub-unit of a protein (i.e., sequences held together usually by disulfide bonds);
2.  domain of a protein or component of a nucleic acid sequence (i.e., a sub-sequence identified to have a certain folding structure or function, e.g. signaling peptide of a protein precursor or promoter and open reading frame of a nucleic acid);
3.  residue on a molecular base skeleton; atom of a molecule (e.g., to identify substitution with a radioactive isotope);
4.  dissociable ion.

*UsageNotes:* The specific code system and concepts are left to be externally defined. However, when the positionNumber attribute is to be used with the part role to indicate where the part is placed, the part role code must specify how the position number vector is to be interpreted. For example, for subunits of a protein oligomer (such as fibrinogen) held together by disulfide bonds, the part relationship would need to specify the position of the links


Code: OrganizationPartRoleType
Display: OrganizationPartRoleType
Definition:
Concepts which further characterize the association between two Entities which are organizations where the playing Entity (the part) is a component of the whole (scoper). Used only with the PART (part) role classCode.

**Examples:** 

 *  business unit
 *  department
 *  executive team


Code: SpecimenRoleType
Display: SpecimenRoleType
Definition:
**Description:** Further classifies the types of specimen roles.

**Examples:** Examples include Quality control specimens, grouped specimens and patient specimens.


Code: DerivedSpecimenRoleType
Display: DerivedSpecimenRoleType
Definition:
**Description:** Specimen types which further classify the types of specimens that are derived from other specimens.

**Examples:** Examples include specimen sections and specimen components.


Code: RoleLinkStatus
Display: RoleLinkStatus
Definition:
**Description:**The status of an instance of the RIM RoleLink class.

**Constraint:** It is intended to be used based on usage of the ParticipationType concept domain.

**Examples:** 

 *  Active
 *  No longer active
 *  Nullified


Code: RoleLinkType
Display: RoleLinkType
Definition:
A code specifying the kind of connection represented by this RoleLink, e.g., has-part, has-authority.


Code: RouteOfAdministration
Display: RouteOfAdministration
Definition:
**Description:**This describes which path the administered medication takes to get into the body or into contact with the body and constitutes part of the *where* (the other part being site - see below). It is the *way in* or the course the medication must take to get to its destination.

Note that a path is in no sense a description of a *final destination*; it is a stylized description of the path taken. For example, an oral antibiotic may be used to treat a severe infection on a toe; the oral route is used to get the medicine to be able to reach and treat the infection in the toe. For some specific routes of administration there may be an incidental sense of *final destination*, for example an ocular administration usually occurs when treatment of an eye condition is required. However, this is in no sense definitional: rectal administration of a medicine may be for a local effect (a steroid foam for treatment of colitis) or for a systemic effect (metronidazole for treatment of infection). The route of administration of a medicine should only be a description of the path taken and not the form.

**Examples:**

 *  oral
 *  rectal
 *  intravenous (IV)
 *  subcutaneous (SC)
 *  intramuscular (IM)


Code: Sequencing
Display: Sequencing
Definition:
**DESCRIPTION:**

Specifies direction of sort.

**Examples:**

 *  Ascending
 *  Descending
 *  None


Code: TransmissionRelationshipType
Display: TransmissionRelationshipType
Definition:
A codes specifying the meaning and purpose of every TransmissionRelationship instance. Each of the values implies specific constraints to what kinds of Transmission objects can be related and in which way.


Code: PatientClass
Display: Patient Class (0004)
Definition:
The domain of possible values that systems to categorize patients by site in HL7 Version 2.x interfaces.


Code: AdmissionType
Display: Admission Type (0007)
Definition:
The domain of possible values for the circumstances under which the patient was or will be admitted.


Code: AcknowledgmentCode
Display: Acknowledgment code (0008)
Definition:
The domain of possible values for acknowledgment codes used in Version 2.x message.  For details of usage, see message processing rules in the published Standard.


Code: BillingStatus
Display: Billing Status (0022)
Definition:
The domain of possible values for whether the particular insurance has been billed and, if so, the type of bill.  No suggested values.


Code: FeeSchedule
Display: Fee Schedule (0024)
Definition:
The domain of possible values for the appropriate fee schedule to be used for this transaction posting.


Code: Charge_PriceIndicator
Display: Charge/Price Indicator (0032)
Definition:
The domain of possible values for which price schedule is to be used for room and bed charges.  No suggested values.


Code: OrderStatus
Display: Order status (0038)
Definition:
The domain of possible values for the status of an order. The purpose of these values are to report the status of an order either upon request (solicited), or when the status changes (unsolicited). The values are not intended to initiate action.  It is assumed that the order status value always reflects the status as it is known to the sending application at the time that a message is sent.  Only the filler can originate these values.


Code: ContractCode
Display: Contract Code (0044)
Definition:
The domain of possible values for the type of contract entered into by the healthcare facility and the guarantor for the purpose of settling outstanding account balances.


Code: ConsentCode
Display: Consent Code (0059)
Definition:
The domain of possible values for the type of consent that was obtained for permission to treat the patient.


Code: Relationship
Display: Relationship (0063)
Definition:
The domain of possible values for an actual personal relationship that the next of kin/associated party has to a patient.


Code: SpecimenActionCode
Display: Specimen Action Code (0065)
Definition:
The domain of possible values for actions to be taken with respect to the specimens that accompany or precede an order.  The purpose of these are to further qualify (when appropriate) the general action indicated by the order control code.


Code: GuarantorType
Display: Guarantor Type (0068)
Definition:
The domain of possible values for the type of guarantor, e.g., individual, institution, etc.  No suggested values.


Code: HospitalService
Display: Hospital Service (0069)
Definition:
The domain of possible values for the treatment or type of surgery the patient is scheduled to receive.


Code: InsurancePlanId
Display: Insurance Plan ID (0072)
Definition:
The domain of possible values for the identifier of an insurance plan with which a transaction should be associated.


Code: InterestRateCode
Display: Interest Rate Code (0073)
Definition:
The domain of possible values for the amount of interest that will be charged the guarantor on any outstanding amounts.


Code: DiagnosticServiceSectionId
Display: Diagnostic Service Section ID (0074)
Definition:
The domain of possible values for a section of a diagnostic service where an observation may be performed.


Code: InterpretationCodes
Display: Interpretation Codes (0078)
Definition:
The domain of possible values for a categorical assessment of an observation value.
Discussion: These interpretation codes are sometimes called "abnormal flags", however, the judgment of normalcy is just one of the common rough interpretations, and is often not relevant. For example, the susceptibility interpretations are not about "normalcy", and for any observation of a pathologic condition, it does not make sense to state the normalcy, since pathologic conditions are never considered "normal."


Code: OutlierType
Display: Outlier Type (0083)
Definition:
The domain of possible values for the type of outlier (i.e. period of care beyond DRG-standard stay in facility) that has been paid.


Code: PerformedBy
Display: Performed by (0084)
Definition:
The domain of possible values for a composite number/name of a person/group that performed a test/procedure/transaction, etc.


Code: ObservationResultStatusCodesInterpretation
Display: Observation Result Status Codes Interpretation (0085)
Definition:
The domain of possible values for observation result status. These codes reflect the current completion status of the results for one Observation Identifier.


Code: PlanId
Display: Plan ID (0086)
Definition:
The domain of possible values for the coding structure that identifies the various plan types (i.e., Medicare, Medicaid, Blue Cross, HMO, etc.).


Code: Pre-admitTestIndicator
Display: Pre-Admit Test Indicator (0087)
Definition:
The domain of possible values for whether the patient must have pre-admission testing done in order to be admitted.


Code: ProcedureCode
Display: Procedure Code (0088)
Definition:
The domain of possible values for a unique identifier assigned to a procedure, if any, associated with a charge.


Code: Re-admissionIndicator
Display: Re-Admission Indicator (0092)
Definition:
The domain of possible values which are used to specify that a patient is being re-admitted to a healthcare facility from which they were discharged, and indicates the circumstances around such re-admission.


Code: ReleaseInformation
Display: Release Information (0093)
Definition:
The domain of possible values for whether the healthcare provider can release information about a patient and what information can be released.


Code: ProcessingId
Display: Processing ID (0103)
Definition:
The domain of possible values for whether the message is part of a production, training or debugging system.


Code: VersionId
Display: Version ID (0104)
Definition:
The domain of possible values which are used to identify an HL7 version in the Version 2.x family of published standards.


Code: TransferToBadDebtCode
Display: Transfer to Bad Debt Code (0110)
Definition:
The domain of possible values for that the account was transferred to bad debts and gives the reason.  No suggested values.


Code: DeleteAccountCode
Display: Delete Account Code (0111)
Definition:
The domain of possible values for that the account was deleted from the file and gives the reason.  No suggested values.


Code: DischargeDisposition
Display: Discharge Disposition (0112)
Definition:
The domain of possible values for the disposition of the patient at time of discharge (i.e., discharged to home, expired, etc.).  No suggested values.  In the US, this field should use the Official Uniform Billing (UB) 04 2008 numeric codes found on form locator 17.


Code: DischargedToLocation
Display: Discharged to Location (0113)
Definition:
The domain of possible values for the healthcare facility to which the patient was discharged.  No suggested values.


Code: ServicingFacilities
Display: Servicing Facilities (0115)
Definition:
The domain of possible values for the healthcare facility with which this visit is associated in a multiple facility environment.  No suggested values.


Code: BedStatus
Display: Bed Status (0116)
Definition:
The domain of possible values for the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not.


Code: OrderControlCodes
Display: Order Control Codes (0119)
Definition:
The domain of possible values which are used to determine the function of the order segment.  Depending on the message, the action specified by one of these control codes may refer to an order or an individual service.


Code: ResponseFlag
Display: Response Flag (0121)
Definition:
The domain of possible values allowing the placer (sending) application to determine the amount of information to be returned from the filler.


Code: ChargeType
Display: Charge Type (0122)
Definition:
The domain of possible values for someone or something other than the patient to be billed for a service.


Code: TransportationMode
Display: Transportation Mode (0124)
Definition:
The domain of possible values for how (or whether) to transport a patient, when applicable, for an ordered service.


Code: ValueType
Display: Value Type (0125)
Definition:
The domain of possible values for the format of the observation value in the Observation Result (OBX).


Code: QuantityLimitedRequest
Display: Quantity Limited Request (0126)
Definition:
The domain of possible values for the maximum length of a query response that can be accepted by a requesting system, and are expressed as units of mesaure of query response objects.


Code: AllergenType
Display: Allergen Type (0127)
Definition:
The domain of possible values fora classification of general allergy categories (drug, food, pollen, etc.).


Code: AccommodationCode
Display: Accommodation Code (0129)
Definition:
The domain of possible values for the fiancial accommodation type of the bed or room which implies the rate to be used when occupied by a patient under specific medical conditions, which determines how it is billed.  No suggested values.


Code: VisitUserCode
Display: Visit User Code (0130)
Definition:
The domain of possible values for categories of a patient's visit with respect to an individual institution's needs, and is expected to be different on a site-specific basis.


Code: ContactRole
Display: Contact Role (0131)
Definition:
The domain of possible values for a relationship role that the next of kin/associated parties plays with regard to a patient. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that issued a referral.


Code: TransactionCode
Display: Transaction Code (0132)
Definition:
The domain of possible values that are used by an institution for the purpose of uniquely identifying a transaction based on the Transaction Type.  For example, procedure, supply item, or test for charges; or to identify the payment medium for payments.


Code: AssignmentOfBenefits
Display: Assignment of Benefits (0135)
Definition:
The domain of possible values which indicate whether an insured person agreed to assign the insurance benefits to a healthcare provider.  If so, the insurance will pay the provider directly.


Code: Yes/noIndicator
Display: Yes/no Indicator (0136)
Definition:
The domain of possible values for either Yes or No used in fields containing binary answers generally user-specified.


Code: MailClaimParty
Display: Mail Claim Party (0137)
Definition:
The domain of possible values for a party to which a claim should be mailed when claims are sent by mail.


Code: EmployerInformationData
Display: Employer Information Data (0139)
Definition:
The domain of possible values for the required employer information data for UB82 form locator 71.  No suggested values.


Code: MilitaryService
Display: Military Service (0140)
Definition:
The domain of possible values for the military branch.  This field is defined by CMS or other regulatory agencies.


Code: MilitaryRank/grade
Display: Military Rank/Grade (0141)
Definition:
The domain of possible values for the military rank/grade of the patient.
Australia: https://en.wikipedia.org/wiki/Australian_Defence_Force_ranks
Canada: http://www.forces.gc.ca/en/honours-history-badges-insignia/rank.page
United States: published in the Defense Travel Administrator's Manual, Appendix M: Military Rank/Civilian Pay Grade Abbreviations and Service Agency Names, http://www.defensetravel.dod.mil/Docs/Training/DTA_App_M.pdf


Code: MilitaryStatus
Display: Military Status (0142)
Definition:
The domain of possible values for the military status of the patient.  This field is defined by CMS or other regulatory agencies.


Code: EligibilitySource
Display: Eligibility Source (0144)
Definition:
The domain of possible values for the source of information about the insured's eligibility for benefits.


Code: CertificationPatientType
Display: Certification Patient Type (0150)
Definition:
The domain of possible values for the category or type of patient for which this certification is requested.


Code: SecondOpinionDocumentationReceived
Display: Second Opinion Documentation Received (0152)
Definition:
The domain of possible values for if accompanying documentation has been received by the provider.  No suggested values.


Code: ValueCode
Display: Value Code (0153)
Definition:
The domain of possible values for the National Uniform Billing Committee (NUBC) code.  In the US, the codes defined in code system 2.16.840.1.113883.6.301.6 nubc-ValueCode-cs are often used.


Code: AcknowledgmentConditions
Display: Accept/Application Acknowledgment Conditions (0155)
Definition:
The domain of possible values which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode.


Code: AllowSubstitution
Display: Allow Substitution (0161)
Definition:
The domain of possible values for whether substitutions are allowed and, if so, the type of substitutions allowed.


Code: AdministrationDevice
Display: Administration Device (0164)
Definition:
The domain of possible values for the mechanical device used to aid in the administration of the drug or other treatment.  Common examples are IV-sets of different types.


Code: AdministrationMethod
Display: Administration Method (0165)
Definition:
The domain of possible values for the specific method requested for the administration of the drug or treatment to the patient.


Code: ProcessingPriority
Display: Processing Priority (0168)
Definition:
The domain of possible values for one or more available priorities for performing the observation or test.


Code: ReportingPriority
Display: Reporting Priority (0169)
Definition:
The domain of possible values for the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority.


Code: DerivedSpecimen
Display: Derived Specimen (0170)
Definition:
The domain of possible values for the parents and children for diagnostic studies, especially in microbiology, where the initial specimen (e.g., blood) is processed to produce results (e.g., the identity of the bacteria grown out of the culture).  The process also produces new "specimens" (e.g., pure culture of staphylococcus, and E. coli), and these are studied by a second order process (bacterial sensitivities). The parents (e.g., blood culture) and children (e.g., penicillin MIC) are identified in such cases.


Code: Citizenship
Display: Citizenship (0171)
Definition:
The domain of possible values for the information related to a person's country citizenship.  No suggested values.


Code: CoordinationOfBenefits
Display: Coordination of Benefits (0173)
Definition:
The domain of possible values for whether this insurance works in conjunction with other insurance plans or if it provides independent coverage and payment of benefits regardless of other insurance that might be available to the patient.


Code: NatureOfService_Test_Observation
Display: Nature of Service/Test/Observation (0174)
Definition:
The domain of possible values for an identification of a test battery, an entire functional procedure or study, a single test value (observation), multiple test batteries or functional procedures as an orderable unit (profile), or a single test value (observation) calculated from other independent observations, typically used as an indicator for Master Files.


Code: MasterFileIdentifierCode
Display: Master File Identifier Code (0175)
Definition:
The domain of possible values which are represented by codes identifying HL7 Versions 2.x Master Files.


Code: ConfidentialityCode
Display: Confidentiality Code (0177)
Definition:
The domain of possible values for the degree to which special confidentiality protection should be applied to the observation.


Code: x_BasicConfidentialityKind
Display: x_BasicConfidentialityKind
Definition:
Domain of possible values for basic confidentiality, as used and defined in the CDA base R2 standard.


Code: V2ResponseLevel
Display: Response Level (0179)
Definition:
The domain of possible values for application response levels defined for a given Master File Message at the MFE segment level, and used for MFN-Master File Notification message.


Code: MfnRecord-levelErrorReturn
Display: MFN Record-level Error Return (0181)
Definition:
The domain of possible values for the status of the requested update.  Site-defined table, specific to each master file being updated via this transaction.


Code: Department
Display: Department (0184)
Definition:
The domain of possible values for the institution department to which this person reports or belongs.  No suggested values.


Code: PreferredMethodOfContact
Display: Preferred Method of Contact (0185)
Definition:
The domain of possible values for which of a group of multiple phone numbers is the preferred method of contact for this person.


Code: EthnicGroup
Display: Ethnic Group (0189)
Definition:
The domain of possible values further defining a patient's ancestry.  In the US, a current use is to use these codes to report ethnicity in line with US federal standards for Hispanic origin.


Code: TelecommunicationUseCode
Display: Telecommunication Use Code (0201)
Definition:
The domain of possible values for specifying a specific use of a telecommunication number.  Best practice is to use this concept whenever a telecommunication number or access string is specified.


Code: TelecommunicationEquipmentType
Display: Telecommunication Equipment Type (0202)
Definition:
The domain of possible values  for specifying a type of telecommunication equipment.  Best practice is to use this concept whenever a telecommunication number or access string for particular equipment is specified.


Code: OrganizationalNameType
Display: Organizational Name Type (0204)
Definition:
The domain of possible values that specify the type of name for an organization i.e., legal name, display name.


Code: PriceType
Display: Price Type (0205)
Definition:
The domain of possible values to identify the intent for the dollar amount on a pricing transaction.


Code: SegmentActionCode
Display: Segment Action Code (0206)
Definition:
The domain of possible values for actions to be applied for segments when an HL7 version 2 interface is operating in "action code mode" (a kind of update mode in the Standard).


Code: QueryResponseStatus
Display: Query Response Status (0208)
Definition:
The domain of possible values defining precise response status concepts in support of HL7 Version 2 query messaging.  It is commonly used to indicate no data is found that matches the query parameters, but no error.


Code: V2RelationalOperator
Display: Relational Operator (0209)
Definition:
The domain of possible values to define the relationship between HL7 segment field names identified in a query construct.


Code: RelationalConjunction
Display: Relational Conjunction (0210)
Definition:
The domain of possible values used with relational operator values to group more than one segment field name.


Code: AlternateCharacterSets
Display: Alternate Character Sets (0211)
Definition:
The domain of possible values that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte.


Code: Nationality
Display: Nationality (0212)
Definition:
The domain of possible values that identify the nation or national grouping to which the person belongs.  This information may be different from a person’s citizenship in countries in which multiple nationalities are recognized (for example, Spain: Basque, Catalan, etc.).


Code: PurgeStatusCode
Display: Purge Status Code (0213)
Definition:
The domain of possible values that define the state of a visit relative to its place in a purge workflow.


Code: SpecialProgramCode
Display: Special Program Code (0214)
Definition:
The domain of possible values that record a health insurance program required for healthcare visit reimbursement.


Code: PublicityCode
Display: Publicity Code (0215)
Definition:
The domain of possible values for a level of publicity of information about a patient for a specific visit.


Code: PatientChargeAdjustment
Display: Patient Charge Adjustment (0218)
Definition:
The domain of possible values that indicate which adjustments should be made to a guarantor’s charges.  For example, when a hospital agrees to adjust a guarantor’s charges to a sliding scale.  No suggested values.


Code: RecurringServiceCode
Display: Recurring Service Code (0219)
Definition:
The domain of possible values that indicate whether a treatment is continuous.  No suggested values.


Code: V2LivingArrangement
Display: Living Arrangement (0220)
Definition:
The domain of possible values characterizing the situation that patient-associated parties live in at their residential address.


Code: ContactReason
Display: Contact Reason (0222)
Definition:
The domain of possible values that indicate a reason for contacting a guarantor, for example, to phone a guarantor if payments are late.  No suggested values.


Code: LivingDependency
Display: Living Dependency (0223)
Definition:
The domain of possible values identifying specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient's healthcare needs.


Code: EscortRequired
Display: Escort Required (0225)
Definition:
The domain of possible values indicating whether a patient must be accompanied while travelling to a diagnostic service department.


Code: ManufacturersOfVaccines
Display: Manufacturers of Vaccines (code=MVX) (0227)
Definition:
The domain of possible values for the organization that manufactures a vaccine. The values are maintained by the US Centers of Disease Control.  Note that the source of truth for these code values are maintained by the CDC, and the code system may be accessed at URL: https://phinvads.cdc.gov/vads/SearchCodeSystems_search.action?searchOptions.searchText=PH_ManufacturersOfVaccinesMVX_CDC_NIP.  The value set is also maintained by the CDC, and may be accessed at URL: https://phinvads.cdc.gov/vads/SearchValueSets_search.action?searchOptions.searchText=PHVS_ManufacturersOfVaccinesMVX_CDC_NIP


Code: DrgPayor
Display: DRG Payor (0229)
Definition:
The domain of possible values that identify a Diagnostic Resource Group Payor.  US Realm.  No suggested values.


Code: Non-concurCode_Description
Display: Non-Concur Code/Description (0233)
Definition:
The domain of possible values that specify a non-concur code and description for a denied request, used in insurance claims processing.  No suggested values.


Code: ReportTiming
Display: Report Timing (0234)
Definition:
The domain of possible values to identify the time span of a report or the reason for a report sent to a regulatory agency.


Code: EventExpected
Display: Event Expected (0239)
Definition:
The domain of possible values to communicate whether an event has been judged to be expected or unexpected.


Code: PatientOutcome
Display: Patient Outcome (0241)
Definition:
The domain of possible values to describe the overall state of a patient as a result of patient care.


Code: PrimaryObserversQualification
Display: Primary Observer's Qualification (0242)
Definition:
The domain of possible values to provide a general description of the kind of health care professional who provided the primary observation.


Code: IdentityMayBeDivulged
Display: Identity May Be Divulged (0243)
Definition:
The domain of possible values to define whether the primary observer has given permission for their identification information to be provided to a product manufacturer.


Code: SingleUseDevice
Display: Single Use Device (0244)
Definition:
The domain of possible values that indicate whether a product is designed for a single use.  No suggested values.


Code: ProductProblem
Display: Product Problem (0245)
Definition:
The domain of possible values that indicate if a product problem would exist if a product malfunction could lead to death or serious injury.


Code: ProductAvailableForInspection
Display: Product Available for Inspection (0246)
Definition:
The domain of possible values that indicate that the product is available for analysis. No suggested values.


Code: ProductSource
Display: Product Source (0248)
Definition:
The domain of possible values to describe the evaluation state of a product identified in an incident.


Code: GenericProduct
Display: Generic Product (0249)
Definition:
The domain of possible values that indicate whether the product used is a generic or a branded product. No suggested values.


Code: RelatednessAssessment
Display: Relatedness Assessment (0250)
Definition:
The domain of possible values to provide an estimate of whether an issue with a  product was the cause of an event.


Code: ActionTakenInResponseToTheEvent
Display: Action Taken in Response to the Event (0251)
Definition:
The domain of possible values to define the action taken as a result of an event related to a product issue.


Code: CausalityObservations
Display: Causality Observations (0252)
Definition:
The domain of possible values to record event observations regarding what may have caused a product related event.


Code: IndirectExposureMechanism
Display: Indirect Exposure Mechanism (0253)
Definition:
The domain of possible values to identify the mechanism of product transmission when the product has not been directly applied to the patient.


Code: KindOfQuantity
Display: Kind of Quantity (0254)
Definition:
The domain of possible values that describe the underlying kind of property represented by an observation.  The categories distinguish concentrations from total amounts, molar concentrations from mass concentrations, partial pressures from colors, and so forth.  These are discussed more fully in the LOINC Users' Manual.   They are derived from the approach described in 1995 edition of the IUPAC Silver Book.  These distinctions are used in IUPAC and LOINC standard codes.    The distinctions of true quantities in this table are based primarily on dimensional analyses. The table contains a number of "families," those related to simple counts (number, number concentration, etc.), to mass (mass, mass concentration, etc.), to enzyme activity (catalytic content, catalytic concentration, etc.), and molar or equivalents (substance content, substance concentration).


Code: DurationCategories
Display: Duration Categories (0255)
Definition:
The domain of possible values that classify an observation definition as intended to measure a patient's state at a point in time.


Code: TimeDelayPostChallenge
Display: Time Delay Post Challenge (0256)
Definition:
The domain of possible values to classify an observation definition as being a component of a challenge test.


Code: NatureOfChallenge
Display: Nature of Challenge (0257)
Definition:
The domain of possible values to further describe an observation definition that is characterized as a challenge observation.


Code: RelationshipModifier
Display: Relationship Modifier (0258)
Definition:
The domain of possible values to an observation definition to describe the subject of an observation in relation to a patient.


Code: Modality
Display: Modality (0259)
Definition:
The domain of possible values that define the imaging apparatus expected to be used to acquire an observation.  This table has been removed from the standard as of 2.7 in favor of table 0910.


Code: PatientLocationType
Display: Patient Location Type (0260)
Definition:
The domain of possible values that identify the kind of location described in the location definition.


Code: LocationEquipment
Display: Location Equipment (0261)
Definition:
The domain of possible values that identify the equipment available in a location definition identified as a room or bed.


Code: PrivacyLevel
Display: Privacy Level (0262)
Definition:
The domain of possible values that identify the level of privacy a patient will be afforded when assigned to this location definition.


Code: LevelOfCare
Display: Level of Care (0263)
Definition:
The domain of possible values that identify the level of care a patient may be afforded when assigned to this location definition.


Code: LocationDepartment
Display: Location Department (0264)
Definition:
The domain of possible values used to specify the institution’s department to which a location belongs, or its cost center.


Code: SpecialtyType
Display: Specialty Type (0265)
Definition:
The domain of possible values that identify the specialty of the care professional who is supported when using this location definition.


Code: DaysOfTheWeek
Display: Days of the Week (0267)
Definition:
The domain of possible values to identify the day(s) of the week when a location may be scheduled for appointments.


Code: Override
Display: Override (0268)
Definition:
The domain of possible values that define whether a Charge Description Master description may be overridden or if it must be overridden.


Code: DocumentConfidentialityStatus
Display: Document Confidentiality Status (0272)
Definition:
The domain of possible values that specify the degree to which special confidentiality protection should be applied to  information.  The assignment of data elements to these categories is left to the discretion of the healthcare organization.


Code: DocumentAvailabilityStatus
Display: Document Availability Status (0273)
Definition:
The domain of possible values to define whether a patient document is appropriate or available for use in patient care.


Code: DocumentStorageStatus
Display: Document Storage Status (0275)
Definition:
The domain of possible values to describe the availability of a document in relation to the type of storage.


Code: AppointmentReasonCodes
Display: Appointment reason codes (0276)
Definition:
The domain of possible values that describe the kind of appointment or the reason why an appointment has been scheduled.


Code: FillerStatusCodes
Display: Filler status codes (0278)
Definition:
The domain of possible values that describe an appointment status from the perspective of the entity assigned to fulfill the appointment.


Code: AllowSubstitutionCodes
Display: Allow Substitution Codes (0279)
Definition:
The domain of possible values that indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment.


Code: ReferralType
Display: Referral Type (0281)
Definition:
The domain of possible values that identify the general category of healthcare professional desired to satisfy a referral.


Code: ReferralDisposition
Display: Referral Disposition (0282)
Definition:
The domain of possible values that identify the expected response from the healthcare professional receiving a referral.


Code: ReferralCategory
Display: Referral Category (0284)
Definition:
The domain of possible values that describe the patient care setting where a referral should take place.


Code: InsuranceCompanyIdCodes
Display: Insurance Company ID Codes (0285)
Definition:
The domain of possible values for the identification of the insurance company or other entity that administers the authorizing coverage plan.  No suggested values.


Code: ReferralProviderRole
Display: Provider Role (0286)
Definition:
The domain of possible values that define the relationship between a referral recipient and a patient or between a referral initiator and a patient.


Code: CensusTract
Display: Census Tract (0288)
Definition:
The domain of possible values for the census tract in which the specified address resides.  No suggested values.


Code: County/Parish
Display: County/Parish (0289)
Definition:
The domain of possible values for the county or parish in which the specified address resides.  No suggested values.


Code: SubtypeOfReferencedData
Display: Subtype of Referenced Data (0291)
Definition:
The domain of possible values for a subset of the media subtypes of binary data that are encoded in an ascii structure or stream.


Code: VaccinesAdministered
Display: Vaccines Administered (0292)
Definition:
The domain of possible values for the administered vaccines.   The values are maintained by the US Centers of Disease Control..  The code system is maintained by the CDC, and may be found at URL;  https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.113883.12.292
The value set is maintained by the CDC and may be found at URL: https://phinvads.cdc.gov/vads/ViewValueSet.action?id=ABDEE003-77C3-48E7-B941-EBF92B6B81FC


Code: BillingCategory
Display: Billing Category (0293)
Definition:
The domain of possible values for the billing category codes for any classification systems needed, for example, general ledger codes and UB92 categories.  No suggested values.


Code: TimeSelectionCriteriaParameterClassCodes
Display: Time Selection Criteria Parameter Class Codes (0294)
Definition:
The domain of possible values that describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling.


Code: CpRangeType
Display: CP Range Type (0298)
Definition:
The domain of possible values that specify whether a composite price range is experssed as a flat rate or a percentage.


Code: Encoding
Display: Encoding (0299)
Definition:
The domain of possible values identifying the type of encoding used to represent successive octets of binary data as displayable ASCII characters.  These are defined by IETF; more information may be found at https://www.ietf.org/rfc/rfc1521.txt


Code: NamespaceId
Display: Namespace ID (0300)
Definition:
The domain of possible values for the unique name of the system that stores the data.   It was previously named the Application ID.  No suggested values.


Code: PointOfCare
Display: Point of Care (0302)
Definition:
The domain of possible values for the point where patient care is administered.  It is conditional on Person Location Type (e.g., nursing unit or department or clinic).   No suggested values.


Code: LocationStatus
Display: Location Status (0306)
Definition:
The domain of possible values for the status or availability of the location, such as the bed status.   No suggested values.


Code: CoverageType
Display: Coverage Type (0309)
Definition:
The domain of possible values for the type of insurance coverage or what types of services are covered for the purposes of a billing system.  For example, a physician billing system will only want to receive insurance information for plans that cover physician/professional charges.


Code: PolicyScope
Display: Policy Scope (0312)
Definition:
The domain of possible values for the extent of insurance coverage for a participating member (e.g., single, family, etc.).  No suggested values.


Code: LivingWillCode
Display: Living Will Code (0315)
Definition:
The domain of possible values for whether or not the patient has a living will and, if so, whether a copy fo the living will is on file at the healthcare facility.  If the patient does not have a living will, the value of this field indicates whether the patient was provided information on living wills.


Code: OrganDonorCode
Display: Organ Donor Code (0316)
Definition:
The domain of possible values for whether the patient wants to donate his/her organs and whether an organ donor card or similar documentation is on file with the healthcare organization.


Code: Annotations
Display: Annotations (0317)
Definition:
The domain of possible values for the coded entry associated with a given point in time during the waveform recording.  Note codes beyond 9903 may exist; extensions to this table may be done by incrementing the code value.


Code: DepartmentCostCenter
Display: Department Cost Center (0319)
Definition:
The domain of possible values for the accounting code that identifies the department in order to charge for the item.  No suggested values.


Code: ItemNaturalAccountCode
Display: Item Natural Account Code (0320)
Definition:
The domain of possible values identifying an item in order to charge for the item.  No suggested values.


Code: LocationCharacteristicId
Display: Location Characteristic ID (0324)
Definition:
The domain of possible values for an identifier code to show which characteristic is being communicated with the segment.


Code: LocationRelationshipId
Display: Location Relationship ID (0325)
Definition:
The domain of possible values for an identifier code to show which relationship is being communicated with the segment.


Code: VisitIndicator
Display: Visit Indicator (0326)
Definition:
The domain of possible values for the level on which data are being sent.  It is the indicator used to send data at two levels, visit and account.  HL7 recommends sending an "A" or no value when the data in the message are at the account level or "V" to indicate that the data sent in the message are at the visit level.


Code: EmployeeClassification
Display: Employee Classification (0328)
Definition:
The domain of possible values that specify a person's employee classification.  No suggested values.


Code: SourceType
Display: Source Type (0332)
Definition:
The domain of possible values to indicate (in certain systems) whether a lower level source identifier is an initiate or accept type.


Code: DisabledPersonCode
Display: Disabled Person Code (0334)
Definition:
The domain of possible values that specify to which person the disability information relates in the message.  For example, if the value is PT, the disability information relates to the patient.


Code: RepeatPattern
Display: Repeat Pattern (0335)
Definition:
The domain of possible values that specify the interval between repeated services. See the Comment/Usage Note in the table below, as the table contains both precoordinated codes that may be used in an HL7 field or component and also explanatory patterns illustrating the syntax used to construct expressions using the codes and other modifiers.


Code: AdvancedBeneficiaryNoticeCode
Display: Advanced Beneficiary Notice Code (0339)
Definition:
The domain of possible values for the status of the patient's or the patient's representative's consent for responsibility to pay for potentially uninsured services. This element was introduced to satisfy CMS Medical Necessity requirements for outpatient services in the United States. Includes concepts such as (a) whether the associated diagnosis codes for the service are subject to medical necessity procedures, (b) whether, for this type of service, the patient has been informed that they may be responsible for payment for the service, and (c) whether the patient agrees to be billed for this service.


Code: ProcedureCodeModifier
Display: Procedure Code Modifier (0340)
Definition:
The domain of possible values that specify a procedure code modifier to a procedure code.  Procedure code modifiers are defined by regulatory agencies such as CMS and the AMA.  Multiple modifiers may be reported.  The modifiers are sequenced in priority according to user entry.  This is a requirement of the UB and the 1500 claim forms.  Multiple modifiers are allowed and the order placed on the form affects reimbursement.


Code: MilitaryRecipient
Display: Military Recipient (0342)
Definition:
The domain of possible values that specify a designation as a military recipient.  This field is defined by CMS or other regulatory agencies.  No suggested values.


Code: MilitaryHandicappedProgramCode
Display: Military Handicapped Program Code (0343)
Definition:
The domain of possible values that specify a military program for the handicapped in which a patient is enrolled.  No suggested values.


Code: Patient'sRelationshipToInsured
Display: Patient's Relationship to Insured (0344)
Definition:
The domain of possible values that specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies.


Code: AppealReason
Display: Appeal Reason (0345)
Definition:
The domain of possible values that specify  reasons an appeal was made on a non-concur for certification.  No suggested values.


Code: CountrySubdivision
Display: State/Province (0347)
Definition:
The domain of possible values for the names of the principal country subdivisions (e.g., provinces or states).  The values in the table are country specific.  For example, in the US, the Federal Information Processing Standard (FIPS) alpha codes may be used by local agreement.


Code: OccurrenceCode
Display: Occurrence Code (0350)
Definition:
The domain of possible values that specify the event or occurrence relating to a bill that may affect payer processing.


Code: CweStatuses
Display: CWE statuses (0353)
Definition:
The domain of possible values that represent an exception identifier code; that is, a code that is not defined in the value set (either model or site-extended).  These are occationsally referred to a 'flavors of null' although this set of concepts is specific to the CWE datatype used in Version 2 messaging, and the codes may be used in the 'identifier' component of the 'triplets' in that datatype.


Code: MessageStructure
Display: Message Structure (0354)
Definition:
The domain of possible values of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard.


Code: AlternateCharacterSetHandlingScheme
Display: Alternate Character Set Handling Scheme (0356)
Definition:
The domain of possible values that specify the scheme used when any alternative character sets are specified in the second or later iterations of MSH-18 Character Set, and if any special handling scheme is needed.


Code: PractitionerGroup
Display: Practitioner Group (0358)
Definition:
The domain of possible values for the name and/or code of a group of practitioners to which this practitioner belongs.  No suggested values.


Code: DiagnosisPriority
Display: Diagnosis Priority (0359)
Definition:
The domain of possible values that identify the significance or priority of the diagnosis code.  Note that the codes are numeric, and the number of the code represents the ordinal priority of the associated diagnosis. The predefined codes are the most common, and just a starter set, as the codes are an unbounded list; additional ranked procedures may be signified by incrementing the code value as needed.


Code: Degree/License/Certificate
Display: Degree/License/Certificate (0360)
Definition:
The domain of possible values for an educational degree (e.g., MD).  Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging.


Code: Application
Display: Application (0361)
Definition:
The domain of possible values that identify a sending application among all other applications within the network enterprise.  The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise.  No suggested values.


Code: Facility
Display: Facility (0362)
Definition:
The domain of possible values for the site-specific name for the facility used by this application.  No suggested values.


Code: AssigningAuthority
Display: Assigning Authority (0363)
Definition:
The domain of possible values for a unique name of the system (or organization or agency or department) that creates the data.  No suggested values.


Code: CommentType
Display: Comment Type (0364)
Definition:
The domain of possible values that identify the type of comment text being sent in the specific comment record.


Code: EquipmentState
Display: Equipment State (0365)
Definition:
The domain of possible values that identify the status the equipment was in at the time the transaction was initiated.


Code: Local_RemoteControlState
Display: Local/Remote Control State (0366)
Definition:
The domain of possible values that identify the current state of control associated with the equipment.   Equipment can either work autonomously ('Local' control state) or it can be controlled by another system, e.g., LAS computer ('Remote' control state).


Code: AlertLevel
Display: Alert Level (0367)
Definition:
The domain of possible values that identify the highest level of the alert state (e.g.,highest alert severity) that is associated with the indicated equipment (e.g. processing event, inventory event, QC event).


Code: ContainerStatus
Display: Container Status (0370)
Definition:
The domain of possible values that identify the status of the unique container in which the specimen resides at the time the transaction was initiated.


Code: Additive/Preservative
Display: Additive/Preservative (0371)
Definition:
The domain of possible values for any additive introduced to the specimen before or at the time of collection.  These additives may be introduced in order to preserve, maintain or enhance the particular nature or component of the specimen.


Code: SpecimenComponent
Display: Specimen Component (0372)
Definition:
The domain of possible values that identify the specimen component, e.g., supernatant, sediment, etc.


Code: SystemInducedContaminants
Display: System Induced Contaminants (0374)
Definition:
The domain of possible values that identify the specimen contaminant identifier associated with the specimen in the container.


Code: ArtificialBlood
Display: Artificial Blood (0375)
Definition:
The domain of possible values that identify the artificial blood identifier associated with the specimen.


Code: SpecialHandlingCode
Display: Special Handling Code (0376)
Definition:
The domain of possible values describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing.


Code: OtherEnvironmentalFactors
Display: Other Environmental Factors (0377)
Definition:
The domain of possible values that identify the other environmental factors associated with the specimen in a specific container, e.g., atmospheric exposure.


Code: CarrierType
Display: Carrier Type (0378)
Definition:
The domain of possible values that identify a type of carrier.  Because the geometry can be different, the carrier type should, if possible, express the number of positions in the carrier.  The definition assumes hierarchical nesting using the following phrases: container is located in a carrier, carrier is located in a tray.  No suggested values.


Code: ContainerTrayType
Display: Tray Type (0379)
Definition:
The domain of possible values that identify a type of tray.  Because the geometry can be different, the tray type should, if possible, express the number of positions in the tray.  The definition assumes hierarchical nesting using the following phrases: container is located in a carrier, carrier is located in a tray.  No suggested values.


Code: SeparatorType
Display: Separator Type (0380)
Definition:
The domain of possible values that identify a type of separator being used (e.g., a gel separator in a container - not to be confused with the communication separators).  It is recommended the first table entry be "NO" meaning "No Separator".  No suggested values.


Code: CapType
Display: Cap Type (0381)
Definition:
The domain of possible values that identify a type of cap that is to be used with a container for decapping, piercing or other mechanisms.  No suggested values.


Code: DrugInterference
Display: Drug Interference (0382)
Definition:
The domain of possible values that identify a drug interference  associated with a specimen.  No suggested values.


Code: SubstanceStatus
Display: Substance Status (0383)
Definition:
The domain of possible values identifying the status of the inventoried item.  The status indicates the current status of the substance.


Code: ManufacturerIdentifier
Display: Manufacturer Identifier (0385)
Definition:
The domain of possible values that identify a manufacturer of a substance.  Relevant external code systems may be used, e.g., HIBCC Manufacturers Labeler ID Code (LIC), UPC, NDC, etc.  No suggested values.


Code: ProcessingType
Display: Processing Type (0388)
Definition:
The domain of possible values identifying the processing type that applies to the test code.  If this attribute is omitted, then regular production is the default.


Code: AnalyteRepeatStatus
Display: Analyte Repeat Status (0389)
Definition:
The domain of possible values identifying the repeat status for the analyte/result (e.g. original, rerun, repeat, reflex).  The following are assumptions regarding the table values: Repeated without dilution — performed usually to confirm correctness of results (e.g., in case of results flagged as "Panic" or mechanical failures).  Repeated with dilution — performed usually in the case the original result exceeded the measurement range (technical limits).  Reflex test — this test is performed as the consequence of rules triggered based on other test result(s).


Code: SegmentGroup
Display: Segment Group (0391)
Definition:
The domain of possible values for the optional segment groups which are to be included in a response.


Code: MatchReason
Display: Match Reason (0392)
Definition:
The domain of possible values identifying what search components (e.g., name, birthdate, social security number) of the record returned matched the original query where the responding system does not assign numeric match weights or confidence levels.  It provides a method for passing a descriptive indication of the reason a particular record was found.


Code: MatchAlgorithms
Display: Match Algorithms (0393)
Definition:
The domain of possible values identifying the name or identity of the specific search algorithm to which the RCP-5 Search Confidence Threshold and the QRI-1 Candidate Confidence refer.


Code: CodingSystem
Display: Coding System (0396)
Definition:
The domain of possible values of specifying the coding system.  This table is maintained outside of the published Version 2 standards, and may be found at http://www.hl7.org/Special/committees/vocab/table_0396/index.cfm.


Code: V2Sequencing
Display: Sequencing (0397)
Definition:
The domain of possible values identifying how the field or parameter will be sorted and, if sorted, whether the sort will be case sensitive (the default) or not.


Code: ContinuationStyleCode
Display: Continuation Style Code (0398)
Definition:
The domain of possible values identifying whether it is a fragmented message or part of an interactive continuation message.


Code: CountryCode
Display: Country Code (0399)
Definition:
The domain of possible values that identifies a country of origin for a message.  It will be used primarily to specify default elements, such as currency denominations. The values to be used are those of ISO 3166. The ISO 3166 table has three separate forms of the country code: HL7 specifies that the 3-character (alphabetic) form be used for the country code.


Code: GovernmentReimbursementProgram
Display: Government Reimbursement Program (0401)
Definition:
The domain of possible values for codes that indicate an agency that the practitioner is authorized to bill for medical services.  Existing codes only for use in the United States.


Code: SchoolType
Display: School Type (0402)
Definition:
The domain of possible values for a categorization of an academic institution that grants a degree to a Staff Member.


Code: LanguageAbility
Display: Language Ability (0403)
Definition:
The domain of possible values for codes that indicate the ability that a Staff Member possesses with respect to the language.


Code: LanguageProficiency
Display: Language Proficiency (0404)
Definition:
The domain of possible values which specify the level of knowledge a person possesses with respect to a language ability identified.


Code: OrganizationUnit
Display: Organization Unit (0405)
Definition:
The domain of possible values which specify the hierarchical components of an organization unit, as defined by the institution.  No suggested values.


Code: ParticipantOrganizationUnitType
Display: Participant Organization Unit Type (0406)
Definition:
The domain of possible values that specify the environment in which the provider acts in the role associated with the provider type, and inludes codes for venues outside of formal organized healthcare settings, such as Home. The provider environment is not the specialty for the provider.


Code: ApplicationChangeType
Display: Application Change Type (0409)
Definition:
The domain of possible values that specify a type of change being requested (if NMR query) or announced (if NMD unsolicited update).


Code: SupplementalServiceInformationValues
Display: Supplemental Service Information Values (0411)
Definition:
The domain of possible values that specify supplemental service information sent between a placer system and a filler system for the universal procedure code reported in OBR-4 Universal Service ID. This specifies ordering information detail that is not available in other specific tables for fields in the OBR segment.  These might be details such as whether a study is to be done on the right or left, for example, where the study is of the arm and the order master file does not distinguish right from left, or whether a study is to be done with or without contrast (when the order master file does not make such distinctions).


Code: CategoryIdentifier
Display: Category Identifier (0412)
Definition:
The domain of possible values that specify a category name (term given to a group of service items for the purpose of classification). Examples: Laboratory, Pharmacy, Diagnostic Imaging, etc.  No suggested values.


Code: ConsentIdentifier
Display: Consent Identifier (0413)
Definition:
The domain of possible values that provide an identifier for the consent specified for a service item.  No suggested values.


Code: TransferType
Display: Transfer Type (0415)
Definition:
The domain of possible values that specify a type of hospital receiving a transfer patient, which affects how a facility is reimbursed under diagnosis related group (DRG's), for example, exempt or non-exempt.


Code: TissueTypeCode
Display: Tissue Type Code (0417)
Definition:
The domain of possible values that specify the type of tissue removed from a patient during a procedure.


Code: ProcedurePriority
Display: Procedure Priority (0418)
Definition:
The domain of possible values specifying a number that identifies the significance or priority of the procedure code.


Code: TriageCode
Display: Triage Code (0422)
Definition:
The domain of possible values specifying a patient's prioritization within the context of this abstract.


Code: CaseCategoryCode
Display: Case Category Code (0423)
Definition:
The domain of possible values specifying the reason a non-urgent patient presents to the emergency room for treatment instead of a clinic or physican office.


Code: ProductionClassCode
Display: Production Class Code (0429)
Definition:
The domain of possible values specifying the code and/or text indicating the primary use for which the living subject was bred or grown.


Code: AdmissionLevelOfCareCode
Display: Admission Level of Care Code (0432)
Definition:
The domain of possible values specifying the acuity level assigned to the patient at the time of admission.


Code: PrecautionCode
Display: Precaution Code (0433)
Definition:
The domain of possible values specifying non-clincal precautions that need to be taken with the patient.


Code: PatientConditionCode
Display: Patient Condition Code (0434)
Definition:
The domain of possible values specifying the patient's current medical condition for the purpose of communicating to non-medical outside parties, e.g. family, employer, religious minister, media, etc.


Code: SensitivityToCausativeAgentCode
Display: Sensitivity to Causative Agent Code (0436)
Definition:
The domain of possible values specifying the reason the patient should not be exposed to a substance.


Code: AlertDeviceCode
Display: Alert Device Code (0437)
Definition:
The domain of possible values specifying any type of allergy alert device the patient may be carrying or wearing.


Code: ProviderRole
Display: Provider Role (0443)
Definition:
The domain of possible values for the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.).


Code: NameAssemblyOrder
Display: Name Assembly Order (0444)
Definition:
The domain of possible values specifying the preferred display order of the components of this person name.


Code: IdentityReliabilityCode
Display: Identity Reliability Code (0445)
Definition:
The domain of possible values for the reliability of patient/person identifying data transmitted via a transaction.


Code: HealthCareProviderTypeCode
Display: Health Care Provider Type Code (0452)
Definition:
The domain of possible values for the major grouping of the service or occupation of a practitioner at a specific organization unit.


Code: HealthCareProviderClassification
Display: Health Care Provider Classification (0453)
Definition:
The domain of possible values for the more specific service or occupation within the healthcare provider type of the practitioner at a specific organization unit.


Code: HealthCareProviderAreaOfSpecialization
Display: Health Care Provider Area of Specialization (0454)
Definition:
The domain of possible values for the segment of the population that a health care provider chooses to service, a specific medical service, a specialization in treating a specific disease, or any other descriptive characteristic about a provider’s practice relating to the services rendered of a practitioner at a specific organization unit.


Code: TypeOfBillCode
Display: Type of Bill Code (0455)
Definition:
The domain of possible values specifying the specific type of bill with digit 1 showing type of facility, digit 2 showing bill classification and digit 3 showing frequency.


Code: RevenueCode
Display: Revenue code (0456)
Definition:
The domain of possible values specifying a service line revenue code.  These are claim codes indicating the identifying number for the product or service provided.


Code: OceEditCode
Display: OCE Edit Code (0458)
Definition:
The domain of possible values that specify the edits that result from processing the HCPCS/CPT procedures for a record after evaluating all the codes, revenue codes, and modifiers.


Code: InventoryNumber
Display: Inventory Number (0463)
Definition:
The domain of possible values specifying an identifying stock number, if any, which might be used, for example, as a cross reference for materials management.


Code: FacilityId
Display: Facility ID (0464)
Definition:
The domain of possible values for the facility of the institution for which a specified price is valid.  For use when needing multi-facility pricing.


Code: TqConjunctionId
Display: TQ Conjunction ID (0472)
Definition:
The domain of possible values for that a second timing specification is to follow using the repeat delimiter.


Code: ChargeTypeReason
Display: Charge Type Reason (0475)
Definition:
The domain of possible values for the choice of, and providing the clinical rationale for, a selected charge type.


Code: V2MedicallyNecessaryDuplicateProcedureReason
Display: Medically Necessary Duplicate Procedure Reason (0476)
Definition:
The domain of possible values specifying the reason the procedure code found in OBR-44 Procedure Code is a duplicate of one ordered/charged previously for the same patient within the same date of service and has been determined to be medically necessary.


Code: ControlledSubstanceSchedule
Display: Controlled Substance Schedule (0477)
Definition:
The domain of possible values for the class of the drug or other substance if its usage is controlled by legislation.


Code: SubstanceFormularyStatus
Display: Formulary Status (0478)
Definition:
The domain of possible values for whether or not the pharmaceutical substance is part of the local formulary.


Code: PharmaceuticalSubstances
Display: Pharmaceutical Substances (0479)
Definition:
The domain of possible values for a medical substance or treatment that has been ordered to be given to a patient, as encoded by a pharmacy or treatment supplier.


Code: PharmacyOrderTypes
Display: Pharmacy Order Types (0480)
Definition:
The domain of possible values for the general category of pharmacy order which may be used to determine the processing path the order will take.


Code: OrderType
Display: Order Type (0482)
Definition:
The domain of possible values for whether the order is to be executed in an inpatient setting or an outpatient setting.


Code: AuthorizationMode
Display: Authorization Mode (0483)
Definition:
The domain of possible values of forms of authorization a recorder may receive from the responsible practitioner to create or change an order.


Code: SpecimenType
Display: Specimen Type (0487)
Definition:
The domain of possible values that describe the precise nature of an entity that may be used as the source material for an observation.


Code: RiskCodes
Display: Risk Codes (0489)
Definition:
The domain of possible values for any known or suspected specimen hazards, e.g., exceptionally infectious agent or blood from a hepatitis patient.


Code: SpecimenRejectReason
Display: Specimen Reject Reason (0490)
Definition:
The domain of possible values for the reasons a specimen may be rejected for a specified observation/result/analysis.


Code: SpecimenAppropriateness
Display: Specimen Appropriateness (0492)
Definition:
The domain of possible values for the suitability of the specimen for the particular planned use as determined by the filler.


Code: SpecimenChildRole
Display: Specimen Child Role (0494)
Definition:
The domain of possible values for for child specimens the relationship between this specimen and the parent specimen.


Code: ConsentType
Display: Consent Type (0496)
Definition:
The domain of possible values for to what the subject is consenting, i.e. what type of service, surgical procedure, information access/release or other event.


Code: ConsentDisclosureLevel
Display: Consent Disclosure Level (0500)
Definition:
The domain of possible values to specify how much information was disclosed to the subject as part of the informed consent process.


Code: Non-subjectConsenterReason
Display: Non-Subject Consenter Reason (0502)
Definition:
The domain of possible values to specify a reason consent was granted by a person other than the subject of the consent.


Code: Sequence_ResultsFlag
Display: Sequence/Results Flag (0503)
Definition:
The domain of possible values to specify the sequencing relationship between the current service request and a related service request(s) specified in the same information model structure.


Code: SequenceConditionCode
Display: Sequence Condition Code (0504)
Definition:
The domain of possible values to specify the relationship between the start/end of the related service request(s) and the current service request.


Code: CyclicEntry_ExitIndicator
Display: Cyclic Entry/Exit Indicator (0505)
Definition:
The domain of possible values to specify if this service request is the first or last service request in a cyclic series of service requests.


Code: ServiceRequestRelationship
Display: Service Request Relationship (0506)
Definition:
The domain of possible values to specify an additional or alternate relationship between this service request and other service requests.


Code: ObservationResultHandling
Display: Observation Result Handling (0507)
Definition:
The domain of possible values regarding the handling of a result.  For example, an order may specify that the result (e.g., an x-ray film) should be given to the patient for return to the requestor.


Code: BloodProductProcessingRequirements
Display: Blood Product Processing Requirements (0508)
Definition:
The domain of possible values that specify additional information about the blood component class associated with the Universal Service ID.  The placer of the order can specify any required processing of the blood product that must be completed prior to transfusion to the intended recipient.


Code: BloodProductDispenseStatus
Display: Blood Product Dispense Status (0510)
Definition:
The domain of possible values to specify the current status of the specified blood product as indicated by the filler or placer.  For example, the first status change of a product that may trigger a Blood Product Dispense Status Message occurs when it first becomes linked to a patient and is ready to dispense. The placer system may use the Blood Product Dispense Status Message to request the transfusion service to dispense the product.  When the blood product is delivered or issued to a patient, the status of the blood product would be changed to indicate that it has now been "dispensed".


Code: BpObservationStatusCodesInterpretation
Display: BP Observation Status Codes Interpretation (0511)
Definition:
The domain of possible values to specify the interpretation for the blood product observation status codes.  A status is considered preliminary until a blood product has reached a final disposition for the patient. For example, when the product is first cross-matched and a status message is sent, it would be considered preliminary. When the product is dispensed to the patient, that status would also be considered preliminary.  However, once the product is transfused, the status would be considered final.


Code: CommercialProduct
Display: Commercial Product (0512)
Definition:
The domain of possible values that specify a commercial product.  Examples of commercial products are blood derivatives such as Rh Immune Globulin and Factor VIII concentrate, Leukoreduction filters and blood administration sets.


Code: BloodProductTransfusion_DispositionStatus
Display: Blood Product Transfusion/Disposition Status (0513)
Definition:
The domain of possible values to specify the current status of the specified blood product as indicated by the placer.  For example, the placer may return the blood product to the transfusion service unused because an IV could not be started. The blood component may have been entered, but the line was clogged and could not be used, in which case the component must be wasted. A final status would indicate that the product has actually been "transfused."


Code: TransfusionAdverseReaction
Display: Transfusion Adverse Reaction (0514)
Definition:
The domain of possible values that specify the type of adverse reaction that the recipient of the blood product experienced.


Code: TransfusionInterruptedReason
Display: Transfusion Interrupted Reason (0515)
Definition:
The domain of possible values that specify the reason the transfusion of the blood product was interrupted.


Code: ErrorSeverity
Display: Error Severity (0516)
Definition:
The domain of possible values for the severity of an application error as reported during acknowledgment of messages. Knowing if something is Error, Warning or Information is intrinsic to how an application handles the content and the information flow.


Code: InformPersonCode
Display: Inform Person Code (0517)
Definition:
The domain of possible values that specify who (if anyone) shouldor should not be informed of an error.


Code: OverrideType
Display: Override Type (0518)
Definition:
The domain of possible values that specify what type of override can be used to override the specific error identified.


Code: OverrideReason
Display: Override Reason (0519)
Definition:
The domain of possible values that specify the override codes that can be used to override enforcement of the application rule that generated an error.


Code: V2MessageWaitingPriority
Display: Message Waiting Priority (0520)
Definition:
The domain of possible values to specify how important the most important waiting mesasge is.  For example, if there are 3 low priority messages, 1 medium priority message and 1 high priority message, the message waiting priority would be "high", because that is the highest priority of any new message waiting.


Code: ComputationType
Display: Computation Type (0523)
Definition:
The domain of possible values to specify if the change is computed as a percent change or as an absolute change.


Code: CalendarAlignment
Display: Calendar Alignment (0527)
Definition:
The domain of possible values to specify an alignment of the repetition to a calendar (e.g., to distinguish every  30 days from "the 5th of every month").


Code: Organization_Agency_Department
Display: Organization, Agency, Department (0530)
Definition:
The domain of possible values that specify the agency or department that assigned a specified identifier.


Code: ExpandedYes_NoIndicator
Display: Expanded Yes/no Indicator (0532)
Definition:
The domain of possible values to specify an expansion on the original Yes/No indicator table by including "flavors of null".  It is intended to be applied to fields where the response is not limited to "yes" or "no".


Code: ApplicationErrorCode
Display: Application Error Code (0533)
Definition:
The domain of possible values that specify the application specific code identifying the specific error that occurred.


Code: SignatureCode
Display: Signature Code (0535)
Definition:
The domain of possible values that indicate how a patient/subscriber authorization signature is obtained and how it is being retained by a provider.


Code: CertificateStatus
Display: Certificate Status (0536)
Definition:
The domain of possible values that specify the status of the certificate held by a health professional.


Code: Institution2
Display: Institution (0537)
Definition:
The domain of possible values that specify the institution a specified practitioner began or intends to begin practicing at (e.g., at hospital, at physician organization, at managed care network).


Code: InstitutionRelationshipType
Display: Institution Relationship Type (0538)
Definition:
The domain of possible values that specify the relationship the staff person has with the institution for whom he/she provides services.


Code: CostCenterCode
Display: Cost Center Code (0539)
Definition:
The domain of possible values that specify the organization unit in the General Ledger to which the staff member is currently assigned.


Code: SpecimenTypeModifier
Display: Specimen Type Modifier (0541)
Definition:
The domain of possible values that specify the modifying or qualifying description(s) about the specimen type.


Code: SpecimenSourceTypeModifier
Display: Specimen Source Type Modifier (0542)
Definition:
The domain of possible values that specify the modifying or qualifying description(s) about the specimen source site.


Code: SpecimenCollectionSite
Display: Specimen Collection Site (0543)
Definition:
The domain of possible values that specify the modifying or qualifying description(s) about the specimen collection site.  This Domain differs from SpecimenSourceSite in those cases where the source site must be approached via a particular site (e.g., anatomic location). For example, in the case where a liver biopsy is obtained via a percutaneous needle, the collection site would be the point of entry of the needle. For venous blood collected from the left radial vein, the collection site could be “antecubital fossa”.


Code: ContainerCondition
Display: Container Condition (0544)
Definition:
The domain of possible values to specify at each receipt the status of the container in which the specimen is shipped in chain of custody cases where specimens are moved from lab to lab.  If the container is compromised in any way (seal broken, container cracked or leaking, etc.), then this status needs to be recorded for legal reasons.


Code: JurisdictionalBreadth
Display: Jurisdictional Breadth (0547)
Definition:
The domain of possible values that specify the breadth/extent of the jurisdiction where the qualification is valid.


Code: NdcCodes
Display: NDC Codes (0549)
Definition:
The domain of possible values that specify the National Drug Codes (NDC) that are required by the Health Insurance Portability and Accountability Act (HIPAA) for electronic claims for pharmacy charges.


Code: AdvancedBeneficiaryNoticeOverrideReason
Display: Advanced Beneficiary Notice Override Reason (0552)
Definition:
The domain of possible values that specify the reason the patient did not sign an Advanced Beneficiary Notice.


Code: PayeeRelationshipToInvoice
Display: Payee Relationship to Invoice (0558)
Definition:
The domain of possible values used to specify the relationship to the invoice for Person Payee Types.


Code: ProcessingConsiderationCodes
Display: Processing Consideration Codes (0562)
Definition:
The domain of possible values that specify special processing requested of Payer for this Product/Service Line Item (e.g., hold until paper supporting documentation is received by Payer).


Code: AdjustmentCategoryCode
Display: Adjustment Category Code (0564)
Definition:
The domain of possible values used to specify the category of adjustment and is used to assist in determining which table is used for Adjustment Reason.


Code: AdjustmentAction
Display: Adjustment Action (0569)
Definition:
The domain of possible values used to specify the action requested of a party that receives an adjustment.


Code: InvoiceProcessingResultsStatus
Display: Invoice Processing Results Status (0571)
Definition:
The domain of possible values used to specify the processing status for an Invoice Processing Result.


Code: ProtectionCode
Display: Protection Code (0618)
Definition:
The domain of possible values for that an address needs to be treated with special care or sensitivity.


Code: ItemStatusCodes
Display: Item Status Codes (0625)
Definition:
The domain of possible values for the state of an inventory item within the context of an inventory location.


Code: ItemImportanceCodes
Display: Item Importance Codes (0634)
Definition:
The domain of possible values that denote a level or importance of an inventory item within the context of an inventory location.


Code: LaborCalculationType
Display: Labor Calculation Type (0651)
Definition:
The domain of possible values for the method used to calculate employee labor and measure employee productivity.


Code: LotControl
Display: Lot Control (0659)
Definition:
The domain of possible values for whether the sterilization load for a device is built in the sub-sterile area adjacent to an Operating Room or the Central Processing Department.


Code: LoadStatus
Display: Load Status (0669)
Definition:
The domain of possible values for the status of the information provided in a device sterilization or decontamination cycle.


Code: CycleType
Display: Cycle Type (0702)
Definition:
The domain of possible values for the type of cycle that is being executed.  A cycle type is a specific sterilization method used for a specific type of supply item.


Code: AccessRestrictionValue
Display: Access Restriction Value (0717)
Definition:
The domain of possible values for the policies governing the information to which access is contolled.


Code: CclValue
Display: CCL Value (0728)
Definition:
The domain of possible values for the clinical complexity level (CCL) value for the determined diagnosis related group (DRG) for this diagnosis.


Code: DrgDiagnosisDeterminationStatus
Display: DRG Diagnosis Determination Status (0731)
Definition:
The domain of possible values for the status of a diagnosis for a diagnosis related group (DRG) determination.


Code: DrgStatusPatient
Display: DRG Status Patient (0739)
Definition:
The domain of possible values for whether the length of stay is normal or respectively shorter or longer than normal.


Code: DrgStatusFinancialCalculation
Display: DRG Status Financial Calculation (0742)
Definition:
The domain of possible values for the status of the diagnosis related group (DRG) calculation regarding the financial aspects.


Code: DrgGroupingStatus
Display: DRG Grouping Status (0749)
Definition:
The domain of possible values for the status of the use of the gender information for diagnosis related group (DRG) determination.


Code: StatusWeightAtBirth
Display: Status Weight At Birth (0755)
Definition:
The domain of possible values for the status of the use of the weight at birth for diagnosis related group (DRG) determination.


Code: DrgStatusRespirationMinutes
Display: DRG Status Respiration Minutes (0757)
Definition:
The domain of possible values for the status of the use of the respiration minutes information for diagnosis related group (DRG) determination.


Code: StatusAdmission
Display: Status Admission (0759)
Definition:
The domain of possible values for the admission status for the diagnosis related group (DRG) determination.


Code: DRGProcedureDeterminationStatus
Display: DRG Procedure Determination Status (0761)
Definition:
The domain of possible values for the status of the use of this particular procedure for the diagnosis related group (DRG) determination.


Code: DRGProcedureRelevance
Display: DRG Procedure Relevance (0763)
Definition:
The domain of possible values for the relevance of this particular procedure for the diagnosis related group (DRG) determination.


Code: ItemStatus
Display: Item Status (0776)
Definition:
The domain of possible values for the status (useful for reporting and item usage purposes) that applies to an item.


Code: ItemType
Display: Item Type (0778)
Definition:
The domain of possible values for a classification of material items into like groups as defined and utilized within an operating room setting for charting procedures.


Code: ApprovingRegulatoryAgency
Display: Approving Regulatory Agency (0790)
Definition:
The domain of possible values for the regulatory agency by which the item has been approved, such as the FDA or AMA.


Code: RulingAct
Display: Ruling Act (0793)
Definition:
The domain of possible values for an act containing a rule that the item is legally required to be included in notification reporting.


Code: SterilizationType
Display: Sterilization Type (0806)
Definition:
The domain of possible values specifying the type of sterilization used for sterilizing the inventory supply item in the ITM segment.


Code: MaintenanceCycle
Display: Maintenance Cycle (0809)
Definition:
The domain of possible values specifying the maintenance cycle used for the inventory supply item, such as the number of times to sharpen after five uses.


Code: MaintenanceType
Display: Maintenance Type (0811)
Definition:
The domain of possible values specifying the type of maintenance performed on the inventory supply item.  This is different than the maintenance cycle in the sense that it can describe the number of maintenance cycles that can be performed before disposing of the inventory supply item.


Code: Package
Display: Package (0818)
Definition:
The domain of possible values specifying the packaging unit in which this inventory supply item can be ordered or issued when purchased from the vendor in the related vendor segment.


Code: ReferralDocumentationCompletionStatus
Display: Referral Documentation Completion Status (0865)
Definition:
The domain of possible values specifying to the receiving provider that the clinical history in the message is incomplete and that more will follow.


Code: TelecommunicationExpirationReason
Display: Telecommunication Expiration Reason (0868)
Definition:
The domain of possible values specifying the reason this contact number/email was marked as "ended".


Code: SupplyRiskCodes
Display: Supply Risk Codes (0871)
Definition:
The domain of possible values specifying any known or suspected hazard associated with this material item.


Code: Product_ServiceCodeModifier
Display: Product/Service Code Modifier (0880)
Definition:
The domain of possible values specifying additional optional modifier(s) for the Product/Service Code (e.g., after hours - evening, after hours - weekend).


Code: RoleExecutingPhysician
Display: Role Executing Physician (0881)
Definition:
The domain of possible values specifying the account role of the physician, for example, only billing for the professional part, the technical part or both.


Code: PresentOnAdmissionIndicator
Display: Present On Admission (POA) Indicator (0895)
Definition:
The domain of possible values specifying the present on admission indicator for this particular diagnosis.


Code: Participation
Display: Participation (0912)
Definition:
The domain of possible values that represent functional involvement of a caregiver or member of a care team with an activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.).


Code: MonetaryDenominationCode
Display: Monetary Denomination Code (0913)
Definition:
The domain of possible values specifying the denomination in which the quantity is expressed. Values commonly used are the three-character codes specified in  ISO-4217 (1.0.4217 iso4217).


Code: RelevantClinicialInformation
Display: Relevant Clincial Information (0916)
Definition:
The domain of possible values for additional clinical information about the patient or specimen to report the supporting and/or suspected diagnosis and clinical findings on requests for interpreted diagnostic studies.


Code: ExclusiveTest
Display: Exclusive Test (0919)
Definition:
The domain of possible values that define if a test should be a specific event with no other tests to be performed with this test, or not, or other special circumstances.


Code: PreferredSpecimen_AttributeStatus
Display: Preferred Specimen/Attribute Status (0920)
Definition:
The domain of possible values that indicate whether a Specimen/Attribute is Preferred or Alternate for collection of a particular specimen.


Code: ProcessInterruption
Display: Process Interruption (0923)
Definition:
The domain of possible values specifying whether a process was interrrupted and whether a needle had been inserted in the donor's arm prior to the interruption.


Code: V2ObservationType
Display: Observation Type (0936)
Definition:
The domain of possible values for types of observations to enable systems to distinguish between observations sent along with an order, versus observations sent as the result to an order.


Code: PayerCoverageProcedureCode
Display: Procedure Code (0941)
Definition:
The domain of possible values specifying procedure codes that may impact payer coverage requirements, for example procedure code 1234 is not covered by a payer ABCD or may be covered in conjunction with a specific diagnosis code which can be identifeid in DPS-1 Diagnosis Code. The procedure codes should be drawn from appropriate externally defined procedure codes, for example in the US Realm these include CPT-4 codes defined by the American Medical Association and ICD codes published by CMS.


Code: EquipmentStateIndicatorTypeCode
Display: Equipment State Indicator Type Code (0942)
Definition:
The domain of possible values that specify the type of measurement of the state of an automated laboratory instrument.


Code: Auto-dilutionType
Display: Auto-Dilution Type (0945)
Definition:
The domain of possible values for the pre‑configured dilution to be applied on the instrument, which can be used instead of a numeric declaration.


Code: SupplierType
Display: Supplier Type (0946)
Definition:
The domain of possible values for the type of supplier that will distribute the supply items associated to a contract number.


Code: ClassOfTrade
Display: Class of Trade (0947)
Definition:
The domain of possible values for the purchasing channel with which the contract is associated  such as Hospital, Retail, etc.


Code: RelationshipType
Display: Relationship Type (0948)
Definition:
The domain of possible values for the type of relationship that is established between the instances of Source Information and  Target Information.


Code: reasonForStudy
Display: Reason for Study (0951)
Definition:
The domain of possible values that provide additional information to the universal service identifier on why a test, study or review was ordered.


Code: ConfidentialityV2
Display: Confidentiality Classification (0952)
Definition:
Types of privacy metadata classifying an IT resource (data, information object, service, or system capability) according to its level of sensitivity, which is based on an analysis of applicable privacy policies and the risk of financial, reputational, or other harm to an individual or entity that could result if made available or disclosed to unauthorized individuals, entities, or processes.
Usage Note : Confidentiality codes may be used in security labels and privacy markings to classify IT resources based on sensitivity to indicate the obligation of a custodian or receiver to ensure that the protected resource is not made available or disclosed to individuals, entities, or processes (security principals) unless authorized per applicable policies. Confidentiality codes may also be used in the clearances of initiators requesting access to protected resources.
Map: Definition aligns with ISO 7498-2:1989 - Confidentiality is the property that information is not made available or disclosed to unauthorized individuals, entities, or processes


Code: WorkClassificationODH
Display: Work Classification ODH (0959)
Definition:
Types of a person’s employment type as defined by compensation and sector (e.g. paid vs. unpaid, self-employed vs. not self-employed, government vs. private, etc.).


Code: DeviceTypeSNAFU
Display: Device Type (0961)
Definition:
Domain of concepts describing what kind a particular device is. Focus here is on devices used in the medical field.


Code: ServiceReason
Display: Service Reason (0964)
Definition:
Domain of concepts describing reasons why a particular service was performed.
This could be explaining why something was ordered differently than typically done, or explain that it was ordered by mistake.
	Patient disability requires it
	No provider in network
	Patient paid out of pocket


Code: ContractType
Display: Contract Type (0965)
Definition:
The domain of possible values describing the scope of contracts in a masterfile, e.g.:
•	Local
•	Regional
•	Global


Code: PricingTierLevel
Display: Pricing Tier Level (0966)
Definition:
The domain of possible values describing the declared level of pricing for a particular product under a contract, usually based on a discount for larger orders under the contract – often assigned numerically, e.g.:
•	Tier 1
•	Tier 2
•	Tier 3


Code: ContainerFormV2
Display: Container Form (0967)
Definition:
The domain of possible values describing shape or type of the container, e.g.:
•	Tube/vial
•	Jar
•	Bag
•	Block
•	Slide


Code: ContainerMaterial
Display: Container Material (0968)
Definition:
The domain of possible values describing the material a container is made of or indication that the container may be a virtual type, e.g.:
•	Glass
•	Plastic
•	Whole Slide Image


Code: ContainerCommonName
Display: Container Common Name (0969)
Definition:
Codes created by an organization as a shorthand way to express a combination of container attributes; for example the combination of SAC-47 (Container Form) of “Tube/vial” + SAC-48 (Container Material) of “Glass” + SAC-27 (Additive) of “EDTA” may be referenced commonly in an organization as a “Lavender Top”, e.g.:
•	Lavender Top
•	Wet Mount (slides for parasitology)
•	LJ plate (for Mycobacterium cultures)


Code: OnlineVerificationResultErrorCode
Display: Online Verification Result Error Code (0971)
Definition:
Domain of values representing a type of error from a failed operation to perform online verification of insurance data.


Code: synonymCode
Display: synonymCode
Definition:
Notes a different identifying concept representation (code) which is the same concept and thus considered a synonym. Used in UTG CodeSystem extensions.


Code: preferredForLanguage
Display: Preferred For Language
Definition:
Denotes a code designation which is preferred for the identified language among more than one for that language. Used in value set designation-use in FHIR.


Code: consumer
Display: Consumer-friendly
Definition:
Designation for use in display to non-clinicians and those not in healthcare professions as a more friendly term for coommunication.


Code: sponsor
Display: sponsor
Definition:
Sponsor of the terminology object, as defined in the MIF using legacy tooling, and held in the codeSystem.header.contributor.role element.


Code: Publisher
Display: Publisher of the terminology object
Definition:
Publisher of the terminology object, as defined in the MIF using legacy tooling, and held in the codeSystem.header.contributor.role element. Typically used only where the developer and steward is different than the organization publishing the code system.


Code: UTGRELManifest
Display: UTG Release Instance Manifest
Definition:
Identifies List resourrce instance used as a Manifest of a release of the HL7 Vocabulary through UTG.


Code: Specializes
Definition:
The child code is a more narrow version of concept represented by the parent code.  I.e. Every child concept is also a valid parent concept.  Used to allow determination of subsumption.  Must be transitive, irreflexive, antisymetric.


Code: ComponentOf
Definition:
The child code is a part of the concept represented by the parent code.  Used to determine allowed nesting, for example of address components.  Must be transitive, irreflexive, antisymetric.


Code: GroupedBy
Definition:
The child code is a part of a grouping represented by the parent code.  Used to determine navigational hierarchy not based on a specializes or component relationship.  E.g. ICD9 hierarchy.  Is transitive, irreflexive and antisymetric


Code: LessThan
Definition:
For coded ordeinal code systems, indicates that the specified code is considered less than the related code.  Used to determine relationships for coded ordinals.  Must be transitive, irreflexive, antisymetric.


Code: DefinitionallyQualifies
Definition:
Identifies a code that can act as a qualifier for the referenced code, both as part of concept definition within the code system and as part of run-time concept definition to determine concepts allowed for use as qualifiers for a concept within a CD datatype.  Must be non-transitive, irreflexive.


Code: NonDefinitionallyQualifies
Definition:
Same as definitionally qualifies, but restricted to only being used at run-time.  Must be non-transitive, irreflexive.


Code: Other
Definition:
The child code has a relationship with the parent that does not follow one of the pre-defined stereotypical patterns.  Any application behavior based on the relationship must be custom-coded.  Transitivity, Reflexivity and Symmetry must be asserted


Code: v2-binding
Display: V2 Binding Code
Definition:
Coded value identifying the binding realm for those tables that have a binding to a value set.  0=no binding or binding N/A; 1=Example; 2=Representative; 3=Universal; 4=US Realm.


Code: v2-cld
Display: V2 VS CLD Type
Definition:
Categorization of Content Logical Definition for the V2 value set informing the table, as printed in the V2 ballot.  0=no expansion, 1=all codes, 2=enumerated, 3=V3 vaue set definition, 4=unique intensional definition, 5=non-HL7 value set definition, 6=FHIR value set definition


Code: v2-table-deprecated
Display: deprecated
Definition:
Indicates that although still being published in the V2 international standard, the table has been deprecated in favor of alternative codes, and will be withdrawn in the future.


Code: v2TblStatus
Display: V2 Table Status
Definition:
Status of the table as published in the V2 ballots. This is different from the concept status, which is the status of the concept representing the table infomration in the V2 Tables code system.


Code: v2-version-csvs-introduced
Display: version-csvs-introduced
Definition:
HL7 V2 version when the code system and value set were introduced.   This is either the creation date of the V2 code system or value set objects, or the date when the FHIR or V3 or External code system and/or value set were associated to the table.


Code: rim-classifies-class-code
Display: ClassifiesC RIM Class Code
Definition:
Associates a concept domain with th ActClass code that it is intended to be associated with, ie for late binding, informs the IG devloper which code should be populated in ActClass when a value sset for ActCode is being bound.


Code: ConceptualSpaceForClassCode
Display: Conceptual Space For ClassCode
Definition:
This concept domain provides the semantic category space indicates by the identifies Class code.  Used in HL7 V3 RIM.


Code: source
Display: Source
Definition:
Indicaates the etiology of this domain, i.e. which HL7 product family or other area that the domain originally was needed for and triggered its creation.


Code: v2-concComment
Display: V2 Concept Comment
Definition:
String value from the V2 publishing database source holding comments for the concepts for populated tables.  These comments are separate from the concept Definition and the Usage Notes.


Code: v2-concCommentAsPub
Display: V2 Concept Comment As Published
Definition:
String value from the V2 publishing database source holding comments as published for the concepts for populated tables.  These comments are separate from the concept Definition and the Usage Notes, and may be distinct from the other comments due to publishing requirements.


Code: HL7usageNotes
Display: HL7 Concept Usage Notes
Definition:
String value from the HL7 sources holding the Usage Notes for the concepts for populated tables and code systems.  These  are separate from the concept Definitions and the other comments.


Code: OwningAffiliate
Display: HL7 Affiliate Owner
Definition:
Used in the V3 ballot and publication process to indicate content which is owned by one of the HL7 International Affiliates.


Code: DeprecationInfo
Display: Deprecation Informaton
Definition:
Used to support the capture of comments, remarks, V3 release ID, and other information related to the deprecation of a concept.


Code: SmallerThan
Display: Smaller Than
Definition:
Points to another code value in the codeSystem which this concept is smaller than.  Typically used in systems of Ordinal relationship codes, where size or magnitude is the ordering key.


Code: X
Display: Non-Binary
Definition:
Intended for situations where the gender or sex representation of the individual is not strictly male, or strictly female, and is driven by jurisdictional requirements, personal needs, or legal boundaries.


Code: O55
Display:
ORL - Laboratory Order Acknowledgment Message  – Multiple Order Per Container of Specimen (Patient Optional)

Definition:
ORL - Laboratory Order Acknowledgment Message  – Multiple Order Per Container of Specimen (Patient Optional)


Code: R03
Display:
QRY/DSR Display-oriented results, query/unsol. update (for backward compatibility only) (Replaced by Q05)

Definition:
QRY/DSR Display-oriented results, query/unsol. update (for backward compatibility only) (Replaced by Q05)


Code: S40
Display: Specimen Collection Unsuccessful
Definition:
Describes the event when specimen collection was not successful and provides a means to document the reason


Code: S51
Display: Specimen Procedure Step Successful, no Derived Specimen(s)
Definition:
Describes the event when a specimen has been successfully processed without producing any child specimen(s)


Code: S52
Display: Specimen Procedure Step Unsuccessful
Definition:
Describes the event when a specimen could not be successfully processed and provides a means to document the reason


Code: SET
Display: Specimen Event Tracking
Definition:
This message type is used to report how the specimen moves through its lifecycle from collection, identification, transport, acceptance or rejection, processing to storage and disposition.


Code: A
Display:
Amended based on adjustments provided by the Placer (Physician) regarding patient demographics (such as age and/or gender or other patient specific information

Definition:
Amended based on adjustments provided by the Placer (Physician) regarding patient demographics (such as age and/or gender or other patient specific information


Code: B
Display:
Appended Report - Final results reviewed and further information provided for clarity without change to the original result values.

Definition:
Appended Report - Final results reviewed and further information provided for clarity without change to the original result values.


Code: N
Display:
Not asked; used to affirmatively document that the observation identified in the OBX was not sought when the universal service ID in OBR-4 implies that it would be sought.

Definition:
Not asked; used to affirmatively document that the observation identified in the OBX was not sought when the universal service ID in OBR-4 implies that it would be sought.


Code: V
Display:
Verified - Final results reviewed and confirmed to be correct, no change to result value, normal range or abnormal flag

Definition:
Verified - Final results reviewed and confirmed to be correct, no change to result value, normal range or abnormal flag


Code: U
Display:
Results status change to final without retransmitting results already sent as 'preliminary.'  E.g., radiology changes status from preliminary to final

Definition:
Results status change to final without retransmitting results already sent as 'preliminary.'  E.g., radiology changes status from preliminary to final


Code: T
Display: Training
Definition:
Messages used for training, where new/updated configurations are utilized to prepare users outside of a production setting.


Code: N
Display: Non-Production Testing
Definition:
Messages used for testing of an interface for structure, content, and conformance between trading partners, using non-production data.


Code: NR
Display: Notification Received
Definition:
Notifies the Filler that the Placer received a cancellation, discontinuance, or other state change notice


Code: SU
Display: Supplement this order
Definition:
Identifies existing orders to be supplemented in Supplementation Recommendation (filler to placer) and Supplementation Request (placer to filler) messages.


Code: N
Display: Procedure completed, results pending
Definition:
No result available; requested procedure done.  To indicate that a requested test is performed but results are pending/not yet available.


Code: REV
Display:
All values within the range returned in reverse chronological order (This is the default if not otherwise specified.)

Definition:
All values within the range returned in reverse chronological order (This is the default if not otherwise specified.)


Code: P
Display:
Profile or battery consisting of many independent atomic observations (e.g., SMA12, electrolytes), usually done at one instrument on one specimen

Definition:
Profile or battery consisting of many independent atomic observations (e.g., SMA12, electrolytes), usually done at one instrument on one specimen


Code: F
Display:
Functional procedure that may consist of one or more interrelated measures (e.g., glucose tolerance test, creatinine clearance), usually done at different times and/or on different specimens

Definition:
Functional procedure that may consist of one or more interrelated measures (e.g., glucose tolerance test, creatinine clearance), usually done at different times and/or on different specimens


Code: S
Display:
Superset-a set of batteries or procedures ordered under a single code unit but processed as separate batteries (e.g., routines = CBC, UA, electrolytes)<p>This set indicates that the code being described is used to order multiple service/test/observation b

Definition:
Superset—a set of batteries or procedures ordered under a single code unit but processed as separate batteries (e.g., routines = CBC, UA, electrolytes)
This set indicates that the code being described is used to order multiple service/test/observation batteries.  For example, a client who routinely orders a CBC, a differential, and a thyroxine as an outpatient profile might use a single, special code to order all three test batteries, instead of having to submit three separate order codes.


Code: C
Display:
Single observation calculated via a rule or formula from other independent observations (e.g., Alveolar-arterial ratio, cardiac output)

Definition:
Single observation calculated via a rule or formula from other independent observations (e.g., Alveolar-arterial ratio, cardiac output)


Code: ER
Display:
Error/Reject conditions only.  Only MFA segments denoting errors must be returned via the application-level acknowledgment for this message

Definition:
Error/Reject conditions only.  Only MFA segments denoting errors must be returned via the application-level acknowledgment for this message


Code: AL
Display:
Always.  All MFA segments (whether denoting errors or not) must be returned via the application-level acknowledgment message

Definition:
Always.  All MFA segments (whether denoting errors or not) must be returned via the application-level acknowledgment message


Code: SU
Display:
Success.  Only MFA segments denoting success must be returned via the application-level acknowledgment for this message

Definition:
Success.  Only MFA segments denoting success must be returned via the application-level acknowledgment for this message


Code: RH
Display:
Registry home. Refers to the information system, typically managed by a public health agency, that stores patient information such as immunization histories or cancer data, regardless of where the patient obtains services.

Definition:
Registry home. Refers to the information system, typically managed by a public health agency, that stores patient information such as immunization histories or cancer data, regardless of where the patient obtains services.


Code: AC
Display: Accreditation/Certification Identifier
Definition:
Identifier that has been assigned by an accreditation or certification organization in specific fields, indicating a recognized skill


Code: AIN
Display: Animal Identification Number (US Official)
Definition:
A numbering system for the official identification of individual animals in the United States that provides a nationally unique identification number for each animal. The first two numbers on a tag are the numbers assigned to a specific State.


Code: APRN
Display: Advanced Practice Registered Nurse number
Definition:
An identifier that is unique to an advanced practice registered nurse within the jurisdiction of a certifying board


Code: BCFN
Display: Birth Certificate File Number
Definition:
The identifier used within the jurisdictional vital records office file system as an auxiliary means of accessing the record associated with the birth certificate.


Code: BR
Display: Birth registry number
Definition:
An identifier unique within the Assigning Authority that is the official legal record of a person's birth.


Code: CAAI
Display: Consumer Application Account Identifier
Definition:
An identifier for the consumer (e.g., patient, caregiver) for an application such as a portal or App.


Code: DC
Display: Death Certificate ID
Definition:
The identifier assigned to a death certificate, and printed on the death certificate when issued by a jurisdictional vital records office


Code: DCFN
Display: Death Certificate File Number
Definition:
The identifier used within the jurisdictional vital records office file system as an auxiliary means of accessing the record associated with the death certificate.


Code: DEA
Display: Drug Enforcement Administration registration number
Definition:
An identifier for an individual or organization relative to controlled substance regulation and transactions.


Code: ESN
Display: Staff Enterprise Number
Definition:
An identifier that is unique to a staff member within an enterprise (as identified by the Assigning Authority).


Code: ETIN
Display: Electronic Transmitter Identification Number
Definition:
A unique identifier usually assigned by a health plan or clearinghouse to an organization or provider that electronically transmits healthcare transactions, such as claims, eligibility inquiries, or remittance advices.


Code: FDR
Display: Fetal Death Report ID
Definition:
The identifier assigned to a fetal death report, and printed on the fetal death report when issued by a jurisdictional vital records office


Code: FDRFN
Display: Fetal Death Report File Number
Definition:
The identifier used within the jurisdictional vital records office file system as an auxiliary means of accessing the record associated with the fetal death report certificate.


Code: FILL
Display: Filler Identifier
Definition:
An identifier for a request where the identifier is issued by the person, or service, that produces the observations or fulfills the request.


Code: GKV
Display: Insured's ID with Public Insurance
Definition:
Identifier that can be used to unambiguously describe the ID of a patient with a public insurance company.


Code: IRISTEM
Display: An IRI stem
Definition:
An IRI string that can be prepended to the code to obtain a concept IRI for RDF applications. This should be a valid, absolute IRI as defined in RFC 3987. See https://hl7.org/fhir/rdf.html#iri-stem for details on how this value may be used.


Code: L&I
Display: Labor and industries number
Definition:
Labor and industries number.  Note that this was introduced erroneously (with an ampersand in the code value) many years ago.


Code: MB
Display: Member Number
Definition:
An identifier for the insured of an insurance policy (this insured always has a subscriber), usually assigned by the insurance carrier.


Code: MI
Display: Military ID number
Definition:
A number assigned to an individual who has had military duty, but is not currently on active duty. The number is assigned by the DOD or Veterans' Affairs (VA).


Code: MR
Display: Medical record number
Definition:
An identifier that is unique to a patient within a set of medical records, not necessarily unique within an application.


Code: NCT
Display: Naturalization Certificate
Definition:
A number associated with a document identifying a person's retention of citizenship in a particular country.


Code: NNxxx
Display:
National Person Identifier where the xxx is the ISO table 3166 3-character (alphabetic) country code

Definition:
National Person Identifier where the xxx is the ISO table 3166 3-character (alphabetic) country code


Code: OD
Display: Optometrist license number
Definition:
A number that is unique to an individual optometrist within the jurisdiction of the licensing board.


Code: PAYERID
Display: Payer Identifier
Definition:
A unique identifier, usually assigned by a health plan or clearinghouse, used in electronic healthcare transactions to designate the specific health insurance company or plan that is the recipient or sender of the transaction.


Code: PE
Display: Living Subject Enterprise Number
Definition:
An identifier that is unique to a living subject within an enterprise (as identified by the Assigning Authority).


Code: PHO
Display: Public Health Official ID
Definition:
An identifier for a person working at a public health agency (PHA),  assigned or issued by the agency


Code: PKV
Display: Insured's ID with Private Insurance
Definition:
Identifier that can be used to unambiguously describe the ID of a patient with a private insurance company.


Code: PLAC
Display: Placer Identifier
Definition:
An identifier for a request where the identifier is issued by the person or service making the request.


Code: PRN
Display: Provider number
Definition:
A number that is unique to an individual provider, a provider group or an organization within an Assigning Authority.


Code: RR
Display: Railroad Retirement number
Definition:
An identifier for an individual enrolled with the Railroad Retirement Administration.  Analogous to, but distinct from, a Social Security Number


Code: SAMN
Display: SAMN# accession Number
Definition:
The accession number for the BioSample data repository at the National Center for Biotechnology Information (NCBI)


Code: SB
Display: Social Beneficiary Identifier
Definition:
An identifier issued by a governmental organization to a person to identify the person should they apply for or receive social services and/or benefits


Code: SN
Display: Subscriber Number
Definition:
An identifier for a subscriber of an insurance policy which is unique for, and usually assigned by, the insurance carrier.


Code: SNBSN
Display: State assigned NDBS card Identifier
Definition:
The identifier on a Newborn Screening Dried Bloodspot (NDBS) card that is assigned by the state which provided the sample collection cards and to whom this information must be reported


Code: SNO
Display: Serial Number
Definition:
An identifier affixed to an item by the manufacturer when it is first made, where each item has a different identifier.


Code: SP
Display: Study Permit
Definition:
A number associated with a permit identifying a person who is a resident of a jurisdiction for the purpose of education.


Code: SRX
Display: SRA Accession number
Definition:
The accession number generated by the Sequence Read Archive (SRA) at the National Center for Biotechnology Information (NCBI) when sequence data are uploaded to NCBI.


Code: UDI
Display: Universal Device Identifier
Definition:
An identifier assigned to a device using the Unique Device Identification framework as defined by IMDRF (http://imdrf.org).


Code: UMB
Display: Unique Product-independent Payer Person Identifier
Definition:
A unique identifier assigned to an individual by a payer that remains consistent regardless of the individual's role (e.g., subscriber, dependent) or the specific product(s) they are enrolled in with that payer.


Code: UPIN
Display: Medicare/CMS (formerly HCFA)'s Universal Physician Identification numbers
Definition:
An identifier for a provider within the CMS/Medicare program.  A globally unique identifier for the provider in the Medicare program.


Code: WP
Display: Work Permit
Definition:
A number associated with a permit for a person who is granted permission to work in a country for a specified time period.


Code: XV
Display: Health Plan Identifier
Definition:
National unique health plan identifier required by the US Department of Health and Human Services, Centers for Medicare and Medicaid Services (CMS) in the US Realm.


Code: S
Display: Used in Snapshot mode
Definition:
Declares when segment falls under snapshot  mode handling, i.e. all elements that were previously sent will be sent, not just any changes


Code: PD
Display: Protected data
Definition:
Data matching the query parameters was found but could not be shared with the querying system for reasons including local policy or legal restrictions.


Code: ISO IR159
Display:
Code of the supplementary Japanese Graphic Character set for information interchange (JIS X 0212-1990).

Definition:
Code of the supplementary Japanese Graphic Character set for information interchange (JIS X 0212-1990).


Code: PT
Display: point in time
Definition:
To identify measures at a point in time.  This is a synonym for "spot" or "random" as applied to urine measurements.


Code: CFST
Display:
Fasting (no calorie intake) for the period specified in the time component of the term, e.g., 1H POST CFST

Definition:
Fasting (no calorie intake) for the period specified in the time component of the term, e.g., 1H POST CFST


Code: COMPLETE
Display:
A request to add a completed appointment, used to maintain records of completed appointments that did not appear in the schedule (e.g., STAT, walk-in, etc.)

Definition:
A request to add a completed appointment, used to maintain records of completed appointments that did not appear in the schedule (e.g., STAT, walk-in, etc.)


Code: DC
Display: Discontinued
Definition:
The indicated appointment was discontinued (DC’ed while in progress, discontinued parent appointment, or discontinued child appointment)


Code: NOTIFY
Display:
Notify the Placer Contact Person, through normal institutional procedures, that a substitution of this resource has been made

Definition:
Notify the Placer Contact Person, through normal institutional procedures, that a substitution of this resource has been made


Code: PREFSTART
Display:
The preferred start time for the appointment request, service or resource.   Any legal time specification in the format HHMM, using 24-hour clock notation

Definition:
The preferred start time for the appointment request, service or resource.   Any legal time specification in the format HHMM, using 24-hour clock notation


Code: PREFEND
Display:
The preferred end time for the appointment request, service or resource.  Any legal time specification in the format HHMM, using 24-hour clock notation

Definition:
The preferred end time for the appointment request, service or resource.  Any legal time specification in the format HHMM, using 24-hour clock notation


Code: MON
Display:
An indicator that Monday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Monday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred


Code: TUE
Display:
An indicator that Tuesday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Tuesday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred


Code: WED
Display:
An indicator that Wednesday is or is not preferred for the day on which the appointment will occur. OK = Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Wednesday is or is not preferred for the day on which the appointment will occur. OK = Preferred appointment day NO = Day is not preferred


Code: THU
Display:
An indicator that Thursday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Thursday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred


Code: FRI
Display:
An indicator that Friday is or is not preferred for the day on which the appointment will occur.  OK =  Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Friday is or is not preferred for the day on which the appointment will occur.  OK =  Preferred appointment day NO = Day is not preferred


Code: SAT
Display:
An indicator that Saturday is or is not preferred for the day on which the appointment will occur.  OK =  Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Saturday is or is not preferred for the day on which the appointment will occur.  OK =  Preferred appointment day NO = Day is not preferred


Code: SUN
Display:
An indicator that Sunday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred

Definition:
An indicator that Sunday is or is not preferred for the day on which the appointment will occur.  OK = Preferred appointment day NO = Day is not preferred


Code: P
Display:
Pro-rate. Apply this price to this interval, pro-rated by whatever portion of the interval has occurred/been consumed

Definition:
Pro-rate. Apply this price to this interval, pro-rated by whatever portion of the interval has occurred/been consumed


Code: F
Display:
Flat-rate. Apply the entire price to this interval, do not pro-rate the price if the full interval has not occurred/been consumed

Definition:
Flat-rate. Apply the entire price to this interval, do not pro-rate the price if the full interval has not occurred/been consumed


Code: Base64
Display:
Encoding as defined by MIME (Multipurpose Internet Mail Extensions) standard RFC 1521. Four consecutive ASCII characters represent three consecutive octets of binary data. Base64 utilizes a 65-character subset of US-ASCII, consisting of both the upper and

Definition:
Encoding as defined by MIME (Multipurpose Internet Mail Extensions) standard RFC 1521. Four consecutive ASCII characters represent three consecutive octets of binary data. Base64 utilizes a 65-character subset of US-ASCII, consisting of both the upper and lower case alphabetic characters, digits “0” through “9”, “+”, “/”, and “=”.


Code: CLIA
Display: Clinical Laboratory Improvement Amendments
Definition:
Clinical Laboratory Improvement Amendments. Allows for the ability to designate organization identifier as a "CLIA" assigned number (for labs)


Code: CLIP
Display: Clinical laboratory Improvement Program
Definition:
Clinical laboratory Improvement Program. Allows for the ability to designate organization identifier as a "CLIP" assigned number (for labs).Â  Used by US Department of Defense.


Code: DNS
Display: Domain Name System
Definition:
An Internet host name, in accordance with RFC 1035; or an IP address. Either in ASCII or as integers, with periods between components ("dotted" notation).


Code: EUI64
Display: IEEE 64-bit Extended Unique Identifier
Definition:
IEEE 64-bit Extended Unique Identifier is comprised of a  24-bit company identifier and a 40-bit instance identifier.  The value shall be formatted as 16 ASCII HEX digits, for example, “AABBCC1122334455”.  The 24-bit company identifier, formally known as Organizationally Unique Identifier (OUI-24), is guaranteed to be globally unique.  The 40-bit extensions are assigned by manufacturers.  This identifier is often used in equipment interfaces (e.g., “MAC” address format for IPv4 & IPv6).  [See http://standards.ieee.org/regauth/oui/tutorials/EUI64.html for a detailed explanation of the format.]


Code: ISO
Display: ISO Object Identifier
Definition:
An International Standards Organization Object Identifier (OID), in accordance with ISO/IEC 8824.  Formatted as decimal digits separated by periods; recommended limit of 64 characters


Code: NPI
Display: US National Provider Identifier
Definition:
Allows for the ability to designate organization identifier as a "NPI" assigned number (lab, any medical provider, can be a person or an organization)


Code: Random
Display: Random
Definition:
Usually a base64 encoded string of random bits.<p>Note: Random IDs are typically used for instance identifiers, rather than an identifier of an Assigning Authority that issues instance identifiers


Code: UUID
Display: Universal Unique Identifier
Definition:
The DCE Universal Unique Identifier, in accordance with RFC 4122. Recommended format is 32 hexadecimal digits separated by hyphens, in the digit grouping 8-4-4-4-12


Code: U <spec>
Display:
for future use, where <spec> is an interval specification as defined by the UNIX cron specification.

Definition:
for future use, where <spec> is an interval specification as defined by the UNIX cron specification.


Code: OMQ_O57
Display: O57
Definition:
Identifier  for the message structure for an OMQ message with a trigger event of General Order Message with Document Payload (O57)


Code: ORL_O53
Display: O53
Definition:
Identifier  for the message structure for an ORL message with a trigger event of - General Laboratory Order Acknowledgment Message (Patient Optional) (O53)


Code: ORL_O54
Display: O54
Definition:
Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message  – Multiple Order Per Specimen (Patient Optional) (O54)


Code: ORL_O55
Display: O55
Definition:
Identifier  for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message  – Multiple Order Per Container of Specimen (Patient Optional) (O55)


Code: ORL_O56
Display: O56
Definition:
Identifier  for the message structure for an ORL message with a trigger event of Specimen Shipment Centric Laboratory Order Acknowledgment Message (Patient Optional) (O56)


Code: ORX_O58
Display: O58
Definition:
Identifier  for the message structure for an ORX message with a trigger event of General Order Message with Document Payload Acknowledgement Message  (O58)


Code: OSU_O51
Display: O51
Definition:
Identifier for the message structure for an OSU message with a trigger event of Order Status Update (O51)


Code: OSU_O52
Display: O52
Definition:
Identifier for the message structure for an OSU message with a trigger event of Order Status Update Acknowledgement (O52)


Code: SET_S38
Display: Specimen Container Preparation and Specimen Collection Event
Definition:
This message structure supports tracking of information related to preparations for specimen collection and the collection event.


Code: SET_S41
Display: Specimen Movement Event
Definition:
This message structure supports tracking of information related to the movements of specimens across locations, and placement in and out of storage.


Code: SET_S45
Display: Specimen Identification Events
Definition:
This message structure supports tracking of information to identify or de-identify specimens or at time of final disposal.


Code: SET_S50
Display: Specimen Procedure Step successful
Definition:
This message structure supports tracking of information related to processing of one or more specimen that may result in derived (child) specimen or not.


Code: SET_S52
Display: Specimen Procedure Step unsuccessful
Definition:
This message structure supports tracking of information when the processing of a specimen was unsuccessful.


Code: ISO 2022-1994
Display:
This standard is titled "Information Technology - Character Code Structure and Extension Technique". .

Definition:
This standard is titled "Information Technology - Character Code Structure and Extension Technique". .


Code: 2.3
Display:
The character set switching mode specified in HL7 2.5, section 2.7.2 and section 2.A.46, "XPN - extended person name".

Definition:
The character set switching mode specified in HL7 2.5, section 2.7.2 and section 2.A.46, "XPN - extended person name".


Code: 198
Display: Non-Conformant Cardinality
Definition:
An error has been encountered related to HL7 message content. Message is not -conformant with the applicable specification’s (base standard, conformance profile or implementation profile)  cardinality.


Code: 199
Display: Other HL7 Error
Definition:
Any other error with the HL7 syntax that is not captured in any of the other error codes in this set.


Code: 204
Display: Unknown key identifier
Definition:
Retained for backwards compatibility only: This situation should be reported in ERR-5 (Application Error Code) using code 101 (Unknown Key Identifier) from code system HL70533.


Code: 205
Display: Duplicate key identifier
Definition:
Retained for backwards compatibility only: This situation should be reported in ERR-5 (Application Error Code) using code 102 (Duplicate Key Identifier) from code system HL70533.


Code: 206
Display: Application record locked
Definition:
Retained for backwards compatibility only: This situation should be reported in ERR-5 (Application Error Code) using code 103 (Application record locked) from code system HL70533.


Code: B
Display: Blind Sample
Definition:
Used to test the validity of the measurement process, where the composition of the sample is unknown except to the person submitting it.


Code: G
Display: Group
Definition:
Used when solid specimens consist of multiple individual elements that are not individually identified but can be separated again into the original specimens.  The identifiers of the original specimens may be tracked.


Code: L
Display: Pool
Definition:
Used when aliquots of liquid individual specimens are combined to form a single specimen representing all of the components that are not individually identified.  The identifiers of the original specimens may be tracked.


Code: A
Display: Archived
Definition:
Archived status is used by one system to inform another that the container was already processed by this system, archived for a longer time period and is re-introduced to the automation system for re-processing.


Code: I
Display: Identified
Definition:
Identified status is used by one system to inform another that it has received a container. In the exchange between the LAS and LIS the Identified status can be used for reporting of the "In Lab" (Specimen Received) status. In some cases this may not be equal to the first event of sample recognition.


Code: L
Display: Left Equipment
Definition:
Left Equipment status is used by one system to inform another that the container has been released from that system.


Code: M
Display: Missing
Definition:
Missing status is used by one system to inform another that the container did not arrive at its next expected location.


Code: O
Display: In Process
Definition:
In Process status is 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.


Code: P
Display: In Position
Definition:
In Position status is used by one system to inform another that the container is in position for specimen transfer (e.g., container removal from track, pipetting, etc.).


Code: R
Display: Process Completed
Definition:
Process Completed 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.


Code: X
Display: Container Unavailable
Definition:
Cancelled status is 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).


Code: 99zzz
Display:
Local general code for a site-defined code system used for a specific set of trading partners.  The 'zzz' SHALL be any printable ASCII string.  Length of the name SHALL not exceed field width, and is subject to local implementation.

Definition:
Local general code for a site-defined code system used for a specific set of trading partners.  The 'zzz' SHALL be any printable ASCII string.  Length of the name SHALL not exceed field width, and is subject to local implementation.


Code: ACTRELSS
Display:
Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.
Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtere

Definition:
Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.
Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtere


Code: CMSHCC
Display: CMS Hierarchical Condition Categories
Definition:
The CMS-HCC model uses more than 9,000 ICD-10-CM codes, which are mapped to condition categories that predict costs well. The condition categories are based on diagnoses clinically related to one another and with similar predicted cost implications. Hierarchies are imposed on the condition categories to capture the most costly diagnoses. Hierarchy logic is imposed on certain condition categories to account for different hierarchical costs, thus, the term Hierarchical Condition Category, or HCC.


Code: HL7nnnn
Display:
Health Level Seven defined table of codes, where nnnn is the HL7 table number.  The number is four numeric digits as published in HL7 Version 2 chapter 2C.  For example, HL70001.

Definition:
Health Level Seven defined table of codes, where nnnn is the HL7 table number.  The number is four numeric digits as published in HL7 Version 2 chapter 2C.  For example, HL70001.


Code: PLT
Display:
CDC PHLIP Lab test codes, where LOINC concept is too broad or not yet available, especially as needed for ordering and or lab to lab reporting )

Definition:
CDC PHLIP Lab test codes, where LOINC concept is too broad or not yet available, especially as needed for ordering and or lab to lab reporting )


Code: SPCU
Display: Sex Parameter for Clinical Use
Definition:
A summary parameter that provides guidance on how a receiver should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.


Code: VIS
Display:
Clinicians are required to track the Vaccine Information Sheet (VIS) that was shared with the recipient of a vaccination.  This code system contains codes that  identify the document type and the owner of the document.

Definition:
Clinicians are required to track the Vaccine Information Sheet (VIS) that was shared with the recipient of a vaccination.  This code system contains codes that  identify the document type and the owner of the document.


Code: VPS
Display:
Verifying Pharmaceutical Supplier   (not sure how to dissect Pharmacist/Treatment Supplier's Verifier ID)

Definition:
Verifying Pharmaceutical Supplier   (not sure how to dissect Pharmacist/Treatment Supplier's Verifier ID)


Code: VTS
Display:
Verifying Treatment Supplier   (not sure how to dissect Pharmacist/Treatment Supplier's Verifier ID)

Definition:
Verifying Treatment Supplier   (not sure how to dissect Pharmacist/Treatment Supplier's Verifier ID)


Code: RL
Display: Returned unused but linked
Definition:
Blood product was returned unused, because it is not currently needed, but should remain linked to the patient for future use.


Code: TI
Display: Transfusion Interrupted
Definition:
Transfusion of the blood product was interrupted and considered ended; a reason for interruption is usually also reported.


Code: C
Display:
Signed CMS-1500 claim form on file, e.g., authorization for release of any medical or other information necessary to process this claim and assignment of benefits.

Definition:
Signed CMS-1500 claim form on file, e.g., authorization for release of any medical or other information necessary to process this claim and assignment of benefits.


Code: S
Display:
Signed authorization for release of any medical or other information necessary to process this claim on file.

Definition:
Signed authorization for release of any medical or other information necessary to process this claim on file.


Code: PersDEID
Display: personal de-identified information policy
Definition:
Personal policy on collection, access, use, or disclosure of de-identified information as defined by the information subject or by applicable jurisdictional law.


Code: JurisIP
Display: jurisdictional information policy
Definition:
Jurisdictional policy on collection, access, use, or disclosure of information as defined by applicable jurisdictional law.


Code: JurisCUI
Display: jurisdictional controlled unclassified information policy
Definition:
Jurisdictional policy on collection, access, .use, or disclosure of controlled unclassified information as defined by applicable jurisdictional law.


Code: JurisDEID
Display: jurisdictional de-identified information policy
Definition:
Jurisdictional policy on collection, access, use, or disclosure of de-identified information as defined by applicable jurisdictional law.


Code: JurisLDS
Display: jurisdictional limited data set
Definition:
Jurisdictional policy on collection, access, use, or disclosure of information in a limited data set as defined by applicable jurisdictional law.


Code: JurisNSI
Display: jurisdictional non-sensitive information policy
Definition:
Jurisdictional policy on collection, access, use, or disclosure of information deemed non-sensitive by applicable jurisdiction law.


Code: JurisPI
Display: jurisdictional public information policy
Definition:
Jurisdictional policy on collection, access, use, or disclosure of information deemed public by applicable jurisdiction law.


Code: JurisSP-CUI
Display: jurisdictional specified controlled unclassified information policy
Definition:
Jurisdictional policy on collection, access, use, or disclosure of specified controlled unclassified information as defined by applicable jurisdictional policy.


Code: JurisUUI
Display: jurisdictional uncontrolled unclassified information policy
Definition:
Jurisdictional policy on collection, access, use, or disclosure of uncontrolled unclassified information as defined by applicable jurisdictional policy.


Code: OrgIP
Display: organizational information policy
Definition:
Organizational policy on collection, access, use, or disclosure of information, which does not conflict with jurisdictional law


Code: OrgCUI
Display: organizational basic controlled unclassified information policy
Definition:
Organizational policy on collection, access, use, or disclosure of basic controlled unclassified information as defined by the organization or by applicable jurisdictional law.


Code: OrgDEID
Display: organizational de-identified information policy
Definition:
Organizational policy on collection, access, use, or disclosure of de-identified information as defined by the organization or by applicable jurisdictional law.


Code: OrgLDS
Display: organizational limited data set information policy
Definition:
Organizational policy on collection, access, use, or disclosure of information in a limited data set as defined by the organization or by applicable jurisdictional law.


Code: OrgNSI
Display: organizational non-sensitive information policy
Definition:
Organizational policy on collection, access, use, or disclosure of information deemed non-sensitive by the organization by applicable jurisdictional law.


Code: OrgPI
Display: organizational public information policy
Definition:
Organizational policy on collection, access, use, or disclosure of public information as defined by the organization or by applicable jurisdictional law.


Code: OrgSP-CUI
Display: organizational specified controlled unclassified information policy
Definition:
Organizational policy on collection, access, use, or disclosure of specified controlled unclassified information as defined by the organization or by applicable jurisdictional law.


Code: OrgUUI
Display: organizational uncontrolled unclassified information policy
Definition:
Organizational policy on collection, access, use, or disclosure of uncontrolled unclassified information as defined by the organization or by applicable jurisdictional law.


Code: PersNSI
Display: personal non-sensitive information policy
Definition:
Personal policy on collection, access, use, or disclosure of information deemed non-sensitive by the information subject.


Code: PersLDS
Display: personal limited data set information policy
Definition:
Personal policy personal policy on collection, access, use, or disclosure of information in a limited data set by the information subject.


Code: PersPI
Display: personal public information policy
Definition:
Personal policy on collection, access, use, or disclosure of information deemed public by the information subject.


Code: GRANTORCHOICE
Display: grantor choice
Definition:
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.

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.


Code: IMPLIED
Display: implied consent
Definition:
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.

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.


Code: IMPLIEDD
Display: implied consent with opportunity to dissent
Definition:
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.

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.


Code: NOCONSENT
Display: no consent
Definition:
No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement.

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.


Code: OPTIN
Display: opt-in
Definition:
A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms.

Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies.


Code: OPTINR
Display: opt-in with restrictions
Definition:
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.

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.


Code: OPTOUT
Display: opt-out
Definition:
A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms.

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.


Code: OPTOUTE
Display: opt-out with exceptions
Definition:
A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms.

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.


Code: EMRGONLY
Display: opt-in emergency only
Definition:
Privacy consent directive restricting or prohibiting access, use, or disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for all purposes except for emergency treatment generally, which may include treatment during a disaster, a threat, in an emergency department and for break the glass purposes of use as specified by applicable domain policy.


Code: NOPP
Display: notice of privacy practices
Definition:
An implied privacy consent directive or notification, which the data subject may or may not acknowledge.  The notification specifies permitted actions, which may include access, use, or disclosure of any and all personal information.   The notification specifies the scope of personal information, which may include de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, that may be used to identify an individual in a registry or repository. The notification specifies the purposes for which personal information may be used such as treatment, payment, operations, research, information exchange, public health, disaster, quality and safety reporting; as required by law including court order, law enforcement, national security, military authorities; and for data analytics, marketing, and profiling.


Code: OOC
Display: opt-out of personal information or effect collection in a registry or repository
Definition:
An expressed privacy consent directive restricting or prohibiting collection of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling.


Code: OOS
Display: opt-out of personal information or effect sharing via a registry or repository
Definition:
An expressed privacy consent directive restricting or prohibiting access, use, or disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling


Code: OIC
Display: opt-in to personal information or effect collection in a registry or repository
Definition:
An expressed privacy consent directive permitting the collection of a some or all personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling.


Code: OIS
Display: opt-in to personal information or effect sharing via a registry or repository
Definition:
An expressed privacy consent directive permitting access, use, or disclosure of a some or all personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling


Code: 42CFRPart2CD
Display: 42 CFR Part 2 consent directive
Definition:
A code representing consent directive that complies with Section 2.31 Consent requirements https://www.gpo.gov/fdsys/pkg/CFR-2017-title42-vol1/pdf/CFR-2017-title42-vol1-sec2-31.pdf, which is a US Federal law stipulating the policy elements content of a written consent to a disclosure under the regulations in Part 2. 
42 CFR Part 2.31 (a)Required elements for written consent. A written consent to a disclosure under the regulations in this part may be paper or electronic and must include: 
(1) The name of the patient. 
(2) The specific name(s) or general designation(s) of the part 2 program(s), entity(ies), or individual(s) permitted to make the disclosure. 
(3) How much and what kind of information is to be disclosed, including an explicit description of the substance use disorder information that may be disclosed. 
(4) (i) The name(s) of the individual(s) to whom a disclosure is to be made; or 
(ii)Entities with a treating provider relationship with the patient. If the recipient entity has a treating provider relationship with the patient whose information is being disclosed, such as a hospital, a health care clinic, or a private practice, the name of that entity; or 
(iii)Entities without a treating provider relationship with the patient. 
(A) If the recipient entity does not have a treating provider relationship with the patient whose information is being disclosed and is a third-party payer, the name of the entity; or 
(B) If the recipient entity does not have a treating provider relationship with the patient whose information is being disclosed and is not covered by paragraph (a)(4)(iii)(A) of this section, such as an entity that facilitates the exchange of health information or a research institution, the name(s) of the entity(-ies); and 
(1) The name(s) of an individual participant(s); or 
(2) The name(s) of an entity participant(s) that has a treating provider relationship with the patient whose information is being disclosed; or 
(3) A general designation of an individual or entity participant(s) or class of participants that must be limited to a participant(s) who has a treating provider relationship with the patient whose information is being disclosed. 
(i) When using a general designation, a statement must be included on the consent form that the patient (or other individual authorized to sign in lieu of the patient), confirms their understanding that, upon their request and consistent with this part, they must be provided a list of entities to which their information has been disclosed pursuant to the general designation (see Section 2.13(d)). 
(ii) [Reserved] 
(5) The purpose of the disclosure. In accordance with Section 2.13(a), the disclosure must be limited to that information which is necessary to carry out the stated purpose. 
(6) A statement that the consent is subject to revocation at any time except to the extent that the part 2 program or other lawful holder of patient identifying information that is permitted to make the disclosure has already acted in reliance on it. Acting in reliance includes the provision of treatment services in reliance on a valid consent to disclose information to a third-party payer 
(7) The date, event, or condition upon which the consent will expire if not revoked before. This date, event, or condition must ensure that the consent will last no longer than reasonably necessary to serve the purpose for which it is provided. 
(8) The signature of the patient and, when required for a patient who is a minor, the signature of an individual authorized to give consent under Section 2.14; or, when required for a patient who is incompetent or deceased, the signature of an individual authorized to sign under Section 2.15. Electronic signatures are permitted to the extent that they are not prohibited by any applicable law. 
(9) The date on which the consent is signed.


Code: HIPAAAuthCD
Display: HIPAA Authorization Consent Directive
Definition:
A code representing an individual’s consent directive that complies with HIPAA Privacy rule 45 CFR Section 164.508 Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is a US Federal law stipulating the policy elements of a valid authorization under this Section.

An “authorization” is required by the Privacy Rule for uses and disclosures of protected health information not otherwise allowed by the Rule. Where the Privacy Rule requires patient authorization, voluntary consent is not sufficient to permit a use or disclosure of protected health information unless it also satisfies the requirements of a valid authorization. An authorization is a detailed document that gives covered entities permission to use protected health information for specified purposes, which are generally other than treatment, payment, or health care operations, or to disclose protected health information to a third party specified by the individual.

An authorization must specify a number of elements, including a description of the protected health information to be used and disclosed, the person authorized to make the use or disclosure, the person to whom the covered entity may make the disclosure, an expiration date, and, in some cases, the purpose for which the information may be used or disclosed. With limited exceptions, covered entities may not condition treatment or coverage on the individual providing an authorization. https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html
A HIPAA Authorization must comply with 45 CFR Section164.508(c) Implementation specifications: Core elements and requirements – 
(1) Core elements. A valid authorization under this Section must contain at least the following elements: (i) A description of the information to be used or disclosed that identifies the information in a specific and meaningful fashion. 
(ii) The name or other specific identification of the person(s), or class of persons, authorized to make the requested use or disclosure. 
(iii) The name or other specific identification of the person(s), or class of persons, to whom the covered entity may make the requested use or disclosure. 
(iv) A description of each purpose of the requested use or disclosure. The statement “at the request of the individual” is a sufficient description of the purpose when an individual initiates the authorization and does not, or elects not to, provide a statement of the purpose. 
(v) An expiration date or an expiration event that relates to the individual or the purpose of the use or disclosure. The statement “end of the research study,” “none,” or similar language is sufficient if the authorization is for a use or disclosure of protected health information for research, including for the creation and maintenance of a research database or research repository. 
(vi) Signature of the individual and date. If the authorization is signed by a personal representative of the individual, a description of such representative's authority to act for the individual must also be provided. 
(2)Required statements. In addition to the core elements, the authorization must contain statements adequate to place the individual on notice of all of the following: 
(i) The individual's right to revoke the authorization in writing, and either: 
(A) The exceptions to the right to revoke and a description of how the individual may revoke the authorization; or (B) To the extent that the information in paragraph (c)(2)(i)(A) of this section is included in the notice required by Section 164.520, a reference to the covered entity's notice.
https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf


Code: HIPAAConsentCD
Display: HIPAA Consent Directive
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.522 Rights to request privacy protection for protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf, which stipulates the process by which a covered entity seeks agreement from an individual regarding how it will use and disclose the individual's protected health information for treatment, payment, and health care operations is termed a "consent.


Code: HIPAAROACD
Display: HIPAA Right of Access Consent Directive
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.524 Access of individuals to protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-524.pdf, stipulating the policy elements of an individual’s written and signed right of access directive requesting that a covered entity send the individual’s protected health information (PHI) to a third party. 

See 45 CFR 164.524(c)(3)(ii) If an individual's request for access directs the covered entity to transmit the copy of protected health information directly to another person designated by the individual, the covered entity must provide the copy to the person designated by the individual. The individual's request must be in writing, signed by the individual, and clearly identify the designated person and where to send the copy of protected health information.  https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-524.pdf 

This right applies to PHI in a designated record set, which is defined as “Designated record set means: 
(1) A group of records maintained by or for a covered entity that is: 
(i) The medical records and billing records about individuals maintained by or for a covered health care provider; 
(ii) The enrollment, payment, claims adjudication, and case or medical management record systems maintained by or for a health plan; or 
(iii) Used, in whole or in part, by or for the covered entity to make decisions about individuals. [https://www.law.cornell.edu/cfr/text/45/164.501].
Also see HHS Individuals’ Right under HIPAA to Access their Health Information 45 CFR Section 164.524 [https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html#maximumflatfee].


Code: HIPAAResearchAuthCD
Display: HIPAA Authorization for Disclosure for Research Consent Directive
Definition:
A code representing an individual’s consent directive that complies with HIPAA Privacy rule 45 CFR Section 164.508 Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is a US Federal law stipulating the policy elements of a valid authorization under this Section specific to disclosures for purposes of research.


Code: CompoundResearchCD
Display: Compound HIPAA Research Authorization and Informed Consent for Research
Definition:
A code representing an individual’s consent directive that complies with HIPAA Privacy rule 45 CFR Section 164.508 Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is a US Federal law stipulating the policy elements of a valid authorization under this Section specific to disclosures for purposes of research when combined with a Common Rule or Federal Drug Administration consent to participate in research also known as a compound authorization.


Code: MDHHS-5515
Display: Michigan Consent to Share Behavioral Health Information for Care Coordination Purposes
Definition:
Michigan’s standard consent form for the sharing of health information specific to behavioral health and substance use treatment in accordance with Public Act 129 of 2014. In Michigan, while providers are not required to use this new standard form (MDHHS-5515), they are required to accept it.


Code: GDPRCD
Display: GDPR Consent Directive
Definition:
A consent directive compliant with the European Union General Data Protection Regulation (GDPR) definition: Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.

Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data.

If the data subject’s consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language.  Any part of such a declaration which constitutes an infringement of this Regulation shall not be binding.

The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal.  Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent.

When assessing whether consent is freely given, utmost account shall be taken of whether, inter alia, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract.

Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject’s agreement to the processing of personal data relating to him or her, such as by a written statement, including by electronic means, or an oral statement. 

This could include ticking a box when visiting an internet website, choosing technical settings for information society services or another statement or conduct which clearly indicates in this context the data subject’s acceptance of the proposed processing of his or her personal data. 

Silence, pre-ticked boxes or inactivity should not therefore constitute consent. 

Consent should cover all processing activities carried out for the same purpose or purposes. 

When the processing has multiple purposes, consent should be given for all of them. 

If the data subject’s consent is to be given following a request by electronic means, the request must be clear, concise and not unnecessarily disruptive to the use of the service for which it is provided.


Code: GDPRResearchCD
Display: GDPR Research Consent Directive
Definition:
A consent directive that complies with regulatory requirements for a consent directive compliant with the European Union General Data Protection Regulation (GDPR) definition: Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.

GDPR research consent directive has the additional caveat that it is often not possible to fully identify the purpose of personal data processing for scientific research purposes at the time of data collection. Therefore, data subjects should be allowed to give their consent to certain areas of scientific research when in keeping with recognized ethical standards for scientific research. Data subjects should have the opportunity to give their consent only to certain areas of research or parts of research projects to the extent allowed by the intended purpose.


Code: 42CFRPart2
Display: 42 CFR Part 2)
Definition:
A code representing 42 CFR Part 2 Confidentiality of Substance Use Disorder Patient Records. 42 CFR Part 2 stipulates the privacy rights of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program, which includes non-disclosure of health information relating to health care paid for by a federally assisted substance use disorder program without patient consent.  https://www.gpo.gov/fdsys/pkg/CFR-2010-title42-vol1/pdf/CFR-2010-title42-vol1-part2.pdf


Code: COMMONRULE
Display: Common Rule
Definition:
A code representing U.S. Federal laws governing research-related privacy policies known as the “Common Rule”. The Common Rule is the U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46), which 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.


Code: HIPAANOPP
Display: HIPAA notice of privacy practices
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.520), which stipulates an individual’s right to adequate notice of the uses and disclosures of protected health information that may be made by the covered entity, and of the individual's rights and the covered entity's legal duties with respect to protected health information. Relevant HIPAA Privacy  Rule provisions are at  Section 164.520 (a) Standard: Notice of privacy practices. https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-520.pdf


Code: HIPAAPsyNotes
Display: HIPAA psychotherapy notes
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.508), which stipulates the privacy rights of an individual who is the subject of psychotherapy notes, and requires authorization for certain uses and disclosure of that information.

Definition of Psychotherapy notes 45 CFR  Section 164.501 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-501.pdf: Psychotherapy notes means notes recorded (in any medium) by a health care provider who is a mental health professional documenting or analyzing the contents of conversation during a private counseling session or a group, joint, or family counseling session and that are separated from the rest of the individual's medical record. Psychotherapy notes excludes medication prescription and monitoring, counseling session start and stop times, the modalities and frequencies of treatment furnished, results of clinical tests, and any summary of the following items: Diagnosis, functional status, the treatment plan, symptoms, prognosis, and progress to date. 

See Section 164.508 Uses and disclosures for which an authorization is required. (2)Authorization required: Psychotherapy notes https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf: Notwithstanding any provision of this subpart, other than the transition provisions in  Section 164.532, a covered entity must obtain an authorization for any use or disclosure of psychotherapy notes, except: 
(i) To carry out the following treatment, payment, or health care operations: 
(A) Use by the originator of the psychotherapy notes for treatment; 
(B) Use or disclosure by the covered entity for its own training programs in which students, trainees, or practitioners in mental health learn under supervision to practice or improve their skills in group, joint, family, or individual counseling; or 
(C) Use or disclosure by the covered entity to defend itself in a legal action or other proceeding brought by the individual; and 
(ii) A use or disclosure that is required by Section 164.502(a)(2)(ii) or permitted by Section 164.512(a); Section 164.512(d) with respect to the oversight of the originator of the psychotherapy notes;  Section 164.512(g)(1);  Section 164.512(j)(1)(i).


Code: HIPAASelfPay
Display: HIPAA self-pay
Definition:
A code representing 45 CFR 164.522 Rights to request privacy protection for protected health information, which is a US Federal law stipulating the privacy rights of an individual to restrict disclosure of information related to health care items or services for which the individual pays out of pocket in full to a health plan or payer.

See 45 CFR 164.522 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf. (vi) A covered entity must agree to the request of an individual to restrict disclosure of protected health information about the individual to a health plan if: 
(A) The disclosure is for the purpose of carrying out payment or health care operations and is not otherwise required by law; and 
(B) The protected health information pertains solely to a health care item or service for which the individual, or person other than the health plan on behalf of the individual, has paid the covered entity in full.


Code: Title38Section7332
Display: Title 38 Section 7332
Definition:
A code representing Title 38 Section 7332, which is a US Federal law stipulating the privacy rights of veterans diagnosed and treated for substance use disorders, infection with the human immunodeficiency virus, or sickle cell anemia.
Title 38 Section 7332 - Confidentiality of certain medical records
https://www.gpo.gov/fdsys/granule/USCODE-2011-title38/USCODE-2011-title38-partV-chap73-subchapIII-sec7332/content-detail.html  
(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).
(2) Paragraph (1) prohibits the disclosure to any person or entity other than the patient or subject concerned of the fact that a special written consent is required in order for such records to be disclosed.
(b) (1) The content of any record referred to in subsection (a) may be disclosed by the Secretary in accordance with the prior written consent of the patient or subject with respect to whom such record is maintained, but only to such extent, under such circumstances, and for such purposes as may be allowed in regulations prescribed by the Secretary.
(2) Whether or not any patient or subject, with respect to whom any given record referred to in subsection (a) is maintained, gives written consent, the content of such record may be disclosed by the Secretary as follows: 
(A) To medical personnel to the extent necessary to meet a bona fide medical emergency.
(B) To qualified personnel for the purpose of conducting scientific research, management audits, financial audits, or program evaluation, but such personnel may not identify, directly or indirectly, any individual patient or subject in any report of such research, audit, or evaluation, or otherwise disclose patient or subject identities in any manner.
(C) (i) In the case of any record which is maintained in connection with the performance of any program or activity relating to infection with the human immunodeficiency virus, to a Federal, State, or local public-health authority charged under Federal or State law with the protection of the public health, and to which Federal or State law requires disclosure of such record, if a qualified representative of such authority has made a written request that such record be provided as required pursuant to such law for a purpose authorized by such law.
(ii) A person to whom a record is disclosed under this paragraph may not redisclose or use such record for a purpose other than that for which the disclosure was made.
(D) If authorized by an appropriate order of a court of competent jurisdiction granted after application showing good cause therefor. In assessing good cause the court shall weigh the public interest and the need for disclosure against the injury to the patient or subject, to the physician-patient relationship, and to the treatment services. Upon the granting of such order, the court, in determining the extent to which any disclosure of all or any part of any record is necessary, shall impose appropriate safeguards against unauthorized disclosure.
(E) To an entity described in paragraph (1)(B) of section 5701(k) of this title, but only to the extent authorized by such section.
(F) (i) To a representative of a patient who lacks decision-making capacity, when a practitioner deems the content of the given record necessary for that representative to make an informed decision regarding the patient’s treatment.
(ii) In this subparagraph, the term “representative” means an individual, organization, or other body authorized under section 7331 of this title and its implementing regulations to give informed consent on behalf of a patient who lacks decision-making capacity.
(G) To a State controlled substance monitoring program, including a program approved by the Secretary of Health and Human Services under section 399O of the Public Health Service Act (42 U.S.C. 280g–3), to the extent necessary to prevent misuse and diversion of prescription medicines.
(H) (i) To a non-Department entity (including private entities and other Federal agencies) for purposes of providing health care, including hospital care, medical services, and extended care services, to Veterans or performing other health care-related activities or functions. 
(ii) An entity to which a record is disclosed under this subparagraph may not disclose or use such record for a purpose other than that for which the disclosure was made or as permitted by law.
(I) To a third party in order to recover or collect reasonable charges for care furnished to, or paid on behalf of, a Veteran in connection with a non-service connected disability as permitted by section 1729 of this title or for a condition for which recovery is authorized or with respect to which the United States is deemed to be a third party beneficiary under the Act entitled ‘An Act to provide for the recovery from tortiously liable third persons of the cost of hospital and medical care and treatment furnished by the United States’ (Public Law 87–693; 42 U.S.C. 2651 et seq.; commonly known as the ‘Federal Medical Care Recovery Act’).


Code: HIPAAConsent
Display: HIPAA Consent
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.522), which stipulates the process by which a covered entity seeks agreement from an individual regarding how it will use and disclose the individual's protected health information for treatment, payment, and health care operations is termed a "consent."  The Privacy Rule permits, but does not require, a covered entity to voluntarily obtain patient consent for uses and disclosures of protected health information for treatment, payment, and health care operations. Covered entities that do so have complete discretion to design a process that best suits their needs. From https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html. The provisions relating to consent are largely contained in  Section 164.522 Rights to request privacy protection for protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf


Code: HIPAAAuth
Display: HIPAA Authorization for Disclosure
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.508) Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which stipulates the process by which a covered entity seeks agreement from an individual to use or disclose protected health information for other purposes, or to authorize another covered entity to disclose protected health information to the requesting covered entity, are termed ""authorizations"".

An “authorization” is required by the Privacy Rule for uses and disclosures of protected health information not otherwise allowed by the Rule. Where the Privacy Rule requires patient authorization, voluntary consent is not sufficient to permit a use or disclosure of protected health information unless it also satisfies the requirements of a valid authorization. An authorization is a detailed document that gives covered entities permission to use protected health information for specified purposes, which are generally other than treatment, payment, or health care operations, or to disclose protected health information to a third party specified by the individual.

An authorization must specify a number of elements, including a description of the protected health information to be used and disclosed, the person authorized to make the use or disclosure, the person to whom the covered entity may make the disclosure, an expiration date, and, in some cases, the purpose for which the information may be used or disclosed. With limited exceptions, covered entities may not condition treatment or coverage on the individual providing an authorization. https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html


Code: HIPAAROA
Display: HIPAA Right of Access
Definition:
A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.524 Access of individuals to protected health information https://www.govinfo.gov/app/details/CFR-2017-title45-vol1/CFR-2017-title45-vol1-sec164-524, which stipulates that an individual has a right of access to inspect and obtain a copy of protected health information about the individual in a designated record set, for as long as the protected health information is maintained in the designated record set with exceptions stipulated in HIPAA Privacy Rule Section 164.524. Exceptions include psychotherapy notes and information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding.

If an individual's request for access directs the covered entity to transmit the copy of protected health information directly to another person designated by the individual, the covered entity must provide the copy to the person designated by the individual. The individual's request must be in writing, signed by the individual, and clearly identify the designated person and where to send the copy of protected health information.

For discussion on extent of right, grounds for denial, and documentation requirements see: HHS Individuals’ Right under HIPAA to Access their Health Information 45 CFR Section 164.524 https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html and HHS FAQ on Right of Access vs. HIPAA Authorization https://www.hhs.gov/hipaa/for-professionals/faq/2041/why-depend-on-the-individuals-right/index.html


Code: GDPRCONSENT
Display: GDPR Consent
Definition:
Processing of personal data, inclusive of the special categories of data, is lawful only if the data subject has given explicit consent to the processing of his or her personal data, inclusive of the special categories of data, for one or more specific purposes, except where Union or Member State law provide that the prohibition to use the data may not be lifted by the data subject; and for personal data which are manifestly made public by the data subject.


Code: GDPRCONTRACT
Display: GDPR contract
Definition:
Processing of personal data, inclusive of the special categories of data, is lawful only if necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract.


Code: GDPRHLTHSOCSY
Display: GDPR health or social system management
Definition:
Processing of special categories of data is lawful if necessary for archiving purposes the management of health or social care systems and services on the basis of Union or Member State law or pursuant to contract with a health professional.


Code: GDPRLEGALCLAIM
Display: GDPR legal claim
Definition:
Processing of special categories of data is lawful if necessary for the establishment, exercise or defense of legal claims or whenever courts are acting in their judicial capacity.


Code: GDPRLEGALOBL
Display: GDPR legal obligation
Definition:
Processing of personal data, inclusive of the special categories of data, is lawful if necessary for compliance with a legal obligation to which the controller is subject. 

This includes the processing of the special categories of data that are necessary for the purposes of carrying out the obligations and exercising specific rights of the controller or of the data subject in the field of employment and social security and social protection law in so far as it is authorised by Union or Member State law or a collective agreement pursuant to Member State law providing for appropriate safeguards for the fundamental rights and the interests of the data subject.


Code: GDPRLEGITINTEREST
Display: GDPR legitimate interest
Definition:
Processing of personal data, inclusive of the special categories of data, is lawful if necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. 

This includes the processing of the special categories of data that are carried out in the course of its legitimate activities with appropriate safeguards by a foundation, association or any other not-for-profit body with a political, philosophical, religious or trade union aim and on condition that the processing relates solely to the members or to former members of the body or to persons who have regular contact with it in connection with its purposes and that the personal data are not disclosed outside that body without the consent of the data subjects.


Code: GDPRPUBLICHEALTH
Display: GDPR public health
Definition:
Processing of special categories of data is lawful if necessary for reasons of public interest in the area of public health, such as protecting against serious cross-border threats to health or ensuring high standards of quality and safety of health care and of medicinal products or medical devices, on the basis of Union or Member State law which provides for suitable and specific measures to safeguard the rights and freedoms of the data subject, in particular professional secrecy.


Code: GDPRPUBLICINTEREST
Display: GDPR public interest
Definition:
Processing of personal data, inclusive of the special categories of data, is lawful if necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller. This includes the processing of the special categories of data that are necessary for reasons of substantial public interest, on the basis of Union or Member State law which shall be proportionate to the aim pursued, respect the essence of the right to data protection and provide for suitable and specific measures to safeguard the fundamental rights and the interests of the data subject.


Code: GDPRRESEARCH
Display: GDPR research
Definition:
Processing of special categories of data is lawful if necessary for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Article 89(1) based on Union or Member State law which shall be proportionate to the aim pursued, respect the essence of the right to data protection and provide for suitable and specific measures to safeguard the fundamental rights and the interests of the data subject.


Code: GDPRVITALINTEREST
Display: GDPR vital interest
Definition:
Processing of personal data, inclusive of the special categories of data, is lawful if necessary to protect the vital interests of the data subject or of another natural person where the data subject is physically or legally incapable of giving consent. This includes the processing of the special categories of data that are necessary for the purposes of preventive or occupational medicine, for the assessment of the working capacity of the employee, medical diagnosis, the provision of health or social care or treatment or the management of health or social care systems and services on the basis of Union or Member State law or pursuant to contract with a health professional and subject to the conditions and safeguards when those data are processed by or under the responsibility of a professional subject to the obligation of professional secrecy under Union or Member State law or rules established by national competent bodies or by another person also subject to an obligation of secrecy under Union or Member State law or rules established by national competent bodies.


Code: CR
Display:
Callback results - filler should contact the placer as soon as results are available, even for preliminary results

Definition:
Callback results - filler should contact the placer as soon as results are available, even for preliminary results


Code: CSR
Display:
Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service

Definition:
Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service


Code: EM
Display:
Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action

Definition:
Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action


Code: P
Display:
Preop - Used to indicate that a service is to be performed prior to a scheduled surgery.  When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service.  When the order

Definition:
Preop – Used to indicate that a service is to be performed prior to a scheduled surgery.  When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service.  When the order is placed, a message can be generated indicating the time needed for the service so that it is not ordered in conflict with a scheduled operation.


Code: PRN
Display:
As needed - An "as needed" order should be accompanied by a description of what constitutes a need.  This description is represented by an observation service predicate as a precondition.

Definition:
As needed - An "as needed" order should be accompanied by a description of what constitutes a need.  This description is represented by an observation service predicate as a precondition.


Code: T
Display:
Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level).

Definition:
Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level).


Code: B
Display:
Business - 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.  However, no patient related inf

Definition:
Business – 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.  However, no patient related information may ever be of this confidentiality level.


Code: D
Display:
Clinician - Only clinicians may see this item, billing and administration persons can not access this item without special permission.

Definition:
Clinician - Only clinicians may see this item, billing and administration persons can not access this item without special permission.


Code: I
Display:
Individual - Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor typed code).

Definition:
Individual - Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor typed code).


Code: L
Display:
Low - No patient record item can be of low confidentiality.  However, some service objects are not patient related and therefore may have low confidentiality.

Definition:
Low - No patient record item can be of low confidentiality.  However, some service objects are not patient related and therefore may have low confidentiality.


Code: N
Display:
Normal - Normal confidentiality rules (according to good health care practice) apply, that is, only authorized individuals with a legitimate medical or business need may access this item.

Definition:
Normal - Normal confidentiality rules (according to good health care practice) apply, that is, only authorized individuals with a legitimate medical or business need may access this item.


Code: R
Display:
Restricted - Restricted access, e.g. only to providers having a current care relationship to the patient.

Definition:
Restricted - Restricted access, e.g. only to providers having a current care relationship to the patient.


Code: C
Display:
Celebrity - Celebrities are people of public interest (VIP) including employees, whose information require special protection.

Definition:
Celebrity - Celebrities are people of public interest (VIP) including employees, whose information require special protection.


Code: S
Display:
Sensitive - Information for which the patient seeks heightened confidentiality.  Sensitive information is not to be shared with family members.  Information reported by the patient about family members is sensitive by default.  Flag can be set or cleared

Definition:
Sensitive – Information for which the patient seeks heightened confidentiality.  Sensitive information is not to be shared with family members.  Information reported by the patient about family members is sensitive by default.  Flag can be set or cleared on patient's request.


Code: T
Display:
Taboo - Information not to be disclosed or discussed with patient except through physician assigned to patient in this case.  This is usually a temporary constraint only; example use is a new fatal diagnosis or finding, such as malignancy or HIV.

Definition:
Taboo - Information not to be disclosed or discussed with patient except through physician assigned to patient in this case.  This is usually a temporary constraint only; example use is a new fatal diagnosis or finding, such as malignancy or HIV.


Code: SWNL
Display:
Share Within Normal Limits -<p>Share result in reference/therapeutic range with patient immediately<p>Share result out of reference/therapeutic ranges with patient after 1 or more business day as agreed to by the systems in play.

Definition:
Share Within Normal Limits -<p>Share result in reference/therapeutic range with patient immediately<p>Share result out of reference/therapeutic ranges with patient after 1 or more business day as agreed to by the systems in play.


Code: SID
Display:
Share In1 Day -<p>Share result regardless of reference/therapeutic range after 1 or more business day as agreed to by the systems in play.

Definition:
Share In1 Day -<p>Share result regardless of reference/therapeutic range after 1 or more business day as agreed to by the systems in play.


Code: SIDC
Display:
Share in 1 Day Conditionally -<p>Share result in reference ranges/therapeutic with patient after 1 or more business day as agreed to by the systems in play.<p>Withhold result out of reference/therapeutic range until physician release

Definition:
Share in 1 Day Conditionally -<p>Share result in reference ranges/therapeutic with patient after 1 or more business day as agreed to by the systems in play.<p>Withhold result out of reference/therapeutic range until physician release


Code: AHP
Display: Authorized Performing Health Professional
Definition:
The specific Health Professional who has been approved to perform the ordered services for the patient.


Code: APO
Display: Authorized Performing Provider Organization
Definition:
The Provider Organization that has been approved to perform the sanctioned procedures to which the patient was referred to.


Code: FL
Display: From Location
Definition:
Describes the location (coordinates) of the specimen/container in the previous holder / storage equipment before the move or the geographical location from which the specimen/container was moved.


Code: TL
Display: To Location
Definition:
Describes the location (coordinates) of the specimen/container in the previous holder / storage equipment after the move or the geographical location to which the specimen/container was moved.


Code: VP
Display: Verifier (Verifying Person)
Definition:
Identifies the person verifying the dispense / a step in the dispense process / verifying the treatment corresponds to the order


Code: D
Display:
In some cases, this test should be only exclusively with like tests (examples are cyto or pathology)

Definition:
In some cases, this test should be only exclusively with like tests (examples are cyto or pathology)


Code: MCS
Display: Micro Culture Status
Definition:
Sub-type of RSLT (Result) This term identifies observations that give overall culture outcome, when no specific organism is being named.


Code: MIG
Display: Micro Isolate Growth Quantity
Definition:
Sub-type of RSLT (Result) This term identifies growth levels of an isolate – can be numeric or categorical.


Code: MIN
Display: Micro Isolate Name
Definition:
Sub-type of RSLT (Result) This term identifies observations that name a specific organism either at the species or the genus level.


Code: MOD
Display: Micro Other Descriptor
Definition:
Sub-type of RSLT (Result) This term identifies observations that do not fit the culture status, but is not at the isolate level.


Code: MSS
Display: Micro Sample Stain
Definition:
Sub-type of RSLT (Result) This term identifies observations on gram stains (and other stains or smears) on the clinical sample.


Code: INTF
Display: Interferes / interfered
Definition:
Source universal service identifier interferes / interfered with fulfilment of target universal service identifier


Code: LIMIT
Display: Limits/limited
Definition:
Source universal service identifier limits/limited the fulfillment of target universal service identifier


Code: SUCCD
Display: Succeeds
Definition:
Target universal service identifier should succeed (starts after end of) source universal service identifier


Code: SVTGT
Display: Service target
Definition:
Target universal service identifier is the object of the service identified by the source universal service identifier


Code: IT
Display: Incorrect test performed
Definition:
For process improvement work this code can be used to identify when an incorrect test was performed for the target order


Code: OP
Display: Test ordering problem
Definition:
For process improvement work this code can be used to identify orders and the respective results, where problems occurred during ordering


Code: PI
Display: Patient identification problem
Definition:
For process improvement work this code can be used to identify when a patient identification issue has occurred on the target order


Code: SP
Display: Sampling problem
Definition:
For process improvement work this code can be used to identify orders, where problems occurred during sample collection


Code: TP
Display: Specimen transport problem
Definition:
For process improvement work this code can be used to identify orders, where problems occurred during sample transport


Code: TT
Display: Turnaround time problem
Definition:
For process improvement work this code can be used to identify results with excessive reporting delay


Code: XR
Display: Incorrect results
Definition:
For process improvement work this code can be used to identify when incorrect result were reported for the target order


Code: 2
Display: update not necessary
Definition:
English: update of insurance information on card not necessary

German: Keine Aktualisierung VSD auf eGK erforderlich


Code: 3
Display: Error
Definition:
English: An unrecoverable error occurred during the update or verification of the insurance information

German: Aktualisierung VSD auf eGK war nicht möglich


Code: 1
Display: Update technically not possible
Definition:
English: update of insurance date on card technically not possible

German: Aktualisierung VSD auf eGK technisch nicht möglich


Code: 3
Display: Online verification technically not possible
Definition:
English: online verification of authentication certificate is technically not possible

German: Onlineprüfung des Authentifizierungszerti-fikats technisch nicht möglich


Code: 4
Display: Update technically not possible due to offline time exceeded
Definition:
English: update of insurance date is technically not possible due to maximum offline time exceeded

German: Aktualisierung VSD auf eGK technisch nicht möglich weil maximaler Offline-Zeitraum überschritten


Code: 0005
Display: Race
Definition:
Table of codes specifying the patient's race. These values are suggestions only, they are not required for use in HL7 messages.


Code: 0008
Display: Acknowledgment code
Definition:
HL7-defined table of codes specifying acknowledgment codes used in Version 2.x message.  For details of usage, see message processing rules in the published Standard.


Code: 0012
Display: STOCK LOCATION
Definition:
Table of codes specifying the stock location.  Table is no longer published as part of the relased standard after version 2.2.


Code: 0021
Display: Bad Debt Agency Code
Definition:
Table of codes specifying the bad debt agency to which the account was transferred.  No suggested values.


Code: 0022
Display: Billing Status
Definition:
Table of codes specifying whether the particular insurance has been billed and, if so, the type of bill.  No suggested values.


Code: 0024
Display: Fee Schedule
Definition:
Table of codes specifying the appropriate fee schedule to be used for this transaction posting.  No suggested values.


Code: 0032
Display: Charge/Price Indicator
Definition:
Table of codes specifying which price schedule is to be used for room and bed charges.  No suggested values.


Code: 0033
Display: ROUTE
Definition:
Table of codes that indicate a means of administrating a medication dose. As of HL7 version 2.3, it was replaced by tables 0162 Route of Administration and table 0165 Administration Method.


Code: 0034
Display: SITE ADMINISTERED
Definition:
Table of codes specifying a location on the body where a dose is to be administered, e.g., IV, IM, Subcutaneous.   Used in HL7 Version 2.1 messaging only in the RX1 segment; as of version 2.2 it has been replaced with table 0163 Body Site.


Code: 0038
Display: Order status
Definition:
HL7-defined table of codes specifying the status of an order. The purpose of these values are to report the status of an order either upon request (solicited), or when the status changes (unsolicited). The values are not intended to initiate action.  It is assumed that the order status value always reflects the status as it is known to the sending application at the time that a message is sent.  Only the filler can originate these values.


Code: 0043
Display: Condition Code
Definition:
Table of codes specifying the condition code.  These codes are defined by CMS or other regulartory agencies.  No suggested values.


Code: 0044
Display: Contract Code
Definition:
Table of codes specifying the type of contract entered into by the healthcare facility and the guarantor for the purpose of settling outstanding account balances.  No suggested values.


Code: 0045
Display: Courtesy Code
Definition:
Table of codes specifying whether the patient will be extended certain special courtesies.  No suggested values.


Code: 0047
Display: DANGER CODE
Definition:
HL7-defined table of concepts which specify actions to be taken with respect to the specimens that accompany or precede an order.  The purpose of these are to further qualify (when appropriate) the general action indicated by the order control code  (code system 2.16.840.1.133883.18.25).


Code: 0048
Display: What subject filter
Definition:
HL7-defined table of concepts which specify the kind of information that is required to satisfy a query request.  The values define the type of transaction inquiry.


Code: 0049
Display: Department Code
Definition:
Table of codes specifying the department code that controls the transaction code.  No suggested values.


Code: 0053
Display: Diagnosis Coding Method
Definition:
Table of codes specifying a diagnosis coding method.  No suggested values.  Table is no longer published as part of the released standard after version 2.5.1.


