Product RX

Product Brief - V3 Domain: Pharmacy

back to Main_Page
back to Product_List

Product Name

HL7 V3 RX, R1: HL7 Version 3 Standard: Pharmacy, Release 1
Topic Level Ballots: January 2010

Topics

ANSI/HL7 V3 RXMEDORDER, R1-2009 - HL7 Version 3 Standard: Pharmacy: Medication Order, Release 1
HL7 V3 RX MDSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Dispense and Supply Event, Release 1

Normative Ballot 2 - January 2010

HL7 V3 RX MSSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Statement, Release 1

Normative Ballot 1 - January 2010

HL7 V3 RX CMETs, R1 - HL7 Version 3 Standard: Pharmacy CMETs, Release 10

Normative Ballot 2 - January 2010

Non-normative (draft) topics not having balloted for more than a year:

• Common Order
• Device Order
• Common Dispense & Supply Event
• Device Dispense & Supply Event
• Generic Patient-Related Pharmacy Query
• Patient Medication Contraindication Query
• Pharmacy Proposed Shared Messages
• Pharmacy Proposed CMETs
• Appendix - Patient-Related Medication Query
• Appendix - Patient-related Device Query
• Appendix - Dosage Instruction
• Appendix - Dose Form Vocabulary
• Appendix - International Specifications

Standard Category

• Health Information Exchange Standards

Integration Paradigm

• Messaging

Type

• Normative, ANSI standard (RXMEDORDER)
• Normative, not yet published (RX MDSE)
• balloting Normative (MSSE, CMETs)

Releases

ANSI/HL7 V3 RXMEDORDER, R1-2009
HL7 V3 RX MDSE, R1 - 2009Sep Normative ballot

Summary

This standard will include support for Prescribing, Dispensing and Administration messages, as well as 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 (POME) which defines the overall description of a medicine.

Description

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

As a high level model, it may not appear to mimic exactly real life objects or classes. 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. We also have to recognize that each class will progress through a number of distinct moods before the business process is complete eg. substance administration in the mood of order (as on a prescription) and also substance administration in the mood of event (as in a notification of administration). Overall the DMIM is a tool to assist the process of generating specific pharmacy message models and is not intended to be used by those unfamiliar with HL7 Version 3 modeling.

Business Case (Intended Use, Customers)

Vendors: Healthcare IT Vendors: Pharmaceutical Providers: Pharmacy Providers: Healthcare Institutions

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

Resources

Work Groups

Pharmacy WG

Education

• See more at http://www.hl7.org/implement/training.cfm

Links to current projects in development

• Project Insight ID # 558, Medication Order Release 2
• Project Insight ID # 249, HL7 V3 Std: Pharmacy, Release 1: Pharmacy CMETs
• Project Insight ID # 244, HL7 V3 Std: Pharmacy, Release 1: Medication Statement and Supply Event
• Project Insight ID # 242, HL7 V3 Std: Pharmacy, Release 1: Medication Dispense and Supply Event
• Project Insight ID # 241, HL7 V3 Std: Pharmacy, Release 1: Generic Patient-Related Pharmacy Query
• Project Insight ID # 240, HL7 V3 Std: Pharmacy, Release 1: Dosage Instruction
• Project Insight ID # 236, HL7 V3 Std: Pharmacy, Release 1: Common Order
• Project Insight ID # 189, HL7 V3 Std: Medication, Release 1: Drug Knowledge-Base Query