Uzbekistan Digital Health Platform
0.13.0 - ci-build
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.13.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
| Official URL: https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report | Version: 0.13.0 | ||||
| Active as of 2026-02-06 | Computable Name: UZCoreDiagnosticReport | ||||
Uzbekistan Core profile for DiagnosticReport, representing clinical records of diagnostic reports within the national health information exchange.
UZ Core DiagnosticReport is the report a laboratory or other diagnostic service issues for a patient: a complete blood count, a coagulation panel, a urinalysis. It closes the laboratory order to result chain. The report points back to the ServiceRequest it answers (basedOn), lists the Observation results it summarises (result) and the Specimen they were measured on, and can carry the issued report as a PDF. The individual values live in the Observations; the report groups them and records who issued them and when. An Encounter and a DeviceUsage can point to a report as their reason.
The elements below must always be present (mandatory) or must be supported when the data is available (Must Support). Not all of them are required, but your system must populate each Must Support element when it has the data, and process it on receipt. This is the human-readable summary; the formal views below give the exact cardinalities, types and terminology bindings.
The profile adds no mandatory elements. The base resource requires a status and a code saying what kind of report it is.
basedOn);status of the report (registered / partial / preliminary / final / amended / corrected / cancelled / entered-in-error);category (hematology / chemistry / microbiology …);code);subject), usually the patient;effective[x]), usually when the specimen was collected;performer: the practitioner, role or organization responsible for the report;result);media), each with a link and an optional comment;presentedForm), for example a PDF.The examples below go from the smallest valid report to a full laboratory report with its order, specimen and results. Each one validates against this profile. The complete reference instances are the CBC report, the external report with its own code and the external report with text only.
A report needs a status and a code. Every UZ Core resource also names its profile in meta.profile, and a report is only useful with the patient it is about:
{
"resourceType": "DiagnosticReport",
"meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report"] },
"status": "final",
"code": {
"coding": [ { "system": "https://terminology.dhp.uz/fhir/core/CodeSystem/lab-report-types-cs", "code": "lab-rep-01" } ]
},
"subject": { "reference": "Patient/example-salim" }
}
code comes from the national laboratory report types, here lab-rep-01 (complete blood count). status uses HL7 codes, whose Uzbek and Russian displays come from DHP supplements, so you can leave display out.
The usual report answers an order and summarises its results. basedOn points to the ServiceRequest, specimen to the sample, and result to the Observations. Here result is a single CBC panel Observation whose analytes are its components:
{
"resourceType": "DiagnosticReport",
"meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report"] },
"language": "uz",
"identifier": [
{ "system": "https://terminology.dhp.uz/fhir/core/NamingSystem/diagnostic-report-id", "value": "DR-2026-0001" }
],
"basedOn": [ { "reference": "ServiceRequest/example-cbc-order" } ],
"status": "final",
"category": [
{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0074", "code": "HM" } ] }
],
"code": {
"coding": [
{
"system": "https://terminology.dhp.uz/fhir/core/CodeSystem/lab-report-types-cs",
"code": "lab-rep-01",
"display": "Umumiy qon tahlili"
}
]
},
"subject": { "reference": "Patient/example-salim" },
"encounter": { "reference": "Encounter/example-encounter" },
"effectiveDateTime": "2026-02-06T10:30:00+05:00",
"issued": "2026-02-06T11:00:00+05:00",
"performer": [ { "reference": "Organization/tashkent-hospital" } ],
"specimen": [ { "reference": "Specimen/example-specimen-blood-cbc" } ],
"result": [ { "reference": "Observation/cbc-panel-example" } ]
}
The laboratory report types code system is in Uzbek, so a display you send must be the Uzbek one and the resource must say "language": "uz". category takes a code from the national service category value set (HL7 v2 table 0074); codes from other systems may sit beside it. effective[x] is when the result is clinically relevant, usually the collection time; issued is when the report was released. Use the diagnostic report identifier system for the report number.
presentedForm carries the report as the patient or clinician sees it, usually a PDF. Give its contentType, and either the content inline in data (base64) or a url to a Binary. media links images or other documents that belong to the report, each through a link to a DocumentReference with an optional comment:
{
"resourceType": "DiagnosticReport",
"meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report"] },
"status": "final",
"code": {
"coding": [ { "system": "https://terminology.dhp.uz/fhir/core/CodeSystem/lab-report-types-cs", "code": "lab-rep-01" } ]
},
"subject": { "reference": "Patient/example-salim" },
"result": [ { "reference": "Observation/cbc-panel-example" } ],
"media": [
{
"comment": "Blood smear, x1000",
"link": { "reference": "DocumentReference/example-blood-smear-image" }
}
],
"presentedForm": [
{
"contentType": "application/pdf",
"title": "Complete Blood Count report",
"url": "Binary/example-cbc-report-pdf"
}
]
}
The PDF does not replace the coded results: send the Observations in result as well, so other systems can read the values.
The code binding is extensible. When a laboratory issues a report that has no national code, send the laboratory information system's own code with its own system, and the report name in text:
{
"resourceType": "DiagnosticReport",
"meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report"] },
"status": "final",
"category": [
{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0074", "code": "LAB" } ] }
],
"code": {
"coding": [ { "system": "https://lis.aurora-lab.uz/fhir/CodeSystem/report-type", "code": "AUR-0142" } ],
"text": "Special immunology assay reported by Aurora LIS"
},
"subject": { "reference": "Patient/example-salim" },
"effectiveDateTime": "2026-02-06T10:30:00+05:00",
"performer": [ { "reference": "Practitioner/example-practitioner" } ]
}
The code system URL above is only an example; use the one your laboratory system publishes. When the source system has no code at all, send code with text only, as in the text-only example.
For example API calls, see the Quick Start at the bottom of this page.
Usages:
You can also check for usages in the FHIR IG Statistics
Description Differentials, Snapshots, and other representations.
| Name | Flags | Card. | Type | Description & Constraints Filter: ![]() |
|---|---|---|---|---|
![]() |
C | 0..* | DiagnosticReport(5.0.0) | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Constraints: dgr-1 |
![]() ![]() |
0..1 | uri | A set of rules under which this content was created | |
![]() ![]() |
0..* | Resource | Contained, inline Resources | |
![]() ![]() |
0..* | Extension | Extensions that cannot be ignored Constraints: ext-1 | |
![]() ![]() |
0..* | Identifier | Identifier for report | |
![]() ![]() |
0..* | Reference(ServiceRequest) | What was requested | |
![]() ![]() |
1..1 | code | registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown Binding: DiagnosticReportStatusVS (0.13.0) (required) | |
![]() ![]() |
0..* | CodeableConcept | Service category Slice: Unordered, Open by value:$this Binding: DiagnosticReportServiceCategoryVS (0.13.0) (preferred) Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them | |
![]() ![]() ![]() |
0..* | CodeableConcept | Service category from the national value set Binding: DiagnosticReportServiceCategoryVS (0.13.0) (required) | |
![]() ![]() |
1..1 | CodeableConcept | Report types used in Ministry of Health of Uzbekistan (399) Binding: LabReportTypesVS (0.13.0) (extensible) | |
![]() ![]() |
0..1 | Reference(UZ Core Patient(0.13.0) | UZ Core Organization(0.13.0) | UZ Core Practitioner(0.13.0) | UZ Core Location(0.13.0) | UZ Core Medication(0.13.0)) | Who and/or what this report is about | |
![]() ![]() |
0..1 | Reference(UZ Core Encounter(0.13.0)) | The healthcare event which this Laboratory Report is about (when test ordered). | |
![]() ![]() |
0..1 | Clinically relevant time/time-period for report. | ||
![]() ![]() ![]() |
dateTime | |||
![]() ![]() ![]() |
Period | |||
![]() ![]() |
0..* | Reference(UZ Core Practitioner(0.13.0) | UZ Core PractitionerRole(0.13.0) | UZ Core Organization(0.13.0)) | Responsible Diagnostic Service. | |
![]() ![]() |
0..* | Reference(UZ Core Specimen(0.13.0)) | Specimens this report is based on. | |
![]() ![]() |
C | 0..* | Reference(UZ Core Observation(0.13.0)) | Laboratory and etc,. results |
![]() ![]() |
0..* | BackboneElement | Additional data (like images, diagrams or documents) associated with this report | |
![]() ![]() ![]() |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |
![]() ![]() ![]() |
0..1 | string | Comment or explanation about the image or data | |
![]() ![]() ![]() |
1..1 | Reference(DocumentReference) | Reference to the image or data | |
![]() ![]() |
0..* | Attachment | Entire report as issued pdf | |
Documentation for this format | ||||
| Path | Status | Usage | ValueSet | Version | Source |
| DiagnosticReport.status | Base | required | DiagnosticReport status | 📍0.13.0 | This IG |
| DiagnosticReport.category | Base | preferred | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.category:dhpCategory | Base | required | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.code | Base | extensible | Laboratory report type | 📍0.13.0 | This IG |
| Id | Grade | Path(s) | Description | Expression |
This structure is derived from DiagnosticReport
| Name | Flags | Card. | Type | Description & Constraints Filter: ![]() |
|---|---|---|---|---|
![]() |
0..* | DiagnosticReport(5.0.0) | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports | |
![]() ![]() |
0..* | Identifier | Identifier for report | |
![]() ![]() |
0..* | Reference(ServiceRequest) | What was requested | |
![]() ![]() |
1..1 | code | registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown Binding: DiagnosticReportStatusVS (0.13.0) (required) | |
![]() ![]() |
0..* | CodeableConcept | Service category Slice: Unordered, Open by value:$this Binding: DiagnosticReportServiceCategoryVS (0.13.0) (preferred) Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them | |
![]() ![]() ![]() |
0..* | CodeableConcept | Service category from the national value set Binding: DiagnosticReportServiceCategoryVS (0.13.0) (required) | |
![]() ![]() |
1..1 | CodeableConcept | Report types used in Ministry of Health of Uzbekistan (399) Binding: LabReportTypesVS (0.13.0) (extensible) | |
![]() ![]() |
0..1 | Reference(UZ Core Patient(0.13.0) | UZ Core Organization(0.13.0) | UZ Core Practitioner(0.13.0) | UZ Core Location(0.13.0) | UZ Core Medication(0.13.0)) | Who and/or what this report is about | |
![]() ![]() |
0..1 | Reference(UZ Core Encounter(0.13.0)) | The healthcare event which this Laboratory Report is about (when test ordered). | |
![]() ![]() |
0..1 | dateTime, Period | Clinically relevant time/time-period for report. | |
![]() ![]() |
0..* | Reference(UZ Core Practitioner(0.13.0) | UZ Core PractitionerRole(0.13.0) | UZ Core Organization(0.13.0)) | Responsible Diagnostic Service. | |
![]() ![]() |
0..* | Reference(UZ Core Specimen(0.13.0)) | Specimens this report is based on. | |
![]() ![]() |
0..* | Reference(UZ Core Observation(0.13.0)) | Laboratory and etc,. results | |
![]() ![]() |
0..* | BackboneElement | Additional data (like images, diagrams or documents) associated with this report | |
![]() ![]() ![]() |
0..1 | string | Comment or explanation about the image or data | |
![]() ![]() ![]() |
1..1 | Reference(DocumentReference) | Reference to the image or data | |
![]() ![]() |
0..* | Attachment | Entire report as issued pdf | |
Documentation for this format | ||||
| Path | Status | Usage | ValueSet | Version | Source |
| DiagnosticReport.status | Base | required | DiagnosticReport status | 📍0.13.0 | This IG |
| DiagnosticReport.category | Base | preferred | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.category:dhpCategory | Base | required | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.code | Base | extensible | Laboratory report type | 📍0.13.0 | This IG |
| Name | Flags | Card. | Type | Description & Constraints Filter: ![]() | ||||
|---|---|---|---|---|---|---|---|---|
![]() |
C | 0..* | DiagnosticReport(5.0.0) | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Constraints: dgr-1 | ||||
![]() ![]() |
0..1 | id | Logical id of this artifact | |||||
![]() ![]() |
0..1 | Meta | Metadata about the resource | |||||
![]() ![]() |
0..1 | uri | A set of rules under which this content was created | |||||
![]() ![]() |
0..1 | code | Language of the resource content Binding: AllLanguages (required): IETF language tag for a human language
| |||||
![]() ![]() |
0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | |||||
![]() ![]() |
0..* | Resource | Contained, inline Resources | |||||
![]() ![]() |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
![]() ![]() |
0..* | Extension | Extensions that cannot be ignored Constraints: ext-1 | |||||
![]() ![]() |
0..* | Identifier | Identifier for report | |||||
![]() ![]() |
0..* | Reference(ServiceRequest) | What was requested | |||||
![]() ![]() |
1..1 | code | registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown Binding: DiagnosticReportStatusVS (0.13.0) (required) | |||||
![]() ![]() |
0..* | CodeableConcept | Service category Slice: Unordered, Open by value:$this Binding: DiagnosticReportServiceCategoryVS (0.13.0) (preferred) Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them | |||||
![]() ![]() ![]() |
0..* | CodeableConcept | Service category from the national value set Binding: DiagnosticReportServiceCategoryVS (0.13.0) (required) | |||||
![]() ![]() |
1..1 | CodeableConcept | Report types used in Ministry of Health of Uzbekistan (399) Binding: LabReportTypesVS (0.13.0) (extensible) | |||||
![]() ![]() |
0..1 | Reference(UZ Core Patient(0.13.0) | UZ Core Organization(0.13.0) | UZ Core Practitioner(0.13.0) | UZ Core Location(0.13.0) | UZ Core Medication(0.13.0)) | Who and/or what this report is about | |||||
![]() ![]() |
0..1 | Reference(UZ Core Encounter(0.13.0)) | The healthcare event which this Laboratory Report is about (when test ordered). | |||||
![]() ![]() |
0..1 | Clinically relevant time/time-period for report. | ||||||
![]() ![]() ![]() |
dateTime | |||||||
![]() ![]() ![]() |
Period | |||||||
![]() ![]() |
0..1 | instant | DateTime this version was made | |||||
![]() ![]() |
0..* | Reference(UZ Core Practitioner(0.13.0) | UZ Core PractitionerRole(0.13.0) | UZ Core Organization(0.13.0)) | Responsible Diagnostic Service. | |||||
![]() ![]() |
0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Primary result interpreter | |||||
![]() ![]() |
0..* | Reference(UZ Core Specimen(0.13.0)) | Specimens this report is based on. | |||||
![]() ![]() |
C | 0..* | Reference(UZ Core Observation(0.13.0)) | Laboratory and etc,. results | ||||
![]() ![]() |
0..* | Annotation | Comments about the diagnostic report | |||||
![]() ![]() |
0..* | Reference(GenomicStudy | ImagingStudy) | Reference to full details of an analysis associated with the diagnostic report | |||||
![]() ![]() |
0..* | BackboneElement | Additional information supporting the diagnostic report | |||||
![]() ![]() ![]() |
0..1 | string | Unique id for inter-element referencing | |||||
![]() ![]() ![]() |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
![]() ![]() ![]() |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |||||
![]() ![]() ![]() |
1..1 | CodeableConcept | Supporting information role code Binding: Hl7VSVSObservationType (3.0.0) (example): The code value for the role of the supporting information in the diagnostic report. | |||||
![]() ![]() ![]() |
1..1 | Reference(Procedure | Observation | DiagnosticReport | Citation) | Supporting information reference | |||||
![]() ![]() |
0..* | BackboneElement | Additional data (like images, diagrams or documents) associated with this report | |||||
![]() ![]() ![]() |
0..1 | string | Unique id for inter-element referencing | |||||
![]() ![]() ![]() |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
![]() ![]() ![]() |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |||||
![]() ![]() ![]() |
0..1 | string | Comment or explanation about the image or data | |||||
![]() ![]() ![]() |
1..1 | Reference(DocumentReference) | Reference to the image or data | |||||
![]() ![]() |
C | 0..1 | Reference(Composition) | Reference to a Composition resource for the DiagnosticReport structure | ||||
![]() ![]() |
0..1 | markdown | Clinical conclusion (interpretation) of test results | |||||
![]() ![]() |
0..* | CodeableConcept | Codes for the clinical conclusion of test results Binding: SNOMEDCTClinicalFindings (example): SNOMED CT Clinical Findings | |||||
![]() ![]() |
0..* | Attachment | Entire report as issued pdf | |||||
Documentation for this format | ||||||||
| Path | Status | Usage | ValueSet | Version | Source |
| DiagnosticReport.language | Base | required | All Languages | 📍5.0.0 | FHIR Std. |
| DiagnosticReport.status | Base | required | DiagnosticReport status | 📍0.13.0 | This IG |
| DiagnosticReport.category | Base | preferred | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.category:dhpCategory | Base | required | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.code | Base | extensible | Laboratory report type | 📍0.13.0 | This IG |
| DiagnosticReport.supportingInfo.type | Base | example | hl7VS-VS-observationType | 📍3.0.0 | THO v7.5 |
| DiagnosticReport.conclusionCode | Base | example | SNOMED CT Clinical Findings | 📍5.0.0 | FHIR Std. |
| Id | Grade | Path(s) | Description | Expression |
This structure is derived from DiagnosticReport
Summary
Must-Support: 16 elements
Structures
This structure refers to these other structures:
Slices
This structure defines the following Slices:
Key Elements View
| Name | Flags | Card. | Type | Description & Constraints Filter: ![]() |
|---|---|---|---|---|
![]() |
C | 0..* | DiagnosticReport(5.0.0) | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Constraints: dgr-1 |
![]() ![]() |
0..1 | uri | A set of rules under which this content was created | |
![]() ![]() |
0..* | Resource | Contained, inline Resources | |
![]() ![]() |
0..* | Extension | Extensions that cannot be ignored Constraints: ext-1 | |
![]() ![]() |
0..* | Identifier | Identifier for report | |
![]() ![]() |
0..* | Reference(ServiceRequest) | What was requested | |
![]() ![]() |
1..1 | code | registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown Binding: DiagnosticReportStatusVS (0.13.0) (required) | |
![]() ![]() |
0..* | CodeableConcept | Service category Slice: Unordered, Open by value:$this Binding: DiagnosticReportServiceCategoryVS (0.13.0) (preferred) Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them | |
![]() ![]() ![]() |
0..* | CodeableConcept | Service category from the national value set Binding: DiagnosticReportServiceCategoryVS (0.13.0) (required) | |
![]() ![]() |
1..1 | CodeableConcept | Report types used in Ministry of Health of Uzbekistan (399) Binding: LabReportTypesVS (0.13.0) (extensible) | |
![]() ![]() |
0..1 | Reference(UZ Core Patient(0.13.0) | UZ Core Organization(0.13.0) | UZ Core Practitioner(0.13.0) | UZ Core Location(0.13.0) | UZ Core Medication(0.13.0)) | Who and/or what this report is about | |
![]() ![]() |
0..1 | Reference(UZ Core Encounter(0.13.0)) | The healthcare event which this Laboratory Report is about (when test ordered). | |
![]() ![]() |
0..1 | Clinically relevant time/time-period for report. | ||
![]() ![]() ![]() |
dateTime | |||
![]() ![]() ![]() |
Period | |||
![]() ![]() |
0..* | Reference(UZ Core Practitioner(0.13.0) | UZ Core PractitionerRole(0.13.0) | UZ Core Organization(0.13.0)) | Responsible Diagnostic Service. | |
![]() ![]() |
0..* | Reference(UZ Core Specimen(0.13.0)) | Specimens this report is based on. | |
![]() ![]() |
C | 0..* | Reference(UZ Core Observation(0.13.0)) | Laboratory and etc,. results |
![]() ![]() |
0..* | BackboneElement | Additional data (like images, diagrams or documents) associated with this report | |
![]() ![]() ![]() |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |
![]() ![]() ![]() |
0..1 | string | Comment or explanation about the image or data | |
![]() ![]() ![]() |
1..1 | Reference(DocumentReference) | Reference to the image or data | |
![]() ![]() |
0..* | Attachment | Entire report as issued pdf | |
Documentation for this format | ||||
| Path | Status | Usage | ValueSet | Version | Source |
| DiagnosticReport.status | Base | required | DiagnosticReport status | 📍0.13.0 | This IG |
| DiagnosticReport.category | Base | preferred | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.category:dhpCategory | Base | required | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.code | Base | extensible | Laboratory report type | 📍0.13.0 | This IG |
| Id | Grade | Path(s) | Description | Expression |
Differential View
This structure is derived from DiagnosticReport
| Name | Flags | Card. | Type | Description & Constraints Filter: ![]() |
|---|---|---|---|---|
![]() |
0..* | DiagnosticReport(5.0.0) | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports | |
![]() ![]() |
0..* | Identifier | Identifier for report | |
![]() ![]() |
0..* | Reference(ServiceRequest) | What was requested | |
![]() ![]() |
1..1 | code | registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown Binding: DiagnosticReportStatusVS (0.13.0) (required) | |
![]() ![]() |
0..* | CodeableConcept | Service category Slice: Unordered, Open by value:$this Binding: DiagnosticReportServiceCategoryVS (0.13.0) (preferred) Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them | |
![]() ![]() ![]() |
0..* | CodeableConcept | Service category from the national value set Binding: DiagnosticReportServiceCategoryVS (0.13.0) (required) | |
![]() ![]() |
1..1 | CodeableConcept | Report types used in Ministry of Health of Uzbekistan (399) Binding: LabReportTypesVS (0.13.0) (extensible) | |
![]() ![]() |
0..1 | Reference(UZ Core Patient(0.13.0) | UZ Core Organization(0.13.0) | UZ Core Practitioner(0.13.0) | UZ Core Location(0.13.0) | UZ Core Medication(0.13.0)) | Who and/or what this report is about | |
![]() ![]() |
0..1 | Reference(UZ Core Encounter(0.13.0)) | The healthcare event which this Laboratory Report is about (when test ordered). | |
![]() ![]() |
0..1 | dateTime, Period | Clinically relevant time/time-period for report. | |
![]() ![]() |
0..* | Reference(UZ Core Practitioner(0.13.0) | UZ Core PractitionerRole(0.13.0) | UZ Core Organization(0.13.0)) | Responsible Diagnostic Service. | |
![]() ![]() |
0..* | Reference(UZ Core Specimen(0.13.0)) | Specimens this report is based on. | |
![]() ![]() |
0..* | Reference(UZ Core Observation(0.13.0)) | Laboratory and etc,. results | |
![]() ![]() |
0..* | BackboneElement | Additional data (like images, diagrams or documents) associated with this report | |
![]() ![]() ![]() |
0..1 | string | Comment or explanation about the image or data | |
![]() ![]() ![]() |
1..1 | Reference(DocumentReference) | Reference to the image or data | |
![]() ![]() |
0..* | Attachment | Entire report as issued pdf | |
Documentation for this format | ||||
| Path | Status | Usage | ValueSet | Version | Source |
| DiagnosticReport.status | Base | required | DiagnosticReport status | 📍0.13.0 | This IG |
| DiagnosticReport.category | Base | preferred | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.category:dhpCategory | Base | required | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.code | Base | extensible | Laboratory report type | 📍0.13.0 | This IG |
Snapshot ViewView
| Name | Flags | Card. | Type | Description & Constraints Filter: ![]() | ||||
|---|---|---|---|---|---|---|---|---|
![]() |
C | 0..* | DiagnosticReport(5.0.0) | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Constraints: dgr-1 | ||||
![]() ![]() |
0..1 | id | Logical id of this artifact | |||||
![]() ![]() |
0..1 | Meta | Metadata about the resource | |||||
![]() ![]() |
0..1 | uri | A set of rules under which this content was created | |||||
![]() ![]() |
0..1 | code | Language of the resource content Binding: AllLanguages (required): IETF language tag for a human language
| |||||
![]() ![]() |
0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | |||||
![]() ![]() |
0..* | Resource | Contained, inline Resources | |||||
![]() ![]() |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
![]() ![]() |
0..* | Extension | Extensions that cannot be ignored Constraints: ext-1 | |||||
![]() ![]() |
0..* | Identifier | Identifier for report | |||||
![]() ![]() |
0..* | Reference(ServiceRequest) | What was requested | |||||
![]() ![]() |
1..1 | code | registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown Binding: DiagnosticReportStatusVS (0.13.0) (required) | |||||
![]() ![]() |
0..* | CodeableConcept | Service category Slice: Unordered, Open by value:$this Binding: DiagnosticReportServiceCategoryVS (0.13.0) (preferred) Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them | |||||
![]() ![]() ![]() |
0..* | CodeableConcept | Service category from the national value set Binding: DiagnosticReportServiceCategoryVS (0.13.0) (required) | |||||
![]() ![]() |
1..1 | CodeableConcept | Report types used in Ministry of Health of Uzbekistan (399) Binding: LabReportTypesVS (0.13.0) (extensible) | |||||
![]() ![]() |
0..1 | Reference(UZ Core Patient(0.13.0) | UZ Core Organization(0.13.0) | UZ Core Practitioner(0.13.0) | UZ Core Location(0.13.0) | UZ Core Medication(0.13.0)) | Who and/or what this report is about | |||||
![]() ![]() |
0..1 | Reference(UZ Core Encounter(0.13.0)) | The healthcare event which this Laboratory Report is about (when test ordered). | |||||
![]() ![]() |
0..1 | Clinically relevant time/time-period for report. | ||||||
![]() ![]() ![]() |
dateTime | |||||||
![]() ![]() ![]() |
Period | |||||||
![]() ![]() |
0..1 | instant | DateTime this version was made | |||||
![]() ![]() |
0..* | Reference(UZ Core Practitioner(0.13.0) | UZ Core PractitionerRole(0.13.0) | UZ Core Organization(0.13.0)) | Responsible Diagnostic Service. | |||||
![]() ![]() |
0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Primary result interpreter | |||||
![]() ![]() |
0..* | Reference(UZ Core Specimen(0.13.0)) | Specimens this report is based on. | |||||
![]() ![]() |
C | 0..* | Reference(UZ Core Observation(0.13.0)) | Laboratory and etc,. results | ||||
![]() ![]() |
0..* | Annotation | Comments about the diagnostic report | |||||
![]() ![]() |
0..* | Reference(GenomicStudy | ImagingStudy) | Reference to full details of an analysis associated with the diagnostic report | |||||
![]() ![]() |
0..* | BackboneElement | Additional information supporting the diagnostic report | |||||
![]() ![]() ![]() |
0..1 | string | Unique id for inter-element referencing | |||||
![]() ![]() ![]() |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
![]() ![]() ![]() |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |||||
![]() ![]() ![]() |
1..1 | CodeableConcept | Supporting information role code Binding: Hl7VSVSObservationType (3.0.0) (example): The code value for the role of the supporting information in the diagnostic report. | |||||
![]() ![]() ![]() |
1..1 | Reference(Procedure | Observation | DiagnosticReport | Citation) | Supporting information reference | |||||
![]() ![]() |
0..* | BackboneElement | Additional data (like images, diagrams or documents) associated with this report | |||||
![]() ![]() ![]() |
0..1 | string | Unique id for inter-element referencing | |||||
![]() ![]() ![]() |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
![]() ![]() ![]() |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |||||
![]() ![]() ![]() |
0..1 | string | Comment or explanation about the image or data | |||||
![]() ![]() ![]() |
1..1 | Reference(DocumentReference) | Reference to the image or data | |||||
![]() ![]() |
C | 0..1 | Reference(Composition) | Reference to a Composition resource for the DiagnosticReport structure | ||||
![]() ![]() |
0..1 | markdown | Clinical conclusion (interpretation) of test results | |||||
![]() ![]() |
0..* | CodeableConcept | Codes for the clinical conclusion of test results Binding: SNOMEDCTClinicalFindings (example): SNOMED CT Clinical Findings | |||||
![]() ![]() |
0..* | Attachment | Entire report as issued pdf | |||||
Documentation for this format | ||||||||
| Path | Status | Usage | ValueSet | Version | Source |
| DiagnosticReport.language | Base | required | All Languages | 📍5.0.0 | FHIR Std. |
| DiagnosticReport.status | Base | required | DiagnosticReport status | 📍0.13.0 | This IG |
| DiagnosticReport.category | Base | preferred | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.category:dhpCategory | Base | required | DiagnosticReport service category | 📍0.13.0 | This IG |
| DiagnosticReport.code | Base | extensible | Laboratory report type | 📍0.13.0 | This IG |
| DiagnosticReport.supportingInfo.type | Base | example | hl7VS-VS-observationType | 📍3.0.0 | THO v7.5 |
| DiagnosticReport.conclusionCode | Base | example | SNOMED CT Clinical Findings | 📍5.0.0 | FHIR Std. |
| Id | Grade | Path(s) | Description | Expression |
This structure is derived from DiagnosticReport
Summary
Must-Support: 16 elements
Structures
This structure refers to these other structures:
Slices
This structure defines the following Slices:
Other representations of profile: CSV, Excel, Schematron
Common API interactions for this profile. Requests require a JWT access token - see Security and authentication. [base] is the FHIR server base URL; | separates a code system from its value and must be URL-encoded as %7C.
Read a report by server id, and its earlier versions
GET [base]/DiagnosticReport/[id]
GET [base]/DiagnosticReport/[id]/_history
Search
GET [base]/DiagnosticReport?identifier=https://terminology.dhp.uz/fhir/core/NamingSystem/diagnostic-report-id%7CDR-2026-0001
GET [base]/DiagnosticReport?patient=Patient/[id]&code=https://terminology.dhp.uz/fhir/core/CodeSystem/lab-report-types-cs%7Clab-rep-01
GET [base]/DiagnosticReport?patient=Patient/[id]&category=http://terminology.hl7.org/CodeSystem/v2-0074%7CHM
GET [base]/DiagnosticReport?patient=Patient/[id]&status=final&date=ge2026-01-01
GET [base]/DiagnosticReport?based-on=ServiceRequest/[id]&_include=DiagnosticReport:result
GET [base]/DiagnosticReport?encounter=Encounter/[id]
GET [base]/DiagnosticReport?specimen=Specimen/[id]
GET [base]/DiagnosticReport?performer=Organization/[id]&issued=ge2026-02-01
Create a report
POST [base]/DiagnosticReport
{
"resourceType": "DiagnosticReport",
"meta": { "profile": [ "https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report" ] },
"basedOn": [ { "reference": "ServiceRequest/[id]" } ],
"status": "preliminary",
"code": { "coding": [ { "system": "https://terminology.dhp.uz/fhir/core/CodeSystem/lab-report-types-cs", "code": "..." } ] },
"subject": { "reference": "Patient/[id]" },
"result": [ { "reference": "Observation/[id]" } ],
...
}
Send the report together with its Observations (and the Specimen, when new) in one transaction Bundle so they arrive atomically - see Bundles.
Update an existing report (e.g. set status to final once all results are in, or to amended after a correction)
PUT [base]/DiagnosticReport/[id]
If-Match: W/"3" # the ETag from your last read; 412 if it changed since
{
"resourceType": "DiagnosticReport",
"id": "[id]",
"meta": { "profile": [ "https://dhp.uz/fhir/core/StructureDefinition/uz-core-diagnostic-report" ] },
"status": "final",
...
}
See the CapabilityStatement for the full list of supported search parameters.