MyHealthEu MVC package
9.1.0 - ci-build

MyHealthEu MVC package - Local Development build (v9.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: eHDSI Data Absent Reason

Official URL: http://terminology.ehdsi.eu/ValueSet/eHDSIDataAbsentReason Version: 9.1.0
Active as of 2026-02-19 Computable Name: EHDSIDataAbsentReason
Other Identifiers: OID:1.3.6.1.4.1.12559.11.10.1.3.1.42.92

The Value Set is used to specify why the normally expected content of the data element is missing.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/data-absent-reason version 📦1.0.0
    CodeDisplayDefinition
    as-textAs TextThe content of the data is represented in the resource narrative.
    asked-declinedAsked But DeclinedThe source was asked but declined to answer.
    asked-unknownAsked But UnknownThe source was asked but does not know the value.
    errorErrorSome system or workflow process error means that the information is not available.
    maskedMaskedThe information is not available due to security, privacy or related reasons.
    negative-infinityNegative Infinity (NINF)The numeric value is excessively low and unrepresentable due to a floating point processing error.
    not-a-numberNot a Number (NaN)The numeric value is undefined or unrepresentable due to a floating point processing error.
    not-applicableNot ApplicableThere is no proper value for this element (e.g. last menstrual period for a male).
    not-askedNot AskedThe workflow didn't lead to this value being known.
    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).
    positive-infinityPositive Infinity (PINF)The numeric value is excessively high and unrepresentable due to a floating point processing error.
    temp-unknownTemporarily UnknownThere is reason to expect (from the workflow) that the value may become known.
    unknownUnknownThe value is expected to exist but is not known.
    unsupportedUnsupportedThe source system wasn't capable of supporting this element.

 

Expansion

Expansion performed internally based on codesystem DataAbsentReason v1.0.0 (CodeSystem)

This value set contains 15 concepts

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

Explanation of the columns that may appear on this page:

Level 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
System 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)
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