Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel3

...

Request to process the request using a token in the headers

Headers

Наприклад:

  • Content-Type:application/json

  • Authorization:Bearer: {{access_token}}

  • api-key: {{secret}}

...

  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

...