/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)
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-001-001-001-0001 |
Microservices (namespace) | MPI |
Component | Auth |
Component ID | COM-001-001 |
Link на API-специфікацію | |
Resource | {{host}}//api.ehealth.gov.ua/api/patients/id/encounter_package |
Scope | |
Protocol type | REST |
Request type | |
Sync/Async | |
Public/Private |
Purpose
This method allows to get composition_configurations that are used for request validation on Create Composition method.
Logic
Service logic
Select composition_configurations records from PRM filtered by type and category from the request
Exclude from composition_configurations.settings json elements where check = “Any”
Return response to the client according to schema
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
Input parameter | Mandatory | Type | Description | Example | |
|---|---|---|---|---|---|
| 1 | composition_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
Headers
Key | Value | Mandatory | Description | Example | |
|---|---|---|---|---|---|
| 1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json |
| 2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9 | M | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 |
| 3 |
|
|
|
|
|
Request data validation
Validate query parameters
Validate required query parameter type is filled
Return 422 ("Required query parameter
typeis missing”) in case of error
Validate value in query parameter type is from COMPOSITION_TYPES dictionary
Return 422 ("Incorrect value for query parameter
type") in case of error
Validate required query parameter category is filled
Return 422 ("Required query parameter category is missing”) in case of error
Validate value in query parameter category is from COMPOSITION_CATEGORIES dictionary
Return 422 ("Incorrect value for query parameter category”) in case of error
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-специфікацією)
Description of the REST API response structure, example
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
|---|---|---|---|---|---|
| 1 | Базові | ||||
| 2 | 401 | Invalid access token | |||
| 3 |
| 401 | Unauthorized |
| Помилка підтвердження |
| 4 | 403 | Your scope does not allow to access this resource. Missing allowances: composition:read | |||
| 5 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
| 6 | 422 | Incorrect value for query parameter | |||
| 7 | 422 | Incorrect value for query parameter category | |||
| 8 | 422 | Required query parameter | |||
| 9 | Специфічні | ||||
| 10 |
| 422 | Only for active MPI record can be created medication request! |
|
|
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
Название | ID ТМ | Статус |
|---|---|---|
TM0112 | ||