ACK^RDE

[Jared Parish]

I have a Other Vender sending an acknowledgment with a message type of “ACK^RDE”.  This seems to be throwing an error in the engine of “No routes defined for TrxId ‘ACK_RDE'”  Is this HL7 standard?  or have I not configured something correctly?

Thanks,

Jared Parish

- Jared Parish

Topic

[Jim Kosloskey]

Jared,

If you do not intend to use the Recoveryxx Tcl procs for reply handling, you will need to route the reply in the NetConfig for the thread receiving the reply.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Stephan Head]

The HL7 standard started splitting out ACK’s for each message with release 2.3.1.  They added more in 2.4.  I believe this HL7 message showed up in 2.5.

[Jared Parish]

I do use the recovery procs,  what could be causing this to slip through the cracks?

Thanks,

Jared

- Jared Parish

[Stephan Head]

If your thread is an outbound thread, on your Inbound tab under Thread Configuration, check to see if the Trx id determination Format is set to HL7.  If so, and you have a version set on there, the route id HAS to be there or you will get your error.  If you are using a variant, just add ACK^RDE as a valid message type.  You should be able to use ACK^A01, etc. as an example on how the message is constructed.

[Jim Kosloskey]

Jared,

If you are utilizing the Recoveryxx procs, assure your reply is being treated by the engine as a reply and not data; also insure you are killing the reply message in the inbound TPS UPoC.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies