Skip to main content

Product: HL7 Log Enhancements

· 4 min read

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.

What's New​

1. Enriched HL7 Log columns​

What changed:​

The HL7 Log previously showed a small, fixed set of columns — Status, Status Reason, Intent, Description, Study Instance UID, Patient Name, and Requester — which was 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
You can now narrow a busy log by the identifiers support actually searches on — Patient ID, Patient Name, and Accession Number — as well as by Task Id, Status, HL7 Message Type, HL7 Message Event, Study Instance UID, and Last Modified. Managing Organization and Imaging Organization are pickers, so you select an organization from a list instead of typing a name. Text filters match from the start of the value, and Error Count is sortable, bringing the most-retried messages to the top.

Know who triggered a message
Sender shows the login email of the user who triggered the outbound message, the name of the device that initiated it, or System when neither can be determined. It is captured when the message is first created, so it continues to identify who originally triggered the message even after a resend.

Choose your own columns
Log Settings is now 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 is now also available for ORU and DFT messages.

2. Resend a cancelled HL7 message​

What changed:​

A Resend action appears in the Action column 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 destination.

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, or in the other log views.

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.

Why are some columns blank? Accession Number, Study Instance UID, and Imaging Organization are populated from the imaging study linked to a message. Messages that reference no study — a document uploaded to a patient record, for example — show Patient Name and Patient ID but leave those study columns empty.

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

For the full column reference and the Resend walkthrough, see the HL7 Log help article.