v2+ Vocabulary
0.2.0 - Working Draft to present the concept ideas (FO)
v2+ Vocabulary - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Codesystem tableNo |
extension for tableNo |
| Codesystem v2versionCreated |
extension for v2versionCreated |
| Codesystem versionHistory |
extension for versionHistory |
| Codesystem versionIntroduced |
extension for versionIntroduced |
These define sets of codes used by systems conforming to this implementation guide.
| ABNORMAL FLAGS (2.1 - 1.0.0) |
A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. |
| ABNORMAL FLAGS (2.2 - 1.1.0) |
A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. |
| ACCEPT/APPLICATION ACKNOWLEDGEMENT CONDITIONS (2.2 - 1.0.0) |
Concepts which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode. |
| ACKNOWLEDGMENT CODE (2.1 - 1.0.0) |
Concepts specifying acknowledgment codes used in Version 2.x message. For details of usage, see message processing rules in the published Standard. |
| ACKNOWLEDGMENT CODE (2.2 - 1.1.0) |
Concepts specifying acknowledgment codes used in Version 2.x message. For details of usage, see message processing rules in the published Standard. |
| ACTION CODE (2.2 - 2.0.0) |
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 xxxx). |
| ADMINISTRATION DEVICE (2.2 - 1.0.0) |
Value Set of codes that specify the mechanical device used to aid in the administration of the drug or other treatment. Common examples are IV-sets of different types. |
| ADMINISTRATION METHOD (2.2 - 1.0.0) |
Value Set of codes that specify the specific method requested for the administration of the drug or treatment to the patient. |
| ADMINISTRIVE SITE (2.2 - 1.0.0) |
Concepts that specify a body site from which a specimen is obtained. |
| ALLERGY SEVERITY (2.2 - 1.0.0) |
Value Set of codes that specify the general severity of an allergy. |
| ALLERGY TYPE (2.2 - 1.0.0) |
Value Set of codes that specify classification of general allergy categories (drug, food, pollen, etc.). |
| ALLOW SUBSTITUTION (2.2 - 1.0.0) |
Value Set of codes that specify whether substitutions are allowed and, if so, the type of substitutions allowed. |
| AMOUNT TYPE (2.2 - 1.0.0) |
Value Set of codes that specify amount quantity type. |
| ASSIGNMENT OF BENEFITS (2.2 - 1.0.0) |
Value Set of codes 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. |
| Access Restriction Reason Code (2.6 - 1.0.0) |
Value Set of codes that specify the reason for the restricted access. |
| Access Restriction Value (2.6 - 1.0.0) |
Value Set of codes that specify the information to which access is restricted. Note that the new codes as of November 2018 have been temporarily loaded into the underlying V2 code system pending availability of the currently unavailable new tooling, at which time this value set will be retired and a value set based on the HL7 V3 ActCode code system will be used instead for this table, and the rendered URL will be valid at terminology.hl7.org. |
| Access Restriction Value (2.9 - 1.1.0) |
Value Set of codes that specify the information to which access is restricted. Note that the new codes as of November 2018 have been temporarily loaded into the underlying V2 code system pending availability of the currently unavailable new tooling, at which time this value set will be retired and a value set based on the HL7 V3 ActCode code system will be used instead for this table, and the rendered URL will be valid at terminology.hl7.org. |
| ActPriority (2.7 - 1.0.0) |
Value Set of codes specifying the priority for a shipment. |
| Action Code (2.3 - 1.0.0) |
Status codes of record operations. |
| Action Code (2.5 - 1.1.0) |
Status codes of record operations. |
| Action Taken in Response to the Event (2.3 - 1.0.0) |
Value Set of codes that define the action taken as a result of an event related to a product issue. |
| Active/Inactive (2.2 - 1.0.0) |
Value Set of codes that specify whether a person is currently a valid staff member. |
| Additive (2.4 - 1.0.0) |
Concepts specifying 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. Used in Version 2 messaging in the SPM segment. |
| Additive/Preservative (2.5 - 1.1.0) |
Concepts specifying 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. Used in Version 2 messaging in the SPM segment. |
| Address Expiration Reason (2.6 - 1.0.0) |
Value Set of codes that specify the reason this address was marked as “ended”. |
| Address Type (2.3 - 1.1.0) |
Concepts specifying types or kinds of addresses. |
| Address Type (2.7 - 1.4.0) |
Concepts specifying types or kinds of addresses. |
| Address Usage (2.6 - 1.0.0) |
Value Set of codes that specify how an address is intended to be used. |
| Address type (2.3.1 - 1.2.0) |
Concepts specifying types or kinds of addresses. |
| Address type (2.6 - 1.3.0) |
Concepts specifying types or kinds of addresses. |
| Adjustment Action (2.6 - 1.0.0) |
Value Set of codes used to specify the action requested of a party that receives an adjustment. |
| Adjustment Category Code (2.6 - 1.0.0) |
Value Set of codes used to specify the category of adjustment and is used to assist in determining which table is used for Adjustment Reason. |
| Administration Method (2.6 - 1.1.0) |
Value Set of codes that specify the specific method requested for the administration of the drug or treatment to the patient. |
| Administrative Sex (2.4 - 2.0.0) |
Concepts specifying a patient’s sex for administrative purposes. |
| Administrative Sex (2.9 - 3.0.0) |
Concepts specifying a patient’s sex for administrative purposes. |
| Administrative Site (2.3 - 1.1.0) |
Concepts that specify a body site from which a specimen is obtained. |
| Administrative site (2.3.1 - 1.2.0) |
Concepts that specify a body site from which a specimen is obtained. |
| Admission Type (2.1 - 1.0.0) |
Value Set of codes that specify the circumstances under which the patient was or will be admitted. |
| Admission Type (2.4 - 1.1.0) |
Value Set of codes that specify the circumstances under which the patient was or will be admitted. |
| Admission level of care code (2.4 - 1.0.0) |
Value Set of codes specifying the acuity level assigned to the patient at the time of admission. |
| Admit source (2.3.1 - 1.0.0) |
Value Set of codes that specify where the patient was admitted. No suggested values. |
| Adress Type (2.2 - 1.0.0) |
Concepts specifying types or kinds of addresses. |
| Advanced Beneficiary Notice Code (2.3.1 - 1.0.0) |
Status codes specifying a patient’s or a patient’s representative’s consent for responsibility to pay for potentially uninsured services. Note that this set of codes is generally used in the US only. |
| Alert device code (2.4 - 1.0.0) |
Value Set of codes specifying any type of allergy alert device the patient may be carrying or wearing. |
| Alert level (2.4 - 1.0.0) |
Value Set of codes 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). |
| Allergen type (2.4 - 1.1.0) |
Value Set of codes that specify classification of general allergy categories (drug, food, pollen, etc.). |
| Allergy Clinical Status (2.4 - 1.0.0) |
Value Set of codes specifying the verification status for the allergy. |
| Allergy severity (2.4 - 1.1.0) |
Value Set of codes that specify the general severity of an allergy. |
| Allow Substitution Codes (2.3 - 1.0.0) |
Value Set of codes that indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment. |
| Alternate Character Sets (2.3 - 1.0.0) |
Value Set of codes that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte. |
| Alternate Character Sets (2.8 - 1.4.0) |
Value Set of codes that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte. |
| Alternate character set handling scheme (2.3.1 - 1.0.0) |
Concepts 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. |
| Alternate character sets (2.3.1 - 1.1.0) |
Value Set of codes that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte. |
| Alternate character sets (2.5 - 1.2.0) |
Value Set of codes that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte. |
| Alternate character sets (2.6 - 1.3.0) |
Value Set of codes that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte. |
| Ambulatory Payment Classification code (2.4 - 1.0.0) |
Value Set of codes that specify the derived Ambulatory Payment Classification (APC) code. |
| Ambulatory Status (2.1 - 1.0.0) |
Value Set of codes that specify permanent or transient handicapped conditions of a person. |
| Amount Class (2.2 - 1.0.0) |
Value Set of codes that specify the amount quantity class. |
| Analyte Repeat Status (2.4 - 1.0.0) |
Value Set of codes 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 r |
| Annotations (2.3 - 1.0.0) |
Value Set of codes that specify 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. |
| Appointment Reason Codes (2.3 - 1.0.0) |
Value Set of codes that describe the kind of appointment or the reason why an appointment has been scheduled. |
| Appointment Type Codes (2.3 - 1.0.0) |
Value Set of codes that an appointment request to describe the kind of appointment. |
| Arm Stick (2.8 - 1.0.0) |
Value Set of codes specifying the arm(s) receiving a stick. |
| Artificial blood (2.4 - 1.0.0) |
Value Set of codes that identify the artificial blood identifier associated with the specimen. |
| Assigning authority (2.4 - 1.0.0) |
Example values ONLY for Assigning Authority, and only pubished in HL7 Version 2.4; coded values for fields that are intended to specify Assinging Authority are intended to be locally user defined codes. |
| Authorization Mode (2.5 - 1.0.0) |
Concepts of forms of authorization a recorder may receive from the responsible practitioner to create or change an order. Used in Version 2 messaging for orders in the ORC segment. |
| Auto-Dilution Type (2.9 - 1.0.0) |
Value Set of codes that specify the pre‑configured dilution to be applied on the instrument, which can be used instead of a numeric declaration. |
| BED STATUS (2.1 - 1.0.0) |
Value Set of codes that specify the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not. |
| BED STATUS (2.2 - 1.1.0) |
Value Set of codes that specify the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not. |
| BP Observation Status Codes Interpretation (2.5 - 1.0.0) |
Value Set of codes that 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 c |
| Blood Product Code (2.4 - 1.0.0) |
Value Set of codes specifying the blood product code. |
| Blood Product Dispense Status (2.5 - 1.0.0) |
Value Set of codes that 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 fir |
| Blood Product Processing Requirements (2.5 - 1.0.0) |
Value Set of codes 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 t |
| Blood Product Transfusion/Disposition Status (2.5 - 1.0.0) |
Value Set of codes that 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 co |
| Blood Product Transfusion/Disposition Status (2.9 - 1.1.0) |
Value Set of codes that 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 co |
| Blood Unit Type (2.8 - 1.0.0) |
Value Set of codes used to specify the type of blood unit |
| Body Parts (2.5 - 1.0.0) |
Value Set of codes that specify the part of the body. |
| Body Site Modifier (2.5 - 1.0.0) |
Value Set of codes that specify the modifier for the body site. |
| Bolus Type (2.8 - 1.0.0) |
Value Set of codes specifying a type of bolus. |
| CCL Value (2.6 - 1.0.0) |
Value Set of codes that specify the clinical complexity level (CCL) value for the determined diagnosis related group (DRG) for this diagnosis. |
| CHARGE TYPE (2.1 - 1.0.0) |
Value Set of codes that specify someone or something other than the patient to be billed for a service. |
| CONFIDENTIALITY CODE (2.2 - 1.0.0) |
Value Set of codes that specify the degree to which special confidentiality protection should be applied to the observation. |
| COORDINATION OF BENEFITS (2.2 - 1.0.0) |
Value Set of codes that specify 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. |
| CP Range Type (2.3 - 1.0.0) |
Value Set of codes that specify whether a composite price range is experssed as a flat rate or a percentage. |
| CWE statuses (2.3.1 - 1.0.0) |
Concepts 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. |
| Calendar Alignment (2.5 - 1.0.0) |
Value Set of codes that specify an alignment of the repetition to a calendar (e.g., to distinguish every 30 days from “the 5th of every month”). |
| Causality Observations (2.3 - 1.0.0) |
Value Set of codes that record event observations regarding what may have caused a product related event. |
| Certificate Status (2.5 - 1.0.0) |
Value Set of codes that specify the status of the certificate held by a health professional. |
| Certification Category Code (2.8 - 1.0.0) |
Value Set of codes specifying the code for a certification category. |
| Certification Status (2.3 - 1.0.0) |
Value Set of codes that specify the status of the practitioner’s speciality certification. |
| Certification Type Code (2.8 - 1.0.0) |
Value Set of codes specifying the code for a certification type. |
| Charge Type Reason (2.5 - 1.0.0) |
Value Set of codes that specify the choice of, and providing the clinical rationale for, a selected charge type. |
| Charge on Indicator (2.3 - 1.0.0) |
Value Set of codes that define the event upon which a charge should be generated. |
| Check Digit Scheme (2.1 - 1.0.0) |
Concepts used to identify the check digit scheme employed when a check digit is used in various HL7 Version 2.x datatypes. |
| Check Digit Scheme (2.2 - 1.1.0) |
Concepts used to identify the check digit scheme employed when a check digit is used in various HL7 Version 2.x datatypes. |
| Check Digit Scheme (2.3.1 - 1.2.0) |
Concepts used to identify the check digit scheme employed when a check digit is used in various HL7 Version 2.x datatypes. |
| Check Digit Scheme (2.6 - 1.3.0) |
Concepts used to identify the check digit scheme employed when a check digit is used in various HL7 Version 2.x datatypes. |
| Coding System (2.4 - 1.0.0) |
Names of coding systems. Each coding system is assigned a unique identifier, which is generally a short mnemonic derived from the full name of the coding system. |
| Coding System (2.6 - 1.1.0) |
Names of coding systems. Each coding system is assigned a unique identifier, which is generally a short mnemonic derived from the full name of the coding system. |
| Coding System (2.7 - 1.2.0) |
Names of coding systems. Each coding system is assigned a unique identifier, which is generally a short mnemonic derived from the full name of the coding system. |
| Coding System (2.9 - 1.3.0) |
Names of coding systems. Each coding system is assigned a unique identifier, which is generally a short mnemonic derived from the full name of the coding system. |
| Coding System (2.9.1 - 1.4.0) |
Names of coding systems. Each coding system is assigned a unique identifier, which is generally a short mnemonic derived from the full name of the coding system. |
| Collection Event/Process Step Limit (2.8.2 - 1.0.0) |
Value Set of codes specifying the limit for a collection event or process step. |
| Command Response (2.4 - 1.0.0) |
Value Set of codes identifying the response of the previously issued command. |
| Comment type (2.3.1 - 1.0.0) |
Value Set of codes that identify the type of comment text being sent in the specific comment record. |
| Communication Location (2.8.2 - 1.0.0) |
Value Set of codes specifying a communication location. |
| Completion Status (2.3 - 1.0.0) |
Status codes used in the workflow of treatment administration events. |
| Computation Type (2.5 - 1.0.0) |
Value Set of codes that specify if the change is computed as a percent change or as an absolute change. |
| Condition code (2.3.1 - 1.0.0) |
Value Set of codes that specify the condition code. |
| Confidentiality (2.7 - 1.0.0) |
Value Set of codes specifying the confidentiality for a shipment. |
| Consent Bypass Reason (2.5 - 1.0.0) |
Value Set of codes that specify the reason the subject’s consent was not sought. |
| Consent Disclosure Level (2.5 - 1.0.0) |
Value Set of codes that specify how much information was disclosed to the subject as part of the informed consent process. |
| Consent Mode (2.5 - 1.0.0) |
Value Set of codes that specify the method in which a subject provides consent. |
| Consent Non-Disclosure Reason (2.5 - 1.0.0) |
Value Set of codes that specify a reason the subject did not receive full disclosure. |
| Consent Status (2.5 - 1.0.0) |
Value Set of codes that specify whether the consent has been sought and granted. |
| Consent Type (2.5 - 1.0.0) |
Value Set of codes that specify to what the subject is consenting, i.e. what type of service, surgical procedure, information access/release or other event. |
| Contact Role (2.3 - 1.0.0) |
Concepts which specify the relationship role (next of kin, employer, emergency contact, etc.) and specifies the role that a next of kin/associated parties plays with regard to a patient. |
| Contact Role (2.5 - 1.0.0) |
Concepts which specify a relationship role that the next of kin/associated parties plays with regard to the patient. Built on the updated code system. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that sent a referral. |
| Container Condition (2.7 - 1.0.0) |
Value Set of codes that 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 |
| Container Status (2.9 - 2.0.0) |
Value Set of codes that identify the status of the unique container in which the specimen resides at the time the transaction was initiated. |
| Container status (2.4 - 1.0.0) |
Value Set of codes that identify the status of the unique container in which the specimen resides at the time the transaction was initiated. |
| Continuation style code (2.4 - 1.0.0) |
Value Set of codes identifying whether it is a fragmented message or part of an interactive continuation message. |
| Controlled Substance Schedule (2.5 - 1.0.0) |
Value Set of codes that specify the class of the drug or other substance if its usage is controlled by legislation. |
| Coverage Type (2.3 - 1.0.0) |
Note that this set of codes is used generally in the US only. |
| Coverage Type (2.6 - 1.1.0) |
Note that this set of codes is used generally in the US only. |
| Cumulative Dosage Limit UoM (2.8 - 1.0.0) |
Value Set of codes specifying the unit of measure (UoM) for the cumulative dosage limit. |
| Cycle Type (2.6 - 1.0.0) |
Value Set of codes that specify the type of cycle that is being executed. A cycle type is a specific sterilization method used for a specific type of supply item. |
| Cyclic Entry/Exit Indicator (2.5 - 1.0.0) |
Value Set of codes that specify if this service request is the first or last service request in a cyclic series of service requests. |
| Cyclic Entry/Exit Indicator (2.9 - 1.1.0) |
Value Set of codes that specify if this service request is the first or last service request in a cyclic series of service requests. |
| DATE/TIME QUALIFIER (2.2 - 1.0.0) |
Value Set of codes that specify the type of date referred to in the other date fields in the QRF segment. |
| DATE/TIME SELECTION QUALIFIER (2.2 - 1.0.0) |
Value Set of codes that allow the specification of certain types of values within the date/time range. |
| DAY TYPE (2.2 - 1.0.0) |
Value Set of codes that specify whether the days are denied, pending or approved. |
| DEFERRED RESPONSE TYPE (2.1 - 1.0.0) |
Value Set of codes which specify which type of deferred query resonse is desired, as specified with the query parameters. |
| DEFERRED RESPONSE TYPE (2.2 - 1.1.0) |
Value Set of codes which specify which type of deferred query resonse is desired, as specified with the query parameters. |
| DELAYED ACKNOWLEDGMENT TYPE (2.1 - 1.0.0) |
Concepts which specify a response type used in deferred processing two phase reply for delayed acknowldgement mode of the original acknowledgement mechanism defined in HL7 Version 2.x messaging. |
| DELAYED ACKNOWLEDGMENT TYPE (2.2 - 1.1.0) |
Concepts which specify a response type used in deferred processing two phase reply for delayed acknowldgement mode of the original acknowledgement mechanism defined in HL7 Version 2.x messaging. |
| DERIVED SPECIMEN (2.2 - 1.0.0) |
Value Set of codes that specify 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 pro |
| DIAGNOSTIC SERVICE SECTION ID (2.1 - 1.0.0) |
Concepts which specify a section of a diagnostic service where the observation may be performed. |
| DIAGNOSTIC SERVICE SECTION ID (2.2 - 1.1.0) |
Concepts which specify a section of a diagnostic service where the observation may be performed. |
| DIET TYPE (2.2 - 1.0.0) |
Value Set of codes that specify the type of diet. |
| DRG Diagnosis Determination Status (2.6 - 1.0.0) |
Value Set of codes that specify the status of a diagnosis for a diagnosis related group (DRG) determination. |
| DRG Grouping Status (2.6 - 1.0.0) |
Value Set of codes that specify the status of the use of the gender information for diagnosis related group (DRG) determination. |
| DRG Procedure Determination Status (2.6 - 1.0.0) |
Value Set of codes that specify the status of the use of this particular procedure for the diagnosis related group (DRG) determination. |
| DRG Procedure Relevance (2.6 - 1.0.0) |
Value Set of codes that specify the relevance of this particular procedure for the diagnosis related group (DRG) determination. |
| DRG Status Financial Calculation (2.6 - 1.0.0) |
Value Set of codes that specify the status of the diagnosis related group (DRG) calculation regarding the financial aspects. |
| DRG transfer type (2.4 - 1.0.0) |
Value Set of codes 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. |
| Data Types (2.7 - 1.2.0) |
Value Set of codes specifying the data type. |
| Data Types (2.9.1 - 1.4.0) |
Value Set of codes specifying the data type. |
| Data types (2.4 - 1.0.0) |
Value Set of codes specifying the data type. |
| Data types (2.5 - 1.1.0) |
Value Set of codes specifying the data type. |
| Data types (2.5.1 - 1.3.0) |
Value Set of codes specifying the data type. |
| Date Format (2.6 - 1.0.0) |
Value Set of codes that specify the date format for a decontamination/sterilization instance. |
| Days of the Week (2.3 - 1.0.0) |
Value Set of codes that identify the day(s) of the week when a location may be scheduled for appointments. |
| Degree (2.3.1 - 1.0.0) |
Concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Degree (2.4 - 1.1.0) |
Concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Degree/License/Certificate (2.7 - 1.0.0) |
Concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Degree/License/Certificate (2.8 - 1.1.0) |
Concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Degree/license/certificate (2.5 - 1.2.0) |
Concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Denial or Rejection Code (2.4 - 1.0.0) |
Value Set of codes that specify the OCE status of the line item. |
| Device Data State (2.6 - 1.0.0) |
Value Set of codes that specify the state of the data as provided from a device. |
| Device Status (2.6 - 1.0.0) |
Value Set of codes that specify the state of a device. |
| Diagnosis Classification (2.3 - 1.0.0) |
Value Set of codes that classify whether a patient visit can be related to a diagnosis. |
| Diagnosis Type (2.3 - 1.0.0) |
Concepts specifying a type of diagnosis being sent in HL7 Version 2.x messages. |
| Diagnosis priority (2.3.1 - 1.0.0) |
Concepts 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. Used in the DG1 segment in Version 2 messaging. |
| Diagnostic Service Section ID (2.3 - 1.2.0) |
Concepts which specify a section of a diagnostic service where the observation may be performed. |
| Diagnostic Service Section ID (2.9.1 - 1.4.0) |
Concepts which specify a section of a diagnostic service where the observation may be performed. |
| Diagnostic service section ID (2.4 - 1.3.0) |
Concepts which specify a section of a diagnostic service where the observation may be performed. |
| Disabled Person (2.3 - 1.0.0) |
Value Set of codes 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. |
| Discharge disposition (2.3.1 - 1.0.0) |
Value Set of codes that specify 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 |
| Dispense Method (2.3 - 1.0.0) |
Value Set of codes that specify the method by which treatment is dispensed. |
| Dispense Type (2.5 - 1.0.0) |
Value Set of codes that specify the type of dispensing event that occurred. |
| Document Availability Status (2.3 - 1.0.0) |
Value Set of codes that define whether a patient document is appropriate or available for use in patient care. |
| Document Completion Status (2.3 - 1.0.0) |
Value Set of codes that record the state of a document in a workflow. |
| Document Confidentiality Status (2.3 - 1.0.0) |
Value Set of codes 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. |
| Document Storage Status (2.3 - 1.0.0) |
Value Set of codes that describe the availability of a document in relation to the type of storage. |
| Document availability status (2.3.1 - 1.1.0) |
Value Set of codes that define whether a patient document is appropriate or available for use in patient care. |
| Document confidentiality status (2.3.1 - 2.0.0) |
Value Set of codes 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. |
| Duration Categories (2.3 - 1.0.0) |
Value Set of codes that classify an observation definition as intended to measure a patient’s state at a point in time. |
| Duration categories (2.4 - 1.1.0) |
Value Set of codes that classify an observation definition as intended to measure a patient’s state at a point in time. |
| ELIGIBILITY SOURCE (2.2 - 1.0.0) |
Value Set of codes that specify the source of information about the insured’s eligibility for benefits. |
| ETHNIC GROUP (2.1 - 1.0.0) |
Concepts specifying the ethnicity of a patient. |
| EVENT REASON (2.1 - 1.0.0) |
Value Set of codes that specify the reason for an event. |
| EVENT REASON (2.2 - 1.1.0) |
Value Set of codes that specify the reason for an event. |
| Employment Status (2.5 - 2.0.0) |
Value Set of codes that specify the guarantor’s employment status. |
| Employment status (2.4 - 1.0.0) |
Value Set of codes that specify the guarantor’s employment status. |
| Encoding (2.3 - 1.0.0) |
Concept identifying the type of IETF encoding used to represent successive octets of binary data as displayable ASCII characters. |
| Equipment State (2.8 - 1.1.0) |
Value Set of codes that identify the status the equipment was in at the time the transaction was initiated. |
| Equipment State (2.9 - 1.2.0) |
Value Set of codes that identify the status the equipment was in at the time the transaction was initiated. |
| Equipment State Indicator Type Code (2.9 - 1.0.0) |
Value Set of codes that specify the type of measurement of the state of an automated laboratory instrument. |
| Equipment state (2.4 - 1.0.0) |
Value Set of codes that identify the status the equipment was in at the time the transaction was initiated. |
| Error Severity (2.5 - 1.0.0) |
Concepts documenting the severity of an application error as reported during acknowledgment of messages. |
| Error Severity (2.6 - 1.1.0) |
Concepts documenting the severity of an application error as reported during acknowledgment of messages. |
| Escort Required (2.3 - 1.0.0) |
Value Set of codes indicating whether a patient must be accompanied while travelling to a diagnostic service department. |
| Event (2.1 - 1.0.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.2 - 1.1.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.3 - 1.2.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.3.1 - 1.3.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.4 - 1.4.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.5 - 1.5.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.5.1 - 1.6.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.6 - 1.7.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.7 - 1.8.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.8 - 1.9.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.8.2 - 1.10.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event (2.9 - 1.11.0) |
Concepts specifying the trigger event for Version 2.x interface messages. |
| Event Consequence (2.3 - 1.0.0) |
Value Set of codes that describe the impact of an event on a patient. |
| Event Expected (2.3 - 1.0.0) |
Value Set of codes that communicate whether an event has been judged to be expected or unexpected. |
| Event Qualification (2.3 - 1.0.0) |
Value Set of codes that qualify an event related to a product experience. |
| Event Related Period (2.5 - 1.0.0) |
Value Set of codes that specify a common (periodical) activity of daily living. |
| Event Seriousness (2.3 - 1.0.0) |
Value Set of codes that a sender to designate an event as serious or significant. |
| Event Type (2.4 - 1.0.0) |
Value Set of codes specifying the type of event of the message. |
| Event reason (2.5 - 1.2.0) |
Value Set of codes that specify the reason for an event. |
| Exclusive Test (2.8 - 1.0.0) |
Concepts 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. |
| Expanded Yes/no Indicator (2.5 - 1.0.0) |
Value Set of codes that 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”. |
| Extended Priority Codes (2.5 - 1.0.0) |
Concepts describing the urgency of a request carried in an order. Used in Version 2 messaging in timing/quantity; in older versions of the Standard was used in the TQ datatype, but in later versions it is used in the TQ1 segment (which replaced the TQ datatype which has been withdrawn). Many of the codes are widely recognized values used in healthcare settings in the english-speaking world. |
| FILE-LEVEL EVENT CODE (2.2 - 1.0.0) |
Concepts specifying file-level events for master files. Used in HL7 Version 2 messaging in the MFI segment. |
| Facility Type (2.3 - 1.0.0) |
Value Set of codes that specify the type of facility. |
| Filler Status Codes (2.3 - 1.0.0) |
Value Set of codes that describe an appointment status from the perspective of the entity assigned to fulfill the appointment. |
| Filler status codes (2.5 - 1.1.0) |
Value Set of codes that describe an appointment status from the perspective of the entity assigned to fulfill the appointment. |
| Formulary Status (2.5 - 1.0.0) |
Value Set of codes that specify whether or not the pharmaceutical substance is part of the local formulary. |
| Gender Harmony Concepts (2.9.1 - 1.0.0) |
tbd |
| Gestation category code (2.4 - 1.0.0) |
Value Set of codes specifying the status of the birth in relation to the gestation |
| Grouper Status (2.6 - 1.0.0) |
Value Set of codes that specify the status of a grouper in general. |
| Health Care Provider Area of Specialization (2.4 - 1.0.0) |
Value Set of codes that specify 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 practic |
| Health Care Provider Classification (2.4 - 1.0.0) |
Value Set of codes that specify the more specific service or occupation within the healthcare provider type of the practitioner at a specific organization unit. |
| Health Care Provider Type Code (2.4 - 1.0.0) |
Value Set of codes that specify the major grouping of the service or occupation of a practitioner at a specific organization unit. |
| Identifier Type (2.3 - 1.0.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identifier Type (2.7 - 1.5.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identifier Type (2.9.1 - 1.9.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identifier type (2.3.1 - 1.1.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identifier type (2.4 - 1.2.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identifier type (2.5 - 1.3.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identifier type (2.6 - 1.4.0) |
Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards. |
| Identity Reliability Code (2.4 - 1.0.0) |
Value Set of codes that specify the reliability of patient/person identifying data transmitted via a transaction. |
| Identity may be Divulged (2.3 - 1.0.0) |
Value Set of codes that define whether the primary observer has given permission for their identification information to be provided to a product manufacturer. |
| Immunization registry status (2.4 - 1.0.0) |
Immunization registry status codes of a patient. Used in Version 2 messaging in the PD1 segment. |
| Inactive Reason Code (2.5 - 1.0.0) |
Value Set of codes that specify the reason the staff member is inactive. |
| Incident type code (2.4 - 1.0.0) |
Value Set of codes specifying a classification of the incident type. |
| Indirect Exposure Mechanism (2.3 - 1.0.0) |
Value Set of codes that identify the mechanism of product transmission when the product has not been directly applied to the patient. |
| Inform Person Code (2.5 - 1.0.0) |
Value Set of codes that specify who (if anyone) shouldor should not be informed of an error. |
| Institution Relationship Type (2.5 - 1.0.0) |
Value Set of codes that specify the relationship the staff person has with the institution for whom he/she provides services. |
| Intended Procedure Type (2.8 - 1.0.0) |
Value Set of codes specifying the type of intended procedure. |
| Interpretation Codes (2.7 - 1.2.0) |
A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. |
| Interpretation Codes (2.8.2 - 1.3.0) |
A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. |
| Invoice Control Code (2.6 - 1.0.0) |
Value Set of codes that specify what invoice action is being performed by this message. |
| Invoice Processing Results Status (2.6 - 1.0.0) |
Value Set of codes used to specify the processing status for an Invoice Processing Result. |
| Invoice Reason Codes (2.6 - 1.0.0) |
Value Set of codes that specify the reason for an invoice. |
| Invoice Type (2.6 - 1.0.0) |
Value Set of codes that specify the type of invoice. |
| Item Status (2.6 - 1.0.0) |
Value Set of codes that specify the status (useful for reporting and item usage purposes) that applies to an item. |
| Item Status Codes (2.6 - 1.0.0) |
Value Set of codes that specify the state of an inventory item within the context of an inventory location. |
| Item Type (2.6 - 1.0.0) |
Value Set of codes that specify a classification of material items into like groups as defined and utilized within an operating room setting for charting procedures. |
| Job status (2.4 - 1.0.0) |
Value Set of codes that specify a next of kin/associated party’s job status. |
| Jurisdictional Breadth (2.5 - 1.0.0) |
Value Set of codes that specify the breadth/extent of the jurisdiction where the qualification is valid. |
| Kind of Quantity (2.3 - 1.0.0) |
Value Set of codes 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 |
| Labor Calculation Type (2.6 - 1.0.0) |
Value Set of codes that specify the method used to calculate employee labor and measure employee productivity. |
| Language ability (2.4 - 1.0.0) |
Value Set of codes that specify codes that indicate the ability that a Staff Member possesses with respect to the language. |
| Language proficiency (2.4 - 1.0.0) |
Value Set of codes which specify the level of knowledge a person possesses with respect to a language ability identified. |
| Level of Care (2.3 - 1.0.0) |
Value Set of codes that identify the level of care a patient may be afforded when assigned to this location definition. |
| Limitation Type Codes (2.8.2 - 1.0.0) |
Value Set of codes specifying a type of limitation. |
| Living Arrangements (2.3 - 1.0.0) |
Concepts characterizing the situation that patient-associated parties live in at their residential address. |
| Living Dependency (2.5 - 1.1.0) |
Value Set of codes identifying specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient’s healthcare needs. |
| Living Will (2.3 - 1.0.0) |
Value Set of codes that specify 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 |
| Living arrangement (2.3.1 - 1.1.0) |
Concepts characterizing the situation that patient-associated parties live in at their residential address. |
| Living dependency (2.4 - 1.0.0) |
Value Set of codes identifying specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient’s healthcare needs. |
| Load Status (2.6 - 1.0.0) |
Value Set of codes that specify the status of the information provided in a device sterilization or decontamination cycle. |
| Local/remote control state (2.4 - 1.0.0) |
Value Set of codes 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) |
| Location Characteristic ID (2.3 - 1.0.0) |
Value Set of codes that specify an identifier code to show which characteristic is being communicated with the segment. |
| Location Equipment (2.3 - 1.0.0) |
Value Set of codes that identify the equipment available in a location definition identified as a room or bed. |
| Location Relationship ID (2.3 - 1.0.0) |
Value Set of codes that specify an identifier code to show which relationship is being communicated with the segment. |
| Location service code (2.4 - 1.0.0) |
Value Set of codes specifying the types of services provided by the location. |
| Lot Control (2.6 - 1.0.0) |
Value Set of codes that specify whether the sterilization load for a device is built in the sub-sterile area adjacent to an Operating Room or the Central Processing Department. |
| MAIL CLAIM PARTY (2.2 - 1.0.0) |
Value Set of codes that specify a party to which a claim should be mailed when claims are sent by mail. |
| MASTER FILE IDENTIFIER CODE (2.2 - 1.0.0) |
Concepts which are represented by codes identifying HL7Versions 2.x Master Files. |
| MESSAGE TYPE (2.1 - 1.0.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| MESSAGE TYPE (2.2 - 1.1.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| MFN Recode-Level Error Return (2.2 - 1.0.0) |
Concepts which code status values for requested master file record update operations. |
| MIME Types (2.6 - 1.0.0) |
Value Set of codes specifying the general type of data. |
| MIME base64 encoding Characters (2.3 - 1.0.0) |
Value Set of codes that are used for base64 MIME encoding. Base64 is defined as follows (adapted from MIME Internet standard RFC 1521). |
| Main type of referenced Data (2.3 - 1.1.0) |
Concepts declaring the general type of media data that is encoded. |
| Manufacturers of Vaccines (2.3 - 1.0.0) |
HL7-published value Set of codes that specify the organization that manufactures a vaccine. Superceded by 2.16.840.1.114222.4.11.826, published by the US Centers for Disease Control and Prevention (CDC). |
| Manufacturers of Vaccines (code=MVX) (2.5 - 1.2.0) |
Value Set of codes that specify 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 acce |
| Manufacturers of Vaccines (code=MVX) (2.6 - 1.3.0) |
Value Set of codes that specify 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 acce |
| Manufacturers of vaccines (code=MVX) (2.3.1 - 1.1.0) |
HL7-published value Set of codes that specify the organization that manufactures a vaccine. Superceded by 2.16.840.1.114222.4.11.826, published by the US Centers for Disease Control and Prevention (CDC). |
| Marital Status (2.1 - 1.0.0) |
Value Set of codes that specify a person’s marital (civil/legal) status. |
| Marital Status (2.4 - 1.1.0) |
Value Set of codes that specify a person’s marital (civil/legal) status. |
| Marketing Basis (2.3 - 1.0.0) |
Value Set of codes that specify the basis for marketing approval. |
| Master File Identifier Code (2.3 - 1.1.0) |
Concepts which are represented by codes identifying HL7Versions 2.x Master Files. |
| Master file identifier code (2.3.1 - 1.2.0) |
Concepts which are represented by codes identifying HL7Versions 2.x Master Files. |
| Master file identifier code (2.4 - 1.3.0) |
Concepts which are represented by codes identifying HL7Versions 2.x Master Files. |
| Master file identifier code (2.5 - 1.4.0) |
Concepts which are represented by codes identifying HL7Versions 2.x Master Files. |
| Match reason (2.4 - 1.0.0) |
Value Set of codes 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 |
| Medical Role Executing Physician (2.6 - 1.0.0) |
Value Set of codes specifying the role of the physician (“self-employed” or “employed”). |
| Message Error Condition Codes (2.7 - 1.1.0) |
HL7 (communications) error codes, as transmitted in a message acknowledgement. |
| Message Error Condition Codes (2.9 - 1.2.0) |
HL7 (communications) error codes, as transmitted in a message acknowledgement. |
| Message Structure (2.3.1 - 1.0.0) |
HL7 abstract message structure codes. |
| Message Structure (2.4 - 1.1.0) |
HL7 abstract message structure codes. |
| Message Structure (2.5 - 1.2.0) |
HL7 abstract message structure codes. |
| Message Structure (2.5.1 - 1.6.0) |
HL7 abstract message structure codes. |
| Message Structure (2.6 - 1.3.0) |
HL7 abstract message structure codes. |
| Message Structure (2.7 - 1.4.0) |
HL7 abstract message structure codes. |
| Message Structure (2.7.1 - 1.7.0) |
HL7 abstract message structure codes. |
| Message Structure (2.8 - 1.5.0) |
HL7 abstract message structure codes. |
| Message Structure (2.8.2 - 1.8.0) |
HL7 abstract message structure codes. |
| Message Structure (2.9.1 - 1.9.0) |
HL7 abstract message structure codes. |
| Message Type (2.3 - 1.2.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message Type (2.7 - 1.7.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message Type (2.7.1 - 1.10.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message Type (2.8 - 1.8.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message Type (2.9.1 - 1.11.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message error condition codes (2.3.1 - 1.0.0) |
HL7 (communications) error codes, as transmitted in a message acknowledgement. |
| Message type (2.3.1 - 1.3.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message type (2.4 - 1.4.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message type (2.5 - 1.5.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message type (2.5.1 - 1.9.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message type (2.6 - 1.6.0) |
Concepts which specify message types for HL7 Version 2.x messaging. |
| Message waiting priority (2.6 - 1.0.0) |
Value Set of codes that 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 |
| Military rank/grade (2.3.1 - 1.0.0) |
Value Set of codes that specify 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 t |
| Military rank/grade (2.4 - 2.0.0) |
Value Set of codes that specify 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 t |
| Military service (2.3.1 - 1.0.0) |
Value Set of codes that specify the military branch. This field is defined by CMS or other regulatory agencies. |
| Military service (2.4 - 1.1.0) |
Value Set of codes that specify the military branch. This field is defined by CMS or other regulatory agencies. |
| Military status (2.3.1 - 1.0.0) |
Value Set of codes that specify the military status of the patient. This field is defined by CMS or other regulatory agencies. |
| Modality (2.3 - 1.0.0) |
Value Set of codes 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. |
| Mode of arrival code (2.4 - 1.0.0) |
Value Set of codes specifying how the patient was brought to the healthcare facility. |
| Modifier Edit Code (2.4 - 1.0.0) |
Value Set of codes that specify the edits of the modifiers for each line or HCPCS/CPT. |
| Modify Indicator (2.4 - 1.0.0) |
Value Set of codes identifying whether the subscription is new or is being modified. |
| Mood Codes (2.6 - 1.0.0) |
Value Set of codes that specify the functional state of an order. |
| NATURE OF ABNORMAL TESTING (2.1 - 1.0.0) |
Value Set of codes that specify the nature of an abnormal test. |
| NATURE OF TEST/OBSERVATION (2.2 - 1.0.0) |
Concepts specifying 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. |
| Name Assembly Order (2.4 - 1.0.0) |
Value Set of codes specifying the preferred display order of the components of this person name. |
| Name Representation (2.3 - 1.0.0) |
Value Set of codes that provide an indication of the kind of representation provided by a name or address, but does not necessarily specify the character sets used for the data. It is used to provides hints for a receiver, so it can make choic |
| Name Type (2.7 - 1.0.0) |
Concepts for types of names for persons. |
| Name Type (2.8 - 1.1.0) |
Concepts for types of names for persons. |
| Name type (2.4 - 1.2.0) |
Concepts for types of names for persons. |
| Name type (2.6 - 1.3.0) |
Concepts for types of names for persons. |
| Nature of Abnormal Testing (2.5 - 1.1.0) |
Value Set of codes that specify the nature of an abnormal test. |
| Nature of Challenge (2.3 - 1.0.0) |
Value Set of codes that further describe an observation definition that is characterized as a challenge observation. |
| Network Source Type (2.3 - 1.0.0) |
Value Set of codes that indicate (in certain systems) whether a lower level source identifier is an initiate or accept type. |
| Newborn Code (2.4 - 1.0.0) |
Value Set of codes specifying whether the baby was born in or out of the facility. |
| Non-Subject Consenter Reason (2.5 - 1.0.0) |
Value Set of codes that specify a reason consent was granted by a person other than the subject of the consent. |
| Notify Clergy Code (2.5 - 1.0.0) |
Value Set of codes that specify whether the clergy should be notified. |
| OBSERVATION RESULT STATUS (2.1 - 1.0.0) |
Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. |
| OBSERVATION RESULT STATUS CODES INTERPRETATION (2.2 - 1.1.0) |
Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. |
| OCE Edit Code (2.4 - 1.0.0) |
Value Set of codes that specify the edits that result from processing the HCPCS/CPT procedures for a record after evaluating all the codes, revenue codes, and modifiers. |
| ORDER CONTROL (2.1 - 1.0.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| ORDER CONTROL (2.2 - 1.1.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| Observation Result Handling (2.5 - 1.0.0) |
Concepts regarding the handling of a result. |
| Observation Result Handling (2.7.1 - 1.1.0) |
Concepts regarding the handling of a result. |
| Observation Result Status Codes Interpretation (2.3 - 1.2.0) |
Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. |
| Observation Sub-Type (2.8.2 - 1.0.0) |
Value Set of codes specifying an observation sub-type. |
| Observation Sub-Type (2.9 - 1.1.0) |
Value Set of codes specifying an observation sub-type. |
| Observation Type (2.8.2 - 1.0.0) |
Value Set of codes that specify types of observations to enable systems to distinguish between observations sent along with an order, versus observations sent as the result to an order. |
| Observation result status codes interpretation (2.3.1 - 1.3.0) |
Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. |
| Observation result status codes interpretation (2.6 - 1.4.0) |
Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. |
| Occurrence code (2.3.1 - 1.0.0) |
Concepts drawn from the National Uniform Billing Committee (NUBC) code for the event or occurrence relating to a bill that may affect payer processing. Used in Version 2 messaging in the Occurrence Code and Date (OCD) value. |
| Occurrence span (2.3.1 - 1.0.0) |
Concepts drawn from the National Uniform Billing Committee (NUBC) code that identifies an event that relates to the payment of a claim. Used in Version 2 messaging in the Occurrence Span Code and Date (OSP) value. |
| Online Verification Result (2.9 - 1.0.0) |
Code values used to indicate the result of an online verification of insurance data. |
| Online Verification Result Error Code (2.9 - 1.0.0) | |
| Order Control Code (2.3 - 1.2.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| Order Control Code Reason (2.9 - 1.0.0) |
Value Set of codes that describe reasons for the chosen order control codes. |
| Order Control Codes (2.8 - 1.6.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| Order Status (2.1 - 1.0.0) |
Value Set of codes that specify 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 as |
| Order Status (2.2 - 1.1.0) |
Value Set of codes that specify 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 as |
| Order Status (2.3 - 1.2.0) |
Value Set of codes that specify 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 as |
| Order Status Modifier (2.9 - 1.0.0) |
Value Set of codes that further define an identified status. |
| Order Type (2.5 - 1.0.0) |
Value Set of codes that specify whether the order is to be executed in an inpatient setting or an outpatient setting. |
| Order control codes (2.3.1 - 1.3.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| Order control codes (2.5 - 1.4.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| Order control codes (2.6 - 1.5.0) |
Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service. |
| Organ Donor (2.3 - 1.0.0) |
Value Set of codes that specify 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. |
| Organ donor (2.3.1 - 1.1.0) |
Value Set of codes that specify 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. |
| Organ donor code (2.4 - 1.2.0) |
Value Set of codes that specify 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. |
| Organizational Name Type (2.3 - 1.0.0) |
Concepts used to specify the type of name for an organization i.e., legal name, display name. |
| Outlier Type (2.3 - 1.0.0) |
Value Set of codes that identify a Diagnostic Resource Group Payor. US Realm. No suggested values. |
| Overall Claim Disposition Code (2.4 - 1.0.0) |
Value Set of codes specifying the final status of the claim. |
| Override (2.3 - 1.0.0) |
Value Set of codes that define whether a Charge Description Master description may be overridden or if it must be overridden. |
| Override Type (2.5 - 1.0.0) |
Value Set of codes that specify what type of override can be used to override the specific error identified. |
| PCA Type (2.8 - 1.0.0) |
Value Set of codes specifying a type of PCA. |
| PENALTY TYPE (2.2 - 1.0.0) |
Value Set of codes that specify whether the amount is currency or a percentage. |
| POLICY TYPE (2.2 - 1.0.0) |
Value Set of codes that specify the policy type. |
| PRECERTIFICATION PATIENT TYPE (2.2 - 1.0.0) |
Value Set of codes that specify the category or type of patient for which this certification is requested. |
| PRIORITY (COMPONENT 6 QTY/TIMING[735]) (2.1 - 1.0.0) |
Value Set of codes that specify the allowed priorities for obtaining the specimen. |
| PRIORITY (COMPONENT 6 QTY/TIMING[735]) (2.2 - 1.1.0) |
Value Set of codes that specify the allowed priorities for obtaining the specimen. |
| PROCEDURE PRACTITIONER TYPE (2.2 - 1.0.0) |
Value Set of codes of concepts which specify the different types of practitioners associated with this procedure. This set of codes is known to be incomplete. |
| PROCESSING ID (2.1 - 1.0.0) |
Value Set of codes that specify whether the message is part of a production, training or debugging system. |
| PROCESSING PRIORITY (2.2 - 1.0.0) |
Value Set of codes that specify one or more available priorities for performing the observation or test. |
| Package (2.6 - 1.0.0) |
Value Set of codes 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. |
| Packaging Status Code (2.4 - 1.0.0) |
Value Set of codes that specify the packaging status of the service. |
| Participant Organization Unit Type (2.4 - 1.0.0) |
Value Set of codes 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 no |
| Participation (2.7 - 1.0.0) |
Concepts 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.) |
| Participation (2.8 - 1.1.0) |
Concepts 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.) |
| Participation (2.8.2 - 1.2.0) |
Concepts 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.) |
| Participation (2.9 - 1.3.0) |
Concepts 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.) |
| Patient Class (2.1 - 1.0.0) |
Concepts used by systems to categorize patients by sites. |
| Patient Class (2.2 - 1.1.0) |
Concepts used by systems to categorize patients by sites. |
| Patient Class (2.4 - 1.2.0) |
Concepts used by systems to categorize patients by sites. |
| Patient Location Type (2.3 - 1.0.0) |
Value Set of codes that identify the kind of location described in the location definition. |
| Patient Outcome (2.3 - 1.0.0) |
Value Set of codes that describe the overall state of a patient as a result of patient care. |
| Patient Results Release Categorization Scheme (2.7 - 1.0.0) |
Value Set of codes specifying the scheme for the patient results release categorization. |
| Patient condition code (2.4 - 1.0.0) |
Value Set of codes 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. |
| Patient’s relationship to insured (2.3.1 - 1.0.0) |
Value Set of codes that specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies. |
| Payee Relationship to Invoice (2.6 - 1.0.0) |
Value Set of codes used to specify the relationship to the invoice for Person Payee Types. |
| Payee Type (2.6 - 1.0.0) |
Value Set of codes that specify the type of payee (e.g., organization, person). |
| Payment Adjustment Code (2.4 - 1.0.0) |
Value Set of codes that specify any payment adjustment due to drugs or medical devices. |
| Payment Method Code (2.6 - 1.0.0) |
Value Set of codes used to specify the method for the movement of payment. |
| Person location type (2.4 - 1.0.0) |
Value Set of codes that specify the categorization of the person’s location. |
| Pharmacy Order Types (2.5 - 1.0.0) |
Value Set of codes that specify the general category of pharmacy order which may be used to determine the processing path the order will take. |
| Phlebotomy Issue (2.8 - 1.0.0) |
Value Set of codes specifying a phlebotomy issue. |
| Phlebotomy Status (2.8 - 1.0.0) |
Value Set of codes specifying the status of a phlebotomy. |
| Practitioner ID number type (2.3 - 1.0.0) |
Value Set of codes that specify the type of number used for the practitioner identification. |
| Practitioner ID number type (2.5 - 1.1.0) |
Value Set of codes that specify the type of number used for the practitioner identification. |
| Practitioner Organization Unit Type (2.4 - 1.0.0) |
Value Set of codes that specify the classification of the organization unit. |
| Practitioner Organization Unit Type (2.5 - 1.1.0) |
Value Set of codes that specify the classification of the organization unit. |
| Precaution code (2.4 - 1.0.0) |
Value Set of codes specifying non-clincal precautions that need to be taken with the patient. |
| Precision (2.5 - 1.0.0) |
Value Set of codes used to specify the degree of precision of a time stamp. |
| Preferred Method Of Contrct (2.2 - 1.0.0) |
Value Set of codes that specify which of a group of multiple phone numbers is the preferred method of contact for this person. |
| Preferred Specimen/Attribute Status (2.8 - 1.0.0) |
Concepts that indicate whether a Specimen/Attribute is Preferred or Alternate for collection of a particular specimen. |
| Present On Admission (POA) Indicator (2.6 - 1.0.0) |
Value Set of codes specifying the present on admission indicator for this particular diagnosis. |
| Price Type (2.3 - 1.0.0) |
Value Set of codes that identify the intent for the dollar amount on a pricing transaction. |
| Primary Observer's Qualification (2.3 - 1.0.0) |
Value Set of codes that provide a general description of the kind of health care professional who provided the primary observation. |
| Primary key value type (2.3.1 - 1.0.0) |
Value Set of codes that specify the type for the master file record identifier. |
| Primary key value type (2.6 - 1.1.0) |
Value Set of codes that specify the type for the master file record identifier. |
| Privacy Level (2.3 - 1.0.0) |
Value Set of codes that identify the level of privacy a patient will be afforded when assigned to this location definition. |
| Procedure DRG type (2.4 - 1.0.0) |
Value Set of codes that specify a procedure’s priority ranking relative to its DRG. |
| Procedure Functional Type (2.3 - 1.0.0) |
Value Set of codes that classify a procedure. |
| Procedure Practitioner Identifier Code Type (2.3 - 1.1.0) |
Value Set of codes of concepts which specify the different types of practitioners associated with this procedure. This set of codes is known to be incomplete. |
| Procedure priority (2.4 - 1.0.0) |
Value Set of codes specifying a number that identifies the significance or priority of the procedure code. |
| Process Interruption Reason (2.8 - 1.0.0) |
Value Set of codes specifying the reason for a process interruption. |
| Processing Consideration Codes (2.6 - 1.0.0) |
Value Set of codes that specify special processing requested of Payer for this Product/Service Line Item (e.g., hold until paper supporting documentation is received by Payer). |
| Processing Mode (2.3 - 1.0.0) |
Concepts that indicate an archival process or an initial load process. |
| Processing Type (2.4 - 1.0.0) |
Value Set of codes identifying the processing type that applies to the test code. If this attribute is omitted, then regular production is the default. |
| Processing mode (2.3.1 - 1.1.0) |
Concepts that indicate an archival process or an initial load process. |
| Product Source (2.3 - 1.0.0) |
Value Set of codes that describe the evaluation state of a product identified in an incident. |
| Product/Service Status (2.6 - 1.0.0) |
Value Set of codes that specify the processing status for the Product/Service Code. |
| Product/Services Clarification Codes (2.6 - 1.0.0) |
Value Set of codes that specify the Product/Service Code. |
| Production class Code (2.4 - 1.0.0) |
Value Set of codes specifying the code and/or text indicating the primary use for which the living subject was bred or grown. |
| Protection Code (2.6 - 1.0.0) |
Value Set of codes that specify that an address needs to be treated with special care or sensitivity. |
| Provider Adjustment Reason Code (2.6 - 1.0.0) |
Value Set of codes used to specify the reason for this adjustment. |
| Provider Role (2.4 - 1.0.0) |
Value Set of codes that specify the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). |
| Provider Role (2.6 - 1.1.0) |
Value Set of codes that specify the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). |
| Provider Role (2.7 - 1.2.0) |
Value Set of codes that specify the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). |
| Provider billing (2.2 - 1.0.0) |
Value Set of codes that specify how provider services are billed. |
| Purge Status (2.3 - 1.0.0) |
Value Set of codes that define the state of a visit relative to its place in a purge workflow. |
| QUANTITY LIMITED REQUEST (2.1 - 1.0.0) |
Concepts which specify 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. |
| QUANTITY LIMITED REQUEST (2.2 - 1.1.0) |
Concepts which specify 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. |
| QUERY FORMAT CODE (2.1 - 1.0.0) |
Value Set of codes which specify which of several types of formats for data to be returned in response to a query. |
| QUERY FORMAT CODE (2.2 - 1.1.0) |
Value Set of codes which specify which of several types of formats for data to be returned in response to a query. |
| QUERY PRIORITY (2.1 - 1.0.0) |
Concepts which specify a time frame in which a querry response is expected. |
| QUERY RESULTS LEVEL (2.1 - 1.0.0) |
Value Set of codes which are used to control level of detail in query results. |
| QUERY RESULTS LEVEL (2.2 - 1.1.0) |
Value Set of codes which are used to control level of detail in query results. |
| Quantity Method (2.3 - 1.0.0) |
Value Set of codes that specify the method by which the quantity distributed is measured. |
| Quantity limited request (2.4 - 1.2.0) |
Concepts which specify 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. |
| Query Response Status (2.3 - 1.0.0) |
Concepts defining precise response status concepts in support of HL7 Version 2 query messaging. |
| Query response status (2.3.1 - 1.1.0) |
Concepts defining precise response status concepts in support of HL7 Version 2 query messaging. |
| Query/Response Format Code (2.3 - 1.2.0) |
Value Set of codes which specify which of several types of formats for data to be returned in response to a query. |
| REPORT PRIORITY (2.1 - 1.0.0) |
Value Set of codes which specify the priority associated with a report or update run using a query. |
| REPORTIN PRIORITY (2.2 - 1.0.0) |
Value Set of codes that specify the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority. |
| RESPONSE FLAG (2.1 - 1.0.0) |
Value Set of codes allowing the placer (sending) application to determine the amount of information to be returned from the filler. |
| RESPONSE FLAG (2.2 - 1.1.0) |
Value Set of codes allowing the placer (sending) application to determine the amount of information to be returned from the filler. |
| RESULT STATUS - OBR (2.1 - 1.0.0) |
Concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| RESULT STATUS - OBR (2.2 - 1.1.0) |
Concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| ROUTE (2.1 - 1.0.0) |
Value Set of codes that are used to indicate a means of administrating a medication dose. |
| ROUTE OF ADMINISTRATION (2.2 - 1.0.0) |
Value Set of codes that specify the route of administration. |
| RX COMPONENT TYPE (2.2 - 1.0.0) |
Value Set of codes that specify the RX component type. |
| Reason for Study (2.9 - 1.0.0) |
Value Set of codes that provide additional information to the universal service identifier on why a test, study or review was ordered. |
| Record Level Event Code (2.2 - 1.0.0) |
Concepts specifying an action for a master file record. Used in HL7 V2.x messaging in the MFE segment. |
| Recreational drug use code (2.4 - 1.0.0) |
Value Set of codes specifying what recreational drugs the patient uses. |
| Referral Category (2.3 - 1.0.0) |
Value Set of codes that describe the patient care setting where a referral should take place. |
| Referral Disposition (2.3 - 1.0.0) |
Value Set of codes that identify the expected response from the healthcare professional receiving a referral. |
| Referral Priority (2.3 - 1.0.0) |
Value Set of codes that designate the urgency of a referral. |
| Referral Reason (2.3 - 1.0.0) |
Value Set of codes that specify the reason for which the referral will take place. |
| Referral Status (2.3 - 1.0.0) |
Value Set of codes that define the state of a referral. |
| Referral Type (2.3 - 1.0.0) |
Value Set of codes that identify the general category of healthcare professional desired to satisfy a referral. |
| Reimbursement Action Code (2.4 - 1.0.0) |
Value Set of codes that specify the action to be taken during reimbursement calculations. |
| Reimbursement type code (2.4 - 1.0.0) |
Value Set of codes that specify the fee schedule reimbursement type applied to a line item. |
| Relatedness Assessment (2.3 - 1.0.0) |
Value Set of codes that provide an estimate of whether an issue with a product was the cause of an event. |
| Relational Conjunction (2.3 - 1.0.0) |
Value Set of codes used with relational operator values to group more than one segment field name. |
| Relational Operator (2.3 - 1.0.0) |
Value Set of codes that define the relationship between HL7 segment field names identified in a query construct. |
| Relationship (2.4 - 1.0.0) |
Concepts specifying an actual personal relationship that the next of kin/associated party has to a patient. Used in HL7 Version 2.x messaging in the NK1 segment. |
| Relationship Modifier (2.3 - 1.0.0) |
Value Set of codes that an observation definition to describe the subject of an observation in relation to a patient. |
| Relationship Type (2.9 - 1.0.0) |
Value Set of codes that specify the type of relationship that is established between the instances of Source Information and Target Information. |
| Relevant Clinicial Information (2.7.1 - 1.0.0) |
Value Set of codes that specify 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. |
| Religion (2.1 - 1.0.0) |
Value Set of codes that specify a person’s religion. |
| Religion (2.4 - 2.0.0) |
Value Set of codes that specify a person’s religion. |
| Religion (2.6 - 2.1.0) |
Value Set of codes that specify a person’s religion. |
| Remote Control Command (2.8 - 1.1.0) |
Value Set of codes that identify the comment the component is to initiate. |
| Remote control command (2.4 - 1.0.0) |
Value Set of codes that identify the comment the component is to initiate. |
| Reorder Theory Codes (2.6 - 1.0.0) |
Value Set of codes that specify the calculation method used to determine the resupply schedule. |
| Repeat pattern (2.4 - 1.0.0) |
Value Set of codes 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 i |
| Report Source (2.3 - 1.0.0) |
Value Set of codes that identify where a report sender learned about an event. |
| Report Timing (2.3 - 1.0.0) |
Value Set of codes that identify the time span of a report or the reason for a report sent to a regulatory agency. |
| Report Type Code (2.3 - 1.0.0) |
Value Set of codes that identify the kind of patient document. |
| Reported To (2.3 - 1.0.0) |
Value Set of codes that identify the type of entity to which the event has been reported. |
| Response Level (2.2 - 1.0.0) |
Concepts specifying application response levels defined for a given Master File Message at the MFE segment level, and used for MFN-Master File Notification message. Specifies additional detail (beyond MSH-15 - Accept Acknowledgment Type and MSH-16 - Application Acknowledgment Type) for application-level acknowledgment paradigms for Master Files transactions. |
| Response Modality (2.4 - 1.0.0) |
Value Set of codes identifying the timing and grouping of the response message(s). |
| Result Status (2.3 - 1.2.0) |
Concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| Result Status (2.9 - 1.3.0) |
Concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| Revenue code (2.4 - 1.0.0) |
Value Set of codes specifying a revenue code as specified in the National Uniform Billing Committee (NUBC) UB-04 manual, UB form locator 42, the service line revenue code. These are claim codes indicating the identifying number for the product or service provided. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. |
| Risk Codes (2.5 - 1.0.0) |
Value Set of codes that specify any known or suspected specimen hazards, e.g., exceptionally infectious agent or blood from a hepatitis patient. |
| Risk Management Incident Code (2.4 - 1.0.0) |
Value Set of codes specifying the incident that occurred during a patient’s stay. |
| Role Executing Physician (2.6 - 1.0.0) |
Value Set of codes specifying the account role of the physician, for example, only billing for the professional part, the technical part or both. |
| Room Type (2.2 - 1.0.0) |
Value Set of codes that specify the room type. |
| Root Cause (2.8 - 1.0.0) |
Value Set of codes specifying a root cause. |
| Route of Administration (2.3 - 1.1.0) |
Value Set of codes that specify the route of administration. |
| Route of Administration (2.8 - 1.3.0) |
Value Set of codes that specify the route of administration. |
| Route of administration (2.3.1 - 1.2.0) |
Value Set of codes that specify the route of administration. |
| SOURCE OF COMMENT (2.1 - 1.0.0) |
Concepts which are used to specify the source of a comment, as used in HL7 Version 2.x messaging in the NTE segment. |
| SOURCE OF COMMENT (2.2 - 1.1.0) |
Concepts which are used to specify the source of a comment, as used in HL7 Version 2.x messaging in the NTE segment. |
| SOURCE OF SPECIMEN (2.1 - 1.0.0) |
Value Set of codes which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in table 0487 Specimen Type and table |
| SOURCE OF SPECIMEN (2.2 - 2.0.0) |
Value Set of codes which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in table 0487 Specimen Type and table |
| STOCK LOCATION (2.1 - 1.0.0) |
Value Set of codes that specify a stock location. |
| SUBSTITUTION STATUS (2.2 - 1.0.0) |
Value Set of codes that specify the substitution status. |
| Security Check Scheme (2.7 - 1.0.0) |
Value Set of codes specifying the scheme for a security check. |
| Segment Action Code (2.3 - 1.0.0) |
Concepts specifying 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). |
| Segment Group (2.6 - 1.0.0) |
Value Set of codes that specify the optional segment groups which are to be included in a response. |
| Segment action code (2.6 - 1.1.0) |
Concepts specifying 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). |
| Sensitivity to Causative Agent Code (2.7 - 1.1.0) |
Value Set of codes specifying the reason the patient should not be exposed to a substance. |
| Sensitivity to Causative Agent code (2.4 - 1.0.0) |
Value Set of codes specifying the reason the patient should not be exposed to a substance. |
| Sequence Condition Code (2.5 - 1.0.0) |
Value Set of codes that specify the relationship between the start/end of the related service request(s) and the current service request. |
| Sequence condition (2.5 - 1.0.0) |
Value Set of codes that identify whether sequence conditions or a repeating cycle of orders is defined, as part of the Order Sequence Definition. |
| Sequence/Results Flag (2.5 - 1.0.0) |
Value Set of codes that specify the sequencing relationship between the current service request and a related service request(s) specified in the same information model structure. |
| Sequencing (2.4 - 1.0.0) |
Value Set of codes identifying how the field or parameter will be sorted and, if sorted, whether the sort will be case sensitive (the default) or not. |
| Service Request Relationship (2.5 - 1.0.0) |
Value Set of codes that specify an additional or alternate relationship between this service request and other service requests. |
| Severity of illness code (2.4 - 1.0.0) |
Value Set of codes specifying the severity ranking of a patient’s illness. |
| Sex (2.1 - 1.0.0) |
Concepts specifying a person’s sex. |
| Sexual Orientation (2.9.1 - 1.0.0) |
Concepts specifying a person’s sexual orientation. Used in HL7 Version 2.x messages in the GSP segment. |
| Shipment Status (2.7 - 1.0.0) |
Value Set of codes specifying the status of a shipment. |
| Side of body (2.6 - 1.0.0) |
Value Set of codes specifying the side of the body (“left” or “right”). |
| Signatory's Relationship to Subject (2.5 - 1.0.0) |
Value Set of codes that specify the relationship of the consenter to the subject. |
| Signature Code (2.5 - 1.0.0) |
Concepts that indicate how a patient/subscriber authorization signature is obtained and how it is being retained by a provider. |
| Special Handling Code (2.5 - 1.1.0) |
Concepts describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing. Used in Version 2 messaging in the SPM segment. |
| Special handling considerations (2.4 - 1.0.0) |
Concepts describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing. Used in Version 2 messaging in the SPM segment. |
| Specialty Type (2.3 - 1.0.0) |
Value Set of codes that identify the specialty of the care professional who is supported when using this location definition. |
| Specimen Appropriateness (2.5 - 1.0.0) |
Value Set of codes that specify the suitability of the specimen for the particular planned use as determined by the filler. |
| Specimen Child Role (2.5 - 1.0.0) |
Value Set of codes that specify for child specimens the relationship between this specimen and the parent specimen. |
| Specimen Collection Method (2.5 - 1.0.0) |
Concepts to document procedures or processes by which a specimen may be collected. This is one of two code systems that are used instead of table 0070 (code system xxxx) which conflated specimen types and specimen collection methods. Used in Version 2 messaging in the SPM segment. |
| Specimen Condition (2.5 - 1.0.0) |
Concepts of modes or states of being that describe the nature of a specimen. Used in Version 2 messaging in the SPM segment. |
| Specimen Condition (2.8 - 1.1.0) |
Concepts of modes or states of being that describe the nature of a specimen. Used in Version 2 messaging in the SPM segment. |
| Specimen Quality (2.5 - 1.0.0) |
Value Set of codes that specify the degree or grade of excellence of the specimen at receipt. |
| Specimen Reject Reason (2.5 - 1.0.0) |
Reasons a specimen may be rejected for a specified observation/result/analysis. Used in Version 2 messaging in the SPM segment. |
| Specimen Role (2.5 - 1.1.0) |
Value Set of codes that identify the role of a sample. |
| Specimen Role (2.9 - 1.2.0) |
Value Set of codes that identify the role of a sample. |
| Specimen Source Codes (2.3 - 3.0.0) |
Value Set of codes which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in table 0487 Specimen Type and table |
| Specimen Source Codes (2.5 - 4.0.0) |
Value Set of codes which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in table 0487 Specimen Type and table |
| Specimen Type (2.5 - 1.0.0) |
Concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system xxxx) which conflated specimen types and specimen collection methods. Used in Version 2 messaging in the SPM segment. |
| Specimen Type (2.7 - 2.0.0) |
Concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system xxxx) which conflated specimen types and specimen collection methods. Used in Version 2 messaging in the SPM segment. |
| Specimen Type (2.8.2 - 3.0.0) |
Concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system xxxx) which conflated specimen types and specimen collection methods. Used in Version 2 messaging in the SPM segment. |
| Specimen component (2.4 - 1.0.0) |
Value Set of codes that identify the specimen component, e.g., supernatant, sediment, etc. |
| Specimen role (2.4 - 1.0.0) |
Value Set of codes that identify the role of a sample. |
| Start of Evaluation (2.3 - 1.0.0) |
Value Set of codes that describes the status of product evaluation. |
| Status Admission (2.6 - 1.0.0) |
Value Set of codes that specify the admission status for the diagnosis related group (DRG) determination. |
| Status Patient (2.6 - 1.0.0) |
Value Set of codes that specify whether the length of stay is normal or respectively shorter or longer than normal. |
| Status Respiration Minutes (2.6 - 1.0.0) |
Value Set of codes that specify the status of the use of the respiration minutes information for diagnosis related group (DRG) determination. |
| Status Weight At Birth (2.6 - 1.0.0) |
Value Set of codes that specify the status of the use of the weight at birth for diagnosis related group (DRG) determination. |
| Sterilization Type (2.6 - 1.0.0) |
Value Set of codes specifying the type of sterilization used for sterilizing the inventory supply item in the ITM segment. |
| Student Status (2.3 - 1.0.0) |
Value Set of codes that designate whether a guarantor is a full or part time student. |
| Substance Status (2.4 - 1.0.0) |
Value Set of codes identifying the status of the inventoried item. The status indicates the current status of the substance. |
| Substance Type (2.4 - 1.0.0) |
Value Set of codes identifying the type of substance. |
| Substitution status (2.3.1 - 1.1.0) |
Value Set of codes that specify the substitution status. |
| Subtype of Referenced Data (2.3 - 1.0.0) |
A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream. |
| Subtype of Referenced Data (2.3.1 - 1.1.0) |
A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream. |
| Subtype of Referenced Data (2.4 - 1.2.0) |
A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream. |
| Supplemental Service Information Values (2.9 - 1.0.0) |
Value Set of codes that specify a kind of 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). |
| Supplier Type (2.9 - 1.0.0) |
Value Set of codes specifying the type of supplier that will distribute the supply items associated to a contract number. |
| Supply Risk Codes (2.6 - 1.0.0) |
Value Set of codes specifying any known or suspected hazard associated with this material item. |
| TQ Conjunction ID (2.4 - 1.0.0) |
Value Set of codes that specify that a second timing specification is to follow using the repeat delimiter. |
| TRANSPORTATION MODE (2.1 - 1.0.0) |
Value Set of codes that specify how (or whether) to transport a patient, when applicable, for an ordered service. |
| TRAY TYPE (2.2 - 1.0.0) |
Value Set of codes that specify the type of dietary tray. |
| Tax status (2.6 - 1.0.0) |
Value Set of codes used to specify the tax status of a provider. |
| Telecommunication Equipment Type (2.3 - 1.0.0) |
Concepts for specifying a type of telecommunication equipment. |
| Telecommunication Expiration Reason (2.6 - 1.0.0) |
Value Set of codes specifying the reason this contact number/email was marked as “ended”. |
| Telecommunication Use Code (2.3 - 1.0.0) |
Concepts for specifying a specific use of a telecommunication number. |
| Telecommunication equipment type (2.5 - 1.1.0) |
Concepts for specifying a type of telecommunication equipment. |
| Telecommunication equipment type (2.6 - 1.2.0) |
Concepts for specifying a type of telecommunication equipment. |
| Telecommunication use code (2.3.1 - 1.1.0) |
Concepts for specifying a specific use of a telecommunication number. |
| Telecommunication use code (2.6 - 1.2.0) |
Concepts for specifying a specific use of a telecommunication number. |
| Time Delay Post Challenge (2.3 - 1.0.0) |
Value Set of codes that classify an observation definition as being a component of a challenge test. |
| Time Selection Criteria Parameter Class Codes (2.3 - 1.0.0) |
Value Set of codes that describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling. |
| Time Selection Criteria Parameter Class Codes (2.4 - 1.1.0) |
Value Set of codes that describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling. |
| Tissue Type Code (2.4 - 1.0.0) |
Value Set of codes that specify the type of tissue removed from a patient during a procedure. |
| Transaction Type (2.3 - 1.0.0) |
Value Set of codes that specify a type of financial transaction. |
| Transaction Type (2.4 - 1.1.0) |
Value Set of codes that specify a type of financial transaction. |
| Transfusion Adverse Reaction (2.5 - 1.0.0) |
Value Set of codes that specify the type of adverse reaction that the recipient of the blood product experienced. |
| Transport Arranged (2.3 - 1.0.0) |
Value Set of codes defining whether patient transportation preparations are in place. |
| Treatment (2.4 - 1.0.0) |
Value Set of codes that identify the specimen treatment performed during lab processing. |
| Triage Code (2.4 - 1.0.0) |
Value Set of codes specifying a patient’s prioritization within the context of this abstract. |
| Type Of Data (2.2 - 1.0.0) |
Concepts declaring the general type of media data that is encoded. |
| Type of Bill Code (2.4 - 1.0.0) |
Value Set of codes specifying the specific type of bill with digit 1 showing type of facility, digit 2 showing bill classification and digit 3 showing frequency. |
| Type of referenced data (2.3.1 - 1.2.0) |
Concepts declaring the general type of media data that is encoded. |
| Type of referenced data (2.4 - 1.3.0) |
Concepts declaring the general type of media data that is encoded. |
| Universal ID Type (2.7 - 1.2.0) |
Types of UID (Universal Identifiers). |
| Universal ID Type (2.9 - 1.3.0) |
Types of UID (Universal Identifiers). |
| Universal ID type (2.3 - 1.0.0) |
Types of UID (Universal Identifiers). |
| Universal ID type (2.5 - 1.1.0) |
Types of UID (Universal Identifiers). |
| User Authentication Credential Type Code (2.6 - 1.0.0) |
Value Set of codes that specify a type of user authentication credential. |
| VERSION CONTROL TABLE (2.1 - 1.0.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| VERSION ID (2.2 - 1.1.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Vaccines Administered (2.3 - 1.0.0) |
HL7-published value Set of codes that specify the administered vaccines. Superceded by 2.16.840.1.114222.4.11.934, published by the US Centers for Disease Control and Prevention (CDC). |
| Vaccines administered (2.3.1 - 1.1.0) |
HL7-published value Set of codes that specify the administered vaccines. Superceded by 2.16.840.1.114222.4.11.934, published by the US Centers for Disease Control and Prevention (CDC). |
| Vaccines administered (2.4 - 1.2.0) |
HL7-published value Set of codes that specify the administered vaccines. Superceded by 2.16.840.1.114222.4.11.934, published by the US Centers for Disease Control and Prevention (CDC). |
| Vaccines administered (2.5 - 0.0.) |
Table of codes specifying 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 |
| Vaccines administered (2.6 - 0.0.) |
Value Set of codes that specify 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.1 |
| Version ID (2.3 - 1.2.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.3.1 - 1.3.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.4 - 1.4.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.5 - 1.5.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.5.1 - 1.9.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.6 - 1.6.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.7 - 1.7.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.7.1 - 1.10.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.8 - 1.8.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.9 - 1.11.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Version ID (2.9.1 - 1.12.0) |
Concepts which are used to identify an HL7 version in the Version 2.x family of published standards. |
| Visit Indicator (2.3 - 1.0.0) |
Value Set of codes that specify 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 i |
| Visit priority code (2.4 - 1.0.0) |
Value Set of codes that define a relative level of urgency applied to a patient visit. |
| Visit user code (2.4 - 1.0.0) |
Value Set of codes that specify 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. |
| WHEN TO CHARGE (2.1 - 1.0.0) |
Value Set of codes that specify codes for an event precipitating/triggering a charge activity. |
| WHIHC DATE/TIME STATUS QUALIFIER (2.2 - 1.0.0) |
Value Set of codes that specify the status type of objects selected in date range defined by QRF-2 and QRF-3. |
| What Subject Filter (2.1 - 1.0.0) |
Value Set of codes which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. |
| What Subject Filter (2.2 - 1.1.0) |
Value Set of codes which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. |
| What Subject Filter (2.3 - 1.2.0) |
Value Set of codes which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. |
| What subject filter (2.3.1 - 1.3.0) |
Value Set of codes which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. |
| What subject filter (2.4 - 1.4.0) |
Value Set of codes which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. |
| Which date/time qualifier (2.3.1 - 1.1.0) |
Value Set of codes that specify the type of date referred to in the other date fields in the QRF segment. |
| Y/N Indicator (2.2 - 1.0.0) |
Codes specifying either Yes or No used in fields containing binary answers generally user-specified. |
These define new code systems used by systems conforming to this implementation guide.
| ABNORMAL FLAGS (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify a categorical assessment of an observation value. Used in HL7 Version 2.x messaging in the OBX segment. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. |
| ABNORMAL FLAGS (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify a categorical assessment of an observation value. Used in HL7 Version 2.x messaging in the OBX segment. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. |
| ACCEPT/APPLICATION ACKNOWLEDGEMENT CONDITIONS (2.2 - 1.0.0) |
HL7-defined code system of concepts which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode. Used in HL7 Versions 2 messaging in the MSH segment. |
| ACKNOWLEDGMENT CODE (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying acknowledgment codes. For details of usage, see message processing rules in the published Standard. Used in HL7 Version 2.x messaging in the MSA segment. |
| ACKNOWLEDGMENT CODE (2.2 - 1.1.0) |
HL7-defined code system of concepts specifying acknowledgment codes. For details of usage, see message processing rules in the published Standard. Used in HL7 Version 2.x messaging in the MSA segment. |
| ACTION CODE (2.1 - 1.0.0) |
HL7-defined code system 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 xxxx). Used in HL7 Version 2.x messaging in the OBR segment. |
| ACTION CODE (2.2 - 2.0.0) |
HL7-defined code system 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 xxxx). Used in HL7 Version 2.x messaging in the OBR segment. |
| ADMINISTRATION DEVICE (2.2 - 1.0.0) |
Code system of concepts which specify the mechanical device used to aid in the administration of the drug or other treatment. Common examples are IV-sets of different types. Used in HL7 Version 2.x messaging in the RXR segment. |
| ADMINISTRATION METHOD (2.2 - 1.0.0) |
Code system of concepts which specify the specific method requested for the administration of the drug or treatment to the patient. Used in HL7 Version 2.x messaging in the RXR segment. |
| ADMINISTRIVE SITE (2.2 - 1.0.0) |
HL7-defined code system of concepts that specify a body site from which a specimen is obtained. Used in HL7 Version 2.x messaging in the OBX and CH7 segments. |
| ALLERGY SEVERITY (2.2 - 1.0.0) |
Code system of concepts which specify the general severity of an allergy. Used in HL7 Version 2.x messaging in the AL1 segment. |
| ALLERGY TYPE (2.2 - 1.0.0) |
Code system of concepts speciying a classification of general allergy categories (drug, food, pollen, etc.). Used in HL7 Version 2.x messaging in the AL1 segment. |
| AMOUNT TYPE (2.2 - 1.0.0) |
Code system of concepts which specify amount quantity type. Used in HL7 Version 2.x messaging in the RMC segment. |
| ASSIGNMENT OF BENEFITS (2.2 - 1.0.0) |
Code system of concepts which indicate whether an insured person agreed to assign the insurance benefits to the healthcare provider. If so, the insurance will pay the provider directly. Used in HL7 Version 2.x messaging in the IN1 segment. |
| Access Restriction Reason Code (2.6 - 1.0.0) |
Code system of concepts specifying the reason for the restricted access. Used in HL7 Version 2.x messaging in the ARV segment. |
| Access Restriction Value (2.6 - 1.0.0) |
Code system of concepts specifying the information to which access is restricted. Used in HL7 Version 2.x messaging in the ARV segment. Note that these new codes as of November 2018 have been temporarily loaded into this V2 code system pending availability of the currently unavailable new tooling, at which time this code systrem will be retired and a value set of codes from the HL7 V3 ActCode code system will be used instead for this table. |
| Access Restriction Value (2.9 - 1.1.0) |
Code system of concepts specifying the information to which access is restricted. Used in HL7 Version 2.x messaging in the ARV segment. Note that these new codes as of November 2018 have been temporarily loaded into this V2 code system pending availability of the currently unavailable new tooling, at which time this code systrem will be retired and a value set of codes from the HL7 V3 ActCode code system will be used instead for this table. |
| ActPriority (2.7 - 1.0.0) |
HL7-defined code system of concepts specifying the priority for the shipment. Used in HL7 Version 2.x messaging in the SHP segment. |
| Action Code (2.3 - 1.0.0) |
HL7-defined code system ofstatus codes of record operation. Used in Version 2 messaging, these are used in the RXA segment in the vaccine messages, where a method of correcting vaccination information transmitted with incorrect patient identifying information is needed. As of version 2.6, this table was replaced with table 0206, whose values are defined by code system xxxx. |
| Action Code (2.3 - 1.0.0) |
HL7-defined code system of concepts used in Patient Care for the intent of a problem or goal. Used in HL7 Version 2.x messaging in the GOL, ROL, PRB and PTH segments. |
| Action Code (2.5 - 1.1.0) |
HL7-defined code system ofstatus codes of record operation. Used in Version 2 messaging, these are used in the RXA segment in the vaccine messages, where a method of correcting vaccination information transmitted with incorrect patient identifying information is needed. As of version 2.6, this table was replaced with table 0206, whose values are defined by code system xxxx. |
| Action Taken in Response to the Event (2.3 - 1.0.0) |
HL7-defined code system of concepts used to define the action taken as a result of an event related to a product issue. Used in HL7 Version 2.x messaging in the PCR segment. |
| Active/Inactive (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying whether a person is currently a valid staff member. Used in HL7 Version 2.x messaging in the STF segment. |
| Additive (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the SPM and SAC segments. |
| Additive/Preservative (2.5 - 1.1.0) |
HL7-defined code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the SPM and SAC segments. |
| Address Expiration Reason (2.6 - 1.0.0) |
Code system of concepts specifying the reason this address was marked as “ended”. Used in HL7 Version 2.x messaging in the XAD segment. |
| Address Type (2.3 - 1.1.0) |
HL7-defined code system of concepts specifying types or kinds of addresses. Used in HL7 Version 2.x messaging in the XAD segment. |
| Address Type (2.7 - 1.4.0) |
HL7-defined code system of concepts specifying types or kinds of addresses. Used in HL7 Version 2.x messaging in the XAD segment. |
| Address Usage (2.6 - 1.0.0) |
HL7-defined code system of concepts specifying how an address is intended to be used. Used in HL7 Version 2.x messaging in the XAD segment. |
| Address type (2.3.1 - 1.2.0) |
HL7-defined code system of concepts specifying types or kinds of addresses. Used in HL7 Version 2.x messaging in the XAD segment. |
| Address type (2.6 - 1.3.0) |
HL7-defined code system of concepts specifying types or kinds of addresses. Used in HL7 Version 2.x messaging in the XAD segment. |
| Adjustment Action (2.6 - 1.0.0) |
Code system of concepts used to specify the action requested of the party that receives an adjustment. Used in the Adjustment (ADJ) segment in HL7 Version 2.x messaging. |
| Adjustment Category Code (2.6 - 1.0.0) |
Code system of concepts used to specify the category of adjustment and is used to assist in determining which table is used for Adjustment Reason. Used in the Adjustment (ADJ) segment in HL7 Version 2.x messaging. |
| Administration Method (2.6 - 1.1.0) |
Code system of concepts which specify the specific method requested for the administration of the drug or treatment to the patient. Used in HL7 Version 2.x messaging in the RXR segment. |
| Administrative Sex (2.4 - 2.0.0) |
Code system of concepts specifying a patient’s sex for administrative purposes. Used in HL7 Version 2.x messages in the PID segment. |
| Administrative Sex (2.9 - 3.0.0) |
tbd |
| Administrative Site (2.3 - 1.1.0) |
HL7-defined code system of concepts that specify a body site from which a specimen is obtained. Used in HL7 Version 2.x messaging in the OBX and CH7 segments. |
| Administrative site (2.3.1 - 1.2.0) |
HL7-defined code system of concepts that specify a body site from which a specimen is obtained. Used in HL7 Version 2.x messaging in the OBX and CH7 segments. |
| Admission Type (2.1 - 1.0.0) |
Code system of concepts specifying the circumstances under which the patient was or will be admitted. Used in HL7 Version 2.x messaging in the PV1 segment. |
| Admission Type (2.4 - 1.1.0) |
Code system of concepts specifying the circumstances under which the patient was or will be admitted. Used in HL7 Version 2.x messaging in the PV1 segment. |
| Admission level of care code (2.4 - 1.0.0) |
Code system of concepts specifying the acuity level assigned to the patient at the time of admission. Used in HL7 Version 2.x messaging in the PV2 segment. |
| Admit source (2.3.1 - 1.0.0) |
HL7 published code system of values that indicate where a patient was admitted. In the US, this field is used on UB92 FL20 “Source of Admission”; note that the UB codes listed are not an exhaustive or current list; refer to a UB specification for additional information. This needs review by HTA and PA/FM; this may be a value set built on external CMS codes from the UB. It has not been published after the HL7 Version 2.6 release of the Standard. |
| Adress Type (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying types or kinds of addresses. Used in HL7 Version 2.x messaging in the XAD segment. |
| Advanced Beneficiary Notice Code (2.3.1 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the ORC and FT1 segments. |
| Alert device code (2.4 - 1.0.0) |
Code system of concepts specifying any type of allergy alert device the patient may be carrying or wearing. Used in HL7 Version 2.x messaging in the IAM segment. |
| Alert level (2.4 - 1.0.0) |
HL7-defined code system of concepts 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). Used in the Equipment Detail (EQU) and Notification Detail (NDS) segments in HL7 Version 2.x messaging. |
| Allergen type (2.4 - 1.1.0) |
Code system of concepts speciying a classification of general allergy categories (drug, food, pollen, etc.). Used in HL7 Version 2.x messaging in the AL1 segment. |
| Allergy Clinical Status (2.4 - 1.0.0) |
Code system of concepts specifying the verification status for the allergy. Used in HL7 Version 2.x messaging in the IAM segment. |
| Allergy severity (2.4 - 1.1.0) |
Code system of concepts which specify the general severity of an allergy. Used in HL7 Version 2.x messaging in the AL1 segment. |
| Allow Substitution Codes (2.3 - 1.0.0) |
Code system of concepts used to indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment. Used in HL7 Version 2.x messaging in the AIS and AIG segments. |
| Alternate Character Sets (2.3 - 1.0.0) |
HL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment. |
| Alternate Character Sets (2.8 - 1.4.0) |
HL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment. |
| Alternate character set handling scheme (2.3.1 - 1.0.0) |
HL7-defined code system of concept 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. Used in HL7 Version 2.x messaging in the MSH segment. |
| Alternate character sets (2.3.1 - 1.1.0) |
HL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment. |
| Alternate character sets (2.5 - 1.2.0) |
HL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment. |
| Alternate character sets (2.6 - 1.3.0) |
HL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment. |
| Ambulatory Payment Classification code (2.4 - 1.0.0) |
Code system of concepts specifying the derived Ambulatory Payment Classification (APC) code. Used in HL7 Version 2.x messaging in the GP2 segment. |
| Ambulatory Status (2.1 - 1.0.0) |
Code system of concepts specifying permanent or transient handicapped conditions of a person. Used in HL7 Version 2.x messaging in the PV1 segment. |
| Amount Class (2.2 - 1.0.0) |
Code system of concepts specifying the amount quantity class. Used in HL7 Version 2.x messaging in the PTA segment. |
| Analyte Repeat Status (2.4 - 1.0.0) |
HL7-defined code system of concepts 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). Used in HL7 Version 2.x messaging in the Test Code Detail (TCD) segment. |
| Annotations (2.3 - 1.0.0) |
Code system of concepts specifying the coded entry associated with a given point in time during the waveform recording. Used in HL7 Version 2.x messaging in the Observation Result (OBX) Another Observation (ANO) segments. |
| Appointment Reason Codes (2.3 - 1.0.0) |
Code system of concepts used to describe the kind of appointment or the reason why an appointment has been scheduled. Used in HL7 Version 2.x messaging in the ARQ segment. |
| Appointment Type Codes (2.3 - 1.0.0) |
Code system of concepts used in an appointment request to describe the kind of appointment. Used in HL7 Version 2.x messaging in the ARQ segment. |
| Arm Stick (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the arm(s) receiving the stick. Used in HL7 Version 2.x messaging in the DON segment. |
| Artificial blood (2.4 - 1.0.0) |
Code system of concepts that identify the artificial blood identifier associated with the specimen. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging. |
| Assigning authority (2.4 - 1.0.0) |
HL7-defined code system of example values ONLY for Assigning Authority, and only pubished in HL7 Version 2.4; coded values for fields that are intended to specify Assinging Authority are intended to be locally user defined codes. |
| Authorization Mode (2.5 - 1.0.0) |
HL7-defined code system of concepts of forms of authorization a recorder may receive from the responsible practitioner to create or change an order. Used in HL7 Version 2.x messaging in the ORC segment. |
| Auto-Dilution Type (2.9 - 1.0.0) |
Code system of vendor-defined codes that specify the pre‑configured dilution to be applied on the instrument, which can be used instead of a numeric declaration. Used in Version 2 messaging in the TCD segment. |
| BED STATUS (2.1 - 1.0.0) |
Code system of concepts which specify the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not. Used in HL7 Version 2.x messaging in the DLD and PV1 segments. |
| BED STATUS (2.2 - 1.1.0) |
Code system of concepts which specify the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not. Used in HL7 Version 2.x messaging in the DLD and PV1 segments. |
| BP Observation Status Codes Interpretation (2.5 - 1.0.0) |
HL7-defined code system of concepts used 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. Used in the Blood Product Dispense Status (BPX) and Blood Product Transfusion/Disposition (BTX) segments in HL7 Version 2.x messaging. |
| Blood Product Code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a type of blood product. Used in HL7 Version 2 messaging in the BLC segment. |
| Blood Product Dispense Status (2.5 - 1.0.0) |
HL7-defined code system of concepts used 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”. Used in the Blood Product Dispense Status (BPX) segment in HL7 Version 2.x messaging. |
| Blood Product Processing Requirements (2.5 - 1.0.0) |
Code system of concepts used to 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. Used in the Blood Product Order (BPO) segment in HL7 Version 2.x messaging. |
| Blood Product Transfusion/Disposition Status (2.5 - 1.0.0) |
HL7-defined code system of concepts used 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.” Used in the Blood Product Transfusion/Disposition (BTX) segment in HL7 Version 2.x messaging. |
| Blood Product Transfusion/Disposition Status (2.9 - 1.1.0) |
HL7-defined code system of concepts used 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.” Used in the Blood Product Transfusion/Disposition (BTX) segment in HL7 Version 2.x messaging. |
| Blood Unit Type (2.8 - 1.0.0) |
HL7-defined code system of concepts used to specify the type of blood unit. Used in the Blood Unit Information (BUI) segment in HL7 Version 2.x messaging. |
| Body Parts (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying the part of the body. Used in HL7 Version 2 messaging in the RXR segment. |
| Body Site Modifier (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying the modifier for the body site. Used in HL7 Version 2.x messaging in the RXR segment. |
| Bolus Type (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the type of bolus. Used in HL7 Version 2.x messaging in the RXV segment. |
| CCL Value (2.6 - 1.0.0) |
Code system of concepts specifying the clinical complexity level (CCL) value for the determined diagnosis related group (DRG) for this diagnosis. US Realm. Used in HL7 Version 2.x messaging in the DG1 segment. |
| CHARGE TYPE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify someone or something other than the patient to be billed for a service. Used in HL7 Version 2.x messaging in the BLG segment. |
| CONFIDENTIALITY CODE (2.2 - 1.0.0) |
Code system of concepts specifying the degree to which special confidentiality protection should be applied to the observation. Used in HL7 Version 2.x messaging in the OM1 and ORC segments. |
| COORDINATION OF BENEFITS (2.2 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the IN1 segment. |
| CP Range Type (2.3 - 1.0.0) |
HL7-defined code system of concepts used to define a type of range used in composite pricing in financial transacxtions. Used in HL7 Version 2 messaging in the CP datatype. |
| CWE statuses (2.3.1 - 1.0.0) |
HL7-defined code system of comcepts 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 HL7 Version 2.x messaging, and the codes may be used in the ‘identifier’ component of the ‘triplets’ in that datatype. |
| Calendar Alignment (2.5 - 1.0.0) |
HL7-defined code system of concepts used to specify an alignment of the repetition to a calendar (e.g., to distinguish every 30 days from “the 5th of every month”). Used in HL7 Version 2 messaging in the RPT segment. |
| Causality Observations (2.3 - 1.0.0) |
HL7-defined code system of concepts used to record event observations regarding what may have caused a product related event. Used in HL7 Version 2.x messaging in the PCR segment. |
| Certificate Status (2.5 - 1.0.0) |
Code system of concepts specifying the status of the certificate held by the health professional. Used in HL7 Version 2 messaging in the CER segment. |
| Certification Category Code (2.8 - 1.0.0) |
Code system of concepts specifying the code for the certification category. Used in HL7 Version 2.x messaging in the IN3 segment. |
| Certification Status (2.3 - 1.0.0) |
HL7-defined code system of concepts used to specify the status of the practitioner’s speciality certification. Used in HL7 Version 2.x messaging in the Specialty Description (SPD) value and Practitioner Detail (PRA) segment. |
| Certification Type Code (2.8 - 1.0.0) |
Code system of concepts specifying the code for the certification type. Used in HL7 Version 2.x messaging in the IN3 segment. |
| Charge Type Reason (2.5 - 1.0.0) |
Code system of concepts specifying the choice of, and providing the clinical rationale for, a selected charge type. Used in HL7 Version 2.x messaging in the BLG segment. |
| Charge on Indicator (2.3 - 1.0.0) |
Code system of concepts used to define the event upon which a charge should be generated. Used in HL7 Version 2.x messaging in the PRC segment. |
| Check Digit Scheme (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying the check digit scheme employed. Used in HL7 Version 2.x messaging in PPN, XCN and XON segments. |
| Check Digit Scheme (2.2 - 1.1.0) |
HL7-defined code system of concepts specifying the check digit scheme employed. Used in HL7 Version 2.x messaging in PPN, XCN and XON segments. |
| Check Digit Scheme (2.3.1 - 1.2.0) |
HL7-defined code system of concepts specifying the check digit scheme employed. Used in HL7 Version 2.x messaging in PPN, XCN and XON segments. |
| Check Digit Scheme (2.6 - 1.3.0) |
HL7-defined code system of concepts specifying the check digit scheme employed. Used in HL7 Version 2.x messaging in PPN, XCN and XON segments. |
| Coding System (2.4 - 1.0.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the CWE segment. |
| Coding System (2.6 - 1.1.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the CWE segment. |
| Coding System (2.7 - 1.2.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the CWE segment. |
| Coding System (2.9 - 1.3.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the CWE segment. |
| Coding System (2.9.1 - 1.4.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the CWE segment. |
| Collection Event/Process Step Limit (2.8.2 - 1.0.0) |
HL7-defined code system of concepts specifying the limit for the collection event or process step. Used in HL7 Version 2.x messaging in the OMC segment. |
| Command Response (2.4 - 1.0.0) |
Code system of concepts identifying the response of the previously issued command. Used in HL7 Version 2.x messaging in the Equipment Command Response (ECR) and Interaction Status Detail (ISD) segments. |
| Comment type (2.3.1 - 1.0.0) |
Code system of concepts that identify the type of comment text being sent in the specific comment record. Used in the Notes and Comments (NTE) segment in HL7 Version 2.x messaging. |
| Communication Location (2.8.2 - 1.0.0) |
HL7-defined code system of concepts specifying the communication location. Used in HL7 Version 2.x messaging in the OMC segment. |
| Completion Status (2.3 - 1.0.0) |
HL7-defined code system of concepts specifying the status of the treatment administration event segment. Used in HL7 Version 2.x messaging in the Pharmacy Order Administration (RXA) segment. |
| Computation Type (2.5 - 1.0.0) |
HL7-defined code system of concepts used to specify if the change is computed as a percent change or as an absolute change. Used in the Delta (DLT) segment in HL7 Version 2.x messaging. |
| Concept Domains for 2.1 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.2 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.3 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.3.1 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.4 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.5 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.5.1 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.6 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.7 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.7.1 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.8 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.8.1 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.8.2 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.9 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Concept Domains for 2.9.1 |
List of all concept domains that are used within this HL7 v2 version to designate the semantic concepts for coded elewments. |
| Condition code (2.3.1 - 1.0.0) |
HL7-defined code system of concepts specifying the condition code. This field is defined by CMS or other regulartory agencies. Used in HL7 Version 2.x messaging in the UB2 segment. |
| Confidentiality (2.7 - 1.0.0) |
HL7-defined code system of concepts specifying the confidentiality for the shipment. Used in HL7 Version 2.x messaging in the SHP segment. |
| Consent Bypass Reason (2.5 - 1.0.0) |
Code system of concepts specifying the reason the subject’s consent was not sought. Used in HL7 Version 2.x messaging in the CON segment. |
| Consent Disclosure Level (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying how much information was disclosed to the subject as part of the informed consent process. Used in HL7 Version 2.x messaging in the CON segment. |
| Consent Mode (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying the method in which a subject provides consent. Used in HL7 Version 2.x messaging in the TXA and CON segments. |
| Consent Non-Disclosure Reason (2.5 - 1.0.0) |
Code system of concepts used to specify a reason the subject did not receive full disclosure. Used in the Consent (CON) segment in HL7 Version 2.x messaging. |
| Consent Status (2.5 - 1.0.0) |
HL7-code system of concepts specifying whether the consent has been sought and granted. Used in HL7 Version 2.x messaging in the TXA and CON segments. |
| Consent Type (2.5 - 1.0.0) |
Code system of concepts specifying to what the subject is consenting, i.e. what type of service, surgical procedure, information access/release or other event. Used in HL7 Version 2.x messaging in the TXA and CON segments. |
| Contact Role (2.3 - 1.0.0) |
HL7-defined code system of concepts which specify the relationship role (next of kin, employer, emergency contact, etc.) and specifies the role that a next of kin/associated parties plays with regard to a patient. Examples might include an employer, emergency contact, next of kin, insurance company, state agency, federal agency, etc. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that sent a referral. Used in HL7 Version 2 messaging through 2.4; replaced with 2.16.840.1.113883.18.58 as of 2.5. |
| Contact Role (2.5 - 1.0.0) |
Code system of concepts which specify a relationship role that the next of kin/associated parties plays with regard to the patient. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that sent a referral. Used in HL7 Version 2 messaging in the NK1 and CTD segments after 2.5, when it replace 2.16.840.1.113883.18.57. |
| Container Condition (2.7 - 1.0.0) |
HL7-defined code system of concepts used 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. Used in the Specimen (SPM), Shipment (SHP) and Shipment Package (PAC) segments in HL7 Version 2.x messaging. |
| Container Status (2.9 - 2.0.0) |
HL7-defined code system of concepts that identify the status of the unique container in which the specimen resides at the time the transaction was initiated. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging. |
| Container status (2.4 - 1.0.0) |
HL7-defined code system of concepts that identify the status of the unique container in which the specimen resides at the time the transaction was initiated. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging. |
| Continuation style code (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying whether it is a fragmented message or part of an interactive continuation message. Used in HL7 Version 2.x messaging in the Continuation Pointer (DSC) segment. |
| Controlled Substance Schedule (2.5 - 1.0.0) |
Code system of concepts specifying the class of the drug or other substance if its usage is controlled by legislation. In the USA, such legislation includes the federal Controlled Substance Act (CSA) or a State Uniform Controlled Substance Act. Other countries should create their own versions of this table. Used in HL7 Version 2.x messaging in the RXE segment. The name of the table is taken from the Pharmacy Law Digest July 1988. |
| Coverage Type (2.3 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Insurance (IN1) segment. |
| Coverage Type (2.6 - 1.1.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Insurance (IN1) segment. |
| Cumulative Dosage Limit UoM (2.8 - 1.0.0) |
Code system of concepts specifying the unit of measure (UoM) for the cumulative dosage limit. Used in HL7 Version 2.x messaging in the CDO segment. |
| Cycle Type (2.6 - 1.0.0) |
Code system of concepts specifying the type of cycle that is being executed. A cycle type is a specific sterilization method used for a specific type of supply item. Used in HL7 Version 2.x messaging in the SCD segment. |
| Cyclic Entry/Exit Indicator (2.5 - 1.0.0) |
HL7-defined code system of concepts used to specify if this service request is the first or last service request in a cyclic series of service requests. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging. |
| Cyclic Entry/Exit Indicator (2.9 - 1.1.0) |
HL7-defined code system of concepts used to specify if this service request is the first or last service request in a cyclic series of service requests. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging. |
| DATE/TIME QUALIFIER (2.2 - 1.0.0) |
HL7-defined code system of concepts that specify a type of date referred to in query specifications. Used in HL7 Version 2 messaging in the QRF segment. |
| DATE/TIME SELECTION QUALIFIER (2.2 - 1.0.0) |
HL7-defined code system of conceptss that allow the specification of certain types of values within the date/time range. Used in HL7 Vesion 2 messaging in the QRF segment. |
| DAY TYPE (2.2 - 1.0.0) |
Code system of concepts which specify whether the days are denied, pending or approved. Used in HL7 Version 2.x messaging in the DTN segment. |
| DEFERRED RESPONSE TYPE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify which type of deferred query resonse is desired, as specified with the query parameters. Used in HL7 Version 2 messaging in the QRD segment. |
| DEFERRED RESPONSE TYPE (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify which type of deferred query resonse is desired, as specified with the query parameters. Used in HL7 Version 2 messaging in the QRD segment. |
| DELAYED ACKNOWLEDGMENT TYPE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify a response type used in deferred processing two phase reply for delayed acknowldgement mode of the original acknowledgement mechanism defined in HL7 Version 2.x messaging and used in the MSH segment. |
| DELAYED ACKNOWLEDGMENT TYPE (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify a response type used in deferred processing two phase reply for delayed acknowldgement mode of the original acknowledgement mechanism defined in HL7 Version 2.x messaging and used in the MSH segment. |
| DERIVED SPECIMEN (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify 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. Used in HL7 Version 2.x messaging in the OM4 segment. |
| DIAGNOSTIC SERVICE SECTION ID (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify a section of a diagnostic service where the observation may be performed. Used in HL7 Version 2.x messaging in the OBR and OM4 segments. |
| DIAGNOSTIC SERVICE SECTION ID (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify a section of a diagnostic service where the observation may be performed. Used in HL7 Version 2.x messaging in the OBR and OM4 segments. |
| DIET TYPE (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify whether the type of diet. Used in HL7 Version 2.x messaging in the ODS segment. |
| DRG Diagnosis Determination Status (2.6 - 1.0.0) |
HL7-defined cCode system of concepts specifying the status of a diagnosis for a diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DG1 segment. |
| DRG Grouping Status (2.6 - 1.0.0) |
Code system of concepts specifying the status of the use of the gender information for diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment. |
| DRG Procedure Determination Status (2.6 - 1.0.0) |
Code system of concepts specifying the status of the use of this particular procedure for the diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the PR1 segment. |
| DRG Procedure Relevance (2.6 - 1.0.0) |
Code system of concepts specifying the relevance of this particular procedure for the diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the PR1 segment. |
| DRG Status Financial Calculation (2.6 - 1.0.0) |
Code system of concepts specifying the status of the diagnosis related group (DRG) calculation regarding the financial aspects. US Realm. Used in HL7 Version 2.x messaging in the DRG segment. |
| DRG transfer type (2.4 - 1.0.0) |
HL7-defined code system of concepts which 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. Used in HL7 Version 2 messaging in the DRG segment. |
| Data Types (2.7 - 1.2.0) |
HL7-defined code system of concepts specifying the format of the observation value in the Observation Result (OBX). Used in HL7 Version 2.x messaging in the OBX, OM1, OM3 and OMC segments. |
| Data Types (2.9.1 - 1.4.0) |
HL7-defined code system of concepts specifying the format of the observation value in the Observation Result (OBX). Used in HL7 Version 2.x messaging in the OBX, OM1, OM3 and OMC segments. |
| Data types (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying the format of the observation value in the Observation Result (OBX). Used in HL7 Version 2.x messaging in the OBX, OM1, OM3 and OMC segments. |
| Data types (2.5 - 1.1.0) |
HL7-defined code system of concepts specifying the format of the observation value in the Observation Result (OBX). Used in HL7 Version 2.x messaging in the OBX, OM1, OM3 and OMC segments. |
| Data types (2.5.1 - 1.3.0) |
HL7-defined code system of concepts specifying the format of the observation value in the Observation Result (OBX). Used in HL7 Version 2.x messaging in the OBX, OM1, OM3 and OMC segments. |
| Date Format (2.6 - 1.0.0) |
Code system of concepts that identify the date format for a decontamination/sterilization instance. Used in HL7 Version 2.x messaging in the SCP segment. |
| Days of the Week (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify the day(s) of the week when a location may be scheduled for appointments. Used in HL7 Version 2.x messaging in the UVC and LDP segments. |
| Degree/License/Certificate (2.7 - 1.0.0) |
Code system of concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in HL7 Version 2.x messaging in the CNN segment; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Degree/License/Certificate (2.8 - 1.1.0) |
Code system of concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in HL7 Version 2.x messaging in the CNN segment; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Degree/license/certificate (2.5 - 1.2.0) |
HL7-defined code system of concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7. |
| Denial or Rejection Code (2.4 - 1.0.0) |
Code system of concepts specifying the OCE status of the line item. Used in HL7 Version 2.x messaging in the GP2 segment. |
| Device Data State (2.6 - 1.0.0) |
Code system of concepts that define the state of the data as provided from a device. Used in HL7 Version 2.x messaging in the SDD segment. |
| Device Status (2.6 - 1.0.0) |
Code system of concepts that communicate the state of a device. Used in HL7 Version 2.x messaging in the SCD segment. |
| Diagnosis Classification (2.3 - 1.0.0) |
Code system of concepts used to classify whether a patient visit can be related to a diagnosis. Used in HL7 Version 2.x messaging in the DG1 segment. |
| Diagnosis Type (2.3 - 1.0.0) |
Code system of concepts specifying a type of diagnosis being sent. Used in HL7 Version 2.x messaging in the DG1 segment.. |
| Diagnosis priority (2.3.1 - 1.0.0) |
Code system of concepts 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. Used in the DG1 segment in HL7 Version 2.x messaging. 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. |
| Diagnostic Service Section ID (2.3 - 1.2.0) |
HL7-defined code system of concepts which specify a section of a diagnostic service where the observation may be performed. Used in HL7 Version 2.x messaging in the OBR and OM4 segments. |
| Diagnostic Service Section ID (2.9.1 - 1.4.0) |
HL7-defined code system of concepts which specify a section of a diagnostic service where the observation may be performed. Used in HL7 Version 2.x messaging in the OBR and OM4 segments. |
| Diagnostic service section ID (2.4 - 1.3.0) |
HL7-defined code system of concepts which specify a section of a diagnostic service where the observation may be performed. Used in HL7 Version 2.x messaging in the OBR and OM4 segments. |
| Disabled Person (2.3 - 1.0.0) |
Code system of concepts used to 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. Used in HL7 Version 2.x messaging in the Disability (DB1) segment. |
| Discharge disposition (2.3.1 - 1.0.0) |
Code system of concepts which specify the disposition of the patient at time of discharge (i.e., discharged to home, expired, etc.). Used in HL7 Version 2.x messaging in the PV1 segment. |
| Dispense Method (2.3 - 1.0.0) |
HL7-definde code system of concepts specifying the method by which treatment is dispensed. Used in HL7 Version 2.x messaging in the Pharmacy/Treatment Encoded order (RXE) and Pharmacy/Treatment dispense (RXD) segments. |
| Dispense Type (2.5 - 1.0.0) |
Code system of concepts specifying the type of dispensing event that occurred. Used in HL7 Version 2.x messaging in the RXD segment. |
| Document Availability Status (2.3 - 1.0.0) |
HL7-defined code system of concepts used to define whether a patient document is appropriate or available for use in patient care. Used in HL7 Version 2.x messaging in the TXA segment. |
| Document Completion Status (2.3 - 1.0.0) |
HL7-defined code system of concepts used to record the state of a document in a workflow. Used in HL7 Version 2.x messaging in the TXA segment. |
| Document Confidentiality Status (2.3 - 1.0.0) |
HL7-defined code system of concetps used to identify the degree to which special confidentiality protection should be applied to this information. Used in HL7 Version 2.x messaging in the TXA segment, but only in HL7 release 2.3; as of 2.3.1 it was replaced by 2.16.840.1.113883.18.166 documentConfidentialityStatus2. |
| Document Storage Status (2.3 - 1.0.0) |
HL7-defined code system of concepts used to describe the availability of a document in relation to the type of storage. Used in HL7 Version 2.x messaging in the TXA segment. |
| Document availability status (2.3.1 - 1.1.0) |
HL7-defined code system of concepts used to define whether a patient document is appropriate or available for use in patient care. Used in HL7 Version 2.x messaging in the TXA segment. |
| Document confidentiality status (2.3.1 - 2.0.0) |
HL7-defined code system of concetps used to identify the degree to which special confidentiality protection should be applied to this information. Used in HL7 Version 2.x messaging in the TXA segment. |
| Duration Categories (2.3 - 1.0.0) |
Code system of concepts used to classify an observation definition as intended to measure a patient’s state at a point in time. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Duration categories (2.4 - 1.1.0) |
Code system of concepts used to classify an observation definition as intended to measure a patient’s state at a point in time. Used in HL7 Version 2.x messaging in the OM1 segment. |
| ELIGIBILITY SOURCE (2.2 - 1.0.0) |
Code system of concepts which specify the source of information about the insured’s eligibility for benefits. Used in HL7 Version 2.x messaging in the IN2 segment. |
| ETHNIC GROUP (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying the patient’s race for administrative transactions. Note replaced with the CDC code system 2.16.840.1.113883.6.238 as of version 2.2. |
| EVENT REASON (2.1 - 1.0.0) |
Code system of concepts which specify the reason for an event. Used in HL7 Version 2.x messaging in the EVN segment. |
| EVENT REASON (2.2 - 1.1.0) |
Code system of concepts which specify the reason for an event. Used in HL7 Version 2.x messaging in the EVN segment. |
| Employment Status (2.5 - 2.0.0) |
HL7-defined code system of concepts which specify an employment status of a person. Used in HL7 Version 2 messaging in the GT1 segment. |
| Employment status (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify an employment status of a person. Used in HL7 Version 2 messaging in the GT1 segment. |
| Encoding (2.3 - 1.0.0) |
HL7-defined code system of concept 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. Used in HL7 Version 2.x messaging in the ED datatypes. |
| Equipment State (2.8 - 1.1.0) |
HL7-defined code system of concepts that identify the status the equipment was in at the time the transaction was initiated. Used in HL7 Version 2.x messaging in the EQU segment. |
| Equipment State (2.9 - 1.2.0) |
HL7-defined code system of concepts that identify the status the equipment was in at the time the transaction was initiated. Used in HL7 Version 2.x messaging in the EQU segment. |
| Equipment State Indicator Type Code (2.9 - 1.0.0) |
HL7-defined code sytem of cocepts that specify the type of measurement of the state of an automated laboratory instrument. Used in HL7 Version 2.x messaging in the INV segment. |
| Equipment state (2.4 - 1.0.0) |
HL7-defined code system of concepts that identify the status the equipment was in at the time the transaction was initiated. Used in HL7 Version 2.x messaging in the EQU segment. |
| Error Severity (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying 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. Used in HL7 Version 2.x messaging acknowledgment in the ERR segment. |
| Error Severity (2.6 - 1.1.0) |
HL7-defined code system of concepts specifying 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. Used in HL7 Version 2.x messaging acknowledgment in the ERR segment. |
| Escort Required (2.3 - 1.0.0) |
HL7-defined code system of concepts defining whether patient transportation preparations are in place. Used in HL7 Version 2.x messaging in the OBR segment. |
| Event (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.2 - 1.1.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.3 - 1.2.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.3.1 - 1.3.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.4 - 1.4.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.5 - 1.5.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.5.1 - 1.6.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.6 - 1.7.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.7 - 1.8.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.8 - 1.9.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.8.2 - 1.10.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event (2.9 - 1.11.0) |
HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment. |
| Event Consequence (2.3 - 1.0.0) |
HL7-defined code system of concepts used to describe the impact of an event on a patient. Used in HL7 Version 2.x messaging in the PEO segment. |
| Event Expected (2.3 - 1.0.0) |
HL7-defined code system of concepts used to communicate whether an event has been judged to be expected or unexpected. Used in HL7 Version 2.x messaging in the PEO segment. |
| Event Qualification (2.3 - 1.0.0) |
HL7-defined code system of concepts used to qualify an event related to a product experience. Used in HL7 Version 2.x messaging in the PEO segment. |
| Event Related Period (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying a common (periodical) activity of daily living. Used in HL7 Version 2 messaging in the RPT segment. |
| Event Seriousness (2.3 - 1.0.0) |
HL7-defined code system of concepts used by a sender to designate an event as serious or significant. Used in HL7 Version 2.x messaging in the PEO segment. |
| Event Type (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying the type of event of the message. Used in HL7 Version 2.x messaging in the EQP segment. |
| Event reason (2.5 - 1.2.0) |
Code system of concepts which specify the reason for an event. Used in HL7 Version 2.x messaging in the EVN segment. |
| Exclusive Test (2.8 - 1.0.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in Master Files (OM1 segment) to characterize observations in a master of such orderables. |
| Expanded Yes/no Indicator (2.5 - 1.0.0) |
HL7-defined code system of concepts used 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”. Used in numerous locations in HL7 Version 2.x messaging. |
| Extended Priority Codes (2.5 - 1.0.0) |
Code system of concepts describing the urgency of a request carried in an order. Used in HL7 Version 2.x messaging in timing/quantity; in older versions of the Standard was used in the TQ datatype, but in later versions it is used in the TQ1 segment (which replaced the TQ datatype which has been withdrawn). |
| FILE-LEVEL EVENT CODE (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying file-level events for master files. Used in HL7 Version 2 messaging in the MFI segment. |
| Facility Type (2.3 - 1.0.0) |
HL7-defined code system of concepts used to specify the type of facility. Used in HL7 Version 2.x messaging in the Facility (FAC) segment. |
| Filler Status Codes (2.3 - 1.0.0) |
Code system of concepts used to describe an appointment status from the perspective of the entity assigned to fulfill the appointment. Used in HL7 Version 2.x messaging in the SCH segment. |
| Filler status codes (2.5 - 1.1.0) |
Code system of concepts used to describe an appointment status from the perspective of the entity assigned to fulfill the appointment. Used in HL7 Version 2.x messaging in the SCH segment. |
| Formulary Status (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying whether or not the pharmaceutical substance is part of the local formulary. Used in HL7 Version 2.x messaging in the RXE segment. |
| Gender Harmony Concepts (2.9.1 - 1.0.0) |
See http://loinc.org for a detailed description; the HL70396 code for LOINC is ‘LN’ |
| Gestation category code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify the status of a birth in relation to the gestation. Used in HL7 Version 2 messaging in the ABS segment. |
| Grouper Status (2.6 - 1.0.0) |
Code system of concepts specifying the status of a grouper in general. US Realm. Used in HL7 Version 2.x messaging in the DRG segment. |
| Health Care Provider Area of Specialization (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying the more specific service or occupation within the healthcare provider type of the practitioner at a specific organization unit. Used in HL7 Version 2.x messaging in the ORG segment. |
| Health Care Provider Classification (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying the more specific service or occupation within the healthcare provider type of the practitioner at a specific organization unit. Used in HL7 Version 2.x messaging in the ORG segment. |
| Health Care Provider Type Code (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying the major grouping of the service or occupation of the practitioner at a specific organization unit. Used in HL7 Version 2.x messaging in the ORG segment. |
| Identifier Type (2.3 - 1.0.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identifier Type (2.7 - 1.5.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identifier Type (2.9.1 - 1.9.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identifier type (2.3.1 - 1.1.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identifier type (2.4 - 1.2.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identifier type (2.5 - 1.3.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identifier type (2.6 - 1.4.0) |
HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON. |
| Identity Reliability Code (2.4 - 1.0.0) |
Code system of concepts specifying the reliability of patient/person identifying data transmitted via a transaction. Used in HL7 Version 2.x messaging in the PID segment. |
| Identity may be Divulged (2.3 - 1.0.0) |
HL7-defined code system of concepts used to define whether the primary observer has given permission for their identification information to be provided to a product manufacturer. Used in HL7 Version 2.x messaging in the PEO segment. |
| Immunization registry status (2.4 - 1.0.0) |
Code system of concepts specifying the immunization registry status of the patient. Used in HL7 Version 2.x messaging in the PD1 segment. |
| Inactive Reason Code (2.5 - 1.0.0) |
Code system of concepts specifying the reason the staff member is inactive. Used in HL7 Version 2 messaging in the STF segment. |
| Incident type code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a classification of types of incidents. Used in HL7 Version 2 messaging in the RMI segment. |
| Indirect Exposure Mechanism (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify the mechanism of product transmission when the product has not been directly applied to the patient. Used in HL7 Version 2.x messaging in the PCR segment. |
| Inform Person Code (2.5 - 1.0.0) |
Code system of concepts specifying who (if anyone) should or should not be informed of an error. Used in the Error (ERR) segment in HL7 Version 2.x messaging. |
| Institution Relationship Type (2.5 - 1.0.0) |
Code system of concepts specifying the relationship the staff person has with the institution for whom he/she provides services. Used in HL7 Version 2 messaging in the STF segment. |
| Intended Procedure Type (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the type of intended procedure. Used in HL7 Version 2.x messaging in the DON segment. |
| Interpretation Codes (2.7 - 1.2.0) |
HL7-defined code system of concepts which specify a categorical assessment of an observation value. Used in HL7 Version 2.x messaging in the OBX segment. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. |
| Interpretation Codes (2.8.2 - 1.3.0) |
HL7-defined code system of concepts which specify a categorical assessment of an observation value. Used in HL7 Version 2.x messaging in the OBX segment. Notes: This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. |
| Invoice Control Code (2.6 - 1.0.0) |
Code system of concepts used to specify what action is being performed by this message. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging. |
| Invoice Processing Results Status (2.6 - 1.0.0) |
Code system of concepts used to specify the processing status for an Invoice Processing Result. Used in the Invoice Processing Result (IPR) segment in HL7 Version 2.x messaging. |
| Invoice Reason Codes (2.6 - 1.0.0) |
Code system of concepts used to specify the reason for this invoice. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging. |
| Invoice Type (2.6 - 1.0.0) |
Code system of concepts used to specify the type of invoice. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging. |
| Item Status (2.6 - 1.0.0) |
Code system of concepts specifying the status (useful for reporting and item usage purposes) that applies to an item. Used in HL7 Version 2.x messaging in the ITM segment. |
| Item Type (2.6 - 1.0.0) |
Code system of concepts specifying a classification of material items into like groups as defined and utilized within an operating room setting for charting procedures. Used in HL7 Version 2.x messaging in the ITM segment. |
| Job status (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying the next of kin/associated party’s job status. Used in HL7 Version 2.x messaging in the Next of Kin/Associated Parties (NK1) segment. |
| Jurisdictional Breadth (2.5 - 1.0.0) |
Code system of concepts specifying the breadth/extent of the jurisdiction where the qualification is valid. Used in HL7 Version 2 messaging in the CER segment. |
| Kind of Quantity (2.3 - 1.0.0) |
HL7 published code system of concepts that describe categories of an underlying kind of property represented by an observation. These are intended to 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. These defined categories are derived from the approach described in 1995 edition of the IUPAC Silver Book. These distinctions are used in IUPAC and LOINC standard codes. Needs review by OO and HTA to determined if this is a value set built on LOINC part codes or some other external vocabulary. |
| Labor Calculation Type (2.6 - 1.0.0) |
Code system of concepts that identify the method used to calculate employee labor and measure employee productivity. Used in HL7 Version 2.x messaging in the SCP segment. |
| Language ability (2.4 - 1.0.0) |
Code system of concepts which specify codes that indicate the ability that a Staff Member possesses with respect to the language. Used in HL7 Version 2.x messaging in the LAN segment. |
| Language proficiency (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a level of knowledge that a Staff Member possesses with respect to their language ability. Used in HL7 Version 2 messaging in the LAN segment. |
| Level of Care (2.3 - 1.0.0) |
Code system of concepts used to identify the level of care a patient may be afforded when assigned to this location definition. Used in HL7 Version 2.x messaging in the LCH segment. |
| Limitation Type Codes (2.8.2 - 1.0.0) |
HL7-defined code system of concepts specifying the type of limitation. Used in HL7 Version 2.x messaging in the DPS segment. |
| Living Arrangements (2.3 - 1.0.0) |
Code system of concepts characterizing the situation that patient-associated parties live in at their residential address. Used in HL7 Version 2.x messaging in the NK1 and PD1 segments. |
| Living Dependency (2.3 - 1.0.0) |
HL7-defined code system of concepts that identify specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient’s healthcare needs. This information can be used for discharge planning. Examples might include Spouse Dependent, Medical Supervision Required, Small Children Dependent. Used in Version 2.s messaging in the NK1 segment. Used in HL7 Version 2 messaging only in Versions 2.3 and 2.3.1; superceded by 2.16.840.1.113883.18.124 livingDependency2 in Version 2.4 of the Standard. |
| Living Dependency (2.5 - 1.1.0) |
HL7-defined code system of concepts that identify specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient’s healthcare needs. This information can be used for discharge planning. Examples might include Spouse Dependent, Medical Supervision Required, Small Children Dependent. Used in Version 2.s messaging in the NK1 segment. |
| Living Will (2.3 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Patient Visit - Additional Information ( PV2) and Patient Additional Demographic (PD1) segments. |
| Living arrangement (2.3.1 - 1.1.0) |
Code system of concepts characterizing the situation that patient-associated parties live in at their residential address. Used in HL7 Version 2.x messaging in the NK1 and PD1 segments. |
| Living dependency (2.4 - 1.0.0) |
HL7-defined code system of concepts that identify specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient’s healthcare needs. This information can be used for discharge planning. Examples might include Spouse Dependent, Medical Supervision Required, Small Children Dependent. Used in Version 2.s messaging in the NK1 segment. |
| Load Status (2.6 - 1.0.0) |
Code system of concepts used to define the status of the information provided in a device sterilization or decontamination cycle. Used in HL7 Version 2.x messaging in the SDD segment. |
| Local/remote control state (2.4 - 1.0.0) |
HL7-defined code system of concepts 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). Used in the Equipment Detail (EQU) segment in HL7 Version 2.x messaging. |
| Location Characteristic ID (2.3 - 1.0.0) |
Code system of concepts specifying an identifier code to show which characteristic is being communicated with the segment. Used in HL7 Version 2.x messaging in the Location Characteristic (LCH) segment. |
| Location Equipment (2.3 - 1.0.0) |
Code system of concepts used to identify the equipment available in a location definition identified as a room or bed. Used in HL7 Version 2.x messaging in the LOC segment. |
| Location Relationship ID (2.3 - 1.0.0) |
Code system of concepts specifying an identifier code to show which relationship is being communicated with the segment. Used in HL7 Version 2.x messaging in the Location Relationship (LRL) segment. |
| Location service code (2.4 - 1.0.0) |
Code system of concepts specifying the types of services provided by the location. Used in HL7 Version 2.x messaging in the LOC segment. |
| Lot Control (2.6 - 1.0.0) |
Code system of concepts that define whether the sterilization load for a device is built in the sub-sterile area adjacent to an Operating Room or the Central Processing Department. Used in HL7 Version 2.x messaging in the SCP segment. |
| MAIL CLAIM PARTY (2.2 - 1.0.0) |
Code system of concepts which specify a party to which a claim should be mailed when claims are sent by mail. Used in HL7 Version 2.x messaging in the IN2 segment. |
| MASTER FILE IDENTIFIER CODE (2.2 - 1.0.0) |
HL7-defined code system of concepts which are represented by codes identifying HL7 Versions 2.x Master Files. Used in HL7 Version 2.x messaging in the MFI segment. |
| MESSAGE TYPE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| MESSAGE TYPE (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| MFN Recode-Level Error Return (2.2 - 1.0.0) |
Code system of concepts specifying the status of the requested update. Site-defined table, specific to each master file being updated via this transaction. Used in HL7 Version 2.x messaging in the MFA segment. |
| MIME Types (2.6 - 1.0.0) |
Code system of concepts specifying the general type of data. Used in HL7 Version 2.x messaging in the RP and ED datatypes. |
| MIME base64 encoding Characters (2.3 - 1.0.0) |
HL7-defined code system of concepts specifying the characters used in the MIME Base 64 encoding mechanism. These are for reference only, as they are not carried as explicit code values in any HL7 coded field. This table was published only in releases 2.3, 2.3.1, and 2.4 of the Standard, and was removed thereafter. |
| Main type of referenced Data (2.3 - 1.1.0) |
HL7-defined code system of concepts declaring the general type of media data that is encoded. Used in v2.5.1 interfaces and earlier, and replaced with the full set of IANA media types as a standard coding system for this after HL7 version 2.6 (see value set 2.16.840.1.113883.21.425 hl7VS-mimeTypes for HL7 table 0834 built on MIME types). More information may be found at http://www.iana.org/assignments/media-types/media-types.xhtml |
| Manufacturers of Vaccines (2.3 - 1.0.0) |
Code system of concepts specifying the organization that manufactures a vaccine. The values are maintained by the US Centers of Disease Control. Used in HL7 Version 2.x messaging in the RXA, RXD and RXG segments. |
| Manufacturers of Vaccines (code=MVX) (2.5 - 1.2.0) |
Table of codes specifying 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 |
| Manufacturers of Vaccines (code=MVX) (2.6 - 1.3.0) |
Table of codes specifying 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 |
| Manufacturers of vaccines (code=MVX) (2.3.1 - 1.1.0) |
Code system of concepts specifying the organization that manufactures a vaccine. The values are maintained by the US Centers of Disease Control. Used in HL7 Version 2.x messaging in the RXA, RXD and RXG segments. |
| Marital Status (2.1 - 1.0.0) |
Code system of concepts specifying a person’s marital (civil/legal) status. Used in HL7 Version 2.x messages in the PID segment. |
| Marital Status (2.4 - 1.1.0) |
Code system of concepts specifying a person’s marital (civil/legal) status. Used in HL7 Version 2.x messages in the PID segment. |
| Marketing Basis (2.3 - 1.0.0) |
HL7-defined code system of concepts used to specify the basis for marketing approval. Used in HL7 Version 2.x messaging in the Product Detail Country (PDC) segment. |
| Master File Identifier Code (2.3 - 1.1.0) |
HL7-defined code system of concepts which are represented by codes identifying HL7 Versions 2.x Master Files. Used in HL7 Version 2.x messaging in the MFI segment. |
| Master file identifier code (2.3.1 - 1.2.0) |
HL7-defined code system of concepts which are represented by codes identifying HL7 Versions 2.x Master Files. Used in HL7 Version 2.x messaging in the MFI segment. |
| Master file identifier code (2.4 - 1.3.0) |
HL7-defined code system of concepts which are represented by codes identifying HL7 Versions 2.x Master Files. Used in HL7 Version 2.x messaging in the MFI segment. |
| Master file identifier code (2.5 - 1.4.0) |
HL7-defined code system of concepts which are represented by codes identifying HL7 Versions 2.x Master Files. Used in HL7 Version 2.x messaging in the MFI segment. |
| Match reason (2.4 - 1.0.0) |
Code system of concepts 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. Used in HL7 Version 2.x messaging in the Query Response Instance (QRI) segment. |
| Medical Role Executing Physician (2.6 - 1.0.0) |
Code system of concepts specifying the role of the physician (“self-employed” or “employed”). Used in HL7 Version 2.x messaging in the PSL segment. |
| Message Error Condition Codes (2.7 - 1.1.0) |
HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging. |
| Message Error Condition Codes (2.9 - 1.2.0) |
HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging. |
| Message Structure (2.3.1 - 1.0.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.4 - 1.1.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.5 - 1.2.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.5.1 - 1.6.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.6 - 1.3.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.7 - 1.4.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.7.1 - 1.7.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.8 - 1.5.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.8.2 - 1.8.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Structure (2.9.1 - 1.9.0) |
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Type (2.3 - 1.2.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Type (2.7 - 1.7.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Type (2.7.1 - 1.10.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Type (2.8 - 1.8.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message Type (2.9.1 - 1.11.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message error condition codes (2.3.1 - 1.0.0) |
HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging. |
| Message type (2.3.1 - 1.3.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message type (2.4 - 1.4.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message type (2.5 - 1.5.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message type (2.5.1 - 1.9.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message type (2.6 - 1.6.0) |
HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment. |
| Message waiting priority (2.6 - 1.0.0) |
HL7-defined code system of concepts which specify the disposition of the patient at time of discharge (i.e., discharged to home, expired, etc.). Used in HL7 Version 2.x messaging in the MSA segment. |
| Military rank/grade (2.3.1 - 1.0.0) |
Code system of concepts which specify the military rank/grade of the patient. Used in HL7 Version 2.x messaging in the PD1 segment. |
| Military rank/grade (2.4 - 2.0.0) |
Code system of concepts which specify the military rank/grade of the patient. Used in HL7 Version 2.x messaging in the PD1 segment. |
| Military service (2.3.1 - 1.0.0) |
Code system of concepts which specify the military branch. This field is defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the PD1 segment. |
| Military service (2.4 - 1.1.0) |
Code system of concepts which specify the military branch. This field is defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the PD1 segment. |
| Military status (2.3.1 - 1.0.0) |
Code system of concepts which specify the military status of the patient. This field is defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the PD1 segment. |
| Modality (2.3 - 1.0.0) |
Code system of concepts used to 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. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Mode of arrival code (2.4 - 1.0.0) |
Code system of concepts specifying how the patient was brought to the healthcare facility. Used in HL7 Version 2.x messaging in the PV2 segment. |
| Modifier Edit Code (2.4 - 1.0.0) |
The OPPS functionality of the Integrated Outpatient Code Editor (I/OCE) software was developed for the implementation of the Medicare outpatient prospective payment system mandated by the 1997 Balanced Budget Act. CMS released the proposed OPPS rules using the Ambulatory Payment Classification (APC) system in the September 8, 1998 Federal Register. Final regulations were published in the April 7, 2000 Federal Register and the system became effective for Medicare on August 1, 2000. Used in HL7 Version 2.x messaging in the GP1 segment. The APC-based OPPS developed by CMS is the outpatient equivalent of the inpatient, DRG-based PPS. The APC system establishes groups of covered services so that the services within each group are comparable clinically and with respect to the use of resources. Hospitals are required to use HCPCS when billing for outpatient services. The OCE not only identifies individual errors but also indicates what actions should be taken and the reasons why these actions are necessary. In order to accommodate this functionality, the OCE is structured to return lists of edit numbers. This structure facilitates the linkage between the actions being taken, the reasons for the actions and the information on the claim (e.g., a specific diagnosis) that caused the action. In general, the OCE performs all functions that require specific reference to HCPCS codes, HCPCS modifiers and ICD-10-CM diagnosis codes (ICD-9-CM diagnosis codes for historical claims with From Dates prior to 10/1/2015). Since these coding systems are complex and annually updated, the centralization of the direct reference to these codes and modifiers in a single program reduces effort and reduces the chance of inconsistent processing. This is a CMS maintained list of edits: Please see the following for additional information: • https://www.cms.gov/Medicare/Coding/OutpatientCodeEdit/index.html • https://www.cms.gov/Medicare/Coding/OutpatientCodeEdit/Background.htmlC • https://www.cms.gov/Medicare/Coding/OutpatientCodeEdit/OCEQtrReleaseSpecs.html |
| Modify Indicator (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying whether the subscription is new or is being modified. Used in HL7 Version 2.x messaging in the Response Control Parameter (RCP) segment. |
| Mood Codes (2.6 - 1.0.0) |
HL7-defined code system of concepts that represent the functional state of an order. Used in HL7 Version 2.x messaging in the RXO and OBX segments. |
| NATURE OF ABNORMAL TESTING (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying the nature of an abnormal test. Used in HL7 Version 2.x messaging in the OBX segment. |
| NATURE OF TEST/OBSERVATION (2.2 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Name Assembly Order (2.4 - 1.0.0) |
Code system of concepts specifying the preferred display order of the components of this person name. Used in HL7 Version 2.x messaging in the PPN, XCN and XPN segments. |
| Name Representation (2.3 - 1.0.0) |
HL7-defined cdoe system of concepts that provide an indication of the kind of representation provided by a name or address, but does not necessarily specify the character sets used for the data. It is used to provides hints for a receiver, so it can make choices regarding what it has been sent and what it is capable of displaying. |
| Name Type (2.3 - 1.0.0) |
HL7-defined code system of concepts for types of names for persons. |
| Name Type (2.7 - 1.0.0) |
HL7-defined code system of concepts for types of names for persons. Used in HL7 Version 2.x messaging in the XPN, PPN, XCN, PID and MRG segments. |
| Name Type (2.8 - 1.1.0) |
HL7-defined code system of concepts for types of names for persons. Used in HL7 Version 2.x messaging in the XPN, PPN, XCN, PID and MRG segments. |
| Name type (2.3.1 - 1.1.0) |
HL7-defined code system of concepts for types of names for persons. |
| Name type (2.4 - 1.2.0) |
HL7-defined code system of concepts for types of names for persons. |
| Name type (2.6 - 1.3.0) |
HL7-defined code system of concepts for types of names for persons. |
| Nature of Abnormal Testing (2.5 - 1.1.0) |
HL7-defined code system of concepts specifying the nature of an abnormal test. Used in HL7 Version 2.x messaging in the OBX segment. |
| Nature of Challenge (2.3 - 1.0.0) |
HL7-defined code system of concepts used to further describe an observation definition that is characterized as a challenge observation. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Network Source Type (2.3 - 1.0.0) |
HL7-defined code system of concepts used to specify the type of facility. Used in HL7 Version 2.x messaging in the Facility (FAC) segment. |
| Newborn Code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify whether the baby was born in or out of a specified facility. Used in HL7 Version 2 messaging in the ABS segment. |
| Non-Subject Consenter Reason (2.5 - 1.0.0) |
HL7-defined code system of concepts used to specify a reason consent was granted by a person other than the subject of the consent. Used in the Consent (CON) segment in HL7 Version 2.x messaging. |
| Notify Clergy Code (2.5 - 1.0.0) |
Code system of concepts specifying whether the clergy should be notified. Used in HL7 Version 2 messaging in the PV2 segment. |
| OBSERVATION RESULT STATUS (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. Used in HL7 Version 2.x messaging in the OBX segment. |
| OBSERVATION RESULT STATUS CODES INTERPRETATION (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. Used in HL7 Version 2.x messaging in the OBX segment. |
| OCE Edit Code (2.4 - 1.0.0) |
Code system of concepts specifying the action to be taken during reimbursement calculations. Used in HL7 Version 2.x messaging in the GP2 segment. |
| ORDER CONTROL (2.1 - 1.0.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| ORDER CONTROL (2.2 - 1.1.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| Observation Result Handling (2.5 - 1.0.0) |
Code system of concepts 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. Used in HL7 Version 2.x messaging in the OBR segment. |
| Observation Result Handling (2.7.1 - 1.1.0) |
Code system of concepts 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. Used in HL7 Version 2.x messaging in the OBR segment. |
| Observation Result Status Codes Interpretation (2.3 - 1.2.0) |
HL7-defined code system of concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. Used in HL7 Version 2.x messaging in the OBX segment. |
| Observation Sub-Type (2.8.2 - 1.0.0) |
HL7-defined code system of concepts specifying the observation sub-type. Used in HL7 Version 2.x messaging in the OBX segment. |
| Observation Sub-Type (2.9 - 1.1.0) |
HL7-defined code system of concepts specifying the observation sub-type. Used in HL7 Version 2.x messaging in the OBX segment. |
| Observation Type (2.8.2 - 1.0.0) |
HL7-defined code system of concepts specifying types of observations to enable systems to distinguish between observations sent along with an order, versus observations sent as the result to an order. Used in HL7 Version 2.x messaging in the OBX segment. |
| Observation result status codes interpretation (2.3.1 - 1.3.0) |
HL7-defined code system of concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. Used in HL7 Version 2.x messaging in the OBX segment. |
| Observation result status codes interpretation (2.6 - 1.4.0) |
HL7-defined code system of concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. Used in HL7 Version 2.x messaging in the OBX segment. |
| Occurrence code (2.3.1 - 1.0.0) |
National Uniform Billing Committee (NUBC) UB-04 Data Specifications Manual, UB form locator 31 - 34, Occurrence Codes and Amounts - code and associated date defining a significant event relating to the bill that may affect payer processing the claim. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the OCD segment. Updated by NUBC annually; see the coding instructions for more detail. |
| Occurrence span (2.3.1 - 1.0.0) |
HL7-defined code system of concepts specifying a National Uniform Billing Committee (NUBC) code that identifies an event that relates to the payment of a claim. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the Occurrence Span Code and Date (OSP) value. Updated by NUBC annually; see the coding instructions for more detail. |
| Online Verification Result (2.9 - 1.0.0) |
Code values used to indicate the result of an online verification of insurance data. |
| Online Verification Result Error Code (2.9 - 1.0.0) |
Code values representing a type of error from a failed operation to perform online verification of insurance data. |
| Order Control Code (2.3 - 1.2.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| Order Control Code Reason (2.9 - 1.0.0) |
HL7-defined code system of concepts that describe reasons for the chosen order control codes. Used in HL7 Version 2 messaging in the ORC segment. |
| Order Control Codes (2.8 - 1.6.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| Order Status (2.1 - 1.0.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the ORC segment. |
| Order Status (2.2 - 1.1.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the ORC segment. |
| Order Status (2.3 - 1.2.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the ORC segment. |
| Order Status Modifier (2.9 - 1.0.0) |
HL7-defined code system of concepts used to further define the status identified in ORC-5. Used in HL7 Version 2 messaging in the ORC segment. |
| Order Type (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying whether the order is to be executed in an inpatient setting or an outpatient setting. Used in HL7 Version 2.x messaging in the ORC segment. |
| Order control codes (2.3.1 - 1.3.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| Order control codes (2.5 - 1.4.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| Order control codes (2.6 - 1.5.0) |
HL7-defined code system of concepts 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. Used in Version 2.x messaging of orders in the ORC segment. |
| Organ Donor (2.3 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Patient Visit - Additional Information ( PV2) and Patient Additional Demographic (PD1) segments. |
| Organ donor (2.3.1 - 1.1.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Patient Visit - Additional Information ( PV2) and Patient Additional Demographic (PD1) segments. |
| Organ donor code (2.4 - 1.2.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Patient Visit - Additional Information ( PV2) and Patient Additional Demographic (PD1) segments. |
| Organizational Name Type (2.3 - 1.0.0) |
Code system of concepts used to specify the type of name for an organization i.e., legal name, display name. Used in HL7 Version 2.x messaging in the XON and PD1 segments. |
| Outlier Type (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify a Diagnostic Resource Group Payor. US Realm. |
| Outlier Type (2.3.1 - 1.0.0) |
HL7-defined code system of concepts specifying the type of outlier (i.e. period of care beyond DRG-standard stay in facility) that has been paid. Used in HL7 Vesrion 2.x messaghing in the DRG segment. |
| Overall Claim Disposition Code (2.4 - 1.0.0) |
Code system of concepts specifying the final status of the claim. Used in HL7 Version 2.x messaging in the GP1 segment. |
| Override (2.3 - 1.0.0) |
Code system of concepts used to define whether a Charge Description Master description may be overridden or if it must be overridden. Used in HL7 Version 2.x messaging in the CDM and PRC segments. |
| Override Type (2.5 - 1.0.0) |
Code system of concepts used to specify what type of override can be used to override the specific error identified. Used in HL7 Version 2 messaging in the ERR and OVR segments. |
| PCA Type (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the type of PCA. Used in HL7 Version 2.x messaging in the RXV segment. |
| PENALTY TYPE (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify whether the amount is currency or a percentage. Used in HL7 Version 2.x messaging in the MOP segment. |
| POLICY TYPE (2.2 - 1.0.0) |
Code system of concepts which specify the policy type. Used in HL7 Version 2.x messaging in the PTA segment. |
| PRECERTIFICATION PATIENT TYPE (2.2 - 1.0.0) |
Code system of concepts which specify the category or type of patient for which this certification is requested. Used in HL7 Version 2.x messaging in the ICD segment. |
| PRIORITY (COMPONENT 6 QTY/TIMING[735]) (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying the allowed priorities for obtaining the specimen. Used in HL7 Version 2.x messaging in the OM4 segment. |
| PRIORITY (COMPONENT 6 QTY/TIMING[735]) (2.2 - 1.1.0) |
HL7-defined code system of concepts specifying the allowed priorities for obtaining the specimen. Used in HL7 Version 2.x messaging in the OM4 segment. |
| PROCEDURE PRACTITIONER TYPE (2.2 - 1.0.0) |
HL7-defined table of concepts which specify the different types of practitioners associated with this procedure. This set of codes is known to be incomplete. Note that as of v2.6, this table and the field(s) it was used in was replaced by table 443 used in the ROL segment. Used in Version 2.x messaging in the PR1 segment, but was discontinued as of 2.6; usage replaced with code system 2.16.840.1.113883.18.283 providerRole. |
| PROCESSING ID (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify whether the message is part of a production, training or debugging system. Used in HL7 Version 2.x messaging in the PT datatype. |
| PROCESSING PRIORITY (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify one or more available priorities for performing the observation or test. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Package (2.6 - 1.0.0) |
Code system of concepts 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. Used in HL7 Version 2.x messaging in the PKG segment. |
| Packaging Status Code (2.4 - 1.0.0) |
Code system of concepts specifying the packaging status of the service. Used in HL7 Version 2.x messaging in the GP2 segment. |
| Participation (2.7 - 1.0.0) |
HL7-defined code system of concepts 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.). Used in HL7 Version 2.x messaging in the PRT segment. |
| Participation (2.8 - 1.1.0) |
HL7-defined code system of concepts 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.). Used in HL7 Version 2.x messaging in the PRT segment. |
| Participation (2.8.2 - 1.2.0) |
HL7-defined code system of concepts 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.). Used in HL7 Version 2.x messaging in the PRT segment. |
| Participation (2.9 - 1.3.0) |
HL7-defined code system of concepts 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.). Used in HL7 Version 2.x messaging in the PRT segment. |
| Patient Class (2.1 - 1.0.0) |
Code system of concepts used by systems to categorize patients by site in HL7 Version 2.x interfaces in the PV1 segment. |
| Patient Class (2.2 - 1.1.0) |
Code system of concepts used by systems to categorize patients by site in HL7 Version 2.x interfaces in the PV1 segment. |
| Patient Class (2.4 - 1.2.0) |
Code system of concepts used by systems to categorize patients by site in HL7 Version 2.x interfaces in the PV1 segment. |
| Patient Location Type (2.3 - 1.0.0) |
Code system of concepts used to identify the kind of location described in the location definition. Used in HL7 Version 2.x messaging in the LOC segment. |
| Patient Outcome (2.3 - 1.0.0) |
HL7-defined code system of concepts used to describe the overall state of a patient as a result of patient care. Used in HL7 Version 2.x messaging in the PEO segment. |
| Patient Results Release Categorization Scheme (2.7 - 1.0.0) |
HL7-defined code system of concepts specifying the scheme for the patient results release categorization. Used in HL7 Version 2.x messaging in the OBX segment. |
| Patient condition code (2.4 - 1.0.0) |
Code system of concepts 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. Used in HL7 Version 2.x messaging in the PV2 segment. |
| Patient’s relationship to insured (2.3.1 - 1.0.0) |
Code system of concepts used to specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the Insurance Additional Information (IN2) segment. |
| Payee Relationship to Invoice (2.6 - 1.0.0) |
Code system of concepts used to specify the relationship to the invoice for Person Payee Types. Used in the Payee Information (PYE) segment in HL7 Version 2.x messaging. |
| Payee Type (2.6 - 1.0.0) |
Code system of concepts used to specify the type of payee (e.g., organization, person). Used in the Payee Information (PYE) segment in HL7 Version 2.x messaging. |
| Payment Adjustment Code (2.4 - 1.0.0) |
Code system of concepts specifying any payment adjustment due to drugs or medical devices. Used in HL7 Version 2.x messaging in the GP2 segment. |
| Payment Method Code (2.6 - 1.0.0) |
Code system of concepts used to specify the method for the movement of payment. Used in the Payment Information (PMT) segment in HL7 Version 2.x messaging. |
| Person location type (2.4 - 1.0.0) |
Code system of concepts specifying the categorization of the person’s location. Used in HL7 Version 2.x messaging datatypes that contain location identifiers such as Person Location (PL), Location with address variation (LA) and Name with date and location (NDL). |
| Pharmacy Order Types (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying the general category of pharmacy order which may be used to determine the processing path the order will take. Used in HL7 Version 2.x messaging in the RXO, RXE, RXD, RXG and RXA segments. |
| Phlebotomy Issue (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the phlebotomy issue. Used in HL7 Version 2.x messaging in the DON segment. |
| Phlebotomy Status (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the status of the phlebotomy. Used in HL7 Version 2.x messaging in the DON segment. |
| Practitioner ID number type (2.3 - 1.0.0) |
Code system of concepts used to specify the type of number used for the practitioner identification. Used in HL7 Version 2.x messaging in the Practitioner License or Other ID Number (PLN) value as well as the Provider Data (PRD) and Contact Data (CTD)segments. |
| Practitioner ID number type (2.5 - 1.1.0) |
Code system of concepts used to specify the type of number used for the practitioner identification. Used in HL7 Version 2.x messaging in the Practitioner License or Other ID Number (PLN) value as well as the Provider Data (PRD) and Contact Data (CTD)segments. |
| Practitioner Organization Unit Type (2.4 - 1.0.0) |
Code system of concepts specifying the classification of the organization unit. Used in HL7 Version 2.x messaging in the ORG segment. |
| Practitioner Organization Unit Type (2.5 - 1.1.0) |
Code system of concepts specifying the classification of the organization unit. Used in HL7 Version 2.x messaging in the ORG segment. |
| Precaution code (2.4 - 1.0.0) |
Code system of concepts specifying non-clincal precautions that need to be taken with the patient. Used in HL7 Version 2.x messaging in the PV2 segment. |
| Precision (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Used in HL7 Version 2 messaging in the TS datatype. Note deprecated in 2.5.1 and retained only for backward compatibility, as the datatypes and architecture for the degree of precision for timestamps was changed. |
| Preferred Method Of Contrct (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying which of a group of multiple phone numbers is the preferred method of contact for this person. Used in HL7 Version 2.x messaging in the STF, PRD, and CTD segments. |
| Preferred Specimen/Attribute Status (2.8 - 1.0.0) |
HL7-defined code system of concepts that indicate whether a Specimen/Attribute is Preferred or Alternate for collection of a particular specimen. Used in HL7 Version 2.x messaging in Master Files (OM4 segment) to characterize information about specimens that are associated with certain observations. |
| Present On Admission (POA) Indicator (2.6 - 1.0.0) |
National Uniform Billing Committee (NUBC) UB-04 Data Specifications Manual, UB form locator 67, Present on Admission (POA) Indicator. Code identifying a diagnosis that was present at the time the order for inpatient admission occurs. POA indicator is assigned to all diagnoses as defined in Appendix I of the “ICD-9-CM Official Guidelines for Coding and Reporting” or “ICD-10-CM Official Guidelines for Coding and Reporting (appropriate to the ICD revision used). The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the DG1 segment. |
| Price Type (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify the intent for the dollar amount on a pricing transaction. Used in HL7 Version 2.x messaging in the CP datatype. |
| Primary Observer's Qualification (2.3 - 1.0.0) |
HL7-defined code system of concepts used to provide a general description of the kind of health care professional who provided the primary observation. Used in HL7 Version 2.x messaging in the PEO and PCR segments. |
| Primary key value type (2.3.1 - 1.0.0) |
HL7-defined code system of concepts used to specify the type for the master file record identifier. Used in HL7 Version 2.x messaging in the Master File Entry (MFE) segment. |
| Primary key value type (2.6 - 1.1.0) |
HL7-defined code system of concepts used to specify the type for the master file record identifier. Used in HL7 Version 2.x messaging in the Master File Entry (MFE) segment. |
| Privacy Level (2.3 - 1.0.0) |
Code system of concepts used to identify the level of privacy a patient will be afforded when assigned to this location definition. Used in HL7 Version 2.x messaging in the LCH segment. |
| Procedure DRG type (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a procedure’s priority ranking relative to its DRG. Used in HL7 Version 2 messaging in the PR1 segment. |
| Procedure Functional Type (2.3 - 1.0.0) |
Code system of concepts used to classify a procedure. Used in HL7 Version 2.x messaging in the PR1 segment. |
| Procedure Practitioner Identifier Code Type (2.3 - 1.1.0) |
HL7-defined table of concepts which specify the different types of practitioners associated with this procedure. This set of codes is known to be incomplete. Note that as of v2.6, this table and the field(s) it was used in was replaced by table 443 used in the ROL segment. Used in Version 2.x messaging in the PR1 segment, but was discontinued as of 2.6; usage replaced with code system 2.16.840.1.113883.18.283 providerRole. |
| Procedure priority (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify the significance or priority of a procedure code. Used in HL7 Version 2 messaging in the PR1 segment. Note that this is a post-coordinated code system, where additional ordinal priorities are created by incrementing the numericinteger code value as needed. Only the first 2 ordinal values are predefined in the code system. |
| Process Interruption Reason (2.8 - 1.0.0) |
HL7-defined code system of concepts specifying the reason for the process interruption. Used in HL7 Version 2.x messaging in the DON segment. |
| Processing Consideration Codes (2.6 - 1.0.0) |
Code system of concepts used to specify special processing requested of Payer for this Product/Service Line Item (e.g., hold until paper supporting documentation is received by Payer). Used in the Product/Service Line Item (PSL) segment in HL7 Version 2.x messaging. |
| Processing Mode (2.3 - 1.0.0) |
HL7-defined code system of concepts that indicate an archival process or an initial load process. Used in HL7 Version 2.x messaging in the PT datatype. |
| Processing Type (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying the processing type that applies to the test code. If this attribute is omitted, then regular production is the default. Used in HL7 Version 2.x messaging in the Test Code Configuration (TCC) segment. |
| Processing mode (2.3.1 - 1.1.0) |
HL7-defined code system of concepts that indicate an archival process or an initial load process. Used in HL7 Version 2.x messaging in the PT datatype. |
| Product Source (2.3 - 1.0.0) |
HL7-defined code system of concepts used to describe the evaluation state of a product identified in an incident. Used in HL7 Version 2.x messaging in the PCR segment. |
| Product/Service Status (2.6 - 1.0.0) |
Code system of concepts used to specify the processing status for the Product/Service Code. Used in the Product/Service Line Item (PSL) segment in HL7 Version 2.x messaging. |
| Product/Services Clarification Codes (2.6 - 1.0.0) |
Code system of concepts used to specify the Product/Service Code. Used in the Product/Service Line Item (PSL) segment in HL7 Version 2.x messaging. |
| Production class Code (2.4 - 1.0.0) |
Code system of concepts specifying the code and/or text indicating the primary use for which the living subject was bred or grown. Used in HL7 Version 2.x messaging in the PID segment. |
| Protection Code (2.6 - 1.0.0) |
Code system of concepts specifying that an address needs to be treated with special care or sensitivity. Used in HL7 Version 2.x messaging in the XAD and XTN segments. |
| Provider Adjustment Reason Code (2.6 - 1.0.0) |
Code system of concepts used to specify the reason for this adjustment. Used in the Adjustment (ADJ) segment in HL7 Version 2.x messaging. |
| Provider Role (2.4 - 1.0.0) |
Code system of concepts specifying the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). Used in HL7 Version 2.x messaging in the ROL segment. |
| Provider Role (2.6 - 1.1.0) |
Code system of concepts specifying the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). Used in HL7 Version 2.x messaging in the ROL segment. |
| Provider Role (2.7 - 1.2.0) |
Code system of concepts specifying the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). Used in HL7 Version 2.x messaging in the ROL segment. |
| Provider billing (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying how provider services are billed. Used in HL7 Version 2.x messaging in the PRA segment. |
| Purge Status (2.3 - 1.0.0) |
Code system of concepts used to define the state of a visit relative to its place in a purge workflow. Used in HL7 Version 2.x messaging in the PV2 segment. |
| QUANTITY LIMITED REQUEST (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify 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. Used in HL7 Version 2.x messaging in the RCP segment. |
| QUANTITY LIMITED REQUEST (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify 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. Used in HL7 Version 2.x messaging in the RCP segment. |
| QUERY FORMAT CODE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify which of several types of formats for data to be returned in response to a query. Used in HL7 Version 2 messaging in the EQL segment. |
| QUERY FORMAT CODE (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify which of several types of formats for data to be returned in response to a query. Used in HL7 Version 2 messaging in the EQL segment. |
| QUERY PRIORITY (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify a time frame in which a querry response is expected. Used in HL7 Verson 2.x messaging in the RCP segment. |
| QUERY RESULTS LEVEL (2.1 - 1.0.0) |
HL7-defined code system of concepts which are used to control level of detail in query results. Used in HL7 Version 2 messaging in the URD segment. |
| QUERY RESULTS LEVEL (2.2 - 1.1.0) |
HL7-defined code system of concepts which are used to control level of detail in query results. Used in HL7 Version 2 messaging in the URD segment. |
| Quantity Method (2.3 - 1.0.0) |
HL7-defined code system of concepts used to specify the method by which the quantity distributed is measured. Used in HL7 Version 2.x messaging in the Product Summary Header (PSH) segment. |
| Quantity limited request (2.4 - 1.2.0) |
HL7-defined code system of concepts which specify 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. Used in HL7 Version 2.x messaging in the RCP segment. |
| Query Response Status (2.3 - 1.0.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the QAK segment. |
| Query response status (2.3.1 - 1.1.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the QAK segment. |
| Query/Response Format Code (2.3 - 1.2.0) |
HL7-defined code system of concepts which specify which of several types of formats for data to be returned in response to a query. Used in HL7 Version 2 messaging in the EQL segment. |
| REPORT PRIORITY (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify the priority associated with a report or update run using a query. Used in HL7 Version 2 messaging in the URD segment. |
| REPORTIN PRIORITY (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority. Used in HL7 Version 2.x messaging in the OM1 segment. |
| RESPONSE FLAG (2.1 - 1.0.0) |
HL7-defined code system of concepts allowing the placer (sending) application to determine the amount of information to be returned from the filler. Used in HL7 Version 2.x messaging in the ORC segment. |
| RESPONSE FLAG (2.2 - 1.1.0) |
HL7-defined code system of concepts allowing the placer (sending) application to determine the amount of information to be returned from the filler. Used in HL7 Version 2.x messaging in the ORC segment. |
| RESULT STATUS - OBR (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| RESULT STATUS - OBR (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| ROUTE (2.1 - 1.0.0) |
HL7-defined code system of concepts that indicate a means of administrating a medication dose. Used in HL7 Version 2 messaging in the RX1 segment (which was withdrawn after version 2.2). As of HL7 version 2.3, it was replaced by 2.16.840.1.113883.18.80 routeOfAdministration and 2.16.840.1.113883.18.83 administrationMethod. Used in the RX1 segment. |
| ROUTE OF ADMINISTRATION (2.2 - 1.0.0) |
Code system of concepts which specify the route of administration. Used in HL7 Version 2.x messaging in the RXR segment. |
| RX COMPONENT TYPE (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify the RX component type. Used in HL7 Version 2.x messaging in the RXC segment. |
| Reason for Study (2.9 - 1.0.0) |
HL7-defined code system of concepts that provide additional information to the universal service identifier on why a test, study or review was ordered. Initial values are to support the IHE LCC LAB-7 transaction. |
| Record Level Event Code (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying an action for a master file record. Used in HL7 Version 2.x messaging in the MFE segment. |
| Recreational drug use code (2.4 - 1.0.0) |
Code system of concepts specifying what recreational drugs the patient uses. Used in HL7 Version 2.x messaging in the PV2 segment. |
| Referral Category (2.3 - 1.0.0) |
Code system of concepts used to describe the patient care setting where a referral should take place. Used in HL7 Version 2.x messaging in the RF1 segment. |
| Referral Disposition (2.3 - 1.0.0) |
Code system of concepts used to identify the expected response from the healthcare professional receiving a referral. Used in HL7 Version 2.x messaging in the RF1 segment. |
| Referral Priority (2.3 - 1.0.0) |
Code system of concepts used to designate the urgency of a referral. Used in HL7 Version 2.x messaging in the RF1 segment. |
| Referral Reason (2.3 - 1.0.0) |
Code system of concepts used to specify the reason for which the referral will take place. Used in HL7 Version 2.x messaging in the Referral Information (RF1) segment. |
| Referral Status (2.3 - 1.0.0) |
Code system of concepts used to define the state of a referral. Used in HL7 Version 2.x messaging in the RF1 segment. |
| Referral Type (2.3 - 1.0.0) |
Code system of concepts used to identify the general category of healthcare professional desired to satisfy a referral. Used in HL7 Version 2.x messaging in the RF1 segment. |
| Reimbursement Action Code (2.4 - 1.0.0) |
Code specifying the action to be taken during reimbursement calculations. In the US, this field is defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the GP2 segment. |
| Reimbursement type code (2.4 - 1.0.0) |
Code system of concepts specifying the fee schedule reimbursement type applied to the line item. Used in HL7 Version 2.x messaging in the GP2 segment. |
| Relatedness Assessment (2.3 - 1.0.0) |
HL7-defined code system of concepts used to provide an estimate of whether an issue with a product was the cause of an event. Used in HL7 Version 2.x messaging in the PCR segment. |
| Relational Conjunction (2.3 - 1.0.0) |
HL7-defined code system of concepts used with relationalOperator values to group more than one segment field name. Used in HL7 Version 2.x messaging in the QSC segment. |
| Relational Operator (2.3 - 1.0.0) |
HL7-defined code system of concepts used to define the relationship between HL7 segment field names identified in a query construct. Used in HL7 Version 2.x messaging in the QSC segment. |
| Relationship (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying an actual personal relationship that the next of kin/associated party has to a patient. Used in HL7 Version 2.x messaging in the NK1 and IN1 segments. |
| Relationship Modifier (2.3 - 1.0.0) |
HL7-defined code system of concepts used in an observation definition to describe the subject of an observation in relation to a patient. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Relationship Type (2.9 - 1.0.0) |
HL7-defined code system of concepts that identify the type of relationship identified by Relationship Instance Identifier (REL-3) that is established between the Source Information Instance (REL-4) and the Target Information Instance (REL-5). |
| Relevant Clinicial Information (2.7.1 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the OBR segment. |
| Religion (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying a person’s religion. Used in HL7 Version 2.x messaging in the PID segment. |
| Religion (2.4 - 2.0.0) |
Code system of concepts specifying a person’s religion. Used in HL7 Version 2.x messaging in the PID segment. |
| Religion (2.6 - 2.1.0) |
Code system of concepts specifying a person’s religion. Used in HL7 Version 2.x messaging in the PID segment. |
| Remote Control Command (2.8 - 1.1.0) |
Code system of concepts that identify the comment the component is to initiate. Used in the Equipment Command (ECD) and Interaction Status Detail (ISD) segments in HL7 Version 2.x messaging. |
| Remote control command (2.4 - 1.0.0) |
Code system of concepts that identify the comment the component is to initiate. Used in the Equipment Command (ECD) and Interaction Status Detail (ISD) segments in HL7 Version 2.x messaging. |
| Reorder Theory Codes (2.6 - 1.0.0) |
Code system of concepts that identify the calculation method used to determine the resupply schedule. Used in HL7 Version 2.x messaging in the IVT segment. |
| Repeat pattern (2.4 - 1.0.0) |
Code system of concepts used to specify the interval between repeated services. Used in HL7 Version 2.x messaging in the RI datatype and RPT segment. |
| Report Source (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify where a report sender learned about an event. Used in HL7 Version 2.x messaging in the PES segment. |
| Report Timing (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify the time span of a report or the reason for a report sent to a regulatory agency. Used in HL7 Version 2.x messaging in the PES segment. |
| Report Type Code (2.3 - 1.0.0) |
Code system of concepts used to identify the kind of patient document. Used in HL7 Version 2.x messaging in the TXA segment. |
| Reported To (2.3 - 1.0.0) |
HL7-defined code system of concepts used to identify the type of entity to which the even has been reported. Used in HL7 Version 2.x messaging in the PES segment. |
| Response Level (2.2 - 1.0.0) |
HL7-defined code system of concepts specifying application response levels defined for a given Master File Message at the MFE segment level, and used for MFN-Master File Notification message. Specifies additional detail (beyond MSH-15 - Accept Acknowledgment Type and MSH-16 - Application Acknowledgment Type) for application-level acknowledgment paradigms for Master Files transactions. Used in HL7 Version 2.x messaging in the MFI segment. |
| Response Modality (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying the timing and grouping of the response message(s). Used in HL7 Version 2.x messaging in the Response Control Parameter (RCP) segment. |
| Result Status (2.3 - 1.2.0) |
HL7-defined code system of concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| Result Status (2.9 - 1.3.0) |
HL7-defined code system of concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment. |
| Revenue code (2.4 - 1.0.0) |
Code system of concepts specifying a revenue code as specified in the . National Uniform Billing Committee (NUBC) UB-04 manual, UB form locator 42, the service line revenue code. These are claim codes indicating the identifying number for the product or service provided. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the Revenue Code (GP1) value. Updated by NUBC annually; see the coding instructions for more detail. |
| Risk Codes (2.5 - 1.0.0) |
Code system of concepts specifying any known or suspected specimen hazards, e.g., exceptionally infectious agent or blood from a hepatitis patient. Used in HL7 Version 2.x messaging in the SPM and PAC segments. |
| Risk Management Incident Code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a type of incident that occurs during a patient’s stay. Used in HL7 Version 2 messaging in the RMI segment. |
| Role Executing Physician (2.6 - 1.0.0) |
Code system of concepts specifying the account role of the physician, for example, only billing for the professional part, the technical part or both. Used in HL7 Version 2.x messaging in the PSL segment. |
| Room Type (2.2 - 1.0.0) |
Code system of concepts which specify the room type. Used in HL7 Version 2.x messaging in the RMC segment. |
| Root Cause (2.8 - 1.0.0) |
Code system of concepts specifying the root cause. Used in HL7 Version 2.x messaging in the OBX segment. |
| Route of Administration (2.3 - 1.1.0) |
Code system of concepts which specify the route of administration. Used in HL7 Version 2.x messaging in the RXR segment. |
| Route of Administration (2.8 - 1.3.0) |
Code system of concepts which specify the route of administration. Used in HL7 Version 2.x messaging in the RXR segment. |
| Route of administration (2.3.1 - 1.2.0) |
Code system of concepts which specify the route of administration. Used in HL7 Version 2.x messaging in the RXR segment. |
| SOURCE OF COMMENT (2.1 - 1.0.0) |
HL7-defined code system of concepts which are used to specify the source of a comment. Used in HL7 Version 2.x messaging in the NTE segment. |
| SOURCE OF COMMENT (2.2 - 1.1.0) |
HL7-defined code system of concepts which are used to specify the source of a comment. Used in HL7 Version 2.x messaging in the NTE segment. |
| SOURCE OF SPECIMEN (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in code system 2.16.840.1.133883.18.311 specimenType and code system 2.16.840.1.133883.18.312 specimenCollectionMethod as of version 2.5 and thereafter. |
| SOURCE OF SPECIMEN (2.2 - 2.0.0) |
HL7-defined code system of concepts which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in code system 2.16.840.1.133883.18.311 specimenType and code system 2.16.840.1.133883.18.312 specimenCollectionMethod as of version 2.5 and thereafter. |
| STOCK LOCATION (2.1 - 1.0.0) |
Code system of concepts specifying a stock location for older Version 2 messaging systems; not used after version 2.2 of the Standard. |
| SUBSTITUTION STATUS (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify the substitution status. Used in HL7 Version 2.x messaging in the RXE, RXD, and RXG segments. |
| Security Check Scheme (2.7 - 1.0.0) |
HL7-defined code system of concepts specifying the scheme for the security check. Used in HL7 Version 2.x messaging in the CX datatypes and PPN and XCN segments. |
| Segment Action Code (2.3 - 1.0.0) |
HL7-defined code system of concepts specifying 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). Used in HL7 Version 2.x messaging in the RXA, RXV, LCH, IAM, ARV, IN1 and OH1 segments. |
| Segment Group (2.6 - 1.0.0) |
HL7-defined code system of concepts specifying the optional segment groups which are to be included in the response. This is a repeating field, to accommodate inclusion of multiple segment groups. The default for this field, not present, means that all relevant groups are included. Used in HL7 Version 2.x messaging in the Response Control Parameter (RCP) segment. |
| Segment action code (2.6 - 1.1.0) |
HL7-defined code system of concepts specifying 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). Used in HL7 Version 2.x messaging in the RXA, RXV, LCH, IAM, ARV, IN1 and OH1 segments. |
| Sensitivity to Causative Agent Code (2.7 - 1.1.0) |
Code system of concepts specifying the reason the patient should not be exposed to a substance. Used in HL7 Version 2.x messaging in the IAM segment. |
| Sensitivity to Causative Agent code (2.4 - 1.0.0) |
Code system of concepts specifying the reason the patient should not be exposed to a substance. Used in HL7 Version 2.x messaging in the IAM segment. |
| Sequence condition (2.5 - 1.0.0) |
HL7-defined code system of concepts that identify whether sequence conditions or a repeating cycle of orders is defined. This is part of the Order Sequence Definition used in HL7 Version 2.x messaaging in the OSD datatype. |
| Sequence/Results Flag (2.5 - 1.0.0) |
HL7-defined code system of concepts used to specify the sequencing relationship between the current service request and the related service request(s) specified in this TQ2 segment. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging. |
| Sequencing (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying how the field or parameter will be sorted and, if sorted, whether the sort will be case sensitive (the default) or not. Used in HL7 Version 2.x messaging in the Sort Order (SRT) value. |
| Service Request Relationship (2.5 - 1.0.0) |
HL7-defined code system of concepts used to specify an additional or alternate relationship between this service request and other service requests. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging. |
| Severity of illness code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify the ranking of a patient’s illness. Used in HL7 Version 2 messaging in the ABS segment. |
| Sex (2.1 - 1.0.0) |
HL7-defined code system of concepts specifying a person’s sex. |
| Sexual Orientation (2.9.1 - 1.0.0) |
Snomed CT |
| Shipment Status (2.7 - 1.0.0) |
HL7-defined code system of concepts specifying the status of the shipment. Used in HL7 Version 2.x messaging in the SHP segment. |
| Side of body (2.6 - 1.0.0) |
Code system of concepts specifying the side of the body (“left” or “right”). Used in HL7 Version 2.x messaging in the PSL segment. |
| Signatory's Relationship to Subject (2.5 - 1.0.0) |
Code system of concepts specifying the relationship of the consenter to the subject. Used in HL7 Version 2 messaging in the CON segment. |
| Signature Code (2.5 - 1.0.0) |
Code system of concepts that indicate how a patient/subscriber authorization signature is obtained and how it is being retained by a provider. Used in HL7 Version 2.x messaging in the IN1 segment. |
| Special Handling Code (2.5 - 1.1.0) |
Code system of concepts describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing. Used in HL7 Version 2.x messaging in the SPM, SAC, PAC and OM4 segments. |
| Special handling considerations (2.4 - 1.0.0) |
Code system of concepts describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing. Used in HL7 Version 2.x messaging in the SPM, SAC, PAC and OM4 segments. |
| Specialty Type (2.3 - 1.0.0) |
Code system of concepts used to identify the specialty of the care professional who is supported when using this location definition. Used in HL7 Version 2.x messaging in the LDP segment. |
| Specimen Appropriateness (2.5 - 1.0.0) |
Code system of concepts specifying the suitability of the specimen for the particular planned use as determined by the filler. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Child Role (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying for child specimens the relationship between this specimen and the parent specimen. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Collection Method (2.5 - 1.0.0) |
HL7-defined code system of concepts specifying the specimen collection method. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Condition (2.5 - 1.0.0) |
Code system of concepts specifying a mode or state of being that describes the nature of the specimen. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Condition (2.8 - 1.1.0) |
Code system of concepts specifying a mode or state of being that describes the nature of the specimen. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Quality (2.5 - 1.0.0) |
Code system of concepts specifying the degree or grade of excellence of the specimen at receipt. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Reject Reason (2.5 - 1.0.0) |
HL7-defined code system of reasons a specimen may be rejected for a specified observation/result/analysis. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Role (2.5 - 1.1.0) |
HL7-defined code system of concepts that identify the role of a sample. Used in HL7 Version 2.x messaging in the Specimen (SPM) and Observation Request (OBR) segments. |
| Specimen Role (2.9 - 1.2.0) |
HL7-defined code system of concepts that identify the role of a sample. Used in HL7 Version 2.x messaging in the Specimen (SPM) and Observation Request (OBR) segments. |
| Specimen Source Codes (2.3 - 3.0.0) |
HL7-defined code system of concepts which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in code system 2.16.840.1.133883.18.311 specimenType and code system 2.16.840.1.133883.18.312 specimenCollectionMethod as of version 2.5 and thereafter. |
| Specimen Source Codes (2.5 - 4.0.0) |
HL7-defined code system of concepts which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in code system 2.16.840.1.133883.18.311 specimenType and code system 2.16.840.1.133883.18.312 specimenCollectionMethod as of version 2.5 and thereafter. |
| Specimen Type (2.5 - 1.0.0) |
HL7-defined code system of concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system 2.16.840.1.113883.18.28) which conflated specimen types and specimen collection methods. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Type (2.7 - 2.0.0) |
HL7-defined code system of concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system 2.16.840.1.113883.18.28) which conflated specimen types and specimen collection methods. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen Type (2.8.2 - 3.0.0) |
HL7-defined code system of concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system 2.16.840.1.113883.18.28) which conflated specimen types and specimen collection methods. Used in HL7 Version 2.x messaging in the SPM segment. |
| Specimen component (2.4 - 1.0.0) |
Code system of concepts that identify the specimen component, e.g., supernatant, sediment, etc. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging. |
| Specimen role (2.4 - 1.0.0) |
HL7-defined code system of concepts that identify the role of a sample. Used in HL7 Version 2.x messaging in the Specimen (SPM) and Observation Request (OBR) segments. |
| Start of Evaluation (2.3 - 1.0.0) |
HL7-defined code system of concepts that describes the status of product evaluation. Used in HL7 Version 2.x messaging in the PCR segment. |
| Status Admission (2.6 - 1.0.0) |
Code system of concepts specifying the admission status for the diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment. |
| Status Patient (2.6 - 1.0.0) |
Code system of concepts specifying whether the length of stay is normal or respectively shorter or longer than normal. Used in HL7 Version 2.x messaging in the DRG segment. |
| Status Respiration Minutes (2.6 - 1.0.0) |
Code system of concepts specifying the status of the use of the respiration minutes information for diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment. |
| Status Weight At Birth (2.6 - 1.0.0) |
Code system of concepts specifying the status of the use of the weight at birth for diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment. |
| Sterilization Type (2.6 - 1.0.0) |
Code system of concepts specifying the type of sterilization used for sterilizing the inventory supply item in the ITM segment. Used in HL7 Version 2.x messaging in the STZ segment. |
| Student Status (2.3 - 1.0.0) |
Code system of concepts used to designate whether a guarantor is a full or part time student. Used in HL7 Version 2.x messaging in the GT1, NK1 and PD1 segments. |
| Substance Status (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying the status of the inventoried item. The status indicates the current status of the substance. Used in HL7 Version 2.x messaging in the Inventory Detail (INV) segment. |
| Substance Type (2.4 - 1.0.0) |
HL7-defined code system of concepts identifying the type of substance. Used in HL7 Version 2.x messaging in the Inventory Detail (INV) segment. |
| Substitution status (2.3.1 - 1.1.0) |
HL7-defined code system of concepts which specify the substitution status. Used in HL7 Version 2.x messaging in the RXE, RXD, and RXG segments. |
| Subtype of Referenced Data (2.3 - 1.0.0) |
Code system of a subset of the media subtypes of binary data that are encoded in an ascii structure or stream. Used in Version 2 messaging ED and RP datatypes, but only in standard 2.5.1 and earlier; after that, it was recommended that the IANA media types be used instead of this short list of HL7-defined codes. More information on the standard media types and subtypes may be found at http://www.iana.org/assignments/media-types/media-types.xhtml. |
| Subtype of Referenced Data (2.3.1 - 1.1.0) |
Code system of a subset of the media subtypes of binary data that are encoded in an ascii structure or stream. Used in Version 2 messaging ED and RP datatypes, but only in standard 2.5.1 and earlier; after that, it was recommended that the IANA media types be used instead of this short list of HL7-defined codes. More information on the standard media types and subtypes may be found at http://www.iana.org/assignments/media-types/media-types.xhtml. |
| Subtype of Referenced Data (2.4 - 1.2.0) |
Code system of a subset of the media subtypes of binary data that are encoded in an ascii structure or stream. Used in Version 2 messaging ED and RP datatypes, but only in standard 2.5.1 and earlier; after that, it was recommended that the IANA media types be used instead of this short list of HL7-defined codes. More information on the standard media types and subtypes may be found at http://www.iana.org/assignments/media-types/media-types.xhtml. |
| Supplemental Service Information Values (2.9 - 1.0.0) |
HL7-defined code system of concepts which specify the 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). |
| Supplier Type (2.9 - 1.0.0) |
Code system that Identifies the type of supplier that will distribute the supply items associated to a contract number. Used in HL7 Version 2.x messaging in the CTR segment. |
| Supply Risk Codes (2.6 - 1.0.0) |
Code system of concepts specifying any known or suspected hazard associated with this material item. Used in HL7 Version 2.x messaging in the ITM segment. |
| TQ Conjunction ID (2.4 - 1.0.0) |
HL7-defined code system of concepts specifying that a second timing specification is to follow using the repeat delimiter. Used in HL7 Version 2.x messaging in the TQ1 segment. |
| TRANSPORTATION MODE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify how (or whether) to transport a patient, when applicable, for an ordered service. Used in HL7 Version 2.x messaging in the OBR segment. |
| TRAY TYPE (2.2 - 1.0.0) |
HL7-defined code system of concepts which specify whether the type of diet. Used in HL7 Version 2.x messaging in the ODT segment. |
| Tax status (2.6 - 1.0.0) |
Code system of concepts used to specify the tax status of the provider. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging. |
| Telecommunication Equipment Type (2.3 - 1.0.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the XTN segment. |
| Telecommunication Expiration Reason (2.6 - 1.0.0) |
Code system of concepts specifying the reason this contact number/email was marked as “ended”. Used in HL7 Version 2.x messaging in the XTN segment. |
| Telecommunication Use Code (2.3 - 1.0.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the XTN segment. |
| Telecommunication equipment type (2.5 - 1.1.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the XTN segment. |
| Telecommunication equipment type (2.6 - 1.2.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the XTN segment. |
| Telecommunication use code (2.3.1 - 1.1.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the XTN segment. |
| Telecommunication use code (2.6 - 1.2.0) |
HL7-defined code system of concepts 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. Used in HL7 Version 2.x messaging in the XTN segment. |
| Time Delay Post Challenge (2.3 - 1.0.0) |
HL7-defined code system of concepts used to classify an observation definition as being a component of a challenge test. Used in HL7 Version 2.x messaging in the OM1 segment. |
| Time Selection Criteria Parameter Class Codes (2.3 - 1.0.0) |
Code system of concepts used to describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling. Used in HL7 Version 2.x messaging in the SCV and APR segments. |
| Time Selection Criteria Parameter Class Codes (2.4 - 1.1.0) |
Code system of concepts used to describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling. Used in HL7 Version 2.x messaging in the SCV and APR segments. |
| Tissue Type Code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a type of tissue removed from a patient during a procedure. Used in HL7 Version 2 messaging in the PR1 segment. |
| Transaction Type (2.3 - 1.0.0) |
Code system of concepts specifying a type of financial transaction. Used in HL7 Version 2.x messaging in the FT1 segment. |
| Transaction Type (2.4 - 1.1.0) |
Code system of concepts specifying a type of financial transaction. Used in HL7 Version 2.x messaging in the FT1 segment. |
| Transfusion Adverse Reaction (2.5 - 1.0.0) |
Code system of concepts used to specify the type of adverse reaction that the recipient of the blood product experienced. Used in the Blood Product Transfusion/Disposition (BTX) segment in HL7 Version 2.x messaging. |
| Transport Arranged (2.3 - 1.0.0) |
HL7-defined code system of concepts defining whether patient transportation preparations are in place. Used in HL7 Version 2.x messaging in the OBR segment. |
| Treatment (2.4 - 1.0.0) |
Code system of concepts that identify the specimen treatment performed during lab processing. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging. |
| Triage Code (2.4 - 1.0.0) |
HL7-defined code system of concepts which specify a patient’s prioritization within the context of a transmitted abstract. Used in HL7 Version 2 messaging in the ABS segment. |
| Type Of Data (2.2 - 1.0.0) |
HL7-defined code system of concepts declaring the general type of media data that is encoded. Used in v2.5.1 interfaces and earlier, and replaced with the full set of IANA media types as a standard coding system for this after HL7 version 2.6 (see value set 2.16.840.1.113883.21.425 hl7VS-mimeTypes for HL7 table 0834 built on MIME types). More information may be found at http://www.iana.org/assignments/media-types/media-types.xhtml |
| Type of Bill Code (2.4 - 1.0.0) |
HL7 published codes from the UB92 Form Locator 4 “Type of Bill”; note that the UB codes listed are not an exhaustive or current list; refer to a UB specification for additional information. This needs review by HTA and PA/FM; this may be a value set built on external CMS codes from the UB. Used in HL7 Version 2.x messaging in the GP1 segment. |
| Type of referenced data (2.3.1 - 1.2.0) |
HL7-defined code system of concepts declaring the general type of media data that is encoded. Used in v2.5.1 interfaces and earlier, and replaced with the full set of IANA media types as a standard coding system for this after HL7 version 2.6 (see value set 2.16.840.1.113883.21.425 hl7VS-mimeTypes for HL7 table 0834 built on MIME types). More information may be found at http://www.iana.org/assignments/media-types/media-types.xhtml |
| Type of referenced data (2.4 - 1.3.0) |
HL7-defined code system of concepts declaring the general type of media data that is encoded. Used in v2.5.1 interfaces and earlier, and replaced with the full set of IANA media types as a standard coding system for this after HL7 version 2.6 (see value set 2.16.840.1.113883.21.425 hl7VS-mimeTypes for HL7 table 0834 built on MIME types). More information may be found at http://www.iana.org/assignments/media-types/media-types.xhtml |
| Universal ID Type (2.7 - 1.2.0) |
HL7-defined code system of types of UID (Universal Identifiers). Used in HL7 Version 2.x messaging HD and EI datatypes. |
| Universal ID Type (2.9 - 1.3.0) |
HL7-defined code system of types of UID (Universal Identifiers). Used in HL7 Version 2.x messaging HD and EI datatypes. |
| Universal ID type (2.3 - 1.0.0) |
HL7-defined code system of types of UID (Universal Identifiers). Used in HL7 Version 2.x messaging HD and EI datatypes. |
| Universal ID type (2.5 - 1.1.0) |
HL7-defined code system of types of UID (Universal Identifiers). Used in HL7 Version 2.x messaging HD and EI datatypes. |
| User Authentication Credential Type Code (2.6 - 1.0.0) |
HL7-defined code system of concepts specifying a type of user authentication credential. Used in HL7 Version 2.x messaging in the UAC segment. |
| VERSION CONTROL TABLE (2.1 - 1.0.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| VERSION ID (2.2 - 1.1.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Vaccines Administered (2.3 - 1.0.0) |
Code system of codes specifying the administered vaccines, and used only in HL7 releases 2.3, 2.3.1, and 2.4 of the standard. This code system was superceded when the US Centers of Disease Control began publishing the codes directly; the code system to be used now is 2.16.840.1.113883.12.292 PH_VaccinesAdministeredCVX_CDC_NIP. |
| Vaccines administered (2.3.1 - 1.1.0) |
Code system of codes specifying the administered vaccines, and used only in HL7 releases 2.3, 2.3.1, and 2.4 of the standard. This code system was superceded when the US Centers of Disease Control began publishing the codes directly; the code system to be used now is 2.16.840.1.113883.12.292 PH_VaccinesAdministeredCVX_CDC_NIP. |
| Vaccines administered (2.4 - 1.2.0) |
Code system of codes specifying the administered vaccines, and used only in HL7 releases 2.3, 2.3.1, and 2.4 of the standard. This code system was superceded when the US Centers of Disease Control began publishing the codes directly; the code system to be used now is 2.16.840.1.113883.12.292 PH_VaccinesAdministeredCVX_CDC_NIP. |
| Vaccines administered (2.6 - 0.0.) |
Table of codes specifying 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 |
| Version ID (2.3 - 1.2.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.3.1 - 1.3.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.4 - 1.4.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.5 - 1.5.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.5.1 - 1.9.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.6 - 1.6.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.7 - 1.7.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.7.1 - 1.10.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.8 - 1.8.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.9 - 1.11.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Version ID (2.9.1 - 1.12.0) |
HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment. |
| Visit Indicator (2.3 - 1.0.0) |
Code system of concepts specifying 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. Used in HL7 Version 2.x messaging in the Patient Visit (PV1) segment. |
| Visit priority code (2.4 - 1.0.0) |
Code system of concepts used to define a relative level of urgency applied to a patient visit. Used in HL7 Version 2.x messaging in the PV2 segment. |
| Visit user code (2.4 - 1.0.0) |
Code system of concepts which specify 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. Used in HL7 Version 2.x messaging in the PV2 segment. |
| WHEN TO CHARGE (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify codes for an event precipitating/triggering a charge activity. Used in HL7 Version 2.x messaging in the CCD and BLG segments. |
| WHIHC DATE/TIME STATUS QUALIFIER (2.2 - 1.0.0) |
HL7-defined code system of concepts that specify the status type of objects selected in a date range. Used in HL7 Vesion 2 messaging in the QRF segment. |
| What Subject Filter (2.1 - 1.0.0) |
HL7-defined code system of concepts which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. Used in HL7 Version 2 messaging in the URD segment. |
| What Subject Filter (2.2 - 1.1.0) |
HL7-defined code system of concepts which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. Used in HL7 Version 2 messaging in the URD segment. |
| What Subject Filter (2.3 - 1.2.0) |
HL7-defined code system of concepts which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. Used in HL7 Version 2 messaging in the URD segment. |
| What subject filter (2.3.1 - 1.3.0) |
HL7-defined code system of concepts which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. Used in HL7 Version 2 messaging in the URD segment. |
| What subject filter (2.4 - 1.4.0) |
HL7-defined code system of concepts which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. Used in HL7 Version 2 messaging in the URD segment. |
| Which date/time qualifier (2.3.1 - 1.1.0) |
HL7-defined code system of concepts that specify a type of date referred to in query specifications. Used in HL7 Version 2 messaging in the QRF segment. |