Product CMET

Product Brief - HL7 V3: Common Message Element Types

back to Main_Page
back to Product_List

Product Name

HL7 V3: Common Message Element Types

Topics

Balloted CMETs:
AM – Administrative Management (Section)

• PR – Subsection: Practice
  • PA: Domain: Patient Administration
  • PM: Domain: Personnel Management
  • SC: Domain: Scheduling
• FI -- Subsection: Financial
  • CR: Domain: Claims and Reimbursement
  • AB: Domain: Accounting and Billing
  • CO: Domain: Coverage

HM – Health and Clinical Management (Section)

• PO – Subsection: Operations
  • CG: Domain: Clinical Genomics
  • CP: Common Product Model
  • II - Imaging Integration CMET: A_DicomCompositeObjectReference minimal
  • LB: Domain: Laboratory
  • ME: Domain: Medication
  • OB: Observations
  • PH: Public Health
  • RX: Domain: Pharmacy
  • SP: Specimen Handling
• RE – Subsection: Reasoning
  • PC: Domain: Care Provision (Formerly Patient Care)
• RC – Subsection: Records
  • MR: Domain: Medical Records

IM – Infrastructure Management (Section)

• CO – Subsection: Common Message Elements (CMETs)
  • CS: Domain: Clinical Statement
  • CT: Domain: Common Message Elements
• MC – Subsection: Message Control
  • AI: Message Control Act Infrastructure
• MF – Subsection: Master File Management
  • MI: Domain: Master File Infrastructure
• QU – Subsection: Query
  • PA: Domain: Patient Administration

Standard Category

• Health Information Exchange Standards

Integration Paradigm

• Messaging

Type

Normative, ANSI Standard

Releases

ANSI/HL7 V3 CMET, R1-2005, R2-2009

Summary

Common Message Element Types (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.

Description

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

Business Case (Intended Use, Customers)

CMETs (Common Message Element Types) are a work product produced by a particular committee for expressing a common, useful and reusable concept. They are generally "consumed", or used by both the producing committee and other committees.

CMETs are now (as of January 2010) balloted at the topic level by the individual working groups, who now provide direct stewardship over them. 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.

Resources

Work Groups

Modeling and Methodology

Education

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

Links to current projects in development

• Project Insight ID # 221, Common Message Element Types (COCT) Release 8

See also search on Project Insight Database for 'CMET' here

• Project Insight ID # 249, HL7 V3 Std: Pharmacy, Release 1: Pharmacy CMETs
• Project Insight ID # 349, Laboratory Related CMETs
• Project Insight ID # 350, Public Health Related CMETs
• Project Insight ID # 361, Patient Administration Derived CMETs
• Project Insight ID # 362, Account and Billing CMETs
• Project Insight ID # 459, Scheduling CMETs
• Project Insight ID # 474, CMET: A_DicomCompositeObjectReference minimal (COCT_RM830120UV05) R2
• Project Insight ID # 557, Medication CMETS
• Project Insight ID # 565, Specimen Handling CMET
• Project Insight ID # 574, Personnel Management CMETs