Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel3

...

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}}

...

  • Validate field type is codeable concept

  • Check that codeable concept refers to eHealth/care_plan_complete_reasons dictionary

  • Validate value within dictionary specified above

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

Validate activities

  • Get Care plan activities

  • Check all activities has final status

    • Return 409 (Care plan has scheduled or in-progress activities) in case if activities not in final statuses found

  • Check that Care plan has at least one activity in status=completed

    • Return 409 ('Care plan has no one completed activity') in case if completed activities not found

...

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 scheduled or in-progress activities

  • Care plan has no one completed activity

Validation error

422

  • value is not allowed in enum

Validation error