DataAbsentReason

DataAbsentReason

activeExtensions for Using Data Elements from FHIR R5 in FHIR R40.1.0complete15 concepts

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

Metadata

hl7.org/fhir
Canonical URL
http://terminology.hl7.org/CodeSystem/data-absent-reason
ID
data-absent-reason
Version
0.1.0
Publisher
Orders and Observations
Case Sensitive
Yes

Concepts (15)

CodeDisplayDefinition
unknownUnknownThe value is expected to exist but is not known.
└asked-unknownAsked But UnknownThe source was asked but does not know the value.
└temp-unknownTemporarily UnknownThere is reason to expect (from the workflow) that the value may become known.
└not-askedNot AskedThe workflow didn't lead to this value being known.
└asked-declinedAsked But DeclinedThe source was asked but declined to answer.
maskedMaskedThe information is not available due to security, privacy or related reasons.
not-applicableNot ApplicableThere is no proper value for this element (e.g. last menstrual period for a male).
unsupportedUnsupportedThe source system wasn't capable of supporting this element.
as-textAs TextThe content of the data is represented in the resource narrative.
errorErrorSome system or workflow process error means that the information is not available.
└not-a-numberNot a Number (NaN)The numeric value is undefined or unrepresentable due to a floating point processing error.
└negative-infinityNegative Infinity (NINF)The numeric value is excessively low and unrepresentable due to a floating point processing error.
└positive-infinityPositive Infinity (PINF)The numeric value is excessively high and unrepresentable due to a floating point processing error.
not-performedNot PerformedThe value is not available because the observation procedure (test, etc.) was not performed.
not-permittedNot PermittedThe value is not permitted in this context (e.g. due to profiles, or the base data types).