2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

1.22.4.1.55 v3 Code System HL7ConformanceInclusion

This code system (http://hl7.org/fhir/v3/HL7ConformanceInclusion) is defined as part of HL7 v3.

Formal value Set definition (identifier http://hl7.org/fhir/v3/vs/HL7ConformanceInclusion): XML or JSON

Release Date: 2014-12-11

OID for code system: 2.16.840.1.113883.5.55

1.22.4.1.55.1 Description

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.

LevelCodeDisplayDefinition
1(_InclusionNotMandatory)  The message element is not mandatory, but its appearance may be constrained by one of the non-mandatory concepts.
2  NP Not permitted This message element may not appear when the message is communicated.
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.
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.
3    X Excluded Pursuant to a profile or vendor conformance claim, this message element may not appear when the message is communicated.
2  RQ Required The message element must appear every time the message is communicated, but the value may be communicated as null.
1M 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.