| Note |
|---|
| Info |
REST API method / Метод REST API (настанова) Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
| Info |
|---|
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
| Table of Contents |
|---|
Properties of a REST API method document
| Page Properties | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Purpose
Return single short Encounter info
Logic
The endpoint returns single short Encounter info
Configuration parameters
N/A (Not applicable)
Dictionaries
eHealth/resources - encounter(parameter “encounter_id“ in request)
eHealth/encounter_statuses (parameter “status“ in response)
eHealth/encounter_typesresources - episode (parameter “typeepisode “ in response)
eHealth/encounter_classes (parameter “class“ in response)
eHealth/encounter_types (parameter “type“ in response)
SPECIALITY_TYPE (parameter “performer_speciality“ in response)
Input parameters
Input parameter | Mandatory | Type | Description | Example | |
|---|---|---|---|---|---|
| 1 | patient_id | M | String | Unique patient identifier |
|
| 2 | encounter_id | M | String | Unique encounter identifier |
|
Request structure
See on API-specification
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer {{access_token}}
...
M
...
Перевірка користувача
...
Authorization:Bearer {{access_token}}
...
api-key
...
{{secret}}
...
...
Секретний ключ
...
api-key:{{secret}}
...
X-Custom-PSK
...
{{secret}}
...
...
Секретний ключ МІС
...
X-Custom-PSK:{{secret}}
See on Headers
Request data validation
Authorize
Request to process the request using a token in the headers
Validate token
Verify the validity of access token
Return 401 in case validation fails
Verify token is not expired
in case error return 401
Validate scopes
Check user scopes in order to perform this action (scope = 'patient_summary:read')
Return 403 in case invalid scope(s)
Validate patient
Validate patient exists in MongoDB
In case of error return 404 not found
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
...
See on API-specification
...
| title | Example |
|---|
...
...
{
"data": {
"id": "465fb6fe-2dea-4b8a-9ef7-58379d1eaab0",
"status": "finised",
"date": "2018-08-02T10:45:16.000Z",
"episode": {
"identifier": {
"type": {
"coding": [
{
"system": "eHealth/resources",
"code": "episode"
}
]
},
"value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
}
},
"class": {
"system": "eHealth/encounter_classes",
"code": "inpatient"
},
"type": {
"coding": [
{
"system": "eHealth/encounter_types",
"code": "discharge"
}
]
},
"performer_speciality": {
"coding": [
{
"system": "SPECIALITY_TYPE",
"code": "VIROLOGY"
}
]
}
},
"meta": {
"code": 200,
"url": "http://example.com/resource",
"type": "object",
"request_id": "req-adasdoijasdojsda"
}
}HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Базові | |||||||||||||||
| 2 |
| 200 | Response Response |
|
| |||||||||||
| 3 |
| 401 |
| Access token validation failed |
| |||||||||||
| 4 |
| 401 |
| Access token expired |
| |||||||||||
| 5 |
| 403 |
| Invalid Invalid scope |
| |||||||||||
| 6 |
| 404 | Patient Patient not found |
|
| |||||||||||
| 7 | 8 | Специфічні | 9 |
|
|
|
| |||||||||
Post-processing processes
N/A (Not applicable)
Technical modules where the method is used
N/A (Not applicable)