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

Uzbekistan Digital Health Platform - Local Development build (v0.7.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. 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.

Ushbu jarayon laboratoriya tekshiruvi qanday tayinlanishi va uning natijasi qanday qaytarilishini ko'rsatadi. Bu FHIR diagnostikasining kanonik zanjiri bo'lib, undagi references tuzilmasi aniq ko'rsatilgan - profil jadvali Observation.specimen elementi mavjudligini ko'rsatadi, ushbu sahifada esa u mazkur tayinlash doirasida olingan namunaga reference ko'rsatishi kerakligi tushuntiriladi.

Ishtirokchilar: tekshiruvni tayinlaydigan klinitsist; laboratoriya (LIS - Laboratory Information System, laboratoriya axborot tizimi); platforma (DHP - Digital Health Platform, Raqamli sog'liqni saqlash platformasi).

O'zaro ishlash 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


Resurslar zanjiri va uning references:

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: to'rtta resursning barchasi UZ Core'da profillangan - Specimen, Observation, ServiceRequest (laboratoriyaga xos) va DiagnosticReport. Har bir resursdagi meta.profile elementida mos profilni ko'rsating va quyidagi references tuzilmasiga rioya qiling.

1. Tekshiruvni tayinlash

​Klinitsist ServiceRequest resursini yaratadi va unda intent = order qiymatini, tekshiruv yoki panelni code elementida, bemorni subject elementida, requester elementida so'rov yuboruvchini va reasonCode/reasonReference elementida tekshirilayotgan Condition resursini ko'rsatadi. Tayinlash mumkin bo'lgan tekshiruvlar HealthcareService yozuvlari sifatida e'lon qilinadi; priority qiymati routine, urgent yoki asap.

POST [base]/ServiceRequest
{ "resourceType": "ServiceRequest",
  "meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest-laboratory"] },
  "status": "active", "intent": "order",
  "code": { "coding": [{ "system": "http://loinc.org", "code": "58410-2" }] },
  "subject": { "reference": "Patient/[id]" },
  "requester": { "reference": "PractitionerRole/[id]" },
  "priority": "routine" }

Avvalgi tekshiruv takrorlanganda ServiceRequest.basedOn elementida dastlabki tayinlashga reference ko'rsatiladi.

2. Namunani olish

Laboratoriya Specimen resursini qayd etadi. Unda type elementi, namuna olingan sana va vaqt, identifikator hamda bemor subject elementida ko'rsatiladi. Eng muhimi, Specimen.request elementida ServiceRequest resursiga reference ko'rsatiladi.

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 aniqlanadigan ko'rsatkich Observation resursi sifatida taqdim etiladi; unda LOINC code elementi, value[x], interpretation (normal / high / low / critical) hamda referenceRange elementi ko'rsatiladi. Har bir Observation resursida basedOn elementida ServiceRequest resursiga reference, specimen elementida esa Specimen resursiga reference ko'rsatiladi. Natijalar to'plami umumlashtiriladi va DiagnosticReport resursida taqdim etiladi: uning basedOn elementi ServiceRequest resursiga reference saqlaydi, result elementida esa Observation resurslari ro'yxati ko'rsatiladi.

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

​Butun to'plamni bitta tranzaksion Bundle sifatida qaytarish tavsiya etiladi, shunda tayinlash, namuna, Observation resurslari va hisobot birgalikda atomar tarzda qaytariladi. Yakunlangan va imzolangan hisobot hujjat Bundle sifatida shakllantiriladi (Composition natijalarga references saqlaydigan sarlavha vazifasini bajaradi va hisobot Provenance orqali imzolanadi) - Composition resurslarni takrorlamaydi, balki ularga references saqlaydi. Umumiy ko'rsatmalar → Bundle bo'limiga qarang.

Statuslar va parallel o'zgartirishlar

ServiceRequest.status tayinlashning hayotiy sikliga mos ravishda o'zgaradi (draft → active → completed yoki revoked); entered-in-error/unknown qiymatlari tuzatishlar uchun ajratilgan. Bekor qilishda faol tayinlash revoked holatiga o'tkaziladi (izoh bilan), yakunlangan tayinlashni esa o'zgartirib bo'lmaydi. Bir vaqtda tahrirlashda optimistik versiya nazorati qo'llaniladi - oxirgi o'qishda olingan ETag qiymatini If-Match sifatida yuboring; eskirgan versiya 412 Precondition Failed xatosi bilan rad etiladi. Resursni qayta o'qing va so'rovni takrorlang - Parallel o'zgartirishlar bo'limiga qarang.

Tegishli materiallar