ЕСОЗ - публічна документація
Care plan data model_EN
- 1 FHIR description
- 2 Schema
- 3 eHealth description
- 3.1 Care plan
- 3.1.1 Care plan document
- 3.2 Activities
- 3.2.1 Activity document
- 3.2.2 Detail document
- 3.1 Care plan
- 4 Example
FHIR description
Schema
eHealth description
Care plan
Collection name: care_plans
This collection used to store care plan document without activity documents.
Care plan document
Name | Type | M/O | Description and constraints | HL7 vs eHealth comparison result |
---|---|---|---|---|
id | string | M | System identifier of Care plan (ObjectID) | Doesn't comply with FHIR |
based_on | O | Reference on parent Care plan | Ok | |
part_of | O | Reference on another Care plan | Ok | |
category | M | Category of the care plan. Fetches from the dictionary | Ok | |
title | string | M | Title of the care plan | Ok |
description | string | O | Description of the care plan | Ok |
period | {Period} | M | Period when care plan starts and ends | Ok |
supporting_info | O | Reference on supporting medical events. | Ok | |
note | string | O | Comments, notes about care plan | Doesn't comply with FHIR |
requisition | string | M | Hashed value of human-readable care plan number | Doesn't comply with FHIR |
managing_organization | M | Reference on legal_entity | Doesn't comply with FHIR | |
intent | string | M | By default is order | Ok |
encounter | M | Reference on encounter with main diagnosis | Ok | |
addresses | M | Condition code. Fetches from the dictionary | Doesn't comply with FHIR (datatype) | |
status | string | M | Status of care plan | Ok |
status_reason | O | Reason of changing a status | Doesn't comply with FHIR | |
status_history | M | Care plan status change history | Doesn't comply with FHIR | |
subject | string | M | Hashed patient_id | Doesn't comply with FHIR (datatype) |
author | M | Reference on care plan creator employee | Ok | |
contributor | O | References on care plan contributor employees | Ok | |
terms_of_service | M | Providing condition of care plan. Fetches from the dictionary | Doesn't comply with FHIR | |
inserted_at | timestamp | M | Datetime when care plan was created | Doesn't comply with FHIR |
inserted_by | string | M | Identifier on the user created the care plan | Doesn't comply with FHIR |
updated_at | timestamp | M | Datetime when care plan was last updated | Doesn't comply with FHIR |
updated_by | string | M | Identifier on the user last updated the care plan | Doesn't comply with FHIR |
signed_content_links | [string] | M | Array with links on signed content in media storage. | Doesn't comply with FHIR |
Activities
Collection name: activities
This collection is used to store activities only with link on their Care plan
Activity document
Activity should be described with detail
attribute only, without using reference
attribute.
Name | Type | M/O | Description and constraints | HL7 vs eHealth comparison result |
---|---|---|---|---|
id | string | M | System identifier of the activity. Unique within the Care plan | Doesn’t comply with FHIR |
care_plan | M | Reference on the Care plan to which activity has been related. | Doesn’t comply with FHIR | |
author | M | Reference on activity creator employee | Doesn’t comply with FHIR CarePlan (matches with ActivityDefinition) | |
signed_content_links | [string] | M | Array with links on signed content in media storage. | Doesn't comply with FHIR |
outcome_reference | O | Reference on resources which represents result of the activity. For medication requests there are medication dispenses, for service requests - procedures, encounters, diagnostic_reports. And for device requests - there are device dispenses | Ok | |
outcome_codeable_concept | O | Descriptions of the activity result. Fetches from a dictionary. | Ok | |
inserted_at | timestamp | M | Datetime when care plan was created | Doesn't comply with FHIR |
inserted_by | string | M | Identifier on the user created the care plan | Doesn't comply with FHIR |
updated_at | timestamp | M | Datetime when care plan was last updated | Doesn't comply with FHIR |
updated_by | string | M | Identifier on the user last updated the care plan | Doesn't comply with FHIR |
detail | M | Summary of the care plan activity | Ok |
Detail document
Name | Type | M/O | Description and constraints | HL7 vs eHealth comparison result |
---|---|---|---|---|
kind | string | M | Type of the activity. Allowed values: | Ok |
reason_code | O | Diagnoses. May be a few, fetches from the | Ok | |
reason_reference | O | References on conditions/oservations/diagnostic_reports with diagnoses. | Ok | |
goal | O | A goal of the activity. Fetches from a dictionary. | Doesn't comply with FHIR (type) | |
status | string | M | Status of the activity. | Ok |
status_reason | O | Reason of the activity status change. Fetches from a dictionary. | Ok | |
quantity | O | Quantity of required medications (MR) or procedures e.t.c. (SR) | Ok | |
scheduled_timing sheduled_period scheduted_string | {Timing} {Period} string | O | One of these fields is allowed, another should be forbidden. Describes a period, timing or frequency upon which the activity is to occur. | Ok |
location | O | Reference on the performer’s division | Ok | |
performer | O | Reference on employee who will perform the activity. | Ok | |
product_reference product_codeable_concept | M О О | Required. If Field For kind device_request one of these fields is allowed, another should be forbidden - product_reference or product_codeable_concept:
| Ok | |
daily_amount | O | Quantity of medication, procedures to be consumed a day | Ok | |
remaining_quantity | O | Remaining quantity medication (procedures e.t.c. fot SR) allowed to medication dispense. It calculates as difference between detail.quantity and count of corresponding references in activity.outcome_reference??? | Ok | |
description | string | O | Description of the activity | Ok |
do_not_perform | bool | M | By default is false | Ok |
program | O | Reference on medical program resource | Doesn't comply with FHIR |
Example
ЕСОЗ - публічна документація