Table of Contents | ||||
---|---|---|---|---|
|
Required parameters are marked with "*"
...
Purpose
API paragraph not found”.
...
This WS allows to get detailed condition info from Admin panel.
Specification
...
Page Properties | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Project Name | COVID-certificate | ||||||||||||||||||||||||||||||||
Project abreviation | SVC | ||||||||||||||||||||||||||||||||
Developer | Розробник методу API. Наприклад, Edenlab | Project Manager | @Єлизавета Гессен-Дармштадська|||||||||||||||||||||||||||||||
Version 1.0 Date of release Link https://ehealthmedicaleventsapimedicaleventsmisapi.docs.apiary.io/#reference/medical-events/patient-summary/get-condition-by-id Resource /api/patients/{{patient_id}}/summary/conditions/{{id}} Scope patient_summary:read Components Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescriptionPatient Summary Microservices Перелік мікросервісів, які використовує метод API. Наприклад: Auth, ABACAPI paragraph not found Protocol type Тип протоколу, який використовується запитом, наприклад: SOAP | REST Request type GET Sync/Async Метод є синхронним чи асинхронним? |
...
|
Logic
API paragraph not found
Preconditions
Key points
...
This is a graphQl query used in Administration panel only
...
Only authenticated and authorized NHS employee with appropriate scope can get condition details.
...
Query returns single condition by person (mpi id) and condition identifier.
...
Filtration with forbidden group items is worked here. So NHS employee should have an approval from patient to see a condition with forbidden elements.
...
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Unique patient identifier |
| |
id | String | Unique condition identifier |
|
Request structure
...
API paragraph not found
Authorize
...
Verify the validity of access token
in case of error - return 401 (“Invalid access token”) in case of validation fails
Verify that token is not expired
...
...
Check user scopes in order to perform this action (scope = 'condition:practical_monitor')
return 403 (“Your scope does not allow to access this resource. Missing allowances: condition:practical_monitor”) in case of 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
...
Request data validation
API paragraph not found
Request data validation*
Validate legal entity
Extract client_id from token.
Check client scopes in order to perform this action (scope = 'condition:practical_monitor')
in case of error - return 403 (“Your scope does not allow to access this resource. Missing allowances: condition: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 condition
Id
submitted.return 404 (“not found“) in case not exist or not related to the person
return 403 (“Access denied“) in case condition has forbidden group items. Take into account approvals granted to NHS employee on forbidden groups (look at Medical Events filtration by Forbidden groups for details)
Processing*
Service logic
Get condition by id and patient_id
Render detailed condition data according to schema
...
Processing
API paragraph not found
Response structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
Post-processing processes
...
API paragraph not found
HTTP status codes
...
Page Properties | ||||||
---|---|---|---|---|---|---|
|
...