O‘zbekiston Raqamli sog‘liqni saqlash platformasi
0.5.0 - ci-build Uzbekistan bayroqcha

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

Laboratory order to result

​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 ish jarayoni laboratoriya tahlili qanday buyurtirilishini va natija qanday qaytishini ko'rsatadi. Bu FHIR ning kanonik diagnostika zanjiri bo'lib, unda havolalar bog'lanishi aniq ko'rsatilgan - profil jadvali sizga Observation.specimen mavjudligini aytadi, ammo ushbu sahifa uning aynan shu buyurtmadan olingan namunaga ishora qilishi kerakligini bildiradi.

Ishtirokchilar: buyurtma beruvchi shifokor; laboratoriya (LIS); platforma (DHP).

O'zaro ta'sirlar ketma-ketligi:

Ordering a test and returning the resultOrderingclinicianOrderingclinicianDHPFHIR serverDHPFHIR serverLaboratory(LIS)Laboratory(LIS)1POST ServiceRequest (intent = order)2order availablecollect specimen,run each analyte3POST Bundle (transaction):Specimen+Observations + DiagnosticReport(all reference ServiceRequest)4GET DiagnosticReport?based-on=ServiceRequest/[id]&_include=DiagnosticReport:result5Bundle - report + observations


Zanjir va uning havolalari:

Laboratory result - reference wiring ServiceRequest Specimen Observation DiagnosticReportBlue boxes are profiled in UZ Core and link totheir profile page; the rest are not yet profiled. request basedOn specimen basedOn result


Profil holati: Specimen va Observation UZ Core da profillangan. ServiceRequest va DiagnosticReport profillari ishlab chiqilmoqda - ular e'lon qilinmaguncha, meta.profile ni tashlab qoldirib yoki asosiy resursga o'rnatib, asosiy FHIR R5 resurslaridan foydalaning va quyidagi bog'lanishga amal qiling.

1. Tahlilni buyurtirish

Shifokor ServiceRequest yaratadi: intent = order, code da tahlil yoki panel, subject da bemor, buyurtmachi va reasonCode/reasonReference (tekshirilayotgan Condition). Buyurtirish mumkin bo'lgan tahlillar HealthcareService yozuvlari sifatida e'lon qilinadi; priority qiymati routine, urgent yoki asap.

POST [base]/ServiceRequest
{ "resourceType": "ServiceRequest", "status": "active", "intent": "order",
  "code": { "coding": [{ "system": "http://loinc.org", "code": "58410-2" }] },
  "subject": { "reference": "Patient/[id]" },
  "requester": { "reference": "PractitionerRole/[id]" },
  "priority": "routine" }

Avvalgi tahlilning takrori ServiceRequest.basedOn ni dastlabki buyurtmaga o'rnatadi.

2. Namunani olish

Laboratoriya Specimen ni qayd etadi: uning type i, olingan sana/vaqti va identifikatori, subject da bemor va eng muhimi Specimen.request ServiceRequest ga qaytib ishora qiladi.

POST [base]/Specimen
{ "resourceType": "Specimen",
  "meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-specimen"] },
  "subject": { "reference": "Patient/[id]" },
  "request": [{ "reference": "ServiceRequest/[id]" }],
  "type": { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/v2-0487", "code": "BLD", "display": "Whole blood" }] } }

3. Natijalarni qaytarish

Har bir analit - bu LOINC code, value[x], interpretation (normal / high / low / critical) va referenceRange ga ega Observation. Har bir Observation basedOn ni ServiceRequest ga va specimen ni Specimen ga o'rnatadi. To'plam DiagnosticReport orqali jamlanadi: uning basedOn i ServiceRequest, result i esa Observation larni sanab o'tadi.

GET [base]/DiagnosticReport?based-on=ServiceRequest/[id]&_include=DiagnosticReport:result
GET [base]/Observation?patient=Patient/[id]&category=laboratory&_sort=-date

​Butun to'plamni bitta transaction Bundle sifatida qaytarish maqsadga muvofiq, shunda buyurtma, namuna, kuzatuvlar va hisobot atomar tarzda yetib keladi. Yakunlangan, imzolangan hisobot document Bundle sifatida yig'iladi (Composition sarlavhasi natijalarga ishora qiladi va Provenance orqali imzolanadi) - Composition resurslarni takrorlamasdan ularga ishora qiladi. Qarang: Umumiy ko'rsatmalar → Bundle lar.

Holat va parallellik

ServiceRequest.status buyurtma hayotiy tsikliga amal qiladi (draft → active → completed yoki revoked); entered-in-error/unknown tuzatishlar uchun ajratilgan. Bekor qilish faol buyurtmani revoked ga o'tkazadi (izoh bilan), yakunlangan buyurtmani esa o'zgartirib bo'lmaydi. Parallel tahrirlar optimistik parallellikdan foydalanadi - oxirgi o'qishdan olingan ETag ni If-Match sifatida yuboring; eskirgan versiya 412 Precondition Failed bilan rad etiladi. Qaytadan o'qing va qayta urinib ko'ring - qarang: Parallellik.

Aloqador