Info |
---|
Note |
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
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
This WS is designed to search (get list) of Employee roles.
Logic
Only authenticated and authorized user can use this service
Service returns only employee roles related to the same legal entity as the user
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
Input parameter | Mandatory | Type | Description | Example | ||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | composition_id | M | String ($uuid) (path) | Composition object ID | 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59 | |||||
2 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
Headers
Key | Value | Mandatory | Description | Example | ||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | Content-Typeapplication/json | M | Тип контенту | Content-Type:application/json | ||||||
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувачаAuthorization:Bearer c2778f3064753ea70de870a53795f5c9 | ||||||
3 |
Request data validation
...
Authorize
Verify the
...
validity of access token
Return 401 in case validation fails
Check scopes in order to perform this action (scope = 'employee_role:read')
Return 403 in case invalid scope(s)
Processing
Extract client_id from token
Return entries filtered by client_id and query params
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 | 201 | Response |
| |||||
3 | 401 | Invalid access token | ||||||
4 | 401Unauthorized | Помилка підтвердження | 5 | 403 | Invalid scope(s) | 6 | ||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | |||
8 | Специфічні | |||||||
9 | 422 | Only for active MPI record can be created medication request!5 | ||||||
6 | Специфічні | |||||||
7 |
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 | ||||
---|---|---|---|---|
|
...