...

• Verify the validity of access token

  • Return (401, 'unauthorized') in case of validation fails

• Verify that token is not expired

  • in case of error - return (401, 'unauthorized')

• Check user scopes in order to perform this action (scope = 'service_request:write')

  1. Return (403, 'invalid scopes') in case of invalid scope(s)

• If BLOCK_UNVERIFIED_PARTY_USERS is true, then check party's data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at > current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):

  • in case not match - return 403 ("Access denied. Party is not verified")

• If BLOCK_DECEASED_PARTY_USERS is true, check that party is not deceased (party_verification record does not equal to: dracs_death_verification_status = VERIFIED and dracs_death_verification_reason = MANUAL_CONFIRMED):

  • in case of error - return 403 ("Access denied. Party is deceased")

Request to process the request using a token in the headers

Headers

Наприклад:

• Content-Type:application/json

• Authorization:Bearer: {{access_token}}

• api-key: {{secret}}

...

1. Validate that DS belongs to the requester of encounter

2. Check if service request based on Care plan if not match:

   1. Determine at least one of the user employees has an active approval on write this Care plan 

      1. in case of error - return 409 ('Employees related to this party_id not in current MSP')

3.1. Determine the party_id associated with requester ($.requester.identifier.value)

...

Covered by DS validation (see Validate digital signature p.2)

Validate user

Recalling a Service Request is allowed for user if he has one of the following active and approved employee that:

• is an Employee from legal entity where Service Request is created

  • in case of error - return 409 ("Only an employee from legal entity where service request is created can recall service request")

Validate transition

Only active service request can be recalled

1. Get current service request status

   1. Check that status in ('active')

      1. in case of error - return 409 error ('Service request in status %status% cannot be recalled')

Validate

...

recall reason

1. Validate $.status_reason is a value from eHealth/service_request_recall_reasons dictionary

   1. in case of error - return 422 ("value is not allowed in enum")

Validate content

Signed content must match with service request in DB in order to be recalled

...

1. Save signed content to media storage

2. Update service request status to Recalled (update also updated_at, updated_by)

3. Write record to status history

4. Send SMS to patient (if authentication_method_current == SMS, do NOT send sms in case performer is present in SR)

5. Send SMS to patient (if authentication_method_current == SMS)

   1. Template - TBD

6. Async! Revoke all approvals made by this service request

7. if the service request is based on activity with quantity:

   1. Recalculate and set remaining_quantity for the activity as described at PreQualify Service Request | Validate service request

Response structure

See on Apiary

...