Notifications
Clear all
Topic starter
I have a form with multiple action buttons for printing handouts. This approach was chosen as I wished to execute code when the handout is printed, i.e. to allow filling obs term for having printed the handout(s). If the user clicks a button and in very short sequence attempts to exit the form, the system locks up. This appears to occur if exiting before the brief Printing Handout popup appears. Is this a known problem? Is there a solution or work-around?
Code behind action button:
{PrintHandout("Handouts\Arizona Cardiology Group\Low Sodium")
Update_Obs("Low Sodium")
}
Posted : August 1, 2012 8:24 am
SP3 is suppose to fix this.
Posted : August 1, 2012 10:42 pm
Update_Obs? Is that a CPS only function? It isn't available in EMR to my knowledge. Shouldn't you use OBSNOW?
OBSNOW("Low Sodium","Handout Printed")
David Shower
OU Tulsa School of Community Medicine
Posted : August 1, 2012 11:04 pm
Topic starter
Update_Obs() is a function within the form, not a system function.
Posted : August 2, 2012 3:28 am
Can you post the function code?
Posted : August 2, 2012 3:38 am
Topic starter
This is just a simple function to format a comma delimited string.
/*update Handout Printed Obs*/
{ fn Update_Obs(strHOP)
{
local strNow=obsnow("HANDOUTSPRTD")
if strNow<>"" then
strNow=strNow+", "+strHOP
else
strNow=strHop
endif
obsnow("HANDOUTSPRTD",strNow)
}
}
Posted : August 2, 2012 3:41 am
All looks good, I guess it is just the timing issue and hopefully the SP3 fix another poster mentioned will take care of the issue. Only other thing would be to see what a MEL trace shows during that working and/or check and see if any crash logs are being written on the client.
Posted : August 2, 2012 5:08 am
Maybe it is trying to print to a nonexistent printer? Can you print handouts from other forms?
Posted : August 7, 2012 7:33 am
Topic starter
Same user, same printer, same session. This is a problem that only occures with rapid keyboard input.
Posted : August 7, 2012 7:35 am
We use a similar approach to printing and updating the "HANDOUTSPRTD" obs term, but do the obs update just before calling the PrintHandout routine. This usually works well.
We do get sporadic crashes from one provider when printing in notes for which he joined an 'In progress' note created by an RN - who is also continuing to work in the note and update the vitals obs terms.
We are now wondering if the problem is related to the Symbol table update bug which was reported in CPS 10 (we are in CPS 9.0.63) and that 2 users updating the temporary db while a note is in progress is what is causing our crash.
Do any of you have users who routinely join 'In progress' notes and have similar crash problem when the 2 users are essentially updating the temporary db at the same time?
Posted : August 9, 2012 2:09 am
