Required parameters are marked with "*"
Якщо інформації по відповідному параметру немає, потрібно зазначити: “API paragraph not found”.
Purpose*
This WS allows to cancel procedure in case they were entered in error.
Specification*
Logic*
This WS allows to cancel existing procedure and change its status to entered_in_error
in case of any mistake. The new correct procedure could be created instead. 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)
Important
Signed content of procedure must be equal to procedure stored in DB. See Get Procedure by search params
status_reason
andexplanatory_letter
(optional) must be added to signed content
Please see Cancel Procedure and [Dummy Cancel Procedure for more details
Request structure*
See on Apiary
Example:
Authorize*
Request to process the request using a token in the headers
Headers*
Наприклад:
Content-Type:application/json
Authorization:Bearer mF_9.B5f-4.1JqM
api-key:aFBLVTZ6Z2dON1V
Request data validation*
Validate token
Verify the validity of access token
Return 401 in case validation fails
Verify token is not expired
in case error return 401
Validate scopes
Check user scopes in order to perform this action (scope = 'procedure:write')
Return 403 in case invalid scope(s)
Validate legal entity
Validate procedure belongs to the legal entity where the current user works
ME.procedure.managing_organization==token.client_id
in case of error return 409 "Managing_organization in the procedure does not correspond to user`s legal_entity"
Validate patient
Validate patient is active
ME.patient.status=="active" and is_active=true
in case of error return "Patient is not active"
Validate User
Extract user_id and client_id from token
Get list of APPROVED employees with this user_id in current Legal Entity
Check that for user one of the conditions is TRUE:
user has an employee that specified as author of the procedure ($.procedure.recorded_by.identifier.value is in the list of APPROVED employees)
OR check that user has an employee which has approval granted by the patient with access_level:write for this procedure resource ($.approvals.granted_resources.identifier.value==$.procedure._id AND $.approvals.granted_to.identifier.value==PRM.employees.id AND $.approvals.access_level='write')
OR user has an employee which has MED_ADMIN employee type
otherwise, return error 409 "Employee is not performer of procedure, don't has approval or required employee type"
Request validation
Validate digital signature
ds.drfo == PRM.parties.tax_id where (PRM.parties.id==PRM.employees.party_id
where (PRM.employees.id==$.performer.identifier.value))in case of error - return 409 ("Signer DRFO doesn't match with requester tax_id")
Compare signed_content to previously created content
select procedure, select * from procedures context.identifier.value=procedure_id and compare to signed_content (do not include status, status_reason and explanatory_letter )
in case of inconsistencies return "Submitted signed content does not correspond to previously created content"
Validate status_reason is in dictionary eHealth/procedure_status_reasons
in case error return 422, "status_reason not in a dictionary eHealth/procedure_status_reasons"
Validate user performs action with procedure that belong to his legal entity
ME.patient{patinet_id}.procedures{procedure_id}.managing_organization==token.client_id
in case of error return 422 "Managing_organization in the procedure does not correspond to user`s legal_entity"
Processing*
Save signed_content to Media Storage
Set status `ENTERED_IN_ERROR` for procedure
Set cancellation_reason
Set explanatory_letter
Response structure*
See on Apiary
Example:
Post-processing processes*
API paragraph not found