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

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

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

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 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 for the amount quantity class.

The domain of possible values for types of names for persons.

The domain of possible values for specifying a specific use of a telecommunication number. Best practice is to use this concept whenever a telecommunication number or access string is specified.

The domain of possible values for specifying a type of telecommunication equipment. Best practice is to use this concept whenever a telecommunication number or access string for particular equipment is specified.

The domain of possible values for the type of identifier.

The domain of possible values that specify the type of name for an organization i.e., legal name, display name.

The domain of possible values to identify the intent for the dollar amount on a pricing transaction.

The domain of possible values for actions to be applied for segments when an HL7 version 2 interface is operating in "action code mode" (a kind of update mode in the Standard).

The domain of possible values that indicate an archival process or an initial load process.

The domain of possible values defining precise response status concepts in support of HL7 Version 2 query messaging. It is commonly used to indicate no data is found that matches the query parameters, but no error.

The domain of possible values to define the relationship between HL7 segment field names identified in a query construct.

The domain of possible values used with relational operator values to group more than one segment field name.

The domain of possible values that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte.

The domain of possible values that identify the nation or national grouping to which the person belongs. This information may be different from a person’s citizenship in countries in which multiple nationalities are recognized (for example, Spain: Basque, Catalan, etc.).

The domain of possible values that define the state of a visit relative to its place in a purge workflow.

The domain of possible values that record a health insurance program required for healthcare visit reimbursement.

The domain of possible values for a level of publicity of information about a patient for a specific visit.

The domain of possible values that define the state of a care episode for a patient.

The domain of possible values that define a relative level of urgency applied to a patient visit.

The domain of possible values that indicate which adjustments should be made to a guarantor’s charges. For example, when a hospital agrees to adjust a guarantor’s charges to a sliding scale. No suggested values.

The domain of possible values that indicate whether a treatment is continuous. No suggested values.

The domain of possible values characterizing the situation that patient-associated parties live in at their residential address.

The domain of possible values that indicate a reason for contacting a guarantor, for example, to phone a guarantor if payments are late. No suggested values.

The domain of possible values identifying specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient's healthcare needs.

The domain of possible values defining whether patient transportation preparations are in place.

The domain of possible values indicating whether a patient must be accompanied while travelling to a diagnostic service department.

The domain of possible values for the organization that manufactures a vaccine. The values are maintained by the US Centers of Disease Control. Note that the source of truth for these code values are maintained by the CDC, and the code system may be accessed at URL: https://phinvads.cdc.gov/vads/SearchCodeSystems_search.action?searchOptions.searchText=PH_ManufacturersOfVaccinesMVX_CDC_NIP. The value set is also maintained by the CDC, and may be accessed at URL: https://phinvads.cdc.gov/vads/SearchValueSets_search.action?searchOptions.searchText=PHVS_ManufacturersOfVaccinesMVX_CDC_NIP

The domain of possible values that classify whether a patient visit can be related to a diagnosis.

The domain of possible values that identify a Diagnostic Resource Group Payor. US Realm. No suggested values.

The domain of possible values that classify a procedure.

The domain of possible values that designate whether a guarantor is a full or part time student.

The domain of possible values that describe why an insurance company has been contacted.

The domain of possible values that specify a non-concur code and description for a denied request, used in insurance claims processing. No suggested values.

The domain of possible values to identify the time span of a report or the reason for a report sent to a regulatory agency.

The domain of possible values to identify where a report sender learned about an event.

The domain of possible values to identify the type of entity to which the event has been reported.

The domain of possible values to qualify an event related to a product experience.

The domain of possible values to a sender to designate an event as serious or significant.

The domain of possible values to communicate whether an event has been judged to be expected or unexpected.

The domain of possible values to describe the impact of an event on a patient.

The domain of possible values to describe the overall state of a patient as a result of patient care.

The domain of possible values to provide a general description of the kind of health care professional who provided the primary observation.

The domain of possible values to define whether the primary observer has given permission for their identification information to be provided to a product manufacturer.

The domain of possible values that indicate whether a product is designed for a single use. No suggested values.

The domain of possible values that indicate if a product problem would exist if a product malfunction could lead to death or serious injury.

The domain of possible values that indicate that the product is available for analysis. No suggested values.

