...

Specification

...

Returns care plan's activity details by it's identifier within care plan and patient context

Input parameters

Dictionaries

eHealth/care_plan_activity_outcomes

...

Request structure

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:read')

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

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

Request data validation

Validate Patient

1. Get Patient identifier from the URL

2. Check it exists in DB

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

Validate Care plan

1. Get Care plan identifier from the URL

2. Check it exists in DB

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

Validate User

1. Extract user_id from token.

2. Check user has an active and approved employee from legal entity (token) for which one of the conditions is TRUE:

   1. has an active Approval granted by the Patient on write or read the Care plan resource (care plan id from URL)

      1. Return 403 ('Access denied') in case employee has no Approval on read or write

   2. has an active declaration with the patient

      1. Return 403 ('Access denied') in case there no active declaration with patient and none of other conditions is true

   3. user belongs to the legal entity where the care_plans were created

      1. Return 403 ('Access denied') in case employee belongs to another legal_entity and none of conditions above is true

Response structure

See on Apiary

...