...

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

  • Return 403 in case 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")

Headers

Наприклад:

• Content-Type:application/json

• Authorization:Bearer {{access_token}}

• API-key:{{secret}}

Request data validation

1. Validate digital signature

   1. ds.drfo == PRM.parties.tax_id where PRM.parties.id==PRM.employees.party_id where:

      1. PRM.employees.id==$.encounter.performer.identifier.value)

      2. OR PRM.employees.id==$.approval.granted_to.identifier.value ($.approvals.granted_resources.identifier.value==$.encounter_id AND $.approvals.access_level='write')

      3. OR PRM.employees.employee_type==MED_ADMIN

2. Compare signed_content to previously created content

   1. select encounter, select * from observations, conditions, immunizations, allergy_intolerances where context.identifier.value=encounter_id and compare to signed_content (do not include statuses to comparation, cancellation_reason and  explanatory_letter )

      1. in case of inconsistencies return "Submitted signed content does not correspond to previously created content"

3. Validate diagnoses still valid

   1. if ($.encounter.status!="entered_in_error") validate ($.conditions[?(@.verification_status=="entered_in_error")].id is not IN $.encounter.diagnoses[*].condition.identifier.value)

      1. in case of error "The condition can not be canceled while encounter is not canceled" 

4. Validate cancellation_reason

   1. $.cancellation_reason.coding[*].system == "eHealth/cancellation_reasons"

5. Validate status_reason if present

   1. $.status_reason.code is a value from the dictionary that is referenced in $.status_reason.coding[*].system

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

6. Validate entities are not canceled yet (status!= "entered_in_error")

   1. in case of error "Invalid transition"

7. Validate at least one entity in the request marked as "entered_in_error"

   1. in case of error "At least one entity should have status "entered_in_error""

8. Validate user performs action with an episode that belong to his legal entity

   1. ME.patient{patinet_id}.episodes{episode_id}.managing_organization==token.client_id

      1. in case of error return 422 "Managing_organization in the episode does not correspond to user`s legal_entity"

9. If entity is device_dispense:

   1. Check that status != “entered_in_error” and status != “completed”

      1. in case of error - return 409 error ('Device dispense in status <status> cannot be marked in error')

10. Validate reasons (eHealth/ICPC2/reasons dictionary)

    1. is case is_active = false return error 422 “value is not allowed in enum“

11. If there is Device in statusentered_in_error in the package:

    1. Check that there all related Device Associations within current Encounter and related to current Device are in the package and has entered_in_error status:

       • in case of error - return 409 error ('Can not mark in error Device related to active Device Association

       within the same Encounter')

    2. Check that there all related Detected Issues within current Encounter and related to current Device are in the package and has entered_in_error status:

       • in case of error - return 409 error ('Can not mark in error Device related to active Detected Issues

       within the same Encounter')

12. If there is Device Association in statusentered_in_error in the package:

    1. Check if there is a Device in DB that references the same encounter. If there is:

       1. Check that this Device is present in the package in status entered_in_error

          1. in case of error - return 409 error ('Can not mark in error Device Association related to Device, that is not marked in error' )

13. If there is Detected Issue in statusentered_in_error in the package:

    1. Check if there is a Device ($.subject) in DB that references the same encounter. If there is:

       1. Check that this Device is present in the package in status entered_in_error

          1. in case of error - return 409 error ('Can not mark in error Detected Issue related to Device, that is not marked in error' )

Validate legal entity

• Validate episode belongs to the legal entity where the current user works

  • ME.episode.managing_organization==token.client_id

    • in case of error return 409 "User is not allowed to perform actions with an episode that belongs to another legal entity"

...