Uzbekistan Digital Health Platform
0.5.0 - ci-build
UZ
Uzbekistan Digital Health Platform, published by Ministry of Health of the Republic of Uzbekistan. This guide is not an authorized publication; it is the continuous build for version 0.5.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/uzinfocom-org/digital-health-ig/ and changes regularly. See the Directory of published versions
| Official URL: https://terminology.dhp.uz/fhir/core/ValueSet/data-absent-reason-vs | Version: 0.5.0 | ||||
| Draft as of 2026-05-13 | Computable Name: DataAbsentReasonVS | ||||
Defines the reasons why a value is missing in an observation within the Uzbekistan Core Implementation
References
This ValueSet requires the Code system Supplement Data absent reason.
http://terminology.hl7.org/CodeSystem/data-absent-reason version 📍1.0.0
Expansion performed internally based on:
This value set contains 15 concepts
| Level | System | Code | Display (en) | Definition | JSON | XML |
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | unknown | Unknown | The value is expected to exist but is not known. | ||
| 2 | http://terminology.hl7.org/CodeSystem/data-absent-reason | asked-unknown | Asked But Unknown | The source was asked but does not know the value. | ||
| 2 | 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. | ||
| 2 | http://terminology.hl7.org/CodeSystem/data-absent-reason | not-asked | Not Asked | The workflow didn't lead to this value being known. | ||
| 2 | http://terminology.hl7.org/CodeSystem/data-absent-reason | asked-declined | Asked But Declined | The source was asked but declined to answer. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | masked | Masked | The information is not available due to security, privacy or related reasons. | ||
| 1 | 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). | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | unsupported | Unsupported | The source system wasn't capable of supporting this element. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | as-text | As Text | The content of the data is represented in the resource narrative. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | error | Error | Some system or workflow process error means that the information is not available. | ||
| 2 | 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. | ||
| 2 | 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. | ||
| 2 | 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. | ||
| 1 | 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. | ||
| 1 | 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). |