Concept Properties that are associated with this Code System or Value Set Version

Indicates whether the relationship is intended to be navigated when selecting a code

Indicates if the association always holds for a concept with itself (refexive), never holds for a concept with itself (irreflexive)

Identifies the name of the relationship that references the inverse of the current relationship. Allows linking a relationship and its derived inverse.

Identifies a type of relationship between codes that is supported by this code system version

Indicates if the relationship always holds in the reverse direction as well (symetric), never holds in the reverse direction as well (antisymetric)

Indicates whether the relationship always (transitive) or never (antitransitive) propagates such that if the association exists from A to B and from B to C that the relationship can be inferred to exist from A to C

The human-readable descriptive name for the code or identifier system

The business version associated with the Naming System

Either a practitioner role or a relationship type. Note from UTG import - may have been a temporary entry that subsequently disappeared from the FHIR source; unable to locate. Version set to 0.1.0

The type of action to be performed.

High-level categorization of the type of activity.

This value set includes a smattering of adjudication codes.

This value set includes smattering of Adjudication Reason codes.

This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc.

Overall categorization of the event, e.g. product-related or situational.

Codes for the assessment of whether the entity caused the event.

TODO.

Overall seriousness of this event for the patient.

The severity of the adverse event itself, in direct relation to the subject.

The risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products).

Preferred value set for AllergyIntolerance Clinical Status.

The verification status to support or decline the clinical status of the allergy or intolerance.

This example value set defines a set of reasons for the cancellation of an appointment.

Method of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation.

The type of process where the audit event originated from.

The type of process where the audit event originated from.

This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts.

This value set includes a smattering of Network type codes.

This value set includes a smattering of Benefit Term codes.

This value set includes a smattering of Benefit type codes.

This value set includes a smattering of Unit type codes.

The type of catalog.

The relative quality of the statistic.

The quality rating of the subcomponent of a quality of evidence rating.

The subcomponent classification of quality of evidence rating systems.

The method used to determine the characteristic(s) of the variable.

Example set of codes that can be used for billing purposes.

Direction in which lists of possible answers should be displayed.

Chromosome number for human.

This value set includes sample Claim Care Team Role codes.

This value set includes sample Exception codes.

This value set includes sample Information Category codes.

This value set includes sample Modifier type codes.

This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation.

This value set includes Claim Type codes.

Indicates the type of use for which the code is defined.

Common Tag Codes defined by FHIR project

Codes for general categories of communications such as alerts, instructions, etc.

Codes for the reason why a communication did not happen.

Codes describing the purpose or content of the communication.

The composite scoring method of the measure.

Indicates the type of use for which the code is defined.

Preferred value set for Condition Categories.

Preferred value set for Condition Clinical Status.

Enumeration indicating whether the condition is currently active, inactive, or has been resolved.

The verification status to support or decline the clinical status of the condition or diagnosis.

Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification.

This value set includes sample Consent Action codes.

This value set includes sample Regulatory consent policy types from the US and other regions.

This value set includes the four Consent scope codes.

This value set includes base Consent Verification codes.

This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.

Color of the container cap.

This value set includes sample Contract Action codes.

This value set includes sample Contract Actor Role codes.

This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.

How a resource reference is interpreted when evaluating contract offers.

This value set includes sample Contract Signer Type codes.

This value set includes sample Contract Subtype codes.

This value set includes sample Contract Term SubType codes.

This value set includes sample Contract Term Type codes.

This value set includes sample Contract Type codes.

Copy Number Event.

This value set includes Coverage Class codes.

This value set includes sample Coverage Copayment Type codes.

This value set includes Example Coverage Financial Exception Codes.

This value set includes Coverage SelfPay codes.

This value set includes CoverageEligibilityResponse Auth Support codes.

Codes identifying the lifecycle stage of a definition.

High-level categorization of the definition, used for searching, sorting, and filtering.

Structure Definition Use Codes / Keywords

Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.

The availability status reason of the device.

This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.

The quality of how direct the match is.

The kind of dose or rate specified.

This value set defines a set of codes that can be used to indicate from where the patient came in.

This value set defines a set of codes that can be used to indicate the class of encounter: a specific code indicating class of service provided.

This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.

This value set defines a set of codes that can be used to where the patient left the hospital.

This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit.

This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter

This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided.

This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.

EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example.

This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.

A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems.

This value set includes examples of Benefit Category codes.

This value set includes example Diagnosis on Admission codes.

This value set includes example Diagnosis Related Group codes.

This value set includes example Diagnosis Type codes.

The type of Claim payee Resource.

This value set includes example Payment Type codes.

This value set includes example Procedure Type codes.

This value set includes sample Program Reason Span codes.

This value set includes sample Revenue Center codes.

Declares what the source of a parameter is.

Defines how concepts are processed into the expansion when it’s for UI presentation.

This value set includes Financial Task codes.

This value set includes Financial Task Input Type codes.

Example list of general categories for flagged issues. (Not complete or necessarily appropriate.)

This value set includes a sample set of Forms codes.

This value set includes sample funds reservation type codes.

Codes indicating whether the goal has been accepted by a stakeholder.

Describes the progression, or lack thereof, towards the goal against the target.

Example codes for grouping goals to use for filtering or presentation.

Indicates the level of importance associated with reaching or sustaining a goal.

Types of relationships between two goals.

Code of parameter that is input to the guide.

Set of handling instructions prior testing of the specimen.

Codes describing the reason why a family member’s history is not available.

An HL7 administrative unit that owns artifacts in the FHIR specification.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient’s eligibility for a vaccination program. This value set is provided as a suggestive example.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example.

A set codes that define the functional status of an implanted device.

Whether the cost applies to in-network or out-of-network providers.

This example value set defines a set of codes that can be used to indicate a type of insurance plan.

The type of knowledge asset this library contains.

General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).

Example use codes for the List resource - typical kinds of use.

Base values for the order of the items in a list resource.

This example value set defines a set of codes that can be used to indicate the physical form of the Location.

A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not.

The intended usage for supplemental data elements in the measure.

Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.

The type of population.

The scoring type of the measure.

The type of measure (includes codes from 2.16.840.1.113883.1.11.20368).

MedicationAdministration Performer Function Codes

Direction in which lists of possible answers should be displayed.

Direction in which lists of possible answers should be displayed.

MedicationDispense Performer Function Codes

MedicationKnowledge Characteristic Codes

MedicationKnowledge Package Type Codes

MedicationKnowledge Status Codes

Direction in which lists of possible answers should be displayed.

MedicationRequest Category Codes

MedicationRequest Course of Therapy Codes

MedicationRequest Status Reason Codes

Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.

This value set includes sample Missing Tooth Reason codes.

NutritionIntake Category Codes

Code representing the role the entity played in the audit event.

Observation Category codes.

The statistical operation parameter -“statistic” codes.

This example value set defines a set of codes that can be used to indicate a type of organization.

Codes identifying groupings of parameters; e.g. Cardiovascular.

This value set includes sample Payee Type codes.

This value set includes smattering of Payment Adjustment Reason codes.

This value set includes a sample set of Payment Status codes.

This value set includes sample Payment Type codes.

The type of PlanDefinition.

Concepts that describe whether a condition is present when a patient is admitted to a healthcare facility.

This value set includes the financial processing priority codes.

This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties.

The type of participation a provenance participant.

This value set includes sample Provider Qualification codes.

Flags an element as having unlimited repetitions.

Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item.

Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event.

This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process.

A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems.

This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population.

Criterion for rejection of the specimen by laboratory.

This value set includes sample Related Claim Relationship codes.

Codes for the kind of study objective.

Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation.

Codes for the main intent of the study.

Codes for why the study ended prematurely.

Indicates the progression of a study subject through the study milestones.

Identifies the kind of state being refered to.

Indicates the progression of a study subject through a study.

Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource.

The type of payee Resource.

Codes representing the likelihood of a particular outcome in a risk assessment.

This value set defines an example set of codes that can be used to classify groupings of service-types/specialties.

This value set includes a smattering of Service Place codes.

The code(s) that detail the conditions under which the healthcare service is available/offered.

The methods of referral can be used when referring to a specific HealthCareService resource.

This value set defines an example set of codes of service-types.

This value set includes a smattering of USCLS codes.

Codes that define what the server is capable of.

SNOMED International Global Patient Set (GPS) value set. The value set includes all of the codes from the SNOMED International Global Patient Set (GPS) subset of SNOMED CT. The current version of the value set contains all concepts (26,158) from the September 2020 release of the GPS (based on the July 2020 SNOMED CT International Edition release).

This value set is provided as a FHIR ValueSet resource instance for the convenience of implementers.

A set of generally useful codes defined so they can be included in value sets.

HL7 Ballot/Standards status of artifact.

Indicates why the state of the subject changed.

The type of a specific statistic.

The type of study a statistic was derived from.

This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient).

Codes to represent subscription error details

Codes to represent subscription error details

A status code for the state of the Subscription.

Tags to put on a resource after subscriptions have been sent.

Substance category codes

This value sets refers to a specific supply item.

This value sets refers to a Category of supply.

The reason why the supply item was requested.

This value set includes a smattering of FDI tooth surface codes.

Types of combining results from a body of evidence (eg. summary data meta-analysis).

This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.

This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript.

This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript.

This value set includes a smattering of FDI oral site codes.

A code that specifies a type of context being specified by a usage context.

The role that the assertion variable plays.

Codes providing the status of the variant test result.

Ability of the primary source to push updates/alerts

Attested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system’s API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated.

The result if validation fails

The frequency with which the target must be validated

Type of the validation primary source

Type of alerts/updates the primary source can send

The primary process by which the target is validated

Status of the validation of the target against the primary source

What the target is validated against

This value set includes a smattering of Prescription Product codes.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Deprecation Comment: This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.

Description: Deprecation Comment: Was mis-named, and a proper representation has been provided. Replaced by value set ActRelationshipCompliesWith.

Code systems used in HL7 standards.

An anatomical location on a human which can be the focus of an act. OpenIssue: This value set was approved for deletion in November 2008, and was deleted at release #762. Subsequently, however, it was found that this deletion caused the legacy software embedded in the RMIM Designer in Visio to fail to show appropriate options for concepts in the subject area of this value set. For that reason, the value set was re-added in releasse 813 and DEPRECATED from general use at the same time. This value set should be deleted as soon as it is no longer required to support of the legacy software.

Codes for use in the ext-mif-relationship-relationshipKind to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.relationshipKind values

Codes for use in the ext-mif-relationship-reflexivity to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.reflexivity values

Codes for use in the ext-mif-relationship-symmetry to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.symmetry values

Codes for use in the ext-mif-relationship-transitivity to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.transitivity values

This value set contains 4 concepts commonly used as answers to items in a questionnaire.

Concepts specifying a patient’s sex for administrative purposes.

Value Set of codes that specify a person’s marital (civil/legal) status.

Concepts specifying the trigger event for Version 2.x interface messages.

Concepts used by systems to categorize patients by sites.

This race value set is based upon CDC check-digit codes, but using the HL7 table 0005. HL7 adopted the CDC Race and Ethnicity codes in HL7 Table 0005 in 2005. This value set has been created for backward compatibility and some historic Implementation guides (E.g. Immunization). Recommend using Race Category value set based upon CDC Race & Ethnicity code system.

Value Set of codes that specify a person’s religion.

Value Set of codes that specify the circumstances under which the patient was or will be admitted.

Concepts specifying acknowledgment codes used in Version 2.x message. For details of usage, see message processing rules in the published Standard.

Value Set of codes that specify permanent or transient handicapped conditions of a person.

Value Set of codes that specify a stock location.

Value Set of codes that specify a type of financial transaction.

Value Set of codes that specify the allowed priorities for obtaining the specimen.

Value Set of codes that are used to indicate a means of administrating a medication dose.

Value Set of codes that specify a location on the body where a dose is to be administered, e.g., IV, IM, Subcutaneous.

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

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.

Concepts specifying a type of diagnosis being sent in HL7 Version 2.x messages.

Concepts used to identify the check digit scheme employed when a check digit is used in various HL7 Version 2.x datatypes.

Value Set of codes that specify the reason for an event.

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.

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

Value Set of codes that specify the guarantor’s employment status.

Value Set of codes that specify the treatment or type of surgery the patient is scheduled to receive.

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

Concepts which specify a section of a diagnostic service where the observation may be performed.

Concepts which specify message types for HL7 Version 2.x messaging.

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.

Value Set of codes that specify the nature of an abnormal test.

Value Set of codes that specify the type of outlier (i.e. period of care beyond DRG-standard stay in facility) that has been paid.

Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier.

Concepts which specify a time frame in which a querry response is expected.

Value Set of codes 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.

Concepts which specify codes to further identify an insurance plan.

Value Set of codes that specify codes for an event precipitating/triggering a charge activity.

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.

Value Set of codes that specify whether the message is part of a production, training or debugging system.

Concepts which are used to identify an HL7 version in the Version 2.x family of published standards.

Concepts which are used to specify the source of a comment, as used in HL7 Version 2.x messaging in the NTE segment.

Value Set of codes which specify which of several types of formats for data to be returned in response to a query.

Value Set of codes which specify which type of deferred query resonse is desired, as specified with the query parameters.

Value Set of codes which are used to control level of detail in query results.

Value Set of codes which specify the priority associated with a report or update run using a query.

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.

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.

Value Set of codes allowing the placer (sending) application to determine the amount of information to be returned from the filler.

Value Set of codes that specify someone or something other than the patient to be billed for a service.

Concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment.

Value Set of codes that specify how (or whether) to transport a patient, when applicable, for an ordered service.

Concepts which specify the data type of OBX-5, Observation Value, and are a subset of the datatypes defined in HL7 Version 2.x.

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.

