Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
The legal entity (Owner, HR) can see only employee_requests that were made by this legal entity.
NHS Admin can see all employee_requests
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
POSITION
EMPLOYEE_TYPE
GENDER
+DOCUMENT_TYPE
PHONE_TYPE
COUNTRY
EDUCATION_DEGREE
QUALIFICATION_TYPE
SPECIALITY_TYPE
SPECIALITY_LEVEL
SPEC_QUALIFICATION_TYPE
Input parameters
...
parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id |
| String | 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 (string, optional) | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 (string, optional) |
3 |
Request data validationvalidation
Authorize
Request to process the request using a token in the headers
Validate request
Verify the validity of access token
in case error return 401
Check user scopes in order to perform this action (scope = 'employee_request:read')
in case error return 403
...
Get legal_entity.id from '$.context'. Filter employee requests by legal_entity.id
in case error return 404
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 | Access token validation failed | |||||||
4 | 401 | Error |
| ||||||
5 | 401 | Unauthorized | Помилка підтвердження6 | 403 | Check user scopes in order to perform this action failed | ||||
6 | |||||||||
7 | 8 | 403 | Error | 9 | 1000|||||
8 | 404Composition not found | Не знайдено медичний висновок | 10 | 404 | COMPOSITION_NOT_FOUND_404 | ||||
119 | 404 | Error | |||||||
1210 | 404 | Get legal_entity.id from '$.context'. Filter employee requests by legal_entity.id failed | |||||||
1311 | 404 | Not found employee request in DB with this ID | |||||||
1412 | |||||||||
1513 | Специфічні | ||||||||
16 | 422 | Only for active MPI record can be created medication request!14 |
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 | ||||
---|---|---|---|---|
|
...