All messages should be posted in plain text. HTML will be converted to attachments. The meditech-l web site is MTUsers.com ======================================
Hi Susan, The simplest way to do this is to use the IFE attribute on the first BMI query to nil the value to the /variable temporary response to the second query. Then, make the second one required! If the user moves back to the first query, the second one is erased (even though it is still displayed on the screen if it is on the same page). If the user tries to file, they will have to go to fill in the BMI on the second query first. To prevent the user from having to fill in the second, I would use either an IFE to default and skip or use an DFT attribute to default the value to the first. However, if you are not skipping... it is possible that the user may enter a BMI different than the first. It might be a good idea to also use an FCLn/FCLnA to be sure that these match! Good luck, Kenny Whiteside Kenny Whiteside RN, BSN Patient Care Information Systems Catawba Valley Medical Center 810 Fairgrove Church Road Hickory, NC 28602 [EMAIL PROTECTED] >>> <[EMAIL PROTECTED]> 08/04/2006 2:03:38 PM >>> All messages should be posted in plain text. HTML will be converted to attachments. The meditech-l web site is MTUsers.com ====================================== Hi, We use an attribute to convert patient's weight to BMI. On the same CDS, we have a series of queries to trigger a DVT protocol, which includes the BMI. We have a DFT attribute on the 2nd BMI query to pull in the previously calculated BMI. Work fine....UNLESS....someone changes the weight value. Is there a way to default the response from the 1st query into the 2nd query, AND update it if changed on the 1st query (same CDS)? TIA. Susan Tanner, RN I.S. Nurse Coordinator Lourdes [EMAIL PROTECTED] _______________________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l