Value Set of codes that specify classification of general allergy categories (drug, food, pollen, etc.).

Value Set of codes that specify the general severity of an allergy.

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.

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.

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.

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.

Codes specifying either Yes or No used in fields containing binary answers generally user-specified.

Value Set of codes that specify a party to which a claim should be mailed when claims are sent by mail.

Value Set of codes that specify the military branch. This field is defined by CMS or other regulatory agencies.

Value Set of codes that specify the military status of the patient. This field is defined by CMS or other regulatory agencies.

Value Set of codes that specify the source of information about the insured’s eligibility for benefits.

Value Set of codes that specify the room type.

Value Set of codes that specify amount quantity type.

Value Set of codes that specify the policy type.

Value Set of codes that specify whether the amount is currency or a percentage.

Value Set of codes that specify whether the days are denied, pending or approved.

Value Set of codes that specify the category or type of patient for which this certification is requested.

Concepts which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode.

Value Set of codes that specify the type of date referred to in the other date fields in the QRF segment.

Value Set of codes that specify the status type of objects selected in date range defined by QRF-2 and QRF-3.

Value Set of codes that allow the specification of certain types of values within the date/time range.

Value Set of codes that specify the type of diet.

Value Set of codes that specify the type of dietary tray.

Value Set of codes that specify whether substitutions are allowed and, if so, the type of substitutions allowed.

Value Set of codes that specify the route of administration.

Concepts that specify a body site from which a specimen is obtained.

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.

Value Set of codes that specify the specific method requested for the administration of the drug or treatment to the patient.

Value Set of codes that specify the RX component type.

Value Set of codes that specify the substitution status.

Value Set of codes that specify one or more available priorities for performing the observation or test.

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.

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

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.

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.

Concepts which are represented by codes identifying HL7Versions 2.x Master Files.

Value Set of codes that specify the degree to which special confidentiality protection should be applied to the observation.

Concepts specifying file-level events for master files. Used in HL7 Version 2 messaging in the MFI segment.

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.

Concepts specifying an action for a master file record. Used in HL7 V2.x messaging in the MFE segment.

Concepts which code status values for requested master file record update operations.

Value Set of codes that specify whether a person is currently a valid staff member.

Value Set of codes that specify which of a group of multiple phone numbers is the preferred method of contact for this person.

Value Set of codes that specify how provider services are billed.

Concepts 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. Used for HL7 Version 2 messaging in the PID segment.

Concepts specifying types or kinds of addresses.

Concepts declaring the general type of media data that is encoded.

Value Set of codes that specify the amount quantity class.

Concepts for types of names for persons.

Concepts for specifying a specific use of a telecommunication number.

Concepts for specifying a type of telecommunication equipment.

Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards.

Concepts used to specify the type of name for an organization i.e., legal name, display name.

Value Set of codes that identify the intent for the dollar amount on a pricing transaction.

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

Concepts that indicate an archival process or an initial load process.

Concepts defining precise response status concepts in support of HL7 Version 2 query messaging.

Value Set of codes that define the relationship between HL7 segment field names identified in a query construct.

Value Set of codes used with relational operator values to group more than one segment field name.

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.

Value Set of codes that define the state of a visit relative to its place in a purge workflow.

Value Set of codes that record a health insurance program required for healthcare visit reimbursement.

Concepts specifying a level of publicity of information about a patient for a specific visit.

Value Set of codes that define the state of a care episode for a patient.

Value Set of codes that define a relative level of urgency applied to a patient visit.

Concepts characterizing the situation that patient-associated parties live in at their residential address.

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.

Value Set of codes defining whether patient transportation preparations are in place.

Value Set of codes indicating whether a patient must be accompanied while travelling to a diagnostic service department.

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

Value Set of codes that classify whether a patient visit can be related to a diagnosis.

Value Set of codes that classify a procedure.

Value Set of codes that designate whether a guarantor is a full or part time student.

Value Set of codes that describe why an insurance company has been contacted.

Value Set of codes that identify the time span of a report or the reason for a report sent to a regulatory agency.

Value Set of codes that identify where a report sender learned about an event.

Value Set of codes that identify the type of entity to which the event has been reported.

Value Set of codes that qualify an event related to a product experience.

Value Set of codes that a sender to designate an event as serious or significant.

Value Set of codes that communicate whether an event has been judged to be expected or unexpected.

Value Set of codes that describe the impact of an event on a patient.

Value Set of codes that describe the overall state of a patient as a result of patient care.

Value Set of codes that provide a general description of the kind of health care professional who provided the primary observation.

Value Set of codes that define whether the primary observer has given permission for their identification information to be provided to a product manufacturer.

Value Set of codes that describes the status of product evaluation.

Value Set of codes that describe the evaluation state of a product identified in an incident.

Value Set of codes that provide an estimate of whether an issue with a product was the cause of an event.

Value Set of codes that define the action taken as a result of an event related to a product issue.

Value Set of codes that record event observations regarding what may have caused a product related event.

Value Set of codes that identify the mechanism of product transmission when the product has not been directly applied to the patient.

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

Value Set of codes that classify an observation definition as intended to measure a patient’s state at a point in time.

Value Set of codes that classify an observation definition as being a component of a challenge test.

Value Set of codes that further describe an observation definition that is characterized as a challenge observation.

Value Set of codes that an observation definition to describe the subject of an observation in relation to a patient.

Value Set of codes that identify the kind of location described in the location definition.

Value Set of codes that identify the equipment available in a location definition identified as a room or bed.

Value Set of codes that identify the level of privacy a patient will be afforded when assigned to this location definition.

Value Set of codes that identify the level of care a patient may be afforded when assigned to this location definition.

Value Set of codes that identify the specialty of the care professional who is supported when using this location definition.

Value Set of codes that identify the day(s) of the week when a location may be scheduled for appointments.

Value Set of codes that define whether a Charge Description Master description may be overridden or if it must be overridden.

Value Set of codes that define the event upon which a charge should be generated.

Value Set of codes that identify the kind of patient document.

Value Set of codes that record the state of a document in a workflow.

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.

Value Set of codes that define whether a patient document is appropriate or available for use in patient care.

Value Set of codes that describe the availability of a document in relation to the type of storage.

Value Set of codes that describe the kind of appointment or the reason why an appointment has been scheduled.

Value Set of codes that an appointment request to describe the kind of appointment.

Value Set of codes that describe an appointment status from the perspective of the entity assigned to fulfill the appointment.

Value Set of codes that indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment.

Value Set of codes that designate the urgency of a referral.

Value Set of codes that identify the general category of healthcare professional desired to satisfy a referral.

Value Set of codes that identify the expected response from the healthcare professional receiving a referral.

Value Set of codes that define the state of a referral.

Value Set of codes that describe the patient care setting where a referral should take place.

Value Set of codes that define the relationship between a referral recipient and a patient or between a referral initiator and a patient.

Concepts used in Patient Care for the intent of a problem or goal. Used in Version 2 messaging in the GOL segment.

Value Set of codes that are used for base64 MIME encoding. Base64 is defined as follows (adapted from MIME Internet standard RFC 1521).

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

Value Set of codes that describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling.

Value Set of codes that specify whether a composite price range is experssed as a flat rate or a percentage.

Concept identifying the type of IETF encoding used to represent successive octets of binary data as displayable ASCII characters.

Types of UID (Universal Identifiers).

Value Set of codes that specify the categorization of the person’s location.

Note that this set of codes is used generally in the US only.

Value Set of codes that specify a next of kin/associated party’s job status.

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

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.

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.

Value Set of codes that specify the method by which treatment is dispensed.

Status codes used in the workflow of treatment administration events.

Status codes of record operations.

Value Set of codes that specify an identifier code to show which characteristic is being communicated with the segment.

Value Set of codes that specify an identifier code to show which relationship is being communicated with the segment.

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

Value Set of codes that specify the method by which the quantity distributed is measured.

Value Set of codes that specify the basis for marketing approval.

Value Set of codes that specify the type of facility.

Value Set of codes that indicate (in certain systems) whether a lower level source identifier is an initiate or accept type.

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.

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

Value Set of codes that specify the reason for which the referral will take place.

Value Set of codes that specify the status of the practitioner’s speciality certification.

Value Set of codes that specify the type of number used for the practitioner identification.

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.

Value Set of codes that specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies.

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.

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.

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.

HL7 abstract message structure codes.

Value Set of codes that specify the type for the master file record identifier.

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.

HL7 (communications) error codes, as transmitted in a message acknowledgement.

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.

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.

Value Set of codes that identify the type of comment text being sent in the specific comment record.

Value Set of codes that identify the status the equipment was in at the time the transaction was initiated.

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)

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

Value Set of codes that identify the comment the component is to initiate.

Value Set of codes that identify the role of a sample.

Value Set of codes that identify the status of the unique container in which the specimen resides at the time the transaction was initiated.

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.

Value Set of codes that identify the specimen component, e.g., supernatant, sediment, etc.

Value Set of codes that identify the specimen treatment performed during lab processing.

Value Set of codes that identify the specimen contaminant identifier associated with the specimen in the container.

Value Set of codes that identify the artificial blood identifier associated with the specimen.

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.

Value Set of codes that identify the other environmental factors associated with the specimen in a specific container, e.g., atmospheric exposure.

Value Set of codes identifying the status of the inventoried item. The status indicates the current status of the substance.

Value Set of codes identifying the type of substance.

Value Set of codes identifying the response of the previously issued command.

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.

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

Value Set of codes that specify the optional segment groups which are to be included in a response.

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

Value Set of codes 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.

Value Set of codes identifying the timing and grouping of the response message(s).

Value Set of codes identifying whether the subscription is new or is being modified.

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.

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.

Value Set of codes identifying whether it is a fragmented message or part of an interactive continuation message.

Value Set of codes that specify codes that indicate an agency that the practitioner is authorized to bill for medical services. Existing codes only for use in the United States.

Value Set of codes that specify a categorization of an academic institution that grants a degree to a Staff Member.

Value Set of codes that specify codes that indicate the ability that a Staff Member possesses with respect to the language.

Value Set of codes which specify the level of knowledge a person possesses with respect to a language ability identified.

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

Value Set of codes that specify a type of change being requested (if NMR query) or announced (if NMD unsolicited update).

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.

Value Set of codes that specify a procedure’s priority ranking relative to its DRG.

Value Set of codes that specify the type of tissue removed from a patient during a procedure.

Value Set of codes specifying a number that identifies the significance or priority of the procedure code.

Value Set of codes specifying the severity ranking of a patient’s illness.

Value Set of codes specifying a patient’s prioritization within the context of this abstract.

Value Set of codes specifying the reason a non-urgent patient presents to the emergency room for treatment instead of a clinic or physican office.

Value Set of codes specifying the status of the birth in relation to the gestation

Value Set of codes specifying whether the baby was born in or out of the facility.

Value Set of codes specifying the blood product code.

Value Set of codes specifying the incident that occurred during a patient’s stay.

Value Set of codes specifying a classification of the incident type.

Value Set of codes specifying the code and/or text indicating the primary use for which the living subject was bred or grown.

Value Set of codes specifying how the patient was brought to the healthcare facility.

Value Set of codes specifying what recreational drugs the patient uses.

Value Set of codes specifying the acuity level assigned to the patient at the time of admission.

Value Set of codes specifying non-clincal precautions that need to be taken with the patient.

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.

Value Set of codes specifying the patient’s instructions to the healthcare facility.

Value Set of codes specifying the reason the patient should not be exposed to a substance.

Value Set of codes specifying any type of allergy alert device the patient may be carrying or wearing.

Value Set of codes specifying the verification status for the allergy.

Value Set of codes specifying the data type.

Immunization registry status codes of a patient. Used in Version 2 messaging in the PD1 segment.

Value Set of codes specifying the types of services provided by the location.

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

Value Set of codes specifying the preferred display order of the components of this person name.

Value Set of codes that specify the reliability of patient/person identifying data transmitted via a transaction.

Value Set of codes specifying the type of event of the message.

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.

Value Set of codes specifying the final status of the claim.

Value Set of codes that specify an indication of the representation provided by the data item.

Value Set of codes that specify the derived Ambulatory Payment Classification (APC) code.

Value Set of codes that specify any payment adjustment due to drugs or medical devices.

Value Set of codes that specify the packaging status of the service.

Value Set of codes that specify the fee schedule reimbursement type applied to a line item.

Value Set of codes that specify that a second timing specification is to follow using the repeat delimiter.

Value Set of codes that specify whether or not the service (pharmaceutical) is in the formulary.

Value Set of codes that specify the classification of the organization unit.

Value Set of codes that specify the choice of, and providing the clinical rationale for, a selected charge type.

Value Set of codes that specify the class of the drug or other substance if its usage is controlled by legislation.

Value Set of codes that specify whether or not the pharmaceutical substance is part of the local formulary.

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.

Value Set of codes that specify whether the order is to be executed in an inpatient setting or an outpatient setting.

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.

Value Set of codes that specify the type of dispensing event that occurred.

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.

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.

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.

Value Set of codes that specify any known or suspected specimen hazards, e.g., exceptionally infectious agent or blood from a hepatitis patient.

Reasons a specimen may be rejected for a specified observation/result/analysis. Used in Version 2 messaging in the SPM segment.

Value Set of codes that specify the degree or grade of excellence of the specimen at receipt.

Value Set of codes that specify the suitability of the specimen for the particular planned use as determined by the filler.

Concepts of modes or states of being that describe the nature of a specimen. Used in Version 2 messaging in the SPM segment.

Value Set of codes that specify for child specimens the relationship between this specimen and the parent specimen.

Value Set of codes that specify the modifier for the body site.

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.

Value Set of codes that specify the method in which a subject provides consent.

Value Set of codes that specify whether the consent has been sought and granted.

