Reply To: Filtering messages

[Alan James]

You’ll need to type the exact code for your outreach patient type, as found in the HL7 charge message in either FT1.18 or in PV1.18.  The patient type is found in either place, and both are optional, meaning the message doesn’t have to contain that information – unless you have an HL7 variant requiring that field to be populated.  At my site, for example, ER patients have the code “ER”, which is the patient type, in FT1.18 for some charges, and that same information is found in the PV1.18 segment of the charge message from other applications.  Hopefully, all your DFT (charge) messages will contain the patient type code in the same place consistently.

If that’s true, then here’s how you can route your messages to the desired outbound thread:

In the GUI, go into thread configuration.  Right click on your inbound thread, and select thread properties.  Click on the route messages tab.  Highlight the route to the OB thread that will get all but the outreach patient type charges, and click on properties, which will bring up a raw route details dialog window.  (My routes are almost all “raw” routes…)  For the “Procs:” field, hit the Edit button, click ADD, and select the kill_msg proc from the drop down menu.  Type your arguments in the arguments window, using ~pttype in the PASSCOND argument.  Remember that you have to use the actual code, so what you type will look something like this, if ORPT is your code for outreach patient type:

{PASSCOND ~ORPT} {SEGNAME FT1} {FIELDNUM 18} {SUBFIELDNUM 0}.

Repeat all of the above steps to route charge messages to the OB thread for outreach patient type, except don’t use the ~ in your PASSCOND argument.  (And, remember that you’ll be adding the kill_msg proc to a different route – the one going to the appropriate OB thread).

Clear as mud?  It’s really very simple – the kill_msg proc can be very versatile…