| 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
This web service is designed to return conditions by episode_id or encouner_id.
Logic
Description of the working algorithm of the API method and the interaction of services with each other add Service logic (if necessary)
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
Description of input parameters
Configuration parameters
N/A (Not applicable)
Dictionaries
eHealth/resources - employee (parameter “asserter“ in response)
eHealth/report_origins (parameter “patient“ in response)
eHealth/resources - encounter (parameter “context“ in response)
eHealth/ICD10/condition_codes(parameter “code“ in response)
eHealth/condition_clinical_statuses (parameter “clinical_status“ in response)
eHealth/condition_verification_statuses (parameter “verification_status“ in response)
eHealth/condition_severities (parameter “severity“ in response)
eHealth/body_sites(parameter “body_sites“ in response)
eHealth/condition_stages(parameter “body_sites“ in response)
eHealth/ICPC2/reasons(parameter “evidences:codes“ in response)
eHealth/resources - observations (parameter “evidences:details“ in response)
Input parameters
Input parameter | Mandatory | Type | Description | Example | ||
|---|---|---|---|---|---|---|
| 1 | compositionpatient_id | M | String ($uuid) (path) | Composition object ID | 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59 | 2 |
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
Unique MPI patient identifier |
| ||||
| 2 | code |
| String | Condition code |
|
| 3 | onset_date_time_from |
| String |
|
|
| 4 | onset_date_time_to |
| String |
|
|
| 5 | page |
| Number | Page number |
|
| 6 | page_size |
| Number | A limit on the number of objects to be returned, between 1 and 100. Default: 50 |
|
Request structure
See on API-specification
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 = 'condition:read')
Return 403 in case invalid scope(s)
Access to the resource is also managed by ABAC module
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 ApiarySee 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 | 1000 | 404401 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | |
| 5 | Специфічні | |||||
| 6 | 422 | Only for active MPI record can be created medication request! | 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)