Reject Medication Request

Specification

Purpose

This WS is designed to recall (cancel) previously created and signed Medication request (patch).

Input parameters (filters)

• id 
• reason

Authorize

1. Verify the validity of access token
2. Check user scope (scope = 'medication_request:reject') in order to perform this action
   1. In case error - generate 401 response

Digital signature

Decode content that is encrypted in an electronic digital signature.
Use Digital signature WS. Method checks digital signature and returns result.
See service specification

Validate DS

Extract user from token

• check if tax_id in DS = (SELECT parties.tax_id from party_users join parties on party_users.party_id=parties.id where party_users.user_id=$.user;)
  • in case error return error 422, "Invalid drfo in DS"

Validation transition

1. For info - status charts: Medication_request
2. Get Medication request status by $.id
3. Check status of medication request == ACTIVE
   
   1. if invalid - return 409 error (message: "Invalid status Medication request for reject transition!")'
4. Check connected medication dispenses medication_dispenses.status !== PROCESSED or NEW
   1. if invalid - return 409 error (message: "Medication request with connected processed medication dispenses can not be rejected")
5. Validate request using JSON schema
   1. In case validation fails - generate 422 error
6. Validate content. Check equality decoded signed content with previously created medication request, except, "Reason"!
   1. in case error return 422, "Signed content does not match the previously created content."

Update status

1. Update (Set values) Medication request
   1. status  =  REJECTED
   2. updated_by = user_id
   3. updated_at = timestamp

Send SMS for person 

1. Get authentication_method of MPI
2. If authentication_method == OTP -  send SMS:
   1. Generate text SMS (call Man method - templates rendering service with template "TEMPLATE_SMS_FOR_REJECT_MEDICATION_REQUEST".
   2. Sending SMS for MPI via service