- This topic has 2 replies, 3 voices, and was last updated 1 year, 8 months ago by
.
-
Topic
-
In the near future we’re going to be adding a LOT of new facilities based on service within our EMR and as such the associated messages would need to be routed to their specific threads. Looking just at our ADT for starters, there are applications which would ONLY need certain facilities; AA, BB and CC for example, while others will ONLY need DD or EE. Our all-else-fails solution would be managing a LOT of kills on the routes based on facility, but that’d be a headache to manage. We’re trying to see if the Wild Card Routes could be purposed to look at MSH.3 since all available documentation seems to point only to MSH.9. Searching Clovertech it appears it’s possible by changing what field it looks at but I’m not able to find where the change is made.
The end goal would be to have 1 inbound ADT thread, with separate Wild Card Routes filtering based on MSH.3 so we can manage all filtering in 1 location.
Thanks in advance!
-
Replies
-
-
-
You can use a TrxID upoc to change how the Transaction ID is built for routing. These procs can pull in the current message so you can parse it out, then the returned value is the transaction id (trxId) which is then used in the routing instead of the normalized MSH-9 field.
For instance, we have one of these procs setup for messages from our lab system so the different types of result messages (all ORU^R01) can be routed based on the MSH-3 field along with the MSH-9 so the blood bank results go through one translate, the micro results another, the pathology results a third, and then a default for everything else. This is because a different HL7 variant was needed for each type of message.
On the inbound thread, in Inbound/Inbound Data tab, you would then change the “Trx ID Determination Format:” to be “UPOC” and plug your proc into the setting under the Edit button.
Hope this helps!
Paul Bishop
Carle Foundation Hospital
Urbana, IL
-
- You must be logged in to reply to this topic.
