Uzbekistan Digital Health Platform - Integrations
0.10.0 - draft
This page is part of the Uzbekistan Digital Health Platform - Integrations (v0.10.0: Releases Draft) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
The patient's social status is represented using the UZ Core Socioeconomic Observation profile.
Examples: example-psychiatry-socio-economic-observation
The observation identifies the social-status observation using SNOMED CT concept 82996008. The patient's actual social status is recorded in valueCodeableConcept using SocialStatusVS.
| Information to record | Value set | Example code | Stored in |
|---|---|---|---|
| Observation status | ObservationStatus | final |
status |
| Observation type | SocioeconomicObservationCodesVS | SNOMED CT#82996008 |
code |
| Social status | SocialStatusVS | regis0010.00003 (Employed) |
valueCodeableConcept |
| Patient | - | reference to UZCorePatient | subject |
| Observation date | - | 2026-08-15 |
effectiveDateTime |
| Performer | - | reference to UZCorePractitionerRole | performer |
The subject references the patient whose social status is being recorded.
The patient's psychiatry registration and dynamic observation group are represented using the Psychiatry Episode Of Care profile.
Examples: example-psychiatry-episode-of-care
The episode records the patient's registration status, service type, dynamic observation group, diagnoses associated with the episode, patient, managing organization, registration period, and responsible practitioner role.
| Information to record | Value set | Example code | Stored in |
|---|---|---|---|
| Identifier | - | https://dhp.uz/fhir/core/sid/reg/uz/psychiatry |
identifier |
| Registration status | EpisodeOfCareStatusVS | active |
status |
| Service type | Episode Of Care Type | mserv-0001-00004 (Treatment services) |
type[serviceType] |
| Dynamic observation group | NarcologyPsychiatryEpisodeOfCareTypeGroupVS | psycr0001-00001 |
type[group] |
| Diagnosis | ConditionCodeVS | F15.1 |
diagnosis.condition |
| Diagnosis use | Encounter Diagnosis Use | working |
diagnosis.use |
| Patient | - | reference to UZCorePatient | patient |
| Managing organization | - | reference to UZCoreOrganization | managingOrganization |
| Registration date | - | 2026-08-15 |
period.start |
| Care manager | - | reference to UZCorePractitionerRole | careManager |
When the patient is registered in the Psychiatry Registry, the episode status is active.
When the patient is removed from registration, the episode status should be finished.
The dynamic observation group is represented using the group slice on EpisodeOfCare.type.
The defined narcology and psychiatry episode-of-care group codes are:
| Code | SNOMED CT code | RU | UZ | ENG |
|---|---|---|---|---|
narcr0001-00001 |
302805002 |
Профилактическая группа | Profilaktik guruh | Preventive group |
narcr0001-00002 |
225419007 |
Диспансерная группа | Dispanser guruhi | Dispensary group |
psycr0001-00001 |
52748007 |
Стационарное принудительное лечение | Majburiy statsionar davolanish | Compulsory inpatient treatment |
The SNOMED CT mappings are defined by the Narcology and Psychiatry EpisodeOfCare Type Groups to SNOMED CT.
When recording a diagnosis associated with the psychiatry episode, implementers should use the applicable code from ConditionCodeVS.
The Psychiatry Registry examples use the following diagnosis:
| Clinical condition | Code system | Code | When to record |
|---|---|---|---|
| Harmful use of other stimulants, including caffeine | ICD-10 | F15.1 |
Record when this psychiatry diagnosis applies to the patient |
The episode may contain multiple diagnoses. Each diagnosis.condition references the corresponding UZ Core Condition.
A patient's medical visit within the Psychiatry Registry is represented using the UZ Core Encounter profile.
Examples: example-psychiatry-encounter
The encounter represents the medical visit recorded by the healthcare provider and may be associated with the patient's PsychiatryEpisodeOfCare.
| Information to record | Value set | Example code | Stored in |
|---|---|---|---|
| Encounter status | Encounter Status | completed |
status |
| Patient | - | reference to UZCorePatient | subject |
| Episode of care | - | reference to PsychiatryEpisodeOfCare | episodeOfCare |
| Actual encounter period | - | starts 2026-08-15 |
actualPeriod |
| Participant type | Participant Type | ATND |
participant.type |
| Encounter practitioner | - | reference to UZCorePractitionerRole | participant.actor |
| Encounter type | - | mserv-0001-00004 (Treatment services) |
type |
| Diagnosis | ConditionCodeVS | F15.1 |
diagnosis.condition |
| Diagnosis use | Encounter Diagnosis Use | final |
diagnosis.use |
The encounter status may be:
in-progresson-holdcompletedcancelledentered-in-errorThe episodeOfCare reference may be used to associate the encounter with the patient's psychiatry registration episode.
An encounter may contain multiple diagnoses. Each diagnosis references a UZ Core Condition and may have an associated diagnosis-use value.
The medical-consultation commission's decision is represented using the PsychiatryCommissionObservation profile.
Examples: example-psychiatry-commission-observation
The profile is used to record the decision of the medical-consultation commission, including the decision result and, where applicable, the protocol number or court name supporting a compulsory-treatment decision.
| Information to record | Value set | Example code | Stored in |
|---|---|---|---|
| Identifier | - | https://dhp.uz/fhir/core/sid/reg/uz/psychiatry |
identifier |
| Observation status | Observation Status | final |
status |
| Commission decision type | TypeResourceCS | type-res-0002-0001 (fixed) |
code |
| Patient | - | reference to UZCorePatient | subject |
| Encounter | - | reference to UZCoreEncounter | encounter |
| Commission decision date | - | 2026-08-15 |
effectiveDateTime |
| Commission member | - | reference to UZCorePractitionerRole | performer |
| Commission result | - | Compulsory inpatient treatment is required. |
valueString |
| Free-text note | - | clinical summary supporting the decision | note |
| Protocol number / court name | - | Protocol No. 123, Tashkent City Civil Court |
component[protocolNumber].valueString |
The commission decision type is:
| Code | SNOMED CT code | RU | UZ | ENG |
|---|---|---|---|---|
type-res-0002-0001 |
444804000 |
Решение комиссии | Komissiya qarori | The commission's decision |
The corresponding terminology is defined in TypeResourceCS, and the SNOMED CT mapping is defined by the Type Resource to SNOMED CT ConceptMap.
The protocolNumber component is used to record the protocol number or court name associated with a compulsory-treatment decision. It uses type-resource-cs#type-res-0002-0002.
Each commission member is recorded as a separate performer reference.
A psychiatry-related clinical condition is represented using the PsychiatryCondition profile.
Examples: example-psychiatry-condition
The PsychiatryCondition profile records the clinical status, verification status, diagnosis, patient, related encounter, onset date, registration date, and organization providing the information.
| Information to record | Value set | Example code | Stored in |
|---|---|---|---|
| Identifier | - | https://dhp.uz/fhir/core/sid/reg/uz/psychiatry |
identifier |
| Clinical status | Condition Clinical Status Codes | active |
clinicalStatus |
| Verification status | Condition Verification Status | confirmed |
verificationStatus |
| Diagnosis | ConditionCodeVS | F15.1 |
code |
| Patient | - | reference to UZCorePatient | subject |
| Encounter | - | reference to UZCoreEncounter | encounter |
| Onset date | - | 2026-08-15 |
onsetDateTime |
| Registration date | - | 2026-08-15 |
recordedDate |
| Information provider | - | reference to UZCoreOrganization | participant.actor |
The clinical status is required.
When the condition is currently applicable to the patient, its status should be active.
When the condition is no longer applicable, the condition status should be changed according to the appropriate FHIR clinical-status semantics, for example resolved where applicable.
Implementers should use the applicable diagnosis code from ConditionCodeVS.
The Psychiatry Registry examples use the following diagnosis:
| Condition | Code system | Code | When to record |
|---|---|---|---|
| Harmful use of other stimulants, including caffeine | ICD-10 | F15.1 |
Record when this psychiatry diagnosis applies to the patient |
Each condition is associated with the patient through subject.
When a condition is identified or managed during a specific medical encounter, the encounter reference may be populated.
Important registry information that healthcare providers should be aware of when assessing, treating, or managing a patient is represented using the NarcologyPsychiatryFlag profile.
Examples: example-psychiatry-flag
The Flag resource is shared by the Narcology and Psychiatry Registries and is used to record registry information such as social danger, compulsory treatment, legal guardian status, disability, and compulsory inpatient treatment.
| Information to record | Value set | Example code | Stored in |
|---|---|---|---|
| Flag status | FlagStatusVS | active |
status |
| Registry flag | NarcologyPsychiatryRegistryFlagVS | psycr0001-00001 |
code |
| Patient | - | reference to UZCorePatient | subject |
| Validity period | - | 2026-08-15 |
period |
| Encounter | - | reference to UZCoreEncounter | encounter |
| Author | - | reference to UZCorePractitionerRole | author |
The flag status is required and may be:
activeinactiveentered-in-errorThe registry flag codes applicable to Narcology and Psychiatry are:
| Code | SNOMED CT code | SNOMED name | RU | UZ | ENG |
|---|---|---|---|---|---|
registri0001-00001 |
129707006 |
At increased risk for other-directed violence (finding) | Социальная опасность | Ijtimoiy xavflilik | Social danger / Social risk |
registri0001-00002 |
303163003 |
Treatments administered under the provisions of the law (regime/therapy) | Принудительное лечение | Majburiy davolanish | Compulsory treatment |
registri0001-00003 |
303163003 |
Treatments administered under the provisions of the law (regime/therapy) | Принудительное амбулаторное лечение | Majburiy ambulatoriya sharoitida davolanish | Compulsory outpatient treatment |
registri0001-00005 |
1193838006 |
Legal guardian status (observable entity) | Под опекой | Vasiylik ostida | Legal guardian status |
registri0001-00006 |
21134002 |
Disability (finding) | Инвалидность | Nogironlik | Disability |
psycr0001-00001 |
52748007 |
Involuntary hospital admission (procedure) | Стационарное принудительное лечение | Majburiy statsionar davolanish | Compulsory inpatient treatment |
The psycr0001-00001 code is specifically applicable to the Psychiatry Registry. The code is defined in the shared NarcologyPsychiatryEpisodeOfCareTypeGroupCS CodeSystem and is included in the NarcologyPsychiatryRegistryFlagVS ValueSet.
The complete mapping between registry flag codes and SNOMED CT concepts is defined by the Narcology and Psychiatry Registry Flags to SNOMED CT ConceptMap.
The subject identifies the patient to whom the registry flag applies.
The encounter may be used to associate the flag with a specific medical encounter.
The author references the practitioner role responsible for recording the flag.
The terminology used by the Psychiatry Registry resources is summarized below.
| Terminology | Resource / Element | Purpose |
|---|---|---|
| SocialStatusVS | Observation.valueCodeableConcept |
Patient's social status |
| SocioeconomicObservationCodesVS | Observation.code |
Identifies the social-status observation |
| NarcologyPsychiatryEpisodeOfCareTypeGroupVS | EpisodeOfCare.type[group] |
Dynamic observation group shared with Narcology |
| EpisodeOfCareStatusVS | EpisodeOfCare.status |
Psychiatry registration lifecycle |
| TypeResourceCS | Observation.code |
Medical-consultation commission decision |
| ConditionCodeVS | Condition.code, EpisodeOfCare.diagnosis.condition |
Psychiatry diagnosis |
| NarcologyPsychiatryRegistryFlagVS | Flag.code |
Narcology and Psychiatry registry flags |
| FlagStatusVS | Flag.status |
Flag lifecycle |
A typical Psychiatry Registry record may connect the resources as follows:
Patient is the central subject.PsychiatryEpisodeOfCare.psycr0001-00001.These resources are linked through patient, episode-of-care, encounter, organization, and practitioner-role references to represent the patient's psychiatry registration, clinical diagnoses, social status, medical encounters, commission decisions, and important registry flags.