Table of Contents | ||||
---|---|---|---|---|
|
...
This web service is designed to update existing episode of care for the patient.
Specification
Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logic
Read more about business logic and validations.API paragraph not found
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Patient identifier |
| |
episode_id | String | Episode identifier |
|
...
Request to process the request using a token in the headers
Headers
Наприклад:
Content-Type:application/json
Authorization:Bearer mF_9.B5f-4.1JqM
...
ME.episode.status == "active"
in case of error "Episode in status {episode_status} can not be updated"
Validate care_manager
$.care_manager.identifier.type.coding.[0].code = "employee"
in case of error return 422 "Submitted code is not allowed for this field"
$.care_manager.identifier.type.coding.[0].system = "eHealth/resources"
in case of error return 422 "Submitted system is not allowed for this field"
$.care_manager.identifier.value must meet the following requirements
PRM.employee.type = "DOCTOR" or "SPECIALIST" OR "ASSISTANT"value from list of employee_types in configuration:
ALLOWED_EPISODE_CARE_MANAGER_EMPLOYEE_TYPESin case of error return 409 "Employee submitted as a care_manager is not a not in the list of allowed employee types"
PRM.employee.status= "active"
in case of error return 409 "Employee submitted as a care_manager is not active "
PRM.employee.legal_entity = token.client_id=ME.episode.care_manager.identifier.value
in case of error return 409 "User doesn`t have permitions to set the employee as a care_manager of the episode"
...
HTTP status code | Message | What caused the error |
---|---|---|
202 |
|
|
404 |
| |
202 | Response |
|
401 |
| Access token validation failed |
403 |
| Invalid scope |
404 | Patient not found |
|
409 |
| Validation failed |
422 |
| Validation failed |