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.4.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
Bosh sahifa
Ushbu sahifa qo‘llanma yozilgan asl manba tilidan tarjimalarni o‘z ichigaoladi. Ushbu tarjimalar haqidagi ma’lumot va ularga fikr bildirish bo‘yichako‘rsatmalarni bu yerda topishingiz mumkin.
Ushbu FHIR R5 implementatsiya qo'llanmasi (IG) ishlab chiqish jarayonida bo'lib, hali ishlab chiqarish muhitida foydalanish uchun tayyor emas. U faqatgina Digital Health Platform (DHP) doirasida sinov va fikr-mulohazalarni yig'ish maqsadida mo'ljallangan. IG mazmuni ishlab chiqish davomida o'zgarishi mumkin.
Hozirgi ustuvor yo'nalish — DHP'da implementatsiyani ta'minlash uchun asosiy resurs profillarini yakunlash. Keyinchalik, modellashtirish imkoniyatlari kengaytirilgach, IG'ning qolgan matn qismi to'liq ishlab chiqiladi.
Kirish qismi
Ushbu qo'llanma O'zbekiston Raqamli Sog'liqni Saqlash Platformasi doirasida FHIR'ni implementatsiya qilish uchun rasmiy hujjat bo'lib, mamlakat sog'liqni saqlash tizimining real sharoitlari, ehtiyojlari va xususiyatlariga moslashtirilgan.
Qo'llanma quyidagi yo'nalishlar uchun asos bo'lib xizmat qiladi:
- O'zbekiston sharoitlariga moslashtirilgan UZ Core profillarini ishlab chiqish, bu FHIR resurslarini mahalliy ehtiyojlarga moslashtirish va respublika bo'yicha yagona raqamli sog'liqni saqlash infratuzilmasini yaratish uchun zarur asosni ta'minlaydi;
- bu moslashtirishlar umumiy identifikatorlarni modellashtirish, HL7 kod tizimlarining tarjimalari va barcha tizimlar tomonidan qo'llab-quvvatlanishi shart bo'lgan elementlarni belgilashni o'z ichiga oladi
- Ma'lum klinik yoki ma'muriy stsenariylarni qo'llab-quvvatlovchi maxsus profillarni ishlab chiqish;
- masalan, tug'ilish va o'limni ro'yxatga olish tizimlari;
- Xalqaro va milliy tasnif hamda terminologiyalardan foydalanish — SNOMED CT, LOINC, ICD-10, ICD-11, CBPEPW-2020 va boshqalar.
Ushbu Implementatsiya qo'llanmasidan foydalanish tibbiy ma'lumotlarni ifodalashda izchillikni ta'minlaydi, tizimlararo interoperabellikni oshiradi hamda kengaytiriladigan raqamli sog'liqni saqlash ekotizimini yaratish uchun mustahkam asos yaratadi.
Loyiha tarixi
Raqamli sog'liqni saqlash platformasi (DHP) "Sog'liqni saqlash tizimini raqamlashtirish islohotini qo'llab-quvvatlash" loyihasi doirasida ishlab chiqilmoqda. Loyiha O'zbekiston Respublikasi va KfW Taraqqiyot banki o'rtasidagi bitim asosida amalga oshirilmoqda. Ushbu tashabbus O'zbekiston Respublikasi Prezidentining 2023-yil 1-maydagi PQ-140-son qarori ("Sog'liqni saqlash tizimini raqamlashtirish bo'yicha qo'shimcha chora-tadbirlar to'g'risida") va 2023-yil 28-dekabrdagi PQ-415-son qarori ("Sog'liqni saqlash tizimini raqamlashtirishni jadallashtirish va ilg'or raqamli texnologiyalarni joriy etish bo'yicha qo'shimcha chora-tadbirlar to'g'risida") bilan uyg'unlashgan.
Qamrov sohalari
O'zbekiston Respublikasi Raqamli Sog'liqni Saqlash Platformasi quyidagi 19 ta xizmat asosida tashkil etilgan:
- Metama'lumotlar va xavfsizlikni boshqarish (MSM)
- Asosiy ma'lumotlarni boshqarish (MDM)
- Bemorni davolash jarayonini boshqarish
- Elektron tibbiy yozuvlar
- Yo'llanmalar
- Retseptlar
- Qabul va rejalashtirish
- Laboratoriya
- Diagnostika va nurli vizualizatsiya
- Tez tibbiy yordam
- Tibbiy ta'minot
- Xarajatlarni qoplash
- Klinik qarorlarni qo'llab-quvvatlash
- Hamshiralik ishi
- Qon resurslarini boshqarish
- Emlashni boshqarish
- Jamoat salomatligi bo'yicha hisobotlar
- Skrining jadvalini boshqarish
- Sifatni ta'minlash
Versiyalarni aniqlash
Ushbu Implementatsiya qo'llanmasida keltirilgan artefaktlar — profillar, kengaytmalar, kod tizimlari (CodeSystem), qiymatlar to'plamlari (ValueSet), nomlash tizimlari (NamingSystem) va FHIR paketlari — IG versiyasi bilan bir xil versiya raqamiga ega bo'ladi. IG versiyalash Semantic Versioning (SemVer) tamoyillariga asoslanadi va MAJOR.MINOR.PATCHformatida ifodalanadi. Masalan, agar IG versiyasi 2.0.0 bo'lsa, barcha artefaktlar ham 2.0.0 versiyasiga ega bo'ladi. Bu artefaktning qaysi IG versiyasiga tegishli ekanligini oson aniqlash imkonini beradi.
Artefakt ishlab chiqish jarayonida bo'lib, ishlab chiqarish uchun tayyor bo'lmaguncha, draftmaqomiga ega bo'ladi. Ishlab chiqarishga tayyor bo'lganda esa active holatiga o'tkaziladi. Agar artefakt bekor qilingan bo'lsa, uning holati retired bo'ladi.
Haqiqiy muhitda artefaktlarni sinovdan o'tkazish uchun yetuklik (maturity) modeli kelajakda joriy etiladi, hozircha barcha artefaktlar draft maqomida hisoblanadi.
Versiyalashdan yagona istisno THO kod tizimlarining tarjima qo'shimchalari (supplement) bo'lib, ular asl tizim versiyasiga mos keladi. Masalan, agar THO kod tizimi versiyasi 2.1.0 bo'lsa, qo'shimcha ham 2.1.0 versiyasiga ega bo'ladi. Agar THO tizimi 2.2.0 versiyasiga yangilansa, qo'shimcha ham shunga mos ravishda yangilanadi. Agar qo'shimchani yangilash zarur bo'lib, lekin THO tizimining o'zi o'zgarmagan bo'lsa, versiyaga qo'shimcha raqam qo'shiladi — masalan, 2.2.0.1.
IG'ning ishlab chiqish versiyasi: 0.x.x
- IG holati:
draft
- Artefaktlar holati:
draft with experimental flag set to true
- Dastlabki ishlab chiqish va testlash bosqichlarida qo'llaniladi
- Kichik versiyalar orasida o'zgarishlar bo'lishi mumkin
IG'ning ishlab chiqarish versiyalari: 1.x.x+
- IG holati:
active
- Artefaktlar holati:
active with experimental flag set to false
- Birinchi barqaror versiya: 1.0.0
- Qat'iy SemVer moslik qoidalariga amal qiladi
IG'ning keyingi yirik versiyalari: 2.x.x, 3.x.x va hokazo
- Ishlab chiqarish versiyalariga o'xshash
- IG'ning ba'zi qismlarida katta o'zgarishlar yoki arxitektura yangilanishlarini bildiradi
Intellektual mulk bayonotlari
This publication includes IP covered under the following statements.
- These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.
Show Usage
- This is an example set.
Show Usage
- This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
Show Usage
- LOINC: Bundle/example-transaction-bundle, Observation/blood-pressure-example... Show 10 more, Observation/bmi-example, Observation/body-height-example, Observation/body-temperature-example, Observation/body-weight-example, Observation/head-circumference-example, Observation/heart-rate-example, Observation/oxygen-saturation-example, Observation/respiratory-rate-example, ObservationCodesVS and UZCoreObservation
- This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
Show Usage
- SNOMED Clinical Terms® (SNOMED CT®): Condition/example-cancer, Condition/example-disability... Show 20 more, Condition/example-headache, Condition/example-pregnancy, ConditionCodeVS, ConditionSeverityVS, Goal/example-goal, GoalDescriptionVS, GoalStartEventVS, Observation/example-david-benefits, Observation/example-david-education, Observation/example-david-profession, Observation/example-david-social-status, Observation/example-salim-benefits, Observation/example-salim-education, Observation/example-salim-profession, Observation/example-salim-social-status, SocioeconomicObservationCodesVS, UZCoreCondition, UZCoreGoal, UZCoreObservation and UZCoreSocioeconomicObservation
- This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
Show Usage
- Admit source: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterAdmitSourceVS and UZCoreEncounter
- Admit source: EncounterAdmitSourceCS
- AllergyIntolerance Clinical Status Codes: AllergyClinicalStatusVS, AllergyIntolerance/example-grass-pollen-allergy and UZCoreAllergyIntolerance
- AllergyIntolerance Clinical Status Codes: AllergyClinicalStatusCS
- AllergyIntolerance Verification Status: AllergyIntolerance/example-grass-pollen-allergy, AllergyVerificationStatusVS and UZCoreAllergyIntolerance
- AllergyIntolerance Verification Status: AllergyVerificationStatusCS
- Condition Clinical Status Codes: ClinicalStatusVS, Condition/example-cancer... Show 4 more, Condition/example-disability, Condition/example-headache, Condition/example-pregnancy and UZCoreCondition
- Condition Clinical Status Codes: ClinicalStatusCS
- ConditionVerificationStatus: Condition/example-cancer, Condition/example-disability... Show 4 more, Condition/example-headache, Condition/example-pregnancy, ConditionVerificationStatusVS and UZCoreCondition
- ConditionVerificationStatus: ConditionVerificationStatusCS
- Consent Action Codes: Consent/example-consent, ConsentActionVS and UZCoreConsent
- Consent Action Codes: ConsentActionCS
- DataAbsentReason: DataAbsentReasonVS and UZCoreObservation
- DataAbsentReason: DataAbsentReasonCS
- Diagnosis Role: Bundle/example-transaction-bundle, EpisodeOfCare/UZCoreEpisodeOfCare-Example and EpisodeOfCare/UZCoreEpisodeOfCare-Example02
- Discharge disposition: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterDischargeDispositionVS and UZCoreEncounter
- Discharge disposition: EncounterDischargeDispositionCS
- Security Role Type: AuditEvent/example-auditevent-condition-lookup, AuditEvent/example-auditevent-login... Show 4 more, AuditParticipationRoleTypeVS, ConditionParticipationRoleTypeVS, UZCoreAuditEvent and UZCoreCondition
- Security Role Type: ExtraSecurityRoleTypeCS
- Goal achievement status: Goal/example-goal, GoalAchievementVS and UZCoreGoal
- Goal achievement status: GoalAchievementCS
- Goal category: Goal/example-goal, GoalCategoryVS and UZCoreGoal
- Goal category: GoalCategoryCS
- Goal priority: Goal/example-goal, GoalPriorityVS and UZCoreGoal
- Goal priority: GoalPriorityCS
- AuditEventEntityRole: AuditEvent/example-auditevent-condition-lookup, ObjectRoleVS and UZCoreAuditEvent
- Observation Category Codes: Bundle/example-transaction-bundle, Observation/blood-pressure-example... Show 11 more, Observation/bmi-example, Observation/body-height-example, Observation/body-temperature-example, Observation/body-weight-example, Observation/cbc-panel-example, Observation/head-circumference-example, Observation/heart-rate-example, Observation/oxygen-saturation-example, Observation/respiratory-rate-example, ObservationCategoryVS and UZCoreObservation
- Observation Category Codes: ObservationCategoryCS
- Participant type: EncounterParticipantTypeVS and UZCoreEncounter
- Participant type: ParticipantTypeCS
- Provenance participant type: Condition/example-cancer, Condition/example-disability... Show 7 more, Condition/example-headache, Condition/example-pregnancy, ConditionParticipationRoleTypeVS, Provenance/example-provenance, ProvenanceParticipationRoleTypeVS, UZCoreCondition and UZCoreProvenance
- Provenance participant type: ProvenanceParticipationRoleTypeCS
- Observation Reference Range Meaning Codes: ReferenceRangeMeaningVS and UZCoreObservation
- Observation Reference Range Meaning Codes: ReferenceRangeMeaningCS
- Audit Event Source Type: AuditEvent/example-auditevent-condition-lookup and AuditEvent/example-auditevent-login
- re-admissionIndicator: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterReAdmissionVS and UZCoreEncounter
- re-admissionIndicator: EncounterReAdmissionCS
- contactRole2: Patient/example-david, Patient/example-emma, Patient/example-salim, RelationshipTypeVS and UZCoreRelatedPerson
- contactRole2: ContactRole2CS
- identifierType: IdentifierDomainCS, IdentifierTypeVS... Show 33 more, Patient/example-david, Patient/example-emma, Patient/example-salim, Practitioner/example-practitioner, Practitioner/example-practitioner-gender-other, RelatedPerson/example-related-person, Respublika onkologiya markazi, Toshkent viloyati yuqumli kasalliklar shifoxonasi, UZCoreLocation, UZCoreOrganization, UZCorePatient, UZCorePractitioner, UZCorePractitionerRole, UZCoreRelatedPerson, UzDhpEpisodeOfCareIdentifier, UzDhpLocationUnitSystem, UzbekistanBirthCertificateSystem, UzbekistanDriversLicenseSystem, UzbekistanHealthCardNumberSystem, UzbekistanHrmArgosPractitionerSystem, UzbekistanHrmArgosSystem, UzbekistanMilitaryIdNumberSystem, UzbekistanNationalUniqueIdSystem, UzbekistanPassportDiplomaticSystem, UzbekistanPassportInternationalSystem, UzbekistanPassportLocalSystem, UzbekistanPenitentiaryInstitutionNumberSystem, UzbekistanPensionNumberSystem, UzbekistanProviderAssignedIdentifierSystem, UzbekistanSoliqSystem, UzbekistanTempMedicalRecordSystem, UzbekistanUnknownPatientCodeSystem and Xonobod shahar tibbiyot birlashmasi
- identifierType: IdentifierTypeCS
- degreeLicenseCertificate: LicenseCertificateVS, Practitioner/example-practitioner and UZCorePractitioner
- degreeLicenseCertificate: LicenseCertificateCS
- specimenType: Specimen/specimen-example-blood
- relevantClincialInformation: Specimen/specimen-example-blood
- ActCode: AuditEvent/example-auditevent-condition-lookup, Bundle/example-transaction-bundle... Show 5 more, Encounter/example-encounter, EncounterClassVS, SecurityLabelVS, UZCoreAuditEvent and UZCoreEncounter
- ActCode: ActCodeCS
- ActPriority: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterPriorityVS and UZCoreEncounter
- ActPriority: EncounterPriorityCS
- ActReason: AuditEvent/example-auditevent-condition-lookup, AuditEvent/example-auditevent-login... Show 6 more, AuditPurposeOfUseVS, Consent/example-consent, ConsentPurposeOfUseVS, SecurityLabelVS, UZCoreAuditEvent and UZCoreConsent
- ActReason: ActReasonCS
- Confidentiality: SecurityLabelVS and UZCoreAuditEvent
- Confidentiality: ConfidentialityCS
- DocumentCompletion: Provenance/example-provenance, ProvenanceActivityTypesVS and UZCoreProvenance
- DocumentCompletion: ProvenanceActivityTypesCS
- MaritalStatus: MaritalStatusVS, Patient/example-david, Patient/example-emma, Patient/example-salim and UZCorePatient
- MaritalStatus: MaritalStatusCS
- NullFlavor: MaritalStatusVS and UZCorePatient
- NullFlavor: NullFlavorCS
- ObservationInterpretation: Observation/oxygen-saturation-example, ObservationInterpretationVS and UZCoreObservation
- ObservationInterpretation: ObservationInterpretationCS
- ParticipationType: Bundle/example-transaction-bundle, Encounter/example-encounter... Show 5 more, EncounterParticipantTypeVS, RelatedPerson/example-related-person, RelationshipTypeVS, UZCoreEncounter and UZCoreRelatedPerson
- ParticipationType: ParticipationTypeCS
- RoleClass: RelationshipTypeVS and UZCoreRelatedPerson
- RoleClass: RoleClassCS
- RoleCode: LocationTypesVS, RelationshipTypeVS, Respublika onkologiya markazi, UZCoreLocation and UZCoreRelatedPerson
- RoleCode: RoleCodeCS