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
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.
Mashina tarjimasi, inson tomonidan tekshirilishi zarur. Ushbu sahifa ingliz tilidan sun'iy intellekt yordamida avtomatik tarjima qilingan va hali muharrir tomonidan tekshirilmagan. Har qanday nomuvofiqlikda asl inglizcha versiya ustuvor hisoblanadi.
Ushbu FHIR R5 joriy etish qo'llanmasi (IG) ishlab chiqish jarayonida bo'lib, hozircha production muhitida foydalanish uchun tayyor emas. U faqat Raqamli sog'liqni saqlash platformasi (DHP) doirasida testdan o'tkazish va fikr-mulohazalarni yig'ish uchun mo'ljallangan. IG takomillashtirilishi davomida uning mazmuni o'zgarib boradi.
Joriy ustuvor vazifa — asosiy resurslar profillarini DHPda joriy etishni ta'minlash uchun ularni avvalo yakunlash. Shundan so'ng, modellashtirish imkoniyatlari yetarli bo'lganda, IGning matnli qismining qolgan qismi to'ldiriladi.
Kirish qismi
Ushbu qo'llanma O'zbekistonning Raqamli sog'liqni saqlash platformasi doirasida FHIRni joriy etish bo'yicha rasmiy hujjatlar manbai hisoblanadi hamda milliy sog'liqni saqlash tizimining real sharoitlari, ehtiyojlari va xususiyatlariga moslashtirilgan.
Qo'llanma quyidagilar uchun asos bo'lib xizmat qiladi:
- FHIR resurslarini O'zbekistonning lokal ehtiyojlariga moslashtiradigan hamda respublikada raqamli sog'liqni saqlashni qo'llab-quvvatlash uchun yagona bazani yaratadigan UZ Core profillarini ishlab chiqish;
- bunday moslashtirishlar umumiy identifikatorlarni modellashtirish, HL7 kod tizimlari tarjimalari va barcha tizimlar tomonidan qo'llab-quvvatlanishi lozim bo'lgan elementlarni belgilashni o'z ichiga oladi
- Alohida klinik va ma'muriy jarayonlarni qo'llab-quvvatlaydigan muayyan ssenariylar uchun profillarni ishlab chiqish;
- masalan, tug'ilish va o'lim reyestrlari
- Xalqaro va milliy klassifikatorlar hamda terminologiyalardan foydalanish (SNOMED-CT, LOINC, ICD-10, ICD-11, CBPEPW-2020).
Ushbu IGdan foydalanish tibbiy ma'lumotlarni taqdim etishda izchillikni ta'minlaydi, tizimlar interoperabelligini oshiradi va raqamli sog'liqni saqlashning kengaytiriladigan ekotizimi uchun mustahkam poydevor yaratadi.
Loyiha tarixi
Raqamli sog'liqni saqlash platformasi (DHP) "Sog'liqni saqlashni raqamlashtirish islohotini qo'llab-quvvatlash" loyihasi doirasida ishlab chiqilmoqda. Loyiha O'zbekiston Respublikasi va KfW Taraqqiyot banki o'rtasidagi kelishuv asosida amalga oshiriladi. Ushbu tashabbus O'zbekiston Respublikasi Prezidentining 2023-yil 1-maydagi "Sog'liqni saqlash tizimini raqamlashtirish bo'yicha qo'shimcha chora-tadbirlar to'g'risida"gi PQ-140-son qarori hamda O'zbekiston Respublikasi Prezidentining 2023-yil 28-dekabrdagi "Sog'liqni saqlash tizimini raqamlashtirishni jadallashtirish va ilg'or raqamli texnologiyalarni joriy etish bo'yicha qo'shimcha chora-tadbirlar to'g'risida"gi PQ-415-son qaroriga muvofiq keladi.
Qamrov sohalari
O'zbekiston Respublikasi Raqamli sog'liqni saqlash platformasi quyidagi 19 ta komponentga asoslanadi:
Versiyalarni aniqlash
Artefaktlar, masalan profillar, kengaytmalar, kod tizimlari, qiymatlar to'plamlari, nomlash tizimlari va ushbu IGdagi FHIR paketi IGning o'z versiyasiga amal qiladi. IGni versiyalash MAJOR.MINOR.PATCH formatidagi Semantic Versioning (SemVer) tamoyillariga asoslanadi. Masalan, IGning 2.0.0 versiyasidagi barcha artefaktlar bir xil 2.0.0 versiya raqamiga ega bo'ladi. Bu esa artefakt IGning qaysi versiyasiga tegishli ekanligini oson aniqlash imkonini beradi.
Artefakt ishlab chiqish jarayonida bo'lsa va production muhitida foydalanish uchun tayyor bo'lmasa, uning statusi draft bo'ladi. Artefakt production muhitida foydalanish uchun tayyor bo'lganda, uning statusi active deb belgilanadi. Artefakt foydalanishdan chiqarilganda, uning statusi retired bo'ladi.
Kelgusida artefaktlarni real sharoitlarda testdan o'tkazish uchun yetuklik modeli joriy etiladi, biroq hozircha barcha artefaktlar production muhitida foydalanish uchun tayyor bo'lmaguncha draft hisoblanadi.
Versiyalashdan yagona istisno rasmiy THO kod tizimlarining tarjima qo'shimchalari bo'lib, ular asl kod tizimining versiyalash tartibiga amal qiladi. Masalan, agar THO kod tizimi versiyasi 2.1.0 bo'lsa, qo'shimcha ham, IG versiyasidan qat'i nazar, 2.1.0 bo'ladi. Agar THO kod tizimi 2.2.0 versiyasigacha yangilansa, qo'shimcha ham 2.2.0 versiyasigacha yangilanadi. Agar THO kod tizimi o'zgarmasdan turib qo'shimchani yangilash talab etilsa, qo'shimchaga qo'shimcha versiya raqami qo'shiladi, masalan 2.2.0.1.
IG'ning ishlab chiqish versiyasi: 0.x.x
- IG statusi:
draft
- Artefaktlar statusi:
experimental bayrog'i true ga o'rnatilgan draft
- Ishlab chiqish va testdan o'tkazishning dastlabki bosqichlarida foydalaniladi
- Kichik versiyalar orasida mos kelmaydigan o'zgarishlar bo'lishi mumkin
IG'ning ishlab chiqarish versiyalari: 1.x.x+
- IG statusi:
active
- Artefaktlar statusi:
experimental bayrog'i false ga o'rnatilgan active
- Birinchi barqaror versiya 1.0.0 dan boshlanadi
- SemVer moslik qoidalariga qat'iy rioya qilinadi
IG'ning keyingi yirik versiyalari: 2.x.x, 3.x.x va hokazo
- Production versiyalariga o'xshash
- IGning ayrim qismlarida mos kelmaydigan o'zgarishlar yoki sezilarli arxitektura yangilanishlarini bildiradi
Intellektual mulk bayonotlari
This publication includes IP covered under the following statements.
- Copyright © 2021 Australian Digital Health Agency - All rights reserved. Except for the material identified below, this content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/.[This resource also includes material from the ‘Australian Immunisation Register Vaccine Code Formats’ last updated: 22 February 2021 © Commonwealth of Australia, represented by Services Australia https://www.servicesaustralia.gov.au/organisations/health-professionals/services/medicare/australian-immunisation-register-health-professionals/resources/air-vaccine-code-formats. Licensed under https://creativecommons.org/licenses/by/3.0/au).All copies of this resource must include this copyright statement and all information contained in this statement.
Show Usage
- 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, Immunization/immunization-example-001... Show 17 more, ImmunizationRecommendation/example-uz-core-immunization-recommendation, Observation/blood-pressure-example, Observation/bmi-example, Observation/body-height-example, Observation/body-temperature-example, Observation/body-weight-example, Observation/head-circumference-example, Observation/heart-rate-example, Observation/observation-reaction-example, Observation/oxygen-saturation-example, Observation/respiratory-rate-example, ObservationCodesVS, RecommendationDateCriterionCS, RecommendationDateCriterionVS, UZCoreHealthcareService, UZCoreImmunizationRecommendation 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®): AdverseEvent/example-fatal-anaphylaxis, AdverseEventOutcomeCS... Show 45 more, AdverseEventOutcomeVS, Condition/condition-tuberculosis-risk-example, Condition/example-anaphylaxis, Condition/example-cancer, Condition/example-disability, Condition/example-headache, Condition/example-pregnancy, ConditionCodeVS, ConditionSeverityVS, Goal/example-goal, GoalDescriptionVS, GoalStartEventVS, Immunization/immunization-example-001, ImmunizationRecommendation/example-uz-core-immunization-recommendation, 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, Observation/observation-reaction-example, ObservationCodesVS, Procedure/example-procedure, ProcedureCodeVS, ProcedureOutcomeVS, ReactionTypeVS, RecommendationReasonCS, RecommendationReasonVS, RouteCodeCS, RouteCodeVS, SocioeconomicObservationCodesVS, TargetDiseaseCS, TargetDiseaseVS, UZCoreAdverseEvent, UZCoreCondition, UZCoreGoal, UZCoreHealthcareService, UZCoreImmunization, UZCoreImmunizationRecommendation, UZCoreObservation, UZCoreProcedure, UZCoreSocioeconomicObservation and UZCoreSpecimen
- 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
- AdverseEventSeriousness: AdverseEvent/example-averted-medication-error, AdverseEvent/example-fatal-anaphylaxis, AdverseEventSeriousnessVS and UZCoreAdverseEvent
- AdverseEventSeriousness: AdverseEventSeriousnessCS
- 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/condition-tuberculosis-risk-example... Show 6 more, Condition/example-anaphylaxis, Condition/example-cancer, Condition/example-disability, Condition/example-headache, Condition/example-pregnancy and UZCoreCondition
- Condition Clinical Status Codes: ClinicalStatusCS
- ConditionVerificationStatus: Condition/condition-tuberculosis-risk-example, Condition/example-anaphylaxis... Show 6 more, Condition/example-cancer, Condition/example-disability, 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
- Immunization Funding Source: FundingSourceVS, Immunization/immunization-example-001 and UZCoreImmunization
- Immunization Funding Source: FundingSourceCS
- Immunization Origin Codes: Immunization/immunization-example-001, ImmunizationOriginVS and UZCoreImmunization
- Immunization Origin Codes: ImmunizationOriginCS
- Immunization Program Eligibility: Immunization/immunization-example-001
- Immunization Recommendation Status Codes: ImmunizationRecommendation/example-uz-core-immunization-recommendation, ImmunizationRecommendation/immunization-recommendation-example, RecommendationforecastStatusVS and UZCoreImmunizationRecommendation
- Immunization Recommendation Status Codes: RecommendationforecastStatusCS
- Immunization Subpotent Reason: SubpotentReasonVS and UZCoreImmunization
- Immunization Subpotent Reason: SubpotentReasonCS
- 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 35 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, UzbekistanMedicalInformationSystem, UzbekistanMilitaryIdNumberSystem, UzbekistanNationalUniqueIdSystem, UzbekistanPassportDiplomaticSystem, UzbekistanPassportInternationalSystem, UzbekistanPassportLocalSystem, UzbekistanPenitentiaryInstitutionNumberSystem, UzbekistanPensionNumberSystem, UzbekistanProviderAssignedIdentifierSystem, UzbekistanShifSystem, UzbekistanSoliqSystem, UzbekistanTempMedicalRecordSystem, UzbekistanUnknownPatientCodeSystem and Xonobod shahar tibbiyot birlashmasi
- identifierType: IdentifierTypeCS
- degreeLicenseCertificate: LicenseCertificateVS, Practitioner/example-practitioner and UZCorePractitioner
- degreeLicenseCertificate: LicenseCertificateCS
- providerRole: Immunization/immunization-example-001
- specimenType: Specimen/example-specimen-blood-cbc, SpecimenTypesVS and UZCoreSpecimen
- specimenType: SpecimenTypesCS
- relevantClincialInformation: RelevantClinicalInformationVS, Specimen/example-specimen-blood-cbc and UZCoreSpecimen
- relevantClincialInformation: RelevantClinicalInformationCS
- 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 9 more, AuditPurposeOfUseVS, Consent/example-consent, ConsentPurposeOfUseVS, Immunization/immunization-example-001, ImmunizationStatusReasonVS, SecurityLabelVS, UZCoreAuditEvent, UZCoreConsent and UZCoreImmunization
- ActReason: ActReasonCS
- ActSite: Immunization/immunization-example-001, ImmunizationSiteVS and UZCoreImmunization
- ActSite: ImmunizationSiteCS
- 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: AdverseEvent/example-averted-medication-error, AdverseEvent/example-fatal-anaphylaxis... Show 8 more, Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterParticipantTypeVS, RelatedPerson/example-related-person, RelationshipTypeVS, UZCoreAdverseEvent, UZCoreEncounter and UZCoreRelatedPerson
- ParticipationType: ParticipationTypeCS
- RoleClass: RelationshipTypeVS and UZCoreRelatedPerson
- RoleClass: RoleClassCS
- RoleCode: LocationTypesVS, RelationshipTypeVS, Respublika onkologiya markazi, UZCoreLocation and UZCoreRelatedPerson
- RoleCode: RoleCodeCS
- WHO Collaborating Centre for Drug Statistics Methodology, Oslo, Norway. Use of all or parts of the material requires reference to the WHO Collaborating Centre for Drug Statistics Methodology. Copying and distribution for commercial purposes is not allowed. Changing or manipulating the material is not allowed.
Show Usage
