routing messages question

[Dennis Shirk]

I went to cloverleaft training at McKesson last week. As stated in my other posts I am new to HL7 and Cloverleaf. In class we learned that an HL7 message will route on field 9 of the MSH segment. We use McKesson Paragon and all orders will be coming in to Cloverleaf on the same interface.

My question is how do I route the message to the appropriate recieving system. For example in field 9 of the message it says ORM^001.

In the OBR segment field 24 says lab. I use 7edit and it shows field 24 is the “diagnostic Serv Sect ID”.

How would I get this order to route to the lab system.

Topic

[Keith McLeod]

On your inbound thread properties you will need to establish on the inbound tab under inbound data that you are using HL7. Then establish a route to your destination thread under the route messages tab.  You can give the route a name for example ORM_O01.  There is a button to add route detail once you have established the route name.  This is where you determine the type of route such as raw with a destination being the outbound thread to your destination system.  This should help you get started….

[Jim Kosloskey]

Dennis,

I suspect you need to further determine what kind of ORM^O01 you have.

Is it true that the single inbound thread will have Orders for the Lab, Radiology, Nutrition, Respitory Therapy, etc.?

If so, you will need a Tcl proc.

You can either deploy a TRXID Tcl proc or use a message filter proc.

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

[Dennis Shirk]

Jim Kosloskey wrote:

Dennis,

Is it true that the single inbound thread will have Orders for the Lab, Radiology, Nutrition, Respitory Therapy, etc.?

Hi Jim,

Yes, the single inbound thread will have orders for various systems as you described. Now I just need to learn how to write tcl procs 😉

[Dee Davis]

We use a TRXID proc to create routes as ORM_LAB, ORM_RAD, etc.  In the proc your goal is to return the trxid upon completion.

[Dennis Shirk]

Dee, would it be possible to email the proc to me so I can review it?

[Dee Davis]

Dennis,

Check your PM here.

Dee

[Sergey Sevastyanov]

Dennis,

We also use McKesson Paragon.

It is actually possible to do everything in xltate. You just define several routes for all ORM^R01 (ORM_R01), then in each xlate you check OBR-24 and kill the message if it doesn’t belong to particular route.

But I agree with others that it’s overhead (because instead of one copy of a message your engine will be translation 3, 4, etc copies), so I use TrxId proc. My proc returns for example, ORM_R01_RAD if OBR-24 = any of XRA, MRI, CT, USR, ORM_R01_LB for LB, and ORM_R01_MB for MICR. It does returns similar TrxId for ORU results. For everything else it returns “standard” Id, like ADT_A05.

It sounds like Dee was going to send you TrxId proc, but if you still need one please let me know and I will send it to you

Thanks

[Dennis Shirk]

Sergey if you don’t mind sending me yours that would be great. Then I can have two to compare 🙂

[Sergey Sevastyanov]

Dennis,

Here is attached. Set it as TrxId Determination Format proc

Thanks

[Dennis Shirk]

Thank you. I appreciate the help.

[Author]

Replies