Required parameters are marked with "*"
...
Purpose*
Table of Contents |
---|
Purpose
Use this method to obtain a list of Declaration Requests for an empolee_id
.
Key features
Only authenticated and authorized user can use declaration requests
Specification
...
Link | Apiaryhttps://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/declaration-requests/get-declaration-requests-list-v3 |
Resource | /api/v3/declaration_requests |
Scope | declaration_request:read |
Components | Необхідно зазначити перелік компонентів, які використовують цей метод, наприклад: ePrescription |
Using Dictionaries | Потрібно вказати словники, які використовує метод API |
Using Microservices | Вкажіть перелік мікросервісів, які використовує метод API. Наприклад: Auth, ABACDeclarations |
Microservices | API paragraph not found |
Protocol type | Вкажіть тип протоколу, який використовується запитом, наприклад: SOAP | REST | JSON |
Request type | GET |
Sync/Async | Метод є синхронним чи асинхронним? |
Logic*
Only authenticated and authorized user can use declaration requests
If you want to reduce amount of data that is going trough your application, use status
filter and show only requests that Doctor or Admin is interested in current UI section.
Also we suggest use employee_id
and legal_entity_id
to make sure that end-user understands context of actions that he or she will perform.
Method returns shortened details, to obtain full information - get Declaration Request it by it's ID.
Important
...
API paragraph not found | |
Public/Private/Internal | Public |
Logic
API paragraph not found
Filters
Filter | Values | Type | Description | Example |
---|---|---|---|---|
employee_id |
| String | user_id of a doctor |
|
legal_entity_id | String | MSP ID |
| |
status |
| Enum |
|
|
page | Number | Page number | 2 | |
page_size | Number | A limit on the number of objects to be returned, between 1 and 100. Default: 50 | 50 |
Request structure
...
API paragraph not found
Authorize
...
Verify the validity of access token
Return 401 in case validation fails
Check scopes in order to perform this action (scope = 'declaration_request:read')
Return 403 in case invalid scope(s)
Request to process the request using a token in the headers.
Headers
...
Content-Type:application/json
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
Validate request (JSON schema)*
Наприклад:
Validate request using JSON schema
In case validation failed - generate 422 error
...
title | JSON schema |
---|
...
Validation data request
...
API paragraph not found
Processing
...
API paragraph not found
Response structure
...
Expand | ||
---|---|---|
| ||
|
Post-processing processes
...
API paragraph not found
HTTP status codes
HTTP status code | Message | What caused the error | 200|
---|---|---|---|
200 | Response |
| |
401 |
| Access token validation failed | |
403 |
| Invalid scope |
Backward compatibility
This endpoint returns declaration requests that were created through V2 and V3. Field person_id
will be empty for declaration request V2.