Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
Service logic
Update Medication request in OPS DB:
set is_blocked = trueset blocked_to = $.blocked_to OR $.medication_request.dispense_valid_to date + 23:59 time (in case blocked_to is absent in request)
set blocked_by_legal_entity_id = legal_entity_id (client_id) from token
set block_reason_code = $.block_reason_code
set block_reason = $.block_reason
set updated_by = user_id
set updated_at = now()
Send SMS for personIf Medication request has program with medical program settingmedication_request_notification_disabled=true, then don't send SMS.Else:Get authentication_method of person from MPIIf authentication_method == OTP, then send SMS to a person from Medication request:Generate SMS textget template fromblock_template_smsparameterenrich template with data from Medication request
Send SMS to a person
Return Medication request data with trimmed information about legal entity, division and employee
Add new record in Event manager:
...
Configuration parameters
No
Dictionaries
eHealth/SNOMED/anatomical_structure_administration_site_codes
eHealth/SNOMED/administration_methods
eHealth/SNOMED/dose_and_rate
eHealth/clinical_impression_patient_categories
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id | M | String | Medication Request identifier | d290f1ee-6c54-4b01-90e6-d701748f0851 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
...
in case of error - return 409 ("Only pharmacist can block medication request")
Validate legal_entity
If MR still blocked (blocked_to > now()) and MR.blocked_by_legal_entity_id is not null - check that match with client_id from token
in case of error - return 409 ("It is not allowed to block medication request that has been blocked from another legal entity")
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 not blocked, i.e. is_blocked = falsein case of error - return 409 ("Medication request is already blocked")
Validate block reason code
Validate $.block_reason_system should be “MEDICATION_REQUEST_BLOCK_REASON”
in case of error return 422 error ("value is not allowed in enum")
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 PHARMACIST_MEDICATION_REQUEST_BLOCK_REASON_CODES chart parameter for validated user
in case of error - return 422 ("Block reason code is not allowed for PHARMACIST")
Validate blocked_to
Validate $.blocked_to > now() (datetime)
in case of error - return 422 ("Blocked_to date should be greater than the current date")
Validate $.blocked_to <= $.medication_request.dispense_valid_to
in case of error - return 422 ("Blocked_to date should be equal to or less than the dispense validity end date")
Validate medical program
It must be allowed to block medication request only in case of such medication request is prescribed under specific medical program. In other cases it is prohibited to block medication request
Check that
$.medical_program_id
is in list of predefined programs in MEDICATION_REQUEST_BLOCK_ALLOWED_PROGRAMS config parameterin case of error - return 422 ("It is not allowed to block medication request under this medical program")
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 | ||
---|---|---|
| ||
|
...
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 | ||||
---|---|---|---|---|
|
...