This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Product RX"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 5: Line 5:
  
 
HL7 V3 RX, R1: HL7 Version 3 Standard: Pharmacy, Release 1<br/>
 
HL7 V3 RX, R1: HL7 Version 3 Standard: Pharmacy, Release 1<br/>
Topic Level Ballots: January 2010
+
 
 +
 
 +
 
 
===Topics===
 
===Topics===
ANSI/HL7 V3 RXMEDORDER, R1-2009 - HL7 Version 3 Standard: Pharmacy: Medication Order, Release 1<br/>
+
Topic Level Ballots:
HL7 V3 RX MDSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Dispense and Supply Event, Release 1
+
 
:Normative Ballot 2 - January 2010<br/>
+
*ANSI/HL7 V3 RXMEDORDER, R1-2009 - HL7 Version 3 Standard: Pharmacy: Medication Order, Release 1
HL7 V3 RX MSSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Statement, Release 1
+
*HL7 V3 RX MDSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Dispense and Supply Event, Release 1 (N3 - 2010May)
:Normative Ballot 1 - January 2010<br/>
+
*HL7 V3 RX MSSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Statement, Release 1 (N2 - 2010May)
HL7 V3 RX CMETs, R1 - HL7 Version 3 Standard: Pharmacy CMETs, Release 10
+
*HL7 V3 RX CMETs, R1 - HL7 Version 3 Standard: Pharmacy CMETs, Release 10 (N2 - January 2010)
:Normative Ballot 2 - January 2010<br/>
+
*HL7 V3 RX CMNORDER R1 - HL7 Version 3 Standard: Pharmacy; Common Order, Release 1 (N1 - 2010May)
 +
*HL7 V3 RX CDSE R1 - HL7 Version 3 Standard: Pharmacy; Common Dispense and Supply Event, Release 1 (N1 - 2010May)
 +
* HL7 V3 RX DKBQ R1 - HL7 Version 3 Standard: Pharmacy; Medication Knowledge-Base Query, Release 1 (N4 - 2010Sept) (formerly part of Medication domain)
  
  
 
Non-normative (draft) topics not having balloted for more than a year:
 
Non-normative (draft) topics not having balloted for more than a year:
*Common Order
+
*Device Order (I1 - 2007May)
*Device Order  
+
*Device Dispense & Supply Event (I1 - 2007May)
*Common Dispense & Supply Event
+
*Generic Patient-Related Pharmacy Query (O2 - 2007May)
*Device Dispense & Supply Event  
+
*Patient Medication Contraindication Query (I1 - 2007May)
*Generic Patient-Related Pharmacy Query  
+
*Appendix - Patient-Related Medication Query (I2 - 2007May)
*Patient Medication Contraindication Query  
+
*Appendix - Patient-related Device Query (I2 - 2007May)
*Pharmacy Proposed Shared Messages
+
*Appendix - Dosage Instruction (O2 - 2007May)
*Pharmacy Proposed CMETs
+
*Appendix - Dose Form Vocabulary (O1 - 2007May)
*Appendix - Patient-Related Medication Query  
+
 
*Appendix - Patient-related Device Query  
+
 
*Appendix - Dosage Instruction  
 
*Appendix - Dose Form Vocabulary  
 
*Appendix - International Specifications
 
 
===Standard Category===
 
===Standard Category===
 
*Health Information Exchange Standards
 
*Health Information Exchange Standards
Line 36: Line 37:
 
===Type===
 
===Type===
 
*Normative, ANSI standard (RXMEDORDER)
 
*Normative, ANSI standard (RXMEDORDER)
*Normative, not yet published (RX MDSE)
+
*balloting Normative (RX MDSE, MSSE, CMETs, CMNORDER, CDSE, DKBQ)
*balloting Normative (MSSE, CMETs)
 
  
 
===Releases===
 
===Releases===
 
ANSI/HL7 V3 RXMEDORDER, R1-2009<br/>
 
