HL7 Terminology
2.1.0 - Publication
This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="data-absent-reason"/>
<meta>
<lastUpdated value="2019-10-31T16:29:23.356-06:00"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p>This code system http://terminology.hl7.org/CodeSystem/data-absent-reason defines the following codes:</p><table class="codes"><tr><td><b>Lvl</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>Comments</b></td></tr><tr><td>1</td><td style="white-space:nowrap">unknown<a name="data-absent-reason-unknown"> </a></td><td>Unknown</td><td>The value is expected to exist but is not known.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> asked-unknown<a name="data-absent-reason-asked-unknown"> </a></td><td>Asked But Unknown</td><td>The source was asked but does not know the value.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> temp-unknown<a name="data-absent-reason-temp-unknown"> </a></td><td>Temporarily Unknown</td><td>There is reason to expect (from the workflow) that the value may become known.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> not-asked<a name="data-absent-reason-not-asked"> </a></td><td>Not Asked</td><td>The workflow didn't lead to this value being known.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> asked-declined<a name="data-absent-reason-asked-declined"> </a></td><td>Asked But Declined</td><td>The source was asked but declined to answer.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">masked<a name="data-absent-reason-masked"> </a></td><td>Masked</td><td>The information is not available due to security, privacy or related reasons.</td><td>Using "masked" may be breach of security or confidentiality, but there are times when its use is required to support alternate workflows for gaining access to denied information.</td></tr><tr><td>1</td><td style="white-space:nowrap">not-applicable<a name="data-absent-reason-not-applicable"> </a></td><td>Not Applicable</td><td>There is no proper value for this element (e.g. last menstrual period for a male).</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">unsupported<a name="data-absent-reason-unsupported"> </a></td><td>Unsupported</td><td>The source system wasn't capable of supporting this element.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">as-text<a name="data-absent-reason-as-text"> </a></td><td>As Text</td><td>The content of the data is represented in the resource narrative.</td><td>It may be linked by internal references (e.g. xml:id). This usually implies that the value could not be represented in the correct format - this may be due to system limitations, or this particular data value.</td></tr><tr><td>1</td><td style="white-space:nowrap">error<a name="data-absent-reason-error"> </a></td><td>Error</td><td>Some system or workflow process error means that the information is not available.</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> not-a-number<a name="data-absent-reason-not-a-number"> </a></td><td>Not a Number (NaN)</td><td>The numeric value is undefined or unrepresentable due to a floating point processing error.</td><td>This is sometimes an output value from measuring devices.</td></tr><tr><td>2</td><td style="white-space:nowrap"> negative-infinity<a name="data-absent-reason-negative-infinity"> </a></td><td>Negative Infinity (NINF)</td><td>The numeric value is excessively low and unrepresentable due to a floating point processing error.</td><td>This is sometimes an output value from measuring devices.</td></tr><tr><td>2</td><td style="white-space:nowrap"> positive-infinity<a name="data-absent-reason-positive-infinity"> </a></td><td>Positive Infinity (PINF)</td><td>The numeric value is excessively high and unrepresentable due to a floating point processing error.</td><td>This is sometimes an output value from measuring devices.</td></tr><tr><td>1</td><td style="white-space:nowrap">not-performed<a name="data-absent-reason-not-performed"> </a></td><td>Not Performed</td><td>The value is not available because the observation procedure (test, etc.) was not performed.</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">not-permitted<a name="data-absent-reason-not-permitted"> </a></td><td>Not Permitted</td><td>The value is not permitted in this context (e.g. due to profiles, or the base data types).</td><td>This is most often associated with required bindings that do not include the actual code used, but may be used with other data types.</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="oo"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="normative"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version">
<valueCode value="4.0.0"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="5"/>
</extension>
<url value="http://terminology.hl7.org/CodeSystem/data-absent-reason"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.4.1048"/>
</identifier>
<version value="0.1.0"/>
<name value="DataAbsentReason"/>
<title value="DataAbsentReason"/>
<status value="active"/>
<experimental value="false"/>
<date value="2019-11-01T09:29:23+11:00"/>
<description
value="Used to specify why the normally expected content of the data element is missing."/>
<caseSensitive value="true"/>
<valueSet value="http://hl7.org/fhir/ValueSet/data-absent-reason"/>
<content value="complete"/>
<concept>
<code value="unknown"/>
<display value="Unknown"/>
<definition value="The value is expected to exist but is not known."/>
<concept>
<code value="asked-unknown"/>
<display value="Asked But Unknown"/>
<definition value="The source was asked but does not know the value."/>
</concept>
<concept>
<code value="temp-unknown"/>
<display value="Temporarily Unknown"/>
<definition
value="There is reason to expect (from the workflow) that the value may become known."/>
</concept>
<concept>
<code value="not-asked"/>
<display value="Not Asked"/>
<definition
value="The workflow didn't lead to this value being known."/>
</concept>
<concept>
<code value="asked-declined"/>
<display value="Asked But Declined"/>
<definition value="The source was asked but declined to answer."/>
</concept>
</concept>
<concept>
<extension
url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
<valueString
value="Using "masked" may be breach of security or confidentiality, but there are times when its use is required to support alternate workflows for gaining access to denied information."/>
</extension>
<code value="masked"/>
<display value="Masked"/>
<definition
value="The information is not available due to security, privacy or related reasons."/>
</concept>
<concept>
<code value="not-applicable"/>
<display value="Not Applicable"/>
<definition
value="There is no proper value for this element (e.g. last menstrual period for a male)."/>
</concept>
<concept>
<code value="unsupported"/>
<display value="Unsupported"/>
<definition
value="The source system wasn't capable of supporting this element."/>
</concept>
<concept>
<extension
url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
<valueString
value="It may be linked by internal references (e.g. xml:id). This usually implies that the value could not be represented in the correct format - this may be due to system limitations, or this particular data value."/>
</extension>
<code value="as-text"/>
<display value="As Text"/>
<definition
value="The content of the data is represented in the resource narrative."/>
</concept>
<concept>
<code value="error"/>
<display value="Error"/>
<definition
value="Some system or workflow process error means that the information is not available."/>
<concept>
<extension
url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
<valueString
value="This is sometimes an output value from measuring devices."/>
</extension>
<code value="not-a-number"/>
<display value="Not a Number (NaN)"/>
<definition
value="The numeric value is undefined or unrepresentable due to a floating point processing error."/>
</concept>
<concept>
<extension
url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
<valueString
value="This is sometimes an output value from measuring devices."/>
</extension>
<code value="negative-infinity"/>
<display value="Negative Infinity (NINF)"/>
<definition
value="The numeric value is excessively low and unrepresentable due to a floating point processing error."/>
</concept>
<concept>
<extension
url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
<valueString
value="This is sometimes an output value from measuring devices."/>
</extension>
<code value="positive-infinity"/>
<display value="Positive Infinity (PINF)"/>
<definition
value="The numeric value is excessively high and unrepresentable due to a floating point processing error."/>
</concept>
</concept>
<concept>
<code value="not-performed"/>
<display value="Not Performed"/>
<definition
value="The value is not available because the observation procedure (test, etc.) was not performed."/>
</concept>
<concept>
<extension
url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
<valueString
value="This is most often associated with required bindings that do not include the actual code used, but may be used with other data types."/>
</extension>
<code value="not-permitted"/>
<display value="Not Permitted"/>
<definition
value="The value is not permitted in this context (e.g. due to profiles, or the base data types)."/>
</concept>
</CodeSystem>