Value Set of codes that specify the reason the subject’s consent was not sought.

Value Set of codes that specify how much information was disclosed to the subject as part of the informed consent process.

Value Set of codes that specify a reason the subject did not receive full disclosure.

Value Set of codes that specify a reason consent was granted by a person other than the subject of the consent.

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.

Value Set of codes that specify the relationship between the start/end of the related service request(s) and the current service request.

Value Set of codes that specify if this service request is the first or last service request in a cyclic series of service requests.

Value Set of codes that specify an additional or alternate relationship between this service request and other service requests.

Concepts regarding the handling of a result.

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

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

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

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

Value Set of codes that specify the type of adverse reaction that the recipient of the blood product experienced.

Concepts documenting the severity of an application error as reported during acknowledgment of messages.

Value Set of codes that specify who (if anyone) shouldor should not be informed of an error.

Value Set of codes that specify what type of override can be used to override the specific error identified.

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

Value Set of codes that specify if the change is computed as a percent change or as an absolute change.

Value Set of codes that identify whether sequence conditions or a repeating cycle of orders is defined, as part of the Order Sequence Definition.

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

Value Set of codes that specify a common (periodical) activity of daily living.

Value Set of codes used to specify the degree of precision of a time stamp.

Value Set of codes that specify the agency or department that assigned a specified identifier.

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

Value Set of codes that specify whether the clergy should be notified.

Concepts that indicate how a patient/subscriber authorization signature is obtained and how it is being retained by a provider.

Value Set of codes that specify the status of the certificate held by a health professional.

Value Set of codes that specify the relationship the staff person has with the institution for whom he/she provides services.

Value Set of codes that specify the reason the staff member is inactive.

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

Value Set of codes that specify the breadth/extent of the jurisdiction where the qualification is valid.

Value Set of codes that specify the relationship of the consenter to the subject.

Value Set of codes that specify the part of the body.

Value Set of codes that specify what invoice action is being performed by this message.

Value Set of codes that specify the reason for an invoice.

Value Set of codes that specify the type of invoice.

Value Set of codes that specify the benefit group.

Value Set of codes that specify the type of payee (e.g., organization, person).

Value Set of codes used to specify the relationship to the invoice for Person Payee Types.

Value Set of codes that specify the processing status for the Product/Service Code.

Value Set of codes that specify the adjustment quantity.

Value Set of codes that specify the Product/Service Code.

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

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.

Value Set of codes used to specify the reason for this adjustment.

Value Set of codes used to specify the type of blood unit

Value Set of codes of units of measure that are used to specify weight.

Value Set of codes of units of measure that are used to specify volume.

Value Set of codes used to specify the action requested of a party that receives an adjustment.

Value Set of codes used to specify the method for the movement of payment.

Value Set of codes used to specify the processing status for an Invoice Processing Result.

Value Set of codes used to specify the tax status of a provider.

Value Set of codes that specify a type of user authentication credential.

Value Set of codes that specify the reason this address was marked as “ended”.

Value Set of codes that specify how an address is intended to be used.

Value Set of codes that specify that an address needs to be treated with special care or sensitivity.

Value Set of codes that specify the state of an inventory item within the context of an inventory location.

Value Set of codes that denote a level or importance of an inventory item within the context of an inventory location.

Value Set of codes that specify the calculation method used to determine the resupply schedule.

Value Set of codes that specify the method used to calculate employee labor and measure employee productivity.

Value Set of codes that specify the date format for a decontamination/sterilization instance.

Value Set of codes that specify the kind of device as defined by the manufacturer.

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.

Value Set of codes that specify the state of the data as provided from a device.

Value Set of codes that specify the status of the information provided in a device sterilization or decontamination cycle.

Value Set of codes that specify the state of a device.

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.

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.

Value Set of codes that specify the reason for the restricted access. Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an “employee” sensitivity code would make little sense for use outside of a policy domain. “Taboo” would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system’s Master Files in order to notify those who access a patient’s orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy’s criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.titleValue Set of codes that specify the reason for the restricted access.

Value Set of codes that specify the functional state of an order.

Value Set of codes that specify the clinical complexity level (CCL) value for the determined diagnosis related group (DRG) for this diagnosis.

Value Set of codes that specify the status of a diagnosis for a diagnosis related group (DRG) determination.

Value Set of codes that specify the status of a grouper in general.

Value Set of codes that specify whether the length of stay is normal or respectively shorter or longer than normal.

Value Set of codes that specify the status of the diagnosis related group (DRG) calculation regarding the financial aspects.

Value Set of codes that specify the status of the use of the gender information for diagnosis related group (DRG) determination.

Value Set of codes that specify the status of the use of the weight at birth for diagnosis related group (DRG) determination.

Value Set of codes that specify the status of the use of the respiration minutes information for diagnosis related group (DRG) determination.

Value Set of codes that specify the admission status for the diagnosis related group (DRG) determination.

Value Set of codes that specify the status of the use of this particular procedure for the diagnosis related group (DRG) determination.

Value Set of codes that specify the relevance of this particular procedure for the diagnosis related group (DRG) determination.

Value Set of codes that specify the status (useful for reporting and item usage purposes) that applies to an item.

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.

Value Set of codes that specify the regulatory agency by which the item has been approved, such as the FDA or AMA.

Value Set of codes that specify an act containing a rule that the item is legally required to be included in notification reporting.

Value Set of codes specifying the type of sterilization used for sterilizing the inventory supply item in the ITM segment.

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.

Value Set of codes specifying the general type of data.

Value Set of codes specifying the reason this contact number/email was marked as “ended”.

Value Set of codes specifying any known or suspected hazard associated with this material item.

Value Set of codes specifying the account role of the physician, for example, only billing for the professional part, the technical part or both.

Value Set of codes specifying the role of the physician (“self-employed” or “employed”).

Value Set of codes specifying the side of the body (“left” or “right”).

Value Set of codes specifying the present on admission indicator for this particular diagnosis.

Value Set of codes specifying the scheme for a security check.

Value Set of codes specifying the status of a shipment.

Value Set of codes specifying the priority for a shipment.

Value Set of codes specifying the confidentiality for a shipment.

Value Set of codes specifying the scheme for the patient results release categorization.

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

Value Set of codes specifying a root cause.

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.

Value Set of codes specifying a type of bolus.

Value Set of codes specifying a type of PCA.

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.

Concepts that indicate whether a Specimen/Attribute is Preferred or Alternate for collection of a particular specimen.

Value Set of codes specifying the code for a certification type.

Value Set of codes specifying the code for a certification category.

Value Set of codes specifying whether a process was interrrupted and whether a needle had been inserted in the donor’s arm prior to the interruption.

Value Set of codes specifying the unit of measure (UoM) for the cumulative dosage limit.

Value Set of codes specifying a phlebotomy issue.

Value Set of codes specifying the status of a phlebotomy.

Value Set of codes specifying the arm(s) receiving a stick.

Value Set of codes of units of measure that are used to specify weight.

Value Set of codes of units of measure that are used to specify volume.

Value Set of codes specifying the units of transport temperature.

Value Set of codes specifying the units of donation duration.

Value Set of codes specifying the type of intended procedure.

Value Set of codes specifying the reason for a process interruption.

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.

Value Set of codes specifying an observation sub-type.

Value Set of codes specifying the limit for a collection event or process step.

Value Set of codes specifying a communication location.

Value Set of codes specifying a type of limitation.

Value Set of codes that specify the type of measurement of the state of an automated laboratory instrument.

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.

Value Set of codes specifying the type of supplier that will distribute the supply items associated to a contract number.

Value Set of codes that specify the type of relationship that is established between the instances of Source Information and Target Information.

Value Set of codes that describe reasons for the chosen order control codes.

Value Set of codes that further define an identified status.

Value Set of codes that provide additional information to the universal service identifier on why a test, study or review was ordered.

Concepts drawn from the HL7 V3 Confidentiality code system . Used in Version 2 messaging in the Security Classification elements in the Message Header segment (MSH) and the Access Restrictions segment (ARV).

A person’s employment type as defined by compensation and sector (e.g. paid vs. unpaid, self-employed vs. not self-employed, government vs. private, etc.).

Codes used to identify medical devices.

The availability status of the device.

Codes used to identify medical devices safety characteristics. These codes are taken from the NCI Thesaurus and are provided here as a suggestive example.

Code values used to indicate the result of an online verification of insurance data.

V2 Table 0971 Version Master (Online Verification Result Error Code)

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

A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream.

Concepts used to specify a state or province. Used in Version 2 messaging in the Extended Composite ID with Check Digit (CX), Performing Person Time Stamp (PPN), and Extended Composite ID Number and Name for Persons (XCN) values as well as the Accident (ACC) segment.

Value Set of codes 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 for the codes for each country, this value set includes only the 3-character alpha form.

Testing to measure the minimum concentration of the antibacterial agent in a given culture medium below which bacterial growth is not inhibited.

Test methods designed to determine a microorganismaTMs susceptibility to being killed by an antibiotic.

A device used to allow access to a part of a body

Acknowledgement Condition codes describe the conditions under which accept or application level acknowledgements are required to be returned in response to the message send operation.

A site specific problem code

Refelects rejections because elements of the communication are not supported in the current context.

Reflects errors in the syntax or structure of the communication.

A code identifying the specific message to be provided. A textual value may be specified as the print name, or for non-coded messages, as the original text.Discussion: ‘Required attribute xxx is missing’, ‘System will be unavailable March 19 from 0100 to 0300’Examples:

Acknowledgement code as described in HL7 message processing rules.

Identifies the reason the patient is assigned to this accommodation type

An account represents a grouping of financial transactions that are tracked and reported together with a single balance. Examples of account codes (types) are Patient billing accounts (collection of charges), Cost centers; Cash.

Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results.

Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals).

Actions to be carried out by the recipient of the Adjudication Result information.

Identifies types of detectyed issues for Act class “ALRT” for the administrative and patient administrative acts domains.

Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains.

Definition:A comprehensive term for health care provided in a healthcare facility (e.g. a practitioneraTMs office, clinic setting, or hospital) on a nonresident basis. The term ambulatory usually implies that the patient has come to the location and is not assigned to a bed. Sometimes referred to as an outpatient encounter.

Description: Coded reasons why an antigen is considered invalid.

Definition:An identifying modifier code for healthcare interventions or procedures.

The type of provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider, over a specified period.

Type of bounded ROI.

Description:The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care.

A code specifying the major type of Act that this Act-instance represents. Constraints: The classCode domain is a tightly controlled vocabulary, not an external or user-defined vocabulary. Every Act-instance must have a classCode. If the act class is not further specified, the most general Act.classCode (ACT) is used. The Act.classCode must be a generalization of the specific Act concept (e.g., as expressed in Act.code), in other words, the Act concepts conveyed in an Act must be specializations of the Act.classCode. Especially, Act.code is not a “modifier” that can alter the meaning of a class code. (See Act.code for contrast.)

A unit of work, a grouper of work items as defined by the system performing that work. Typically some laboratory order fulfillers communicate references to accessions in their communications regarding laboratory orders. Often one or more specimens are related to an accession such that in some environments the accession number is taken as an identifier for a specimen (group).

An accommodation is a service provided for a Person or other LivingSubject in which a place is provided for the subject to reside for a period of time. Commonly used to track the provision of ward, private and semi-private accommodations for a patient.

A financial account established to track the net result of financial acts.

Description: An acquisition exposure act describes the proximity (location and time) through which the participating entity was potentially exposed to a physical (including energy), chemical or biological agent from another entity. The acquisition exposure act is used in conjunction with transmission exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion. Constraints: The Acquisition Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPSRC (exposure source) participation must never be associated with the Transmission Exposure either directly or via context conduction.

Sender asks addressee to do something depending on the focal Act of the payload. An example is “fulfill this order”. Addressee has responsibilities to either reject the message or to act on it in an appropriate way (specified by the specific receiver responsibilities for the interaction).

Description:A battery specifies a set of observations. These observations typically have a logical or practical grouping for generally accepted clinical or functional purposes, such as observations that are run together because of automation. A battery can define required and optional components and, in some cases, will define complex rules that determine whether or not a particular observation is made. Examples: “Blood pressure”, “Full blood count”, “Chemistry panel”.

Description:A sequence of biomolecule like the DNA, RNA, protein and the like.

Description:A variation in a sequence as described by BioSequence.

A Region of Interest (ROI) specified for a multidimensional observation, such as an Observation Series (OBSSER). The ROI is specified using a set of observation criteria, each delineating the boundary of the region in one of the dimensions in the multidimensional observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type subject (SUBJ), which must always be present. Each of the boundary criteria observations is connected with the ROI using ActRelationships of type “has component” (COMP). In each boundary criterion, the Act.code names the dimension and the Observation.value specifies the range of values inside the region. Typically the bounded dimension is continuous, and so the Observation.value will be an interval (IVL) data type. The Observation.value need not be specified if the respective dimension is only named but not constrained. For example, an ROI for the QT interval of a certain beat in ECG Lead II would contain 2 boundary criteria, one naming the interval in time (constrained), and the other naming the interval in ECG Lead II (only named, but not constrained).

An Act that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care. Discussion: A care provision event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional. In request (RQO) mood care provision communicates a referral, which is a request:

• from one party (linked as a participant of type author (AUT)),
• to another party (linked as a participant of type performer (PRF),
• to take responsibility for a scope specified by the code attribute,
• for an entity (linked as a participant of type subject (SBJ)). The scope of the care for which responsibility is taken is identified by code attribute. In event (EVN) mood care provision indicates the effective time interval of a specified scope of responsibility by a performer (PRF) or set of performers (PRF) for a subject (SBJ). Examples:
  1. Referral from GP to a specialist.
  2. Assignment of a patient or group of patients to the case list of a health professional.
  3. Assignment of inpatients to the care of particular nurses for a working shift.

A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan. The distinction from Topic relates to value sets. For Category there is a bounded list of things like “Examination”, “Diagnosis” or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter. A CATEGORY MAY CONTAIN ENTRIES.

A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA)

