Info |
---|
Info |
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method 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)
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 parametersUse this method to deactivate msp
Logic
...
Configuration parameters
N/A
Dictionaries
N/A
Input parameters
N/A
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 | ||
---|---|---|
| ||
|
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer c2778f3064753ea70de870a53795f5c9
...
M
...
Перевірка користувача
...
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
...
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
Response structure examples
...
Request data validation
Authorize
Verify the validity of access token
Check user scope legal_entity:deactivate in order to perform this action
In case error - return 401 error
Validate transition
Validate transition according to Available transitions. Deactivation of an legal_entity is possible if parameters have the following values: is_active = true & status = ACTIVE or SUSPENDED.
In case error return Error 409 message "Invalid transition".
Processing
Deactivate employees
Invoke PRM API to get list of active employees by legal_entity_id. Employees list contains active employees where status=APPROVED and is_active = true.
For each employee check active declarations and deactivate it (if exist) according to https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/583404010/Deactivate+Employee#Deactivate-declarations
To deactivate each employee from the list (except OWNER).
Terminate Contract and Contract Requests
Find contracts by contractor_legal_entity_id=$legal_entity_id and status='VERIFIED'
set prm.contracts.status=TERMINATED and status_reason='auto_deactivation_legal_entity'
Find contract requests by contractor_legal_entity_id=$legal_entity_id and status in (`NEW`, `IN_PROCESS`, `APPROVED`, `PENDING_NHS_SIGN`, `NHS_SIGNED`)
set prm.contract_requests.status=TERMINATED and status_reason='auto_deactivation_legal_entity'
Deactivate Legal Entity
Change legal_entity status to CLOSED
Deactivate Medical Program Provision
For PHARMACY legal entity type only (according to link).
For related divisions deactivate linked active medical program provision entities:
set is_active = false
set deactivate_reason = AUTO_LEGAL_ENTITY_DEACTIVATION (according to PROVISION_DEACTIVATE_REASON dictionary)
set updated_at, updated by
Response structure examples
See on API-specification
Expand | |||||
---|---|---|---|---|---|
| |||||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | ||||
---|---|---|---|---|---|---|---|---|
1 | Базові | |||||||
2 | 1000200 | 404 Response | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
| ||
3 | 401 | Unauthorized | Помилка підтвердження Invalid scope | |||||
4 | Специфічні409 | Invalid transition | ||||||
5 | 422 | Only for active MPI record can be created medication request!Специфічні | ||||||
6 |
Post-processing processes
Description of actions performed on data after processingN/A
Technical modules where the method is used
List of pages describing technical modules where the method is usedN/A
Page Properties Report | ||||
---|---|---|---|---|
|
...