Overview​

OmegaAI introduces a Study Locking mechanism designed to protect finalized studies from accidental or unauthorized modifications. When a study reaches a specific configurable status, the system automatically locks it and makes it read-only across key modules— while still allowing controlled overrides for authorized users when necessary.

What's New​

1. Configurable Study Locking Trigger​

What changed​

Study locking is triggered when a study status reaches the configured threshold defined in the workflow step mapping "Prevent Modification ≥ PRIOR." Once met, the study becomes locked and read-only. The mapping between Study Status and the Prevent Modification workflow step is fully configurable per organization.

Benefit​

Organizations can define exactly at which status level a study becomes protected, providing flexibility to align locking behaviour with their specific clinical and operational workflows.

2. Read-Only Behaviour Across Worklist and Study Pages​

What changed​

When a study is locked, all editable study related components on the Worklist page and all study fields on the Study page become read-only. For users without special permissions, edit buttons are hidden and replaced with a lock icon. Hovering over the icon displays a tooltip indicating the study is locked and cannot be modified.

Benefit​

Prevents accidental edits to finalized studies and provides clear visual feedback to users about the locked state, reducing confusion and errors.

3. Modify Locked Study – New UAC Privilege​

What changed​

A new User Access Control (UAC) privilege called "Modify Locked Study" has been introduced. Users assigned this privilege (e.g., QA personnel, lead technologists) can see the Edit button on locked studies. When saving changes, a confirmation dialog is displayed: "This study is currently locked. Are you sure you want to proceed with modifications?" — requiring explicit confirmation before changes are applied.

Benefit​

Enables controlled overrides for authorized users without compromising the integrity protections applied to all other users, supporting both compliance and operational flexibility.

4. Image Ingestion Supported for Locked Studies​

What changed​

OmegaAI can continue to receive and ingest new DICOM images into locked studies through all ingestion paths, including standard image routing workflows. Image and series counts are automatically updated upon ingestion. However, protected metadata — including patient information, study descriptions, and order details — remains unchanged.

Benefit​

Ensures critical imaging operations are not blocked by locking, while still safeguarding finalized study metadata from being overwritten or altered unintentionally.

5. Audit Logging for Locking Activity​

What changed​

OmegaAI now logs all activities related to study locking, including configuration changes to locking settings, successful image ingestion into locked studies, privileged user overrides, and blocked modification attempts by unauthorized users.

Benefit​

Provides a complete audit trail for compliance, traceability, and regulatory requirements, ensuring full operational transparency around finalized imaging studies.

Important Notes​

• Locked studies are read-only for all users without the “Modify Locked Study” UAC priviledge,— edit buttons are hidden on study information page and cannot be accessed.
• The locking threshold is configurable per organization via the workflow step mapping; changes to this configuration are audit-logged.
• Image ingestion into locked studies is permitted, but protected metadata fields cannot be overwritten during ingestion.
• Users with the "Modify Locked Study" privilege must explicitly confirm the intent to modify via the system confirmation dialog before changes are saved.
• Study locking applies across the Worklist and Study pages; ensure all relevant user roles are reviewed and updated with appropriate UAC privileges post-release.

Where to Find It​

Locking Configuration:

Admin → Workflow Settings → Study Status Mapping → Prevent Modification

UAC Privilege Assignment:

Admin → User Access Control → Roles → Modify Locked Study

Lock Icon & Read-Only Behavior:

Worklist → Study Row |  Study → Study Details Page

Audit Logs:

Admin → Audit Logs → Study Locking Activity

Updated Help Articles​

Study Locking | OmegaAI User Guide

Overview​

This release introduces enhancements to User Type Management in OmegaAI to improve usability, administrative efficiency, and system consistency. With this update, User Types are no longer assigned directly on the User page; they are now managed through Roles, enabling centralised configuration and simplified user administration.

What’s New​

1. User Types Managed Through Roles​

What changed:​

User Types are now configured at the Role level instead of being assigned individually on the User page.

