Section 6: Rules and References

HL7 Version 3 Standard: Common Message Element Types

DESCRIPTION

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.

As of January 2010, CMETs are now balloted at the topic level by the individual work groups responsible for those topics. All CMETs that pass membership ballot during the Normative Edition year will become part of that normative edition, as an incremental update to the standard.

ALTERNATIVE NAMES

HL7 Version 3 Standard: Common Message Element Types may also go by the following names or acronyms:

"V3: Common Product Model, R1", "V3: Pharmacy: Medication CMETs, R9", "V3: Pharmacy CMETs, R8", "V3: Common Message Element Types, R2", "V3: Common Message Element Types, R3", CMET, CMETS, RX, Medication CMETs, CPM, CP

TARGETS

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

BENEFITS

  • Enhances and is a foundation for the implementation of Version 3 models used in messages and documents
  • Assures that similar content across multiple domains is consistently represented
  • Enables V3 messaging by providing a consistent representation of common data constructs
  • Enables CPM listing or registering all drug products legally marketed in the US

IMPLEMENTATIONS/CASE STUDIES

  • CMETS have been used in several normative HL7 specifications and are in use in the United Kingdom, Canada and the Netherlands
  • The FDA is now using the CPM for listing medical devices in the Global Unique Device Identification Database
  • Hundreds of US domestic, non-US (international), and multi-national companies, small and large are submitting their product descriptions encoded using the CPM.

DEVELOPMENT BACKGROUND

A CMET can be envisioned as a message type fragment that is reusable by other message types. Any message type can reference a CMET, including other CMETs. As an example, several work groups  may require the use of a common concept, that of a person in the role of a patient. A CMET can be defined to express this concept as a message type that clones a role played by a person, with all appropriate attributes. The CMET is then used to uniformly represent the concept for all interested work groups.

 

CMETs 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 work group and other work groups.

 

 

RESPONSIBLE WORK GROUPS

Modeling and Methodology

Orders and Observations

Pharmacy

RELATED DOCUMENTS

HL7 Version 3 Standard: Common Message Element Types

ADDITIONAL DETAILS

CMETs created in the Pharmacy Domain address key constructs such as Medication Order, Substance Administration and Detected Medication Issue.

Common Product Model CMETs, the product model data structures and the XML schema encoding them have been in use since the early 2000s, and particularly since 2009 for registering ("listing") all drug products legally marketed on in the US. Hundreds of US domestic, non-US (international), and multi-national companies, small and large are submitting their product descriptions encoded using the CPM. The CPM now supports US CMS MEDICARE billing as well as the RxNORM clinical drug terminology management.