ЕСОЗ - публічна документація
Get Care Plan activities
Purpose
This WS is designed to return all records about the activities related to the care plan in patient context
Specification
Link | |
Resource | /api/patients/{{patient_id}}/care_plans/{{care_plan_id}}/activities |
Scope | care_plan:read |
Components | Care plan |
Microservices | me/api-medical-events me/event-consumer me/kafka-consumer il/api(rpc) |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private/Internal | Public |
Logic
Returns all the activities related to the care plan in patient context
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id |
| String | MPI identifier of the patient |
|
care_plan_id |
| String | Care Plan identifier |
|
Filters
Filter | Values | Type | Description | Example |
---|---|---|---|---|
author |
| String | author of the activity |
|
kind |
| Enum | kind of the activity |
|
status |
| String | Care plan activity status |
|
page |
| Number | Page number |
|
page_size |
| Number | A limit on the number of objects to be returned, between 1 and 100. Default: 50 |
|
Dictionaries
eHealth/care_plan_activity_outcomes
eHealth/ICD10_AM/condition_codes
eHealth/care_plan_activity_goals
eHealth/care_plan_activity_cancel_reasons
eHealth/care_plan_activity_complete_reasons
eHealth/ucum/units
Request structure
Authorize
Verify the validity of access token
Return (401, 'Invalid access token') in case of validation fails
Verify that token is not expired
in case of error - return (401, 'Invalid access token')
Check user scopes in order to perform this action (scope = 'care_plan:read')
Return (403, 'Your scope does not allow to access this resource. Missing allowances: care_plan:read') in case of invalid scope(s)
Request to process the request using a token in the headers
Headers
Наприклад:
Content-Type:application/json
Authorization:Bearer {{access_token}}
API-key:{{mis_client_secret}}
Request data validation
Validate Patient
Get Patient identifier from the URL
Check it exists in DB
Return 404 ('not found') in case of error
Validate Care plan
Get Care plan identifier from the URL
Check it exists in DB
Return 404 ('not found') in case of error
Validate User
Extract user_id from token.
Check user has an active and approved employee from legal entity (token) for which one of the conditions is TRUE:
has an active Approval granted by the Patient on write or read the Care plan resource (care plan id from URL)
Return 403 ('Access denied') in case employee has no Approval on read or write
has an active declaration with the patient
Return 403 ('Access denied') in case there no active declaration with patient and none of other conditions is true
user belongs to the legal entity where the care_plans were created
Return 403 ('Access denied') in case employee belongs to another legal_entity and none of conditions above is true
Processing
Service logic
Service returns activity list within specified Care plan related to the patient:
Get activity list by Care plan identifier from care_plan_activities collection (MongoDB)
Validate data consistency:
Ensure that each requested activity in the list relates to requested Patient and Care Plan (from URL)
Return 404 ('not found') in case of error
Render a response according to specification
Response structure
See on Apiary
Example:
Post-processing processes
No
HTTP status codes
HTTP status code | Message | What caused the error |
---|---|---|
200 | Response |
|
401 |
|
|
403 |
|
|
404 |
|
|
ЕСОЗ - публічна документація