Uzbekistan Digital Health Platform
0.10.0 - draft
Uzbekistan Digital Health Platform
0.10.0 - draft
This page is part of the Uzbekistan Digital Health Platform (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
(No changes yet)
Added ICHI in full - the WHO International Classification of Health Interventions, 21,747 concepts from the 2026-09-17 tabulation - under its own WHO canonical http://id.who.int/icd/release/11/ichi, with an ICHI Codes value set.
677 of those concepts are marked inactive with status of retired. They are codes DMED still carries that WHO has withdrawn, kept so records already in DMED stay valid; ichi-vs leaves them out: they should not be used for new records.
UZ Core PlanDefinition now states where a schedule applies, through a jurisdiction use context slice bound (required) to a new Uzbekistan Jurisdictions value set. A national schedule carries one entry with the country code UZ; a regional one carries an entry per region, using the same region codes as Address.state, so a patient's region can be matched against the schedules that apply to them.
At the Ministry of Health's request, the immunization status reason value set has grown from 4 to 8 codes, adding PHILISOP (philosophical objection), RELIG (religious objection), VACEFF (vaccine efficacy concerns) and VACSAF (vaccine safety concerns), so a vaccination that did not happen can say why beyond a patient objection. Their Uzbek and Russian designations are in the act reason supplement.
Added organizational-specialization-cs#176.0 for adult geriatrics, coverage-type-cs#covtp-0001-00014 for the Vaqf charitable fund, admit-source-local-cs#mserv-0006-00007 for a polyclinic referral, and benefits-cs#regis0004.00024 for people with haematological diseases, an entitlement to state-funded high-tech specialized care under Presidential Decree UP-88 - gaps found auditing Form 066 against the live DMED system. The encounter priority value set now also includes UR (urgent) and EL (elective), and the Provenance Participation Role Type value set includes attester.
Procedure Codes now includes ICHI alongside SNOMED CT, because DMED codes an operation in ICHI only, so Procedure.code can carry the statistical code a procedure is reported under as well as its clinical meaning - both as two codings on the same element where a procedure is recorded and reported. The binding is now extensible rather than required, so a guide can narrow Procedure.code to a national subset that includes codes WHO has withdrawn.
The ICHI canonical drops beta: the ICHI NamingSystem moved from http://id.who.int/icd/release/11/beta/ichi to http://id.who.int/icd/release/11/ichi. The NamingSystem published the beta URI in 0.9.0 and 0.9.2, so anything that took the ICHI system URI from there has to move.
The example SNOMED CT to ICHI ConceptMap, published since 0.9.0, has been removed. WHO licenses ICHI under CC BY-ND 3.0 IGO, which makes a map or crosswalk between ICHI and another terminology subject to a separate written agreement with WHO; the guide cannot publish one until that agreement is in place.
target on UZ Core Provenance now also accepts Bundle, since signing a whole FHIR document (as Form 066 does) previously had no valid target type.
UZ Core PlanDefinition has a National or regional section showing both shapes of the jurisdiction use context.
UZ Core Procedure now names both code systems its code accepts, and says to carry SNOMED CT and ICHI as two codings where a procedure is reported as well as recorded.
The package is now built as a publication build. Since 0.2.0 its package.json carried notForPublication and a file:// url, so packages2.fhir.org rejected every version from 0.6.0 on, and guides depending on UZ Core linked to its artifacts through file:// paths. The package now declares https://dhp.uz/fhir/core. Content is unchanged from 0.9.1.
ICD-O-3.2 declared its version as 3.2; it now declares 3.2.0, which is the release identifier validators expect. Codings that pin the version have to move from http://terminology.hl7.org/CodeSystem/icd-o-3|3.2 to |3.2.0.
Added UZ Core MedicationRequest for ordering medications, with a trustee extension naming the relative (RelatedPerson) or patronage nurse (PractitionerRole) authorized to collect the medication on the patient's behalf. It comes with status, status reason, intent and category value sets - the category adding a national reimbursement order code - and days of the week, event timing and timing abbreviation value sets for dosage timing, all with Uzbek and Russian designations.
Added ICD-O-3.2 in full - 330 topography and 1143 morphology codes, with Uzbek and Russian designations - under its HL7 Terminology canonical http://terminology.hl7.org/CodeSystem/icd-o-3, with topography and morphology value sets.
Added a unit of measurement CodeSystem with 181 local unit codes named in Uzbek, Russian and English, its value set, and a ConceptMap mapping 65 of them to UCUM.
entity.detail on UZ Core AuditEvent is now Must Support, with detail.type bound (example) to 13 new audit event detail type codes covering authentication, the client, searches, resource versions and synchronisation.
The encounter type CodeSystem has grown from 7 to 8 codes, adding mserv-0001-00008 for a screening encounter, available through the nationalType slice of type on UZ Core Encounter.
The ICCC-3 CodeSystem has moved from https://terminology.dhp.uz/fhir/core/CodeSystem/iccc-3-cs to its HL7 Terminology canonical http://terminology.hl7.org/CodeSystem/iccc-3, since the classification is IARC's rather than DHP's. The value set keeps its URL.
The passportLocal and passportInternational identifier slices on UZ Core RelatedPerson are now 0..* rather than 0..1, matching UZ Core Patient.
authorizingPrescription on UZ Core MedicationDispense now references UZ Core MedicationRequest rather than any MedicationRequest.
The relationship type value set on UZ Core RelatedPerson now includes FTH (father) and GUARD (guardian), with their Uzbek and Russian designations added to RoleCodeCS.
The route of administration value set now includes 8 local route codes for routes SNOMED CT does not cover, such as implantation, iontophoresis and skin scarification. It is bound (extensible) to dosageInstruction.route on UZ Core MedicationRequest and (example) to route on UZ Core Immunization.
The DMED position SNOMED supplement now carries Uzbek designations alongside the Russian ones, replacing the English designations it had in 0.8.0.
The DHP CapabilityStatement now declares the platform operations - Person/$populate, Patient/$populate, Organization/$practitioners, Practitioner/$organizations and Practitioner/$specializations - each linked to its OperationDefinition. It also lists Bundle and Flag, and now has a canonical URL, name, title and version.
prescription on UZ Core Claim now references UZ Core MedicationRequest rather than any MedicationRequest, as announced in 0.8.0.
UZ Core VaccinationActivityDefinition has been renamed to UZ Core ActivityDefinition, as it is no longer limited to vaccination. This is a breaking change: the canonical URL moves from https://dhp.uz/fhir/core/StructureDefinition/uz-core-vaccination-activity-definition to https://dhp.uz/fhir/core/StructureDefinition/uz-core-activitydefinition, and instances must update meta.profile.
code is no longer fixed to 33879002 (active immunization) but bound (extensible) to procedure codes. The vaccine code binding on product[x] is now extensible, with an additional required binding when code is 33879002, so a vaccination still names a vaccine from that value set.
The CVD risk screening questionnaire has been removed, along with the CvdRiskCategoryCS and CvdTobaccoUseCS code systems. The questionnaire and risk categories now live in the integration IG as https://dhp.uz/fhir/integrations/Questionnaire/CVDRiskScreeningQuestionnaire and https://terminology.dhp.uz/fhir/integrations/CodeSystem/cvd-risk-category-cs, which codes tobacco use in SNOMED CT instead, so references to the old core canonicals must switch.
The DMED role class supplement https://terminology.dhp.uz/fhir/core/CodeSystem/dmed-role-class-cs, added in 0.8.0, has been removed, so PAT in the position and profession value set no longer has Uzbek and Russian designations.
The Components page now describes Blood Management, Nursing and Supplies. The Referrals section now covers the seven axes a referral is classified along, and how the referral ServiceRequest relates to the Tasks that drive its state-insurance approval.
Components with a workflow page now link to it, and each workflow page links back. The Prescription section points at the e-Prescription and dispensing workflow until its Technical Project is written.
The Components page now ends with an interactive cross-component resource architecture diagram showing the FHIR resources each of eleven components works with and which flow into another component. It marks which resources this IG defines and, with a ★, which ones a component is responsible for. Hovering over or tabbing to a resource shows the platform service that holds it, and clicking a component card opens its resource list.
The e-Referral lifecycle no longer calls the ServiceRequest and Task profiles unpublished. Both are now published, as UZ Core ServiceRequest and UZ Core Task Referral Approval, and are still experimental.
The Laboratory order to result workflow's links and worked example now point at UZ Core ServiceRequest instead of uz-core-servicerequest-laboratory, renamed in 0.8.0.
UZ Core RelatedPerson now shows how to link a parent to their child so a system can let the parent act for them, with a new example-mother-of-a-child example. The profile page explains matching children by PINFL, reading the child's age from Patient.birthDate, and why the relationship alone does not grant access.
Added UZ Core Composition profile as the foundation for medical documents and digital forms, with terminology for the document type (470 national document, journal and form codes), category, status, attestation mode, and, on each section, the narrative status, ordering and reason a section is empty.
The operations the platform exposes are now published as OperationDefinitions, so implementers can see their parameters, error behaviour and idempotency without reading the platform documentation. Person/$populate and Patient/$populate create a Person or Patient from an identity document - PINFL (NI), passport or ID card (PPN), or birth certificate (BCT) - populating it from the state registries, and return the existing resource rather than a duplicate when one already exists for that PINFL. Organization/$practitioners, Practitioner/$organizations and Practitioner/$specializations resolve the links between practitioners and the organizations they work at.
A status history extension has been added to UZ Core PlanDefinition, recording each status the definition has held with the period it applied, the reason it changed and who changed it.
characteristic on UZ Core HealthcareService is now sliced with a paymentType slice bound (required) to payment type, so a service can state the funding arrangements it is offered under. The labCategory slice on category.coding is now bound to service categories rather than to the laboratory-specific value set that has been renamed (see below).
Added the International Classification of Childhood Cancer, 3rd edition with its 140 diagnostic groups, subgroups and divisions, and the value set selecting them, for classifying childhood cancers by morphology in registry reporting. It is intended for use in the integration IG.
The diagnosis type CodeSystem has grown from 12 to 22 codes, with cancer-0003-0001 to cancer-0003-0010 naming the document a cancer registration was established from - a medical record or an extract from one, a record or notification from an oncology, haematology or other medical institution, a death certificate, or the civil registry office. They flow into the diagnosis type value set, bound (required) to the diagnosis type extension on UZ Core Condition.
The discharge disposition CodeSystem has grown from 6 to 9 codes, with cancer-0001-0001 to cancer-0001-0003 recording how cancer registry follow-up ended - the patient is alive, the diagnosis was not confirmed, or the patient was taken off the register once the follow-up period ran out. They flow into the discharge disposition value set, which is bound (required) to admission.dischargeDisposition on UZ Core Encounter.
Added an observation day CodeSystem with local codes for the day of life on which a newborn observation was recorded, to discriminate the nested Composition sections of Form 097.
The passportLocal and passportInternational identifier slices on UZ Core Patient are now 0..* rather than 0..1, so a patient may carry more than one of each - for example a current ID card alongside a superseded paper passport, as described on the identifiers page.
prescription on UZ Core Claim is now Must Support, for the reimbursement prescription the claim is made against. It references MedicationRequest and will be narrowed to UZ Core MedicationRequest once that profile is published.
The title and description of UZ Core ClaimResponse no longer split the resource name - "UZ Core Claim Response" is now "UZ Core ClaimResponse". Its canonical URL is unchanged.
The position and profession value set, bound (required) to code on UZ Core PractitionerRole, now also admits the v3 RoleClass code system in full, four v3 RoleCode codes (TPA, PAYOR, ORG and VALIDATOR) and ten named SNOMED CT concepts, so that every target of DMEDPositionToDHPPositionCM is valid against the binding. Uzbek and Russian designations for them are carried by the new DMED position SNOMED supplement and DMED role class supplement. DMEDRoleCS grew from 5 to 43 codes and RoleCodeCS from 2 to 6 as a result.
The display of paytype-0001-0004 in the payment type CodeSystem has changed from "Davlat tomonidan moliyalashtiriladigan" ("State-funded") to "Davlat tarifi" ("State tariff"). The code is unchanged, so systems storing it should check that their own label still matches. A fifth code paytype-0001-0005 ("Boshqalar", "Other") has been added for payment arrangements that the other four do not describe.
The routine and order designations in the request priority and request intent supplements have been shortened to a single term each - "Обычный" rather than "Обычный (плановый)", "Назначение" rather than "Назначение / Приказ" - and urgent, asap and stat gained Uzbek and Russian designations.
UZ Core ServiceRequest Laboratory has been renamed to UZ Core ServiceRequest and generalised from laboratory orders to any requested service - procedures, diagnostic investigations, consultations, screening and admissions. This is a breaking change: the canonical URL moves from https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest-laboratory to https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest, and instances must update meta.profile. priority is now Must Support and bound (required) to request priority. The category and code bindings have changed with it - see below.
LabServiceCategoriesVS has been renamed to ServiceRequestCategoriesVS and widened to cover service requests of any kind, adding SNOMED CT categories for imaging, diagnostic, surgical, physiotherapy, therapeutic and outpatient procedures, consultation, admission, rehabilitation, telemedicine, screening and donation, with a supplement carrying their Uzbek and Russian designations. This is a breaking change: the canonical URL moves from https://dhp.uz/fhir/core/ValueSet/lab-service-categories-vs to https://terminology.dhp.uz/fhir/core/ValueSet/service-request-categories-vs.
ServiceRequestLabCodesVS has been replaced by ServiceRequestCodesVS, which adds the new screening and home visit codes - 20 codes for screening questionnaires and programmes, among them cardiovascular risk, diabetes, breast cancer and cervical cancer, and for patronage (home visit) services - to the LOINC order codes, national laboratory panel codes and SNOMED CT procedures it already carried. This is a breaking change: the canonical URL moves from https://terminology.dhp.uz/fhir/core/ValueSet/service-request-labresearch-code-vs to https://terminology.dhp.uz/fhir/core/ValueSet/service-request-code-vs.
UZ Core Immunization PlanDefinition has been renamed to UZ Core PlanDefinition, because it now covers whole blood donation and screening schedules alongside immunization ones. This is a breaking change: the canonical URL moves from https://dhp.uz/fhir/core/StructureDefinition/uz-core-immunization-plan-definition to https://dhp.uz/fhir/core/StructureDefinition/uz-core-plan-definition, and instances must update meta.profile.
The profile now carries a focus use context naming the kind of schedule - 33879002 (active immunization), 25179006 (whole blood unit collection) or 360156006 (screening intent) - and a constraint requires exactly one of them, so a schedule of a given kind is found with GET [base]/PlanDefinition?context-type-value=focus$http://snomed.info/sct|33879002. The immunization schedule type binding on the schedule category context is now required rather than extensible, so that the slicing can be validated.
code on UZ Core PractitionerRole is now mandatory (1..1).
The national identifier slice on UZ Core Practitioner now fixes system to the PINFL system https://dhp.uz/fhir/core/sid/pid/uz/ni, instead of https://dhp.uz/fhir/core/sid/pro/uz/argos. This matches the NI identifier type the slice already carried, and the system used for the same identifier on UZ Core Patient and UZ Core RelatedPerson.
All 13 codes in the coverage type CodeSystem have been renumbered from mnemonic codes to the covtp-0001-000NN pattern used by the other national code systems: dtsj-treated-case is now covtp-0001-00001, moh-budget is covtp-0001-00008, self-pay is covtp-0001-00009, and so on in the order the codes are listed. Displays and meanings are unchanged. This is a breaking change: coverage type codes stored under the previous version must be re-mapped.
The DMEDPositionToSnomedCM ConceptMap has been removed. Its mappings are now groups inside DMEDPositionToDHPPositionCM, which maps DMED role and profession codes to national positions, SNOMED CT, v3 RoleCode and v3 RoleClass in a single map. Implementers referencing https://terminology.dhp.uz/fhir/core/ConceptMap/dmed-position-to-snomed-cm must use https://terminology.dhp.uz/fhir/core/ConceptMap/dmed-position-to-dhp-position-cm instead.
The Forms page is now called Questionnaires, so that it is not read as the medical forms used in Uzbekistan. The page address is unchanged.
The how to read this guide page now says what to do when no code in a bound value set fits the data, for each binding strength, with worked JSON showing an extensible binding satisfied from the national list and then from SNOMED CT with the original wording kept in text.
Added UZ Core Claim and UZ Core ClaimResponse 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.
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.
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.
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.
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.
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.
participant.actor on UZ Core Condition may now reference UZ Core Organization.
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.
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.
UZ Core 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.
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.
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 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.
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.
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.
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.
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.
Corrected English display names in OrganizationalSpecializationCS (consistent casing; "Children" changed to "Pediatric"). Codes are unchanged.
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.
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.
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.
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.
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.
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 PlanDefinition and UZ Core Questionnaire. name is now required on UZ Core Organization and UZ Core Location.
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.
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.
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.
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 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.
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.
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.
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).
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.