Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Purpose
Describe the purpose of the API method, add Key points (if necessary)
Logic
Description of the working algorithm of the API method and the interaction of services with each other add Service logic (if necessary)
This WS is designed to deactivate healthcare service for the division of a legal entity
Key points
Only authenticated and authorized user with an appropriate scope can deactivate healthcare service.
Only active healthcare service can be deactivated.
Healthcare service can be deactivated for legal entities in ACTIVE or SUSPENDED statuses.
User can deactivate healthcare services only of its legal entity.
Logic
Update healthcare service in healthcare_services table (PRM DB) with data from request and additional fields:
status = 'INACTIVE';
updated_at = now();
updated_by = user_id from access 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 | Healthcare service identifier. Optional | d290f1ee-6c54-4b01-90e6-d701748f0851 |
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
...
Validate legal entity
Extract legal entity id from access token. Check that legal entity is in ‘ACTIVE’ or ‘SUSPENDED’ status
in case of error - return 409 (“Invalid legal entity status”).
Validate healthcare service
Get healthcare service by $.id. Check that healthcare service exists in PRM DB
in case of error - return 404 (“not_found”).
Get healthcare service by $.id. Check that healthcare service belongs to legal entity id from access token
in case of error - return 403 (“forbidden”).
Validate transition
Get healthcare service by $.id. Check that healthcare service status = ‘ACTIVE’
in case of error - return 409 (“healthcare_service.status healthcare service cannot be DEACTIVATED”), where healthcare_service.status = value of status of healthcare service from PRM DB.
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
Expand | ||
---|---|---|
| ||
|
Response code | HTTP Status code | Message | Internal name | Description | |||||
---|---|---|---|---|---|---|---|---|---|
1 | Базові | ||||||||
2 | 200 | Response |
| ||||||
3 | 401 | Invalid access token |
| ||||||
4 | 401 | Unauthorized | Помилка підтвердження | ||||||
5 | 403 | forbidden | |||||||
6 | 403 | Healthcare service belongs to legal entity id from access token check failed. | |||||||
7 | 403 | Your scope does not allow to access this resource. Missing allowances: healthcare_service:write. | |||||||
8 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 3 | 401 | Unauthorized | Помилка підтвердження |
4 | Специфічні | ||||||||
9 | 404 | Not found | Healthcare service exists in PRM DB check failed | ||||||
10 | 409 | Invalid legal entity status. |
| ||||||
11 | 409 | healthcare_service.status healthcare service cannot be DEACTIVATED. | |||||||
12 | |||||||||
13 | |||||||||
14 | Специфічні | ||||||||
15 | 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
Page Properties Report | ||||
---|---|---|---|---|
|
...