kill_msg.tcl

This topic has 5 replies, 5 voices, and was last updated 12 years ago by Krishna Kumar.

Creator

Topic
March 9, 2011 at 5:45 pm #52327
Tom Arrowsmith
Participant
Does anyone have a copy of this script (kill_msg.tcl) you can send me? I have always edited kill scripts – but realize that it would be easier to use this one and simply supply the correct aurguments.

I don’t have it though. Could anyone please email it to me at tom.arrowsmith@inova.org ? Documentation on how to use the argument parameters would be welcome too.

Thanks!
Creator

Topic

Viewing 4 reply threads

Author

Replies
- April 18, 2011 at 1:12 pm #73820
  Kirby Knight
  Participant
  I just sent it.
- October 17, 2012 at 4:08 pm #73821
  Mike Keys
  Participant
  Could I get a copy of this as well?
  
  Please email me at keys.mike@mhsil.com
  
  Thanks!
- October 18, 2012 at 9:28 pm #73822
  Robert Milfajt
  Participant
  Just wondering what the difference between kill_msg.tcl and hcitpsmsgkill, which comes standard??
  
  Robert Milfajt
  Northwestern Medicine
  Chicago, IL
- October 19, 2012 at 11:47 am #73823
  Mike Keys
  Participant
  Robert:
  
  hcitpsmsgkill is standard and just kills everything on a route. Very useful for testing.
  
  kill_msg takes a regular expression (usually a list of value like event types), the segment name, field and subfield location that the list it to be compared to. If a match is found in the list, the PASSCOND is true and the message passes. If not, then it is killed.
  
  I like to use this when creating routes as I don’t have to create an ADT_A01, ADT_A02, etc with detail repeated multiple times. I can specify a wildcard route ADT.* and apply the kill_msg proc to the details to limit which event types are allowed to pass.
- December 11, 2012 at 5:02 pm #73824
  Krishna Kumar
  Participant
  Hi Kirby
  
  Can you please email me to kkumar3104@sbcglobal.nrt
  
  Thanks
  
  Krishna
Author

Replies

Viewing 4 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.