Table of Contents | ||||
---|---|---|---|---|
|
Purpose
This method returns details of service request by identifier related to specified episode of care.
Specification
Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Filters
Filter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Unique patient identifier |
| |
episode_id | String | Unique episode identifier |
| |
service_request_id | String | Unique service request identifier |
|
Request structure
See on Apiary
Authorize
...
Verify the validity of access token
Return (401, 'Invalid access token') in case of validation fails
Verify that token is not expired
in case of error - return (401, 'Invalid access token')
Check user scopes in order to perform this action (scope = 'service_request:read')
Return (403, 'Your scope does not allow to access this resource. Missing allowances: service_request:read') in case of invalid scope(s)
Access to the resource is also managed by https://e-health-ua.atlassian.net/wiki/spaces/REHABILIT/pages/17325686977 .
Headers
Наприклад:
Content-Type:application/json
Authorization:Bearer {{access_token}}
API-key:{{secret}}
Request data validation
API paragraph not found
Processing
Get Service request by person_id, episode_id and service_request_id from service_request (MongoDB)
Validate data consistency:
Ensure that requested Service requests have ABAC context
Return 403 ('Access denied') in case of error
Render a response according to specification with found Service requests entities.
Response structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Post-processing processes
API paragraph not found
HTTP status codes
Page Properties | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
...