...

1. Validate digital signature 

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

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. If there is Device Dispense in statusentered_in_error in the package:

   1. Check that status of the Device Dispense in DB != “completed”

      1. in case of error - return 409 error ('Device Dispense in status completed cannot be marked in error')

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

   1. Check that there is also related Device Association in statusall 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

      Device Association

      • Detected Issues

      within the same Encounter')

10. 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' )

11. 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' )

Request processing

1. Save signed_content to Media Storage

2. Set status `entered_in_error` for objects, submitted with status `entered_in_error`

3. Set cancellation_reason

4. Set explanatory_letter 

5. Deactivate corresponding diagnoses in the episode in case encounter was entered_in_error

   1. Find episode where id == encouners{encounter_id}.context.identifier.value

   2. Find record in episodes{episode_id}.diagnoses_hstr.evidence.identifier.value==encounter_id

   3. Set is_active = false for this record

6. Replace current diagnoses 

   1. Set in episodes.current_diagnoses the last record from diagnoses_history where is_active==true