Uzbekistan Digital Health Platform
0.3.0 - ci-build
Uzbekistan Digital Health Platform
0.3.0 - ci-build
Uzbekistan Digital Health Platform, published by Uzinfocom LLC. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/vadi2/DHP-temp/ and changes regularly. See the Directory of published versions
| Official URL: https://terminology.dhp.uz/fhir/core/ValueSet/encounter-priority-vs | Version: 0.3.0 | |||
| Draft as of 2025-10-02 | Computable Name: EncounterPriorityVS | |||
Encounter priority codes with English and Russian translations
References
This ValueSet requires the Code system Supplement Encounter priority translations.
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ActPriority| Code | Display | Definition |
| EM | emergency | An unforeseen combination of circumstances or the resulting state that calls for immediate action. |
| P | preop | Used to indicate that a service is to be performed prior to a scheduled surgery. When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service. When the order is placed, a message can be generated indicating the time needed for the service so that it is not ordered in conflict with a scheduled operation. |
| PRN | as needed | An "as needed" order should be accompanied by a description of what constitutes a need. This description is represented by an observation service predicate as a precondition. |
https://terminology.dhp.uz/fhir/core/CodeSystem/encounter-priority-home-cs
| Code | Display |
| gencl-0002-00001 | Yuqori |
| gencl-0002-00002 | O'rtacha |
| gencl-0002-00003 | Past |
Expansion performed internally based on:
This value set contains 6 concepts
| Code | System | Display | Definition |
| EM | http://terminology.hl7.org/CodeSystem/v3-ActPriority | emergency | An unforeseen combination of circumstances or the resulting state that calls for immediate action. |
| P | http://terminology.hl7.org/CodeSystem/v3-ActPriority | preop | Used to indicate that a service is to be performed prior to a scheduled surgery. When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service. When the order is placed, a message can be generated indicating the time needed for the service so that it is not ordered in conflict with a scheduled operation. |
| PRN | http://terminology.hl7.org/CodeSystem/v3-ActPriority | as needed | An "as needed" order should be accompanied by a description of what constitutes a need. This description is represented by an observation service predicate as a precondition. |
| gencl-0002-00001 | https://terminology.dhp.uz/fhir/core/CodeSystem/encounter-priority-home-cs | Yuqori | |
| gencl-0002-00002 | https://terminology.dhp.uz/fhir/core/CodeSystem/encounter-priority-home-cs | O'rtacha | |
| gencl-0002-00003 | https://terminology.dhp.uz/fhir/core/CodeSystem/encounter-priority-home-cs | Past |
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 |