🏥 | Implementation guide for Digital Health Platform [maintainer=@roosyabuddy] https://dhp.uz/fhir/core/en/index.html
  • GLSL 99.6%
  • Batchfile 0.3%
  • Shell 0.1%
Find a file
2026-03-30 14:52:35 +02:00
.github Reduce max allowed errors to 2 (#115) 2026-03-30 14:52:35 +02:00
.vscode Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00
docs Add 0.4.0 to package feed 2026-02-03 13:11:43 +01:00
input Update ignore for new conceptmaps SSV (#113) 2026-03-26 16:43:00 +01:00
.gitignore Sync 9238c13fe6 (#10) 2025-10-15 10:34:37 +02:00
_build.bat Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00
_build.sh Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00
_gencontinuous.bat Add sources 2025-07-02 13:07:11 +05:00
_gencontinuous.sh Add sources 2025-07-02 13:07:11 +05:00
_genonce.bat Add sources 2025-07-02 13:07:11 +05:00
_genonce.sh Add sources 2025-07-02 13:07:11 +05:00
_updatePublisher.bat Add sources 2025-07-02 13:07:11 +05:00
_updatePublisher.sh Add sources 2025-07-02 13:07:11 +05:00
AGENT.md Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00
ig.ini Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00
LICENSE chore: normal readme following @uzinfocom-org's style 2025-07-07 21:49:32 +05:00
modelling-guidelines.md Add clarification that national identifier is the PINFL (#96) 2026-03-11 12:21:27 +01:00
README.md Change medcore.uz to dhp.uz in docs (#83) 2026-02-04 12:56:28 +01:00
Requirements-fromNarrative.json Uz core organization updated for MIS2 compatibility (#100) 2026-03-24 10:45:42 +01:00
sushi-config.yaml Prepare release 0.4.0 (#68) 2026-01-13 08:35:54 +01:00
update-translations.sh Remove old NamingSystem translations, update configs (#59) 2025-12-19 14:35:34 +01:00
updateSiteBasedOnMarkdownChange.ps1 Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00
updateSiteBasedOnMarkdownChange.sh Merge latest DHP-temp (#6) 2025-10-09 09:35:15 +02:00

🇺🇿 DHP Implementation Guide for Uzbekistan

Welcome to the official repository of the Digital Health Platform (DHP) Implementation Guide of the Republic of Uzbekistan. This guide defines the interoperability standards, FHIR profiles, terminology bindings, and business processes that enable secure, patient-centric digital healthcare services nationwide.

📌 Published by Uzinfocom in collaboration with the Ministry of Health of Uzbekistan under the national healthcare digitalization program supported by KfW Development Bank.


🌐 About the Project

The DHP is a unified digital infrastructure supporting Electronic Health Records (EHR), telemedicine, public health reporting, and integrated care across Uzbekistan.

  • 📅 Project duration: 20242027
  • 🧭 Aligned with: Digital Uzbekistan 2030, Presidential Decree PD-415, Concept for Health 20192025
  • 🔗 Interoperability standard: HL7® FHIR® R5

📘 Guide Contents

This Implementation Guide includes:

  • FHIR profiles for patient management, prescriptions, referrals, diagnostics, immunizations, etc.
  • 🏥 Business use cases (e.g., EHR exchange, appointment booking, public health reporting)
  • 🔐 Security and access control models (RBAC, consent, audit, OAuth2)
  • 🌍 Terminology services: ICD-11, SNOMED CT, LOINC, ATC, UCUM
  • 🧪 Validation and examples for all use cases


👥 Contributors

Name Role Organization
Rustam Sadykov IG Maintainer Uzinfocom
Vadim Peretokin Primary Author Peretokin Consulting
Bekhzod Akhmedov Co-Author Uzinfocom
Sarvar Kubaev Co-Author Uzinfocom
Saodat Kadirova Business Analyst Uzinfocom
Irina Berger Business Analyst Uzinfocom
Ministry of Health of the Republic of Uzbekistan Strategic Partner Government
KfW Development Bank Financial & Technical Support International Donor

🛠️ Repository Management and Development Standards

Semantic versioning: Version identification follows the conventions documented at https://build.fhir.org/ig/vadi2/DHP-temp/en/index.html#identification-of-versions.

Branching strategy: Feature branches are created as needed and merged into the main branch via rebase or squash-commit. All releases are tagged from the main branch according to semantic versioning standards.

Code review policy: Pull requests must pass IG Publisher QA checks without introducing new errors or warnings, and require approval from at least one FHIR expert before merging.

Quality assurance: Static analysis is enforced through the FHIR IG Publisher's built-in validation and QA tooling, which checks for conformance issues, broken references, terminology validation errors, and a host of other issues.


📚 Documentation

Modelling Guidelines


📜 License

This Implementation Guide is open-source under the CC BY-SA 4.0 license.