Route messages based doctor

[Scott Smith]

I need to take ORU messages and route to at least 3 different threads based on doctor.  I think I can use a lookup table with the dr number being on the left side.  I am not going to be able to add any fields to the message, so what do I do with the returned value of dr number?

Any examples would be great as I am on a time crunch with this one.

Also, where would be the best place put this proc?  I need to have route determined on my inbound thread before sending the message.  These messages are being sent raw, so there is no xlate(s).

Any help would be great

Scott Smith

Topic

[Dennis Pfeifer]

Even though you are routing raw, you can still put in a proc in the route.

Send the message to all three destinations, then kill it on two of them.

You could use the same proc on all three, and have a parameter on each route indicating the ID to keep …

Dennis

[Scott Smith]

So Dennis,

Could I put the dr ID on the left and KILL, CONTINUE. etc on the right and use that value to match on each route.  Then I would put the proc in each route, right?

[Dennis Pfeifer]

That’s an option…

You could use one table instead of three (sounds like you intend to use three) ..

Input would be Dr. number. output would be destination interface ‘id’ ..

then put the ID as a parameter to the tcl proc.

If the ID returned by the table look up does not match the ID in the parameter, then kill the message..

You would use a different ID on each route…

Dennis

[Scott Smith]

That’s the idea I was looking for.

[Alan James]

Build three threads.  Use the kill_msg.tcl proc (attached) on each thread, varying the arguments to filter your ORU transactions accordingly.  I

[Author]

Replies