| Info |
|---|
| Note |
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
| 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
...
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
Provides a list of links to dictionaries that are available in Confluence
Input parameters
...
N/A (Not applicable)
Dictionaries
eHealth/resources - encounter(parameter “encounter_id“ in request)
eHealth/encounter_statuses (parameter “status“ in response)
eHealth/resources - episode (parameter “episode “ 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 (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
...
| title | Example |
|---|
...
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer mF_9.B5f-4.1JqM
...
Authorization:Bearer mF_9.B5f-4.1JqM
Request data validation
Describe the process of checking the input data transmitted in the request for compliance with the given rules and restrictions set in the API
Headers
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 (посилання на сторінку з API-специфікацією)
...
| title | Example |
|---|
...
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
|---|---|---|---|---|---|
| 1 | Базові | ||||
| 2 |
| 200 | Response |
| |
| 3 |
| 401 | |||
Unauthorized
| Access token validation failed |
| |
| 4 |
|
401 |
Composition not found
COMPOSITION_NOT_FOUND_404
Не знайдено медичний висновок
Специфічні
422
| Access token expired |
| |||
| 5 |
| 403 |
| Invalid scope |
|
| 6 |
| 404 | Patient not found |
| |
| 7 | Специфічні | ||||
Post-processing processes
Description of actions performed on data after processingN/A (Not applicable)
Technical modules where the method is used
List of pages describing technical modules where the method is used
...
N/A (Not applicable)