Difference between revisions of "Product CMET"
(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...) |
|||
Line 31: | Line 31: | ||
===Benefits=== | ===Benefits=== | ||
− | + | <!-- | |
===Implementations/ Case Studies (Actual Users)=== | ===Implementations/ Case Studies (Actual Users)=== | ||
− | + | --> | |
===Resources=== | ===Resources=== | ||
Line 39: | Line 39: | ||
[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 | ||
− | + | <!-- | |
− | |||
− | |||
====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 |
Revision as of 16:06, 10 November 2009
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
- Common Message Element Types R9;
- Clinical genomics;
- Imaging Integration,
- Pharmacy,
- Common Product Model
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.
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