Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
In case if persons current authentication method is OTP, request body must contain
verification_code
field with OTP.For any other authentication method, request body must be empty, but additional documents upload is needed for OFFLINE authentication method.
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 | ||||||
---|---|---|---|---|---|---|---|---|---|---|
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
Expand | ||
---|---|---|
| ||
|
...
Key | Value | Mandatory | Description | Example | ||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json | |||||
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 | 3 |
Request data validation
3 |
Request data validation
Authorize user
Verify the validity of access token
Check user scopes declaration_request:write in order to perform this action
In case error - generate 401 response
Validate request
Validate request using JSON schema
In case validation failed - generate 422 error
...
Expand | ||
---|---|---|
|
Authorize user
...
Verify the validity of access token
Check user scopes declaration_request:write in order to perform this action
...
Validate person verification status
...
Change entity
status
in IL_DB.declaration_request to APPROVEDSet
status_reason
to doctor_confirmedSet
is_shareable
to trueSet
updated_at
- now() (Get current date-time)Set
updated_by
- user_id (Extract user from token)
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 | 1000 | 404 | Composition not foundCOMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 3 | 201 | Response |
| |||
43 | 401 |
| Invalid scopes | ||||||||
54 | 404 | Active parent declaration was not found | |||||||||
65 | 409 | Patient is not verified |
| ||||||||
76 | 422 | This doctor has X declarations and could not sign more | 8 | 9 | 10 | 11 | 401 | Unauthorized | Помилка підтвердження | ||
12 | Специфічні | ||||||||||
13 | 422 | Only for active MPI record can be created medication request!7 | Специфічні | ||||||||
8 |
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
Page Properties Report | ||||
---|---|---|---|---|
|
...