Properties This code system defines the following properties for its concepts Code URI Type Description Specializes Coding The 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. Generalizes Coding Inverse of Specializes. Only included as a derived relationship. internalId http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id code The internal identifier for the concept in the HL7 Access database repository. notSelectable http://hl7.org/fhir/concept-properties#notSelectable boolean Indicates that the code is abstract - only intended to be used as a selector for other concepts status http://hl7.org/fhir/concept-properties#status code Designation of a concept's state. Normally is not populated unless the state is retired. synonymCode http://hl7.org/fhir/concept-properties#synonym code An additional concept code that was also attributed to a concept Concepts This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-HL7ConformanceInclusion defines the following codes in a Is-A heirarchy: Lvl Code Display Definition internalId Not Selectable status synonymCode 1 _InclusionNotMandatory InclusionNotMandatory The message element is not mandatory, but its appearance may be constrained by one of the non-mandatory concepts. 21081 true active 2 NP Not permitted This message element may not appear when the message is communicated. 10014 active 2 NR Not required The 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. 10015 active 3 RE Required may be empty Pursuant 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. 10016 active 3 X Excluded Pursuant to a profile or vendor conformance claim, this message element may not appear when the message is communicated. 10017 active 2 RQ Required The message element must appear every time the message is communicated, but the value may be communicated as null. 10013 active 1 M Mandatory The 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. 10011 active R 1 R Mandatory The 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. 10011 active M
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.
The 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.
Inverse of Specializes. Only included as a derived relationship.
The internal identifier for the concept in the HL7 Access database repository.
Indicates that the code is abstract - only intended to be used as a selector for other concepts
Designation of a concept's state. Normally is not populated unless the state is retired.
An additional concept code that was also attributed to a concept
The message element is not mandatory, but its appearance may be constrained by one of the non-mandatory concepts.
This message element may not appear when the message is communicated.
The 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.
Pursuant 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.
Pursuant to a profile or vendor conformance claim, this message element may not appear when the message is communicated.
The message element must appear every time the message is communicated, but the value may be communicated as null.
The 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.