HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

HL7ConformanceInclusion

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v3-HL7ConformanceInclusion
Version:2.0.0
Name:HL7ConformanceInclusion
Title:HL7ConformanceInclusion
Status:retired
Content:All the concepts defined by the code system are included in the code system resource
Definition:

These concepts represent theconformance requirments defined for including or valuing an element of an HL7 message. The concepts apply equally to conformance profiles defined for Version 2.x messgaes as defined by the Conformance SIG, and to the conformance columns for Version 3 messages as specified in the HMD.

Deprecation Comment: Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.

Publisher:Health Level 7
OID:2.16.840.1.113883.5.55 (for OID based terminology systems)
Content Mode:Complete
Source Resource:XML / JSON / Turtle

This Code system is referenced in the content logical definition of the following value sets:

This CodeSystem is not used here; it may be used elsewhere

HL7ConformanceInclusion

These concepts represent theconformance requirments defined for including or valuing an element of an HL7 message. The concepts apply equally to conformance profiles defined for Version 2.x messgaes as defined by the Conformance SIG, and to the conformance columns for Version 3 messages as specified in the HMD.

Deprecation Comment: Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.

Properties

CodeURLDescriptionType
SpecializesThe child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.Coding
GeneralizesInverse of Specializes. Only included as a derived relationship.Coding
internalIdhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-idThe internal identifier for the concept in the HL7 Access database repository.code
notSelectablehttp://hl7.org/fhir/concept-properties#notSelectableIndicates that the code is abstract - only intended to be used as a selector for other conceptsboolean
statushttp://hl7.org/fhir/concept-properties#statusDesignation of a concept's state. Normally is not populated unless the state is retired.code
synonymCodehttp://hl7.org/fhir/concept-properties#synonymAn additional concept code that was also attributed to a conceptcode

This code system http://terminology.hl7.org/CodeSystem/v3-HL7ConformanceInclusion defines the following codes:

LvlCodeDisplayDefinitioninternalIdNot SelectablestatussynonymCode
1_InclusionNotMandatory InclusionNotMandatoryThe message element is not mandatory, but its appearance may be constrained by one of the non-mandatory concepts.21081trueactive
2  NP Not permittedThis message element may not appear when the message is communicated.10014active
2  NR Not requiredThe message element may be populated or used by one system sponsor (or profile), but not by another. Each system sponsor or profile is required to state the ability to accept or send the message element as part of a conformance claim.10015active
3    RE Required may be emptyPursuant to a profile or vendor conformance claim, the message element must appear every time the message is communicated, but the value may be communicated as null.10016active
3    X ExcludedPursuant to a profile or vendor conformance claim, this message element may not appear when the message is communicated.10017active
2  RQ RequiredThe message element must appear every time the message is communicated, but the value may be communicated as null.10013active
1M MandatoryThe message element must appear every time the message is communicated and its value must not be null. This condition is subject to the rules of multiplicity and conditionality. If a non-null default value is defined for the element, a null value may be communicated.10011activeR
1R MandatoryThe message element must appear every time the message is communicated and its value must not be null. This condition is subject to the rules of multiplicity and conditionality. If a non-null default value is defined for the element, a null value may be communicated.10011activeM

Additional Language Displays

CodeEnglish (English, en)
_InclusionNotMandatory
MRequired - V2.x
RRequired - V2.x

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.