REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
...
Properties of a REST API method document
Document type | Метод REST API |
---|---|
Document title | [Document status] REST API [Назва методу] [ID методу] |
Guideline ID | GUI-0011 |
Author | @ |
Document version | 1 |
Document status | DRAFT |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-005-009-001-0173 |
Microservices (namespace) | IL |
Component | Legal Entities |
Component ID | COM-005-009 |
Link на API-специфікацію | |
Resource | {{host}}/api/healthcare_services/{{id}} |
Scope | healthcare_service:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private | Public |
...
Get data from healthcare_services by id (PRM DB).
Render a response according to specification.
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
PROVIDING_CONDITION
SPECIALITY_TYPE
HEALTHCARE_SERVICE_CATEGORIES
HEALTHCARE_SERVICE_PHARMACY_DRUGS_TYPES
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id |
| String | Healthcare service identifier. Optional. | 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 |
|
|
|
|
|
Request data validation
Authorize
Verify the validity of access token
in case of error - return 401 (“Invalid access token”) in case of validation fails.
Verify that token is not expired
in case of error - return 401 (“Invalid access token”).
Check user scopes in order to perform this action (scope = 'healthcare_service:read')
return 403 (“Your scope does not allow to access this resource. Missing allowances: healthcare_service:read”) in case of invalid scope(s).
Validate healthcare service
Get healthcare service by $.id. Check that healthcare service exists in PRM DB
in case of error - return 404 (“not_found”).
Get healthcare service by $.id. Check that healthcare service belongs to legal entity id from access token
in case of error - return 403 (“forbidden”).
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 | Invalid access token |
| |||||||
4 | 401 | Unauthorized |
| Помилка підтвердження | 5 | 403 | forbidden | Healthcare service belongs to legal entity id from access token check failed. | ||
65 | 403 | Your scope does not allow to access this resource. Missing allowances: healthcare_service:read. | ||||||||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | |||||
86 | 404 | Not found | Healthcare service exists in PRM DB check failed | |||||||
97 | Специфічні | |||||||||
10 |
| 422 | Only for active MPI record can be created medication request! | 8 |
|
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
Название | ID ТМ | Статус |
---|---|---|
TM0112 | ||