The domain of possible values that describes the status of product evaluation.

The domain of possible values to describe the evaluation state of a product identified in an incident.

The domain of possible values that indicate whether the product used is a generic or a branded product. No suggested values.

The domain of possible values to provide an estimate of whether an issue with a product was the cause of an event.

The domain of possible values to define the action taken as a result of an event related to a product issue.

The domain of possible values to record event observations regarding what may have caused a product related event.

The domain of possible values to identify the mechanism of product transmission when the product has not been directly applied to the patient.

The domain of possible values that describe the underlying kind of property represented by an observation. The categories distinguish concentrations from total amounts, molar concentrations from mass concentrations, partial pressures from colors, and so forth. These are discussed more fully in the LOINC Users' Manual. They are derived from the approach described in 1995 edition of the IUPAC Silver Book. These distinctions are used in IUPAC and LOINC standard codes. The distinctions of true quantities in this table are based primarily on dimensional analyses. The table contains a number of "families," those related to simple counts (number, number concentration, etc.), to mass (mass, mass concentration, etc.), to enzyme activity (catalytic content, catalytic concentration, etc.), and molar or equivalents (substance content, substance concentration).

The domain of possible values that classify an observation definition as intended to measure a patient's state at a point in time.

The domain of possible values to classify an observation definition as being a component of a challenge test.

The domain of possible values to further describe an observation definition that is characterized as a challenge observation.

The domain of possible values to an observation definition to describe the subject of an observation in relation to a patient.

The domain of possible values that define the imaging apparatus expected to be used to acquire an observation. This table has been removed from the standard as of 2.7 in favor of table 0910.

The domain of possible values that identify the kind of location described in the location definition.

The domain of possible values that identify the equipment available in a location definition identified as a room or bed.

The domain of possible values that identify the level of privacy a patient will be afforded when assigned to this location definition.

The domain of possible values that identify the level of care a patient may be afforded when assigned to this location definition.

The domain of possible values used to specify the institution’s department to which a location belongs, or its cost center.

The domain of possible values that identify the specialty of the care professional who is supported when using this location definition.

The domain of possible values to identify the day(s) of the week when a location may be scheduled for appointments.

The domain of possible values that define whether a Charge Description Master description may be overridden or if it must be overridden.

The domain of possible values that define the event upon which a charge should be generated.

The domain of possible values that identify the kind of patient document.

The domain of possible values to record the state of a document in a workflow.

The domain of possible values that specify the degree to which special confidentiality protection should be applied to information. The assignment of data elements to these categories is left to the discretion of the healthcare organization.

The domain of possible values to define whether a patient document is appropriate or available for use in patient care.

The domain of possible values to describe the availability of a document in relation to the type of storage.

The domain of possible values that describe the kind of appointment or the reason why an appointment has been scheduled.

The domain of possible values that an appointment request to describe the kind of appointment.

The domain of possible values that describe an appointment status from the perspective of the entity assigned to fulfill the appointment.

The domain of possible values that indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment.

The domain of possible values that designate the urgency of a referral.

The domain of possible values that identify the general category of healthcare professional desired to satisfy a referral.

The domain of possible values that identify the expected response from the healthcare professional receiving a referral.

The domain of possible values that define the state of a referral.

The domain of possible values that describe the patient care setting where a referral should take place.

The domain of possible values for the identification of the insurance company or other entity that administers the authorizing coverage plan. No suggested values.

The domain of possible values that define the relationship between a referral recipient and a patient or between a referral initiator and a patient.

The domain of possible values to Patient Care for the intent of a problem or goal.

The domain of possible values for the census tract in which the specified address resides. No suggested values.

The domain of possible values for the county or parish in which the specified address resides. No suggested values.

The domain of possible values that are used for base64 MIME encoding. Base64 is defined as follows (adapted from MIME Internet standard RFC 1521).

The domain of possible values for a subset of the media subtypes of binary data that are encoded in an ascii structure or stream.

The domain of possible values for the administered vaccines. The values are maintained by the US Centers of Disease Control.. The code system is maintained by the CDC, and may be found at URL; https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.113883.12.292 The value set is maintained by the CDC and may be found at URL: https://phinvads.cdc.gov/vads/ViewValueSet.action?id=ABDEE003-77C3-48E7-B941-EBF92B6B81FC

