ЕСОЗ - публічна документація
[DRAFT] Public. Get Contract printout form [API-005-002-001-0023]
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою.
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
- 9.1 Validate token
- 9.2 Validate scopes
- 9.3 Validate employee
- 9.4 Validate context
- 9.5 Validate data
- 9.6 Extract Printout form
- 10 Processing
- 11 Response structure examples
- 12 HTTP status codes
- 13 Post-processing processes
- 14 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-005-002-001-0023 |
Microservices (namespace) | IL |
Component | Contracts |
Component ID | COM-005-002 |
Link на API-специфікацію | |
Resource | {{host}/api/contracts/{{contract_type}}/{{id}}/printout_content |
Scope | contract:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private | Private |
Purpose
This WS allows to extract Printout form by $contract_id from media storage
Logic
This method is designed to get printout content by contract id. After contract request was signed by both sides signed contract request with printout content was saved to the storage. This WS extract printout content from the storage.
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 | id |
| String | contract identifier |
|
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 token
Verify the validity of access token
Return 401 in case validation fails
token is not expired
in case error return 401
Validate scopes
Check user scopes in order to perform this action (scope = 'contract:read')
Return 403 in case invalid scope(s) -"Your scope does not allow to access this resource. Missing allowances: contract:read"
Validate employee
extract user_id from token
extract client_id from token
Check if user is active
in case error return 403 - "user is not active"
Check nhs_legal_entity is active
in case error return 403 - "Client is not active"
Validate context
extract client_id from token. LE employee can see only this legal entities contracts. NHS employee can see any contracts.
if TOKENS_TYPES_PERSONAL
Check client_id = contracts.contractor_legal_entity_id
in case error return 403 "User is not allowed to perform this action"
Validate data
Validate contract id. Check contracts.id = $.id
in case error return 404 ("Contract with id=$id doesn't exist")
Extract Printout form
search contracts in media storage by contract_request_id
decode base64
return "printout_content"
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 |
|
|
|
|
|
3 |
| 200 |
|
|
|
4 |
| 401 |
|
| Помилка підтвердження |
5 |
| 403 | Client is not active |
|
|
6 |
|
|
|
|
|
7 |
| 403 | user is not active |
|
|
8 |
| 403 | Unauthorized |
|
|
9 |
| 403 | User is not allowed to perform this action |
|
|
10 |
| 403 | Your scope does not allow to access this resource. Missing allowances: contract:read |
|
|
11 |
| 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок |
12 |
| 404 | Contract with id=$id doesn't exist |
|
|
13 | Специфічні | ||||
14 |
| 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
ЕСОЗ - публічна документація