A clinical document is a documentation of clinical observations and services, with the following characteristics: (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care; (3) Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; (5) Human readability - A clinical document is human readable.”

The set of actions that define an experiment to assess the effectiveness and/or safety of a biopharmaceutical product (food, drug, device, etc.). In definition mood, this set of actions is often embodied in a clinical trial protocol; in event mood, this designates the aggregate act of applying the actions to one or more subjects.

An identified point during a clinical trial at which one or more actions are scheduled to be performed (definition mood), or are actually performed (event mood). The actions may or may not involve an encounter between the subject and a healthcare professional.

A group of entries within a composition, topic or category that have a logical association with one another. The representation of a single observation or action might itself be multi-part. The data might need to be represented as a nested set of values, as a table, list, or as a time series. The Cluster class permits such aggregation within an entry for such compound data. Examples include “Haematology investigations” which might include two or more distinct batteries. A cluster may contain batteries and/or individual entries

A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians. A composition represents part of a patient record originating from a single interaction between an authenticator and the record. Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application. A composition contains organizers and entries.

An observable finding or state that persists over time and tends to require intervention or management, and, therefore, distinguished from an Observation made at a point in time; may exist before an Observation of the Condition is made or after interventions to manage the Condition are undertaken. Examples: equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, chronic illness

The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc. The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act. The “signatures” to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of “performer”, the healthcare provider informing the patient, and “consenter”, the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public. Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed.

Used to group a set of acts sharing a common context. Container structures can nest within other context structures - such as where a document is contained within a folder, or a folder is contained within an EHR extract. Open issue: There is a clear conflict between this act and the use of the more general “component” ActRelationship. The question that must be resolved is what should be the class code of the parent (or containing) Act.

An Act where a container is registered either via an automated sensor, such as a barcode reader, or by manual receipt

An agreement of obligation between two or more parties that is subject to contractual law and enforcement.

An act representing a system action such as the change of state of another act or the initiation of a query. All control acts represent trigger events in the HL7 context. ControlActs may occur in different moods.

Container for Observation Sequences (Observations whose values are contained in LIST<>’s) having values correlated with each other. Each contained Observation Sequence LIST<> must be the same length. Values in the LIST<>’s are correlated based on index. E.g. the values in position 2 in all the LIST<>’s are correlated. This is analogous to a table where each column is an Observation Sequence with a LIST<> of values, and each row in the table is a correlation between the columns. For example, a 12-lead ECG would contain 13 sequences: one sequence for time, and a sequence for each of the 12 leads.

When used in the EVN mood, this concept means with respect to a covered party:

1. A health care insurance policy or plan that is contractually binding between two or more parties; or
2. A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program.
   • When used in the definition (DEF) mood, COV means potential coverage for a patient who may or may not be a covered party.
   • The concept’s meaning is fully specified by the choice of ActCoverageTypeCode (abstract) ActProgramCode or ActInsurancePolicyCode.

An observation identifying a potential adverse outcome as a result of an Act or combination of Acts. Examples: Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria. Discussion: This class is commonly used for identifying ‘business rule’ or ‘process’ problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to ‘bypass’ a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation. Constraints: the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id).

Description:A determinant peptide in a polypeptide as described by polypeptide.

Class for holding attributes unique to diagnostic images.

An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be undesirable. Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.Examples:

Specialization of Act to add the characteristics unique to document management services.

A context that distinguishes the body of a document from the document header. This is seen, for instance, in HTML documents, which have discrete <head> and <body> elements.

A context that subdivides the body of a document. Document sections are typically used for human navigation, to give a reader a clue as to the expected content. Document sections are used to organize and provide consistency to the contents of a document body. Document sections can contain document sections and can contain entries.

A context that comprises all compositions. The EHR is an extract that includes the entire chart. NOTE: In an exchange scenario, an EHR is a specialization of an extract.

An interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.

The action of coming into sufficient physical proximity to allow physical or chemical interaction. Examples include: exposure to radiation, inhalation of peanut aerosol or viral particles. This includes intended exposure (e.g. administering a drug product) as well as accidental or environmental exposure. Actual vs. potential exposure can be differentiated using Act.uncertaintyCode. The agent to which the subject was exposed is conveyed as a Direct participation or specialization there-of. Constraints: The following Participations should be used with the following Roles and Entities to distinguish the specific entities:

• The exposed entity is the entity of interest that is the recipient of the exposure and potentially affected. This is conveyed through the subject (SBJ) Participation.
• An entity that has carried the agent transmitted in the exposure is the “exposure source” (EXSRC). For example:
  • a person or animal who carried an infectious disease and interacts (EXSRC) with another person or animal (SBJ) transmitting the disease agent; or
  • a place or other environment (EXSRC) and a person or animal (SBJ) who is exposed in the presence of this environment.
• When it is unknown whether a participating entity is the source of the agent (EXSRC) or the target of the transmission (SBJ), also known as “exposure contact”, the “participant” (PART) is used.
• The substance to which the subject is exposed that carries the exposure agent or the chemical substance of interest itself, participates as a “consumable” (CSM). There are at least two configurations: (a) the player of the Role that participates as CSM is the chemical or biological substance mixed or carried by the scoper-entity of the Role (e.g., ingredient role); or (b) the player of the Role that participates as CSM is a mixture known to contain the chemical, radiological or biological substance of interest.
• The device specifically used to administer the substance is associated using the device (DEV) Participation. This may be a device intentionally used (such as applicator device) or it may be a thing that accidentally carried this substance; for instance, an infected needle or knife. The same entity may be related in the act as both EXSRC and DEV.

Description:An expression level of genes/proteins or other expressed genomic entities.

This context represents the part of a patient record conveyed in a single communication. It is drawn from a providing system for the purposes of communication to a requesting process (which might be another repository, a client application or a middleware service such as an electronic guideline engine), and supporting the faithful inclusion of the communicated data in the receiving system. An extract may be the entirety of the patient record as held by the sender or it may be a part of that record (e.g. changes since a specified date). An extract contains folders or compositions. An extract cannot contain another extract.

A transformation process where a requested invoice is transformed into an agreed invoice. Represents the adjudication processing of an invoice (claim). Adjudication results can be adjudicated as submitted, with adjustments or refused. Adjudication results comprise 2 components: the adjudication processing results and a restated (or adjudicated) invoice or claim

A contract whose value is measured in monetary terms.

A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms. In the “intent” mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts. In the “event” mood, communicates the posting of a transaction to an account.

Description:An observation of genomic phenomena.

An event that occurred outside of the control of one or more of the parties involved. Includes the concept of an accident.

The act of transmitting information and understanding about a topic to a subject where the participation association must be SBJ. Discussion: This act may be used to request that a patient or provider be informed about an Act, or to indicate that a person was informed about a particular act.

Sender sends payload to addressee as information. Addressee does not have responsibilities beyond serving addressee’s own interest (i.e., read and memorize if you see fit). This is equivalent to an FYI on a memo.

An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government.

Represents concepts related to invoice processing in health care

Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on:

• The activity of another party
• The behavior of another party
• The manner in which an act is executed Examples:A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program, e.g., immunizations, methadone treatment, or cancer registries.

Description:The position of a gene (or other significant sequence) on the genome.

An officially or unofficially instituted program to track acts of a particular type or categorization.

Description:An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The code attribute of Observation and the value attribute of Observation must be considered in combination to determine the semantics of the observation. Discussion: Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. Examples:

• Recording the results of a Family History Assessment
• Laboratory test and associated result
• Physical exam test and associated result
• Device temperature
• Soil lead level

Container for Correlated Observation Sequences sharing a common frame of reference. All Observations of the same cd must be comparable and relative to the common frame of reference. For example, a 3-channel ECG device records a 12-lead ECG in 4 steps (3 leads at a time). Each of the separate 3-channel recordings would be in their own “OBSCOR”. And, all 4 OBSCOR would be contained in one OBSSER because all the times are relative to the same origin (beginning of the recording) and all the ECG signals were from a fixed set of electrodes.

Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization on:

• The activity of another party
• The behavior of another party
• The manner in which an act is executed Examples:A clinical or research protocols imposed by a payer, a malpractice insurer, or an institution to which a provider must adhere. A mandate imposed by a denominational institution for a provider to provide or withhold certain information from the patient about treatment options.

An outbreak represents a series of public health cases. The date on which an outbreak starts is the earliest date of onset among the cases assigned to the outbreak, and its ending date is the last date of onset among the cases assigned to the outbreak.

An Outbreak is a concern resulting from a series of public health cases.

A Region of Interest (ROI) specified for an image using an overlay shape. Typically used to make reference to specific regions in images, e.g., to specify the location of a radiologic finding in an image or to specify the site of a physical finding by “circling” a region in a schematic picture of a human body. The units of the coordinate values are in pixels. The origin is in the upper left hand corner, with positive X values going to the right and positive Y values going down. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type “subject” (SUBJ), which must always be present.

Description:A genomic phenomenon that is expressed externally in the organism.

Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on:

• The activity of another party
• The behavior of another party
• The manner in which an act is executed

Description:A polypeptide resulting from the translation of a gene.

An observation denoting the physical location of a person or thing based on a reference coordinate system.

Description:An observation representing the degree to which the assignment of the spatial coordinates, based on a matching algorithm by a geocoding engine against a reference spatial database, matches true or accepted values.

Description:An observation representing one of a set of numerical values used to determine the position of a place. The name of the coordinate value is determined by the reference coordinate system.

An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Examples: : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc.

A public health case is an Observation representing a condition or event that has a specific significance for public health. Typically it involves an instance or instances of a reportable infectious disease or other condition. The public health case can include a health-related event concerning a single individual or it may refer to multiple health-related events that are occurrences of the same disease or condition of interest to public health. An outbreak involving multiple individuals may be considered as a type of public health case. A public health case definition (Act.moodCode = “definition”) includes the description of the clinical, laboratory, and epidemiologic indicators associated with a disease or condition of interest to public health. There are case definitions for conditions that are reportable, as well as for those that are not. There are also case definitions for outbreaks. A public health case definition is a construct used by public health for the purpose of counting cases, and should not be used as clinical indications for treatment. Examples include AIDS, toxic-shock syndrome, and salmonellosis and their associated indicators that are used to define a case.

A public health case is a Concern about an observation or event that has a specific significance for public health. The creation of a PublicHealthCase initiates the tracking of the object of concern. The decision to track is related to but somewhat independent of the underlying event or observation.

Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment. The registration may have a unique identifier - separate from the unique identification of the subject - as well as a core set of related participations and act relationships that characterize the registration event and aid in the disposition of the subject information by a receiving system.Usage notes:

The act of examining and evaluating the subject, usually another act. For example, “This prescription needs to be reviewed in 2 months.”

Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type “subject” (SUBJ), which must always be present.

A record of something that is being done, has been done, can be done, or is intended or requested to be done. Examples:The kinds of acts that are common in health care are (1) a clinical observation, (2) an assessment of health condition (such as problems and diagnoses), (3) healthcare goals, (4) treatment services (such as medication, surgery, physical and psychological therapy), (5) assisting, monitoring or attending, (6) training and education services to patients and their next of kin, (7) and notary services (such as advanced directives or living will), (8) editing and maintaining documents, and many others. Discussion and Rationale: Acts are the pivot of the RIM; all domain information and processes are represented primarily in Acts. Any profession or business, including healthcare, is primarily constituted of intentional and occasionally non-intentional actions, performed and recorded by responsible actors. An Act-instance is a record of such an action. Acts connect to Entities in their Roles through Participations and connect to other Acts through ActRelationships. Participations are the authors, performers and other responsible parties as well as subjects and beneficiaries (which includes tools and material used in the performance of the act, which are also subjects). The moodCode distinguishes between Acts that are meant as factual records, vs. records of intended or ordered services, and the other modalities in which act can appear. One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who “owns” the act. Responsibility for the act means responsibility for what is being stated in the Act and as what it is stated. Ownership of the act is assumed in the sense of who may operationally modify the same act. Ownership and responsibility of the Act is not the same as ownership or responsibility of what the Act-object refers to in the real world. The same real world activity can be described by two people, each being the author of their Act, describing the same real world activity. Yet one can be a witness while the other can be a principal performer. The performer has responsibilities for the physical actions; the witness only has responsibility for making a true statement to the best of his or her ability. The two Act-instances may even disagree, but because each is properly attributed to its author, such disagreements can exist side by side and left to arbitration by a recipient of these Act-instances. In this sense, an Act-instance represents a “statement” according to Rector and Nowlan (1991) [Foundations for an electronic medical record. Methods Inf Med. 30.] Rector and Nowlan have emphasized the importance of understanding the medical record not as a collection of facts, but “a faithful record of what clinicians have heard, seen, thought, and done.” Rector and Nowlan go on saying that “the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view.” Indeed the Act class is this attributable statement, and the rules of updating acts (discussed in the state-transition model, see Act.statusCode) versus generating new Act-instances are designed according to this principle of permanent attributable statements. Rector and Nolan focus on the electronic medical record as a collection of statements, while attributed statements, these are still mostly factual statements. However, the Act class goes beyond this limitation to attributed factual statements, representing what is known as “speech-acts” in linguistics and philosophy. The notion of speech-act includes that there is pragmatic meaning in language utterances, aside from just factual statements; and that these utterances interact with the real world to change the state of affairs, even directly cause physical activities to happen. For example, an order is a speech act that (provided it is issued adequately) will cause the ordered action to be physically performed. The speech act theory has culminated in the seminal work by Austin (1962) [How to do things with words. Oxford University Press]. An activity in the real world may progress from defined, through planned and ordered to executed, which is represented as the mood of the Act. Even though one might think of a single activity as progressing from planned to executed, this progression is reflected by multiple Act-instances, each having one and only one mood that will not change along the Act-instance life cycle. This is because the attribution and content of speech acts along this progression of an activity may be different, and it is often critical that a permanent and faithful record be maintained of this progression. The specification of orders or promises or plans must not be overwritten by the specification of what was actually done, so as to allow comparing actions with their earlier specifications. Act-instances that describe this progression of the same real world activity are linked through the ActRelationships (of the relationship category “sequel”). Act as statements or speech-acts are the only representation of real world facts or processes in the HL7 RIM. The truth about the real world is constructed through a combination (and arbitration) of such attributed statements only, and there is no class in the RIM whose objects represent “objective state of affairs” or “real processes” independent from attributed statements. As such, there is no distinction between an activity and its documentation. Every Act includes both to varying degrees. For example, a factual statement made about recent (but past) activities, authored (and signed) by the performer of such activities, is commonly known as a procedure report or original documentation (e.g., surgical procedure report, clinic note etc.). Conversely, a status update on an activity that is presently in progress, authored by the performer (or a close observer) is considered to capture that activity (and is later superceded by a full procedure report). However, both status update and procedure report are acts of the same kind, only distinguished by mood and state (see statusCode) and completeness of the information.

Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications on:

