Versions Compared

Version Old Version 17 New Version Current
Changes made by

Serhii Boldin (SoE eHealth) (Unlicensed)

Natalia Horodytska (SoE eHealth)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel3

Purpose

...

This WS allows API method is designed to get detailed episode info from Admin panel.

...

information about Episode by its identifier episode_id and patient identifier patient_id

Specification

Page Properties

Link

https://medicaleventsmisapi.docs.apiary.io/#reference/medical-events/episode-of-care/get-episode-by-id

Resource

/api/patients/{{patient_id}}/episodes/{{episode_id}}

Scope

episode:read

Components

Episode of Care

Microservices

API paragraph not found

Protocol type

REST

Request type

GET

Sync/Async

Async

Public/Private/Internal

Public

Logic*

API paragraph not found

Key points

  1. This is a graphQl query used in Administration panel only

  2. Only authenticated and authorized NHS employee with appropriate scope can get episode details.

  3. Query returns single episode by person (mpi id) and episode identifier.

  4. Filtration with forbidden group items is worked here. So NHS employee should have an approval from patient to see an episode with forbidden elements.

  5. Query should be invoked only if Justification for monitoring exists for current user and corresponding patient (ABAC rule_-2).

Input parameters

...

Input parameter

...

Values

...

Type

...

Description

...

Example

...

patient_id

...

String

...

Patient identifier

...

70a9e15b-b71b-4caf-8f2e-ff247e8a5677

...

episode_id

...

String

...

Episode identifier

...

70a9e15b-b71b-4caf-8f2e-ff247e8a5677

Request structure*

API paragraph not found

Authorize*

...

Verify the validity of access token

  • in case of error - 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 = 'episode:practical_monitor')

  • return 403 (“Your scope does not allow to access this resource. Missing allowances: episode:practical_monitor”) in case of invalid scope(s)

...

  • return 403 (“Access denied. Justification required“) in case of error

Request to process the request using a token in the headers

Headers*

Наприклад:

  • Content-Type:application/json

  • Authorization:Bearer mF_9.B5f-4.1JqM

Request data validation*

Validate legal entity

  • Extract client_id from token.

  • Check client scopes in order to perform this action (scope = 'episode:practical_monitor')

    • in case of error - return 403 (“Your scope does not allow to access this resource. Missing allowances: episode:monitor”)

  • Check legal entity status (status = ACTIVE)

    • In case of error - return 409 ('client_id refers to legal entity that is not active')

Validate request

  • Check required personId submitted.

    • return 404 (“not found“) in case not exist

  • Check required episode Id submitted.

    • return 404 (“not found“) in case not exist or not related to person

    • return 403 (“Access denied“) in case episode has forbidden group items. Take into account approvals granted to NHS employee on forbidden groups (look at Medical Events filtration by Forbidden groups for details)

...

Input parameters

Input parameter

Values

Type

Description

Example

patient_id

String

Patient identifier

70a9e15b-b71b-4caf-8f2e-ff247e8a5677

episode_id

String

Episode identifier

70a9e15b-b71b-4caf-8f2e-ff247e8a5677

Request structure

Body has to be empty

Authorize

Request to process the request using a token in the headers

  • Verify the validity of access token

    • Return 401 in case validation fails

  • Verify token is not expired

    • in case error return 401 

...

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

    1. Return 403 in case invalid scope(s)

Validate

Access to the resource is also managed by by ABAC module.

Headers

Processing*

Service logic

  1. Get episode by id and patient_id

  2. Render detailed episode data according to schema

...

Наприклад:

  • Content-Type:application/json

  • Authorization:Bearer {{access_token}}

  • API-key:{{secret}}

Response structure

See on Apiary

Example:

Expand
titleResponse example
Code Block
{
  "data": {
    "id": "90a9e15b-b71b-4caf-8f2e-ff247e8a5600",
    "inserted_at": "2018-08-02T10:45:16.000Z",
    "updated_at": "2018-08-02T10:45:16.000Z",
    "type": {
      "system": "eHealth/episode_types",
      "code": "primary_care"
    },
    "status": "active",
    "name": "Діабет 2018",
    "current_diagnoses": [
      {
        "condition": {
          "identifier": {
            "type": {
              "coding": [
                {
                  "system": "eHealth/resources",
                  "code": "condition"
                }
              ]
            },
            "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
          },
          "display_value": "null"
        },
        "code": {
          "coding": [
            {
              "system": "eHealth/ICPC2/conditions",
              "code": "A20"
            }
          ]
        },
        "role": {
          "coding": [
            {
              "system": "eHealth/diagnosis_roles",
              "code": "CC"
            }
          ]
        },
        "rank": 1
      }
    ],
    "diagnoses_history": [
      {
        "date": "2018-08-02T10:45:16.000Z",
        "evidence": {
          "identifier": {
            "type": {
              "coding": [
                {
                  "system": "eHealth/resources",
                  "code": "encounter"
                }
              ]
            },
            "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
          },
          "display_value": "null"
        },
        "diagnoses": [
          {
            "condition": {
              "identifier": {
                "type": {
                  "coding": [
                    {
                      "system": "eHealth/resources",
                      "code": "condition"
                    }
                  ]
                },
                "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
              },
              "display_value": "null"
            },
            "code": {
              "coding": [
                {
                  "system": "eHealth/ICPC2/conditions",
                  "code": "A20"
                }
              ]
            },
            "role": {
              "coding": [
                {
                  "system": "eHealth/diagnosis_roles",
                  "code": "CC"
                }
              ]
            },
            "rank": 1
          },
          {
            "condition": {
              "identifier": {
                "type": {
                  "coding": [
                    {
                      "system": "eHealth/resources",
                      "code": "condition"
                    }
                  ]
                },
                "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
              },
              "display_value": "null"
            },
            "code": {
              "coding": [
                {
                  "system": "eHealth/ICPC2/conditions",
                  "code": "A20"
                }
              ]
            },
            "role": {
              "coding": [
                {
                  "system": "eHealth/diagnosis_roles",
                  "code": "CC"
                }
              ]
            },
            "rank": 1
          }
        ]
      }
    ],
    "status_history": [
      {
        "status": "active",
        "status reason": {
          "coding": [
            {
              "system": "eHealth/episode_closing_reasons",
              "code": "cured"
            }
          ]
        },
        "inserted_at": "2018-08-02T10:45:16.000Z"
      }
    ],
    "managing_organization": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "legal_entity"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      },
      "display_value": "Медікал Солюшнc"
    },
    "period": {
      "start": "2018-08-02T10:45:16.000Z",
      "end": "2018-08-03T10:45:16.000Z"
    },
    "care_manager": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "employee"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      },
      "display_value": "null"
    },
    "closing_summary": "Носові шляхи вільні, горло рожеве, температура в нормі",
    "status_reason": {
      "coding": [
        {
          "system": "eHealth/episode_closing_reasons",
          "code": "cured"
        }
      ]
    },
    "explanatory_letter": "Епізод був відмінений у зв'язку з помилкою при виборі пацієнта"
  },
  "meta": {
    "code": 200,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  }
}

Post-processing processes*

...

HTTP status codes
...
HTTP status code
Message
What caused the error
 200
 
 
401
 
Access token validation failed
403
 
Invalid scope