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)Use this method to deactivate employee.
Employee status chart
Logic
...
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
...
+DIVISION_TYPE
+DIVISION_STATUS
LEGAL_ENTITY_TYPE_V2
LICENSE_TYPE
+DOCUMENT_TYPE
PHONE_TYPE
COUNTRY
EDUCATION_DEGREE
QUALIFICATION_TYPE
SPECIALITY_TYPE
SPECIALITY_LEVEL
SPEC_QUALIFICATION_TYPE
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 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 |
3 |
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
Validate transition according to Available transitions.
Deactivation of an employee is possible if parameters have the following values: is_active = true & status = APPROVED.
Processing
Revoke role from users
...
Get active employees
Invoke PRM API to get list of employees by legal_entity_id, party_id, employee_type
If found only current employee - Revoke role from user
Deactivate declarations
Invoke OPS_DB API to deactivate declarations
...
Search active declarations
Search active declarations in OPS_DB.declaration using {employee_id}
Search criteria
Code Block |
---|
WHERE OPS_DB.declaration.employee_id = :employee_id
AND OPS_DB.declaration.status = 'ACTIVE'
|
Change declaration status to TERMINATED
Change declarations status in OPS_DB.declaration to {TERMINATED} for all found declarations
Code Block |
---|
SET OPS_DB.declaration.status = 'TERMINATED'
WHERE OPS_DB.declaration.id in (:LIST) |
Dismiss employee from reorganized legal entity
If an employee moved to a new legal entity during the reorganization, his old record (with the same speciality_officio) with the declaration, remain active in the reorganized legal entity.
The owner of the legal successor legal entity can dismiss this employee if necessary. See more details about reorganization process.
If employee id relates to $.related_legal_entities.merged_from_id legal entity OWNER can dismiss this employee
in case no employees were found return 404 with msg (Employee not found)
Deactivate employee
Invoke PRM API to update employee
Parameter | Source | Condition, Action |
---|---|---|
employee_id | Request parameter: $.employee_id |
|
end_date |
|
|
is_active |
| if employee_type in (OWNER, PHARMACY_OWNER) set is_active = false if employee_type ! in (OWNER, PHARMACY_OWNER) is_active not update |
status |
| if employee_type in ( OWNER, PHARMACY_OWNER) status not update if employee_type ! in (OWNER, , PHARMACY_OWNER) set status = DISMISSED |
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 | Error | ||||
4 | 401 | Invalid access token | ||||
5 | 401 | Invalid scope | ||||
6 | 403 | Invalid transition |
| |||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 3|
8 | 404 | Employee not found | ||||
9 | 401 | Unauthorized | Помилка підтвердження | |||
410 | Специфічні | |||||
511 | 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 | ||||
---|---|---|---|---|
|
...