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

Difference between revisions of "Product CMET"

From HL7Wiki
Jump to navigation Jump to search
(New page: ==Product Brief - HL7 V3: Common Message Element Types== back to Main_Page<br/>back to Product_List ===Product Name=== HL7 V3: Common Message Element Types ===Topics=== *Common Me...)
 
 
(5 intermediate revisions by the same user not shown)
Line 5: Line 5:
  
 
===Topics===
 
===Topics===
−
*Common Message Element Types R9;
+
Balloted CMETs:<br/>
−
*Clinical genomics;
+
AM – Administrative Management (Section)
−
*Imaging Integration,
+
*Practice (Subsection)
−
*Pharmacy,
+
**PA: Patient Administration
−
*Common Product Model
+
**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===
 
===Standard Category===
 
*Health Information Exchange Standards
 
*Health Information Exchange Standards
Line 28: Line 61:
 
===Business Case (Intended Use, Customers)===
 
===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 (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===
 
===Benefits===
  
−
 
+
<!--
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
−
 
+
-->
 
===Resources===
 
===Resources===
  
Line 39: Line 74:
 
[http://www.hl7.org/Special/committees/mnm/index.cfm Modeling and Methodology]
 
[http://www.hl7.org/Special/committees/mnm/index.cfm Modeling and Methodology]
 
====Education====
 
====Education====
−
 
 
* See more at http://www.hl7.org/implement/training.cfm
 
* See more at http://www.hl7.org/implement/training.cfm
−
=====Certification Available=====
+
<!--
−
*none
 
−
 
 
 
====Presentations====
 
====Presentations====
 
*
 
*
 
===Relationship to/ Dependencies on, other standards===
 
===Relationship to/ Dependencies on, other standards===
−
*
+
*-->
 
===Links to current projects in development===
 
===Links to current projects in development===
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=221 Project Insight ID # 221], Common Message Element Types (COCT) Release 8
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=221 Project Insight ID # 221], Common Message Element Types (COCT) Release 8
Line 57: Line 89:
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=361 Project Insight ID # 361], Patient Administration Derived CMETs
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=361 Project Insight ID # 361], Patient Administration Derived CMETs
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=362 Project Insight ID # 362], Account and Billing CMETs
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=362 Project Insight ID # 362], Account and Billing CMETs
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=456 Project Insight ID # 456], Common Product Model (CMETs)
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=459 Project Insight ID # 459], Scheduling CMETs
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=459 Project Insight ID # 459], Scheduling CMETs
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=474 Project Insight ID # 474], CMET: A_DicomCompositeObjectReference minimal (COCT_RM830120UV05) R2
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=474 Project Insight ID # 474], CMET: A_DicomCompositeObjectReference minimal (COCT_RM830120UV05) R2
Line 62: Line 95:
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=565 Project Insight ID # 565], Specimen Handling CMET
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=565 Project Insight ID # 565], Specimen Handling CMET
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=574 Project Insight ID # 574], Personnel Management CMETs
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=574 Project Insight ID # 574], Personnel Management CMETs
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=617 Project Insight ID # 617], Laboratory Related CMETs R2
 +
 +
[[Category:Products]]

Latest revision as of 21:34, 10 March 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

Modeling and Methodology

Education

Links to current projects in development

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

Retrieved from "https://wiki.hl7.org/w/index.php?title=Product_CMET&oldid=33708"