MSH 9 Routing with hl7 2.5.1

[Tom Griffiths]

We currently have multiple interfaces that use the hl7 MSH 9 field for routing with wildcard routing like this:  ADT_A(0[1-9]|1[136]|3[18])

and non-wildcard routing like this:  ADT_A17

With interfaces that use hl7 version 2.5.1,  we are now receiving  MSH 9 data that looks like this: ADT^A08^ADT_A01

and the routing that we currently use is failing.

Does anyone have any experience with this?  

Most of our interfaces are Cloverleaf 5.7 Rev 2

How does Cloverleaf account for this change in hl7 version 2.5.1?

Thanks for your help!

Topic

[bill bearden]

This has been discussed some recently. This is the most recent one I saw.

https://usspvlclovertch2.infor.com/viewtopic.php?t=7050

[Charlie Bursell]

When you tell the engine to route on standard HL7 you are telling it to use the contents of MSH.9 for that purpose.  If that field contains ADT^A08^ADT_A01 that is what it will route on.

You say perhaps it should just route on ADT^A08?  How about the next guy that wants it to route on the entire field?  That is why Cloverleaf contains so many mechanisms to make it do what you want.

If you do not want to change every route, how about a simple TDXID proc that will return only the HL7 type and subtype like: ADT_A08

Personally I would prefer the Wildcard route as others have suggested.  Not hard to do if you tackle the NetConfig with an editor instead of a the GUI but be careful    😉

Me, I would just write a script to make the changes

[Austin Adams]

Here is how I have wild card routing defined :

ADT_A(0[12]|0[456789]).*

I handle the A03 message like I would any normal route with this:

ADT_A03.*

The reason I handle the A03 with a different Xlate is because the DG1 segment comes before the OBX segment.

[Author]

Replies