• The activity of another party
• The behavior of another party
• The manner in which an act is executed Examples:An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria, e.g., where disclosure might result in harm to the patient or another person. The set of health care services which a provider is credentialed or privileged to provide.

A procedure for obtaining a specimen from a source entity.

An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation

A procedure or treatment performed on a specimen to prepare it for analysis

Description:A requirement, rule, or expectation typically documented as guidelines, protocols, or formularies imposed or strongly encouraged by an organization that oversees or has authority over the practices within a domain, and which may have legal basis or ramifications on:

• The activity of another party
• The behavior of another party
• The manner in which an act is executed Examples:A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems.

Sender transmits a status change pertaining to the focal act of the payload. This status of the focal act is the final state of the state transition. This can be either a request or a command, according to the mood of the control act.

The act of putting something away for safe keeping. The “something” may be physical object such as a specimen, or information, such as observations regarding a specimen.

The spatial relationship of a subject whether human, other animal, or plant, to a frame of reference such as gravity or a collection device.

The act of introducing or otherwise applying a substance to the subject. Discussion: The effect of the substance is typically established on a biochemical basis, however, that is not a requirement. For example, radiotherapy can largely be described in the same way, especially if it is a systemic therapy such as radio-iodine. This class also includes the application of chemical treatments to an area. Examples: Chemotherapy protocol; Drug prescription; Vaccination record

Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code. Rationale: Used to specify “allowed” substitution when creating orders, “actual” susbstitution when sending events, as well as the reason for the substitution and who was responsible for it.

Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode=”product”. With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.

A group of entries within a composition that are related to a common clinical theme - such as a specific disorder or problem, prevention, screening and provision of contraceptive services. A topic may contain categories and entries.

Definition: The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD.

Description: A transmission exposure act describes the proximity (time and location) over which the participating source entity was capable of transmitting a physical (including energy), chemical or biological substance agent to another entity. The transmission exposure act is used in conjunction with acquisition exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion. Constraints: The Transmission Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPTRGT (exposure target) participation must never be associated with the Transmission Exposure either directly or via context conduction.

Transportation is the moving of a payload (people or material) from a location of origin to a destination location. Thus, any transport service has the three target instances of type payload, origin, and destination, besides the targets that are generally used for any service (i.e., performer, device, etc.)

An act which describes the process whereby a ‘verifying party’ validates either the existence of the Role attested to by some Credential or the actual Vetting act and its details.

Working list collects a dynamic list of individual instances of Act via ActRelationship which reflects the need of an individual worker, team of workers, or an organization to manage lists of acts for many different clinical and administrative reasons. Examples of working lists include problem lists, goal lists, allergy lists, and to-do lists.

A code specifying the particular kind of Act that the Act-instance represents within its class. Constraints: The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code “potassium” together with and Act.classCode for “laboratory observation” to somehow mean “potassium laboratory observation” and then use the same Act.code for “potassium” together with Act.classCode for “medication” to mean “substitution of potassium”. This mutually modifying use of Act.code and Act.classCode is not permitted.

List of condition observations.

ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms.

ActConsentDirective and ActConsentType codes are used to specify the type of Consent Directive or Consent Type to which, for example, a Consent Act conforms, to which a Security Observation (Security Label) refers to, or to which a Privacy or Security Act refers. > Steward: Security WG

Definition: Use to convey the reason that a provider may or has accessed personal healthcare information. Typically, this involves overriding the subject’s consent directives.

Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research.

Constrains the ActCode to the domain of Container Registration

An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure. Control variables are forms of observations because just as with clinical observations, the Observation.code determines the parameter and the Observation.value assigns the value. While control variables sometimes can be observed (by noting the control settings or an actually measured feedback loop) they are not primary observations, in the sense that a control variable without a primary act is of no use (e.g., it makes no sense to record a blood pressure position without recording a blood pressure, whereas it does make sense to record a systolic blood pressure without a diastolic blood pressure).

Codes specify the category of observation, evidence, or document used to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program. The type of evidence is coded as observation values.

Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside.

Response to an insurance coverage eligibility query or authorization request.

Criteria that are applicable to the authorized coverage.

Definition: Codes representing the maximum coverate or financial participation requirements.

Maximum amount paid or maximum number of services/products covered; or maximum amount or number covered during a specified time period under the policy or program.

Description:Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties.

Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties.

Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements. Example:Hospital license; physician license; clinic accreditation.

Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing individuals.

Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing individuals.

Identifies types of detected issues for Act class “ALRT”

Codes dealing with the management of Detected Issue observations

Code set to define specialized/allowed diets

Definition:A patient encounter that takes place at a dedicated healthcare service delivery location where the patient receives immediate evaluation and treatment, provided until the patient can be discharged or responsibility for the patient’s care is transferred elsewhere (for example, the patient could be admitted as an inpatient or transferred to another facility.)

Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type.

Domain provides codes that qualify the ActEncounterClass (ENC)

Concepts that identify the type or nature of exposure interaction. Examples include “household”, “care giver”, “intimate partner”, “common space”, “common substance”, etc. to further describe the nature of interaction.

A qualitative measure of the degree of exposure to the causative agent. This includes concepts such as “low”, “medium” and “high”. This quantifies how the quantity that was available to be administered to the target differs from typical or background levels of the substance.

Definition:A patient encounter that takes place both outside a dedicated service delivery location and outside a patient’s residence. Example locations might include an accident site and at a supermarket.

Code specifying financial indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay stub; tax or income document; asset document; living expenses.

The rationale or purpose for an act relating to health information management, such as archiving information for the purpose of complying with an organization policy or jurisdictional law relating to data retention.

Definition: Set of codes indicating the type of health insurance policy that covers health services provided to covered parties. A health insurance policy is a written contract for insurance between the insurance company and the policyholder, and contains pertinent facts about the policy owner (the policy holder), the health insurance coverage, the insured subscribers and dependents, and the insurer. Health insurance is typically administered in accordance with a plan, which specifies (1) the type of health services and health conditions that will be covered under what circumstances (e.g., exclusion of a pre-existing condition, service must be deemed medically necessary; service must not be experimental; service must provided in accordance with a protocol; drug must be on a formulary; service must be prior authorized; or be a referral from a primary care provider); (2) the type and affiliation of providers (e.g., only allopathic physicians, only in network, only providers employed by an HMO); (3) financial participations required of covered parties (e.g., co-pays, coinsurance, deductibles, out-of-pocket); and (4) the manner in which services will be paid (e.g., under indemnity or fee-for-service health plans, the covered party typically pays out-of-pocket and then file a claim for reimbursement, while health plans that have contractual relationships with providers, i.e., network providers, typically do not allow the providers to bill the covered party for the cost of the service until after filing a claim with the payer and receiving reimbursement).

Definition:Healthcare encounter that takes place in the residence of the patient or a designee

Set of codes indicating the type of incident or accident.

Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy. Examples are client deceased & adopted client has been given a new policy identifier.

Definition: Consent to access healthcare information.

The type of personal health information to which the subject of the information, or the delegate of the subject, consents or dissents to authorize access.

Conveyance of the type of context in which authorization given under jurisdictional law, by organizational policy, or by a patient consent directive permits the collection, access, use or disclosure of specified patient health information. Steward: Security WG

Definition:Indicates the set of information types which may be manipulated or referenced, such as for recommending access restrictions.

ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values.

Description: Conveyance of the type of information transfer protocol.

An inpatient encounter is an encounter in which the patient is admitted to a hospital or equivalent facility.

Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs.

Definition: Set of codes indicating the type of insurance policy. Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions. The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly. A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss. An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer. A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured. Discussion: In contrast to programs, an insurance policy has one or more policy holders, who own the policy. The policy holder may be the covered party, a relative of the covered party, a partnership, or a corporation, e.g., an employer. A subscriber of a self-insured health insurance policy is a policy holder. A subscriber of an employer sponsored health insurance policy is holds a certificate of coverage, but is not a policy holder; the policy holder is the employer. See CoveredRoleType.

Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee and other cost elements such as bonus, retroactive adjustment and transaction fees.

Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc.

Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee, etc.

An identifying data string for healthcare products.

Codes representing a service or product that is being invoiced (billed). The code can represent such concepts as “office visit”, “drug X”, “wheelchair” and other billable items such as taxes, service charges and discounts.

An identifying data string for A substance used as a medication or in the preparation of medication.

The billable item codes to identify adjudicator specified components to the total billing of a claim.

The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments.

The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee.

The billable item codes to identify provider supplied charges or changes to the total billing of a claim.

An identifying data string for medical facility accommodations.

The billable item codes to identify modifications to a billable item charge by a tax factor applied to the amount. As for example 7% provincial sales tax.

Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.

Processing consideration and clarification codes.

Identifies the different types of summary information that can be reported by queries dealing with Statement of Financial Activity (SOFA). The summary information is generally used to help resolve balance discrepancies between providers and payors.

Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it’s immediate children invoice elements.

Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it’s immediate children invoice elements. The domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice.

Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results.

Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it’s immediate children invoice elements. Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is only specified for the root (top level) invoice element group for an Invoice.

Provides codes associated with ActClass value of LIST (working list)

General category of medical service provided to the patient during their encounter.

List of medications.

Identifies types of monitoring programs

A code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command, possibility, goal, etc. Constraints: An Act-instance must have one and only one moodCode value. The moodCode of a single Act-instance never changes. Mood is not state. To describe the progression of a business activity from defined to planned to executed, etc. one must instantiate different Act-instances in the different moods and link them using ActRelationship of general type “sequel”. (See ActRelationship.type.)

A planned Act for a specific time and place.

A request for the booking of an appointment.

These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.

A criterion or condition over actual and potential services that must apply for an associated service to be considered. Matches records any ActMoodCompletionTrack moods.

A definition of a service (master). Historical note: in previous RIM versions, the definition mood was captured as a separate class hierarchy, called Master_service.

A criterion or condition over service events that must apply for an associated service to be considered.

A service that actually happens, may be an ongoing service or a documentation of a past service. Historical note: in previous RIM versions, the event mood was captured as a separate class hierarchy, called Patient_service_event, and later Service_event.

Definition:An act that is considered likely to occur in the future. The essential feature of an act expressed in expectation mood is that it is likely to occur. An expectation may be desirable, undesirable or neutral in effect. Examples:Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning. Discussion:INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with expectation, which is a prediction that something will happen in the future. GOL (goal) reflects a hope rather than a prediction. RSK (risk) reflects a potential negative event that may or may not be expected to happen.

Definition:An observation that is considered to be desirable to occur in the future. The essential feature of a goal is that if it occurs it would be considered as a marker of a positive outcome or of progress towards a positive outcome. Examples:Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction. Discussion: INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with goal which doesn’t represent an intention to act, merely a hope for an eventual result. A goal is distinct from the intended actions to reach that goal. “I will reduce the dose of drug x to 20mg” is an intent. “I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg” is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.

An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order.

An option is an alternative set of property-value bindings. Options specify alternative sets of values, typically used in definitions or orders to describe alternatives. An option can only be used as a group, that is, all assigned values must be used together. Historical note: in HL7 v2.x option existed in the special case for alternative medication routes (RXR segment).

A kind of service which is authorized to be performed.

A request for authorization to perform a kind of service. This is distinct from RQO which is a request for an actual act. PERMRQ is merely a request for permission to perform an act.Discussion:

Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events.

An intent to perform a service that has the strength of a commitment, i.e., other parties may rely on the originator of such promise that said originator will see to it that the promised act will be fulfilled. A promise can be either solicited or unsolicited.

A non-mandated intent to perform an act. Used to record intents that are explicitly not Orders. Professional responsibility for the ‘proposal’ may or may not be present.

A non-mandated intent to perform an act where a level of professional responsibility is being accepted by making the proposal.

A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer). Rationale: The concepts of a “request” and an “order” are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. “Orders” are commonly refused for a variety of clinical and business reasons, and the notion of a “request” obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is “request.” Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the “local” business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an “intent”, of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.

Periods of time on a schedule for a resource. Appointments occupy sets of one or more booked slots. A slot that is open for appointments is considered available and a slot that is held back for administrative purposes is considered blocked. A Resource slot that is “tentatively” booked is referred to as reserved.

