this would be done through the route replies function on the outbound thread. Say you’re routing messages from a vendor to epic with messages coming from thread f_vendor_t and routed to thread t_epic_t. On the t_epic_t thread, Route Replies tab you would setup a static route back to f_vendor_t. Make sure that the Outbound tab, Inbound Replies section does not have the hcitpsmsgkill proc setup in the TPS Inbound Reply field or it will kill the replies instead of routing them.
We have this setup for our infusion orders/verifications between the IV pumps and Epic. When we originally set it up, Epic was insisting that it couldn’t be done through an interface engine but we showed it could and have it working without issues.
Can you look at my attached document below and tell me what I’m forgetting to get the inbound reply route to add the dotted line route to the other thread?
Just be aware that the sending system will wait for that reply before sending the next message. If the receiving system is tardy or delinquent in sending a reply, message soulc back up on the sending system.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
I’m trying to recreate a reply routing that I did years ago and I’m missing something. I did the one for DHEC w/ the assistance of Infor. I’ve attached my config example. I can not remember what needs to be done to get the dotted connection line from the outbound thread to the new thread which will be to a local file.
I want to be able to send the inbound response to a regular text file so that our Goanywhere software can grab it and pull out necessary information to send to an Epic Analyst in an email with only the information needed to correct the error.