Table of Contents | ||||
---|---|---|---|---|
|
...
Specification
Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logic
Відміна направлення (Recalled)
This method must be used to recall existing Service Request. Method receives signed message (pkcs7) that consists of signed content, digital signature and signer public key. All signature fields will be validated (including signer certificate authority)
...
Please see Service request (Referral) state model and Dummy Recall Service Request for more details
Request structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
...
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')
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 mF_9.B5f-4.1JqM: {{access_token}}
api-key: aFBLVTZ6Z2dON1V{{secret}}
Request data validation
Validate legal entity
...
Validate that DS belongs to the requester of encounter
Check if service request based on Care plan if not match:Determine at least one of the user employees has an active approval on write this Care planin 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
Get current service request status
Check that status in ('active')
in case of error - return 409 error ('Service request in status %status% cannot be recalled')
Validate
...
recall reason
Validate $.status_reason is a value from eHealth/service_request_recall_reasons dictionary
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
...
Save signed content to media storage
Update service request status to Recalled (update also updated_at, updated_by)
Write record to status history
Send SMS to patient (if authentication_method_current == SMS, do NOT send sms in case performer is present in SR)
Send SMS to patient (if authentication_method_current == SMS)
Template - TBD
Async! Revoke all approvals made by this service request
if the service request is based on activity with quantity:
Recalculate and set remaining_quantity for the activity as described at PreQualify Service Request | Validate service request
Response structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
...