Define the content of the vocabulary domain as a codesystem: http://terminology.hl7.org/v2plusvocab/CodeSystem/ConceptDomain-v2.2
List of all concept domains that are used within this HL7 v2.2 version to designate the semantic concepts for coded elewments.
example value(s) for a concept domain that provides some example values
type of vocabulary behind this concept: ConceptDomain (only), ValueSet and/or CodeSystem
The domain of possible values for a patient's sex.
The domain of possible values for a person's marital (civil/legal) status.
The domain of possible values for the trigger event for Version 2.x interface messages.
The domain of possible values that systems to categorize patients by site in HL7 Version 2.x interfaces.
The domain of possible values for the patient's race.
The domain of possible values for a person's religion.
The domain of possible values for the circumstances under which the patient was or will be admitted.
The domain of possible values for acknowledgment codes used in Version 2.x message. For details of usage, see message processing rules in the published Standard.
The domain of possible values for permanent or transient handicapped conditions of a person.
The domain of possible values for identifiers for physicians.
The domain of possible values that specify a charging system. Not used after HL7 2.1. No suggested values.
The domain of possible values that specify a stock location.
The domain of possible values that identify reasons for patient isolation. Not used after HL7 2.1.
The domain of possible values for a type of financial transaction.
The domain of possible values for the patient type. No suggested values.
The domain of possible values for the anesthesia used during the procedure. No suggested values.
This table is not used and therefor the domain is invalid!!!
The domain of possible values for the bad debt agency to which the account was transferred.
The domain of possible values for whether the particular insurance has been billed and, if so, the type of bill. No suggested values.
The domain of possible values for where the patient was admitted. No suggested values.
The domain of possible values for the appropriate fee schedule to be used for this transaction posting.
The domain of possible values for the allowed priorities for obtaining the specimen.
The domain of possible values for which price schedule is to be used for room and bed charges. No suggested values.
The domain of possible values that are used to indicate a means of administrating a medication dose.
The domain of possible values that specify a location on the body where a dose is to be administered, e.g., IV, IM, Subcutaneous.
Units of measure abbreviations (pre-coordinated codes), derived from ISO528:1977.
The domain of possible values for the status of an order. The purpose of these values are to report the status of an order either upon request (solicited), or when the status changes (unsolicited). The values are not intended to initiate action. It is assumed that the order status value always reflects the status as it is known to the sending application at the time that a message is sent. Only the filler can originate these values.
The domain of possible values for an insurance company plan uniquely. No suggested values.
The domain of possible values for the condition code.
The domain of possible values for the type of contract entered into by the healthcare facility and the guarantor for the purpose of settling outstanding account balances.
The domain of possible values for whether the patient will be extended certain special courtesies.
The domain of possible values for past credit experience.
The domain of possible values which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry.
The domain of possible values for the department that controls a specified transaction code.
The domain of possible values for the type of accident.
The domain of possible values for the primary diagnosis code for billing purposes.
The domain of possible values that specify a type of diagnosis being sent.
The domain of possible values specifying a diagnosis coding method.
The domain of possible values for the diagnostic related group (DRG) for the transaction.
The domain of possible values for that the grouper results have been reviewed and approved.
The domain of possible values for the type of consent that was obtained for permission to treat the patient.
The domain of concepts that identify a messaging or interface error.
The domain of possible values for the check digit scheme employed.
The domain of possible values for the reason for an event.
The domain of possible values for an actual personal relationship that the next of kin/associated party has to a patient.
The domain of possible values for the financial class assigned to a person.
The domain of possible values for actions to be taken with respect to the specimens that accompany or precede an order. The purpose of these are to further qualify (when appropriate) the general action indicated by the order control code.
The domain of possible values for the guarantor's employment status.
The domain of possible values for the type of guarantor, e.g., individual, institution, etc. No suggested values.
The domain of possible values for the treatment or type of surgery the patient is scheduled to receive.
The domain of possible values 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 0488 Specimen Collection Method as of version 2.5 and thereafter.
The domain of possible values for the identifier of an insurance plan with which a transaction should be associated.
The domain of possible values for the amount of interest that will be charged the guarantor on any outstanding amounts.
The domain of possible values for a section of a diagnostic service where an observation may be performed.
The domain of possible values for message types.
The domain of possible values for a categorical assessment of an observation value. Discussion: These interpretation codes are sometimes called "abnormal flags", however, the judgment of normalcy is just one of the common rough interpretations, and is often not relevant. For example, the susceptibility interpretations are not about "normalcy", and for any observation of a pathologic condition, it does not make sense to state the normalcy, since pathologic conditions are never considered "normal."
The domain of possible values that identify a bed location.
The domain of possible values for the nature of an abnormal test.
The domain of possible values for the type of outlier (i.e. period of care beyond DRG-standard stay in facility) that has been paid.
The domain of possible values for a composite number/name of a person/group that performed a test/procedure/transaction, etc.
Observation Result Status Codes Interpretation
The domain of possible values for observation result status. These codes reflect the current completion status of the results for one Observation Identifier.
The domain of possible values for the coding structure that identifies the various plan types (i.e., Medicare, Medicaid, Blue Cross, HMO, etc.).
The domain of possible values for whether the patient must have pre-admission testing done in order to be admitted.
The domain of possible values for a unique identifier assigned to a procedure, if any, associated with a charge.
The domain of possible values that specify the methodology used to assign a code to a procedure (CPT4, for example). Used for backwards-compatibility purposes.
The domain of concepts that further define a type of procedure.
The domain of possible values for a time frame in which a querry response is expected.
The domain of possible values which are used to specify that a patient is being re-admitted to a healthcare facility from which they were discharged, and indicates the circumstances around such re-admission.
The domain of possible values for whether the healthcare provider can release information about a patient and what information can be released.
The domain of concepts that indicate if an insurer sends a report indication that the patient is eligible for benefits and identifies what those benefits are.
The domain of possible values for codes to further identify an insurance plan.
The domain of possible values for a type of VIP.
The domain of possible values for codes for an event precipitating/triggering a charge activity.
The domain of possible values that 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 query messaging.
The domain of possible values 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.
The domain of possible values for whether the message is part of a production, training or debugging system.
The domain of possible values which are used to identify an HL7 version in the Version 2.x family of published standards.
The domain of possible values which are used to specify the source of a comment.
The domain of possible values which specify which of several types of formats for data to be returned in response to a query.
The domain of possible values which specify which type of deferred query resonse is desired, as specified with the query parameters.
The domain of possible values which are used to control level of detail in query results.
The domain of possible values which specify the priority associated with a report or update run using a query.
The domain of possible values for that the account was transferred to bad debts and gives the reason. No suggested values.
The domain of possible values for that the account was deleted from the file and gives the reason. No suggested values.
The domain of possible values for the disposition of the patient at time of discharge (i.e., discharged to home, expired, etc.). No suggested values. In the US, this field should use the Official Uniform Billing (UB) 04 2008 numeric codes found on form locator 17.
The domain of possible values for the healthcare facility to which the patient was discharged. No suggested values.
The domain of possible values for a special diet type for a patient. No suggested values.
The domain of possible values for the healthcare facility with which this visit is associated in a multiple facility environment. No suggested values.
The domain of possible values for the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not.
The domain of possible values for the account status. No suggested values.
The domain of possible values for the major diagnostic category. No suggested values.
The domain of possible values which are used to determine the function of the order segment. Depending on the message, the action specified by one of these control codes may refer to an order or an individual service.
The domain of possible values allowing the placer (sending) application to determine the amount of information to be returned from the filler.
The domain of possible values for someone or something other than the patient to be billed for a service.
The domain of possible values for a status of results for an order.
The domain of possible values for how (or whether) to transport a patient, when applicable, for an ordered service.
The domain of possible values for the format of the observation value in the Observation Result (OBX).
The domain of possible values for the maximum length of a query response that can be accepted by a requesting system, and are expressed as units of mesaure of query response objects.
The domain of possible values fora classification of general allergy categories (drug, food, pollen, etc.).
The domain of possible values for the general severity of an allergy.
The domain of possible values for the fiancial accommodation type of the bed or room which implies the rate to be used when occupied by a patient under specific medical conditions, which determines how it is billed. No suggested values.
The domain of possible values for categories of a patient's visit with respect to an individual institution's needs, and is expected to be different on a site-specific basis.
The domain of possible values for a relationship role that the next of kin/associated parties plays with regard to a patient. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that issued a referral.
The domain of possible values that are used by an institution for the purpose of uniquely identifying a transaction based on the Transaction Type. For example, procedure, supply item, or test for charges; or to identify the payment medium for payments.
The domain of possible values of concepts which specify the different types of practitioners associated with this procedure.
The domain of possible values which indicate whether an insured person agreed to assign the insurance benefits to a healthcare provider. If so, the insurance will pay the provider directly.
The domain of possible values for either Yes or No used in fields containing binary answers generally user-specified.
The domain of possible values for a party to which a claim should be mailed when claims are sent by mail.
The domain of possible values for the required employer information data for UB82 form locator 71. No suggested values.
The domain of possible values for the military branch. This field is defined by CMS or other regulatory agencies.
The domain of possible values for the military rank/grade of the patient. Australia: https://en.wikipedia.org/wiki/Australian_Defence_Force_ranks Canada: http://www.forces.gc.ca/en/honours-history-badges-insignia/rank.page United States: published in the Defense Travel Administrator's Manual, Appendix M: Military Rank/Civilian Pay Grade Abbreviations and Service Agency Names, http://www.defensetravel.dod.mil/Docs/Training/DTA_App_M.pdf
The domain of possible values for the military status of the patient. This field is defined by CMS or other regulatory agencies.
The domain of possible values for the reason a service is not covered. No suggested values.
The domain of possible values for the source of information about the insured's eligibility for benefits.
The domain of possible values for the room type.
The domain of possible values for amount quantity type.
The domain of possible values for the policy type.
The domain of possible values for whether the amount is currency or a percentage.
The domain of possible values for whether the days are denied, pending or approved.
The domain of possible values for the category or type of patient for which this certification is requested.
The domain of possible values for the status of the second opinion. No suggested values.
The domain of possible values for if accompanying documentation has been received by the provider. No suggested values.
The domain of possible values for the National Uniform Billing Committee (NUBC) code. In the US, the codes defined in code system 2.16.840.1.113883.6.301.6 nubc-ValueCode-cs are often used.
Accept/Application Acknowledgment Conditions
The domain of possible values which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode.
The domain of possible values that specify the type of date referred to in the other date fields in the QRF segment.
The domain of possible values that specify the status type of objects selected in date range defined by QRF-2 and QRF-3.
The domain of possible values that allow the specification of certain types of values within the date/time range.
The domain of possible values for the type of diet.
The domain of possible values for the type of dietary tray.
The domain of possible values for whether substitutions are allowed and, if so, the type of substitutions allowed.
The domain of possible values for the route of administration.
The domain of possible values that specify a body site from which a specimen is obtained.
The domain of possible values for the mechanical device used to aid in the administration of the drug or other treatment. Common examples are IV-sets of different types.
The domain of possible values for the specific method requested for the administration of the drug or treatment to the patient.
The domain of possible values for the RX component type.
The domain of possible values for the substitution status.
The domain of possible values for one or more available priorities for performing the observation or test.
The domain of possible values for the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority.
The domain of possible values for the parents and children for diagnostic studies, especially in microbiology, where the initial specimen (e.g., blood) is processed to produce results (e.g., the identity of the bacteria grown out of the culture). The process also produces new "specimens" (e.g., pure culture of staphylococcus, and E. coli), and these are studied by a second order process (bacterial sensitivities). The parents (e.g., blood culture) and children (e.g., penicillin MIC) are identified in such cases.
The domain of possible values for the information related to a person's country citizenship. No suggested values.
The domain of possible values for the military status assigned to a veteran. No suggested values.
The domain of possible values for whether this insurance works in conjunction with other insurance plans or if it provides independent coverage and payment of benefits regardless of other insurance that might be available to the patient.
The domain of possible values for an identification of a test battery, an entire functional procedure or study, a single test value (observation), multiple test batteries or functional procedures as an orderable unit (profile), or a single test value (observation) calculated from other independent observations, typically used as an indicator for Master Files.
The domain of possible values which are represented by codes identifying HL7 Versions 2.x Master Files.
The domain of possible values that uniquely identify an application responsible for maintaining a master file of a particular type at a particular site. Not used after HL7 v2.2 No suggested values.
The domain of possible values for the degree to which special confidentiality protection should be applied to the observation.
The domain of possible values for file-level events for master files.
The domain of possible values for application response levels defined for a given Master File Message at the MFE segment level, and used for MFN-Master File Notification message.
The domain of possible values for a record-level event for a master file record.
The domain of possible values for the status of the requested update. Site-defined table, specific to each master file being updated via this transaction.
The domain of possible values for the staff person's sex. No suggested values.
The domain of possible values for whether a person is currently a valid staff member.
The domain of possible values for the institution department to which this person reports or belongs. No suggested values.
The domain of possible values for which of a group of multiple phone numbers is the preferred method of contact for this person.
The domain of possible values for the category of practitioner. No suggested values.
The domain of possible values for how provider services are billed.
The domain of possible values for identifiers for operators.
The domain of possible values further defining a patient's ancestry. In the US, a current use is to use these codes to report ethnicity in line with US federal standards for Hispanic origin.
The domain of possible values for types or kinds of addresses.
The domain of possible values declaring the general type of media data that is encoded.
The domain of possible values defining whether patient transportation preparations are in place.
The domain of possible values for the amount quantity class.