Benefit:​

This centralizes permission management and ensures consistent User Type configuration across all users assigned to the same role.

2. Simplified User Administration​

What changed:​

User management is now role-driven. When a Role is assigned to a user, the corresponding User Type configuration is automatically applied.

Benefit:​

This simplifies user administration by reducing manual setup and ensuring that users receive the correct permissions based on their assigned role.

3. Streamlined User Page​

What changed:​

The User Page no longer displays or allows editing of User Type fields. User configuration is now managed entirely through Roles.

Benefit:​

This provides a cleaner interface and reinforces a role-based approach to managing user permissions.

4. Automatic Migration for Existing Users​

What changed:​

Existing users are automatically migrated to the new role-based structure. Their current User Type settings are mapped to corresponding Roles during the migration process.

Benefit:​

Ensures a smooth transition to the new system without requiring manual updates to existing user accounts.

Important Notes​

• During migration, additional roles may be created automatically if duplicate User Type configurations existed. These roles may include suffixes such as “-1” or “-2.”
• Administrators should review these roles and remove or consolidate duplicates if necessary.
• All future User Type management must be performed through Role configuration, not through the User page.

Where to Find It​

Navigation path in the application:

Admin → Organization → Edit Organization → Users and Roles

Use the Users and Roles tab to add users and assign roles within the organization.

Updated Help Articles​

Add User Help

Overview​

This release introduces enhancements to the Image Viewer in OmegaAI, designed to improve workflow efficiency, customization, and accessibility for radiologists and technologists.

What's New​

1. Customizable Mouse Presets​

What changed:​

Users can now select mouse presets from the More Options (⋮) menu in the Image Viewer.

Benefit:​

Mouse controls can be configured to match commonly used PACS vendor workflows, making navigation, zoom, scrolling, and window/level adjustments more intuitive.

2. Multi-Organization Hanging Protocol Support​

What changed:​

Hanging Protocols can now be assigned to multiple organizations when saved.

Benefit:​

This allows protocols to be shared across parent and child organizations, ensuring consistent viewing configurations across sites.

3. Technologist Form Access from the Image Viewer​

What changed:​

The Technologist Form can now be accessed directly from the Image Viewer toolbar. The form opens in a new window and displays the review status.

Benefit:​

Radiologists can quickly review clinical, technical, and procedural details without leaving the viewer, enabling a more efficient reading workflow.

Important Notes​

• The Technologist Form opens in a separate window.

• The form displays the review status for quick verification.

Where to Find It​

Navigation path in the application: Worklist → Open Study → Image Viewer

Access the new options from the Image Viewer toolbar or the More Options (⋮) menu for Mouse Presets, Hanging Protocol configuration, Technologist Form, and Viewer Settings.

Updated Help Articles​

• Managing Organizations in Hanging Protocols

• Mouse Presets in Image Viewer

• Technologist Form in Image Viewer

Overview​

This release introduces updates to the Embedded Document Viewer (EDV) in OmegaAI to improve usability, efficiency, and system reliability. The new EDV delivers a unified, efficient, and intuitive reporting experience---bringing documents, reports, priors, and images together within a single integrated workspace.

What's New​

1. Embedded Reporting within Image Viewer​

What changed:​

The EDV is now fully integrated within the Image Viewer, allowing users to view DICOM images and reports side by side without switching modules.

Benefit:​

Reduces context switching by bringing image viewing and reporting into a single, unified workspace, enabling faster and more efficient reporting workflows.

2. Enhanced Navigation and Editing Experience​

What changed:​

A redesigned collapsible navigation panel provides access to studies, priors, report versions, and metadata. Editing tools now include structured formatting, templates, signatures, bookmarks, and section-level controls.

Benefit:​

Improves usability, enabling users to navigate and edit reports more efficiently with greater control and flexibility.

3. Advanced Version Control and Integrated Workflows​

What changed:​

