Editor | Various Contributors HL7 Publishing Technical Committee |
Last Published: 03/27/2006 3:37 AM
HL7® Version 3 Standard, © 2005 Health Level Seven®, Inc. All Rights Reserved.
HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Off
The HL7 Glossary provides "core" definitions of words and terms used throughout HL7 standards and documents. These definitions are maintained by the Modeling and Methodology (MnM) and Publishing Technical Committees (TC) and are identified in the glossary as "Core Glossary".
It should be noted that while the Modeling and Methodology and Publishing Technical Committees maintain the glossary definitions, the definitions themselves originate from within the various technical committees and special interest groups and are not constrained or veted in any way by the MnM or Publishing TCs. It is expected that each committee and its balloters know their business best and that, should an imprecise or incorrect definition be put forward, it will be corrected through the domain balloting process.
It should further be noted that this glossary does not include all the definitions from the Reference Information Model (RIM) as the RIM definitions are already available in the RIM publication and are in context there.
Readers may also note that "core" definitions may be constrained or narrowed within the context of specific domains. For instance, the PM domain includes a definition for Person that is constrained from the RIM definition of Person. In these cases, the PM:Person is perfectly consistent with the RIM:Person, albeit as a specialized subset of the larger group. So while all instances of a PM:Person will also be members of RIM:Persons, not all instances of RIM:Person will fall within the group of PM:Persons.
The MnM and Publishing TCs encourage all members to review the definitions put forward by committees as part of the balloting process with an eye towards correcting and refining them as necessary and appropriate.
For more information refer to the Relationships section of the Version 3 Guide.
association compositionFor more information refer to the Attributes section of the Version 3 Guide.
attribute typeFor more information refer to the Classes section of the Version 3 Guide.
classifier attributeFor more information refer to the Attributes section of the Version 3 Guide.
cloneFor more information refer to the Common Message Element Types section of the Version 3 Guide.
composite aggregationUniversally accepted "standardese" does not recognize "must". Use "SHALL" to indicate a mandatory aspect or an aspect on which there is no option.
The negatives are SHALL NOT, SHOULD NOT, MAY NOT.
The Publishing Facilitator's Guide requires the Conformance Verbs to be captialized when they are used to indicate conformance criteria, to differentiate from common usage of the words.
The source for this usage is ANSI.
connectionFor more information refer to the Constraints section of the Version 3 Guide.
control event wrapperFor more information refer to the Data Types section of the Version 3 Guide.
default valueFor more information refer to the Information Model section of the Version 3 Guide.
domain nameFor more information refer to the Vocabulary Domain Qualifiers section of the Version 3 Guide.
Extensible Markup LanguageFor more information refer to the Relationships section of the Version 3 Guide.
generalization hierarchyFor more information refer to the Attributes section of the Version 3 Guide.
implementation technologyFor more information refer to the Implementation Technology Specifications section of the Version 3 Guide.
inclusionFor more information refer to the Information Model section of the Version 3 Guide.
inheritance“Functional” interoperability is the capability to reliably exchange information without error
“Semantic" interoperability is the ability to interpret, and, therefore, to make effective use of the information so exchanged.
In our context, "effective use" means that the information can be used in any type of computable algorithm (appropriate) to that information
ITSFor more information refer to the Classes section of the Version 3 Guide.
object identifierThe HL7 OID Registry is available online.
object identityFor more information refer to the Vocabulary Domain Qualifiers section of the Version 3 Guide.
receiver responsibilityFor more information refer to the Information Model section of the Version 3 Guide.
Refined Message Information ModelFor more information refer to the Information Model section of the Version 3 Guide.
requiredFor more information refer to the Dynamic Behavior section of the Version 3 Guide.
state attributeFor more information refer to the Attributes section of the Version 3 Guide.
state diagramFor more information refer to the Dynamic Behavior section of the Version 3 Guide.
state transition modelFor more information refer to the Vocabulary section of the Version 3 Guide.
vocabulary domainFor more information refer to the Vocabulary Domains section of the Version 3 Guide.
vocabulary domain qualifierFor more information refer to the Vocabulary Domain Qualifiers section of the Version 3 Guide.
vocabulary domain specificationThe three-part schema specification issued by the W3C
Return to top of page |