Uzbekistan Digital Health Platform
0.5.0 - ci-build
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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| DHPCapabilityStatement |
DHP platform capability statement, describing the supported resources, profiles, and searchparameters |
These define forms used by systems conforming to this implementation guide to capture or expose data to end users.
| Patient Satisfaction Survey |
Example patient satisfaction survey questionnaire (for Patient Portal) |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| UZ Core AdverseEvent |
Uzbekistan Core AdverseEvent profile, used to represent an adverse event that may be associated with unintended consequences for a patient or research participant. |
| UZ Core AllergyIntolerance |
Uzbekistan Core profile for AllergyIntolerance, representing clinical records of allergy or intolerance within the national health information exchange. |
| UZ Core AuditEvent |
Uzbekistan Core AuditEvent profile, used to track user and application activity |
| UZ Core Condition |
Uzbekistan Core Condition profile, used for documenting a patient's symptoms, conditions, and their characteristics |
| UZ Core Consent |
Uzbekistan Core Consent profile, used to manage patient consent for data sharing and processing |
| UZ Core Encounter |
Uzbekistan Core Encounter profile, used to represent clinical encounters |
| UZ Core EpisodeOfCare |
Uzbekistan Core profile for EpisodeOfCare, representing a patient's period of long-term care such as pregnancy care or chronic disease management. |
| UZ Core Goal |
Uzbekistan Core Goal profile, used for a patient, group or organization care. For example: weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. |
| UZ Core HealthcareService |
Uzbekistan Core HealthcareService profile, used to define healthcare services available |
| UZ Core Immunization |
Uzbekistan Core Immunization profile, used to represent immunization events |
| UZ Core ImmunizationRecommendation |
Uzbekistan Core ImmunizationRecommendation profile, used to represent guidance or recommendations related to immunization. |
| UZ Core Location |
Uzbekistan Core Location profile, used to define locations of healthcare services |
| UZ Core Observation |
Uzbekistan Core Observation profile, used to represent clinical and laboratory observations using SNOMED CT, LOINC, or local codes |
| UZ Core Organization |
Uzbekistan Core Organization profile, used to define healthcare organizations and sub-units |
| UZ Core Patient |
Uzbekistan Core Patient profile, used to represent patients administrative information |
| UZ Core PlanDefinition |
Uzbekistan Core PlanDefinition profile, used to express the national immunization schedule as computable logic |
| UZ Core Practitioner |
Uzbekistan Core Practitioner profile, used to define healthcare practitioners |
| UZ Core PractitionerRole |
Uzbekistan Core PractitionerRole profile, used to define roles of practitioners |
| UZ Core Procedure |
Uzbekistan Core Procedure Profile, used for documenting an action that is or was performed on or for a patient, practitioner, device, organization, or location. |
| UZ Core Provenance |
Uzbekistan Core Provenance profile, used to digitally sign documents via oneID |
| UZ Core Questionnaire |
Uzbekistan Core Questionnaire profile for multilingual structured data capture forms |
| UZ Core QuestionnaireResponse |
Uzbekistan Core QuestionnaireResponse profile for capturing responses with digital signature support |
| UZ Core RelatedPerson |
Uzbekistan Core RelatedPerson profile, used to represent persons related to the patient |
| UZ Core Socioeconomic Observation |
Uzbekistan Core socioeconomic observation profile, used to represent patients' benefits, education, profession, and social status. |
| UZ Core Specimen |
Uzbekistan Core profile for representing laboratory and other clinical specimens in Uzbekistan. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Coverage area |
Administrative territory that this organization provides services to. Use the SSVAdministrativeTerritoryToRegionsCM ConceptMap to translate SSV territory codes to the required StateCS codes. |
| Diagnosis type |
Extension to differentiate the diagnosis type, which is different from the condition type / category |
| Differentiation of the administrative gender 'other' |
Extension for more precise differentiation of the administrative gender 'other', aligned with German base profiles representation of the same concept. |
| Managing organization attachment date |
Date when the patient was attached to the managing organization. In Uzbekistan, patients can only change their managing organization once a year. |
| Patient nationality |
The nationality of the patient. |
These define sets of codes used by systems conforming to this implementation guide.
| Action code translations |
Action code codes with Uzbek and Russian translations |
| Action condition translations |
Action condition codes with Uzbek and Russian translations |
| Admission Origin ValueSet |
ValueSet for local admission origin codes |
| Allergen codes value set |
Value set containing SNOMED CT codes and local codes for allergen codes |
| Allergy category value set |
Categories of allergies or intolerances with Uzbek and Russian designations |
| Allergy clinical status value set |
Value set defining codes that represent the clinical status of an allergy or intolerance. |
| Allergy reaction manifestation value set |
Value set containing SNOMED CT codes and local codes for allergy reaction manifestation |
| Allergy reaction severity value set |
Severity levels of allergy or intolerance reactions. |
| Allergy reaction substance value set |
Value set containing SNOMED CT codes and local codes for allergy reaction substance |
| Allergy types value set |
Value set defining codes representing different types of allergies or intolerances. |
| Allergy verification status value set |
Value set defining codes that represent the verification status of an allergy or intolerance. |
| Audit event action |
Defines audit event action that is being recorded in Uzbek and Russian |
| Audit event outcome |
Defines the outcome of the event that is being recorded in Uzbek and Russian |
| Audit event role type |
Defines how the participant participated in Uzbek and Russian |
| Audit event subtype |
Defines the subtype of event that is being recorded in Uzbek and Russian |
| Audit event type |
Defines the type of event that is being recorded in Uzbek and Russian |
| Cancer-related services |
Defines the actual cancer-related services in Uzbek and Russian |
| Categories of cancer-related services |
Defines categories of cancer-related services in Uzbek and Russian |
| Clinical information |
Relevant clinical information status types |
| Combined status of a specimen |
Uzbekistan local specimen combined status types |
| Condition Codes |
Codes for conditions, allowing use of both ICD-10 and SNOMED CT as appropriate on the context |
| Consent State Codes |
Defines the consent state codes in Uzbek and Russian |
| Consent policies |
Determines the regulatory basis for consent |
| Consent provision type |
Determines the type of consent |
| Consent purpose of use |
Defines the purposes of use for consent |
| Coverage Type ValueSet |
ValueSet for coverage types (financing sources of treatment) |
| DMED Vaccine ValueSet |
DMED Vaccine codes |
| DMED measure unit value set |
Value set containing all measurement unit codes from the DMED system |
| DMED positions and professions value set |
Value set containing all position and profession codes from the DMED system |
| Defines a nationality of a person as used in Uzbekistan from dmp.uz |
Nationality |
| Defines the possible positions and professions |
State classification of positions of employees and worker professions (KODP-2020) |
| Diagnosis Type |
Diagnosis types in Uzbekistan |
| Differentiation of the administrative gender 'other' |
Defines the differentiation of the administrative gender 'other' in Uzbek and Russian |
| Disability levels |
Disability levels in Uzbekistan |
| Education levels |
Education levels in Uzbekistan |
| Encounter Reason Use Codes |
Encounter reason use codes with Uzbek and Russian translations |
| Encounter admission translations |
Encounter readmission codes with Uzbek and Russian translations |
| Encounter admit source translations |
Encounter admit source codes with English and Russian translations |
| Encounter class translations |
Encounter Class codes with Uzbek and Russian translations |
| Encounter discharge disposition translations |
Encounter discharge disposition codes with English and Russian translations |
| Encounter participant type translations |
Encounter participant type codes with Uzbek and Russian translations |
| Encounter priority translations |
Encounter priority codes with English and Russian translations |
| Encounter status translations |
Encounter status codes with Uzbek and Russian translations |
| Encounter subject status translations |
Encounter subject status codes with English and Russian translations |
| Encounter type translations |
Defines encounter type codes with English and Russian translations |
| EpisodeOfCare reason use value set |
Allowed reason use for EpisodeOfCare in Uzbekistan's health information exchange. |
| EpisodeOfCare status value set |
Allowed codes for EpisodeOfCare status in Uzbekistan's health information exchange. |
| EpisodeOfCare type value set |
Allowed codes for EpisodeOfCare types in Uzbekistan's health information exchange. |
| Foreign Driver's License System Value Set |
Allowed system URIs for foreign (non-Uzbekistan) driver's license identifiers. Used in the UZ Core Patient profile for the driversLicenseForeign slice. |
| Foreign Passport System Value Set |
Allowed system URIs for foreign (non-Uzbekistan) passport identifiers. Used in the UZ Core Patient profile for the passportForeign slice. |
| Goal Achievement VS |
Value Set for Goal Achievement translations |
| Goal Category VS |
Value Set for Goal Category translations |
| Goal Description VS |
Value Set for Goal Description |
| Goal Lifecycle Status VS |
Value Set for Goal Lifecycle Status translations |
| Goal Priority VS |
Value Set for Goal Priority translations |
| Goal Start Event VS |
Value Set for Goal Start Event |
| ISO 3166 part 1 2-letter codes |
Defines Uzbek and Russian translations for ISO 3166 part 1 2-letter codes |
| ISO 3166 part 1 2-letter codes, sans Uzbekistan |
Defines Uzbek and Russian translations for ISO 3166 part 1 2-letter codes, sans Uzbekistan, for international addresses |
| Identifier domain |
Description of the identifier systems acceptable for entity (patient, practitioner, organization) identification. This is modelled after the Estonian Identifier Domain with the exception that country codes are ISO 3166 two letter codes for consistency within UZ Core. |
| Immunization funding source value set |
Immunization funding source codes with Uzbek and Russian translations |
| Immunization origin value set |
Immunization origin codes with Uzbek and Russian translations |
| Immunization recommendation date criterion value set |
Immunization recommendation date criteria codes with Uzbek and Russian translations |
| Immunization recommendation forecast status value set |
Immunization recommendation forecast status codes with Uzbek and Russian translations |
| Immunization recommendation reason value set |
Immunization recommendation reason codes with Uzbek and Russian translations |
| Immunization site value set |
Immunization site codes with Uzbek and Russian translations |
| Immunization status reason value set |
Immunization status reason codes with Uzbek and Russian translations |
| Immunization status value set |
Immunization status codes with English and Russian translations |
| Immunization subpotent reason value set |
Immunization subpotent reason codes with Uzbek and Russian translations |
| License, certificate, degree |
Defines the type of license, certificate, degree in Uzbek and Russian |
| Location Kinds |
Defines the kind of Location in Uzbek and Russian |
| Location status |
Defines type of Location |
| Location types |
Location types defined by the Ministry of Health of the Republic of Uzbekistan |
| Mahallas translations |
Mahallas names with English and Russian translations |
| Marital status translations |
Defines marital status codes in Uzbek and Russian |
| Nomenclature group |
High-level classification of healthcare institutions by functional category (e.g., hospitals, outpatient clinics, emergency services). This is a broad grouping defined by the Ministry of Health; for detailed institution types, see OrganizationalStructureVS. |
| Object role |
Defines object's role in Uzbek and Russian |
| Observation Laboratory methods |
Observation Laboratory methods in Uzbekistan |
| Observation category |
Observation category in Uzbekistan |
| Observation codes |
Codes for observations, allowing use of LOINC, local laboratory codes, and SNOMED CT as appropriate for the context |
| Observation normal value |
Observation normal value in Uzbekistan |
| Observation status |
Observation status in Uzbekistan |
| Organization Identifier Domain Value Set |
Allowed codes for organization identification domains (national tax numbers, registration numbers, etc) in Uzbekistan's health information exchange. Used in the UZ Core Organization profile. |
| Organization group types of Uzbekistan |
Organization group types of Uzbekistan |
| Organization types of Uzbekistan |
Organization types of Uzbekistan |
| Organizational service group |
Classifies healthcare organizations by their service delivery capabilities (e.g., outpatient only, inpatient only, outpatient + inpatient, day hospital). Defined by the Ministry of Health. |
| Organizational specialization |
Determines the specialization of a medical organization |
| Organizational structure |
Detailed classification of healthcare institution types (e.g., specialized centers, clinical hospitals, dispensaries). This is a granular categorization defined by the Ministry of Health; for high-level functional groupings, see NomenclatureGroupVS. |
| Organizational subordination group |
Defines the subordination group of the medical organization |
| Organizational subordination institution |
Defines the type of medical organizations without forming a legal entity |
| Participant resource types translations |
Participant resource types codes with Uzbek and Russian translations |
| Patient Identifier Domain Value Set |
Allowed codes for patient identification domains (international passport numbers, drivers licenses) in Uzbekistan's health information exchange. Used in the UZ Core Patient profile. |
| Possible consent actions |
Determines the actions that can be taken with consent |
| Practitioner Identifier Domain Value Set |
Allowed codes for practitioner identification domains (national unique identifiers, etc) in Uzbekistan's health information exchange. Used in the UZ Core Practitioner profile. |
| Practitioner roles |
Defines the roles of medical practitioners |
| Procedure Code Codes |
Procedure code ValueSet with translations in English, Russian and Uzbek |
| Procedure Event Status translations |
Procedure event status ValueSet with translations in Uzbek and Russian |
| Procedure Outcome translations |
Procedure outcome ValueSet with translations in Uzbek and Russian |
| Profession specializations |
Defines the specializations of medical professions |
| Provenance Activity Types |
Defines the provenance activity types. |
| Provenance Entity Role |
Defines the provenance entity role. |
| Provenance Participation Role Type |
Defines how the participant participated in Uzbek and Russian |
| Publication status translations |
Publication status codes with Uzbek and Russian translations |
| Purpose of use |
Defines agent's the purpose of use in Uzbek and Russian |
| Reaction Type ValueSet |
Reaction type codes |
| Reference range meaning |
Reference range meaning in Uzbekistan |
| Relationship type |
Relationship types in Uzbekistan |
| Route of administration value set |
Route of administration codes with Uzbek and Russian translations |
| Security label |
Defines security label in Uzbek and Russian |
| Security role type |
Defines the role of the participant that is being recorded in Uzbek and Russian |
| Signature Type |
Defines the possible Provenance signature types. |
| Social status |
Social status types in Uzbekistan |
| Socioeconomic Observation Codes |
Codes for socioeconomic observations including benefits, education, profession, and social status |
| Specimen Status |
Uzbekistan local specimen status types |
| Specimen collection methods (temp) |
Uzbekistan local collection methods of specimen |
| Specimen role |
Codes providing the role of a specimen. |
| Specimen types |
Uzbekistan local specimen types |
| Target disease value set |
Target disease codes with Uzbek and Russian translations |
| Telecom use |
Telecom use types in Uzbekistan |
| Triggered by type |
Triggered by types in Uzbekistan |
| Types of AdverseEvent actuality |
Types of AdverseEvent actuality in Uzbekistan |
| Types of AdverseEvent outcome |
Types of AdverseEvent outcome in Uzbekistan |
| Types of AdverseEvent seriousness |
Types of AdverseEvent seriousness in Uzbekistan |
| Types of AdverseEvent status |
Types of AdverseEvent status in Uzbekistan |
| Types of Condition severities |
Types of Condition severities in Uzbekistan |
| Types of action relationship |
Types of action relationship in Uzbekistan |
| Types of address registration |
Defines type of address registration in Uzbek and Russian |
| Types of benefits |
Types of benefits in Uzbekistan |
| Types of clinical status |
Types of clinical status in Uzbekistan |
| Types of participation role |
Types of participation role in Uzbekistan |
| Types of possible addresses |
Defines the types of addresses with translations in Uzbek and Russian |
| Types of possible contact points |
Defines the contact point |
| Types of possible identifier uses |
Defines the |
| Types of possible identifiers |
Defines identifier |
| Types of possible name uses |
Defines the different uses of a name in Uzbek and Russian |
| Types of verification status |
Types of verification status in Uzbekistan |
| Types of verification status |
Types of verification status in Uzbekistan |
| UZCore Data Absent Reason |
Defines the reasons why a value is missing in an observation within the Uzbekistan Core Implementation |
| UZCore observation interpretation |
Codes representing the clinical meaning of an observation result in the Uzbekistan Core. |
| Uzbekistan Laboratory Service Categories ValueSet |
ValueSet including categories of laboratory healthcare services used in the Uzbekistan. |
| Uzbekistan MVD's international country codes |
Uzbekistan MVD's international country codes with English and Russian translations |
| Uzbekistan MVD's international country codes (excluding Uzbekistan) |
Uzbekistan MVD's international country codes excluding Uzbekistan for international address use |
| Uzbekistan Regions and Locations |
List of regions and locations in Uzbekistan |
| Uzbekistan states and Locations |
List of states and locations in Uzbekistan |
| Vaccine Code ValueSet |
Vaccine codes from CVX and the Australian Immunisation Register Vaccine code systems, with Uzbek and Russian translation supplements. |
| Version algorithm translations |
Version algorithm codes with Uzbek and Russian translations |
These define new code systems used by systems conforming to this implementation guide.
| Act code translations |
Act code supplement with translations in Uzbek and Russian |
| Act reason translations |
Act reason supplement with translations in Uzbek and Russian |
| Action code translations |
Action code supplement with translations in Uzbek and Russian |
| Action condition translations |
Action condition supplement with translations in Uzbek and Russian |
| Action relationship type translations |
Action relationship type supplement with translations in Uzbek and Russian |
| Additional Defines the possible positions and professions |
State classification of positions of employees and worker professions (KODP-2020) |
| Address registration translations |
Types of address registration supplement with translations in Uzbek and Russian |
| Address type translations |
Address type supplement with Uzbek and Russian translations |
| Admit Source Local CodeSystem |
Local admit source codes with Uzbek, English, and Russian translations |
| Admit source from where patient was admitted |
Admit source where patient was admitted from with English and Russian translations |
| AdverseEvent actuality translations |
AdverseEvent actuality supplement with translations in Uzbek and Russian |
| AdverseEvent outcome translations |
AdverseEvent outcome supplement with translations in Uzbek and Russian |
| AdverseEvent seriousness translations |
AdverseEvent seriousness supplement with translations in Uzbek and Russian |
| AdverseEvent status translations |
AdverseEvent status supplement with translations in Uzbek and Russian |
| All FHIR Types |
One of the types defined as part of this version of FHIR with Uzbek and Russian translations. |
| Allergen codes |
Allergy codes supplement with translations in uzbek and russian |
| Allergy category |
Allergy category supplement with translations in uzbek and russian |
| Allergy clinical status |
Allergy clinical status supplement with translations in uzbek and russian |
| Allergy reaction severity |
Allergy reaction severity supplement with translations in uzbek and russian |
| Allergy types |
Allergy types supplement with translations in uzbek and russian |
| Allergy verification status |
Allergy verification status supplement with translations in uzbek and russian |
| Audit event action translations |
Audit event action supplement with translations in Uzbek and Russian |
| Audit event outcome translations |
Audit event outcome supplement with translations in Uzbek and Russian |
| Australian Immunisation Register Vaccine Code Translations |
Supplement providing Uzbek and Russian translations for the Australian Immunisation Register Vaccine code system. |
| CVX Vaccine Code Translations |
Supplement providing Uzbek and Russian translations for the CVX vaccine code system (http://hl7.org/fhir/sid/cvx). |
| Cancer Types |
List of cancer types defined by the Ministry of Health of the Republic of Uzbekistan |
| Clinical status translations |
Clinical status supplement with translations in Uzbek and Russian |
| Confidentiality translations |
Confidentiality supplement with translations in Uzbek and Russian |
| Consent State Codes translations |
Consent State Codes supplement with translations in Uzbek and Russian |
| Consent policies |
Defines the regulatory basis for consent |
| Consent provision type translations |
Consent provision type supplement with translations in Uzbek and Russian |
| Countries digital MVD translations |
Countries digital MVD codes with translations in Russian and English |
| Coverage Type CodeSystem |
Local coverage type codes for financing source of treatment |
| DICOM Controlled Terminology Definitions |
DICOM Controlled Terminology Definitions supplement with translations in Uzbek and Russian |
| DMED Country (UZ/RU) |
Uzbek and Russian designations for DMED Country codes |
| DMED Measure Unit CodeSystem |
Measurement unit codes in the DMED system |
| DMED Positions and Professions (UZ/RU) |
Uzbek and Russian designations for DMED Professions codes |
| DMED Reaction Type Translations |
DMED Reaction Type Code with Uzbek and Russian translations |
| DMED Vaccine Codes |
Russian DMED Vaccine codes |
| Data absent reason |
Data absent reason supplement with translations in Uzbek and Russian |
| Defines the possible location types |
Defines the possible location types in Uzbek and Russian |
| Defines the possible positions and professions |
State classification of positions of employees and worker professions (KODP-2020) |
| Diagnosis Types |
Diagnosis types in Uzbekistan |
| Differentiation of the administrative gender 'other' |
Differentiation of the administrative gender 'other' in Uzbek and Russian |
| Disability levels |
Disability levels in Uzbekistan |
| Education levels |
Education levels in Uzbekistan |
| Encounter Purpose Classification |
Classification of patient encounter purposes in Uzbek and Russian |
| Encounter Type translations |
Encounter type codes with English and Russian translations |
| Encounter admission translations |
Encounter readmission supplement with translations in Uzbek and Russian |
| Encounter admit source translations |
Encounter admit source supplement with translations in Uzbek and Russian |
| Encounter discharge disposition from died |
Encounter discharge disposition home codes with English and Russian translations |
| Encounter discharge disposition translations |
Encounter discharge disposition supplement with translations in Uzbek and Russian |
| Encounter local priority translations |
Defines the local priority types in Uzbek and Russian |
| Encounter priority home translations |
Encounter priority home codes with English and Russian translations |
| Encounter priority translations |
Encounter priority supplement with translations in Uzbek and Russian |
| Encounter reason use translations |
Encounter reason use codes with English and Russian translations |
| Encounter status translations |
Encounter status supplement with translations in Uzbek and Russian |
| Encounter subject status translations |
Encounter subject status codes with English and Russian translations |
| EpisodeOfCare reason use |
Episode of care reason use in Uzbekistan |
| EpisodeOfCare status translations |
EpisodeOfCare status supplement with translation in Uzbek and Russian. |
| EpisodeOfCare types |
Episode of care types in Uzbekistan |
| Goal Achievement CS |
Goal achievement supplement with translations in Uzbek and Russian |
| Goal Category CS |
Goal category supplement with translations in Uzbek and Russian |
| Goal Lifecycle Status CS |
Goal lifecycle status supplement with translations in Uzbek and Russian |
| Goal Priority CS |
Goal priority supplement with translations in Uzbek and Russian |
| HTTP interaction translations |
HTTP interaction supplement with translations in Uzbek and Russian |
| ISO 3166-1 two-letter translations |
ISO 3166-1 2-letter supplement with Uzbek and Russian translations |
| Identifier domain |
Description of the identifier systems acceptable for entity (patient, practitioner, organization) identification. See identifiers page for guidance and examples on using this codesystem. This is modelled after the Estonian Identifier Domain with the exception that country codes are ISO 3166 two letter codes for consistency within UZ Core. |
| Immunization Funding Source translations |
Immunization Funding Source supplement with Uzbek and Russian translations |
| Immunization Origin translations |
Immunization Origin supplement with translations in Uzbek and Russian |
| Immunization Site translations |
Immunization Site supplement with translations in Uzbek and Russian |
| Immunization Status translations |
Immunization Status supplement with translations in Uzbek and Russian |
| Immunization Subpotent Reason translations |
Immunization Subpotent Reason supplement with Uzbek and Russian translations |
| Immunization reason translations |
Immunization recommendation reason supplement with Uzbek and Russian translations |
| Immunization recommendation date criterion translations |
Immunization recommendation date criteria with Uzbek and Russian translations |
| Immunization recommendation forecast status translations |
Immunization recommendation forecast status supplement with translations in Uzbek and Russian |
| Laboratory Observation Panels and Analytes |
Code system defining laboratory observation panels and individual analytes used in Ministry of Health Uzbekistan (399). |
| Laboratory Observation Panels and Analytes |
Code system defining laboratory observation panels and individual analytes used in Uzbekistan. |
| Laboratory Service Categories |
Uzbekistan national classification of laboratory service categories. |
| Laboratory technique (method of measurement) |
Laboratory technique (method of measurement) used for the result measurement |
| License, certificate, degree translations |
License, certificate, degree supplement with translations in Uzbek and Russian |
| Location Kinds |
Defines the kind of Location in Uzbek and Russian |
| Location status translations |
Location status supplement with translations in Uzbek and Russian |
| Mahalla Coats Codes and Names |
Mahalla coats codes and names with translations in Russian and English from coat |
| Mahalla Codes and Names |
Mahalla codes and names with translations in Russian and English |
| Marital status translations |
Marital status supplement with Uzbek and Russian translations |
| Nationality from dmp.uz |
Defines a nationality of a person as used in Uzbekistan from dmp.uz |
| Nomenclature group |
High-level classification of healthcare institutions by functional category (e.g., hospitals, outpatient clinics, emergency services). This is a broad grouping defined by the Ministry of Health; for detailed institution types, see OrganizationalStructureCS. |
| Null Flavor translations |
Null Flavor supplement with Uzbek and Russian translations |
| Observation category translations |
Observation category supplement with translations in Uzbek and Russian |
| Observation interpretation |
Observation interpretation supplement with translations in Uzbek and Russian |
| Observation normal value translations |
Observation normal value supplement with translations in Uzbek and Russian |
| Observation status translations |
Observation status supplement with translations in Uzbek and Russian |
| Organization group types of Uzbekistan |
Organization group types of Uzbekistan |
| Organization types of Uzbekistan |
Organization types of Uzbekistan |
| Organizational Structure |
Detailed classification of healthcare institution types (e.g., specialized centers, clinical hospitals, dispensaries). This is a granular categorization defined by the Ministry of Health; for high-level functional groupings, see NomenclatureGroupCS. |
| Organizational service group |
Classifies healthcare organizations by their service delivery capabilities (e.g., outpatient only, inpatient only, outpatient + inpatient, day hospital). Defined by the Ministry of Health. |
| Organizational specialization |
Determines the specialization of a medical organization |
| Organizational subordination group |
Defines the subordination group of the medical organization |
| Organizational subordination institution |
Defines the type of medical organizations without forming a legal entity |
| Participant resource types translations |
Participant resource types supplement with translations in Uzbek and Russian |
| Participant type translations |
Participant type supplement with translations in Uzbek and Russian |
| Participation type translations |
Participation type supplement with translations in Uzbek and Russian |
| Patient satisfaction survey answers |
Answer codes for the patient satisfaction questionnaire |
| Patient status when receiving care inpatient |
Patient status when receiving care inpatient with English and Russian translations |
| Possible consent actions translations |
Possible consent actions supplement with translations in Uzbek and Russian |
| Possible identifier uses translations |
Types of possible identifier uses supplement with translations in Uzbek and Russian |
| Possible identifiers translations |
Types of possible identifiers supplement with translations in Uzbek and Russian |
| Possible name uses translations |
Types of possible name uses supplement with translations in Uzbek and Russian |
| Procedure Event Status translations |
Procedure Event Status supplement with translations in Uzbek and Russian |
| Profession specializations |
Defines the specializations of medical professions |
| Provenance Activity Types translations |
Provenance Activity Types supplement with translations in Uzbek and Russian |
| Provenance Entity Role translations |
Provenance Entity Role supplement with translations in Uzbek and Russian |
| Provenance Participation Role Type translations |
Provenance Participation Role Type supplement with translations in Uzbek and Russian |
| Publication status translations |
Publication status supplement with translations in Uzbek and Russian |
| Reaction manifestation codes |
Local codes and multilingual names for allergy symptoms. |
| Reaction substance codes |
Local codes and multilingual names for allergy reaction substance. |
| Readmission Local CodeSystem |
Codes describing whether the admission is first-time or repeated within the current year. |
| Reference range meaning translations |
Meaning of reference range, supplemented with translations in Uzbek and Russian |
| Relationship type |
Relationship types in Uzbekistan |
| Relevant clinical information translations |
Relevant clinical information (v2-0916), supplemented with translations in Uzbek and Russian |
| Role class |
Role class supplement with translations in Uzbek and Russian |
| Role code |
Role code supplement with translations in Uzbek and Russian |
| Route of Administration translations |
Route of administration supplement with Uzbek and Russian translations |
| SSV Administrative Territory |
State Committee on Statistics (SSV) administrative territory codes for Uzbekistan |
| Sample security structural roles |
Sample security structural roles supplement with translations in Uzbek and Russian |
| Secondary Contact Role Definitions |
Contact role supplement with translations in Uzbek and Russian |
| Security role type translations |
Security role type supplement with translations in Uzbek and Russian |
| Signature Type |
Defines the possible Provenance signature types. |
| Social status |
Social status types in Uzbekistan |
| Specimen collection methods (temp) |
Uzbekistan local codesystem collection methods of specimen |
| Specimen combined status translations |
Specimen combined status, supplemented with translations in Uzbek and Russian |
| Specimen local types translations |
Specimen local types, original local codes with translations in Uzbek and Russian |
| Specimen role status translations |
Specimen role status, supplemented with translations in Uzbek and Russian |
| Specimen status translations |
Specimen status, supplemented with translations in Uzbek and Russian |
| Specimen types translations |
Specimen types, supplemented with translations in Uzbek and Russian |
| Target Disease translations |
Target Disease supplement with Uzbek and Russian translations |
| Telecom use |
Telecom use type supplement with translation in Uzbek and Russian |
| Triggered by type translations |
Triggered by type supplement with translations in Uzbek and Russian |
| Types of benefits |
Types of benefits in Uzbekistan |
| Types of possible contact points translations |
Types of possible contact points supplement with translations in Uzbek and Russian |
| Uzbekistan Regions and Locations |
List of regions and locations in Uzbekistan |
| Uzbekistan states and Locations Code System |
List of states and locations in Uzbekistan |
| Verification status types |
Verification status supplement with translations in Uzbek and Russian |
| Verification status types |
Verification status in Uzbekistan |
| Version algorithm translations |
Version algorithm supplement with translations in Uzbek and Russian |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
| Immunization Identifier |
Identifier system for immunization records in Uzbekistan. |
| episodeofcare-identifier |
Identifier system used for EpisodeOfCare resources within the Uzbekistan DHP context. |
| location-unit |
Naming system for unique identifiers assigned to location units such as branches, wards, and beds within healthcare facilities in the Uzbekistan Digital Health Platform |
| patient-id-uzb-birth-certificate |
Birth certificate identifiers assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-drivers-license |
Driver's license identifiers assigned by the Uzbekistan Ministry of Internal Affairs |
| patient-id-uzb-health-card |
Health card number identifiers assigned by the Uzbekistan Ministry of Health |
| patient-id-uzb-military-id |
Military ID number identifiers assigned by the Uzbekistan Ministry of Defense |
| patient-id-uzb-national-id |
National unique identifiers (PINFL) assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-passport-diplomatic |
Diplomatic passport identifiers assigned by the Uzbekistan Ministry of Foreign Affairs |
| patient-id-uzb-passport-international |
International passport identifiers assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-passport-local |
Local (internal) passport identifiers assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-penitentiary-number |
Penitentiary institution number identifiers assigned by the Uzbekistan correctional system |
| patient-id-uzb-pension-number |
The pension number identifier is used to determine whether a patient is registered in the pension system and to identify the type of pension received. |
| patient-id-uzb-provider-assigned |
Provider-assigned patient identifiers issued by healthcare organizations for unidentified patients |
| patient-id-uzb-temp-medical-record |
Temporary medical record numbers for unidentified patients (preferred approach) |
| patient-id-uzb-unknown-patient |
Identifiers for unidentified patients when receiving organization is unknown (fallback) |
| ssv-organization-type-level |
SSV classification of healthcare facility administrative levels (republican, regional, urban, district, etc.) |
| ssv-organization-type-medical |
SSV classification of healthcare facility medical types (hospital, polyclinic, dispensary, etc.) |
| ssv-organization-type-service |
SSV classification of healthcare facility service types (outpatient, inpatient, emergency, etc.) |
| uzb-hrm-argos |
Healthcare provider identifiers assigned by the Uzbekistan Human Resource Management (HRM) system |
| uzb-hrm-argos-practitioner |
Healthcare professional identifiers assigned by the Uzbekistan Human Resource Management (HRM) system |
| uzb-mis-dmed |
Clinical record identifiers issued by the Uzbekistan Medical Information System (MIS) |
| uzb-shif |
Organization identifiers assigned by the State Health Insurance Fund (SHIF) of Uzbekistan |
| uzb-soliq |
Tax identification numbers and other identifiers assigned by the Uzbekistan Tax Authority (Soliq) |
| who-ichi |
WHO International Classification of Health Interventions (ICHI) |
These define transformations to convert between codes by systems conforming with this implementation guide.
| Allergen codes to SNOMED CT |
Maps local UZ allergen codes to SNOMED CT. |
| Allergy manifestations to SNOMED CT |
Maps local UZ ReactionManifestationCS codes to SNOMED CT. |
| Allergy substance to SNOMED CT |
Maps local UZ ReactionSubstanceCS codes to SNOMED CT. |
| DMED Country To DHP Country |
DMED Country to DHP Country ConcepMap |
| DMED Position To DHP Position |
DMED Position and Professions to DHP Position and Professions ConceptMap |
| DMED Position To SNOMED CT |
Maps DMED position and profession codes to SNOMED CT concepts. |
| DMED Vaccine codes To CVX |
ConceptMap for mapping DMED Vaccine codes to CVX vaccine codes |
| DMED measure unit codes To DHP measure unit codes |
ConceptMap for mapping DMED measure unit codes to DHP measure unit codes from unitsofmeasure.org |
| ISO 3166-1 Alpha-3 to Alpha-2 Country Code |
Maps ISO 3166-1 alpha-3 (3-letter) country codes to alpha-2 (2-letter) country codes. For consistency, UZ Core uses 2-letter codes; this ConceptMap is provided to assist 3rd party systems in performing the translation. |
| Laboratory analytes codes to LOINC |
Maps local UZ laboratory analytes codes to LOINC. |
| Laboratory methods codes to LOINC |
Maps local UZ laboratory method (technique of measurement) codes to LOINC method part codes. |
| MIS2 Level Type to Subordination Group |
Maps MIS2 organization level type codes to UZ Core Organizational Subordination Group codes. MIS2 classifies healthcare facilities into administrative levels, while OrganizationalSubordinationGroupCS groups institutions by their administrative subordination (republican, territorial, district/city, other ministries, private). The MIS2 level types Shahar (Urban), Tuman (Area), and Mahalla (District) all fall under the combined district-and-city administration category in the target. |
| MIS2 Medical Type to Organizational Structure |
Maps MIS2 medical type codes to UZ Core Organizational Structure codes. MIS2 classifies healthcare facilities into 45 medical types, while OrganizationalStructureCS provides the Ministry of Health's detailed classification of institution types. |
| MIS2 Service Type to Organizational Service Group |
Maps MIS2 service type codes to UZ Core Organizational Service Group codes. MIS2 uses service type classification per organization, while OrganizationalServiceGroupCS uses a single pre-combined classification. When an organization has multiple MIS2 service types, the combination should be considered to select the appropriate target code (e.g. Inpatient + Outpatient together maps to III_100). |
| Reaction Type codes to SNOMED CT |
Maps local UZ reaction type codes to SNOMED CT. |
| SNOMED CT to ICHI Procedures example |
Maps clinical SNOMED CT codes to ICHI statistical codes for reimbursement reporting - a sample for demo purposes. |
| SSV Administrative Territory to Regions and States |
Maps SSV administrative territory codes to UZ Core StateCS (for regions) and RegionsCS (for districts). Both systems use NATE codes as their underlying identifiers, making this a direct equivalence mapping. Locality-level codes (9213 entries) from the SSV system have no equivalent in the target and are excluded from this map. |
| SSV Level Type to Subordination Group |
Maps SSV organization level type codes to UZ Core Organizational Subordination Group codes. SSV classifies healthcare facilities into administrative levels, while OrganizationalSubordinationGroupCS groups institutions by their administrative subordination (republican, territorial, district/city, other ministries, private). The SSV level types Shahar (Urban), Tuman (Area), and Mahalla (District) all fall under the combined district-and-city administration category in the target. |
| SSV Medical Type to Organizational Structure |
Maps SSV medical type codes to UZ Core Organizational Structure codes. SSV classifies healthcare facilities into 45 medical types, while OrganizationalStructureCS provides the Ministry of Health's detailed classification of institution types. |
| SSV Service Type to Organizational Service Group |
Maps SSV service type codes to UZ Core Organizational Service Group codes. SSV uses service type classification per organization, while OrganizationalServiceGroupCS uses a single pre-combined classification. When an organization has multiple SSV service types, the combination should be considered to select the appropriate target code (e.g. Inpatient + Outpatient together maps to III_100). |
| UZ MVD to ISO 3166-1 Alpha-2 |
Maps Uzbekistan MVD numeric codes to ISO 3166-1 alpha-2 (2-letter) country codes. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Amoxicillin 500 mg capsule |
Example medication suspected as the cause of the adverse event |
| Condition - Tuberculosis vaccination indication |
Example condition representing indication for BCG vaccination. |
| Example ActivityDefinition |
Example ActivityDefinition used by the UZ Core PlanDefinition example to represent the vaccination activity referenced from a plan action. |
| Example Adverse Event - Averted Medication Error |
A potential adverse event (near miss): a contraindicated prednisone order was intercepted before administration, so no dose reached the patient and no harm occurred |
| Example Adverse Event - Fatal Anaphylaxis |
A serious actual adverse event: the patient developed anaphylaxis following amoxicillin administration and died despite resuscitation |
| Example Encounter |
Example of an psychiatric encounter |
| Example Goal |
An example goal instance for a patient aiming to manage benign essential hypertension. |
| Example Medication |
Example medication suspected as the cause of the adverse event |
| Example Transaction Bundle |
Example transaction bundle that submits an episode of care, two encounters, and three observations in a single transaction |
| Example Transaction Error |
Example OperationOutcome returned when a transaction fails due to a validation error |
| Example Transaction Response |
Example of a successful transaction response where all resources were created |
| Example UZ Core AllergyIntolerance - Grass Pollen Allergy |
Example instance conforming to UZCoreAllergyIntolerance. |
| Example UZ Core Condition - Anaphylaxis |
Anaphylactic reaction following amoxicillin administration, recorded as the resulting effect of an adverse event |
| Example UZ Core ImmunizationRecommendation |
Example of an immunization recommendation with non-mandatory elements included. |
| Example Uz Core Condition - Cancer |
Example instance of a cancer diagnosis documented during a patient encounter |
| Example Uz Core Condition - Disability Group I |
Example instance of a disability condition with Group I classification |
| Example Uz Core Condition - Headache |
Example instance of a headache condition documented during a patient encounter |
| Example Uz Core Condition - Pregnancy |
Example instance of a pregnancy condition documented during a patient encounter |
| Example for EpisodeOfCare |
Test example of an episode of care for the UZCoreEpisodeOfCare profile. |
| Example of EpisodeOfCare |
Example EpisodeOfCare for pregnancy management and related treatment services |
| Example of Immunization Organization |
Example of a national immunization organization |
| Example of a Therapeutic Leg Massage Procedure |
An example instance of a UZ Core Procedure profile for a therapeutic massage of the left leg. |
| Immunization - Measles, Mumps and Rubella (MMR) |
Example Immunization resource representing administration of measles, mumps and rubella (MMR) vaccine to a patient. |
| Immunization Recommendation - BCG |
Example ImmunizationRecommendation resource indicating a due BCG vaccine for a patient. |
| Medication - BCG Vaccine |
Example Medication resource representing a Bacillus Calmette-Guerin vaccine. |
| Observation - Post-immunization reaction |
Example Observation capturing a post-immunization reaction for a patient. |
| UZ Core Immunization Example |
Example immunization event for UZ Core Immunization profile. |
| UZ Core PlanDefinition |
Uzbekistan Core PlanDefinition profile, used to represent structured clinical and administrative workflow definitions, including actions, timing, participants, and related activities |
| blood-pressure-example |
Example of a blood pressure vital sign observation with systolic and diastolic components |
| bmi-example |
Example of a body mass index (BMI) vital sign observation |
| body-height-example |
Example of a body height vital sign observation |
| body-temperature-example |
Example of a body temperature vital sign observation |
| body-weight-example |
Example of a body weight vital sign observation |
| cbc-panel-example |
Example of CBC (Umumiy qon tahlili) as a laboratory panel with analytes from observation-lab-research-codes-cs |
| example-auditevent-condition-lookup |
Example of an audit event where a pracititioner looked up the patient's condition |
| example-auditevent-login |
Example of an audit event where a user logs in |
| example-careplan |
Example of a careplan |
| example-cbc-order |
Example ServiceRequest for CBC (Umumiy qon tahlili) order |
| example-consent |
Example of a consent |
| example-david |
Example of a patient named David |
| example-david-benefits |
Example benefits observation for David |
| example-david-education |
Example education observation for David |
| example-david-profession |
Example profession observation for David |
| example-david-social-status |
Example social status observation for David |
| example-emma |
Example of a foreign patient named Emma |
| example-healthcareservice |
Example of a healthcare service |
| example-location |
Example of psychiatric hospital |
| example-location-1 |
Example of an organization location |
| example-location-2 |
Example of a branch location |
| example-medication |
Example of a medication |
| example-organization |
Example of a republican-level oncology center (Respublika onkologiya markazi) with full categorization, contact, and address |
| example-patient |
Example of a patient |
| example-pdf-document |
Example of a PDF document signed via oneID |
| example-practitioner |
Example of a practitioner |
| example-practitioner-gender-other |
Example of a practitioner with a gender extension |
| example-practitionerrole |
Example of a practitioner's role |
| example-practitionerrole-freetext |
Example of a practitioner's role with a freetext description |
| example-provenance |
Example of a provenance event |
| example-related-person |
Example of a related person |
| example-salim |
Example of a patient named Salim |
| example-salim-benefits |
Example benefits observation for Salim |
| example-salim-education |
Example education status for Salim |
| example-salim-profession |
Example profession observation for Salim |
| example-salim-social-status |
Example social status observation for Salim |
| example-specimen-blood-cbc |
Example UZ Core Specimen: venous whole blood collected for a Complete Blood Count (CBC) order. |
| example-unidentified-patient |
Unidentified patient brought in unconscious, with no identifier available. Patient.identifier is mandatory (1..*), so rather than inventing a fake value the single identifier carries a data-absent-reason extension - the resource still validates without fabricating data. |
| head-circumference-example |
Example of a head circumference vital sign observation |
| heart-rate-example |
Example of a heart rate vital sign observation |
| oxygen-saturation-example |
Example of an oxygen saturation vital sign observation with interpretation and reference range |
| respiratory-rate-example |
Example of a respiratory rate vital sign observation |
| tashkent-diseases-hospital |
Example of a hospital organization |
| xonobod-medical-association |
Example of a medical association translated from Hepatitis JSON |
| Пример ответа на опросник удовлетворённости |
Пример заполненного опросника удовлетворённости пациента |