Written by

Question Will · Jun 25

How to search for re-submitted messages?

My HL7 message got "AR" (rejected ack code) and went to the suspended queue. I re-submitted it (without editing it) but forgot to write down the details before doing so. It got "AA" and everything works fine from there.

Now (the next day) I want to check with the downstream system why they returned "AR" initially. Is there a way to search for the original message the got an "AR", along with any returned error message please?

Thanks

Product version: IRIS 2024.1

$ZV: IRIS for UNIX (Red Hat Enterprise Linux 8 for x86-64) 2024.1.1 (Build 347U) Thu Jul 18 2024 17:09:39 EDT [HealthConnect:7.2.0-2.m1]

Discussion (0)0

Add reply

Comments

Jeffrey Drumm · Jun 25

An error that would cause a suspended message should appear in the operation's error log. That would also have the session ID and a link to a trace of the message.

You could also query via SQL for a message header that starts with the string "Resent" in the Description field; that's the resent copy of the message but it will include the original message ID following the word "Resent." It will have the same session ID as the source message and both will show up in the trace.

A sample query:

SELECTID, MessageBodyId, TargetConfigName, TimeCreated, Description
  FROM Ens.MessageHeader
  WHEREID >= (SELECT TOP 1IDFROM Ens.MessageHeader WHERE TimeCreated >='2025-06-25 10:45:00.000'ORDERBY TimeCreated ASC)
    ANDID <= (SELECT TOP 1IDFROM Ens.MessageHeader WHERE TimeCreated <='2025-06-26 00:00:00.000'ORDERBY TimeCreated DESC)
    AND 
        TargetConfigName = 'To_Downstream_System'AND 
        Description LIKE'Resent%'

0 0

Enrico Parisi · Jun 25

If I recall it correctly when a message is suspended a warning event is logged in the Event Log.

Try searching for warnings from that BO around the time it was suspended and from there you can get the trace.

0 0