Table of Contents |
---|
...
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 | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
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 objectCallGet Encounter context:Get Encounter objectby device.context.identifier (device.context.identifier = encounter._id)AFTERGetencounter.episodefrom Encounter object
Render a response according to specification
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Patient identifier |
| |
device_id | String | Device identifier |
|
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
...