Difference between revisions of "Product CMET"
(→Topics) |
(→Topics) |
||
Line 7: | Line 7: | ||
Balloted CMETs:<br/> | Balloted CMETs:<br/> | ||
AM – Administrative Management (Section) | AM – Administrative Management (Section) | ||
− | * | + | *Practice (Subsection) |
− | **PA | + | **PA: Patient Administration |
− | **PM | + | **PM: Personnel Management |
− | **SC | + | **SC: Scheduling |
− | * | + | *Financial (Subsection) |
− | **CR | + | **CR: Claims and Reimbursement |
− | **AB | + | **AB: Accounting and Billing |
− | **CO | + | **CO: Coverage |
− | + | ||
− | * | + | Health and Clinical Management (Section) |
− | **CG | + | *Operations (Subsection) |
+ | **CG: Clinical Genomics | ||
**CP: Common Product Model | **CP: Common Product Model | ||
− | **II | + | **II: Imaging Integration |
− | **LB | + | **LB: Laboratory |
− | **ME | + | **ME: Medication |
**OB: Observations | **OB: Observations | ||
− | **PH: Public Health | + | **PH: Public Health |
− | **RX: | + | **RX: Pharmacy |
+ | **RP: Regulated Products | ||
+ | **RR: Regulated Reporting | ||
**SP: Specimen Handling | **SP: Specimen Handling | ||
− | * | + | *Reasoning (Subsection) |
− | **PC | + | **PC: Care Provision |
− | * | + | *Records (Subsection) |
− | **MR | + | **MR: Medical Records |
− | + | ||
− | * | + | Infrastructure Management (Section) |
− | **CS | + | *CMETs (Subsection) |
− | **CT | + | **CS: Clinical Statement |
− | * | + | **CT: Common Message Elements (no domain) |
+ | *Message Control (Subsection) | ||
**AI: Message Control Act Infrastructure | **AI: Message Control Act Infrastructure | ||
− | * | + | *Master File Management (Subsection) |
− | **MI | + | **MI: Master File Infrastructure |
− | |||
− | |||
===Standard Category=== | ===Standard Category=== |
Revision as of 16:01, 5 February 2010
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)
- Practice (Subsection)
- PA: Patient Administration
- PM: Personnel Management
- SC: Scheduling
- Financial (Subsection)
- CR: Claims and Reimbursement
- AB: Accounting and Billing
- CO: Coverage
Health and Clinical Management (Section)
- Operations (Subsection)
- CG: Clinical Genomics
- CP: Common Product Model
- II: Imaging Integration
- LB: Laboratory
- ME: Medication
- OB: Observations
- PH: Public Health
- RX: Pharmacy
- RP: Regulated Products
- RR: Regulated Reporting
- SP: Specimen Handling
- Reasoning (Subsection)
- PC: Care Provision
- Records (Subsection)
- MR: Medical Records
Infrastructure Management (Section)
- CMETs (Subsection)
- CS: Clinical Statement
- CT: Common Message Elements (no domain)
- Message Control (Subsection)
- AI: Message Control Act Infrastructure
- Master File Management (Subsection)
- MI: Master File Infrastructure
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.
Benefits
Resources
Work Groups
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