...

1. Only authenticated and authorized users with appropriate scope can invoke Create Device Dispense

2. Device Dispense is created in async way. Successful result of the job should return a link on the created Device Dispense (look at /wiki/spaces/CSI/pages/17467506869 ).

3. Device Dispense can be created only under active Device Request within valid dispense period

4. Several devices of different manufacturers with the same code can be dispensed at a time

5. Multiple dispenses to the same Device Request is not allowed

6. It is allowed to create Device Dispense for not active or not verified persons (for the same reasons as in the medication reimbursement process)

Specification

...

Page Properties
id API_Specification
Link Посилання на Apiary або Swagger Resource Посилання на ресурс, наприклад: /api/persons/create Scope Scope для доступу Components Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription Microservices Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC Protocol type Тип протоколу, який використовується запитом, наприклад: SOAP | REST Request type Тип запиту API, наприклад: GET, POST, PATCH… Sync/Async Метод є синхронним чи асинхронним? Public/Private/Internal Потрібно зазначити тип методу за ступенем доступності

Logic

• Fill in the following fields:

  • status = IN_PROGRESS

  • status_reason = null

  • subject. Set hashed patient_id from URL

  • performer_legal_entity. Set client_id from token

  • quantity.unit. Set description according to quantity code and system

  • inserted_at. Set current date and time

  • updated_at. Set current date and time

  • inserted_by. Set current user from token

  • updated_by. Set current user from token

• Save data to device_dispenses collection in MongoDB according to /wiki/spaces/CSI/pages/17467572335

• Send StatusChangeEvent to Event Manager

...