Introduces a detailed version history with timestamps and editor tracking, along with integrated workflows such as technologist forms, peer review scoring, critical findings, and AI-assisted transcription.

Benefit:​

Enhances traceability, ensures reporting accuracy, and streamlines clinical workflows within a single interface.

Important Notes​

• EDV is now the primary interface for report viewing and editing within the Image Viewer

• All reporting-related workflows are consolidated within EDV

• Existing reports and workflows remain supported with improved access and visibility

Where to Find It​

Navigation path in the application:

Worklist → Select Study → Right-click (Omega Dial) → Image Viewer → EDV icon (top-right toolbar)

The Embedded Document Viewer (EDV) opens within the Image Viewer as a side panel for report viewing

Updated Help Articles​

https://help.omegaai.com/docs/Document-Viewer/Edv

Overview​

This release introduces updates to the Patient Page in Blume, focused on improving usability, navigation, profile management, and data consistency across platforms.

We are pleased to announce a series of enhancements to the Patient Page in Blume, designed to offer a cleaner layout, improved navigation, and a more intuitive experience for managing patient and family information. These updates provide users with streamlined control over personal details, documents, profiles, and regional settings across both desktop and mobile.

What’s New​

1. Revamped Patient Page Experience​

What changed:​

The Patient Page now features a more organized structure, enabling users to manage personal and document-related information in a single location. Both Primary Account Holders and Secondary Profiles (family members) can access relevant information based on their association.

Benefit:​

Improves navigation and provides a unified, user-friendly interface for managing patient data.

2. Updated Account Structure​

What changed:​

• Primary Account Holder
  • Determined by the email used at registration
  • Cannot be changed
• Secondary Profiles
  • Includes family members such as children, spouse, or dependents
  • Switching profiles dynamically updates all associated details
• A dropdown profile selector is available for seamless switching

Benefit:​

Clarifies user roles and simplifies management of multiple family profiles.

3. Enhanced Profile Tabs (Patient Details & Documents)​

What changed:​

A. Patient Details

• Personal Information
  • Name and Date of Birth are non-editable (organization-controlled)
  • Other fields remain editable
  • Smoking and alcohol use fields removed
• Home Address
  • Fully editable with autofill support
  • Users can override autofill
  • Unsaved changes trigger confirmation
• Emergency Contacts
  • Add/edit/delete unlimited entries
  • Mandatory: First Name, Last Name, Phone Number
  • Optional: Email, Relation
• Contact Information
  • Primary email set at registration
  • Phone number verification required
  • Saved phone numbers cannot be edited

B. Documents

• Upload via native file manager
• Real-time upload progress indicators
• Edit document name and date
• Document Date auto-derived (DICOM or file creation date)
• Download/delete single or multiple documents

Benefit:​

Enhances organization, improves data control, and streamlines document handling.

4. Family Member Access Improvements​

What changed:​

A structured process enables secure access for caregivers:

How it works:

1. Family member signs up using their email
2. Provider adds the email in OmegaAI
3. Access is automatically granted

Users can:

• View appointments
• Book appointments
• Access completed studies and shared data

Benefit:​

Ensures secure and role-based access for caregivers and dependents.

5. Profile Switching Enhancements​

What changed:​

Users can switch between profiles without logging out. The following update dynamically:

• Personal details
• Contact information
• Home address
• Emergency contacts

Benefit:​

Provides seamless navigation across multiple profiles.

6. Region Selection Updates & Automatic Region Detection​

What changed:​

Mobile:

• Manual region selection available in Profile Settings
• Region switching does not grant cross-region data access

Web:

• Region not visible in settings
• Can be changed via URL

Data Restriction Reminder: Changing region does not bypass data boundaries (e.g., India users still see India data even on .com).

Automatic Region Detection:

• Region assigned during first mobile login based on location

Regional URLs:

• India & neighbouring regions – https://blume.omegaai.in
• Canada – https://blume.omegaai.ca
• US & neighbouring regions – https://blume.omegaai.com

