Info |
---|
Note |
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Info |
---|
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Purpose
This web service is designed to return observations by patient_id, episode_id, diagnostic_report_id or encouner_id.
Logic
Description of the working algorithm of the API method and the interaction of services with each other add Service logic (if necessary)
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
Provides a list of links to dictionaries that are available in Confluence
Input parameters
...
Input parameter
...
Mandatory
...
Type
...
Description
...
Example
...
Request structure
See on Apiary
...
title | Example |
---|
...
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer {{access_token}}
...
Authorization:Bearer {{access_token}}
...
API-key
...
{{secret}}
...
|
Purpose
This method allows to get contexts of Observation in order to create approval on episode and receive access to other medical events.
Logic
Service returns contexts (episode and diagnostic_report), observation based on:
Get Observation object by observation_id from conditions (MongoDB)
Get observation.context_episode_id from Observation object
Get observation.diagnostic_report from Observation object
Render a response according to specification
Configuration parameters
N/A
Dictionaries
N/A
Input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | |||||
2 |
Request structure
See on API-specification
Expand | ||
---|---|---|
| ||
|
Headers
Request data validation
Authorize
...
Response structure examples
See on ApiarySee on API-specification
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
Response code | HTTP Status code | Message | Internal name | Description | ||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | Базові | |||||||||
2 | 200 |
|
| |||||||
3 | 401 |
| Access token validation failed | |||||||
4 | 403 |
| Invalid scope | |||||||
5 | 403 | Специфічні | 6Your scope does not allow to access this resource. Missing allowances: medical_event_context:read | |||||||
6 | 404 | not found | ||||||||
7 | Специфічні | |||||||||
8 |
Post-processing processes
Description of actions performed on data after processingN/A
Technical modules where the method is used
List of pages describing technical modules where the method is usedN/A
Page Properties Report | ||||
---|---|---|---|---|
|
...