The domain of possible values for the billing category codes for any classification systems needed, for example, general ledger codes and UB92 categories. No suggested values.

The domain of possible values that describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling.

The domain of possible values for an associated party's disability. No suggested values.

The domain of possible values for the patient's primary language. No suggested values.

The domain of possible values for the CN identification source. No suggested values.

The domain of possible values that specify whether a composite price range is experssed as a flat rate or a percentage.

The domain of possible values identifying the type of encoding used to represent successive octets of binary data as displayable ASCII characters. These are defined by IETF; more information may be found at https://www.ietf.org/rfc/rfc1521.txt

The domain of possible values for the unique name of the system that stores the data. It was previously named the Application ID. No suggested values.

The domain of possible values for the type of UID (Universal Identifier).

The domain of possible values for the point where patient care is administered. It is conditional on Person Location Type (e.g., nursing unit or department or clinic). No suggested values.

The domain of possible values for the patient's room. No suggested values.

The domain of possible values for the patient's bed. No suggested values.

The domain of possible values for the categorization of the person's location.

The domain of possible values for the status or availability of the location, such as the bed status. No suggested values.

The domain of possible values for the building where the person is located. No suggested values.

The domain of possible values for the floor where the person is located. No suggested values.

The domain of possible values for the type of insurance coverage or what types of services are covered for the purposes of a billing system. For example, a physician billing system will only want to receive insurance information for plans that cover physician/professional charges.

The domain of possible values for a next of kin/associated party's job status.

The domain of possible values for the extent of insurance coverage for a participating member (e.g., single, family, etc.). No suggested values.

The domain of possible values for how an insurance policy is established. No suggested values.

The domain of possible values for whether or not the patient has a living will and, if so, whether a copy fo the living will is on file at the healthcare facility. If the patient does not have a living will, the value of this field indicates whether the patient was provided information on living wills.

The domain of possible values for whether the patient wants to donate his/her organs and whether an organ donor card or similar documentation is on file with the healthcare organization.

The domain of possible values for the coded entry associated with a given point in time during the waveform recording. Note codes beyond 9903 may exist; extensions to this table may be done by incrementing the code value.

The domain of possible values for the accounting code that identifies the department in order to charge for the item. No suggested values.

The domain of possible values identifying an item in order to charge for the item. No suggested values.

The domain of possible values for the method by which treatment is dispensed.

The domain of possible values for the status of the treatment administration event.

The domain of possible values that are used to specify a record operation.

The domain of possible values for an identifier code to show which characteristic is being communicated with the segment.

The domain of possible values for an identifier code to show which relationship is being communicated with the segment.

The domain of possible values for the level on which data are being sent. It is the indicator used to send data at two levels, visit and account. HL7 recommends sending an "A" or no value when the data in the message are at the account level or "V" to indicate that the data sent in the message are at the visit level.

The domain of possible values that specify a person's job code. No suggested values.

The domain of possible values that specify a person's employee classification. No suggested values.

The domain of possible values to specify the method by which the quantity distributed is measured.

The domain of possible values to specify the basis for marketing approval.

The domain of possible values to specify the type of facility.

The domain of possible values to indicate (in certain systems) whether a lower level source identifier is an initiate or accept type.

The domain of possible values for the driver's license issuing authority. No suggested values.

The domain of possible values that specify to which person the disability information relates in the message. For example, if the value is PT, the disability information relates to the patient.

The domain of possible values that specify the interval between repeated services. See the Comment/Usage Note in the table below, as the table contains both precoordinated codes that may be used in an HL7 field or component and also explanatory patterns illustrating the syntax used to construct expressions using the codes and other modifiers.

The domain of possible values that specify the reason for which the referral will take place.

The domain of possible values to specify the status of the practitioner's speciality certification.

The domain of possible values for the type of number used for the practitioner identification.

The domain of possible values for the status of the patient's or the patient's representative's consent for responsibility to pay for potentially uninsured services. This element was introduced to satisfy CMS Medical Necessity requirements for outpatient services in the United States. Includes concepts such as (a) whether the associated diagnosis codes for the service are subject to medical necessity procedures, (b) whether, for this type of service, the patient has been informed that they may be responsible for payment for the service, and (c) whether the patient agrees to be billed for this service.

