For the experts

John,

If you want to reverse the message you can try an OVER disposition but I don’t think it will work within the xlate thread.  More likely, you’ll need to change the metadata DESTCONN setting to your inbound thread.  Your method may vary depending on if you want to have the charge data translated or whether it be ready to send to the inbound thread coming out of your Tcl proc?

Jonathan Hamilton

jonathan.hamilton@hcahealthcare.com

If the original message is in an outbound queue, we use the OVER message disposition for the copy of the message we want to send to the inbound queue. Then the message can be routed in a normal way to an outbound thread, based on the message TRXID

Greetings,

If memory serves me here, in a previous screw-up of mine, when a message is created for the very first time, the metadata is minimal and if you CONTINUE the message, the engine places it at the head of the Inbound queue for the thread as a State 1.

I think this is correct – experimenting will prove or disprove this assertion.

Good luck.

I’m not sure if I understand this correctly, but is sounds like you want to create a copy of the message (under certain conditions), perhaps changing the TRXID, and then have it process through the inbound routing, etc.  If that is the case, then you need to perform the processing in the ‘Inbound Data’ context, before the message is routed.  If you are performing the action pre-xlate, then you have already routed the message down the respective path.

Jim Cobane

Henry Ford Health

This comment is a little off-topic, but in “creating charges” via the interface, if you haven’t already, you may want to check in with your Corporate Compliance folks to see if you’ll be exposing the interface engine as a financial system of record with any add’l security, auditing and recordkeeping requirements that may bring.