REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
Properties of a REST API method document
Purpose
This service returns a list of all active legal entities of all types (except MIS) filtering result by query parameters
Logic
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
Check user context
Return response to user limited by context from user's token
Token type | Limitation |
---|---|
TOKENS_TYPES_PERSONAL | Limited by Legal Entity (ID) |
TOKENS_TYPES_MIS | No limitations |
TOKENS_TYPES_ADMIN | No limitations |
Processing
Get legal entities
Invoke PRM.Legal Entities List
By default service returns legal entities with type - MSP
Service return only active legal_entities, where is_active = true
If settlement_id passes as input parameter - legal entities should be filtered by setllement_id in residence address only
Method returns list of objects with short details from PRM DM legal_entity table and pagination information.
For each legal entity return in response:
legal entity details from legal_entities table and from edr_data table
licenses from licenses table
services from capitation_contract table
addresses from legal_entity table
phones from legal_entity table
emails from legal_entity table
founders from legal_entity table
If according to filters Legal Entities are not found, WS returns empty data array.
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 | 200 | Response | |||
3 | 401 | Unauthorized | Помилка підтвердження | ||
4 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
5 | Специфічні | ||||
6 | 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