The domain of possible values that specify a procedure code modifier to a procedure code. Procedure code modifiers are defined by regulatory agencies such as CMS and the AMA. Multiple modifiers may be reported. The modifiers are sequenced in priority according to user entry. This is a requirement of the UB and the 1500 claim forms. Multiple modifiers are allowed and the order placed on the form affects reimbursement.

The domain of possible values that specify a guarantor's credit rating. No suggested values.

The domain of possible values that specify a designation as a military recipient. This field is defined by CMS or other regulatory agencies. No suggested values.

The domain of possible values that specify a military program for the handicapped in which a patient is enrolled. No suggested values.

The domain of possible values that specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies.

The domain of possible values that specify reasons an appeal was made on a non-concur for certification. No suggested values.

The domain of possible values that specify a certification agency. No suggested values.

The domain of possible values for the names of the principal country subdivisions (e.g., provinces or states). The values in the table are country specific. For example, in the US, the Federal Information Processing Standard (FIPS) alpha codes may be used by local agreement.

The domain of possible values that specify a special program.

The domain of possible values that specify PSRO/UR approval indicators.

The domain of possible values that specify the event or occurrence relating to a bill that may affect payer processing.

The domain of possible values that identify an event that relates to the payment of a claim.

The domain of possible values that represent an exception identifier code; that is, a code that is not defined in the value set (either model or site-extended). These are occationsally referred to a 'flavors of null' although this set of concepts is specific to the CWE datatype used in Version 2 messaging, and the codes may be used in the 'identifier' component of the 'triplets' in that datatype.

The domain of possible values of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard.

The domain of possible values to specify the type for the master file record identifier.

The domain of possible values that specify the scheme used when any alternative character sets are specified in the second or later iterations of MSH-18 Character Set, and if any special handling scheme is needed.

The domain of possible values for the HL7 (communications) error code.

The domain of possible values for the name and/or code of a group of practitioners to which this practitioner belongs. No suggested values.

The domain of possible values that identify the significance or priority of the diagnosis code. Note that the codes are numeric, and the number of the code represents the ordinal priority of the associated diagnosis. The predefined codes are the most common, and just a starter set, as the codes are an unbounded list; additional ranked procedures may be signified by incrementing the code value as needed.

The domain of possible values for an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging.

The domain of possible values that identify a sending application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. No suggested values.

The domain of possible values for the site-specific name for the facility used by this application. No suggested values.

The domain of possible values for a unique name of the system (or organization or agency or department) that creates the data. No suggested values.

The domain of possible values that identify the type of comment text being sent in the specific comment record.

The domain of possible values that identify the status the equipment was in at the time the transaction was initiated.

The domain of possible values that identify the current state of control associated with the equipment. Equipment can either work autonomously ('Local' control state) or it can be controlled by another system, e.g., LAS computer ('Remote' control state).

The domain of possible values that identify the highest level of the alert state (e.g.,highest alert severity) that is associated with the indicated equipment (e.g. processing event, inventory event, QC event).

The domain of possible values that identify the comment the component is to initiate.

The domain of possible values that identify the role of a sample.

The domain of possible values that identify the status of the unique container in which the specimen resides at the time the transaction was initiated.

The domain of possible values for any additive introduced to the specimen before or at the time of collection. These additives may be introduced in order to preserve, maintain or enhance the particular nature or component of the specimen.

The domain of possible values that identify the specimen component, e.g., supernatant, sediment, etc.

The domain of possible values that identify the specimen treatment performed during lab processing.

The domain of possible values that identify the specimen contaminant identifier associated with the specimen in the container.

The domain of possible values that identify the artificial blood identifier associated with the specimen.

The domain of possible values describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing.

The domain of possible values that identify the other environmental factors associated with the specimen in a specific container, e.g., atmospheric exposure.

The domain of possible values that identify a type of carrier. Because the geometry can be different, the carrier type should, if possible, express the number of positions in the carrier. The definition assumes hierarchical nesting using the following phrases: container is located in a carrier, carrier is located in a tray. No suggested values.

