...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
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
...
Document title
...
[Document status] REST API [Назва методу] [ID методу]
...
Guideline ID
...
GUI-0011
...
Author
...
@
...
Document version
...
1
...
Document status
...
DRAFT
...
Date of creation
Table of Contents |
---|
Properties of a REST API method document
Page Properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
...
Процеси роботи з випискою електронних рецептів
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | person_id | M | String | person_id of a patient. Required | 5e661b15-a39a-4713-b18e-ba03a4a48ecc |
2 |
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
...
legal_entity_id | O | String | Unique legal entity identifier | 7124259c-eeb1-4cbb-acac-ada2162675d1 | |
3 | employee_id | O | String | Unique doctor identifier | 7124259c-eeb1-4cbb-acac-ada2162675d1 |
4 | episode_id | O | String | Unique episode identifier, look into episode in encounter | 6f305d0e-1758-4920-9167-d4f97225ad7e |
5 | care_plan_id | O | String | Unique care plan identifier | 8838982b-6a77-4cb5-87cd-cdb82eb55364 |
6 | activity_id | O | String | Unique activity identifier | d1e07d06-d063-4d19-b9ae-88fc1c7a8682 |
7 | encounter_id | O | String | Unique encounter identifier | 7075e0e2-6b57-47fd-aff7-324806efa7e5 |
8 | status | O | Enum | Status of medication request request. Default
| NEW |
9 | intent | O | String | Medication request request intent | order |
10 | page | O | Number | Page number | 2 |
11 | 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 person filtered by submitted parameters:
...
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
|
...
Response code | HTTP Status code | Message | Internal name | Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Базові | ||||||||||||||||
2 | 200 | Response |
| 3 | 401 | Invalid access token |
| 4 | 401 | Unauthorized | Помилка підтвердження | 5 | 403 | Access denied | 6Internal name | Description | |
1 | Базові | ||||||||||||||||
2 | 401 | Invalid access token | Недійсний токен доступу | ||||||||||||||
3 | 403 | Your scope does not allow to access this resource. Missing allowances: medication_request_request:read | |||||||||||||||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | ||||||||||||
8 | Специфічні | ||||||||||||||||
9 | 422 | Only for active MPI record can be created medication request! | Для вашої ролі відсутній доступ до цього ресурсу. Необхідний доступ на перегляд заявки на електронний рецепт | ||||||||||||||
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 | ||||
---|---|---|---|---|
|
...