Using OVER or forwarding a message to a different thread

[John Valdes]

I’m trying to grab a particular kind of ORM inbound from our HIS and immediately send it to another thread bypassing all the routes currently configured.  Essentially I want to avoid having this message go to any other downstream systems without having to add a tcl script to kill the message on each route.

I have a tcl proc in place on the inbound TPS stack (after hl7Raw_ack) of the receiving thread.  I see in the message metadata that the msgDestThread has been successfully updated, but the message just sits in the Recovery Database, state 16 for the inbound thread.

I’ve never used OVER before, and any help would be appreciated.  I’ve attached a copy of the tcl proc used.

Thanks!

Topic

[Charlie Bursell]

Right after this command:

msgmetaset $mh DESTCONN dfm_orm_out

Add:

msgmetaset $mh SKIPXLATE 1

and then change this:

return “{OVER $mh}”

To:

return “{SEND $mh}”

Also pretty weird the way you are extracting the values to check using string first, etc.  I guess what ever works, however IMHO it would make it easier for others to maintain if it were done the way most Cloverleafers do it, like: (never a good idea to hard code separators)

set fldSep [string index $msg 3]

set subSep [string index $msg 4]

set segments [split $msg r]

# MSH fields

set msh_seg [split [lindex $segments 0] $fldSep]

set msgType [string map

[lindex $msh_seg 8]]

if {$msg_type ne “ORM_O01”) {return “{CONTINUE $mh}”}

if {[lsearch -regexp $segments {^ODS}] < 0} {return "{CONTINUE $mh}"}

msgmetaset $mh DESTCONN dfm_orm_out

msgmetaset $mh SKIPXLATE 1

return “{SEND $mh}”

[John Valdes]

I inherited the interface and this script from a co-worker who left before I could go over it in detail.  It’s always fun to try and fix someone else’s code, especially when you’re told it works fine but have seen no proof.  I appreciate the tips, and I’ll implement them and let you know how it goes.  Thanks Charlie!

[John Valdes]

I got it working, thanks to your help.  I completely rewrote the script and the NetConfig.  I would never have thought to use the msgmetaset $mh SKIPXLT 1 and the return “{SEND $mh}”.  I’ll certainly add these to my toolbox.

[Author]

Replies