The domain of possible values that identify a type of tray. Because the geometry can be different, the tray type should, if possible, express the number of positions in the tray. The definition assumes hierarchical nesting using the following phrases: container is located in a carrier, carrier is located in a tray. No suggested values.

The domain of possible values that identify a type of separator being used (e.g., a gel separator in a container - not to be confused with the communication separators). It is recommended the first table entry be "NO" meaning "No Separator". No suggested values.

The domain of possible values that identify a type of cap that is to be used with a container for decapping, piercing or other mechanisms. No suggested values.

The domain of possible values that identify a drug interference associated with a specimen. No suggested values.

The domain of possible values identifying the status of the inventoried item. The status indicates the current status of the substance.

The domain of possible values identifying the type of substance.

The domain of possible values that identify a manufacturer of a substance. Relevant external code systems may be used, e.g., HIBCC Manufacturers Labeler ID Code (LIC), UPC, NDC, etc. No suggested values.

The domain of possible values that identify a supplier of a substance. No suggested values.

The domain of possible values identifying the response of the previously issued command.

The domain of possible values identifying the processing type that applies to the test code. If this attribute is omitted, then regular production is the default.

The domain of possible values identifying the repeat status for the analyte/result (e.g. original, rerun, repeat, reflex). The following are assumptions regarding the table values: Repeated without dilution — performed usually to confirm correctness of results (e.g., in case of results flagged as "Panic" or mechanical failures). Repeated with dilution — performed usually in the case the original result exceeded the measurement range (technical limits). Reflex test — this test is performed as the consequence of rules triggered based on other test result(s).

The domain of possible values for the optional segment groups which are to be included in a response.

The domain of possible values identifying what search components (e.g., name, birthdate, social security number) of the record returned matched the original query where the responding system does not assign numeric match weights or confidence levels. It provides a method for passing a descriptive indication of the reason a particular record was found.

The domain of possible values identifying the name or identity of the specific search algorithm to which the RCP-5 Search Confidence Threshold and the QRI-1 Candidate Confidence refer.

The domain of possible values identifying the timing and grouping of the response message(s).

The domain of possible values identifying whether the subscription is new or is being modified.

The domain of possible values of specifying the coding system. This table is maintained outside of the published Version 2 standards, and may be found at http://www.hl7.org/Special/committees/vocab/table_0396/index.cfm.

The domain of possible values identifying how the field or parameter will be sorted and, if sorted, whether the sort will be case sensitive (the default) or not.

The domain of possible values identifying whether it is a fragmented message or part of an interactive continuation message.

The domain of possible values that identifies a country of origin for a message. It will be used primarily to specify default elements, such as currency denominations. The values to be used are those of ISO 3166. The ISO 3166 table has three separate forms of the country code: HL7 specifies that the 3-character (alphabetic) form be used for the country code.

The domain of possible values for codes that indicate an agency that the practitioner is authorized to bill for medical services. Existing codes only for use in the United States.

The domain of possible values for a categorization of an academic institution that grants a degree to a Staff Member.

The domain of possible values for codes that indicate the ability that a Staff Member possesses with respect to the language.

The domain of possible values which specify the level of knowledge a person possesses with respect to a language ability identified.

The domain of possible values which specify the hierarchical components of an organization unit, as defined by the institution. No suggested values.

The domain of possible values that specify the environment in which the provider acts in the role associated with the provider type, and inludes codes for venues outside of formal organized healthcare settings, such as Home. The provider environment is not the specialty for the provider.

The domain of possible values that specify a type of change being requested (if NMR query) or announced (if NMD unsolicited update).

The domain of possible values that specify supplemental service information sent between a placer system and a filler system for the universal procedure code reported in OBR-4 Universal Service ID. This specifies ordering information detail that is not available in other specific tables for fields in the OBR segment. These might be details such as whether a study is to be done on the right or left, for example, where the study is of the arm and the order master file does not distinguish right from left, or whether a study is to be done with or without contrast (when the order master file does not make such distinctions).

The domain of possible values that specify a category name (term given to a group of service items for the purpose of classification). Examples: Laboratory, Pharmacy, Diagnostic Imaging, etc. No suggested values.

The domain of possible values that provide an identifier for the consent specified for a service item. No suggested values.

The domain of possible values that specify a unit of time. No suggested values.

