Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
REST API method / Метод REST API (настанова)
Info
Note

Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою.

Info

/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)

Table of Contents

Properties of a REST API method document

Page Properties
idpage_properties_method_REST API

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-008-002-0158

Microservices (namespace)

IL

Component

ePrescription

Component ID

COM-005-008

Link на API-специфікацію

https://ehealthmisapi1.docs.apiary.io/#reference/public.-reimbursement/medication-request/block-medication-request-by-pharmacy-user

Resource

{{host}}/api/pharmacy/medication_requests/{{id}}/actions/block

Scope

medication_request:block_pharm

Protocol type

REST

Request type

PATCH

Sync/Async

Sync

Public/Private

Public

Purpose

This WS is designed to block previously created Medication request with indicating block_reason_code and block_reason.

Key points

  1. Only authenticated and authorized user with appropriate scope and ‘PHARMACIST’ employee can block Medication request.

  2. In the response of this endpoint legal entity, division and employee details are trimmed.

  3. Medication request can be blocked only from ‘ACTIVE' status.

Logic

Service logic

  1. Service logic

    1. Update Medication request in OPS DB:

      1. set is_blocked = true

      2. set blocked_to = $.blocked_to OR $.medication_request.dispense_valid_to date + 23:59 time (in case blocked_to is absent in request)

      3. set blocked_by_legal_entity_id = legal_entity_id (client_id) from token

      4. set block_reason_code = $.block_reason_code

      5. set block_reason = $.block_reason

      6. set updated_by = user_id

      7. set updated_at = now()

    2. Send SMS for person

      1. If Medication request has program with medical program setting medication_request_notification_disabled = true, then don't send SMS.

        Else:

        1. Get authentication_method of person from MPI

        2. If authentication_method == OTP, then send SMS to a person from Medication request:

          1. Generate SMS text

            1. get template from block_template_sms parameter

            2. enrich template with data from Medication request

          2. Send SMS to a person

  2. Return Medication request data with trimmed information about legal entity, division and employee

  3. Add new record in Event manager:

field

value

event_type

StateChangeEvent

entity_type

MedicationRequest

entity_id

$.id

properties.is_blocked.new_value

true

event_time

$.update_at

changed_by

$.changed_by

 

Configuration parameters

No

Dictionaries

Input parameters

Description of input parameters

Input parameter

Mandatory

Type

Description

Example

1

id

 M

String

Medication Request identifier

 d290f1ee-6c54-4b01-90e6-d701748f0851

Request structure

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API request structure, example

Expand
titleExample
Code Block

Request data validation

Authorization

  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 scopes in order to perform this action (scope = 'medication_request:block_pharm')

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

Validate request

  • Validate request using JSON schema

    • in case of error - return 422

Validate Medication request

  • Get Medication request identifier from the URL. Check Medication request exists in OPS DB

    • in case of error - return 404 (“Medication request does not exist")

Validate user

Medication Request blocking is allowed for user if he has active and approved employee with employee_type = ‘PHARMACIST’

  • in case of error - return 409 ("Only pharmacist can block medication request")

Validate legal_entity

If MR still blocked (blocked_to > now()) and MR.blocked_by_legal_entity_id is not null - check that match with client_id from token

  • in case of error - return 409 ("It is not allowed to block medication request that has been blocked from another legal entity")

Validation transition

  • Get Medication request by $.id in OPS DB. Check that Medication request status = ‘ACTIVE’

    • in case of error - return 409 ("Medication request must be in active status")

  • Get Medication request by $.id in OPS DB. Check that Medication request is not blocked, i.e. is_blocked = false

    • in case of error - return 409 ("Medication request is already blocked")

Validate block reason code

  • Validate $.block_reason_system should be “MEDICATION_REQUEST_BLOCK_REASON

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

  • Validate $.block_reason_code is a value from MEDICATION_REQUEST_BLOCK_REASON dictionary

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

  • Check that $.block_reason_code is present in PHARMACIST_MEDICATION_REQUEST_BLOCK_REASON_CODES chart parameter for validated user

    • in case of error - return 422 ("Block reason code is not allowed for PHARMACIST")

Validate blocked_to

  • Validate $.blocked_to > now() (datetime)

    • in case of error - return 422 ("Blocked_to date should be greater than the current date")

  • Validate $.blocked_to <= $.medication_request.dispense_valid_to

    • in case of error - return 422 ("Blocked_to date should be equal to or less than the dispense validity end date")

Validate medical program

It must be allowed to block medication request only in case of such medication request is prescribed under specific medical program. In other cases it is prohibited to block medication request

  • Check that $.medical_program_id is in list of predefined programs in MEDICATION_REQUEST_BLOCK_ALLOWED_PROGRAMS config parameter

    • in case of error - return 422 ("It is not allowed to block medication request under this medical program")

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

Expand
titleExample
Code Block

HTTP status codes

Response code

HTTP Status code

Message

Internal name

Description

1

Базові

2

401

Invalid access token

Недійсний токен доступу

3

403

Your scope does not allow to access this resource. Missing allowances: medication_request:block_pharm

Для вашої ролі відсутній доступ до цього ресурсу. Необхідний доступ на блокування рецепта працівником аптеки

4

404

Medication request does not exist

Електронний рецепт не існує

5

409

Only pharmacist can block medication request

Тільки фармацевт може заблокувати електронний рецепт

6

409

It is not allowed to block medication request that has been blocked from another legal entity

Неможливо зарезервувати рецепт, зарезервований іншою аптекою

7

409

Medication request must be in active status

Електронний рецепт має бути в активному статусі

8

Специфічні

9

422

value is not allowed in enum

Недопустиме значення

10

422

Block reason code is not allowed for PHARMACIST

Вказана причинa блокування рецептa не може бути використана ФАРМАЦЕВТОМ

11

422

Blocked_to date should be greater than the current date

Термін резервування повинен вказуватися в майбутньому

12

422

Blocked_to date should be equal to or less than the dispense validity end date

Термін резервування повинен дорівнювати або бути меншим, терміну дії дозволу на погашення рецепта

13

422

It is not allowed to block medication request under this medical program

Неможливо резервувати не екстемпоральний рецепт

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

Page Properties Report
headingsID ТМ, Статус
cqllabel = "tr-mis"

...