Uzbekistan Digital Health Platform
0.7.0 - ci-build
Uzbekistan Digital Health Platform
0.7.0 - ci-build
Uzbekistan Digital Health Platform - Local Development build (v0.7.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
(No changes yet)
Added UZ Core Claim and UZ Core Claim Response profiles for insurance claims, pre-authorization and predetermination, and for the adjudication and reimbursement responses to them. They are supported by claim type, claim use and financial management status terminology, plus response category, decision and outcome codes. A cancellation reason extension records why a response was cancelled, for example when a pre-authorization expires before the claim completes.
Added UZ Core Task Referral Approval profile for tracking the workflow steps of the state insurance referral and hospitalization approval process (Annex 1 to Resolution of the Cabinet of Ministers No. 694, 04.11.2025), with task code, status, intent and business status terminology. A warning-level constraint flags unfinished tasks that are past their requested end date but not marked overdue, for SLA monitoring.
Added UZ Core Group profile for defined collections of entities - screening, vaccination and donation target groups and their outcome cohorts - with group type, group kind, membership basis and characteristic kind terminology.
Added the CVD risk screening questionnaire, an early-detection form for cardiovascular disease risk that calculates its score and risk category from the answers using SDC FHIRPath expressions. The guide now depends on hl7.fhir.uv.sdc so those expressions resolve.
The organization type ConceptMaps have been renamed from the MIS2 prefix to SSV, matching the SSV ValueSets they map from: SSVLevelTypeToSubordinationGroupCM, SSVMedicalTypeToOrganizationalStructureCM and SSVServiceTypeToOrganizationalServiceGroupCM. The duplicate mis2-* ConceptMaps have been removed; implementers should reference the ssv-* canonical URLs. The nomenclature group mappings have been split out of SSVMedicalTypeToOrganizationalStructureCM into the new SSVMedicalTypeToNomenclatureGroupCM, so that each ConceptMap declares a single source and target scope.
Added SNOMED CT supplements carrying Uzbek and Russian designations for condition severity, procedure outcome, reaction type, goal description, goal start event and socioeconomic observation codes.
The SNOMED CT value sets now select a hierarchy where one expresses the intent, instead of listing individual codes: body site is any body structure, procedure code any procedure, target disease any disease, route code any route of administration, condition severity any severity, adverse event outcome any adverse reaction, and goal description, reaction type and recommendation reason any clinical finding. This widens what these value sets accept compared with 0.6.0. Procedure outcome, socioeconomic observation codes, goal start event and action participant role keep their explicit code lists, because their concepts share no ancestor narrow enough to select on.
Added a UCUM units supplement with Uzbek and Russian translations of the unit displays, surfaced as the UCUM units value set. permittedUnit on UZ Core Laboratory ObservationDefinition is now bound to it (extensible) rather than to the UCUM common units value set, and permittedDataType is now bound (required) to the new laboratory observation value types value set.
Added a laboratory source system units CodeSystem holding the unit strings used by the source laboratory systems, its value set, and a ConceptMap translating them to UCUM, so results arriving with local unit strings can be normalised.
The laboratory panel code system now declares kind and parent properties, so a client expanding the observation codes value set can tell panels apart from the analytes reported within them. Language designations on the panel codes were also corrected.
component.code on UZ Core Laboratory ObservationDefinition gained an additional binding for the user interface flow: when a user creates a custom laboratory definition in the Patient Portal, the analyte code must be selected from LOINC. National laboratory panel codes remain reserved for the pre-defined laboratory catalogue.
method on UZ Core Observation now states its binding strength explicitly as extensible.
UZ Core Immunization PlanDefinition now requires a second useContext stating the kind of schedule, bound (extensible) to the new immunization schedule type value set. The choice-type slicing on action.definition[x] has been removed, because it made the validator reject definitionCanonical, and the examples now use definitionCanonical.
participant.actor on UZ Core Condition may now reference UZ Core Organization.
The UZ Core ActivityDefinition profile has been renamed to UZ Core VaccinationActivityDefinition and its canonical URL changed from .../uz-core-activity-definition to .../uz-core-vaccination-activity-definition. Implementers referencing the old canonical must update it.
On UZ Core Location the tax identifier slice has been removed, and name is optional again (0..1), reverting the requirement introduced in 0.6.0.
Added DMED terminology bridges for administration routes mapped to the national and SNOMED CT route codes, and expanded the measurement unit and vaccine code mappings, with further units added to the DMED measurement unit code system.
Added a Forms page where any questionnaire published by this guide can be filled in as a working form, in Uzbek, Russian or English, to check the wording, answer options, skip logic and calculated results before implementing it. The page can pre-fill a form with sample answers and links to the underlying QuestionnaireResponse JSON.
The modelling guidelines now require terminology versions to be in SemVer format (MAJOR.MINOR.PATCH), because the DHP terminology platform cannot parse other formats, and describe how to encode release identifiers that are not SemVer, such as SNOMED CT's 2026-01.
Added UZ Core DiagnosticReport profile for laboratory and diagnostic reports, with supporting terminology for service category, status and report types.
Added UZ Core ServiceRequest profile for ordering services such as procedures, diagnostic investigations, or panels of investigations, including payment type and request status terminology.
Added UZ Core Specimen profile for clinical specimens, with terminology for collection method, specimen type, role and status. It is referenced from the ServiceRequest and DiagnosticReport profiles.
Added UZ Core Laboratory ObservationDefinition profile so systems can publish definitions of laboratory tests - permitted units, measurement methods and sex-specific reference ranges - for the Patient Portal and integrating systems.
Added UZ Core Immunization profile for recording vaccinations, with terminology for target disease, administration site, route and funding source, plus a ConceptMap translating national DMED vaccine codes to CVX.
Added UZ Core ImmunizationRecommendation profile for vaccination forecasts, with forecast status, date criterion and reason terminology.
Added UZ Core Immunization PlanDefinition profile for national immunization schedules.
Added UZ Core ActivityDefinition profile for defining reusable clinical activities (procedures, tests, medication protocols) independent of a specific patient.
Added UZ Core AdverseEvent profile for reporting adverse events, with actuality, seriousness, outcome and status terminology.
Added UZ Core Medication profile with Uzbekistan-specific medication identifiers (marking ID, registration certificate, GTIN, box aggregation ID, national product/service classification code) and ATC-based classification and dose form terminology.
Added UZ Core Procedure profile, with procedure status, SNOMED CT-based procedure codes and outcome terminology, plus an example SNOMED CT to ICHI ConceptMap for reimbursement reporting.
Added laboratory method codes, with ConceptMaps mapping the laboratory panel and analyte codes to LOINC and method codes to SNOMED CT. The method codes are surfaced as the laboratory methods value set, bound to method on UZ Core Observation.
UZ Core PractitionerRole code is now bound (required) to the position and profession ValueSet (previously the practitioner-role value set); specialty remains bound (required) to the profession specialization ValueSet. Implementers must populate practitioner roles with codes from these value sets.
Added a turnaround time extension to UZ Core HealthcareService for stating the expected result turnaround on laboratory services. The category and type bindings on this profile have also been relaxed from required to extensible, so implementers may add local codes.
type on UZ Core Encounter and UZ Core EpisodeOfCare, and signature.type on UZ Core Provenance, are now sliced so a national code is required while additional codings remain allowed.
Reference targets across several profiles now point to UZ Core profiles where they exist - for example UZ Core Observation specimen to UZ Core Specimen and partOf to UZ Core Procedure/Immunization, UZ Core Immunization administeredProduct to UZ Core Medication, and UZ Core AdverseEvent suspectEntity to UZ Core Medication. Referenced resources must now conform to the corresponding UZ Core profile.
UZ Core Encounter reason and UZ Core Observation basedOn may now reference an ImmunizationRecommendation.
The canonical URLs of the identifier-domain and EpisodeOfCare value sets (and the foreign passport and drivers-license value sets) moved from https://dhp.uz/fhir/core/ValueSet/... to https://terminology.dhp.uz/fhir/core/ValueSet/.... Implementers referencing these canonicals directly must update them.
The nationality CodeSystem, used by the nationality value set on UZ Core Patient, has been rebuilt from the updated dmp.uz nationality list: it grew from 306 to 512 entries, displays were standardised to uppercase, with Russian and English designations added, and codes were reassigned - the same code can now denote a different nationality (e.g. #1 changed from "Ruslar" to "ADIGEY"). This is a breaking change: nationality codes stored under the previous version must be re-mapped.
Corrected English display names in OrganizationalSpecializationCS (consistent casing; "Children" changed to "Pediatric"). Codes are unchanged.
Added DMED terminology bridges for ingesting data from the national DMED system: country codes mapped to ISO 3166, measurement units to UCUM, and DMED professions mapped to both SNOMED CT and DHP positions.
gender on UZ Core Patient is now bound (required) to a new administrative gender ValueSet with Russian and Uzbek translations.
managingOrganization on UZ Core Patient is now Must Support and must reference UZ Core Organization.
The multilingual translation extension (Uzbek base value plus Russian and Karakalpak translations) has been added to name on UZ Core HealthcareService, and to title on UZ Core ActivityDefinition, UZ Core Laboratory ObservationDefinition, UZ Core Immunization PlanDefinition and UZ Core Questionnaire. name is now required on UZ Core Organization and UZ Core Location.
Added State Health Insurance Fund (SHIF) and Ministry of Health (Minzdrav) identifier slices to UZ Core Organization. SHIF-assigned provider codes are typed as PRN (provider number). A new payor identification page explains how payors and their contracted providers are identified.
On UZ Core Patient and UZ Core RelatedPerson, the local passport identifier no longer fixes use to official: use official for the current ID card and old for a superseded paper passport sharing the same system. See the identifiers page.
Added implementation guidance pages - how to read this guide, general guidance and Must Support - plus end-to-end workflow walkthroughs for the laboratory, immunization, referral, patient journey and prescription processes. Each profile now also has narrative intro and notes sections.
Added guidance on validating resources against UZ Core using the command-line validator and validator.fhir.org.
Updated API access guidance: only ICD-10 and HL7 code systems currently validate on the playground, PKCE is mandatory for frontend clients, and the authentication details now link to the external SSO documentation.
Renamed the Services page to Components and expanded it with component descriptions and Russian/Uzbek translations.
Added UZ Core AllergyIntolerance profile with supporting CodeSystems and ValueSets (AllergenCodesVS, ReactionSubstanceVS, ReactionManifestationVS, AllergyCategoryVS, AllergyTypeVS, AllergyClinicalStatusVS, AllergyVerificationStatusVS, AllergyReactionSeverityVS) along with ConceptMaps for translating local allergen and manifestation codes to SNOMED CT.
Added laboratory observation codes for panels and analytes used in Uzbekistan.
UZCoreClinicalCondition has been removed and merged into UZ Core Condition. Implementers must update references from uz-core-clinical-condition to uz-core-condition. A new ConditionCodeVS ValueSet combining ICD-10 and SNOMED CT (preferred binding) is now used for Condition.code.
In the Patient Satisfaction Questionnaire, answerOption codes have been moved out of the Questionnaire's own URL into a dedicated PatientSatisfactionCS code system. Implementers populating QuestionnaireResponse answers for this questionnaire must update the Coding system from https://dhp.uz/fhir/core/Questionnaire/PatientSatisfactionQuestionnaire to https://terminology.dhp.uz/fhir/core/CodeSystem/patient-satisfaction-cs. Codes themselves are unchanged.
In UZ Core Observation, ObservationCodesVS has been changed from required to preferred binding and now includes SNOMED CT codes in addition to LOINC and local codes. Implementers may use SNOMED CT codes where appropriate.
In UZ Core HealthcareService, category.coding and type.coding are now sliced to support a new labCategory slice bound to LabServiceCategoriesVS (codes from LabCategoriesCS). Laboratory healthcare services should populate the labCategory slice in addition to the existing dhpCategory.
In UZ Core Patient, MahallaVS (used for address.city) has been expanded to include codes from the new Mahalla COATO code system, providing 2,600+ COATO-based mahalla identifiers in addition to the existing MahallaCS codes.
In UZ Core Socioeconomic Observation, the BenefitCS code system has been expanded with new codes (e.g., #regis0004.00020, #regis0004.00021, #regis0004.00022, #regis0004.00023).
In UZ Core Socioeconomic Observation, new codes have been added to the EducationCS code system (e.g., #regis0005.00011 "No education", #regis0005.00012 "Specialty").
In UZ Core Socioeconomic Observation, the SocialStatusCS code system has been expanded (e.g., #regis0010.00010 "School student", #regis0010.00011 "Eligible for benefits").
A new term has been added to DisabilityCS:
#regis0011.00005 "Disability not established"For UZ Core Encounter, a new AdmitSourceLocalCS code system has been created with the following codes:
#mserv-0006-00001 "Without referral / Self-referred"#mserv-0006-00002 "Dispensary"#mserv-0006-00003 "District psychiatry service"#mserv-0006-00004 "Emergency medical service"#mserv-0006-00005 "By court decision"#mserv-0006-00006 "For examination"Additionally, a new AdmissionOriginVS ValueSet has been created which includes codes from AdmitSourceHomeCS.
For UZ Core Encounter, EncounterPriorityCS has been expanded with missing codes based on HL7 v3-ActPriority (e.g., #A, #CR, #EL, #R, #RR, #S, #T, #UD, #UR), and a new EncounterPriorityLocalCS code system has been created with local priority codes (e.g., #transferred, #mandatory-treatment, #involuntary-hospitalization).
For UZ Core Encounter, a new ReAdmissionLocalCS code system has been created for readmission cases (e.g., #first-time, #repeat-current-year).
For UZ Core Encounter, EncounterDischargeDispositionHomeCS has been expanded with new codes:
#mserv-0004-00004 "Discharged"#mserv-0004-00002 "Died"#mserv-0004-00005 "Transferred to Ministry of Internal Affairs facility"#mserv-0004-00006 "Moved to a charity home (residential care facility)"For UZ Core Encounter, a new EncounterLocalSubjectStatusCS code system has been created to represent patient status:
#loc-cs-001 "Recovered"#loc-cs-002 "Improved"#loc-cs-003 "Unchanged"#loc-cs-004 "Worsened"Although there is no dedicated profile for Coverage in UZ Core, a new CoverageTypeCS code system has been created due to requirements from SSV forms.
It includes funding types through DTSJ and social funds (e.g., #dtsj-treated-case, #dtsj-privileged-category, #saxovat-komak-fund, #womens-notebook-fund, #youth-notebook-fund).
Added document identifier namespace (doc) to identifier systems.
type.coding[organizationType] in UZ Core Organization now uses OrganizationTypeUZCS instead of the HL7 organization-type CodeSystem. For example, $organization-type-cs#prov must be replaced with a code from organization-types-uz-cs (e.g. #I "Distribution by management"). There is no 1:1 mapping - each organization must be classified into the new system (codes I-V).
Added type.coding[organizationGrouping] slice to UZ Core Organization using OrganizationGroupingCS for detailed facility grouping (e.g. #104 "Specialized hospitals", #210 "Family polyclinic"). Implementers should populate this new slice.
type.coding[organizationalServiceGroup] and type.coding[specialization] cardinality in UZ Core Organization widened from 0..1 to 0..*. Implementers can now send multiple service group and specialization codes per organization.
Added code I_6 "Organizations with foreign investors participation" to OrganizationalSubordinationGroupCS. Implementers should use this code in type.coding[subordinationGroup] for applicable organizations.
OrganizationalStructureCS expanded with new codes for outpatient facilities (e.g. #200 polyclinics), educational institutions (#300), blood transfusion centers (#400), sanepid services (#500), and others. Some existing translations corrected (e.g. #116 fixed from "Medical center center" to "Medical center"). Implementers should review if a more specific code now exists for their facilities.
Added coverage area extension to UZ Core Organization for specifying the administrative territory an organization serves, bound to StateVS. SSV territory codes can be mapped to StateCS using SSVAdministrativeTerritoryToRegionsCM.
Added example demonstrating how to translate a MIS2 JSON organization into a UZ Core Organization resource using the ConceptMaps.
Added ConceptMaps for translating MIS2 codes to UZ Core terminology: SSVMedicalTypeToOrganizationalStructureCM for type.coding[organizationalStructure], SSVLevelTypeToSubordinationGroupCM for type.coding[subordinationGroup], and SSVServiceTypeToOrganizationalServiceGroupCM for type.coding[organizationalServiceGroup]. Implementers translating from MIS2 should use these maps to populate the corresponding slices.
In UZ Core Patient, the identifiers documentation has been updated to clarify that the national identifier is the PINFL (Personal Identification Number of an Individual), and to clarify the difference between medicalRecordTemp and unknownPatient identifier usage.
Added an example of a transaction bundle and an example of a PractitionerRole with freetext qualifications for implementers needing reference patterns.
Added UZ Core Goal profile with associated codesystems and valuesets.
Added UZ Core Questionnaire and QuestionnaireResponse profiles with multilingual support for translated answer options.
Added pension certificate identifier type (Номер пенсионного удостоверения) with NamingSystem support in Patient resource.
Clarified binding strength requirements in modelling guidelines.
Applied feedback from DHP Connectathon 1.
Fixed profile references to use UZ Core profiles where possible instead of base FHIR resources.
Patient citizenship now uses ISO 3166-1 alpha-2 codes instead of custom MVD codes.
Fixed OrganizationalSpecialization code consistency (101 → 101.0).
Fixed Russian translation for I_3 in OrganizationalSubordinationGroup.
Clarified descriptions for NomenclatureGroup, OrganizationalStructure, and OrganizationalServiceGroup to explain their purpose and hierarchy.
Added managing organization attachment extension to track when a patient was attached to a managing organization.
Added ConceptMap for translating MVD country codes to ISO 3166-1 alpha-2 codes.
Added explicit slices for foreign patient passport numbers and drivers licenses with country code support.
Updated EpisodeOfCare description.
Improved identifier documentation including PINFL clarity and migration to alpha-2 country codes.
Added vital signs section with guidance and examples.
Added Karakalpak language (kaa) support in the MultilingualName ruleset, used for multilingual names in Organization and Location profiles.
Updated IP holder to Ministry of Health.
UZ Core Clinical Condition added to differentiate clinical (ICD-10) and non-ICD-10 based conditions.
Patient disability status has been moved from the Patient resource (using a FHIR-standard extension) to the Condition resource.
Underscores have been removed from NamingSystem identifiers.
Added a CapabilityStatement describing DHP's supported resources, profiles, operations and searchparameters.
Added IP statements, globals table, and a dependency table to the IG.
Canonical URLs of NamingSystems now start with https://terminology.dhp.uz.
Name of the Observation Interpretation codesystem supplement has been fixed.
Added multilingual terminology strategy with Uzbek-authored CodeSystems and THO supplements for UI localization.
Documented use of ConceptMaps and their associated strategy.
Updated slice names to follow best practice naming convention of lower camelCase.
Added support for international addresses in Patient, Practitioner, and RelatedPerson resources.
Added Uzbek translations.
UZ Core profiles for Encounter, EpisodeOfCare, and Observation have been added.
Canonical URLs have been changed to https://dhp.uz/fhir/core for conformance resources and https://terminology.dhp.uz/fhir/core for terminology resources to accommodate future IGs, which will follow a pattern of https://dhp.uz/fhir/<ig>.
Russian translations have been added.
This is a first, in-development release of the IG that updates the canonical URLs of all resources to their final version.
UZ Core profiles for AuditEvent, Consent, Condition, HealthcareService, Location, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson, Provenance and the Socioeconomic Observation have been added.
Canonical URLs of profiles, terminology resources, and the IG have been changed from the temporary medcore.uz domain to the official dhp.uz domain.