| 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 current diagnoses related only to active episodes.
Logic
This endpoint returns current diagnoses related only to active episodes. In order to get specific condition details, use Get Condition by ID
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 ConfluenceN/A (Not applicable)
Dictionaries
eHealth/resources - condition (parameter “condition“ in response)
eHealth/ICPC2/condition_codes or eHealth/ICD10/condition_codes (parameter “code“ in request/response)
eHealth/diagnosis_roles (parameter “role“ in response)
Input parameters
...
Headers
Key
Value
Mandatory
Description
Example
Content-Type
application/json
M
Тип контенту
Content-Type:application/json
Authorization
Bearer mF_9.B5f-4.1JqM
Input parameter | Mandatory | Type | Description | Example | |
|---|---|---|---|---|---|
| 1 | 2 |
Request structure
See on API-specification
...
| title | Example |
|---|
patient_id | M | String | Unique MPI patient identifier |
| |
| 2 | code |
| String | Diagnose code |
|
| 3 | page |
| Number | Page number |
|
| 4 | 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
Request data validation
Authorize
Request to process the request using a token in the headers
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
...
...
| Code Block |
|---|
{
"meta": {
"code": 200,
"url": "http://example.com/resource",
"type": "object",
"request_id": "req-adasdoijasdojsda"
},
"data": [
{
"condition": {
"identifier": {
"type": {
"coding": [
{
"system": "eHealth/resources",
"code": "condition"
}
]
},
"value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
},
"display_value": "null"
},
"code": {
"coding": [
{
"system": "eHealth/ICPC2/conditions",
"code": "A20"
}
]
},
"role": {
"coding": [
{
"system": "eHealth/diagnosis_roles",
"code": "CC"
}
]
},
"rank": 1
},
{
"condition": {
"identifier": {
"type": {
"coding": [
{
"system": "eHealth/resources",
"code": "condition"
}
]
},
"value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
},
"display_value": "null"
},
"code": {
"coding": [
{
"system": "eHealth/ICPC2/conditions",
"code": "A20"
}
]
},
"role": {
"coding": [
{
"system": "eHealth/diagnosis_roles",
"code": "CC"
}
]
},
"rank": 1
}
],
"paging": {
"page": 2,
"page_size": 50,
"total_entries": 1000,
"total_pages": 20
}
} |
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | ||
|---|---|---|---|---|---|---|
| 1 | Базові | |||||
| 2 | 200 | |||||
| 3 | Специфічні | |||||
| 4 |
| 200 |
| Response |
| |
| 3 |
| 401 |
| Access token validation failed |
| |
| 4 |
| 401 |
| 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)