Uzbekistan Digital Health Platform - Integrations, published by Uzinfocom LLC. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/vadi2/DHP-integrations-temp/ and changes regularly. See the Directory of published versions

Document Categories

Joriy sahifa uchun tarjima sahifasi mavjud emas, shuning uchun u standarttilida ko‘rsatildi

Document categories and identifiers

DHP uses several mechanisms to classify and identify clinical documents:

• Category codes - the main way to identify types of resources
• External identifiers - link to official form or template numbers when present
• Instance identifiers - unique UUIDs to distinguish individual document instances

graph TB
    Doc[Document]
    Doc --> Cat[.category<br/>What type?]
    Doc --> Form[.identifier form-number<br/>Which form?]
    Doc --> Inst[Bundle.identifier<br/>Which version?]
    Doc --> Comp[Composition.identifier<br/>Which composition?]

Category codes

Category codes are the primary method for identifying document types. Use Composition.category or CarePlan.category with codes from DocumentCategoryCS.

{
  "resourceType": "Composition",
  "category": [{
    "coding": [{
      "system": "https://terminology.dhp.uz/fhir/integrations/CodeSystem/document-category-cs",
      "code": "form-094",
      "display": "Certificate of disability due to intoxication"
    }]
  }]
}

Categories are based on Ministry of Health standardized forms.

External identifiers

When a document has an official form number or template number, they are recorded in .identifier. Not all documents have external identifiers - use them when present.

Form numbers

Official form numbers (e.g., Form 094):

{
  "identifier": [{
    "system": "https://dhp.uz/fhir/core/sid/doc/uz/form-number",
    "value": "094"
  }]
}

Template numbers

Template identifiers (distinct from form numbers):

{
  "identifier": [{
    "system": "https://dhp.uz/fhir/core/sid/doc/uz/template-number",
    "value": "094"
  }]
}

Instance identifiers

Individual instances are distinguished using UUID format in .identifier.

For FHIR document Bundles, two identifiers are used:

• Bundle.identifier - unique per document instance, never reused
• Composition.identifier - consistent across all documents derived from the same composition

When a document is updated (e.g., a form is created and later modified), Composition.identifier stays the same while Bundle.identifier will be different between versions. This allows systems to recognize that two document bundles represent different versions of the same underlying clinical information.

{
  "resourceType": "Bundle",
  "identifier": {
    "system": "urn:ietf:rfc:3986",
    "value": "urn:uuid:550e8400-e29b-41d4-a716-446655440000"
  },
  "entry": [{
    "resource": {
      "resourceType": "Composition",
      "identifier": {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:uuid:661f9511-f30c-52e5-b827-557766551111"
      }
    }
  }]
}

For standalone resources (e.g., CarePlan), use the resource's own .identifier.

Summary

Example

See Form 095 CarePlan Example for a complete example showing category, form number, and instance identifier.