Benefit:​

Improves clarity of regional access while maintaining strict data boundaries.

7. Auto-Sharing Consent Update​

What changed:​

A new consent message is displayed during document upload: “By continuing, you acknowledge that you have read and understood this informed consent statement and consent to the sharing of your documents, images, and studies for the purpose of receiving healthcare treatment and care.”

Benefit:​

Enhances transparency and ensures informed user consent.

8. Demographic Sync​

What changed:​

Patient demographic data is now automatically synchronized between Blume and OmegaAI.

Benefit:​

• Improves data accuracy
• Reduces errors
• Enhances workflow efficiency

Important Notes​

• Primary Account Holder is fixed and cannot be modified.
• Certain fields (e.g., Name, DOB) are organization-controlled and non-editable.
• Region switching does not override data access restrictions.
• Phone numbers, once saved, cannot be edited.
• Family member access is strictly tied to registered email authorization.

Where to Find It​

You can access these enhancements from the Patient Profile section in Blume.

Navigation path in the application: Profile → Patient Page → Patient Details / Documents / Profile Selector

Updated Help Articles​

https://blumehelp.omegaai.com/docs/Profile/newpatientpage

https://blumehelp.omegaai.com/docs/Profile/Profiletab

https://blumehelp.omegaai.com/docs/Profile/Demographicsync

Overview​

This release introduces enhancements to the Self-Scheduling workflow in Blume and OmegaAI, focused on improving flexibility, reducing scheduling barriers, and enabling a smoother booking experience for patients and facilities.

We are pleased to introduce updates that allow patients to schedule appointments even when they are unsure of the exact imaging procedure, ensuring continuity in the scheduling process without requiring complete information upfront.

What’s New​

1. Support for Unknown Order Sets (AFD License Only)​

What changed:​

Organizations with an AFD license can enable self-scheduling without requiring patients to select a specific procedure.

• A toggle is available under: OmegaAI → Organization → Details → RIS → Self-Scheduling
• Patients can proceed without selecting a scan name or code
• If no procedure is selected and no document is uploaded, users are directed to the Additional Information & Notes section
• Appointments appear in Blume as “Procedure Not Listed / Not Sure”
• Facilities can later update the procedure in OmegaAI or PowerServer

Benefit:​

Reduces friction in the booking process and ensures appointments are not delayed due to missing procedure details.

2. Improved Workflow When Procedure Is Unknown​

What changed:​

If no document is uploaded:

• Slot selection is skipped
• User is taken directly to the Notes section
• No Informed Consent Statement is required

If a document is uploaded:

• Informed Consent Statement is displayed
• User must acknowledge it before proceeding

Benefit:​

Ensures a seamless and adaptive workflow based on available information, while maintaining compliance where required.

Important Notes​

• This feature is available only for organizations with an AFD license.
• Patients can complete booking without selecting a procedure.
• Procedures can be updated later by the facility.
• Workflow behavior changes dynamically based on document upload.
• Informed Consent is required only when documents are uploaded.

Where to Find It​

You can configure and access this feature within the Self-Scheduling settings.

Navigation path in the application: OmegaAI → Organization → Details → RIS → Self-Scheduling

Updated Help Articles​

Unknown Orderset | Blume User Guide

Overview​

This release introduces updates to login authentication in OmegaAI and Blume, focused on improving security, compliance, and user experience.

We are pleased to announce the rollout of enhanced login security for OmegaAI and Blume. This update replaces the earlier PIN-based system for new users and introduces a more robust, HITRUST-compliant password authentication process. With this enhancement, login workflows are modernized, account protection is strengthened, and both platforms are aligned with industry-standard security practices.

What's New​

1. Secure Password-Based Sign-Up for New Users​

What changed:​

New users are now required to create an alphanumeric password during sign-up. The PIN field has been fully replaced with a password field that meets HITRUST complexity standards.

Benefit:​

Ensures stronger authentication at the point of account creation and reduces vulnerability associated with simple PIN-based access.

