1 Purpose
2 Specification
3 Logic
4 Input parameters
5 Request structure
6 Authorize
7 Headers
8 Request data validation
- 8.1 Validate legal entity
- 8.2 Validate equipment
- 8.3 Validate request
9 Processing
- 9.1 Update object in DB
  - 9.1.1 1. equipment table
10 Response structure
11 HTTP status codes

Purpose

This method used for update equipment data, except link with division and status

Specification

Link	https://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/equipment/update-equipment	Посилання на Apiary або Swagger
Resource	/api/equipment/{{id}}	Посилання на ресурс, наприклад: /api/persons/create
Scope	equipment:write	Scope для доступу
Components	Devices and equipment	Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription
Microservices	API paragraph not found	Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC
Protocol type	REST	Тип протоколу, який використовується запитом, наприклад: SOAP \| REST
Request type	PATCH	Тип запиту API, наприклад: GET, POST, PATCH…
Sync/Async	Sync	Метод є синхронним чи асинхронним?
Public/Private/Internal	Public	Потрібно зазначити тип методу за ступенем доступності

Logic

Only authenticated and authorized HR, ADMIN, OWNER employees can update equipment.
Equipment can be updated from MSP, OUTPATIENT, PRIMARY_CARE and EMERGENCY legal entities.
Only ACTIVE equipment can be updated.
Update of division_id and status is not allowed with this service.
Legal entity can update only its own equipments.

Input parameters

Input parameter	Values	Type	Description	Example

Input parameter	Values	Type	Description	Example
id		String	Equipment identifier. Required	d290f1ee-6c54-4b01-90e6-d701748f0851

Request structure

Example:

{
  "type": "23143534",
  "external_id": "123-ASD-#1",
  "udi": [
    {
      "value": "IMEI 49015420323751",
      "type": "default",
      "assigner_name": "Ukrainian center of the certification"
    }
  ],
  "lot_number": "RZ12345678",
  "manufacturer": "GlobalMed, Inc",
  "manufacture_date": "1999-01-01",
  "expiration_date": "2020-01-01",
  "model_number": "NSPX30",
  "part_number": "#e30-SD",
  "version": "v1.0.1",
  "name": "Рентген апарат флюрографічній",
  "serial_number": "S/N234554",
  "note": "Технічний огляд раз на рік"
}

Authorize

Verify the validity of access token
1. Return 401 in case validation fails
Check user scopes in order to perform this action (scope = 'equipment:write')
1. Return 403 in case invalid scope(s)

Headers

Наприклад:

Content-Type:application/json

Authorization:Bearer c2778f3064753ea70de870a53795f5c9

api-key:uXhEczJ56adsfh3Ri9SUkc4en

Request data validation

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)
1. In case of error - return 409 (Legal entity must be ACTIVE or SUSPENDED)

Validate equipment

Check that ID in URL exists in the system
1. In case of error - return 404
Check that equipment belongs to the same legal entity as the user
1. In case of error - return 403

Validate request

Validate request using schema

Processing

Update object in DB

1. equipment table

Parameter	Source	Description

Parameter	Source	Description
type	Request: type	Get from request body
external_id	Request: external_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
updated_at	Timestamp: now()	Get current date-time
updated_by	Token: user_id	Extract user from token

Response structure