Info |
---|
Info |
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
...
Page Properties | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||
|
Purpose
Describe the purpose of the API method, add Key points (if necessary)
Logic
...
|
Purpose
This WS is designed to appoints an executor (employee), who should Update Contract Request from NHS side.
Logic
This WS is designed for NHS employees. Before rewieving contract request it must be assign to NHS employee who will be responsible for this request. To assign employee contract it must be in status NEW, IN_PROCESS. After assigner was updated, contract request status will be changed to IN_PROCESS
.
This query is also use to update existing assigner in Contract request.
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 | Contract request identifier. Required | d290f1ee-6c54-4b01-90e6-d701748f0851 |
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-Type | application/json | M | Тип контенту | Content-Type:application/json |
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9c2778f3064753ea70de870a53795f5c99 |
3 |
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
...
Validate user
extract user_id from token
extract client_id from token
Check if user is active
in case error return “User is not active”
check nhs_legal_entity is active
in case error return “Client is not active”
Check user role = "NHS ADMIN SIGNER"
in case error return "You don't have permission to access this resource"
Validate contract request id and status
Validate contract request ID exist
in case of error return “Contract Request not found”
Check contract_request.status in ('NEW', 'IN_PROCESS')
in case error return “Incorrect status of contract_request to modify it"
Validate request
Fetch prm.employees by $employee_id. Validate:
employees.legal_entity_id=$client_id
in case of error return “Invalid legal entity id”
employees.status=APPROVED
in case of error return “Invalid employee status”
check employee.party→ party_users→ users_roles→ roles exist role with name = 'NHS ADMIN SIGNER'
in case of error return “Employee doesn't have required role”
Processing
Update contract_requests.assignee_id (IL) - set $employee_id from request
Update contract_requests.status to ‘IN_PROCESS’
Update updated_at = now()
Update updated_by = $user_id
Response structure examples
Description of the REST API response structure, example
Examples:
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
| ||
Expand | ||
| ||
|
Expand | ||
---|---|---|
| ||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | ||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | Базові | |||||||||
2 | 200 | Response |
| |||||||
3 | 401 | Access denied | Invalid token | |||||||
4 | 401 | Unauthorized | Помилка підтвердження | |||||||
5 | 403 | Your scope does not allow to access this resource. Missing allowances: {{scope}} | Scope is missing | |||||||
6 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | |||||
3 | 401 | Unauthorized | Помилка підтвердження | 4 | 7 | Специфічні | ||||
58 | 422 | Only for active MPI record can be created medication request! |
Post-processing processes
...
Add status to event manager
After status was changed (status = IN_PROCESS) - add new record to event_manager
field | value |
---|---|
event_type | StatusChangeEvent |
entity_type | ReimbursementContractRequest |
CapitationContractRequest | |
entity_id | $.id |
properties.status.new_value | $.status |
event_time | $.updated_at |
changed_by | $.updated_by |
Technical modules where the method is used
List of pages describing technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...