Note |
---|
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Purpose
This method is used by NHS_admin to reject declarations that has been created with the offline authorization. In case if the verification result is not acceptable. declaration status will be changed to closed
.
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 | id |
| String | Required | d290f1ee-6c54-4b01-90e6-d701748f0851 |
2 |
|
|
|
|
|
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
Headers
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
Authorize
Verify the validity of access token
Check user scope declaration:reject in order to perform this action
In case error - return 401 error.
Validate transition
Validate transitionю Allowed transitions:
...
If not passed, Return Error 403 message "Invalid transition"
Processing
Update Declaration status
$declaration.status = closed
...
$declaration.updated_at = timestamp
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією))
Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |||||
---|---|---|---|---|---|---|---|---|---|
1 | Базові | ||||||||
2 | 200 | Response |
| ||||||
3 | 401 |
|
| ||||||
4 | 401 | Unauthorized |
| Помилка підтвердження | 5 | 403 | Invalid transition |
| |
6 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 7 | |||
8 |
| ||||||||
9 | Специфічні | ||||||||
10 |
| 422 | Only for active MPI record can be created medication request! | 5 | Специфічні | ||||
6 |
|
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