×

HL7's new AMS is live!   We are working with Fonteva to resolve log in issues. My Account

Section 1e: Version 3 (V3)
Section 2: Clinical and Administrative Domains

HL7 Version 3 Standard: Pharmacy CMETs

DESCRIPTION

The Pharmacy domain covers community prescribing, discharge prescriptions and institutional medication orders. The models are intended to support the requirements of all jurisdictions. This standard will include support for prescribing, dispensing and administration messages, as well as prescription (Rx) status management, active medications and patient Rx queries. This domain is used to derive message patterns to describe and communicate processes related to medication. The primary real life processes being represented are the making of a prescription or medication order, the organizing of a supply of a medication and the administration of the medication to a patient. It differs from the Medication domain, which defines the overall description of a medicine.

 

CMETs (Common Model Element Types) are a work product produced by a particular work group for expressing a common, useful and reusable concept. They are generally "consumed", or used by both the producing and other work groups. CMETs are standardized model fragments intended to be building blocks that individual content domains can "include" in their designs. These blocks reduce the effort to produce a domain-specific design and assure that similar content across multiple domains is consistently represented. The Medication domain defines the overall description of a medicine and these CMETs provide the means to represent Medication consistently.

ALTERNATIVE NAMES

HL7 Version 3 Standard: Pharmacy CMETs may also go by the following names or acronyms:

"Reaffirmation of HL7 Version 3 Standard: Pharmacy CMETs, Release 1", "Reaffirmation of HL7 Version 3 Standard: Pharmacy; Medication CMET, Release 1", "V3: Pharmacy; Medication Order, Release 1", RX, V3: Pharmacy: Medication CMETs, R1, Pharmacy CMETS

TARGETS

  • Clinical and Public Health Laboratories
  • Regulatory Agency
  • Payors
  • EHR, PHR, Vendors
  • Healthcare IT Vendors
  • Pharmaceutical Vendors
  • Clinical Decision Support Systems Vendors
  • Lab Vendors
  • Pharmacy
  • Emergency Services Providers
  • Local and State Departments of Health
  • Healthcare Institutions (hospitals, long term care, home care, mental health)

BENEFITS

This standard allows for consistent communication of a Medication Process. It can communicate using a role as the "header" (something that can be used to "hold together" the other acts of substance administration and supply) that are intimately related and in some senses equally important in the clinical process for a Pharmacy communication. Its messages also function as a holder for information related to the whole process of administration and supply. It can be used as a representation of a "prescription" or of a "line item" and indeed when necessary may be cloned and unrolled to represent both a prescription and a line item within the prescription.

  • The Medication Order topic deals with all content related to the ordering of medications, both for dispensing (supply) and for administration. It is intended to cover community prescribing, discharge prescriptions and institutional medication orders. The models are intended to support the requirements of all jurisdictions
  • The Medication Dispense and Supply Event topic covers the issuing of medication to a patient or representative, as well as bulk supplies of medication
  • The Medication Statement topic deals with the recording of statements about which medications the patient has received or is receiving through mechanisms other than a prescription, dispense or administration. Examples include over the counter medications and patient statements (e.g. patient informs physician of a medication received while on vacation)
  • These Medication CMETs provide consistency in referencing Medication models in other v3 domains. They provide three different ways of referring to a medication - the billing space, the ordering space, and the administering space - as well as a means to fully catalog a medication and its ingredients. They support the use of standards in the Pharmaceutical domain.

IMPLEMENTATIONS/CASE STUDIES

  • In development

DEVELOPMENT BACKGROUND

Analysis of the way this real life process works in systems terms requires some of the real life objects to be represented as more than one class: for example, a prescription can be viewed as a "header" with a medication administration and supply order. As a high-level model, it may not appear to mimic exactly real life objects or classes. We also have to recognize that each class will progress through a number of distinct moods before the business process is complete e.g. substance administration in the mood of order (as on a prescription) and substance administration in the mood of event (as in a notification of administration).

RELATED DOCUMENTS

HL7 Version 3 Standard: Pharmacy CMETs

(Download) (131.60 MB)

HL7 Version 3 Standard: Pharmacy: Medication Dispense and Supply Event, R2 (View Brief)

(Download) (131.60 MB)

HL7 Version 3 Standard: Pharmacy; Medication Knowledge-Base Query, Release 1 (View Brief)

(Download) (131.60 MB)

HL7 Version 3 Standard: Pharmacy; Medication Statement and Administration Event, Release 1 (View Brief)

(Download) (156.94 MB)

TOPIC

  • Pharmacy

BALLOT TYPE

  • Normative

STATUS DATE

2019-05-24

RESPONSIBLE WORK GROUP

Pharmacy

PRODUCT TYPE

  • ANSI-approved

STAKEHOLDERS

  • Clinical and Public Health Laboratories
  • Clinical Decision Support Systems Vendors
  • Emergency Services Providers
  • Healthcare Institutions
  • Lab Vendors
  • Local and State Departments of Health
  • Payors
  • Pharmaceutical Vendors
  • Regulatory Agency

FAMILY

  • V3

CURRENT STATE

  • Stable

REALM

  • Universal