Common Message Element Types
 ANSI/HL7 V3 CMET, R2-2009 HL7 Version 3 Standard: Common Message Element Types, Release 2 (revision of ANSI/HL7 V3 CMET, R1-2005) 7/14/2009 |
| Responsible Group | Methodology & Modeling Work Group HL7 |
| Modeling & Methodology Co-Chair | George Beeler, Jr., PhD Beeler Consulting LLC |
| Principal Contributor | Kathleen Connor Fox Systems, Inc. |
| Modeling & Methodology Co-Chai | Jean-Henri Duteau Duteau Design, Inc. |
| Principal Contributor | Hugh Glover Blue Wave Informatics |
| Modeling & Methodology Co-Chair | Grahame Grieve Australie Kestral Computing |
| MnM, Publishing Facilitator | Patrick E. Loyd Gordon Point Informatics, Ltd. |
| Modeling & Methodology Co-Chair | Lloyd McKenzie LM & A Consulting, Ltd. |
| Editor, Modeling & Methodology Co-Chair | Dale Nelson Zed-Logic Informatics, Inc. |
| Principal Contributor | Gregg Seppala U.S. Department of Veterans Affairs |
HTML Generated: 2012-08-31T12:05:14
Content Last Edited: 2011-07-12T16:13:25
HL7® Version 3 Standard, © 2009 Health Level Seven® International All Rights Reserved.
HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. Pat & TM Off.
Use of these materials is governed by HL7 International's IP Compliance Policy.
Table of Contents
Preface
i Notes to Readers
ii Message Design Element Navigation
1 Overview
1.1 Introduction & Scope
2 Quality Analysis Report Topic
3 CMETs Defined by All Domains
4 CMETs Used by all CMETs
5 Glossary
CMET Notes to Readers
Ballot Status of CMET Specifications
The ballot status for each CMET is marked individually. The majority of the CMETs in this package have reached normative status. Other CMETs are only included here if one of the Normative specifications in this Edition refers to it.
The CMET ballot status identifications are as follows
- Standard (signified by a solid red circle): For each CMET marked "standard", its release level in this edition is shown for reference.
- NonStandardAvailable (signified by an solid brown circle). This content was at Draft, or Membership ballot at the time this Normative Edition was produced. Even though it is not yet a standard, the content is presented because some normative specification refers to it.
Summary of CMETs Releases
- Release 1
- The following CMETs are part of Release 1:
- COCT_MT010000 - A_Encounter universal
- COCT_MT010001 - A_Encounter identified
- COCT_MT020000 - A_Appointment universal
- COCT_MT050000 - R_Patient universal
- COCT_MT050004 - R_PatientClinical universal
- COCT_MT060000 - A_Transportation universal
- COCT_MT070000 - R_LocationLocatedEntity universal
- COCT_MT090000 - R_AssignedEntity universal
- COCT_MT090001 - R_AssignedEntity identified
- COCT_MT090002 - R_AssignedEntity identified-confirmable
- COCT_MT090003 - R_AssignedEntity contact
- COCT_MT090100 - R_AssignedPerson universal
- COCT_MT090101 - R_AssignedPerson identified
- COCT_MT090103 - R_AssignedPerson contact
- COCT_MT090200 - R_AssignedOrganization universal
- COCT_MT090201 - R_AssignedOrganization identified
- COCT_MT090202 - R_AssignedOrganization identified-confirmable
- COCT_MT090203 - R_AssignedOrganization contact
- COCT_MT090300 - R_AssignedDevice universal
- COCT_MT090301 - R_AssignedDevice identified
- COCT_MT090302 - R_AssignedDevice identified-confirmable
- COCT_MT090303 - R_AssignedDevice contact
- COCT_MT110001 - A_Account identified
- COCT_MT150001 - E_Organization identified
- COCT_MT150002 - E_Organization identified-confirmable
- COCT_MT200000 - A_SupportingClinicalInfo universal
- COCT_MT240000 - R_ServiceDeliveryLocation universal
- The following CMETs were removed from Release 1 and not replaced.
- COCT_MT030100 - E_NonPersonLivingSubject universal
- COCT_MT030101 - E_NonPersonLivingSubject identified
- COCT_MT030102 - E_NonPersonLivingSubject identified-confirmable
- COCT_MT030202 - E_Person identified-confirmable
- The following CMETs are part of Release 1:
- Release 2
- The following CMETs are part of Release 2:
- COCT_MT010004 - A_Encounter minimal
- COCT_MT050100 - R_PatientLite universal
- COCT_MT070001 - R_LocationLocatedEntity identified
- COCT_MT070002 - R_LocationLocatedEntity identified-confirmable
- COCT_MT070003 - R_LocationLocatedEntity contact
- COCT_MT090102 - R_AssignedPerson identified-confirmable
- COCT_MT140000 - E_Device universal
- COCT_MT150000 - E_Organization universal
- COCT_MT210000 - A_OrderOptions universal
- COCT_MT240001 - R_ServiceDeliveryLocation identified
- COCT_MT240002 - R_ServiceDeliveryLocation identified-confirmable
- COCT_MT240003 - R_ServiceDeliveryLocation contact
- The following CMETs are part of Release 2:
- Release 3
- The following CMETs are part of Release 3:
- COCT_MT150003 - E_Organization contact
- COCT_MT250000 - R_Reagent universal
- The following CMETs are part of Release 3:
- Release 4
- The following CMETs were newly part of Release 4:
- COCT_MT110101 - A_AccountPayor identified
- COCT_MT110102 - A_AccountPayor contact
- COCT_MT110201 - A_AccountPayee identified
- COCT_MT110202 - A_AccountPayee basic
- COCT_MT180000 - A_Coverage universal
- COCT_MT300000 - A_BillablePharmacyDispense universal
- COCT_MT300001 - A_BillablePharmacyDispense basic
- COCT_MT680002 - A_InvoiceCoordination basic
- COCT_MT680003 - A_InvoiceCoordination enhanced
- COCT_MT740000 - A_BillableOralHealthService universal
- COCT_MT750000 - A_BillingSupportObservation universal
- COCT_MT760000 - A_OralHealthObservation universal
- The following CMETs were first published in Release 1, but were revised and re-issued as part of Release 4:
- COCT_MT110000 - A_Account universal
- COCT_MT110100 - A_AccountPayor universal
- COCT_MT110200 - A_AccountPayee universal
- COCT_MT110300 - A_AccountGuarantor universal
- COCT_MT190000 - A_FinancialTransaction universal
- COCT_MT280000 - A_Billable universal
- COCT_MT310000 - A_BillablePreferredAccomodation universal
- COCT_MT320000 - A_AdjudicationObservation universal
- COCT_MT490000 - A_BillableClinicalProduct universal
- COCT_MT670000 - R_Guarantor universal
- COCT_MT680000 - A_InvoiceCoordination universal
- The following CMET was first published in Release 2, but was revised and re-issued as part of Release 4:
- COCT_MT500000 - R_CoveredParty universal
- The following CMETs were newly part of Release 4:
- Release 5
- The following CMETs are part of Release 5:
- COCT_MT830110 - A_DicomSequence minimal
- COCT_MT830120 - A_DicomCompositeObjectReference minimal
- COCT_MT960000 - A_SpatialCoordinate universal
- The following CMETs are part of Release 5:
- Release 6
- The following CMETs were newly part of Release 6:
- COCT_MT290002 - A_BillableClinicalService basic
- COCT_MT290004 - A_BillableClinicalService encounter
- COCT_MT510000 - A_Coverage universal
- COCT_MT510001 - A_Coverage identified
- COCT_MT510002 - A_Coverage identified/informational
- COCT_MT510003 - A_Coverage contact
- COCT_MT510004 - A_Coverage minimal
- COCT_MT510005 - A_Coverage basic
- COCT_MT600000 - A_BillableVisionDispense universal
- COCT_MT610000 - A_BillableSocialService universal
- The following CMET was first published in Release 1, but was revised and re-issued as part of Release 6:
- COCT_MT290000 - A_BillableClinicalService universal
- The following CMETs were newly part of Release 6:
- Release 7
- The following CMETs were newly part of Release 7:
- COCT_MT030107UV07 - E_NonPersonLivingSubject informational
- COCT_MT030108UV07 - E_NonPersonLivingSubject identified/informational
- COCT_MT030207UV07 - E_Person informational
- COCT_MT050002UV07 - R_Patient identified/confirmable
- COCT_MT050007UV07 - R_Patient informational
- COCT_MT050207UV07 - R_PatientPerson informational
- COCT_MT050208UV07 - R_PatientPerson identified/informational
- COCT_MT290003UV07 - A_BillableClinicalService referral
- COCT_MT400000UV07 - A_Charge universal
- COCT_MT400100UV07 - A_CompositeCharge universal
- COCT_MT410000UV07 - R_ExposureAgentCarrier universal
- COCT_MT410300UV07 - R_ExposureAgentVector universal
- COCT_MT411000UV07 - R_ExposureAgentFomite universal
- COCT_MT550000UV07 - R_InvestigativeSubject universal
- COCT_MT560000UV07 - R_Subject universal
- COCT_MT580000UV07 - A_DataConsent universal
- COCT_MT710007UV07 - E_Place informational
- COCT_MT840500UV07 - E_PublicHealthPathogen universal
- The following CMETs were first published in Release 1, but were revised and re-issued as part of Release 7:
- COCT_MT030201UV07 - E_Person identified
- COCT_MT030201UV07 - E_Person identified
- COCT_MT030202UV07 - E_Person identified/confirmable
- COCT_MT050001UV07 - R_Patient identified
- COCT_MT050203UV07 - R_PatientPerson contact1
- COCT_MT710000UV07 - E_Place universal
- The following CMET was first published in Release 2, but was revised and re-issued as part of Release 7:
- COCT_MT030203UV07 - E_Person contact
- The following CMETs were newly part of Release 7:
- Release 8
- There has never been a Release 8 of CMETs. This release was dropped when HL7 determined to seek to approve CMEts in an annual release package. The candidates for Release 8 were released as part of Release 9
- Release 9
- The following CMETs were newly part of Release 9:
- COCT_MT080000UV09 - R_Specimen universal
- COCT_MT080100UV09 - R_Specimen minimal
- COCT_MT080200UV09 - R_Specimen lite
- COCT_MT430000UV09 - R_LabTestKit universal
- COCT_MT440000UV09 - A_ValuedItem universal
- COCT_MT440001UV09 - A_ValuedItem identified
- COCT_MT440004UV09 - A_ValuedItem minimal
- COCT_MT440005UV09 - A_ValuedItem basic
- COCT_MT440006UV09 - A_ValuedItem definitional
- COCT_MT440007UV09 - A_ValuedItem informational
- COCT_MT480000UV09 - A_PublicHealthStatement universal
- COCT_MT570000UV09 - A_LaboratoryProcessStep universal
- COCT_MT770000UV09 - A_Benefit universal
- COCT_MT770005UV09 - A_Benefit basic
- COCT_MT780005UV09 - A_ProviderContract basic
- COCT_MT840000UV09 - E_PublicHealthEntity universal
- COCT_MT840100UV09 - E_PublicHealthNonPersonLivingSubject universal
- COCT_MT840200UV09 - E_PublicHealthPerson universal
- COCT_MT840300UV09 - E_PublicHealthVector universal
- COCT_MT841000UV09 - E_PublicHealthFomite universal
- COCT_MT841100UV09 - E_PublicHealthMaterial universal
- COCT_MT841200UV09 - E_PublicHealthManufacturedMaterial universal
- COCT_MT841300UV09 - E_PublicHealthPlace universal
- COCT_MT841400UV09 - E_PublicHealthOrganization universal
- COCT_MT841500UV09 - E_PublicHealthPhysicalEntity universal
- The following CMETs were first published in Release 1, but were revised and re-issued as part of Release 9:
- COCT_MT030100UV09 - E_NonPersonLivingSubject universal
- COCT_MT030200UV09 - E_Person universal
- COCT_MT040000UV09 - R_Responsible universal
- COCT_MT040200UV09 - R_ResponsibleParty universal
- COCT_MT040203UV09 - R_NotificationParty contact
- COCT_MT040205UV09 - R_ResponsibleParty contact
- COCT_MT040300UV09 - R_ResponsibleOrganization universal
- The following CMETs were first published in Release 4, but were revised and re-issued as part of Release 9:
- COCT_MT030000UV09 - E_LivingSubject universal
- COCT_MT050003UV09 - R_Patient contact 4
- The following CMETs were newly part of Release 9:
- Non-Standard CMETS
- The following CMETs are at Draft, or Membership level, and thus are not yet Normative:
- COCT_MT030007UV - E_LivingSubject informational
- COCT_MT040008UV - R_Responsible identified/informational
- COCT_MT090008UV - R_AssignedEntity identified/informational
- COCT_MT090107UV - R_AssignedPerson informational
- COCT_MT090108UV - R_AssignedPerson identified/informational
- COCT_MT090208UV - R_AssignedOrganization identified/informational
- COCT_MT090400UV - R_AssignedParty universal
- COCT_MT120100UV - A_ObservationDx universal
- COCT_MT120104UV - A_ObservationDx minimal
- COCT_MT120300UV - A_ObservationIntolerance universal
- COCT_MT120500UV - A_ObservationGeneral universal
- COCT_MT140007UV - E_Device informational
- COCT_MT150007UV - E_Organization informational
- COCT_MT220100UV - R_OrderableMedication universal
- COCT_MT220200UV - R_AdministerableMedication universal
- COCT_MT220300UV - R_BillableMedication universal
- COCT_MT230100UV - R_Medication universal
- COCT_MT230200UV - R_MedicationIngredient universal
- COCT_MT260003UV - A_DetectedMedicationIssue noText
- COCT_MT420000UV - A_AbnormalityAssessment universal
- COCT_MT470000UV - A_Consent universal
- COCT_MT520001UV - A_CareEvent identified
- COCT_MT530000UV - A_SupportingClinicalStatement universal
- COCT_MT530004UV - A_SupportingClinicalStatement minimal
- COCT_MT540000UV - A_GeneticLoci universal
- COCT_MT590000UV - A_Annotation universal
- COCT_MT810000UV - A_Verification universal
- COCT_MT820000UV - A_PrincipalCareProvision universal
- COCT_MT910000UV - R_RelatedParty universal
- COCT_MT930000UV - A_GeneticLocus universal
- COCT_MT970000UV - A_ResearchStudyEnrollment universal
- The following CMETs are at Draft, or Membership level, and thus are not yet Normative:
|
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. Because they are intended for common use across messages produced by all committees, they are proposed to, reviewed by, and maintained by the CMET task force of the MnM committee. The CMET task force harmonizes and becomes steward for all CMETs.
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.
CMET Hierarchy
As described in the V3 Guide, CMETs are categorized along two axes- an attribution axis and a generalization-specialization axis.
-
Attribution refers to the level of specificity of the CMET. As a CMET is implemented as a message type derived from an HMD and R-MIM in the same manner as all other message types, the message type may contain complete information about a concept, or minimal information about a concept. At the complete extreme, this is known as the universal level of attribution of the CMET. Typically, the other extreme is known as the identified level of attribution of the CMET, or universal and identified variants, respectively. The universal variant of a CMET is always present, and all other variants, if they exist, are derived by restriction from the universal variant. The common CMET variants are described below.
-
The Generalization-Specialization axis allows a message designer to choose between several specializations of a concept in a CMET. These choices always are between specializations of a RIM class that plays the central role in the concept modeled by the CMET. For example, we may model an Entity of type LivingSubject in the same fashion as an Entity of type Person or NonPersonLivingSubject (with the exception of the Entity specialization itself!). This results in a generalized CMET called E_LivingSubject, and several specialized CMETs called E_Person and E_NonPersonLivingSubject. With the exception of the entity itself (LivingSubject, Person, NonPersonLivingSubject), the rest of the CMETs are equivalent.
Common CMET Variants
CMETS come in several flavours or variants from the most detailed to the least. Designers should select an appropriate level of detail when building RMIMs. The common variants are:
-
universal - this variant includes all attributes and associations present in the R-MIM. Any of non-mandatory and non-required attributes and/or associations may be present or absent, as permitted in the cardinality constraints.
-
minimal - provides more than identified, but not as much as universal. There are not expected to be many of these.
-
contact - provides sufficient information to allow the object identified to be contacted. This is likely to have the content of identified and confirmable plus telephone number.
-
identified and confirmable - this extends the identified variant by adding just sufficient additional information to allow the identity of object modeled to be confirmed by a number of corroborating items of data; for instance a patient's date of birth and current address. However, specific contact information, such as telephone number, are not viewed as confirming information.
-
identified - this variant is a proper subset of universal and is intended to provide sufficient information to identify the object(s) modeled by the CMET. This variant is only suitable for use within TIGHTLY COUPLED SYSTEMS ONLY. This variant provides ONLY the ID (and code where applicable) and Name. Other variants may not be substituted at runtime.
-
Other variants may be developed in future.
| Return to top of page |