REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
Properties of a REST API method document
Purpose
Use this method to reject previously created Declaration Request
Key features
Only authenticated and authorized user can reject declaration request
New and Approved declaration request can be rejected (/wiki/spaces/PCAB/pages/17513775491 )
Declaration request can be rejected only by the employee who works in the same legal entity in which the request was created
Declaration requests created by patient via PIS and assigned to legal entity could be rejected by legal entity as well
Logic
Service logic
Update declaration request
Change entity status in IL_DB.declaration_request to REJECTED
Set status_reason:
If
channel
= MIS - setstatus_reason
to doctor_rejectIf
channel
= PIS - setstatus_reason
to doctor_rejected_over_limit
Set updated_at - now() (Current date-time)
Set updated_by - user_id (Extract user from token)
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 c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 |
3 |
Request data validation
Validation declaration request
Check that declaration request with such ID exists in the system (is_active = true)
In case of error - return 404
Check that declaration request is allowed to be processed on LE (
channel
== MIS ORis_shareable
== True)In case of error - return 403
Check that declaration request belongs to the same legal entity as the user
In case of error - return 403
Validate transition
Check transition according to /wiki/spaces/PCAB/pages/17513775491
In case of error - return 409 (“Invalid transition“)
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 | 201 | Response |
| ||
3 | 401 | Access token validation failed | |||
4 | 401 | Invalid access token | |||
5 | 401 | Unauthorized | Помилка підтвердження | ||
6 | 403 | Check that declaration request belongs to the same legal entity as the user failed | |||
7 | 403 | Invalid scopes | |||
8 | 403 | Your scope does not allow to access this resource. Missing allowances: declaration_request:reject | |||
9 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
10 | 404 | Check that declaration request with such ID exists in the system (is_active = true) failed | |||
11 | 409 | Invalid transition | |||
12 | Специфічні | ||||
13 | 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