Definition:An act that may occur in the future and which is regarded as undesirable. The essential feature of a risk is that if it occurs this would be regarded as a marker of a negative outcome or of deterioration towards a negative outcome. Recording a risk indicates that it is seen as more likely to occur in the subject than in a general member of the population but does not mean it is expected to occur. Examples:Increased risk of DVT, at risk for sub-acute bacterial endocarditis. Discussion:Note: An observation in RSK mood expresses the undesirable act, and not the underlying risk factor. A risk factor that is present (e.g. obesity, smoking, etc) should be expressed in event mood. INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen. GOL (goal) reflects a hope to achieve something. EXPEC (expectation) is the prediction of a positive or negative event. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen, and may not be expected to happen.

A coded description of the reason for why a patient did not receive a scheduled immunization. (important for public health strategy

Description:Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms.

Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity. Examples:

1. Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program
2. Verification of record - e.g., person has record in an immunization registry
3. Verification of enumeration - e.g. NPI
4. Verification of Board Certification - provider specific
5. Verification of Certification - e.g. JAHCO, NCQA, URAC
6. Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria
7. Verification of Provider Credentials
8. Verification of no adverse findings - e.g. on National Provider Data Bank, Health Integrity Protection Data Base (HIPDB)

Provides a categorization for annotations recorded directly against the patient

Definition: Characterizes how a patient was or will be transported to the site of a patient encounter. Examples: Via ambulance, via public transit, on foot.

Code identifying the method or the movement of payment instructions. Codes are drawn from X12 data element 591 (PaymentMethodCode)

Identifies types of dispensing events

Description:Types of policies that further specify the ActClassPolicy value set.

A code or set of codes (e.g., for routine, emergency,) specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. Discussion: This attribute is used in orders to indicate the ordered priority, and in event documentation it indicates the actual priority used to perform the act. In definition mood it indicates the available priorities.

Filler should contact the placer (or target) to schedule the service. (Was “C” in HL7 version 2.3’s TQ-priority component.)

ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1.

ActPrivacyPolicyType codes support the designation of the 1..* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor. 1..* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode. Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates. Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced.

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

Definition: A set of codes used to indicate coverage under a program. A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight. Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation. Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds. Discussion: Programs do not have policy holders or subscribers. Program eligibles are enrolled based on health status, statutory eligibility, financial status, or age. Program eligibles who are covered parties under the program may be referred to as members, beneficiaries, eligibles, or recipients. Programs risk are underwritten by not for profit organizations such as governmental entities, and the beneficiaries typically do not pay for any or some portion of the cost of coverage. See CoveredPartyRoleType.

A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type “has reason” linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: “routine requirement”, “infectious disease reporting requirement”, “on patient request”, “required by law”.

Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element.

Used to convey the relationship between two or more Acts for purpose of tracking provenance relationships such as the following:

• A predecessor Act and a successor Act (e.g., a predecessor Lab Result from which a successor Lab Result in derived)
• A ProvenanceEvent Act and a target Act for which it records the Provenance (e.g., a target Act is an update of a predecessor Act)
• A predecessor ProvenanceEvent Act and a successor ProvenanceEvent Act UsageConstraint: The v:ActRelationshipActProvenance is intended to limit the types of relationships that could be conveyed by the ActRelationshipType codes to a subset that pertains to these provenance relations.

The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act.

Used to assign a “name” to a condition thread. Source is a condition node, target can be any service.

A relationship in which the target act authorizes or certifies the source act.

Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring.

A code specifying when in the course of an Act a precondition for the Act is evaluated (e.g., before the Act starts for the first time, before every repetition, after each repetition but not before the first, or throughout the entire time of the Act.) Discussion: This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Before each step is executed and has preconditions these conditions are tested and if the test is positive, the Act has clearance for execution. The repeatNumber may indicate that an Act may be repeatedly executed. The checkpointCode is specifies when the precondition is checked and is analogous to the various conditional statements and loop constructs in programming languages “while-do” vs. “do-while” or “repeat-until” vs. “loop-exit”. For all checkpointCodes, except “end”, preconditions are being checked at the time when the preceding step of the plan has terminated and this step would be next in the sequence established by the sequenceNumber attribute. When the checkpointCode for a criterion of a repeatable Act is “end”, the criterion is tested only at the end of each repetition of that Act. When the condition holds true, the next repetition is ready for execution. When the checkpointCode is “entry” the criterion is checked at the beginning of each repetition (if any) whereas “beginning” means the criterion is checked only once before the repetition “loop” starts. The checkpointCode “through” is special in that it requires the condition to hold throughout the execution of the Act, even throughout a single execution. As soon as the condition turns false, the Act should receive an interrupt event (see interruptibleInd) and will eventually terminate. The checkpointCode “exit” is only used on a special plan step that represents a loop exit step. This allows an action plan to exit due to a condition tested inside the execution of this plan. Such exit criteria are sequenced with the other plan components using the ActRelationship.sequenceNumber.

Condition is tested every time before execution of the service (WHILE condition DO service).

Condition is tested at the end of a repeated service execution. The service is repeated only if the condition is true (DO service WHILE condition).

Condition is tested once before the service is executed (IF condition THEN service).

Condition is a loop checkpoint, i.e. it is a step of an activity plan and, if negative causes the containing loop to exit.

Condition must be true throughout the execution and the service is interrupted (asynchronously) as soon as the condition turns false (asynchronous WHILE loop). The service must be interruptible.

Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred

Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act.

A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy.

The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act.

The reasons that may be used when relating a Quality Measure Document to other document types.

Used to convey the relationship between two or more Documents for purpose of tracking provenance relationships such as a predecessor Document and a successor Document. For example, a predecessor Clinical Summary Document from which a successor Clinical Summary Document is derived.

The source act documents the target act.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

The source Act ends after the end of the target Act (i.e. if we say “ActOne EBE ActTwo”, it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

The source Act ends when the target act starts (i.e. if we say “ActOne ECWS ActTwo”, it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target).

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter.

A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a “goal distance” (e.g., goal to observation) can be “calculated” and need not be sent explicitly.

The source is an excerpt from the target.

The source is a direct quote from the target.

The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act.

A specialization of “has support” (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the “ST elevation” observation – the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general “has support” relation is used. Likewise, if a ROI on an image defines the true bounds of a “1st degree burn”, the relation “has bounded support” is used; but if the ROI only points to the approximate area of the burn, the general “has support” relation is used.

A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service. The financial transaction will define the charge (bill) for delivery or performance of the service. Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product.

A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.

A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood.

A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used.

A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device’s settings that influenced the observation.

A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service. The financial transaction will define the cost of delivery or performance of the service. Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product.

A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance.

A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance.

This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition.

A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood.

The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic).

A goal that one defines given a patient’s health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood.

A relationship between a source Act that provides more detailed properties to the target Act. The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements. The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements. Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options.

A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable.

A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services.

Reference ranges are essentially descriptors of a class of result values assumed to be “normal”, “abnormal”, or “critical.” Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results.

A noteworthy undesired outcome of a patient’s condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed.

Relates an Act to its subject Act that the first Act is primarily concerned with. Examples

1. The first Act may be a ControlAct manipulating the subject Act
2. The first act is a region of interest (ROI) that defines a region within the subject Act.
3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. Constraints An Act may have multiple subject acts. Rationale The ActRelationshipType “has subject” is similar to the ParticipationType “subject”, Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship.

Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post.)

A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified. Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded.

Description: The ways that product safety Investigations, about which information is captured in an Individual Case Safety Report, are related to each other. One investigation may be performed at a patient care institution, and the second by a manufacturer, a third by a regulatory agency. They may all investigate the same case and are thus related. Other kinds of relationships are replacement (if the mode of the Investigation is changed).

Used to capture the link between a potential service (“master” or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master’s defaults.

An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered.

Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.

An assertion that a new observation was assumed to be the cause for another existing observation. The assumption is attributed to the same actor who asserts the observation. This is stronger and more specific than the support link. For example, a growth of Staphylococcus aureus may be considered the cause of an abscess. The source (cause) is typically an observation, but may be any service, while the target must be an observation.

An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation.

Items located

A code specifying how concurrent Acts are resynchronized in a parallel branch construct. Discussion: This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. Branches are parallel if the splitCode specifies that more than one branch can be executed at the same time. The joinCode then specifies if and how the braches are resynchronized. The principal re-synchronization actions are (1) the control flow waits for a branch to terminate (wait-branch), (2) the branch that is not yet terminated is aborted (kill-branch), (3) the branch is not re-synchronized at all and continues in parallel (detached branch). A kill branch is only executed if there is at least one active wait (or exclusive wait) branch. If there is no other wait branch active, a kill branch is not started at all (rather than being aborted shortly after it is started.) Since a detached branch is unrelated to all other branches, active detached branches do not protect a kill-branch from being aborted.

Detach this branch from the other branches so it will not be resynchronized with the other branches.

Wait for any one of the branches in the set of exclusive wait branches to terminate, then discontinue all the other exclusive wait branches.

When all other concurrent branches are terminated, interrupt and discontinue this branch.

Wait for this branch to terminate.

A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood.

A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is “observation of pain” and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger.

The source act removes or lessens the occurrence or effect of the target act.

Definition: Used to link a newer version or ‘snapshot’ of a business object (source) to an older version or ‘snapshot’ of the same business object (target). Usage:The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead. Name from source to target = “modifiesPrior” Name from target to source = “modifiesByNew”

The target act is a desired outcome of the source act. Source is any act (typically an intervention). Target must be an observation in criterion mood.

The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the “completion track” but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa).

An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called “post-condition”.) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute

This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays.

Expresses values for describing the relationship between a FinancialTransaction and an Account.

Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a ‘reason’ for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc. Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies.

Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated.

The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. Discussion: In prior releases, the code “SUGG” (suggests) was expressed as “an inversion of the reason link.” That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.

Definition: The source act is performed to recover from the effects of the target act.

Relates either an appointment request or an appointment to the order for the service being scheduled.

A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee.

A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.

A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction. Constraints: the “completion track” mood of the target Act must be equally or more “actual” than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT.

Associates a specific time (and associated resources) with a scheduling request or other intent.

An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation.

A code specifying how branches in an action plan are selected among other branches. Discussion: This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches. In addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as “guard conditions” on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true. In exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true.

The pre-condition associated with the branch is evaluated once and if true the branch may be entered. All other exclusive branches compete with each other and only one will be selected. This implements a COND, IF and CASE conditionals, or “XOR-split.” The order in which the branches are considered may be specified in the priorityNumber attribute.

A branch is selected as soon as the pre-condition associated with the branch evaluates to true. If the condition is false, the branch may be entered later, when the condition turns true. All other exclusive branches compete with each other and only one will be selected. Each waiting branch executes in parallel with the default join code wait (see below). The order in which the branches are considered may be specified in the Service_relationship.priority_nmb.

A branch is executed if its associated preconditions permit. If associated preconditions do not permit, the branch is dropped. Inclusive branches are not suppressed and do not suppress other branches.

A branch is executed as soon as its associated conditions permit. If the condition is false, the branch may be entered later, when the condition turns true. Inclusive branches are not suppressed and do not suppress other branches. Each waiting branch executes in parallel with the default join code wait (see below).

Description:A relationship in which the target act takes place with a defined temporal relationship with respect to the time at which the source act terminates.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

The source Act starts after the start of the target Act (i.e. if we say “ActOne SAS ActTwo”, it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).

The source Act starts after the end of the target Act (i.e. if we say “ActOne SBE ActTwo”, it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

The source Act starts when the target act ends (i.e. if we say “ActOne SCWE ActTwo”, it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target).

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets. Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.

Definition: A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be ‘completed’. The original act is the target act and the successor is the source act.

An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period.

Used in the diagnosis of the indicated disease.

Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.

Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)

A code specifying the meaning and purpose of every ActRelationship instance. Each of its values implies specific constraints to what kinds of Act objects can be related and in which way. Discussion: The types of act relationships fall under one of 5 categories: 1.) (De)-composition, with composite (source) and component (target) 2.) Sequel which includes follow-up, fulfillment, instantiation, replacement, transformation, etc. that all have in common that source and target are Acts of essentially the same kind but with variances in mood and other attributes, and where the target exists before the source and the source refers to the target that it links back to. 3.) Pre-condition, trigger, reason, contraindication, with the conditioned Act at the source and the condition or reason at the target. 4.) Post-condition, outcome, goal and risk, with the Act at the source having the outcome or goal at the target. 5.) A host of functional relationships including support, cause, derivation, etc. generalized under the notion of “pertinence”.

A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread.

Definition: Consent to have healthcare information in an electronic health record accessed for research purposes.

Definition:An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours.

Set of codes related to specimen treatments

Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation

An observation that reports the dilution of a sample.

An observation that relates to factors that may potentially cause interference with the observation

An observation that reports the volume of a sample.

Contains the names (codes) for each of the states in the state-machine of the RIM Act class.

The Act has been terminated prior to the originally intended completion.

Description: The status of an assessment for indications of an abnormal condition.

The Act can be performed or is being performed

** none supplied **

** none supplied **

The Act has been abandoned before activation.

An Act that has terminated normally after all of its constituents have been performed.

An Act that is still in the preparatory stages has been put aside. No action can occur until the Act is released.

An Act that is in the preparatory stages and may not yet be acted upon

Encompasses the expected states of an Act, but excludes “nullified” and “obsolete” which represent unusual terminal states for the life-cycle.

This Act instance was created in error and has been ‘removed’ and is treated as though it never existed. A record is retained for audit purposes only.

This Act instance has been replaced by a new instance.

An Act that has been activated (actions could or have been performed against it), but has been temporarily disabled. No further action should be taken against it until it is released

Describes the type of substance administration being performed.

The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents.

Identifies types of detected issues regarding the administration or supply of an item to a patient.

Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision. E.g. “Suspect fraud”, “Possible abuse”, “Contraindicated”. (used when capturing ‘refusal to fill’ annotations)

