...

...

Purpose

...

This WS allows to get detailed condition info from Admin panelweb service is designed to return conditions by id.

Specification

...

Page Properties

Link https://ehealthmedicaleventsapimedicaleventsmisapi.docs.apiary.io/#reference/medical-events/conditions/get-condition-by-id Resource /api/patients/{{patient_id}}/conditions/{{condition_id}} Scope condition:read Components Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescriptionEpisode of Care Microservices Перелік мікросервісів, які використовує метод API. Наприклад: Auth, ABACAPI paragraph not found Protocol type Тип протоколу, який використовується запитом, наприклад: SOAP | REST Request type GET Sync/Async Метод є синхронним чи асинхронним?

Logic*

1. Get condition by id and patient_id

2. Render detailed condition data according to schema

Key points

...

This is a graphQl query used in Administration panel only

...

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

...

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

...

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

...

Input parameters

Request structure

...

API paragraph not found

...

See on Apiary

Authorize

Request to process the request using a token in the headers

• Verify the validity of access token

  • Return 401 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”)return 401 

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

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

  Check user has access to resource according to @rule_-2 in ABAC

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

...

Headers

...

Наприклад:

• Content-Type:application/json

• Authorization:Bearer mF_9.B5f-4.1JqM{{access_token}}

• API-key:{{secret}}

Request data validation

...

Validate legal entity

• Extract client_id from token.

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

  • in case of error - return 403 (“Your scope does not allow to access this resource. Missing allowances: condition:practical_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 condition Id submitted.

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

  • return 403 (“Access denied“) in case condition 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)

Processing*

API paragraph not found

...

Access to the resource is also managed by ABAC module

Processing

In case episode_id was submitted as a search param:

1. Select all encounters.id where ME.patinents{patient_id}.encounters{*}.episode.identifier.value== episode_id

2. Select all conditions where ME.patients{patient_id}.conditions{*}.context.identifier.value == Select 1

Response structure

See on Apiary

Example:

{
  "data": {
    "id": "6fe6d880-f100-4e39-a278-1d14eb8472ef",
    "primary_source": true,
    "asserter": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "employee"
            }
          ],
          "text": ""
        },
        "value": "97d57238-ffbe-4335-92ea-28d4de117ea2"
      }
    },
    "context": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "encounter"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      },
      "display_value": "null"
    },
    "code": {
      "coding": [
        {
          "system": "eHealth/ICD10/condition_codes",
          "code": "K87"
        }
      ]
    },
    "clinical_status": "active",
    "verification_status": "provisional",
    "severity": {
      "coding": [
        {
          "system": "eHealth/condition_severities",
          "code": "55604002"
        }
      ]
    },
    "body_sites": [
      {
        "coding": [
          {
            "system": "eHealth/body_sites",
            "code": "head"
          }
        ]
      }
    ],
    "onset_date": "2018-10-08T09:46:37.694Z",
    "asserted_date": "2018-10-08T09:46:37.694Z",
    "inserted_at": "2018-08-02T10:45:16.000Z",
    "updated_at": "2018-08-02T10:45:16.000Z",
    "stage": {
      "summary": {
        "coding": [
          {
            "system": "eHealth/condition_stages",
            "code": "14803004"
          }
        ]
      }
    },
    "evidences": [
      {
        "codes": [
          {
            "coding": [
              {
                "system": "eHealth/ICPC2/reasons",
                "code": "169068008"
              }
            ]
          }
        ],
        "details": [
          {
            "identifier": {
              "type": {
                "coding": [
                  {
                    "system": "eHealth/resources",
                    "code": "observation"
                  }
                ]
              },
              "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
            },
            "display_value": "null"
          }
        ]
      }
    ]
  },
  "meta": {
    "code": 200,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  }
}

Post-processing processes

...

API paragraph not found

HTTP status codes

...

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