Purpose

This method allows to get contexts of Procedure in order to create approval on episode and receive access to other medical events.

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

1. Signed content of procedure must be equal to procedure stored in DB. See Get Procedure by search params

2. status_reason and explanatory_letter (optional) must be added to signed content

Please see Cancel Procedure and [Dummy Cancel Procedure for more details

Specification

...

Logic

Service returns contexts (episode and origin_episode), procedure based on:

• Get Procedure object byprocedure_id from procedures (MongoDB)

• Get procedure.encounter.identifier from Procedure object

• Call https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17049388285 :

  • Get Encounter objectby procedure.encounter.identifier (procedure.encounter.identifier = encounter._id)
    AFTER

  • Get encounter.episode from Encounter object

• Get procedure.origin_episode from Procedure object

• Render a response according to specification

Input parameters

Request structure

See on Apiary

Authorize

• Verify the validity of access token

  • Return (401, 'Invalid access token') in case of validation fails

• Verify that token is not expired

  • in case of error - return (401, 'Invalid access token')

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

  • Return (403, 'Your scope does not allow to access this resource. Missing allowances: medical_event_context:read') in case of invalid scope(s)

...

Headers

• Content-Type:application/json

• Authorization:Bearer mF_9.B5f-4.1JqM

Request data validation

Validate Person

• Get Person identifier from the URL

• Check it exists in DB

  • Return 404 ('not_found') in case of error

...

• Get Procedure identifier from the URL

  • Check it exists in DB

    • Return 404 ('not_found') in case of error

  • Check Procedure belongs to patient

    • Return 404 ('not_found') in case of error

Service logic

Service returns contexts (episode and origin_episode), procedure based on:

Get Procedure object byprocedure_id from procedures (MongoDB)

• Get procedure.encounter.identifier from Procedure object

Call https://e-health-ua.atlassian.net/wiki/spaces/PCR/pages/17003184199 :

Get Encounter objectby procedure.encounter.identifier (procedure.encounter.identifier = encounter._id)
AFTER

• Get encounter.episode from Encounter object

• Get procedure.origin_episode from Procedure object

• Render a response according to specification

Processing

Response structure*

See on Apiary

{
  "data": {
    "episode": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "episode"
            }
          ]
        },
        "value": "7c3da506-804d-4550-8993-bf17f9ee0403"
      },
      "display_value": "null"
    },
    "origin_episode": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "episode"
            }
          ]
        },
        "value": "7c3da506-804d-4550-8993-bf17f9ee0403"
      },
      "display_value": "null"
    }
  },
  "meta": {
    "code": 200,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  }
}

Post-processing processes

HTTP status codes