Table of Contents | ||||
---|---|---|---|---|
|
Required parameters are marked with "*"
...
Purpose
...
This WS allows to get detailed immunization info from Admin panelweb service is designed to return immunizations info by patient_id, episode_id or encouner_id.
Specification
...
Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logic*
Get immunization by id and patient_id
Render detailed Immunization data according to schema
Preconditions
Key points
...
This is a graphQl query used in Administration panel only
...
Only authenticated and authorized NHS employee with appropriate scope can get immunization details.
...
Query returns single immunization by person (mpi id) and immunization identifier.
...
Filtration with forbidden group items not implemented for immunizations, so it not used here.
...
|
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Unique patient identifier |
| |
immunization_id | String | Unique immunization identifier |
|
Request structure
...
API paragraph not found
...
See on Apiary
Authorize
Request to process the request using a token in the headers
Verify the validity of access token
in case of error - return 401 (“Invalid access token”) Return 401 in case of validation fails
Verify that token is not expired
in case of error - return 401 (“Invalid access token”)return 401
Check user scopes in order to perform this action (scope = 'immunization:practical_monitorread')
return 403 (“Your scope does not allow to access this resource. Missing allowances: immunization:practical_monitor”) in case of Return 403 in case invalid scope(s)
Check user has access to resource according to @rule_-2 in ABAC
return 403 (“Access denied. Justification required“) in case of error
Request to process the request using a token in the headers
...
Headers
Наприклад:
Content-Type:application/json
Authorization:Bearer mF_9.B5f-4.1JqM
Validate request*
...
{{access_token}}
API-key:{{secret}}
Request data validation
...
Validate legal entity
Extract client_id from token.
Check client scopes in order to perform this action (scope = 'immunization:practical_monitor')
in case of error - return 403 (“Your scope does not allow to access this resource. Missing allowances: immunization:practical_monitor”)
Check legal entity status (status = ACTIVE)
In case of error - return 409 ('client_id refers to legal entity that is not active')
Validate request
Check required
personId
submitted.return 404 (“not found“) in case not exist
Check required immunization
Id
submitted.return 404 (“not found“) in case not exist or not related to person
...
Access to the resource is also managed by ABAC module
Processing
API paragraph not found
Response structure
...
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
Post-processing processes
...
API paragraph not found
HTTP status codes
...
HTTP status code | Message | What caused the error |
---|---|---|
200 |
|
|
401 |
| Access token validation failed |
403 |
| Invalid scope |