Table of Contents

minLevel	1
maxLevel	3

Request to process the request using a token in the headers

Headers

Наприклад:

Content-Type:application/json
Authorization:Bearer {{access_token}}
API-key:{{mis_client_secret}}

...

Check DS is valid and not expired
Validate that DS belongs to the user
- Check that DRFO from DS and user's party.tax_id matches
  - in case of error - return 409 (“Signer DRFO doesn't match with requester tax_id“)

Validate status transition

...

Validate field type is codeable concept
Check that codeable concept refers to eHealth/care_plan_cancel_reasons dictionary
Validate value within dictionary specified above
- in case of error - return 422 ('value is not allowed in enum')

Get Care plan activities
Check Care plan has no activities or all activities has final status.
- Return 409 ('Care plan has unfinished activities') in case if found at least one activity not in final status

...

Page Properties

HTTP status code	Message	What caused the error
201	use payload from response	sync
202	use Get job details to get processing result. Response payload will be returned in the job details	async: default method
401	Invalid access token	validation fails token is expired
403	Your scope does not allow to access this resource. Missing allowances: care_plan:write Access denied	invalid scope(s) employee has no Approval on write
404	not found	The submitted Care Plan is not related to the Patient
409	Legal entity must be ACTIVE Action is not allowed for the legal entity type Care plan in status <cancelled/completed> cannot be cancelled Care plan has unfinished activities Signer DRFO doesn't match with requester tax_id	Validation error
422	Signed content doesn't match with previously created care plan value is not allowed in enum	Validation error