ЕСОЗ - публічна документація
[DRAFT] Create equipment [API-007-002-002-0232]
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою.
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 Validate legal entity
- 10.2 Validate request
- 10.3 Validate division
- 10.4 Validate type
- 10.5 Validate external identifier
- 11 Processing
- 11.1 Save object to DB
- 11.1.1 1. equipments table
- 11.1.2 2. equipment_status_hstr table
- 11.1 Save object to DB
- 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 | [DRAFT] Create equipment [API-007-002-002-0232] |
Guideline ID | GUI-0011 |
Author | @ |
Document version | 1 |
Document status | DRAFT |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-007-002-002-0232 |
Microservices (namespace) | ME |
Component | Devices and equipment |
Component ID | COM-007-002 |
Link на API-специфікацію | |
Resource | {{host}}/api/equipment |
Scope | equipment:write |
Protocol type | REST |
Request type | POST |
Sync/Async | Sync |
Public/Private | Public |
Purpose
This WS is designed for registration equipment in divisions of legal entities
Logic
Only authenticated and authorized HR, ADMIN, OWNER employees can register equipments.
Equipments can be registered in MSP, OUTPATIENT, PRIMARY_CARE and EMERGENCY legal entities.
Equipment has to be linked to division. One division can have many equipments.
Legal entity can register equipments for its own divisions only.
Configuration parameters
N/A
Dictionaries
N/A
Input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 |
|
|
|
|
|
2 |
|
|
|
|
|
Request structure
See on API-specification
Headers
https://e-health-ua.atlassian.net/wiki/spaces/ESOZ/pages/18415648793
Request data validation
Authorize
Verify the validity of access token
Return 401 in case validation fails
Check user scopes in order to perform this action (scope = 'equipment:write')
Return 403 in case invalid scope(s)
Validate legal entity
Check that legal entity is active (status = ACTIVE, SUSPENDED)
Extract client_id from token (token.client_id == legal_entity_id)
Check legal entity status (status = ACTIVE, SUSPENDED)
In case of error - return 409 (Legal entity must be ACTIVE or SUSPENDED)
Validate request
Validate request using schema
Validate division
A division_id should be passed in request body:
Validate division_id in request body - division exists and is_active = true
Return 422 in case validation fails
Check division_id belongs to the same legal_entity_id (from token) as the user
Return 422 with message "Division is not within current legal entity" in case validation fails.
Check division status =ACTIVE.
Return 422 with message "Division is not active" in case validation fails.
Validate type
Validate that an equipments type value exists in dictionary "EQUIPMENT_TYPE"
in case of error "Submitted code is not allowed for this field"
Validate external identifier
Check an external_id field is not empty
Return 422 (required property external_id was not present) in case of error
Processing
Save object to DB
1. equipments table
Parameter | Source | Description |
---|---|---|
id | UUID | Autogenerated |
type | Request: type | Get from request body |
external_id | Request: external_id | Get from request body |
division_id | Request: division_id | Get from request body |
udi | Request: udi | Get from request body |
lot_number | Request: lot_number | Get from request body |
manufacturer | Request: manufacturer | Get from request body |
manufacture_date | Request: manufacture_date | Get from request body |
expiration_date | Request: expiration_date | Get from request body |
model_number | Request: model_number | Get from request body |
part_number | Request: part_number | Get from request body |
version | Request: version | Get from request body |
name | Request: name | Get from request body |
serial_number | Request: serial_number | Get from request body |
note | Request: note | Get from request body |
legal_entity_id | Token: client_id | Extract client from token |
status | Const: ACTIVE | By default ACTIVE for new records |
is_active | Const: TRUE | Always TRUE for new records |
inserted_at | Timestamp: now() | Get current date-time |
inserted_by | Token: user_id | Extract user from token |
updated_at | Timestamp: now() | Get current date-time |
updated_by | Token: user_id | Extract user from token |
2. equipment_status_hstr table
Parameter | Source | Description |
---|---|---|
id | UUID | Autogenerated |
equipment_id | UUID | Reference to equipments.id |
status | Const: ACTIVE | By default ACTIVE for new records |
inserted_by | Token: user_id | Extract user from token |
inserted_at | Timestamp: now() | Get current date-time |
Response structure examples
See on API-specification
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 |
| 201 | Response |
|
|
3 |
| 401 |
| Access token validation failed |
|
4 |
| 403 |
| Invalid scope(s) |
|
5 |
| 409 |
| Validation failed |
|
6 |
| 409 | Legal entity must be ACTIVE or SUSPENDED |
|
|
7 |
| 422 |
| Validation failed |
|
8 |
| 422 | Division is not within current legal entity |
|
|
9 |
| 422 | Division is not active |
|
|
10 |
| 422 | required property external_id was not present |
|
|
11 | Специфічні | ||||
12 |
|
|
|
|
|
Post-processing processes
N/A
Technical modules where the method is used
ЕСОЗ - публічна документація