2. Password Requirements (HITRUST-Aligned)​

What changed:​

Passwords must meet the following criteria:

• Minimum 8 characters

• Include both uppercase and lowercase letters

• Include at least one number or special character
  A real-time password strength indicator is also provided during creation.

Benefit:​

Guides users in creating secure credentials while enforcing compliance with HITRUST security standards.

3. Updated Sign-In Experience​

What changed:​

• New users sign in using their email and password.

• Existing users can continue using their current 6-digit PIN.

• Users who upgrade to a password will use it for all future logins.

Benefit:​

Provides a seamless transition path while gradually moving all users toward a more secure authentication model.

4. Improved Forgot / Reset Password Flow​

What changed:​

The previous PIN reset process has been replaced with a secure password reset flow that includes email verification and password validation.

Benefit:​

Enhances account recovery security and reduces the risk of unauthorized access.

5. Optional Upgrade Path for Existing Users​

What changed:​

Existing users can upgrade from PIN to password using the following flows:

• Blume: Enter registered email ID → Tap Forgot Password

• OmegaAI: Enter registered email ID → Select Forgot Password

This initiates a secure password setup process.

Benefit:​

Enables gradual adoption without disrupting existing users while encouraging migration to a more secure authentication method.

Important Notes​

• The PIN-based login system is no longer available for new users.

• Existing users can continue using their PIN until they upgrade to password-based authentication.

• Once a password is set, it becomes the default login method for all future sessions.

• All passwords must comply with HITRUST complexity requirements.

• Password reset now requires email verification.

Where to Find It​

You can access the updated authentication workflows during sign-up and login processes.

Navigation path in the application:

• Login / Sign-Up Screen → Password Setup / Sign-In

• Login Screen → Forgot Password

Updated Help Articles​

https://help.omegaai.com/docs/Getting-Started/Newpagesignup

https://help.omegaai.com/docs/Getting-Started/Login#updated-authentication-process--introducing-password-based-login

Overview​

This release introduces updates to organizational structure management in OmegaAI, focused on improving data consistency, simplifying hierarchy, and streamlining workflows.

We are pleased to announce the release of the Managing Organization Re-architecture in OmegaAI. This update eliminates the concept of the Master Organization and introduces the Managing Organization model. The Managing Organization becomes the top-level entity that owns patient records, while child organizations operate under it with limited configurations. This re-architecture simplifies organizational management, ensures consistency in patient data, and streamlines integration across all workflows.

What’s New​

1. Managing Organization Replaces Master Organization​

What changed:​

• All references to “Master Organization” are now updated to “Managing Organization.”
• Managing Organization is the top-most entity in the hierarchy.

Benefit:​

Provides a clearer and more intuitive organizational structure, reducing ambiguity in hierarchy definitions.

2. Unified Patient Management​

What changed:​

• Patient records are always created under the Managing Organization.
• User Access Control (UAC) for patients is applied at the Managing Organization level, even for members of child organizations.

Benefit:​

Ensures centralized ownership of patient data and consistent access control across the organization.

3. Child Organization Capabilities​

What changed:​

• Child organizations can manage users and may act as Imaging Organizations.
• In single-location practices, all configurations remain within the Managing Organization.

Benefit:​

Maintains operational flexibility while preserving centralized control over patient data.

4. Data Consistency & Migration​

What changed:​

• All existing patient records from child organizations are migrated and merged into the Managing Organization to ensure consistency and avoid duplication.

Benefit:​

Improves data integrity and eliminates fragmentation of patient records across organizations.

5. User Access Control (UAC) Model Updates​

What changed:​

• Patient UAC: Queries apply at the Managing Organization level and extend across all child organizations.
• Study UAC: Remains based on the Imaging Organization for precision in access control.

Benefit:​

Establishes a clear separation between patient-level and study-level access, improving both governance and operational accuracy.

Important Notes​

