Properties of a REST API method document

Purpose

This API allows to cancel Care plan in cases it has been rejected or entered in error.

Процеси роботи з планом лікування (care plan) | Відміна плану лікування

Key points

1. It can be cancelled by author of the Care plan who has an Approval granted by the patient on write Care plan resource

2. Cancel should be signed with DS. So, all the Care plan data (without activities data) should be submitted.

3. Status of the Care plan changed in async way. The result of the job should be a link on the Care plan details.

Logic

This method must be used to cancel of existing patient's Care plan. Method receives signed message (pkcs7) that consists of signed content, digital signature and signer public key. All signature fields will be validated (including signer certificate authority)

Service logic

1. Save signed content to media storage

2. Update Care plan status (update also updated_at, updated_by)

3. Set $.status_reason and $.status_history

Configuration parameters

Care Plan dictionaries and configurable parameters_UA | Конфігураційні параметри

Medical Events Dictionaries and configurations | ME_ALLOWED_TRANSACTIONS_LE_TYPES

Dictionaries

eHealth/care_plan_categories

eHealth/care_plan_cancel_reasons

eHealth/care_plan_complete_reasons

eHealth/ICD10_AM/condition_codes

PROVIDING_CONDITION

Input parameters

Request structure

See on API-specification

Dummy Cancel Care plan

Headers

Headers

Request data validation

Authorize

1. Verify the validity of access token

   1. Return (401, 'Invalid access token') in case of validation fails

2. Verify that token is not expired

   1. in case of error - return (401, 'Invalid access token')

3. Check user scopes in order to perform this action (scope = 'care_plan:write')

   1. Return (403, 'Your scope does not allow to access this resource. Missing allowances: care_plan:write') in case of invalid scope(s)

Request to process the request using a token in the headers

Validate legal entity

1. Extract client_id from token

2. Check legal entity status is ACTIVE

   1. In case of error - return 409 ('Legal entity must be ACTIVE')

3. Check legal entity type in me_allowed_transactions_le_types config parameter

   1. in case of error - return 409 ('Action is not allowed for the legal entity type')

Validate User

1. Extract user_id from token.

2. Check user has an active and approved employee that:

   1. is specified as Author of the Care plan and has an active Approval granted by the Patient on write the Care plan resource (care plan id from URL)

      1. Return 403 ('Access denied') in case employee has not specified as author of the care plan, or has no Approval on write

Validate data consistency

1. Ensure that submitted Care plan relates to the Patient (from URL)

   1. Return 404 (not found) in case of error

Validate Digital Sign

1. Check DS is valid and not expired

2. Validate that DS belongs to the user

   1. Check that DRFO from DS and user's party.tax_id matches

      1. in case of error - return 409 (“Signer DRFO doesn't match with requester tax_id“)

Validate status transition

1. Get Care plan by id

2. Check status:

   1. Care plan status should be changed according to Care plan status model.

      1. Return 409 ('Care plan in status <cancelled/completed> cannot be cancelled') in case of error

Validate status reason

Validate value in the field $.status_reason, required

1. Validate field type is codeable concept

2. Check that codeable concept refers to eHealth/care_plan_cancel_reasons dictionary

3. Validate value within dictionary specified above

   1. in case of error - return 422 ('value is not allowed in enum')

Validate activities

1. Get Care plan activities

2. Check Care plan has no activities or all activities has final status. 

   1. Return 409 ('Care plan has unfinished activities') in case if found at least one activity not in final status

Validate content

Signed content must match with Care plan in DB in order to be changed

1. Render Care plan from DB

2. Exclude $.status_reason from signed content

3. Compare rendered Care plan and signed content

   1. In case both object doesn't match - return 422 ('Signed content doesn't match with previously created care plan')

Processing

N/A

Response structure examples

See on API-specification

HTTP status codes

Post-processing processes

N/A

Technical modules where the method is used