ЕСОЗ - публічна документація
[DRAFT] Get Observation contexts [API-007-007-001-0278]
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою.
https://e-health-ua.atlassian.net/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)
- 1 Properties of a REST API method document
- 2 Purpose
- 3 Logic
- 4 Configuration parameters
- 5 Dictionaries
- 6 Input parameters
- 7 Request structure
- 8 Headers
- 9 Request data validation
- 10 Authorize
- 10.1 Validate patient
- 11 Processing
- 12 Response structure examples
- 13 HTTP status codes
- 14 Post-processing processes
- 15 Technical modules where the method is used
Properties of a REST API method document
Document type | Метод REST API |
---|---|
Document title | [DRAFT] Get Observation contexts [API-007-007-001-0278] |
Guideline ID | GUI-0011 |
Author | @ |
Document version | 1 |
Document status | DRAFT |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-007-007-001-0278 |
Microservices (namespace) | ME |
Component | Observation |
Component ID | COM-007-007 |
Link на API-специфікацію | |
Resource | {{host}}/api/patients/{{patient_id}}/observations |
Scope | observation:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private | Public |
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
Headers
Request data validation
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 = 'observation:read')
Return 403 in case invalid scope(s)
Access to the resource is also managed by ABAC module.
Validate patient
Validate patient exists in MongoDB
In case of error return 404 not found
Processing
In case episode_id was submitted as a search param:
Select all encounters.id where ME.patinents{patient_id}.encounters{*}.episode.identifier.value== episode_id
Select all observations where ME.patients{patient_id}.observationd{*}.context.identifier.value == Select 1
Response structure examples
See on API-specification
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 |
| 200 |
|
|
|
3 |
| 401 |
| Access token validation failed |
|
4 |
| 403 |
| Invalid scope |
|
5 |
| 403 | Your scope does not allow to access this resource. Missing allowances: medical_event_context:read |
|
|
6 |
| 404 | not found |
|
|
7 | Специфічні | ||||
8 |
|
|
|
|
|
Post-processing processes
N/A
Technical modules where the method is used
N/A
ЕСОЗ - публічна документація