The HL7 Log has always provided a window into your HL7 traffic. It is now a tool you can act on — not just observe.
It adds identifier, diagnostic, and routing columns, alongside a Resend action that requeues a cancelled outbound HL7 message directly from its row.
OmegaAI now introduces the Imaging Object Change Management (IOCM) feature. It is a DICOM/IHE standard that allows imaging systems to communicate image rejection and deletion events across connected systems.
When an image, series, study, document, or report is deleted or rejected in OmegaAI, IOCM automatically notifies configured external PACS, VNAs, archives, and imaging systems so they can update their records accordingly.
Outbound Notifications – OmegaAI sends rejection notices to external systems
Inbound Notifications – OmegaAI receives rejection notices from external systems and updates affected objects within OmegaAI
Does IOCM change the deletion process?
No. Users continue deleting images as usual. IOCM processing occurs automatically in the background.
Can users change the rejection reason?
Yes. The configured default reason is pre-selected but can be modified before confirming the deletion.
Can IOCM be enabled for specific stations only?
Yes. IOCM is configured independently for each station.
Is every IOCM transaction audited?
Yes. All delivery attempts, whether successful or unsuccessful, are recorded in the audit log.
Does moving a series trigger IOCM?
Yes. OmegaAI generates IOCM notifications for the moved series.
Navigation path in the application:
User Guide → Getting Started → Adding Devices & Modalities (DICOM Stations) → What is IOCM?
OmegaAI now introduces the Storage Commitment feature. It is a DICOM service where OmegaAI confirms whether a destination system has permanently stored received images.
Once images are transmitted successfully (C-STORE), OmegaAI sends a Storage Commitment request asking the destination system to confirm safe archival.
The destination responds with:
Enabling Storage Commitment SCU will aid when:
Image transmission alone does not guarantee long-term storage.
Failures such as network issues or destination storage errors may go unnoticed, thus Storage Commitment provides:
Does this change image sending behaviour?
No. Only adds post-send verification.
Is historical data included?
No. Only new sends after enabling.
Does restart affect transactions?
No. Pending transactions resume automatically.
Can this be enabled per station? Yes.
What is Partial Commitment?
Some images stored, others failed or unconfirmed.
Can batch size be changed?
Yes. Default is recommended for most systems.
Timeout behaviour?
OmegaAI waits up to 24 hours before retry logic is triggered.
Navigation path in the application:
User Guide → Getting Started → Adding Devices & Modalities (DICOM Stations) → Storage Commitment SCU
Adding Devices & Modalities (DICOM Stations); Storage Commitment SCU
This feature is currently available to US-based organizations only. International availability will be announced in a future release.
Writing scripts in OmegaAI no longer starts with a blank editor. The Script Editor can now generate a script for you from a plain-language description of what you want it to do. Describe the rule in your own words — click Generate — and OmegaAI produces a ready-to-review script using the correct operations, DICOM tags, and host functions for that editor.
Type a plain-language description into the new AI Prompt pane and click Generate. OmegaAI returns a complete script in the editor — no hand-coding required to get started.
Reduces time to create scripts and lowers barrier to entry for users unfamiliar with JavaScript. Non-technical administrators can now build automation rules using natural language.
AI-assisted generation works in all three scripting contexts: DICOM Device scripts, Import scripts, and Workflow scripts.
Unified AI capability across your entire scripting workflow — whether you're configuring per-device rules, transforming imported data, or orchestrating automation workflows.
Each editor gives the AI its own vocabulary, so the instruction produces the right kind of script in each place. The AI only uses operations that exist in that editor's Tools panel, and exact values you type are preserved verbatim.
Reduces risk of generated code using invalid or non-existent operations. Values like Series Descriptions and facility names are preserved exactly as you specify them.
The AI Prompt pane appears in the Script Editor in all three scripting contexts:
This release introduces the Date of Injury Bookmark feature to OmegaAI, enabling imaging centers handling personal injury and workers' compensation cases to automatically populate the patient's date of injury in radiology report templates. This improves accuracy and efficiency when processing reports that require injury date information for legal and referral purposes.
A new bookmark field automatically resolves to the Date of Injury value from the order's Accident Notes (mapped from HL7 ACC-1 field). Administrators and template editors can add this bookmark to any report template using the Template Manager.
Ensures accurate injury dates are included in reports without requiring manual entry, reducing errors and improving workflow efficiency for personal injury and workers' compensation cases.
When no Date of Injury is recorded on the order, the bookmark displays a blank or editable placeholder field instead of inserting a static "N/A" value. Radiologists can manually enter the date directly in the report editor before signing.
Maintains workflow flexibility by allowing manual data entry when information is not pre-populated, ensuring reports are complete regardless of data availability in the source system.
Date of Injury values are correctly substituted and exported in both PDF and Word (.docx) formats.
Ensures consistency across all report delivery methods, so injury dates appear accurately regardless of the export format selected by the user.
Worklist → Open Report → More Options (⋮) → Template Manager → Bookmarks icon → Date of Injury
This release introduces the Page Break feature in OmegaAI, enabling administrators and reporting users to insert explicit page breaks at any point within report templates. When reports are generated as PDFs—whether in Preview or as Final reports—all content following a page break marker begins on a new page. This feature is available across all sections of a report template and provides greater control over report layout and presentation.
Administrators can now place the cursor at any position in a report template and insert a page break marker using the Page Break button in the Document Viewer text editor toolbar. A horizontal line visually indicates the page break location within the editor.
This allows administrators to control how report content is distributed across pages in PDF output, improving readability and customizing report presentation without manual post-processing.
Page breaks function consistently across both PDF Preview and Final report versions. Content following a page break marker automatically begins on a new page in both output formats.
Administrators can preview exactly how reports will appear in their final PDF format, ensuring layout consistency and eliminating surprises in finalized reports.
The Page Break feature is now available in both the report template and the Document Viewer editor, across all sections, and is not restricted to specific content types or specific areas.
Administrators have full flexibility to structure reports according to organizational standards and reporting requirements, regardless of which template section they're working in.
Navigation path in the application:
User Guide → Document Viewer → Page Breaks in Reports
OmegaAI now introduces the DICOM Receive Completed trigger for Workflow Automation (WFA), enabling workflows to start automatically once a DICOM ingestion operation has successfully completed.
A new Workflow Automation trigger is now available that executes after a DICOM ingestion session has been completed successfully.
The trigger fires when:
Supported Across All DICOM Ingestion Methods
The trigger works consistently regardless of how DICOM data enters OmegaAI, providing a unified automation experience across supported ingestion methods.
Asynchronous Workflow Execution Workflow Automation runs asynchronously after ingestion completes, ensuring image reception and ingestion performance are not delayed or interrupted.
DICOM Receive Completed vs. Study Status Triggers
| DICOM Receive Completed | Study Status Trigger |
|---|---|
| Fires after DICOM ingestion completes | Fires when a study status changes |
| Does not require a study status change | Requires a study status change |
| Supports new studies and incremental arrivals | Executes only when the study status changes |
| Ensures ingestion is complete before automation begins | Based solely on lifecycle transitions |
| Best for ingestion-driven workflows | Best for lifecycle-based workflows |
The DICOM Receive Completed trigger enables organizations to automate workflows immediately after DICOM ingestion, even when no study status change occurs.
This is valuable for:
Navigation path in the application:
User Guide → Workflow Automation → Understanding Triggers → DICOM Receive Completed Trigger
You can now upload common image files directly as documents in the OmegaAI Document Viewer and Image Viewer. Uploaded images are automatically converted to PDF and stored as standard documents.
This release introduces automatic validation during report signing in Document Viewer. When a radiologist signs a report using Done or Done & Next, OmegaAI validates that the report is associated with the currently loaded patient study and verifies the presence of required report header and footer content. If a validation issue is detected, the user is prompted to review the report before signing can proceed. The validation is enabled by default and requires no configuration.
The system automatically validates patient and study context when a report is signed using Done or Done & Next.
Provides an additional verification step before report finalization when report context may no longer match the currently loaded patient study.
The signing workflow now verifies that required report header and footer content is present before signing completes.
Helps ensure that signed reports contain required report components before finalization.
When a validation issue is detected, a pre-sign notice is displayed. Users can choose to reload the study using current patient information or cancel the signing action.
Allows users to review and address validation issues before completing report signing.
Navigation path in the application:
Document Viewer → Open Report → Done / Done & Next
This release introduces updates to Contact & Address Layout in OmegaAI, focused on improving usability and consistency across create/edit forms.
On add/edit forms for Patient, Member, Guarantor, Payer, Employer, Physician, and Organization, Contact and Address details were previously under separate tabs. Users had to click a tab to see one set of fields, like Address, while the other stayed hidden. This has been updated — both sections (Contact and Address) now appear directly on the page, one after the other, so everything is visible without having to click anything else.
Users will be able to see and fill in all the contact and address details in one place, ensuring easier and faster completion of these forms.
On the Physician form, fields are now adjusted for a better appearance and consistency.
On the Payer form, the section previously labeled "Contact Details" is now "Contact", in sync with the naming used elsewhere.
Navigation path in the application: [Module] → [Section] → [Page — please fill in]