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 WS allows to get a list of medical programs already provided by the divisions of legal entity according to contracts. Also, this list can be filtered using search parameters.
Logic
This method allows to get a list of medical programs already provided by the divisions of legal entity according to contracts. Also, this list can be filtered using search parameters.
Key points
Only authenticated and authorized employees with appropriate scope can get a list of Medical programs provision.
Method returns a list of Medical programs provision for user’s legal entity only.
List can be filtered by search params.
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 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 | ||
---|---|---|
| ||
|
...
Key | Value | Mandatory | Description | Example | |
---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json |
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9F3GF124Df565FDS234SDF34 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9F3GF124Df565FDS234SDF34 |
3 | api-key | aDGFDFGT46S5gFGD |
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 legal entity
Extract client_id from token.
Check client scopes in order to perform this action (scope = 'medical_program_provision:read')
in case of error - return 403 “Your scope does not allow to access this resource. Missing allowances: medical_program_provision:read”
Check legal entity status (status = ACTIVE, SUSPENDED)
In case of error - return 422 “Legal entity is not active”
Processing
Search params
All search params are optional. Search with a few params executes according to the logical AND rule.
contract_number
If submitted, filter list by medical_program_provision.contract_number
medical_program_id
If submitted, filter list by medical_program_provision.medical_program_id
division_id
If submitted, filter list by medical_program_provision.division_id
is_active
If submitted, filter list by medical_program_provision.is_active
Service logic
Get client_id from token as legal entity identifier
Define all the divisions of the legal entity
Get and render all the records with defined divisions from medical_program_provision table filtered by search 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 | 200 | |||||||
3 | 401 | Invalid access token | ||||||
4 | 401 | Unauthorized | Помилка підтвердження | |||||
5 | 403 | Your scope does not allow to access this resource. Missing allowances: medical_program_provision:read | ||||||
6 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | |||
37 | 401 | Unauthorized | Помилка підтвердження | 4422 | Legal entity is not active | |||
8 | Специфічні | |||||||
59 | 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 | ||||
---|---|---|---|---|
|
...