REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
Properties of a REST API method document
Purpose
This WS is designed to get declaration requests list.
Key features
Only authenticated and authorized employee with appropriate scope can get declaration requests list.
The service returns only a declaration requests that were created in the same legal entity as the user
Method returns shortened declaration request details, to obtain full information - use Get Declaration request by ID method.
Logic
Extract
client_id
from token. Filter declaration requests byclient_id
(legal_entity_id
)Filter declaration requests to show only originated by legal entity or shared with legal entity (
channel
== MIS ORis_shareable
== True)Filter declaration requests by search params (If
legal_entity_id
is differ fromclient_id
in token - empty list must be returned)Render found declaration requests with shortened details 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 | composition_id | M | String ($uuid) (path) | Composition object ID | 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59 |
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 | Authorization | Bearer {{access_token}} | M | Перевірка користувача | Authorization:Bearer {{access_token}} |
3 | X-Custom-PSK | {{secret}} | X-Custom-PSK:{{secret}} |
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
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 | Response |
| ||
3 | 401 | Access token validation failed | |||
4 | 401 | Invalid access token | |||
5 | 401 | Unauthorized | Помилка підтвердження | ||
6 | 403 | Invalid scope | |||
7 | 403 | Your scope does not allow to access this resource. Missing allowances: declaration_request:read | |||
8 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
9 | |||||
10 | |||||
11 | Специфічні | ||||
12 | 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