Overview:

This document details the new capabilities added to the Add/Edit Order (AOE) form, introducing support for skip-to conditions (conditional workflows), confirmation messages, and pre-filling of questions. This enhancement aligns the AOE form functionality with the existing capabilities of the Consent Form, allowing for highly configurable and dynamic forms.


Important Note: 

The configuration of skip-to conditions, confirmation messages, and pre-filling on the AOE form requires the input of JSON and is only accessible via support logins. These options are not available through the standard user interface for lab users.


View the video of how the form behaves in case of conditional questions and other newly supported configurations:

https://drive.google.com/file/d/1tYFh84Dr6OcYNCui938L6e9yUXCiN2wm/view?usp=sharing 


Key Objectives:

  1. Support of Skip-to Conditions: Implement logic to dynamically navigate users through the AOE form based on their responses.
  2. Support of Confirmation Messages: Enable the configuration of contextual confirmation prompts based on user actions within the AOE form.
  3. Support of Pre-filling of Questions: Allow for the automatic population of question fields based on predefined sources and logic.

Limitations:

  • The conditional question answered on the AOE from on the billing modal (before confirming the bill), once confirmed the answer, cannot be changed, if at all any change is required the users can stop the billing and create the bill again or confirm the bill and then "edit AOE" to make any changes required.
  • The configuration to use the above stated capabilities require JSON input, and hence cannot be done by the end user. We require to input the process and sub-process IDs in the JSON - which the end users are not aware of.
  • When we edit these AOEs after billing, and if the conditional question answer is changed, we do not dynamically change the further responses in this case, only the answer to that question will be changed.

For reference, please view the below configuration types: 

(Adding this for reference only, please contact the Data Entry team or Product Team to help out with such configurations where JSON input is required)


Please note:

In case of help required with these configurations - please raise a JIRA ticket and clearly mention the flow of the form that is required, a flowchart will also do. In case of confirmation messages - please mention the text of the confirmation message. And in case of pre-filling please mention the fields that needs to be pre-filled.


1. Support of Skip-to Conditions in the AOE Form:

Skip-to conditions are configured within the "Conditional Configuration" section of each question in the form builder, accessible via support login.

  • Configuration: Enable the "Allow Skipping" checkbox to reveal a JSON input field.

  • JSON Format: The JSON structure defines the skip-to logic based on question options or a default condition.

    • With Options:
      {"Option Value 1": {"skip_to_type": "Process/SubProcess/End Process","skip_to": "Process/SubProcess ID"},"Option Value 2": {"skip_to_type": "Process/SubProcess/End Process", "skip_to": "Process/SubProcess ID"}}
    • Default Condition:
      {"default": {"skip_to_type": "Process/SubProcess/End Process","skip_to": "Process/SubProcess ID"}}

  • skip_to_type Values: Process, SubProcess, End Process.

  • skip_to Values: The ID of the target Process or SubProcess.

  • Configuration Access: Support Login Only.

2. Support of Confirmation Messages on the AOE Form:

Confirmation messages are configured within the "Conditional Configuration" by enabling "Requires Confirmation Message" and providing a JSON structure, accessible via support login.

  • JSON Format:
    • With Options: "Option Value 1": "Message 1", "Option Value 2":"Message 2"
    • Default Message:"default":"Confirmation Message"
  • Configuration Access:Support Login Only.

3. Support of Pre-filling of Questions in the AOE Form:

Pre-filling is configured by enabling "Allow Prefilling," selecting a "Prefilling Source," and providing a JSON structure in "Prefilling Options," accessible via support login.

  • JSON Format (Focus on source_field):
    {"source_field":"field_name_from_source"}
  • Examples of Pre-filling Sources: Patient Level (Name, DOB, etc.), Billing Level (Tests, Samples).
  • Configuration Access: Support Login Only.

Impact:

These enhancements provide powerful tools for creating dynamic and efficient AOE forms. Please note that the configuration of these features requires support login access and JSON input.