Forcing a message to the error db

[Mike Strout]

With our new lab implementation about to go live, I am now trying to implement notifications for issues I know will arise. One in particular is trying to deal with legacy procedure codes. I would normally figure this out through some trial and error and some serious Clovertech digging (that is how I learn best), but time is a luxury I don’t have.

We have many new procedure codes for things, but some of our reference lab customers haven’t been told what they are, so we will definitely receive “legacy” codes. To deal with this, I created a table to flip the old code to the new one, but there will almost certainly be circumstances where we don’t have a mapping from the old code to the new one in the table. The target lab system reacts very badly when it gets one of these and just dumps the entire message into an error log that can only be viewed (can’t fix and resend in the lab system).

To fix this, I want to stop the message from getting sent and instead send a critical ticket into our helpdesk system about resolving the issue. I was going to use an XLTP to do this translation and email sending, but as I was flowcharting the process, I realized that I probably can’t set the disposition of the message in it. Is this true and does it make better sense to just do this in a pre-tps?

Either way (xltp or tps) is sending the message to the error DB as easy as setting the disposition to ERROR?

Finally, it would be great to be able to add some nice error text so when looking in the error DB, we can see exactly what the issue was. How do I add this to the ERROR’d message?

Topic

[James Cobane]

Mike,

Yes, setting the disposition to ERROR in the tps proc will put it to the error database.  We will normally put some information into the USERDATA metadata field to describe why the message was put to the error database; i.e.

msgmetaset $mh USERDATA “Your info here”

Hope that helps.

Jim Cobane

Henry Ford Health

[Mike Strout]

Thanks Jim! That is just what I needed.

[Jim Kosloskey]

You could also try xpmerror from Tcl within the Xlate.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Author]

Replies