Info |
---|
Note |
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Info |
---|
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method document
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Purpose
This WS is designed to return all records about the activities related to the care plan in patient context
Logic
Returns all the activities related to the care plan in patient context
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
Configuration parameters
Description of the configuration parameters that are used when processing a request in the systemN/A
Dictionaries
eHealth/care_plan_activity_outcomes
...
eHealth/care_plan_activity_complete_reasons
eHealth/ucum/units
Input
...
parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | patient_id |
| String | MPI identifier of the patient |
|
2 | care_plan_id |
| String | Care Plan identifier |
|
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
...
title | Example |
---|
...
Headers
...
Key
...
Value
...
Mandatory
...
Expand | ||
---|---|---|
|
...
|
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer {{access_token}}
...
Authorization:Bearer {{access_token}}
...
API-key
...
{{mis_client_secret}}
...
API-key:{{mis_client_secret}}
...
Headers
Request data validation
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
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
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST APIN/A
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)Description of the REST API response structure, example
Expand | |||||
---|---|---|---|---|---|
| |||||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | Базові | ||||||||||
2 | 200 | Response |
| ||||||||
3 | 401 | Invalid access token | Invalid access token | 4 | 401 | Unauthorized | Помилка підтвердження | 5Invalid access token | |||
4 | 403 | Access denied | Employee has no Approval on read or write | ||||||||
65 | 403 | Your scope does not allow to access this resource. Missing allowances: care_plan:read | Invalid scope(s) | ||||||||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | ||||||
8 | 404 | 6 | 404 | Not found | Request data validation error | ||||||
97 | Специфічні | ||||||||||
10 | 422 | Only for active MPI record can be created medication request! | 8 |
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical N/A
Technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...