Uzbekistan Digital Health Platform
0.12.0 - ci-build
Uzbekistan Digital Health Platform
0.12.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.12.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-careplan | Version: 0.12.0 | ||||
| Active as of 2026-10-30 | Computable Name: UZCoreCarePlan | ||||
Uzbekistan Core CarePlan profile, used to describe how one or more practitioners intend to deliver care to a patient over a period of time, such as a nursing patronage plan, a course of treatment or a sick leave case
UZ Core CarePlan describes how practitioners intend to care for a Patient or a Group over a period of time. It is a general profile for any plan on the Digital Health Platform: a nurse's home patronage visits, a course of physiotherapy, a sick leave case. A scenario-specific guide derives from it and adds its own identifiers, categories and extensions. The plan groups the requests for what is to be done (ServiceRequest, MedicationRequest, SupplyRequest and others) and links the events that record what was done, such as a Procedure. A Procedure, Observation or Immunization carried out under the plan points back to it from basedOn.
The elements below must always be present (mandatory) or must be supported when data is available (Must Support). Must Support means systems populate the element when they have the information and process it on receipt. See the formal profile for exact types, cardinalities, and bindings.
This profile adds no new mandatory cardinalities. Follow the base FHIR requirements: a status, an intent and a subject.
identifier);instantiatesCanonical, a PlanDefinition, ActivityDefinition or Questionnaire, or instantiatesUri);basedOn, replaces and partOf links to other plans;status (bound to request status) and intent (bound to CarePlan intent);category, title and description;subject (Patient or Group) and the Encounter the plan was created in;period and created;custodian, contributor and careTeam;addresses (Condition), supportingInfo and goal (Goal);activity: plannedActivityReference for the request, performedActivity for the event, and progress;note.1. Minimal plan. Only the three base elements are required. intent takes one of five codes: use plan for a plan a practitioner intends to follow and order for a plan that authorises its activities.
{
"resourceType": "CarePlan",
"meta": {
"profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-careplan"]
},
"status": "active",
"intent": "plan",
"subject": { "reference": "Patient/example-jasur" }
}
2. Describe the plan. category says what kind of plan it is, using a SNOMED CT descendant of 734163000 Care plan, here 773130005 Nursing care plan. custodian is who is responsible for the plan, and period how long it lasts.
{
"resourceType": "CarePlan",
"meta": {
"profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-careplan"]
},
"language": "uz",
"status": "active",
"intent": "plan",
"category": [{
"coding": [{ "system": "http://snomed.info/sct", "code": "773130005", "display": "Nursing care plan" }]
}],
"title": "Yangi tug'ilgan chaqaloq patronaji",
"subject": { "reference": "Patient/example-jasur" },
"period": { "start": "2015-06-20", "end": "2015-07-20" },
"created": "2015-06-22T09:00:00+05:00",
"custodian": { "reference": "PractitionerRole/example-patronage-nurse-role" }
}
3. Add the activities. Each activity is either planned or performed. A planned activity is a request, referenced from plannedActivityReference. A performed activity is the event that records it, in performedActivity; that element is a CodeableReference, so the reference sits one level deeper, under reference.
"activity": [
{
"plannedActivityReference": { "reference": "ServiceRequest/example-nursing-newborn-home-visit-request" }
},
{
"performedActivity": [{ "reference": { "reference": "Procedure/example-procedure" } }]
}
]
The full examples are the newborn nursing patronage plan and the therapeutic massage course.
See the Quick Start for API calls.
Usages:
You can also check for usages in the FHIR IG Statistics
Description Differentials, Snapshots, and other representations.
| Path | Status | Usage | ValueSet | Version | Source |
| CarePlan.status | Base | required | ServiceRequest status | 📍0.12.0 | This IG |
| CarePlan.intent | Base | required | CarePlan intent | 📍0.12.0 | This IG |
| CarePlan.category | Base | example | Care Plan Category | 📍5.0.0 | FHIR Std. |
| CarePlan.addresses | Base | example | SNOMED CT Clinical Findings | 📍5.0.0 | FHIR Std. |
| CarePlan.activity.performedActivity | Base | example | Care Plan Activity Performed | 📍5.0.0 | FHIR Std. |
| Id | Grade | Path(s) | Description | Expression |
This structure is derived from CarePlan
| Path | Status | Usage | ValueSet | Version | Source |
| CarePlan.status | Base | required | ServiceRequest status | 📍0.12.0 | This IG |
| CarePlan.intent | Base | required | CarePlan intent | 📍0.12.0 | This IG |
| Name | Flags | Card. | Type | Description & Constraints Filter:  | ||||
|---|---|---|---|---|---|---|---|---|
  CarePlan |
0..* | CarePlan(5.0.0) | Healthcare plan for patient or group | |||||
  id |