A clinician enters a clinical note about a given patient

A person reviews a clinical note of a given patient.

Description: A task or action that a user may perform in a clinical information system.

A person reviews a list of medication orders submitted to a given patient

A person reviews a list of microbiology results of a given patient.

A person enters documentation about a given patient.

A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record.

A person reviews a Risk Assessment Instrument report of a given patient.

Codes used to identify different types of ‘duration-based’ working lists. Examples include “Continuous/Chronic”, “Short-Term” and “As-Needed”.

Characterizes how a transportation act was or will be carried out. Examples: Via private transport, via public transit, via courier.

A code indicating whether the Act statement as a whole, with its subordinate components has been asserted to be uncertain in any way. Examples: Patient might have had a cholecystectomy procedure in the past (but isn’t sure). Constraints: Uncertainty asserted using this attribute applies to the combined meaning of the Act statement established by all descriptive attributes (e.g., Act.code, Act.effectiveTime, Observation.value, SubstanceAdministration.doseQuantity, etc.), and the meanings of any components. Discussion:This is not intended for use to replace or compete with uncertainty associated with a Observation.values alone or other individual attributes of the class. Such pointed indications of uncertainty should be specified by applying the PPD, UVP or UVN data type extensions to the specific attribute. Particularly if the uncertainty is uncertainty of a quantitative measurement value, this must still be represented by a PPD<PQ> in the value and NOT using the uncertaintyCode. Also, when differential diagnoses are enumerated or weighed for probability, the UVP<CD> or UVN<CD> must be used, not the uncertaintyCode. The use of the uncertaintyCode is appropriate only if the entirety of the Act and its dependent Acts is questioned. Note that very vague uncertainty may be thought related to negationInd, however, the two concepts are really independent. One may be very uncertain about an event, but that does not mean that one is certain about the negation of the event.

Deprecation Comment: Content moved to ActCode, and is now represented in value set ActPrivacyLaw.

Definition:A patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone conference, email exchange, robotic surgery, and televideo conference.

This can be a unit designator, such as apartment number, suite number, or floor. There may be several unit designators in an address (e.g., “3rd floor, Appt. 342”.) This can also be a designator pointing away from the location (e.g. Across the street from).

Description: An address line is for either an additional locator, a delivery address or a street address.

Discussion: The hierarchical nature of these concepts shows composition. E.g. “Street Name” is part of “Street Address Line”

Description:Identifies the different representations of a Address. The representation may affect how the address is used. (E.g. use of Ideographic for formal communications.)

The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges). Also includes the concept ‘Adjudicate as zero’ and items not covered under a particular Policy. Invoice element can be reversed (nullified). Recommend that the invoice element is saved for DUR (Drug Utilization Reporting).

Indicates the form in which the drug product should be administered. This element only needs to be specified when (a) the form in which the drug is measured for dispensing differs from the form in which the drug is administered; and (b) the form in which the quantity of the administered drug being administered is not expressed as a discrete measured mass or volume.Usage:

Administration of the proposed therapy may be inappropriate or contraindicated as proposed

A device intended to administer a substance to a subject

A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClassCommissioningParty.

The gender of a person used for adminstrative purposes (as opposed to clinical gender)

The player of the role is a child taken into a family through legal means and raised by the scoping person (parent) as his or her own child.

Proposed therapy may be inappropriate or contraindicated due to patient age

Observation values used to indicate the age group of a person in terms of age group concept codes.

Reaching a decision through the application of an algorithm designed to weigh the different factors involved.

The clinical status of an allergy disposition (Clinical Focus) Used in Program: C-CDA, C-CDA R2.1 2017-06-09 using this value set

Indicates the result of a particular allergy test. E.g. Negative, Mild, Moderate, Severe

An emergency vehicle used for transporting patients to a health care facility after injury or illness. Types of ambulances used in the United States include ground (surface) ambulance, rotor-wing (helicopter), and fixed-wing aircraft (airplane).

Amniotic fluid sac

Application specific media type.

Artificial dentition, artificial subsitutes for the natural dentition

Information was sought but not found (e.g., patient was asked but didn’t know)

Description:A role type that is used to further qualify a non-person subject playing a role where the role class attribute is set to RoleClass AssignedEntity

Audio media type.

This code is used to specify the exact function an actor is authorized to have in a service in all necessary detail.

This code is used to specify the exact function an actor is authorized to have as a receiver of information that is the subject of a consent directive or consent override.

Definition: An insurance policy for losses sustained in an automobile accident that typically covers losses incurred by the named insured and parties who may be claimants for losses, such as pedestrians and passengers.

Biliary tract

Description: All coded binding realms for terminology constraint context binding.

Description:Animals, including fish and insects, and microorganisms which may participate as assigned entities in biotherapies.

A bubblepack. Medications sealed individually, separated into doses.

Body surface

A container, typically rounded, either glass or plastic with a narrow neck and capable of storing liquid.

Buccal mucosa

The number of a building, house or lot alongside the street. Also known as “primary street number”. This does not number the street but rather the building.

One letter calendar cycle abbreviations (Temporary - remove when RoseTree is fixed)

Two letter calendar cycle abbreviations (Temporary - remove when RoseTree is fixed)

A solid dosage form in which the drug is enclosed within either a hard or soft soluble container or “shell” made from a suitable form of gelatin.

Code for the mechanism by which disease was acquired by the living subject involved in the public health case. Includes sexually transmitted, airborne, bloodborne, vectorborne, foodborne, zoonotic, nosocomial, mechanical, dermal, congenital, environmental exposure, indeterminate.

Cecostomy

Cervix of the uterus

Internet Assigned Numbers Authority (IANA) Charset Types

Chew

The player of the role is a child of the scoping entity.

The player of the role is the spouse of scoping person’s child.

(1) A hospital including a physical plant and personnel that provides multidisciplinary diagnosis and treatment for diseases that have one or more of the following characteristics: is permanent; leaves residual disability; is caused by nonreversible pathological alteration; requires special training of the patient for rehabilitation; and/or may be expected to require a long period of supervision or care. In addition, patients require the safety, security, and shelter of these specialized inpatient or partial hospitalization settings. (2) A hospital that provides medical and skilled nursing services to patients with long-term illnesses who are not in an acute phase but who require an intensity of services not available in nursing homes

A role type used to qualify a person’s legal status within a country or nation. Examples:

• Full citizen
• Asylum seeker
• Permit card holder

DescriptionA role recognized through the eligibility of a party play a claimant for benefits covered or provided under an insurance policy.

Description: Subset of null flavors, used for associations as needed for the ITS, and used in InfrastructureRoot.

Definition:Specifies the reason that an event occurred in a clinical research study.

Definition:SSpecifies the reason that a test was performed or observation collected in a clinical research study. Note:This set of codes are not strictly reasons, but are used in the currently Normative standard. Future revisions of the specification will model these as ActRelationships and thes codes may subsequently be retired. Thus, these codes should not be used for new specifications.

Definition:Contains domains for act reasons used in clinical research.

How a code system is maintained by HL7

Identifies how to interpret the instance of the code, codeSystem value in a set of translations. Since HL7 (or a government body) may mandate that codes from certain code systems be sent in conformant messages, other synonyms that are sent in the translation set need to be distinguished among the originally captured source, the HL7 specified code, or some future role. When this code is NULL, it indicates that the translation is an undefined type. When valued, this property must contain one of the following values: SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination) There may be additional values added to this value set as we work through the use of codes in messages and determine other Use Cases requiring special interpretation of the translations.

Description:Indicates why the prescription should be suspended.

Describes the type of communication function that the associated entity plays in the associated transmission.

A named tag set for metadata used to populate a security category label field that “segments” an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System) Usage Note: This is the healthcare analog to the US Intelligence Community’s concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator’s clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - “A division of data into isolated blocks with separate security controls for the purpose of reducing risk.”

There may be an issue with the patient complying with the intentions of the proposed therapy

A container intended to contain sufficient material for more than one use, but grouped or organized to provide individual access to sufficient material for a single use. Often used to ensure that the proper type and amount of material is consumed/expended for each use.

Observation values that communicate the method used in a quality measure to combine the component measure results that are included in a composite measure. Steward: CQI WG

Property identifiers for a concept code

Some conditions may be attached to an allowable substitution. An allowable substitution is based on a match to any other attributes that may be specified.

Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis

Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain “Confidentiality”.

Modifiers of role based access rights (multiple allowed) Usage Note: All codes that are referenced by this value set were retired as of the November 2013 Harmonization cycle. Guidance for what to use instead of the v:ConfidentialityModifers leaf concepts: celebrity, sensitive, and taboo: These codes have been revised and are now included under v:ActCode at:

• V:ActInformationSensitivityPolicy:2.16.840.1.113883.1.11.20429 - taboo
• V:InformationSensitivityPolicy:2.16.840.1.113883.1.11.20428 - celebrity/VIP and patient requested sensitivity

This code is used to specify the exact function an actor is authorized to have in authoring a consent directive.

Consulted prescriber, therapy confirmed

Types of contact for Role code “CON”

The type of cap associated with a container

Material intended to hold another material for purpose of storage or transport.

A material in a blood collection container that facilites the separation of of blood cells from serum or plasma

Description:Identifies the order in which content should be processed.

A code that specifies how an ActRelationship or Participation contributes to the context of an Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see also attributes Participation.contextControlCode, ActRelationship.contextControlCode, ActRelationship.contextConductionInd).

The association adds to the existing context associated with the Act. Both this association and any associations propagated from ancestor Acts are interpreted as being related to this Act.

The association adds to the existing context associated with the Act, but will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an ‘Author’ Participation were marked as “Additive, Non-Propagating” it means that the author will be added to the set of author participations that have propagated from ancestor Acts for the purpose of this Act. However only the previously propagated authors will propagate to any child Acts that allow context to be propagated.

The association adds to the existing context associated with the Act, and will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an ‘Author’ Participation were marked as “Additive, Propagating” it means that the author will be added to the set of author participations that have propagated from ancestor Acts, and will itself propagate with the other authors to any child Acts that allow context to be propagated.

The association applies only to the current Act and will not propagate to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd).

The association adds to the existing context associated with the Act, but replaces associations propagated from ancestor Acts whose typeCodes are the same.

The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. However, this overriding association will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an ‘Author’ Participation were marked as “Overriding, Non-Propagating” it means that the author will replace the set of author participations that have propagated from ancestor Acts. Furthermore, no author participations whatsoever will propagate to any child Acts that allow context to be propagated.

The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. This overriding association will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an ‘Author’ Participation were marked as “Overriding, Propagating” it means that the author will replace the set of author participations that have propagated from ancestor Acts, and will itself be the only author to propagate to any child Acts that allow context to be propagated.

The association propagates to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd).

Description:Identifies reasons for nullifying (retracting) a particular control act. Examples:“Entered in error”, “altered decision”, etc.

Identifies why a specific query, request, or other trigger event occurred.

A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction.

Countries of the world. ISO 3166, part 1, alpha-3 set.

Countries of the world. ISO 3166, part 1, alpha-2 set.

A set of codes identifying specific countries.

Description:Identifies the reason or rational for why a person is eligible for benefits under an insurance policy or program. Examples: A new employee is eligible for health insurance as an employment benefit. A person meets eligibility criteria for government program coverage based on financial, age or health status.

Description:Coded observation values for types of covered parties under a policy or program based on their personal relationships or employment status.

Description:Coded observation values for coverage limitations, for e.g., types of claims or types of parties covered under a policy or program.

Definition: Set of codes indicating the manner in which sponsors, underwriters, and payers participate in a policy or program.

Role recognized through the issuance of insurance coverage to an identified covered party who has this relationship with the policy holder such as the policy holder themselves (self), spouse, child, etc

Description:Codes that indicate a specific type of sponsor. Used when the sponsor’s role is only either as a fully insured sponsor or only as a self-insured sponsor. NOTE: Where a sponsor may be either, use the SponsorParticipationFunction.code (fully insured or self insured) to indicate the type of responsibility. (CO6-0057)

A role recognized through the eligibility of an identified living subject for benefits covered under an insurance policy or a program. Eligibility as a covered party may be conditioned on a relationship with (1) the policy holder such as the policy holder who is covered as an individual under a poliy or as a party sponsored for coverage by the policy holder. Example:An employee as a subscriber; or (2) on being scoped another covered party such as the subscriber, as in the case of a dependent. Discussion: The Abstract Value Set “CoverageRoleType”, which was developed for use in the Canadian realm “pre-coordinate” coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., “handicapped dependent”. Other codes in the Abstract Value Set CoveredPartyRoleType domain can be “post-coordinated” with the EligiblePartyRoleType codes to denote comparable concepts. Decoupling the concepts is intended to support a wider range of concepts and semantic comparability of coded concepts.

A semisolid dosage form containing one or more drug substances dissolved or dispersed in a suitable base; more recently, the term has been restricted to products consisting of oil-in-water emulsions or aqueous microcrystalline dispersions of long chain fatty acids or alcohols that are water washable and more cosmetically and aesthetically acceptable.

Recommended values for criticality observations > Steward: Security WG

Information the US Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. Purpose: Supports the selection of the entire ControlledUnclassifiedInformation value set for e.g., rules engine policy set purposes.

Information the US Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls Purpose: Supports the selection of ControlledUnclassifiedInformation leaf concepts for use, e.g., in security labels.

The currency unit as defined in ISO 4217

A practice setting where cardiovascular diagnostic procedures or therapeutic interventions are performed (e.g., cardiac catheterization lab, echocardiography suite)

Provides codes for decision methods, initially for assessing the causality of events.

A role of a place that further classifies the clinical setting (e.g., cardiology clinic, primary care clinic, rehabilitation hospital, skilled nursing facility) in which care is delivered during an encounter.

A role of a place that further classifies a setting that is intended to house the provision of non-clinical services.

