This
page
is
part
of
the
FHIR
Specification
(v5.0.0:
R5
-
STU
).
This
is
the
(v3.5.0:
R4
Ballot
#2).
The
current
published
version.
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
FHIR
Infrastructure
Work
Group
|
Maturity
Level
:
|
Normative
|
Use
Context
:
|
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 value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/data-absent-reason |
| Version: | 3.5.0 |
| Name: | DataAbsentReason |
| Title: | DataAbsentReason |
| Definition: |
Used to specify why the normally expected content of the data element is missing. |
| Committee: |
Work
Group
|
| OID: | 2.16.840.1.113883.4.642.3.5 (for OID based terminology systems) |
| Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/data-absent-reason
This
expansion
generated
26
Mar
2023
19
Aug
2018
This value set contains 15 concepts
All
codes
from
system
http://terminology.hl7.org/CodeSystem/data-absent-reason
|
|
Code |
|
Definition |
|
|
|
|
The value is expected to exist but is not known. |
|
|
|
|
The source was asked but does not know the value. |
|
|
|
|
There is reason to expect (from the workflow) that the value may become known. |
|
|
|
|
The workflow didn't lead to this value being known. |
|
|
|
|
The source was asked but declined to answer. |
|
|
|
|
The information is not available due to security, privacy or related reasons. |
|
|
|
|
There is no proper value for this element (e.g. last menstrual period for a male). |
|
|
|
|
The source system wasn't capable of supporting this element. |
|
|
|
|
The content of the data is represented in the resource narrative. |
|
|
|
|
Some system or workflow process error means that the information is not available. |
|
|
|
|
The numeric value is undefined or unrepresentable due to a floating point processing error. |
|
|
|
|
The numeric value is excessively low and unrepresentable due to a floating point processing error. |
|
|
|
|
The numeric value is excessively high and unrepresentable due to a floating point processing error. |
|
|
|
|
The value is not available because the observation procedure (test, etc.) was not performed. |
|
|
|
|
The value is not permitted in this context (e.g. due to profiles, or the base data types). |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
| Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - 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 |