2 posts tagged with "workflow automation"

Overview​

We’re pleased to announce enhancements to the Email Template feature in Workflow Automation (WFA) for Blume. These updates are designed to simplify template management, improve usability, and provide greater flexibility in patient communications.

What's New​

1. Enhanced User Experience​

What changed:​

The Email Template interface has been redesigned with a structured grid-based layout, replacing the earlier tile view.

Benefit:​

Templates are easier to browse, compare, and manage within workflows.

2. Improved Template Management​

What changed:​

Users can now seamlessly create, edit, activate, deactivate, and reuse email templates directly within a workflow.

Benefit:​

Templates support common patient communication scenarios such as appointment confirmations, cancellations, invitations, and notifications — all within a single workflow.

3. Flexible Customization & Branding​

What changed:​

Email content is fully customizable using an enhanced editor, allowing organizations to format text and adjust layouts.

Benefit:​

Organizations can align emails with their branding and communication standards for a consistent patient experience.

4. Reply-To Email Configuration​

What changed:​

A configurable Reply-To option allows organizations to route patient responses to a preferred email address.

Benefit:​

When disabled, system-managed footer messaging clearly indicates that the email is auto-generated, ensuring transparent patient communication.

Important Notes​

• Templates can be activated or deactivated but cannot be permanently deleted once in use within a workflow.
• The Reply-To configuration is optional; when not set, the system auto-generated disclaimer appears in the email footer.
• Email Templates are specific to the Blume platform within Workflow Automation and are not shared across other OmegaAI modules.

Where to Find It​

Navigation path in the application:

Workflow Automation → Email Templates

Updated Help Articles​

Email Templates in Workflow Automation (Blume)

Overview​

We are pleased to announce the Signed Report Trigger under the Operations Trigger Type in Workflow Automation (WFA). This new trigger automates post-report actions (e.g., distribution, notifications) immediately after a diagnostic report is finalized, effectively eliminating delays caused by asynchronous DICOM processing. This mainly improves support for customers who are using external reporting solutions, while adding more granular control over other report creation scenarios.

What's New​

Trigger Activation Scenarios​

What changed:​

The Signed Report Trigger could be activated when any of the following occurs:

1. A diagnostic report is uploaded as a final report via the Document Viewer (DV) GUI.
2. A report is received in OmegaAI through HL7 or FHIR integrations.
3. A Structured Report is ingested via DICOM ingestion through OmegaAI Link.
4. A final report (DICOM encapsulated) imported using the Import Feature.
5. A final report is created or saved in OmegaAI’s Document Viewer (DV), including Signed Amendments.

Note: Ensure that you add the appropriate conditions after the trigger to prevent the final sign-off from being activated when not required.

Benefit:​

Workflow Automation allows you to automate processes and tasks, increasing efficiency and reducing manual intervention. With the Signed Report Trigger, we’re taking another step toward streamlining your reporting workflow.

Important Notes​

• It is recommended to configure appropriate conditions with the trigger to avoid unintended execution • Original workflow execution depends on report finalization events across supported ingestion methods • Particularly beneficial for environments using external reporting solutions • Ensure conditions are configured to prevent unnecessary trigger activation

Where to Find It​

Navigation path in the application:

Organization → Details → Workflow Automation → Create/Edit Workflow → Trigger Type: Operations → Signed Report

Updated Help Articles​

Workflow Automation.