Overview
This web service allows to create a new episode of care for a patient.
Note:
|
Specification
Authorization
Validate token
Verify the validity of access token
Return 401 in case validation fails
Verify token is not expired
in case of error return 401
Validate scopes
Check user scopes in order to perform this action (scope = 'episode:write')
Return 403 in case invalid scope(s)
Validate user
If BLOCK_UNVERIFIED_PARTY_USERS is true, then check user's party data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at <= current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):
in case not match - return 403 ("Access denied. Party is not verified")
Request validation
Validate legal entity from token
legal_entities.type in me_allowed_transactions_le_types and legal_entities.status =='active'
Validate patient status
Medical_data status for this patient must be in "active" status
in case of error return 409 - "Patient is not active"
Validate episode id is unique
$.id is unique
in case of error return 422 - "Episode with such id already exists"
Validate request according to Apiary
in case of error return 422
Validate type
according to legal entity type: Medical Events Dictionaries and configurations#legal_entity_episode_types
in case of error return 409 "Episode type <type> is forbidden for your legal entity type"
according to employee type: Medical Events Dictionaries and configurations#employee_episode_types
in case of error return 409 "Episode type <type> is forbidden for your employee type"
Validate managing_organization
Only one item is allowed in coding array
in case of error return 422 "Only one item is allowed in "coding" array"
$.managing_organization.identifier.type.coding.[0].code = "legal_entity"
in case of error return 422 "Only legal_entity could be submitted as a managing_organization"
$.managing_organization.identifier.value = token.client_id
in case of error return 422 "Managing_organization does not correspond to user`s legal_entity"
$.managing_organization.identifier.type.coding.[0].system = "eHealth/resources"
in case of error return 422 "Submitted system is not allowed for this field"
Validate period
$.period.start <= current_date
in case of error return 422 - "Start date of episode must be in past"
$.period.end is absent
in case of error return 422 - "End date of episode could not be submitted on creation"
Validate care_manager
$.care_manager.identifier.type.coding.[0].code = "employee"
in case of error return 422 "Only employee could be submitted as a care_manager"
$.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 = value from list of employee_types in configuration: Medical Events Dictionaries and configurations#ALLOWED_EPISODE_CARE_MANAGER_EMPLOYEE_TYPES
in case of error return 409 "Employee submitted as a care_manager is 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
in case of error return 409 "Employee #{employee_id} doesn't belong to your legal entity"
$.care_manager.identifier.value belongs to one of the user’s employee
in case of error return 422 "<use the same error msg like on encounter.performer>"
Request Processing
Set episodes.care_manager.display_value = ((PRM.parties.first_name + PRM.parties.second_name + PRM.parties.last_name) where PRM.parties.id == PRM.employees.party_id) where PRM.employees.id== $.care_manager.identifier.value
Set episodes.managing_organization.display_value = PRM.legal_entities.public_name where ( PRM.legal_entities.id == $.managing_organization.identifier.value)
Create a record in status_hstr