ANSI/HL7 V3 RXMEDORDER, R1-2009<br/>
HL7 V3 RX MDSE, R1 - 2009Sep Normative ballot
+
HL7 V3 RX MDSE, R1 - 2010May Normative ballot
  
 
===Summary===
 
===Summary===
This 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.  
+
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===
 
===Description===
This message model represents data and associations involved in the creation and storage of a patient's medication order. The order process includes content/concepts related to ordering, dispensing (supply) and administration of prescribed items.
+
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).  
 +
 
 +
The Drug Knowledge-Base Query topic  covers the issuing of queries to drug knowledge base applications for such information as drug monographs, regimens and therapies.
 +
 
 +
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)===
 
===Business Case (Intended Use, Customers)===
 
+
*Vendors: Healthcare IT
 +
*Vendors: Pharmaceutical
 +
*Providers: Pharmacy
 +
*Providers: Healthcare Institutions
  
 
===Benefits===
 
===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.
  
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
Line 73: Line 84:
 
===Links to current projects in development===
 
===Links to current projects in development===
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=558 Project Insight ID # 558], Medication Order Release 2
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=558 Project Insight ID # 558], Medication Order Release 2
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=249 Project Insight ID # 249], HL7 V3 Std: Pharmacy, Release 1: Pharmacy CMETs
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=244 Project Insight ID # 244], HL7 V3 Std: Pharmacy, Release 1: Medication Statement and Supply Event
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=242 Project Insight ID # 242], HL7 V3 Std: Pharmacy, Release 1: Medication Dispense and Supply Event
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=241 Project Insight ID # 241], HL7 V3 Std: Pharmacy, Release 1: Generic Patient-Related Pharmacy Query
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=240 Project Insight ID # 240], HL7 V3 Std: Pharmacy, Release 1: Dosage Instruction
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=236 Project Insight ID # 236], HL7 V3 Std: Pharmacy, Release 1: Common Order
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=189 Project Insight ID # 189], HL7 V3 Std: Medication, Release 1: Drug Knowledge-Base Query

Latest revision as of 19:18, 5 November 2010

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


Topics

Topic Level Ballots:

  • 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 (N3 - 2010May)
  • HL7 V3 RX MSSE, R1 - HL7 Version 3 Standard: Pharmacy; Medication Statement, Release 1 (N2 - 2010May)
  • HL7 V3 RX CMETs, R1 - HL7 Version 3 Standard: Pharmacy CMETs, Release 10 (N2 - January 2010)
  • HL7 V3 RX CMNORDER R1 - HL7 Version 3 Standard: Pharmacy; Common Order, Release 1 (N1 - 2010May)
  • HL7 V3 RX CDSE R1 - HL7 Version 3 Standard: Pharmacy; Common Dispense and Supply Event, Release 1 (N1 - 2010May)
  • HL7 V3 RX DKBQ R1 - HL7 Version 3 Standard: Pharmacy; Medication Knowledge-Base Query, Release 1 (N4 - 2010Sept) (formerly part of Medication domain)


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

  • Device Order (I1 - 2007May)
  • Device Dispense & Supply Event (I1 - 2007May)
  • Generic Patient-Related Pharmacy Query (O2 - 2007May)
  • Patient Medication Contraindication Query (I1 - 2007May)
  • Appendix - Patient-Related Medication Query (I2 - 2007May)
  • Appendix - Patient-related Device Query (I2 - 2007May)
  • Appendix - Dosage Instruction (O2 - 2007May)
  • Appendix - Dose Form Vocabulary (O1 - 2007May)


Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Messaging

Type

  • Normative, ANSI standard (RXMEDORDER)
  • balloting Normative (RX MDSE, MSSE, CMETs, CMNORDER, CDSE, DKBQ)

Releases

ANSI/HL7 V3 RXMEDORDER, R1-2009
HL7 V3 RX MDSE, R1 - 2010May 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).

The Drug Knowledge-Base Query topic covers the issuing of queries to drug knowledge base applications for such information as drug monographs, regimens and therapies.

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.

Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Pharmacy WG

Education

Links to current projects in development