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 details
Key features
Only authenticated and authorized employee with appropriate scope can get declaration requests list.
The service can return only declaration request that was created in the same legal entity as the user or assigned to legal entity and shared
Logic
Get declaration request details from il.declaration_requests table by declaration request id from request
Generate URL to get signed_content (optional)
Generate URL only in case of:
channel = PIS and status APPROVED
Put url to urgent section
Render response according to specification.
Use ael service
Parameter | Source |
---|---|
action | 'GET' |
bucket | 'DECLARATION_REQUESTS' |
resource_id | :DECLARATION_REQUEST_ID |
resource_name | signed_content |
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 | request identifier |
|
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}} | Authorization:Bearer {{access_token}} | ||
3 | X-Custom-PSK | {{secret}} | X-Custom-PSK:{{secret}} |
Request data validation
Check that declaration request:
exists in il DB
is_shareable = true or channel = MIS
belongs to legal entity (get user from token, find employee associated with this user and ensure that this employee has at least one role in the same legal entity as in declaration request)
in case of error - return 404 ('not found')
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
Print form is generated after approve declaration request, so in response on Get declaration request by id show fields context
and data_to_be_signed
if DR approved.
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 | 404 | not found | |||
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