MyHealth@Eu Patient Summary
1.0.0-ci-build - ci-build 150

MyHealth@Eu Patient Summary - Local Development build (v1.0.0-ci-build) 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: 1.0.0-ci-build
Standards status: Draft | Maturity Level: 1 | 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

- Observation: Medical Test Result (Core)

### Logical Definition (CLD)

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/data-absent-reason` version 📍1.0.0

  Code | Display | Definition
  unknown | Unknown | The value is expected to exist but is not known.
  masked | Masked | The information is not available due to security, privacy or related reasons.
  not-applicable | Not Applicable | There is no proper value for this element (e.g. last menstrual period for a male).
  unsupported | Unsupported | The source system wasn't capable of supporting this element.
  as-text | As Text | The content of the data is represented in the resource narrative.
  error | Error | Some system or workflow process error means that the information is not available.
  not-performed | Not Performed | The value is not available because the observation procedure (test, etc.) was not performed.
  not-permitted | Not Permitted | The value is not permitted in this context (e.g. due to profiles, or the base data types).
  asked-unknown | Asked But Unknown | The source was asked but does not know the value.
  temp-unknown | Temporarily Unknown | There is reason to expect (from the workflow) that the value may become known.
  not-asked | Not Asked | The workflow didn't lead to this value being known.
  asked-declined | Asked But Declined | The source was asked but declined to answer.
  not-a-number | Not a Number (NaN) | The numeric value is undefined or unrepresentable due to a floating point processing error.
  negative-infinity | Negative Infinity (NINF) | The numeric value is excessively low and unrepresentable due to a floating point processing error.
  positive-infinity | Positive Infinity (PINF) | The numeric value is excessively high and unrepresentable due to a floating point processing error.

### Expansion

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

This value set contains 15 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | unknown | Unknown | The value is expected to exist but is not known. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | masked | Masked | The information is not available due to security, privacy or related reasons. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | not-applicable | Not Applicable | There is no proper value for this element (e.g. last menstrual period for a male). |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | unsupported | Unsupported | The source system wasn't capable of supporting this element. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | as-text | As Text | The content of the data is represented in the resource narrative. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | error | Error | Some system or workflow process error means that the information is not available. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | not-performed | Not Performed | The value is not available because the observation procedure (test, etc.) was not performed. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | not-permitted | Not Permitted | The 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` | asked-unknown | Asked But Unknown | The source was asked but does not know the value. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | temp-unknown | Temporarily Unknown | There is reason to expect (from the workflow) that the value may become known. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | not-asked | Not Asked | The workflow didn't lead to this value being known. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | asked-declined | Asked But Declined | The source was asked but declined to answer. |  |
`http://terminology.hl7.org/CodeSystem/data-absent-reason` | not-a-number | Not 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` | negative-infinity | Negative 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` | positive-infinity | Positive Infinity (PINF) | The numeric value is excessively high and unrepresentable due to a floating point processing error. |  |

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