Versions Compared

Version Old Version 14 New Version 15
Changes made by

Serhii.Matiushyn

Nickolay Kolotov (SoE eHealth)

Saved on

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

...

Expand
titleResponse example
Code Block
{
  "data": {
    "status": "pending",
    "eta": "2018-08-02T10:45:16.000Z",
    "links": [
      {
        "entity": "job",
        "href": "/Jobs/NBXk9EyErUZv1RhXgyvgg"
      }
    ]
  },
  "meta": {
    "code": 202,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  }
}

Post-processing processes

API paragraph not found

HTTP status codes
 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
Validation error
422
  • Signed content doesn't match with previously created care plan
Validation error
...