Table of Contents |
---|
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.
Specification
Authorization
Verify the validity of access token
in case of error - 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 = 'medication_request:unblock')
return 403 (“Your scope does not allow to access this resource. Missing allowances: medication_request:unblock”) in case of invalid scope(s)
Validations
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 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_system should be “MEDICATION_REQUEST_UNBLOCK_REASON”
in case of error return 422 error ("value is not allowed in enum")
Validate $.block_reason_code is a value from MEDICATION_REQUEST_UNBLOCK_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>")
Validate legal entity type
Validate type of legal entity which is related to blocking <> NHS. Using ops.medication_requests.(by $.id).block_legal_entity_id check in prm.legal_entities.type by id = block_legal_entity_id.
in case of error - return 422 ("It is not allowed to unblock medication request, which is blocked by NHS")
Service logic
Update Medication request in OPS DB:
set is_blocked = false
set block_reason_system = $.block_reason_system
set block_reason_code = $.block_reason_code
set block_reason = $.block_reason
set updated_by = user_id
set updated_at = now()
set block_legal_entity_id = legal entity id out of token
Send SMS for person
If Medication request has program with medical program setting
medication_request_notification_disabledrequest_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
Add new record in Event manager:
...