A role of a place that further classifies a setting that is intended to house the provision of services.

A delivery address line is frequently used instead of breaking out delivery mode, delivery installation, etc. An address generally has only a delivery address line or a street address line, but not both.

A dentist is a person qualified by a doctorate in dental surgery (D.D. S.) or dental medicine (D.M.D.). licensed by the state to practice dentistry, and practicing within the scope of that license. Many dentists are general practitioners who handle a wide variety of dental needs. Other dentists practice in one of eight specialty areas recognized by the American Dental Association: oral and maxillofacial surgery, orthodontics, periodontics, prosthodontics, endodontics, public health, oral pathology and pediatric dentistry.

Description: A role recognized through the eligibility of a party to play a dependent for benefits covered or provided under a health insurance policy because of an association with the subscriber that is recognized by the policy underwriter.

Domain values for the Device.Alert_levelCode

A practice setting where diagnostic procedures or therapeutic interventions are performed

Diffusion

Definition: A public or government health program that administers and funds coverage for health and social services to assist program eligible who meet financial and health status criteria related to a particular disease. Example: Reproductive health, sexually transmitted disease, and end renal disease programs.

Dissolve

Identifies the current completion state of a clinical document.

The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc.

Identifies the storage status of a document.

A storage status in which a document is available on-line.

Proposed dosage instructions for therapy differ from standard practice.

Proposed length of therpay differs from standard practice

Proposed length of therapy is longer than standard practice

Proposed length of therapy is shorter than that necessary for therapeutic effect

Proposed dosage exceeds standard practice

Proposed dosage interval/timing differs from standard practice

Proposed dosage is below suggested therapeutic levels

Douche

Electro-osmosis

Description:Identifies the reason or rational for why a person is eligible for benefits under an insurance policy or program. Examples: A new employee is eligible for health insurance as an employment benefit. A person meets eligibility criteria for government program coverage based on financial, age or health status.

Broad category for individuals who complete additional training and education in the area of pre-hospital emergency services and are licensed and/or practice within the scope of that training.

A supply action where there is no ‘valid’ order for the supplied medication. E.g. Emergency vacation supply, weekend supply (when prescriber is unavailable to provide a renewal prescription)

A code qualifying the employment in various ways, such as, full-time vs. part time, etc.

Concepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment.

A code identifying special courtesies extended to the patient. For example, no courtesies, extended courtesies, professional courtesy, VIP courtesies.

Endocervical

Enema

Enteral

Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable. The value sets beneath are encoded in Entity.code and are drawn from multiple, frequently external, domains that reflect much more fine-grained typing.

A living subject from the animal kingdom.

A physical artifact that stores information about the granting of authorization.

A substance that is fully defined by an organic or inorganic chemical formula, includes mixtures of other chemical substances. Refine using, e.g., IUPAC codes.

The territory of a city, town or other municipality.

A container of other entities.

The territory of a sovereign nation.

The territory of a county, parish or other division of a state or province.

A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind of device is identified by the code attribute inherited from Entity. Usage: This includes durable (reusable) medical equipment as well as disposable equipment.

Naturally occurring, processed or manufactured entities that are primarily used as food for humans and animals.

A grouping of resources (personnel, material, or places) to be used for scheduling purposes. May be a pool of like-type resources, a team, or combination of personnel, material and places.

A health chart included to serve as a document receiving entity in the management of medical records.

A type of container that can hold other containers or other holders.

Class to contain unique attributes of diagnostic imaging equipment.

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

Corresponds to the ManufacturedMaterial class

Any thing that has extension in space and mass, may be of living or non-living origin.

All single celled living organisms including protozoa, bacteria, yeast, viruses, etc.

A politically organized body of people bonded by territory and known as a nation.

A social or legal structure formed by human beings.

A living subject of the species homo sapiens.

A physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant.

A living subject from the order of plants.

An agency of the people of a state often assuming some authority over a certain matter. Includes government, governmental agencies, associations.

Corresponds to the Entity class

A politically organized body of people bonded by territory, culture, or ethnicity, having sovereignty (to a certain extent) granted by other states (enclosing or neighboring states). This includes countries (nations), provinces (e.g., one of the United States of America or a French departement), counties or municipalities. Refine using, e.g., ISO country codes, FIPS-PUB state codes, etc.

The territory of a state, province, department or other division of a sovereign country.

A value representing the specific kind of Entity the instance represents. Examples: A medical building, a Doberman Pinscher, a blood collection tube, a tissue biopsy. Rationale: For each Entity, the value for this attribute is drawn from one of several coding systems depending on the Entity classCode, such as living subjects (animal and plant taxonomies), chemical substance (e.g., IUPAC code), organizations, insurance company, government agency, hospital, park, lake, syringe, etc. It is possible that Entity.code may be so fine grained that it represents a single instance. An example is the CDC vaccine manufacturer code, modeled as a concept vocabulary, when in fact each concept refers to a single instance.

EntityDeterminer in natural language grammar is the class of words that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing.

A standard value set allowing reference to all EntityDeterminer codes that are equal to or specializations of GROUPKIND. This is the value set used when a model indicates that the binding is to “<= GROUPKIND”.

The described quantified determiner indicates that the given Entity is taken as a general description of a specific amount of a thing. For example, QUANTIFIED_KIND of syringe (quantity = 3,) stands for exactly three syringes.

The described determiner is used to indicate that the given Entity is taken as a general description of a kind of thing that can be taken in whole, in part, or in multiples.

The specific determiner indicates that the given Entity is taken as one specific thing instance. For example, a human INSTANCE (quantity = 1,) stands for exactly one human being.

A standard value set allowing reference to all EntityDeterminer codes that are equal to or specializations of GROUP. This is the value set used when a model indicates that the binding is to “<= GROUP”.

Special handling requirements for an Entity. Example:Keep at room temperature; Keep frozen below 0 C; Keep in a dry environment; Keep upright, do not turn upside down.

EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute. May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy. Role.confidentialityCode is defined in the RIM as “an indication of the appropriate disclosure of information about this Role with respect to the playing Entity.”

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

Description:Indicates whether the name part is a given name, family name, prefix, suffix, etc.

Description:A set of codes advising a system or user which name in a set of names to select for a given purpose.

The vocabulary table for the Entity.riskCode attribute

Codes representing the defined possible states of an Entity, as defined by the Entity class state machine.

The state representing the fact that the Entity record is currently active.

Definition: The state representing the fact that the entity is inactive.

The ‘typical’ state. Excludes “nullified” which represents the termination state of an Entity record instance that was created in error.

The state representing the termination of an Entity record instance that was created in error.

Epidural

Description: The EPSG (European Petroleum Survey Group) dataset represents all Datums, coordinate references (projected and 2D geographic) and coordinate systems (including Cartesian coordinate systems) used in surveying worldwide. Each record includes a 4-8 digit unique identifier. The current version is available from http://www.epsg.org/. The database contains over 4000 records covering spatial data applications worldwide.

The section of a health care facility for providing rapid treatment to victims of sudden illness or trauma.

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

An occurrence that is scheduled to occur in the future. An Act whose effective time is greater than ‘now’, where ‘now’ is the time the instance is authored.

Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.

A solid dosage form in which the drug is enclosed within either a hard or soft soluble container made from a suitable form of gelatin, and which releases a drug (or drugs) in such a manner to allow a reduction in dosing frequency as compared to that drug (or drugs) presented as a conventional dosage form.

A solid dosage form containing a drug which allows at least a reduction in dosing frequency as compared to that drug presented in conventional dosage form.

Extra-amniotic

Extracorporeal circulation

A relationship between two people characterizing their “familial” relationship

The initial fill against an order. (This includes initial fills against refill orders.)

Flush

(abstract) Defines font rendering characteristics

The player of the role is a child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties.

Any elastic aeriform fluid in which the molecules are separated from one another and have free paths.

Gastric

A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid.

A value representing whether the primary reproductive organs of NonPersonLivingSubject are present.

(X12N 282N00000N)

Supports communication of purpose of use at a general level.

Description:Identifies why a change is being made to a record.

Codes that specify interpretation of genetic analysis, such as “positive”, “negative”, “carrier”, “responsive”, etc.

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

Description: Identifies the kinds of genetic observations that can be performed.

Description: The domain contains genetic analysis specific observation values, e.g. Homozygote, Heterozygote, etc.

Genitourinary

A practice setting where GI procedures (such as endoscopies) are performed

Gingival

The player of the role is a child of the scoping person’s son or daughter.

parent of a parent of the subject

The player of the role is a parent of the scoping person’s grandparent.

Description:Global Trade Item Number is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council).

Description:Basic abbreviations defined for the General timing Specification data type.

Holidays

Christian Holidays (Roman/Gregorian “Western” Tradition.)

United States National Holidays (public holidays for federal employees established by U.S. Federal law 5 U.S.C. 6103.)

Description:Other, more specific, abbreviations defined for the General timing Specification data type, that are specializations of one of the Base concepts.

Hair

The player of the role is related to the scoping entity by sharing only one biological parent.

This value set includes all HCPCS Level II codes.

A comprehensive classification of locations and settings where healthcare services are provided. This value set is based on the NHSN location code system that has been developed over a number of years through CDCaTMs interaction with a variety of healthcare facilities and is intended to serve a variety of reporting needs where coding of healthcare service locations is required. This valu set is aavailalbe from VSAC at https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.1.11.20275/expansion/Latest

Proposed therapy may be inappropriate based on the patient’s height or body surface area

Description:Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type.

The HL7-FormatCodes value set is defined to be the set of FormatCode(s) defined by implementation guides published by HL7 and other SDOs. The use of a formatCode from the FormatCodes value set specifies the technical format that a document conforms to. The formatCode is a further specialization more detailed than the mime-type. The formatCode provides sufficient information to allow any potential document content consumer to know if it can process and/or display the content of the document based on the document encoding, structure and template conformance indicated by the formatCode. The set of formatCodes is intended to be extensible. The Content Logical Description is defined intentionally to permit formatCodes defined by other Standards Development Organizations to be added by inclusion of additional formatCode Code Systems.

HL7 implementation technology specification versions. These codes will document the ITS type and version for message encoding. The code will appear in the instances based upon rules expressed in the ITS, and do not appear in the abstract message, either as it is presented to received from the ITS.

This is the domain of HL7 version codes for the Version 3 standards. Values are to be determined by HL7 and added with each new version of the HL7 Standard.

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

Definition: Living arrangements lacking a permanent residence.

An acute care institution that provides medical, surgical, or psychiatric care and treatment for the sick or the injured.

HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the current document and the anchor that is the target of the link

Codes for the representation of the names of human languages.

The set of body locations to or through which a drug product may be administered.

Description: The identifier was issued by the system responsible for constructing the instance.

Description: Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II.

Image media type.

Set of LOINC codes that identify the type of date that is specified within an immunization forecast step.

Represents the patient’s status with respect to their immunization guideline as of an evaluation date.

Description: Indicates the valid antigen count.

Implantation

All codes from code system ActCode._IndividualCaseSafetyReportType

DescriptionA role recognized through the eligibility of a party to play an individual insured for benefits covered or provided under an insurance policy where the party is also the policy holder.

Container intended to contain sufficient material for only one use.

Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an “employee” sensitivity code would make little sense for use outside of a policy domain. “Taboo” would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system’s Master Files in order to notify those who access a patient’s orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy’s criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.title.

Infusion

Inhalation

A small device used for inhaling medicine in the form of a vapour or gas in order to ease a respiratory condition such as asthma or to relieve nasal congestion.

Injection

A device intended to administer liquid into a subject via a

Insertion

Instillation

Institution

Interameningeal

Interstitial

Intra-abdominal

Injection, intraarterial

Intra-arterial

Intraarticular

Intrabronchial

Intrabursal

Injection, intracardiac

Intracardiac

Intracartilaginous

Intracaudal

Intracavernosal

Intracavitary

Intracerebral

Intracervical

Intracisternal

Intracorneal

Intracoronal (dental)

Injection, intracoronary

Intracoronary

Intracorpus cavernosum

Intradermal

Intradiscal

Intraductal

Intraduodenal

Intradural

Intraepidermal

Intraepithelial

Intraesophageal

Intragastric

Intraileal

Intralesional

Intraluminal

Intralymphatic

Intramedullary

Injection, intramuscular

Intramuscular

Intraocular

Intraosseous

Intraovarian

Intrapericardial

Intraperitoneal

Intrapleural

Intraprostatic

Intrapulmonary

Intrasinal

Intraspinal

Intrasternal

Intrasynovial

Intratendinous

Intratesticular

Intrathecal

Intrathoracic

Intratracheal

Intratubular

Intratumor

Intratympanic

Intrauterine

Intravascular

Infusion, intravenous

Injection, intravenous

Intravenous

Intraventricular

Intravesicle

Intravitreal

Total counts and total net amounts adjudicated for all Invoice Groupings that were adjudicated within a time period based on the adjudication date of the Invoice Grouping.

Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date.

Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included.

Iontophoresis

Irrigation

A sterile solution intended to bathe or flush open wounds or body cavities; they’re used topically, never parenterally.

Description:Indicates how result sets should be filtered based on whether they have associated issues.

Jejunum

A container for a diverse collection of products intended to be used together for some purpose (e.g. Medicinal kits often contain a syringe, a needle and the injectable medication).

Observation values used to indicate a knowledge subject of interest for which knowledge content is requested (e.g., a medication, a laboratory test, a medical condition).

Observation values used to indicate a knowledge subtopic of interest for which knowledge content is requested (e.g., treatment, etiology, prognosis).

Value Set of codes specifying an observation sub-type used with observation type code RSLT (Result).

Description:Trigger Event ID as published in the standard.

Lacrimal puncta

A value representing the method of expression of the language. Example:Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.