Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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.3.14.6 Code System http://terminology.hl7.org/CodeSystem/data-absent-reason

Orders and Observations Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Any
This page has been approved as part of an ANSI standard. See the Observation Package for further details.

This is a code system defined by the FHIR project.

Summary

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

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

Committee:Orders and Observations Work Group
OID:2.16.840.1.113883.4.642.1.1048 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: DataAbsentReason (Used to specify why the normally expected content of the data element is missing.)

4.3.14.6.1 Content

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

LvlCodeDisplayDefinitionComments
1unknown UnknownThe value is expected to exist but is not known.
2  asked-unknown Asked But UnknownThe source was asked but does not know the value.
2  temp-unknown Temporarily UnknownThere is reason to expect (from the workflow) that the value may become known.
2  not-asked Not AskedThe workflow didn't lead to this value being known.
2  asked-declined Asked But DeclinedThe source was asked but declined to answer.
1masked MaskedThe information is not available due to security, privacy or related reasons.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.
1not-applicable Not ApplicableThere is no proper value for this element (e.g. last menstrual period for a male).
1unsupported UnsupportedThe source system wasn't capable of supporting this element.
1as-text As TextThe content of the data is represented in the resource narrative.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.
1error ErrorSome system or workflow process error means that the information is not available.
2  not-a-number Not a Number (NaN)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 value is excessively low and unrepresentable due to a floating point processing error.This is sometimes an output value from measuring devices.
2  positive-infinity Positive Infinity (PINF)The numeric value is excessively high and unrepresentable due to a floating point processing error.This is sometimes an output value from measuring devices.
1not-performed Not PerformedThe value is not available because the observation procedure (test, etc.) was not performed.
1not-permitted Not PermittedThe 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 code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code