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 activate previously deactivated healthcare service for the division of legal entity
Key points
Only authenticated and authorized user with an appropriate scope can activate healthcare service.
Only deactivated healthcare service can be activated.
Healthcare service can be activated for legal entities in ACTIVE or SUSPENDED statuses.
User can activate healthcare services only of its legal entity.
Logic
Update healthcare service in healthcare_services table (PRM DB) with data from request and additional fields:
status = 'ACTIVE';
updated_at = now();
updated_by = user_id from access token.
Configuration parameters
N/A
Dictionaries
N/A
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
Expand | ||
---|---|---|
| ||
|
Headers
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:write')
return 403 (“Your scope does not allow to access this resource. Missing allowances: healthcare_service:write”) in case of invalid scope(s).
Validate legal entity
Extract legal entity id from access token. Check that legal entity is in ‘ACTIVE’ or ‘SUSPENDED’ status
in case of error - return 409 (“Invalid legal entity status”).
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”).
Validate division
Get healthcare service by $.id. Check that division status = ‘ACTIVE’
in case of error - return 409 (“Division must be active”).
Validate transition
Get healthcare service by $.id. Check that healthcare service status = ‘INACTIVE’
in case of error - return 409 (“healthcare_service.status healthcare service cannot be ACTIVATED”), where healthcare_service.status = value of status of healthcare service from PRM DB.
Processing
N/A
Response structure examples
See on API-specification
Expand | |||||
---|---|---|---|---|---|
| |||||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 | 200 | Response |
| ||
3 | 401 | Invalid access token |
| ||
4 | 403 | forbidden | |||
5 | 403 | Healthcare service belongs to legal entity id from access token check failed. | |||
6 | 403 | Your scope does not allow to access this resource. Missing allowances: healthcare_service:write | |||
7 | 404 | Healthcare service exists in PRM DB check failed | |||
8 | 404 | Not found | |||
9 | 409 | Division must be active. |
| ||
10 | 409 | Invalid legal entity status | |||
11 | 409 | healthcare_service.status healthcare service cannot be ACTIVATED | |||
12 | Специфічні | ||||
13 |
Post-processing processes
N/A
Technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|