Info |
---|
Info |
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
It can be processed in both sync and async methods depends on Server decision.
Service logic
Save signed content to media storage
Update activity status (update also updated_at, updated_by)
Set detail.status_reason
Configuration parameters
Care Plan dictionaries and configurable parameters_UA | Конфігураційні параметри
...
INNM_DOSAGE
Input parameters
Description of 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 |
|
3 | id |
| String | activity identifier |
|
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
Dummy Example:
Expand | ||
---|---|---|
| ||
|
Headers
...
HTTP status codes
Response code
HTTP Status code
Message
Internal name
Description
Базові
1000
404
Composition not found
COMPOSITION_NOT_FOUND_404
Не знайдено медичний висновок
401
Unauthorized
Помилка підтвердження
Специфічні
Key | Value | Mandatory | Description | Example | ||||
---|---|---|---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json | |||
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувача{{access_token}} | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 | 3 |
Request data validation
Describe the process of checking the input data transmitted in the request for compliance with the given rules and restrictions set in the API
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
...
title | Example |
---|
{{access_token}} | |||||
3 | API-key | {{mis_client_secret}} | API-key:{{mis_client_secret}} |
Request data validation
Validate legal entity
Extract client_id from token
Check legal entity status is ACTIVE
In case of error - return 409 (Legal entity must be ACTIVE)
Check legal entity type in ME_ALLOWED_TRANSACTIONS_LE_TYPES config parameter
in case of error - return 409 ('client_id refers to legal entity with type that is not allowed to create medical events transactions')
Validate User
Extract user_id from token.
Check user has an active and approved employee that:
has an active Approval granted by the Patient on write the Care plan resource (care plan id from URL)
Return 403 ('Access denied') in case employee has no Approval on write
Validate data consistency
Ensure that submitted activity relates to the Patient and Care Plan (from URL)
Return 404 (not found) in case of error
Validate Digital Sign
Check DS is valid and not expired
Validate that DS belongs to the user
Check that DRFO from DS and user's party.tax_id matches
in case of error - return 409 (“Signer DRFO doesn't match with requester tax_id“)
Validate status transition
Get activity by id
Check activity.detail.status: activity status should be changed according to activity status model.
Return 409 (Invalid activity status) in case of error
Check activity.detail.status in (in_progress, scheduled)
in case of error - return 409 ('Activity can be cancelled only if it has in_progress or scheduled status')
Validate status reason
Validate value in the field $.detail.status_reason, required
Validate field type is codeable concept
Check that codeable concept refers to the
eHealth/care_plan_activity_cancel_reasons
dictionaryValidate value within dictionary specified above
in case of error - return 422 ('value is not allowed in enum')
Validate related entities
if activity kind = medication_request:
Check there is no medication request requests in status
NEW
based on the activityin case of error - return 409 (Unable to cancel activity with new Medication Request requests).
Check there is no medication requests in status
ACTIVE
based on the activityin case of error - return 409 (Unable to cancel activity with active Medication requests).
if activity kind = service_request:
Check availability of service requests withstatus = active.If such service requests exist, then needs to check availability of service requests withprogram_processing_status:ifprogram_processing_statusis undefined (NULL), then return error 409 (Unable to cancel activity with Service requests in status <status value> and program processing status is NULL or not completed)ifprogram_processing_statusis defined, then needs to check thatprogram_processing_status = complete. Otherwise, return error 409 (Unable to cancel activity with Service requests in status <status value> and program processing status is NULL or not completed)
Check all related service requests in final status: completed, recalled or entered_in_error.
in case at least one is active - return error 409 (Unable to cancel activity with Service requests in active status)
Validate content
Signed content must match with activity in DB in order to be changed
Render activity from DB
Exclude $.detail.status_reason from signed content
Compare rendered activity and signed content
In case both object doesn't match - return 422 ('Signed content doesn't match with previously created activity')
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 | 201 | use payload from response | sync | ||
3 | 202 | use Get job details to get processing result. Response payload will be returned in the job details | async: default method | ||
4 | 401 | Invalid access token |
| ||
5 | 401 | Unauthorized | Помилка підтвердження | ||
6 | 403 | Access denied | invalid scope(s) | ||
7 | 403 | Your scope does not allow to access this resource. Missing allowances: care_plan:write | employee has no Approval on write | ||
8 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
9 | 404 | not found | The submitted activity is not related to the Patient Care Plan | ||
10 | 409 | Activity can be cancelled only if it has in_progress or scheduled status | |||
11 | 409 | client_id refers to legal entity that is not active | Validation error | ||
12 | 409 | client_id refers to legal entity with type that is not allowed to create medical events transactions | |||
13 | 409 | Invalid activity status | |||
14 | 409 | Legal entity must be ACTIVE | |||
15 | 409 | Signer DRFO doesn't match with requester tax_id | |||
16 | 409 | Unable to cancel activity with new Medication Request requests | |||
17 | 409 | Unable to cancel activity with active Medication requests | |||
18 | 409 | Unable to cancel activity with Service requests in active status | |||
19 | 422 | Signed content doesn't match with previously created activity | Validation error | ||
20 | Value is not allowed in enum | ||||
21 | Специфічні | ||||
22 | 422 | Only for active MPI record can be created medication request! |
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...