Table of Contents | ||||
---|---|---|---|---|
|
Required parameters are marked with "*"
...
Purpose*
API paragraph not found
...
Table of Contents | ||||
---|---|---|---|---|
|
Purpose
This method returns details of service request by identifier related to specified episode of care.
Specification
Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logic*
...
|
Filters
Filter | Values | Type | Description |
---|
Example
Example | ||||
---|---|---|---|---|
patient_id | String | Unique patient identifier |
| |
episode_id | String | Unique episode identifier |
| |
service_request_id | String | Unique |
service request identifier |
|
|
|
episode_id
String
Unique episode identifier
ef30f210-5328-4f48-bfe6-c7150d4737a6
service_request_id
String
Unique service request identifier
aff00bf6-68bf-4b49-b66d-f031d48922b3
Request structure*
API paragraph not found
Authorize*
Request to process the request using a token in the headers
...
|
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 mF_9.B5f-4.1JqMapi-key:aFBLVTZ6Z2dON1V{{access_token}}
API-key:{{secret}}
Request data validation
...
API paragraph not found
Processing
...
API paragraph not found
...
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 | |||||||||
---|---|---|---|---|---|---|---|---|---|
|