ЕСОЗ - публічна документація
[DRAFT] Get Procedures by search params [API-007-009-001-0304]
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
- 10.1 Validation
- 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-009-001-0304 |
Microservices (namespace) | ME |
Component | Procedure |
Component ID | COM-007-009 |
Link на API-специфікацію | |
Resource | {{host}}/api/patients/{{patient_id}}/procedures |
Scope | procedure:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private | Public |
Purpose
This metod is designed to return records about procedures by patient_id or/and search_params.
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
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 |
|
|
|
|
|
2 |
|
|
|
|
|
Request structure
See on Apiary
See on API-specification
Headers
Key | Value | Mandatory | Description | Example | |
---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json |
2 | Authorization | Bearer {{access_token}} |
|
| Authorization:Bearer {{access_token}} |
3 | API-key | {{secret}} |
|
| API-key:{{secret}} |
Request data validation
Authorize
Request to process the request using a token in the headers
Verify the validity of access token
Return 401 in case validation fails
Verify token is not expired
in case error return 401
Check user scopes in order to perform this action (scope = 'procedure:read')
Return 403 in case invalid scope(s)
Access to the resource is also managed by ABAC module.
Validation
validate person_id
validate $person_id is existing ID in mpi.persons.id And person is_active=true and status='active
in case error return 404, "Person 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 Apiary
See on API-specification
Return response according to json schema
Return procedures where
managing_organization.identifier.value=$Client_id
consumer_id is a doctor with active declaration for current patient ($.person_id)
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 |
| 200 |
|
|
|
3 |
| 401 | Access denied |
|
|
4 |
| 403 | Invalid scopes |
|
|
5 |
| 404 | Patient not found |
|
|
6 |
| 404 | Person not found |
|
|
7 | Специфічні | ||||
8 |
|
|
|
|
|
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical modules where the method is used
ЕСОЗ - публічна документація