| Table of Contents | ||||
|---|---|---|---|---|
|
Purpose
Return This web service returns episodes, that patient gave approvals to read by a current employee.
...
| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logic
...
Filters
Filter | Values | Type | Description | Example |
|---|---|---|---|---|
patient_id | String | Patient identifier |
| |
page | Number | Page number |
| |
page_size | Number | A limit on the number of objects to be returned, between 1 and 100. Default: 50 |
| |
code | String | current diagnosis code |
|
Request structure
API paragraph not found
Authorize
Request to process the request using a token in the headers
Headers
Наприклад:
Content-Type:application/json
Authorization:Bearer mF_9.B5f-4.1JqM
api-key:aFBLVTZ6Z2dON1V
Request data validation
...
See on Apiary
Authorize
Request to process the request using a token in the headers
Verify the validity of access token
Return 401 in case validation fails
Verify token is not expired
in case error return 401
Validate scopes
Check user scopes in order to perform this action (scope = 'episode:read')
Return 403 in case invalid scope(s)
Headers
Content-Type:application/json
Authorization:Bearer {{access_token}}
API-key:{{secret}}
Processing
Select list of employees from PRM related to the current user in the current legal_entity, using data from the token
Select all active approvals from Medical Events, where these employees referenced as a `granted_to`
Select all the episodes from ME that are referenced as `granted resources` in the approvals from step 2.
Show episodes to the client ordered by inserted_at
...
HTTP status code | Message | What caused the error |
|---|---|---|
200 |
|
|
401 |
| Access token validation failed |
403 |
| Invalid scope |