0..1 | id | Logical id of this artifact | |||||
 meta |
0..1 | Meta | Metadata about the resource | |||||
| implicitRules |
0..1 | uri | A set of rules under which this content was created | |||||
| language |
0..1 | code | Language of the resource content Binding: AllLanguages (required): IETF language tag for a human language
| |||||
| text |
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 | |||||
| contained |
0..* | Resource | Contained, inline Resources | |||||
 extension |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
 modifierExtension |
0..* | Extension | Extensions that cannot be ignored Constraints: ext-1 | |||||
| identifier |
0..* | Identifier | External Ids for this plan | |||||
| instantiatesCanonical |
0..* | canonical(UZ Core PlanDefinition(0.12.0) | UZ Core Questionnaire(0.12.0) | Measure | UZ Core ActivityDefinition(0.12.0) | OperationDefinition) | Instantiates FHIR protocol or definition | |||||
| instantiatesUri |
0..* | uri | Instantiates external protocol or definition | |||||
 basedOn |
0..* | Reference(UZ Core CarePlan(0.12.0) | UZ Core ServiceRequest(0.12.0) | RequestOrchestration | NutritionOrder) | Fulfills plan, proposal or order | |||||
| replaces |
0..* | Reference(UZ Core CarePlan(0.12.0)) | CarePlan replaced by this CarePlan | |||||
| partOf |
0..* | Reference(UZ Core CarePlan(0.12.0)) | Part of referenced CarePlan | |||||
| status |
1..1 | code | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ServiceRequestStatusVS (0.12.0) (required) | |||||
| intent |
1..1 | code | proposal | plan | order | option | directive Binding: CarePlanIntentVS (0.12.0) (required) | |||||
| category |
0..* | CodeableConcept | Type of plan Binding: CarePlanCategory (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc. | |||||
| title |
0..1 | string | Human-friendly name for the care plan | |||||
| description |
0..1 | string | Summary of nature of plan | |||||
| subject |
1..1 | Reference(UZ Core Patient(0.12.0) | UZ Core Group(0.12.0)) | Who the care plan is for | |||||
| encounter |
0..1 | Reference(UZ Core Encounter(0.12.0)) | The Encounter during which this CarePlan was created | |||||
| period |
0..1 | Period | Time period plan covers | |||||
| created |
0..1 | dateTime | Date record was first recorded | |||||
| custodian |
0..1 | Reference(UZ Core Patient(0.12.0) | UZ Core Practitioner(0.12.0) | UZ Core PractitionerRole(0.12.0) | UZ Core Device(0.12.0) | UZ Core RelatedPerson(0.12.0) | UZ Core Organization(0.12.0) | CareTeam) | Who is the designated responsible party | |||||
| contributor |
0..* | Reference(UZ Core Patient(0.12.0) | UZ Core Practitioner(0.12.0) | UZ Core PractitionerRole(0.12.0) | UZ Core Device(0.12.0) | UZ Core RelatedPerson(0.12.0) | UZ Core Organization(0.12.0) | CareTeam) | Who provided the content of the care plan | |||||
| careTeam |
0..* | Reference(CareTeam) | Who's involved in plan? | |||||
| addresses |
0..* | CodeableReference(UZ Core Condition(0.12.0)) | Health issues this plan addresses Binding: SNOMEDCTClinicalFindings (example): Codes that describe the health issues this plan addresses. | |||||
| supportingInfo |
0..* | Reference(Resource) | Information considered as part of plan | |||||
| goal |
0..* | Reference(UZ Core Goal(0.12.0)) | Desired outcome of plan | |||||
 activity |
0..* | BackboneElement | Action to occur or has occurred as part of plan | |||||
 id |
0..1 | string | Unique id for inter-element referencing | |||||
| extension |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
| modifierExtension |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |||||
| performedActivity |
0..* | CodeableReference(UZ Core Procedure(0.12.0) | UZ Core Immunization(0.12.0) | UZ Core MedicationAdministration(0.12.0) | UZ Core MedicationDispense(0.12.0) | UZ Core Observation(0.12.0) | UZ Core DiagnosticReport(0.12.0) | UZ Core Encounter(0.12.0) | UZ Core SupplyDelivery(0.12.0) | NutritionIntake | Communication) | Event that was performed as part of this activity Binding: CarePlanActivityPerformed (example): Identifies the results of the activity. | |||||
| progress |
0..* | Annotation | Comments about the activity status/progress | |||||
 plannedActivityReference |
0..1 | Reference(Appointment | CommunicationRequest | DeviceRequest | UZ Core MedicationRequest(0.12.0) | NutritionOrder | Task | UZ Core ServiceRequest(0.12.0) | VisionPrescription | RequestOrchestration | UZ Core ImmunizationRecommendation(0.12.0) | UZ Core SupplyRequest(0.12.0)) | Request for the planned activity | |||||
| note |
0..* | Annotation | Comments about the plan | |||||
| Documentation for this format | ||||||||
| Path | Status | Usage | ValueSet | Version | Source |
| CarePlan.language | Base | required | All Languages | 📍5.0.0 | FHIR Std. |
| CarePlan.status | Base | required | ServiceRequest status | 📍0.12.0 | This IG |
| CarePlan.intent | Base | required | CarePlan intent | 📍0.12.0 | This IG |
| CarePlan.category | Base | example | Care Plan Category | 📍5.0.0 | FHIR Std. |
| CarePlan.addresses | Base | example | SNOMED CT Clinical Findings | 📍5.0.0 | FHIR Std. |
| CarePlan.activity.performedActivity | Base | example | Care Plan Activity Performed | 📍5.0.0 | FHIR Std. |
| Id | Grade | Path(s) | Description | Expression |
This structure is derived from CarePlan
Summary
Must-Support: 26 elements
Structures
This structure refers to these other structures:
Key Elements View
| Path | Status | Usage | ValueSet | Version | Source |
| CarePlan.status | Base | required | ServiceRequest status | 📍0.12.0 | This IG |
| CarePlan.intent | Base | required | CarePlan intent | 📍0.12.0 | This IG |
| CarePlan.category | Base | example | Care Plan Category | 📍5.0.0 | FHIR Std. |
| CarePlan.addresses | Base | example | SNOMED CT Clinical Findings | 📍5.0.0 | FHIR Std. |
| CarePlan.activity.performedActivity | Base | example | Care Plan Activity Performed | 📍5.0.0 | FHIR Std. |
| Id | Grade | Path(s) | Description | Expression |
Differential View
This structure is derived from CarePlan
| Path | Status | Usage | ValueSet | Version | Source |
| CarePlan.status | Base | required | ServiceRequest status | 📍0.12.0 | This IG |
| CarePlan.intent | Base | required | CarePlan intent | 📍0.12.0 | This IG |
Snapshot ViewView
| Name | Flags | Card. | Type | Description & Constraints Filter: | ||||
|---|---|---|---|---|---|---|---|---|
| CarePlan |
0..* | CarePlan(5.0.0) | Healthcare plan for patient or group | |||||
| id |
0..1 | id | Logical id of this artifact | |||||
| meta |
0..1 | Meta | Metadata about the resource | |||||
| implicitRules |
0..1 | uri | A set of rules under which this content was created | |||||
| language |
0..1 | code | Language of the resource content Binding: AllLanguages (required): IETF language tag for a human language
| |||||
| text |
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 | |||||
| contained |
0..* | Resource | Contained, inline Resources | |||||
| extension |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
| modifierExtension |
0..* | Extension | Extensions that cannot be ignored Constraints: ext-1 | |||||
| identifier |
0..* | Identifier | External Ids for this plan | |||||
| instantiatesCanonical |
0..* | canonical(UZ Core PlanDefinition(0.12.0) | UZ Core Questionnaire(0.12.0) | Measure | UZ Core ActivityDefinition(0.12.0) | OperationDefinition) | Instantiates FHIR protocol or definition | |||||
| instantiatesUri |
0..* | uri | Instantiates external protocol or definition | |||||
| basedOn |
0..* | Reference(UZ Core CarePlan(0.12.0) | UZ Core ServiceRequest(0.12.0) | RequestOrchestration | NutritionOrder) | Fulfills plan, proposal or order | |||||
| replaces |
0..* | Reference(UZ Core CarePlan(0.12.0)) | CarePlan replaced by this CarePlan | |||||
| partOf |
0..* | Reference(UZ Core CarePlan(0.12.0)) | Part of referenced CarePlan | |||||
| status |
1..1 | code | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ServiceRequestStatusVS (0.12.0) (required) | |||||
| intent |
1..1 | code | proposal | plan | order | option | directive Binding: CarePlanIntentVS (0.12.0) (required) | |||||
| category |
0..* | CodeableConcept | Type of plan Binding: CarePlanCategory (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc. | |||||
| title |
0..1 | string | Human-friendly name for the care plan | |||||
| description |
0..1 | string | Summary of nature of plan | |||||
| subject |
1..1 | Reference(UZ Core Patient(0.12.0) | UZ Core Group(0.12.0)) | Who the care plan is for | |||||
| encounter |
0..1 | Reference(UZ Core Encounter(0.12.0)) | The Encounter during which this CarePlan was created | |||||
| period |
0..1 | Period | Time period plan covers | |||||
| created |
0..1 | dateTime | Date record was first recorded | |||||
| custodian |
0..1 | Reference(UZ Core Patient(0.12.0) | UZ Core Practitioner(0.12.0) | UZ Core PractitionerRole(0.12.0) | UZ Core Device(0.12.0) | UZ Core RelatedPerson(0.12.0) | UZ Core Organization(0.12.0) | CareTeam) | Who is the designated responsible party | |||||
| contributor |
0..* | Reference(UZ Core Patient(0.12.0) | UZ Core Practitioner(0.12.0) | UZ Core PractitionerRole(0.12.0) | UZ Core Device(0.12.0) | UZ Core RelatedPerson(0.12.0) | UZ Core Organization(0.12.0) | CareTeam) | Who provided the content of the care plan | |||||
| careTeam |
0..* | Reference(CareTeam) | Who's involved in plan? | |||||
| addresses |
0..* | CodeableReference(UZ Core Condition(0.12.0)) | Health issues this plan addresses Binding: SNOMEDCTClinicalFindings (example): Codes that describe the health issues this plan addresses. | |||||
| supportingInfo |
0..* | Reference(Resource) | Information considered as part of plan | |||||
| goal |
0..* | Reference(UZ Core Goal(0.12.0)) | Desired outcome of plan | |||||
| activity |
0..* | BackboneElement | Action to occur or has occurred as part of plan | |||||
| id |
0..1 | string | Unique id for inter-element referencing | |||||
| extension |
0..* | Extension | Additional content defined by implementations Constraints: ext-1 | |||||
| modifierExtension |
0..* | Extension | Extensions that cannot be ignored even if unrecognized Constraints: ext-1 | |||||
| performedActivity |
0..* | CodeableReference(UZ Core Procedure(0.12.0) | UZ Core Immunization(0.12.0) | UZ Core MedicationAdministration(0.12.0) | UZ Core MedicationDispense(0.12.0) | UZ Core Observation(0.12.0) | UZ Core DiagnosticReport(0.12.0) | UZ Core Encounter(0.12.0) | UZ Core SupplyDelivery(0.12.0) | NutritionIntake | Communication) | Event that was performed as part of this activity Binding: CarePlanActivityPerformed (example): Identifies the results of the activity. | |||||
| progress |
0..* | Annotation | Comments about the activity status/progress | |||||
| plannedActivityReference |
0..1 | Reference(Appointment | CommunicationRequest | DeviceRequest | UZ Core MedicationRequest(0.12.0) | NutritionOrder | Task | UZ Core ServiceRequest(0.12.0) | VisionPrescription | RequestOrchestration | UZ Core ImmunizationRecommendation(0.12.0) | UZ Core SupplyRequest(0.12.0)) | Request for the planned activity | |||||
| note |
0..* | Annotation | Comments about the plan | |||||
| Documentation for this format | ||||||||
| Path | Status | Usage | ValueSet | Version | Source |
| CarePlan.language | Base | required | All Languages | 📍5.0.0 | FHIR Std. |
| CarePlan.status | Base | required | ServiceRequest status | 📍0.12.0 | This IG |
| CarePlan.intent | Base | required | CarePlan intent | 📍0.12.0 | This IG |
| CarePlan.category | Base | example | Care Plan Category | 📍5.0.0 | FHIR Std. |
| CarePlan.addresses | Base | example | SNOMED CT Clinical Findings | 📍5.0.0 | FHIR Std. |
| CarePlan.activity.performedActivity | Base | example | Care Plan Activity Performed | 📍5.0.0 | FHIR Std. |
| Id | Grade | Path(s) | Description | Expression |
This structure is derived from CarePlan
Summary
Must-Support: 26 elements
Structures
This structure refers to these other structures:
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; encode the | separator between a coding system and code as %7C.
Read by server id
GET [base]/CarePlan/[id]
Search care plans
GET [base]/CarePlan?identifier=https://mis.dmed.uz%7CCP-2015-000123
GET [base]/CarePlan?patient=Patient/[id]&status=active
GET [base]/CarePlan?patient=Patient/[id]&category=http://snomed.info/sct%7C773130005
GET [base]/CarePlan?encounter=Encounter/[id]
GET [base]/CarePlan?activity-reference=ServiceRequest/[id]
GET [base]/CarePlan?date=ge2026-01-01
Create
POST [base]/CarePlan
{
"resourceType": "CarePlan",
"meta": {
"profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-careplan"]
},
"status": "active",
"intent": "plan",
"subject": { "reference": "Patient/[id]" },
"activity": [{ "plannedActivityReference": { "reference": "ServiceRequest/[id]" } }]
}
Update (for example, to add an activity or complete the plan): send the complete resource with PUT [base]/CarePlan/[id] and an If-Match header carrying the version you read, so a concurrent change is not overwritten.
The CapabilityStatement lists the supported search parameters, including based-on, part-of, custodian, care-team, condition, goal, intent and instantiates-canonical.