FHIR Release 3 (STU) R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.0.2: STU 3). (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.2.12.6 4.3.13.126 Code System http://hl7.org/fhir/data-absent-reason http://terminology.hl7.org/CodeSystem/data-absent-reason

Vocabulary Orders and Observations Work Group   Maturity Level : 0 5 Informative Normative Use Context : Any

Normative Candidate Note: This page is candidate normative content for R4 in the Observation Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made.

This is a code system defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/data-absent-reason http://terminology.hl7.org/CodeSystem/data-absent-reason
Version: null
Name: DataAbsentReason
Title: DataAbsentReason
Definition:

Used to specify why the normally expected content of the data element is missing.

Committee: FHIR Infrastructure Orders and Observations Work Group
OID: 2.16.840.1.113883.4.642.1.6 2.16.840.1.113883.4.642.1.1048 (for OID based terminology systems)
Source Resource XML / JSON

This Code system is used in the following value sets:

  • Observation Value Absent Reason (This value set defines the set of codes for identifying the reason why the expected result in Observation.value[x] is missing.) ValueSet: DataAbsentReason (Used to specify why the normally expected content of the data element is missing.)

4.2.12.6.1 4.3.13.126.1 Content

4.2.12.6.2 4.3.13.126.2 DataAbsentReason

Used to specify why the normally expected content of the data element is missing.

This code system http://hl7.org/fhir/data-absent-reason http://terminology.hl7.org/CodeSystem/data-absent-reason defines the following codes:

asked temp not-asked astext   NaN
Lvl Code Display Definition Comments
1 unknown Unknown The value is expected to exist but is not known.
1 2   asked-unknown Asked But Unknown The source human was asked but does not know the value.
1 2   temp-unknown Temp Temporarily Unknown There is reason to expect (from the workflow) that the value may become known.
1 2   not-asked Not Asked The workflow didn't lead to this value being known.
1 2   asked-declined Asked But Declined The source was asked but declined to answer.
1 masked Masked The information is not available due to security, privacy or related reasons. Using "masked" "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.
1 not-applicable Not Applicable There is no proper value for this element (e.g. last menstrual period for a male).
1 unsupported Unsupported The source system wasn't capable of supporting this element.
1 as-text As Text The content of the data is represented in the resource narrative. it 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 value.
1 error Error Some system or workflow process error means that the information is not available.
2   not-a-number Not a Number (NaN) NaN, standing for not a number, The numeric value is undefined or unrepresentable due to a floating point processing error. This is sometimes an output value from measuring devices.
2   negative-infinity Negative Infinity (NINF) The numeric data type value representing is excessively low and unrepresentable due to a floating point processing error. This is sometimes an undefined or output value from measuring devices.
2   positive-infinity Positive Infinity (PINF) The numeric value is excessively high and unrepresentable value. due to a floating point processing error. This is sometimes an output value from measuring devices devices.
1 not-performed Not Performed The value is not available because the observation procedure (test, etc.) was not performed.
1 not-permitted Not Permitted The value is not permitted in this context (e.g. due to profiles, or the base data types). This is most often associated with required bindings that do not include the actual code used, but may be used with other data types.

 

See the full registry of value sets code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

Level Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies See Code System for further information.
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display The display (used in the display element of a Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code