The domain of possible values that specify a type of hospital receiving a transfer patient, which affects how a facility is reimbursed under diagnosis related group (DRG's), for example, exempt or non-exempt.

The domain of possible values that specify a procedure's priority ranking relative to its DRG.

The domain of possible values that specify the type of tissue removed from a patient during a procedure.

The domain of possible values specifying a number that identifies the significance or priority of the procedure code.

The domain of possible values specifying the severity ranking of a patient's illness.

The domain of possible values specifying a patient's prioritization within the context of this abstract.

The domain of possible values specifying the reason a non-urgent patient presents to the emergency room for treatment instead of a clinic or physican office.

The domain of possible values specifying the status of the birth in relation to the gestation

The domain of possible values specifying whether the baby was born in or out of the facility.

The domain of possible values specifying the blood product code.

The domain of possible values specifying the incident that occurred during a patient's stay.

The domain of possible values specifying a classification of the incident type.

The domain of possible values specifying the code and/or text indicating the primary use for which the living subject was bred or grown.

The domain of possible values specifying how the patient was brought to the healthcare facility.

The domain of possible values specifying what recreational drugs the patient uses.

The domain of possible values specifying the acuity level assigned to the patient at the time of admission.

The domain of possible values specifying non-clincal precautions that need to be taken with the patient.

The domain of possible values specifying the patient's current medical condition for the purpose of communicating to non-medical outside parties, e.g. family, employer, religious minister, media, etc.

The domain of possible values specifying the patient's instructions to the healthcare facility.

The domain of possible values specifying the reason the patient should not be exposed to a substance.

The domain of possible values specifying any type of allergy alert device the patient may be carrying or wearing.

The domain of possible values specifying the verification status for the allergy.

The domain of possible values specifying the data type.

The domain of possible values for the immunization registry status of the patient.

The domain of possible values specifying the types of services provided by the location.

The domain of possible values for the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.).

The domain of possible values specifying the preferred display order of the components of this person name.

The domain of possible values for the reliability of patient/person identifying data transmitted via a transaction.

The domain of possible values for the species of living organism.

The domain of possible values for the specific breed of animal.

The domain of possible values specifying the context in which a name is used.

The domain of possible reasons a specimen may be rejected for a specified observation/result/analysis.

The domain of possible values specifying the type of event of the message.

The domain of possible values specifying the substance that is in inventory.

The domain of possible values for the major grouping of the service or occupation of a practitioner at a specific organization unit.

The domain of possible values for the more specific service or occupation within the healthcare provider type of the practitioner at a specific organization unit.

The domain of possible values for the segment of the population that a health care provider chooses to service, a specific medical service, a specialization in treating a specific disease, or any other descriptive characteristic about a provider’s practice relating to the services rendered of a practitioner at a specific organization unit.

The domain of possible values specifying the specific type of bill with digit 1 showing type of facility, digit 2 showing bill classification and digit 3 showing frequency.

The domain of possible values specifying a service line revenue code. These are claim codes indicating the identifying number for the product or service provided.

The domain of possible values specifying the final status of the claim.

The domain of possible values that specify the edits that result from processing the HCPCS/CPT procedures for a record after evaluating all the codes, revenue codes, and modifiers.

The domain of possible values for the action to be taken during reimbursement calculations.

The domain of possible values for the OCE status of the line item.

The domain of possible values for the license number for the facility.

The domain of possible values for the cost center to which this location belongs.

The domain of possible values specifying an identifying stock number, if any, which might be used, for example, as a cross reference for materials management.

The domain of possible values for the facility of the institution for which a specified price is valid. For use when needing multi-facility pricing.

The domain of possible values for an indication of the representation provided by the data item.

The domain of possible values for the derived Ambulatory Payment Classification (APC) code.

The domain of possible values that specify the edits of the modifiers for each line or HCPCS/CPT.

The domain of possible values for any payment adjustment due to drugs or medical devices.

The domain of possible values for the packaging status of the service.

The domain of possible values for the fee schedule reimbursement type applied to a line item.

The domain of possible values for the name of a query.

The domain of possible values for that a second timing specification is to follow using the repeat delimiter.

The domain of possible values for whether or not the service (pharmaceutical) is in the formulary.

The domain of possible values for the classification of the organization unit.