Page Comparison

Table of Contents

Specification

...

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

...

• 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"

Check signed content

Check that signed content contains all required fields and is equal to stored object

1. Decode signed content
2. Render requested medication request
3. Check that rendered and decoded data matches

Note! Medication request with intent plan and order has different structure

• Medical program is optional object in order
• Medical program is absent in plan

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."

...

...