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 method should be used for the deactivation of the division
Logic
Only authenticated and authorized user can use this service
Only ACTIVE division can be deactivated
Legal entity can deactivate only its own divisions
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
...
Dictionary ADDRESS_TYPE
Dictionary PHONE_TYPE
Dictionary SETTLEMENT_TYPE
Dictionary STREET_TYPE
Dictionary DIVISION_TYPE
Dictionary COUNTRY
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 | Required | 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{{access_token}} | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 | 3 | {{access_token}} |
3 | API-key | {{mis_client_secret}} | API-key:{{mis_client_secret}} |
Request data validation
Describe the process of checking the input data transmitted in the request for compliance with the given rules and restrictions set in the API
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
...
Validate division
Check that division with such ID exists in the system (is_active = true)
In case of error - return 404
Check that division belongs to the same legal entity as the user
In case of error - return 403
Validate healthcare service
Check that there are no active healthcare services related to this division
Search for healthcare services with this division in status ACTIVE
If search result contains any records - return 409 error (Division cannot be deactivated - active healthcare services exists)
Validate equipment
Check that there are no active records in equipment table related to this division
Search for equipments with this division in ACTIVE status
If search result contains any records - return 409 error (Division cannot be deactivated - active equipments exists)
Validate transition
Only ACTIVE division can be deactivated
Available transitions
ACTIVE → INACTIVE
In other cases - return 409 error ('{current_status} division cannot be DEACTIVATED')
Processing
Save object to DB
Parameter | Source | Description |
---|---|---|
status | INACTIVE |
|
updated_at | Timestamp: now() | Get current date-time |
updated_by | Token: user_id |
|
Deactivate Medical Program Provision
For PHARMACY legal entity type only. For related divisions deactivate linked active medical program provision entities (according to link).
Deactivate related active medical program provision entities:
set is_active = false
set deactivate_reason = AUTO_DIVISION_DEACTIVATION
set updated_at, updated by
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 | Check that division belongs to the same legal entity as the user failed | |||||||
6 | 403 | Invalid scope | |||||||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 3 | 401 | Unauthorized | Помилка підтвердження |
4 | Специфічні | ||||||||
58 | 404 | Validation error | |||||||
9 | 409 | {current_status} division cannot be DEACTIVATED | |||||||
10 | 409 | Division cannot be deactivated - active healthcare services exists | |||||||
11 | 409 | Validation error | |||||||
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
Page Properties Report | ||||
---|---|---|---|---|
|
...