Overview​

Send New Objects Only is now available. It is a per-destination option that sends only the objects a destination does not already hold, instead of re-transmitting the whole study every time.

Overview​

An Order's status now updates on its own as its studies progress. Sign every study on an Order and the Order moves to completed by itself — no manual step, and no finished work still sitting at active.

What's New​

1. Orders reach a status that matches their studies​

What changed:​

When every active study on an Order reaches SIGNED, the Order moves to completed. The same applies across the rest of the workflow: all studies on HOLD moves the Order to on-hold, all studies CANCELLED moves it to revoked, and the first study to reach PATIENT ARRIVED moves a draft Order to active. If work is still outstanding, the Order is left alone.

Benefit:​

Order status is now a dependable signal of where the work actually stands, so worklists, filters and reporting reflect reality without anyone maintaining it by hand.

2. Cancelled and prior studies no longer hold an Order open​

What changed:​

A CANCELLED study stays on its Order but no longer counts as outstanding work, so an Order with one signed study and one cancelled study now reaches completed. Studies at PRIOR — the status a signed study moves to — behave the same way.

Benefit:​

Orders finish when the remaining work finishes, instead of being held open by a study nobody is waiting on.

3. Signing a study no longer re-opens the Order it just finished​

What changed:​

Previously any update to a study moved an on-hold or completed Order back to active — including the very update that should have completed it. Now a study reaching SIGNED or CANCELLED leaves the Order's status alone. Moving a study back to an in-progress status still returns the Order to active, which is intended: the work really has resumed.

Benefit:​

Orders settle instead of oscillating, and there are fewer "Another User has updated this record" conflicts while images are still landing.

Important Notes​

• Existing Orders are not updated retroactively. An Order whose studies were all signed before this release keeps its current status until one of its studies is updated again. This is expected, not a fault.

• Taking an Order off hold does not move its studies back. The studies stay at HOLD and are updated individually.

• Workflow step names matter. These rules are resolved by workflow step name for each organization. An organization with no SIGNED workflow step will never complete Orders — worth checking first if Orders are not completing as expected. Note the step is named PATIENT ARRIVED, even though the study status is displayed as ARRIVED.

• Coverage on a finished Order is now fixed in place. Once an Order reaches completed, revoked or entered-in-error, later changes to patient-level coverage no longer flow down to it. Coverage already recorded on the Order is unchanged.

Where to Find It​

Worklist → right-click a study row → Order → Order panel → Order Status

Order Status is also available as a Worklist column.

Updated Help Articles​

• Study Status — How Order Status is Derived
• Visit / Order / Study Page
• Table of Worklist Fields

Overview​

The Create New Order experience has been redesigned with a new full-page drawer that brings all order details — patient, physician, coverage, order sets, notes, and attachments — into a single, structured workflow, replacing the previous narrow side panel.

Note: This feature is currently available to Canadian users at omegaai.ca.

Overview​

This release brings a set of improvements across the OmegaAI Image Viewer, Hanging Protocols, and the Mobile Image Viewer — including a new stage-navigation option for Hanging Protocols, modality-aware display presets, persistent Cine playback preferences, a refined viewport scrollbar, and improved landscape mode on mobile.

Overview​

The Help Manual now includes a dedicated Troubleshooting & FAQs section, built from the most common issues reported to RamSoft Support, together with the steps that resolve them. Before opening a ticket, check whether your issue is covered: many problems can be resolved in a few minutes without waiting for a response, and when you do need support, the section shows you exactly what to gather so your ticket is resolved faster.

Overview​

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.

Overview​

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.

What's New​

1. Imaging Object Change Management (IOCM)​

What changed:​

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

Benefits:​

• IOCM helps maintain consistency across connected imaging systems by:
• Preventing use of rejected or invalid images
• Synchronizing image deletion and rejection decisions across systems
• Supporting patient safety initiatives
• Maintaining audit and compliance records Eliminating manual communication between systems

Important Notes​

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.

Where to Find It​

Navigation path in the application:

User Guide → Getting Started → Adding Devices & Modalities (DICOM Stations) → What is IOCM?

Updated Help Articles​

Adding Devices & Modalities (DICOM Stations); What is IOCM?

Overview​

OmegaAI now introduces the Storage Commitment feature. It is a DICOM service where OmegaAI confirms whether a destination system has permanently stored received images.

What's New​

1. Storage Commitment (SCU)​

What changed:​

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:

• Confirmation of successful storage
• Partial success (some images stored)
• Failure (images not stored)
• This ensures images are not only delivered but also diligently archived.

Benefits:​

Enabling Storage Commitment SCU will aid when:

• Destination supports DICOM Storage Commitment
• Verified archiving is required
• You require audit-level confirmation of storage
• You have experienced silent image loss

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:

• Verification: Confirms images are permanently stored
• Auditability: Full transaction tracking in logs
• Reliability: Automatic retry and resend mechanisms
• Compliance Support: Helps meet medical imaging retention requirements

Important Notes​

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.

Where to Find It​

Navigation path in the application:

User Guide → Getting Started → Adding Devices & Modalities (DICOM Stations) → Storage Commitment SCU

Updated Help Articles​

Adding Devices & Modalities (DICOM Stations); Storage Commitment SCU

🚨 US-ONLY RELEASE​

This feature is currently available to US-based organizations only. International availability will be announced in a future release.

Overview​

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.

What's New​

1. Describe it, don't code it​

What changed:​

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.

Benefit:​

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.

2. Available everywhere the Script Editor is​

What changed:​

AI-assisted generation works in all three scripting contexts: DICOM Device scripts, Import scripts, and Workflow scripts.

Benefit:​

Unified AI capability across your entire scripting workflow — whether you're configuring per-device rules, transforming imported data, or orchestrating automation workflows.

3. Context-aware and safe by design​

What changed:​

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.

Benefit:​

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.

Important Notes​

• Always review generated scripts before deployment. AI can make mistakes. A generated script is a starting point, not an approved rule — read it carefully, confirm it targets the right operations and tags, and test it before you deploy.
• Generated scripts should always be tested in a pre-prod or test environment before deployment.
• Complex conditional logic may require manual refinement after generation.
• Feature is pre-production only in this release; not yet available in production environments.

Where to Find It​

The AI Prompt pane appears in the Script Editor in all three scripting contexts:

• Device scripts: Organization → Devices → [Select Device] → Script Editor
• Import scripts: Organization → Import Script Section → Script Editor
• Workflow scripts: Workflow Automation → Workflow Configuration → Script Editor

Updated Help Articles​

AI-Assisted Script Generation

Workflow Scripting

Overview​

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.

What's New​

1. Date of Injury Bookmark Support​

What changed:​

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.

Benefit:​

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.

2. Flexible Data Population​

What changed:​

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.

Benefit:​

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.

3. Multi-Format Export Support​

What changed:​

Date of Injury values are correctly substituted and exported in both PDF and Word (.docx) formats.

Benefit:​

Ensures consistency across all report delivery methods, so injury dates appear accurately regardless of the export format selected by the user.

Important Notes​

• When no Date of Injury is recorded, the bookmark remains blank or displays an editable placeholder — it does not insert "N/A".
• The Date of Injury originates from the HL7 ACC-1 (Accident Date/Time) field, mapped to Order Information → Accident Notes in OmegaAI.
• Supported export formats: PDF and Word (.docx).

Where to Find It​

Worklist → Open Report → More Options (⋮) → Template Manager → Bookmarks icon → Date of Injury

Updated Help Articles​

Date of Injury