REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
Properties of a REST API method document
Purpose
This WS is designed to resend SMS to person with Medication request info.
Key points
Only authenticated and authorized user with an appropriate scope can resend Medication request info.
Medication request info can be resend only to a person with verification_type = OTP.
Medication request info can be resend only for medication requests with intent order.
Medication request info can be resend only from ‘ACTIVE' status.
Logic
Call SMS timeout procedure to check if resending is allowed using:
MR_MAX_ATTEMPTS_COUNT as MAX_ATTEMPTS_COUNT;
MR_SEND_TIMEOUT as SEND_TIMEOUT;
"medication_request" as entity_name;
medication_request_id as entity_id.
In case of error - return 429 ("Sending SMS timeout. Try later. Next attempt will be available at <attempts.oldest.value + SEND_TIMEOUT>").
Generate SMS text
get template from sign_template_sms parameter;
enrich template with data from Medication request.
Send SMS to a person.
Процеси роботи з випискою електронних рецептів
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
MEDICATION_REQUEST_BLOCK_REASON
MEDICATION_REQUEST_INTENT
MEDICATION_REQUEST_CATEGORY
MEDICATION_REQUEST_PRIORITY
eHealth/SNOMED/additional_dosage_instructions
eHealth/SNOMED/anatomical_structure_administration_site_codes
eHealth/SNOMED/route_codes
eHealth/SNOMED/administration_methods
eHealth/SNOMED/dose_and_rate
eHealth/ICD10_AM/condition_codes
eHealth/ICPC2/condition_codes
ADDRESS_TYPE
SETTLEMENT_TYPE
STREET_TYPE
PHONE_TYPE
DIVISION_TYPE
POSITION
MEDICATION_FORM
MEDICATION_UNIT
eHealth/clinical_impression_patient_categories
LICENSE_TYPE
FUNDING_SOURCE
MR_BLANK_TYPES
MEDICATION_REQUEST_REJECT_REASON
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id |
| String | Medication Request identifier. Required. | a89f6a26-4221-4597-a1d2-542d5e40b565 |
2 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Headers
Key | Value | Mandatory | Description | Example | |
---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json |
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 |
3 |
Request data validation
Validate Medication request
Get Medication request identifier from the URL. Check Medication request exists in OPS DB
in case of error - return 404 ('Not found').
Validate intent
Get Medication request by $.id in OPS DB. Check that Medication request intent = ‘order’
if invalid - return 409 ("For medication request plan information cannot be resent").
Validate status
Get Medication request by $.id in OPS DB. Check that Medication request status = ‘ACTIVE’
if invalid - return 409 ("Invalid status Medication request for resend action!").
Validate medical program
Get Medication request by $.id in OPS DB. If medical program exists in the medication request:
Get medical program settings by $.medical_program.id.
Check medication_request_notification_disabled = false or null/absent
if true - return 409 ("Notifications are not allowed for the medical program!").
Validate verification code
Get Medication request by $.id in OPS DB. Check that Medication request verification code is not null
if invalid - return 403 ("Can't resend Medication request without verification code!").
Validate person
Get authentication_method of person in MPI DB. Check that persons authentication_method == ‘OTP’ or ‘THIRD_PERSON’ with authentication_method == ‘OTP’
if invalid - return 409 ("Person or third person has no OTP auth method").
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
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 | 200 | Response |
| ||
3 | 401 | Invalid access token |
| ||
4 | 401 | Unauthorized | Помилка підтвердження | ||
5 | 403 | Can't resend Medication request without verification code! |
| ||
6 | 403 | Your scope does not allow to access this resource. Missing allowances: medication_request:resend | |||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
8 | 404 | Not found |
| ||
9 | 409 | For medication request plan information cannot be resent. |
| ||
10 | 409 | Invalid status Medication request for resend action! | |||
11 | 409 | Notifications are not allowed for the medical program! | |||
12 | 409 | Person or third person has no OTP auth method. | |||
13 | |||||
14 | 429 | Sending SMS timeout. Try later. Next attempt will be available at <attempts.oldest.value + SEND_TIMEOUT> | |||
15 | |||||
16 | |||||
17 | |||||
18 | Специфічні | ||||
19 | 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