Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method document
...
id | page_properties_method_REST API |
---|
...
Document type
...
Метод REST API
...
Guideline ID
...
GUI-0011
...
Author
...
@
...
Document version
...
1
...
Document status
...
DRAFT
...
Date of creation
...
ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD)
...
Date of update
...
ХХ.ХХ.ХХХХ (дата зміни версії)
...
Method API ID
...
API-001-001-001-0001
...
Microservices (namespace)
...
MPI
...
Component
...
Auth
...
Component ID
...
COM-001-001
...
Link на API-специфікацію
...
...
Resource
...
{{host}}//api.ehealth.gov.ua/api/patients/id/encounter_package
...
Scope
...
Protocol type
...
Request type
...
Sync/Async
...
Public/Private
Purpose
Describe the purpose of the API method, add Key points (if necessary)
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
Description of input parameters
...
Input parameter
...
Mandatory
...
Type
...
Description
...
Example
...
composition_id
...
M
...
String ($uuid) (path)
...
Composition object ID
...
89678f60-4cdc-4fe3-ae83-e8b3ebd35c59
...
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
...
title | Example |
---|
...
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer c2778f3064753ea70de870a53795f5c9
...
M
...
Перевірка користувача
...
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
...
Request data validation
Describe the process of checking the input data transmitted in the request for compliance with the given rules and restrictions set in the API
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
Note | ||
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Info |
---|
+/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method document
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Purpose
This WS is designed to search Medication request requests in the care plan context. If the user has approval on the care plan, he will receive a list of Medication request requests based on this care plan
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
No
Dictionaries
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | care_plan_id | M | String | unique care plan identifier | 8838982b-6a77-4cb5-87cd-cdb82eb55364 |
2 | employee_id | O | String | user_id of a doctor |
|
3 | person_id | O | String | person_id of a patient |
|
4 | status | O | Enum | Status of medication request request. Default
| NEW |
5 | intent | O | String | Medication request request intent | order |
6 | encounter_id | O | String | Unique encounter identifier | 7075e0e2-6b57-47fd-aff7-324806efa7e5 |
7 | page | O | Number | Page number | 2 |
8 | page_size | O | Number | A limit on the number of objects to be returned, between 1 and 300. Default: 50 | 50 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
Request data validation
Authorize
Verify the validity of access token
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')
Check user scopes in order to perform this action (scope = 'medication_request_request:read')
Return (403, 'Your scope does not allow to access this resource. Missing allowances: medication_request_request:read') in case of invalid scope(s)
Access to the resource is also managed by ABAC rules (EN).
Processing
Service returns all Medication request requests related to the care plan filtered by submitted parameters:
Get all Medication request requests by care_plan_id from medication_request_requests (IL database).
Validate data consistency:
Ensure that requested Medication request requests have ABAC context
Return 403 ('Access denied') in case of error.
Filter list above by submitted search parameters.
Render a response according to specification with found Medication request requests entities.
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | ||||
---|---|---|---|---|---|---|---|---|
1 | Базові | |||||||
2 | 1000401 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновокInvalid access token | Недійсний токен доступу | ||
3 | 401 | Unauthorized | Помилка підтвердження | |||||
4 | Специфічні | |||||||
5 | 422 | Only for active MPI record can be created medication request!403 | Your scope does not allow to access this resource. Missing allowances: medication_request_request:read | Для вашої ролі відсутній доступ до цього ресурсу. Необхідний доступ на перегляд заявки на електронний рецепт | ||||
4 | 403 | Access denied | Доступ заборонено | |||||
5 | Специфічні | |||||||
6 |
Post-processing processes
Description of actions performed on data after processingNo
Technical modules where the method is used
List of pages describing technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...