Pular para o conteúdo principal

Coming Soon: HL7 Log Enhancements

· Leitura de 3 minutos

Overview​

The HL7 Log has always provided a window into your HL7 traffic. With this upcoming release, it will become a tool you can act on — not just observe.

It will introduce: identifier, diagnostic, and routing columns, alongside a Resend action that requeues a cancelled outbound HL7 message directly from its row.

What's Coming​

1. Enriched HL7 Log columns​

What changed:​

The HL7 Log currently shows a small, fixed set of columns — Status, Status Reason, Intent, Description, Study Instance UID, Patient Name, and Requester — which is rarely enough to identify a specific message or work out why it failed. The enhanced grid surfaces the detail that was already being captured behind the scenes:

  • Identify and correlate a message — Task Id, Patient Name, Patient ID, Accession Number, Study Instance UID, Managing Organization, and Imaging Organization.
  • Diagnose a failure — Status, Error Count, and Failure Reason.
  • Understand the message and its route — HL7 Message Type (for example, ORM or ORU), HL7 Message Event (for example, O01 or R01), Sender, and Receiver.
  • Place it in time — Creation Date/Time and Last Modified.
Benefits:​

Find the message you are looking for
Task Id, Study Instance UID, HL7 Message Type, and HL7 Message Event become filterable, so you can narrow a busy log to the messages that matter. Error Count becomes sortable, bringing the most-retried messages to the top.

Choose your own columns
Log Settings becomes available for the HL7 Log, so you can add, remove, and rearrange these columns to suit how your team troubleshoots.

Study Instance UID on more message types
Study Instance UID previously populated only for ORM messages. It will now be available for ORU and DFT messages.

2. Resend a cancelled HL7 message​

What changed:​

A Resend action appears on HL7 Log rows whose status is Cancelled. Selecting it requeues the message: the error count is reset and the outbound message is sent again to the connected system.

Benefits:​

Recover without a support ticket When outbound HL7 messages are cancelled — for example, during an infrastructure interruption — they can be resent from the log itself without requiring a manual behind-the-scenes intervention.

Important Notes​

Which rows show the Resend action? Only HL7 Log rows with a status of Cancelled. It does not appear for messages in any other status.

Does Resend ask for confirmation? No. Selecting Resend requeues the message immediately. The row reflects its new status on the log's next automatic refresh.

Can several messages be resent at once? Not in this release. Resend applies to one message at a time.

Where to Find It​

Navigation path in the application:

OmegaAI homepage → Logs icon in the left-side navigation panel → log selector button (bottom-right) → HL7 Log

Availability​

These enhancements are rolling out progressively and are not yet enabled for every organization. This post will be updated as per official release, and the HL7 Log help article will be expanded with the full column reference and Resend.