O‘zbekiston Raqamli sog‘liqni saqlash platformasi
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
| Rasmiy URL: https://terminology.dhp.uz/fhir/core/ValueSet/data-absent-reason-vs | Versiya: 0.5.0 | ||||
| Draft 2026-05-13 holatiga ko‘ra | Kompyuterda qayta ishlanadigan nom: 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 (uz) | Definition | JSON | XML |
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | unknown | Noma'lum | The value is expected to exist but is not known. | ||
| 2 | http://terminology.hl7.org/CodeSystem/data-absent-reason | asked-unknown | So'ralgan, lekin noma'lum | The source was asked but does not know the value. | ||
| 2 | http://terminology.hl7.org/CodeSystem/data-absent-reason | temp-unknown | Vaqtincha noma'lum | 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 | So'ralmagan | The workflow didn't lead to this value being known. | ||
| 2 | http://terminology.hl7.org/CodeSystem/data-absent-reason | asked-declined | So'raldi, lekin rad etildi | The source was asked but declined to answer. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | masked | Yashirin | The information is not available due to security, privacy or related reasons. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | not-applicable | Qo'llab bo'lmaydigan | 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 | Qo'llab-quvvatlanmaydi | The source system wasn't capable of supporting this element. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | as-text | Matn ko'rinishida | The content of the data is represented in the resource narrative. | ||
| 1 | http://terminology.hl7.org/CodeSystem/data-absent-reason | error | Yashirin | 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 | Son emas | 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 | Manfiy cheksizlik | 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 | Musbat cheksizlik | 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 | Bajarilmagan | 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 | Ruxsat berilmagan | The value is not permitted in this context (e.g. due to profiles, or the base data types). |