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 unblock previously blocked Medication request with indicating block_reason and block_reason_code
Key points
Only authenticated and authorized user with appropriate scope can unblock Medication request.
Medication request can be unblocked only if it was previously blocked.
Medication request can be unblocked only from ‘ACTIVE' status.
Logic
Update Medication request in OPS DB:
set is_blocked = false
set block_reason_code = $.block_reason_code
set block_reason = $.block_reason
set updated_by = user_id
set updated_at = now()
Send SMS for person
If Medication request has program with medical program setting medication_request_notification_disabled = true, then don't send SMS.
Else:
Get authentication_method of person from MPI
If authentication_method == OTP, then send SMS to a person from Medication request:
Generate SMS text
get template from unblock_template_sms parameter
enrich template with data from Medication request
Send SMS to a person with text from template (“Ваш рецепт <request_number> розблоковано. Можете отримати ліки в аптеці”)
Add new record in Event manager:
field | value |
---|---|
|
|
|
|
| $.id |
| false |
| $.update_at |
| $.changed_by |
Configuration parameters
Access to the method is defined by the scope medication_request:unblock. Permission for this scope is determined by the System administrator by configuring scopes in the context of clients and roles.
Dictionaries
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id |
| String | Medication Request identifier | d290f1ee-6c54-4b01-90e6-d701748f0851 |
2 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
Request data validation
Validate request
Validate request using JSON schema
in case of error - return 422
Validate Medication request
Get Medication request identifier from the URL. Check Medication request exists in OPS DB
in case of error - return 404 ("Medication request does not exist")
Validate user
Medication Request unblocking is allowed for user if he has one of the following active and approved employee that:
is an author of the Medication request (medication_request.employee_id)
has an approval on write Care plan if Medication request based on the Care plan (medication_request.based_on)
is Med_Admin from legal entity where Medication Request is created
in case of error - return 409 ("Only an author, employee with approval on care plan or med_admin from the same legal entity can unblock medication request")
Validation transition
Get Medication request by $.id in OPS DB. Check that Medication request status = ‘ACTIVE’
in case of error - return 409 ("Medication request must be in active status")
Get Medication request by $.id in OPS DB. Check that Medication request is blocked, i.e. is_blocked = true
in case of error - return 409 ("Medication request is already unblocked")
Validate block reason code
Validate $.block_reason_code is a value from MEDICATION_REQUEST_BLOCK_REASON dictionary
in case of error - return 422 ("value is not allowed in enum")
Check that $.block_reason_code is present in <EMPLOYEE_TYPE>_MEDICATION_REQUEST_UNBLOCK_REASON_CODES chart parameter for validated user
in case of error - return 422 ("Block reason code is not allowed for <employee_type>")
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 | ||
---|---|---|
| ||
|
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 | 200 | Response |
| ||
3 | 401 | Invalid access token |
| ||
4 | 401 | Unauthorized | Помилка підтвердження | ||
5 | 403 | Your scope does not allow to access this resource. Missing allowances: medication_request:unblock |
| ||
6 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
7 | 404 | Medication request does not exist |
| ||
8 | 409 | Medication request is already unblocked |
| ||
9 | 409 | Medication request must be in active status | |||
10 | 409 | Only an author, employee with approval on care plan or med_admin from the same legal entity can unblock medication request | |||
11 | 422 | Block reason code is not allowed for <employee_type> | Request validation fails | ||
12 | 422 | Error | |||
13 | 422 | Value is not allowed in enum | |||
14 | Специфічні | ||||
15 | 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 | ||||
---|---|---|---|---|
|
...