This page is part of the FUT Infrastructure (v3.1.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://ehealth.sundhed.dk/vs/data-absent-reason | Version: 3.1.0 | |||
Active as of 2023-04-13 | Computable Name: DataAbsentReason |
Used to specify why the normally expected content of the data element is missing.
References
Generated Narrative: ValueSet ehealth-data-absent-reason
http://terminology.hl7.org/CodeSystem/data-absent-reason
Code | Display | Definition |
asked-declined | Asked But Declined | The source was asked but declined to answer. |
error | Error | Some system or workflow process error means that the information is not available. |
Generated Narrative: ValueSet
Expansion based on:
This value set contains 2 concepts
Code | System | Display | Definition |
asked-declined | http://terminology.hl7.org/CodeSystem/data-absent-reason | Asked But Declined | The source was asked but declined to answer. |
error | http://terminology.hl7.org/CodeSystem/data-absent-reason | Error | Some system or workflow process error means that the information is not available. |
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 |