Versions Compared

Key

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

Purpose

This method allows to get an ID of the episode that is a context of the Device, in order to create an approval on the episode, and receive access to the medical events related to that episode, including the Device.

This method allows to get the context of Device in order to create approval on episode and receive access to other medical events.

Specification

Page Properties
idAPI_Specification

Link

https://ehealthmedicaleventsapi.docs.apiary.io/#reference/medical-events/device/get-device-context

Resource

/api/patients/{{patient_id}}/devices/{{device_id}}/context

Scope

medical_event_context:read

Components

EDP

Microservices

API paragraph not found

Protocol type

REST

Request type

GET

Sync/Async

Async

Public/Private/Internal

Public

Logic

Service returns context_episode_id of the device:

  • Get device.context_episode_id from Device object

  • Enrich response with context_episode_id and render the response according to JSON Schema

Service returns context (episode), device based on:

  • Get Device object bydevice_id from devices (MongoDB)

  • Get device.context.identifier from Device object

  • Call Get Encounter context :

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

    • Get encounter.episode from Encounter object

  • Render a response according to specification

Input parameters

Input parameter

Values

Type

Description

Example

patient_id

String

Patient identifier

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

device_id

String

Device identifier

a10aeafb-0df2-4091-bc83-f07e92a100ae

Request structure

See on Apiary

...

  • Get Person identifier from the URL

  • Check it exists in DB

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

Validate Encounter

  • Get Device identifier from the URL

    • Check it exists in DB

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

    • Check Device belongs to patient

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

Validate Device

  • Get Device identifier from the URL

    • Check it exists in DB

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

    • Check Device belongs to the patient

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

Processing

API paragraph not found

...