routing messages question

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….

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.

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,

Check your PM here.

Dee

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,

Here is attached. Set it as TrxId Determination Format proc

Thanks