ЕСОЗ - публічна документація
[DRAFT] Get Diagnostic Report by search params (Patient Summary) [API-007-008-006-0288]
https://e-health-ua.atlassian.net/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)
- 1 Properties of a REST API method document
- 2 Purpose
- 3 Logic
- 4 Configuration parameters
- 5 Dictionaries
- 6 Input parameters
- 7 Request structure
- 8 Headers
- 9 Request data validation
- 10 Authorize
- 11 Processing
- 12 Response structure examples
- 13 HTTP status codes
- 14 Post-processing processes
- 15 Technical modules where the method is used
Properties of a REST API method document
Document type | Метод REST API |
---|---|
Document title | [Document status] REST API [Назва методу] [ID методу] |
Guideline ID | GUI-0011 |
Author | @ |
Document version | 1 |
Document status | DRAFT |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-007-008-006-0288 |
Microservices (namespace) | ME |
Component | Patient Summary |
Component ID | COM-007-008 |
Link на API-специфікацію | |
Resource | {{host}}/api/patients/{{patient_id}}/summary/diagnostic_reports/ |
Scope | patient_summary:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Async |
Public/Private | Public |
Purpose
Describe the purpose of the API method, add Key points (if necessary)
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
Dictionaries
eHealth/resources - service_request (parameter “based_on“ in response)
eHealth/diagnostic_report_statuses (parameter “status“ in request / response)
eHealth/resources - service (parameter “code“ in request / response)
eHealth/diagnostic_report_categories (parameter “category“ in response)
eHealth/ICD10_AM/condition_codes (parameter “conclusion_code“ in response)
eHealth/resources - specimen (parameter “specimens“ in response)
eHealth/resources - equipment (parameter “used_references“ in response)
eHealth/resources - employee (parameter “recorded_by“ in response)
eHealth/resources - encounter (parameter “encounter“ in response)
eHealth/resources - episode (parameter “origin_episode“ in response)
eHealth/resources - division (parameter “division“ in response)
eHealth/resources - legal_enity (parameter “managing_organization“ in response)
eHealth/resources - employee (parameter “performer“ in response)
eHealth/report_origins (parameter “report_origin“ in response)
eHealth/resources - employee (parameter “results_interpreter“ in response)
eHealth/cancellation_reasons (parameter “cancellation_reason“ in response)
Input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | patient_id | M | String | Unique MPI patient identifier |
|
2 | issued_from |
| String |
|
|
3 | issued_to |
| String |
|
|
4 | code |
| String | Service code |
|
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
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
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 |
| 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
N/A (Not applicable)
Technical modules where the method is used
N/A (Not applicable)
ЕСОЗ - публічна документація