Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Purpose

...

Page Properties
idAPI_Specification

Link

https://ehealthmedicaleventsapi.docs.apiary.io/#reference/device-requests/create-device-request/create-device-request

Посилання на Apiary або Swagger

Resource

/api/patients/{{patient_id}}/device_requests

Посилання на ресурс, наприклад: /api/persons/create

Scope

device_request:write

Scope для доступу

Components

Devices

Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription

Microservices

Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC

Protocol type

REST

Тип протоколу, який використовується запитом, наприклад: SOAP | REST

Request type

POST

Тип запиту API, наприклад: GET, POST, PATCH…

Sync/Async

Async

Метод є синхронним чи асинхронним?

Public/Private/Internal

Public

Потрібно зазначити тип методу за ступенем доступності

Logic

  • Save signed content to media storage, in bucket pointed in MEDIA_STORAGE_DEVICE_REQUEST_BUCKET chart parameter

  • Fill in the following fields:

    1. requisition. Generate requisition number as described at Human readable Medication request number, but based on the Device Request identifier and put it in the field.

    2. signed_content_links. Add string item in the array with a link on saved content in media storage

    3. status = ACTIVE

    4. status_reason = null

    5. subject. Set hashed patient_id from URL

    6. requester_legal_entity. Set client_id from token

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

    8. dispense_valid_to. dispense_valid_to. Set (current_date + dispense_period_day) if medical program was set and it has dispense_period_day setting. Otherwise, if medical program was set and it has NO dispense_period_day setting, set the value using device_dispense_period global parameter. Else, if medical program was NOT set dispense_valid_to = null.

      1. Save dispense_valid_to as datetime but truncate time to beginning of date (2013-08-02T00:00:00Z)

    9. verification_code. Generate random 4-digit code if medical program was set

    10. context_episode_id. Set episode from the $.encounter

    11. context_care_plan_id. Get Activity from $.based_on, set activity.care_plan as context_care_plan_id

    12. based_on. Set based_on from the $.based_on

    13. priority. Set priority from the $.priority

    14. parameter. Set parameter from the $.parameter

    15. performer. Set performer from the $.performer

    16. supporting_info. Set supporting_info from the $.supporting_info

    17. inserted_at. Set current date and time

    18. updated_at. Set current date and time

    19. inserted_by. Set current user from token

    20. updated_by. Set current user from token

  • Send

...

...

    1. Get program from request and (if provided) get program setting request_notification_disabled:

      1. if program provided and request_notification_disabled == true:

        1. do not send SMS notification to patient

      2. if program provided and request_notification_disabled == false and OTP defined on patient:

        1. generate text according to CREATE_DEVICE_REQUEST_SMS_TEMPLATE and send SMS with verification_code

      3. if program not provided and OTP defined on patient:

        1. check config parameter DEVICE_REQUESTS_SMS_

...

        1. ENABLED is set to true

          1. generate text according to CREATE_DEVICE_REQUEST_SMS_TEMPLATE_WITHOUT_CODE and send SMS

...

...

...

  • 17782014841

  • If device request is based on activity - recalculate and set remaining_quantity for the activity

    1. select all device requests based on current activity and calculate previously reserved quantity as sum of DR.quantity.value.

    2. calculate reserved at the moment quantity as sum of previously reserved quantity and quantity from current DR

    3. calculate remaining quantity by subtracting reserved at the moment quantity from activity's quantity

    4. Update activity set remaining quantity (activity.detail.remaining_quantity)

  • Send StatusChangeEvent to Event

...

  • Manage

Input parameters

Input parameter

Values

Type

Description

Example

patient_id

String

MPI identifier of the person

7075e0e2-6b57-47fd-aff7-324806efa7e5

...

  1. Verify the validity of access token

    • in case of error - return 401 (“Invalid access token”) in case of validation fails

  2. Verify that token is not expired

    • in case of error - return 401 (“Invalid access token”)

  3. Check user and client scopes in order to perform this action (scope = 'device_request:write')

    • return 403 (“Your scope does not allow to access this resource. Missing allowances: device_request:write”) in case of invalid scope(s)

  4. If BLOCK_UNVERIFIED_PARTY_USERS is true, then check party's data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at > current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):

    1. in case not match - return 403 ("Access denied. Party is not verified")

  5. If BLOCK_DECEASED_PARTY_USERS is true, check that party is not deceased (party_verification record does not equal to: dracs_death_verification_status = VERIFIED and dracs_death_verification_reason = MANUAL_CONFIRMED):

    1. in case of error - return 403 ("Access denied. Party is deceased")

Headers

...

...

Authorization:Bearer mF_9.B5f-4.1JqM

...

api-key:aFBLVTZ6Z2dON1V

Request data validation

Validate digital signature

  1. Validate request is signed

    1. in case of error - return 400 (“Invalid signed content”)

  2. Check DS is valid and not expired

  3. Validate that DS belongs to the requester

    1. Check that DRFO from DS and party.tax_id matches

      1. in case of error - return 422 (“Signer DRFO doesn't match with requester tax_id“)

Validate requester

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#1.-Validate-requester

Validate based on

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#2.-Validate-based-on

Validate intent

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#3.-Validate-intent

Validate legal entity

  • Extract client_id from token

  • Check legal entity status is ACTIVE

    • In case of error - return 409 ('client_id refers to legal entity that is not active')

  • Check legal entity type in ME_ALLOWED_TRANSACTIONS_LE_TYPES config parameter

    • in case of error - return 409 ('client_id refers to legal entity with type that is not allowed to create medical events transactions')

...

  1. Validate $.status is active

    1. in case of error - return 422 ("value is not allowed in enum")

Response structure

See on Apiary

Example:

...

titleResponse example

...

Validate code or code_reference

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#4.-Validate-code-or-code_reference

Skip the following validation in case madical_program is not specified in the request

Note
  • Check that there is at least one active device_definition with the same type (device_definitions.classification_type)

    • device_definitions.is_active = true

      • in case of error - return 422 ('No active device_definitions with the same type')

Validate quantity

Info

If medical program is not specified in request then quantity is optional here

If quantity provided in request - execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#5.-Validate-quantity

  • Check that $.quantity.system is device_unit dictionary, required

    • in case of error - return 422 ('value is not allowed in enum')

  • Check that $.quantity.code comply with $.quantity.system, required

    • in case of error - return 422 ('value is not allowed in enum')

  • Check that $.quantity.value is integer, required

    • in case of error - return 422 ('Value should be an integer')

Validate encounter

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#6.-Validate-encounter

Validate authored on

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#7.-Validate-authored-on

Validate occurrence

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#8.-Validate-occurrence

Validate reason

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#9.-Validate-reason

Validate Package unit and quantity

Info

If medical program is not specified in request then skip this step

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#5.-Validate-quantity

Validate Medical program

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#10.-Validate-Medical-programs

Validate priority

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#11.-Validate-priority

Validate supporting info

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#12.-Validate-supporting-info

Validate performer

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#13.-Validate-performer

Validate parameter

Execute validation as described here

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17573085395/PreQualify+Device+request#14.-Validate-parameter

Response structure

See on Apiary

Example:

Expand
titleResponse example

HTTP status codes

Page Properties
idAPI_HTTP status codes

HTTP status code

Message

What caused the error

 202

 

 

...