- This topic has 7 replies, 3 voices, and was last updated 16 years, 5 months ago by
.
-
Topic
-
What is the generally accepted best practice for efficiently killing unwanted HL7 event types? For example, say a particular inbound interface gets ADT and ORM. There are routes for the various ADTs, and you just want to kill all the ORM events without getting errors and entries unto the error database.
-- Max Drown (Infor)
-
Replies
-
-
Max, What I do is to route the unwanted Message/Event Types to the inbound thread raw (sounds weird but you can do it) and deploy hcitpsmsgkill on the route. The messages get killed.
Doing the routing tells me at a glance in a number of IDE locations that this inbound can provide the currently unwanted messages.
There are other ways to do this as well.
Jim Kosloskey
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
-
-
Max, You need to add a route for the ORM TrxID; the ‘static route’ is not going to handle the ORM for you. Simply add another route for the ORM and utilize the hcitpsmsgkill as you have defined on your static route. You can use any thread as the destination, including itself.
Jim Cobane
Henry Ford Health
-
-
Static route processes all messages the same way, regardless of their transaction ID; it essentially doesn’t care about TrxID determination. Since you are also routing based upon a TrxID, you need to account for any TrxID that may come in. You could also add a wildcard TrxID, and define the TrxID as .* (with the hcitpsmsgkill); this would catch everything. But, you may not want to do that if you want to be made aware of unexpected TrxID values coming in. Jim Cobane
Henry Ford Health
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
