REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
Properties of a REST API method document
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 | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-005-005-001-0086 |
Microservices (namespace) | IL |
Component | Dictionaries and Registers |
Component ID | COM-005-005 |
Link на API-специфікацію | |
Resource | {{host}}/api/rule_engine_rules/{{id}} |
Scope | rule_engine_rule:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private | Public |
Purpose
This WS is designed to return rule engine rule details.
Key points
This is a REST method used by MIS.
Only authenticated and authorized employee with appropriate scope can get rule engine rule details.
Logic
Get data from rule_engine_rules collection (Mongo DB):
rule_engine_rule by id
Render a response according to specification.
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 | |
---|---|---|---|---|---|
1 | id |
| String |
|
|
2 |
|
|
|
|
|
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Headers
Key | Value | Mandatory | Description | Example | |
---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json |
2 |
|
|
|
|
|
Request data validation
Validate rule engine rule
Check that rule engine rule with such ID exists in the system (is_active = true)
In case of error - return 404 "Rule with id <rule_id> is not found", where rule_id - id of rule from request
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 | 200 | ||||
3 | 401 | Invalid access token | |||
4 |
| 401 | Unauthorized |
| Помилка підтвердження |
5 | 403 | Your scope does not allow to access this resource. Missing allowances: rule_engine_rule:read | |||
6 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
7 | 404 | Rule with id <rule_id> is not found | |||
8 | Специфічні | ||||
9 |
| 422 | Only for active MPI record can be created medication request! |
|
|
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical modules where the method is used
Название | ID ТМ | Статус |
---|---|---|
TM0112 | ||