Purpose

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

Specification

Logic

API paragraph not found

...

• 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").

Parameters that are used when processing the request

Configuration parameters

Access to the method is defined by the scope medication_request:block_pharm. Permission for this scope is determined by the System administrator by configuring scopes in the context of clients and roles.

Dictionaries

...

Processing

1. Update Medication request in OPS DB:

   1. set is_blocked = true

   2. set block_reason_code = $.block_reason_code

   3. set block_reason = $.block_reason

   4. set updated_by = user_id

   5. 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

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

4. Add new record in Event manager:

Response structure

Example:

...