• The concept of Master Organization is fully deprecated and replaced by Managing Organization, resulting in a simplified organizational hierarchy and reduced complexity.
• Patient ownership is centralized under the Managing Organization, enabling standardized data governance and improved accuracy and reliability.
• Study-level access continues to depend on the Imaging Organization, ensuring a clear separation between patient ownership and imaging responsibilities.
• Data migration consolidates patient records from child organizations into the Managing Organization, supporting seamless patient and study management across workflows.
• In single-location setups, the Managing Organization handles all configurations without requiring child organizations, maintaining operational simplicity.

Where to Find It​

You can access and manage organizational structure and configurations within the Organization setup workflows.

Navigation path in the application: Admin → Organization Setup → Managing Organization / Child Organization

Overview​

This release introduces enhancements to RIS Procedure Codes and Order Sets in OmegaAI, aimed at improving usability, simplifying management, and maintaining data integrity across scheduling and study workflows.

What’s New​

1. Improved Interface for Procedure Codes and Order Sets​

What changed:​

The Procedure Codes and Order Sets pages have been redesigned with a cleaner and more intuitive layout for easier navigation and configuration.

Benefit:​

Users can locate and manage procedure configurations more efficiently, reducing the time required for daily administrative tasks.

2. Simplified Management​

What changed:​

Users can now easily create, edit, and filter Procedure Codes and Order Sets directly from the RIS Settings interface.

Benefit:​

This improves workflow efficiency and simplifies management of frequently used procedure configurations.

3. Safeguards for In-Use Items​

What changed:​

Procedure Codes or Order Sets that are already associated with existing studies cannot be deleted.

Benefit:​

This safeguard prevents accidental data loss while allowing administrators to deactivate items that are no longer required.

Important Notes​

• Procedure Codes or Order Sets currently used in studies cannot be removed.
• Administrators can deactivate them instead to maintain data integrity.

Where to Find It​

Navigation path in the application:

Admin → Organization → Open Organization → RIS → Procedure Codes / Order Sets

Use these sections to create, edit, and manage Procedure Codes and Order Sets for the selected organization.

Updated Help Articles​

• Procedure Codes –

  RIS Settings - Procedure Codes | OmegaAI User Guide

• Order Sets –

  RIS Settings - Order sets | OmegaAI User Guide

These improvements make managing procedure codes and order sets more reliable and user-friendly, helping you maintain accurate and consistent study data.

Overview​

This release introduces enhancements to the OmegaAI Scheduler, focused on improving scheduling accuracy, usability, and workflow efficiency.

What’s New​

1. Time Display During Drag and Drop​

What changed:​

When dragging a study from the worklist to the scheduler, the exact time slot is displayed within each cell.

Benefit:​

This provides clearer visibility when selecting appointment times and reduces scheduling errors.

2. Modality Mismatch Indicator​

What changed:​

A validation indicator appears when there is a mismatch between the study modality and the healthcare service modality.

Benefit:​

This helps prevent incorrect scheduling and ensures studies are assigned to appropriate services.

3. Customizable Scheduler Time Intervals​

What changed:​

Scheduler intervals can now be configured to 5, 10, 15, or 30 minutes, providing greater flexibility to match scheduling needs.

Benefit:​

Administrators can adjust scheduling intervals to match clinical workflow requirements.

4. Quick View Options​

What changed:​

Users can quickly switch between Day, Week, and Month views directly from the scheduler interface.

Benefit:​

This improves visibility and allows faster navigation between scheduling views.

5. Reorder Healthcare Services with Drag and Drop​

What changed:​

Healthcare services can now be reordered using drag-and-drop within the scheduler.

Benefit:​

Users can personalize the scheduler layout for easier access to frequently used services.

Important Notes​

• These enhancements will be rolled out within one week of the release.

Where to Find It​

Main Navigation → Calendar (right-side navigation bar)

Click the Calendar icon to open the Scheduler, where you can view and manage appointments, resources, and healthcare services.

Updated Help Articles​

log in here