Table of Contents | ||||
---|---|---|---|---|
|
Purpose
...
API paragraph not found
...
This method returns the details of the service request by identifier. without specifying the episode of care
Specification
Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logic*
...
|
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Unique patient identifier |
| |
service_request_id | String | Unique service request identifier |
|
Request structure
...
API paragraph not found
...
See on Apiary
Authorize
Verify the validity of access token
Return (401, 'unauthorized') in case of validation fails
Verify that token is not expired
in case of error - return (401, 'unauthorized')
Check user scopes in order to perform this action (scope = 'service_request:read')
Return (403, 'invalid scopes') in case of invalid scope(s)
Request to process the request using a token in the headers
...
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.1JqM{token}
api-key: aFBLVTZ6Z2dON1V{secret}
Request data validation
...
API paragraph not found
Processing
...
API paragraph not found
...
Get Service request by person_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 | |||||||||
---|---|---|---|---|---|---|---|---|---|
|