tbllookup vs lcontain to kill/continue messages

This topic has 2 replies, 3 voices, and was last updated 13 years, 9 months ago by Tim Hallbauer.

Creator

Topic
January 23, 2012 at 7:52 pm #52903
Jim Beall
Participant
I need to do a kill/continue script based on the value in PV1.10 (hospital service). The message needs to be killed if one of 17 values is present in this field. I think the list will be relatively static. I’ve seen scripts using either an lcontain or doing a tbllookup to determine whether a value qualifies for killing/continuation but I’m not sure which approach to use.

Does anyone have a sense of which function (lcontain or tbllookup) is more efficient given this number of values? If TCL actually hit disk to do a tbllookup I’d say lcontain is more efficient but my understanding of tables is that they’re cached anyway.

Thanks.
Creator

Topic

Viewing 1 reply thread

Author

Replies
- January 23, 2012 at 8:53 pm #75848
  Jim Kosloskey
  Participant
  Jim,
  
  The tbllookup does not hit the disk every time (the Table is in Cache).
  
  Moreover from a maintencance standpoint I would think maintaining the Lookup Table via the GUI or a separate Tcl proc (like my Table Builder) would be safer than changing a Tcl proc list.
  
  That’s my opinion…
  
  email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.
- January 24, 2012 at 2:58 pm #75849
  Tim Hallbauer
  Participant
  We have a Family Practice department that has their own system. I utilize a table with their assigned HIS number to route or kill result transactions to that system. We also utilize another table to route results from resident ordered tests to the attending for co-signature. It works very well and as stated before is easier than changing a list of entries in a TCL proc.
  
  Tim
Author

Replies

Viewing 1 reply thread

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