I am having a weird and random error crop up when printing handouts. We are using Centricity EMR 9.8. This problem is random, and when it starts happening for a particular user, keeps happening for that user, but not for other users. The Handout Header references the LOC symbol. This symbol becomes unrecognized when the handout is printed from the MEL PRINTHANDOUT(...) function. The Handout can be printed from the [Handouts] Centricity toolbar button, and LOC symbol works correctly.
Handout Header defined as
{LOC.ADDRESS1} {LOC.ADDRESS2} {LOC.CITY}, {LOC.STATE} {LOC.ZIP} Page 1
{LOC.PRIMPHONE} Fax: {LOC.FAXPHONE}
{if (match(PRINT_TITLE,"~")>0) then "" else fmt("Patient: ", "B,1") + fmt(PATIENT.LABELNAME, "N") + HRET endif}
{if (match(PRINT_TITLE,"~")>0) then "" else fmt(PRINT_TITLE,"B,4") endif}
1. (Sometimes, randomly for certain users), When printed from a form button [Print Order], as runprocess {PRINTHANDOUT("Handouts\NAO\Orders\Physical Therapy Order") }
The Handout prints with the Header garbled by MEL errors:
(NOTE: Sometimes the error is <- BAD INDEX, Sometimes it is as below)
{LOC.ADDRESS1 <-FUNCTION DEFINITION IS NOT EXECUTABLE {LOC.ADDRESS2 <-FUNCTION DEFINITION IS NOT EXECUTABLE {LOC.CITY <-FUNCTION DEFINITION IS NOT EXECUTABLE, {LOC.STATE <-FUNCTION DEFINITION IS NOT EXECUTABLE {LOC.ZIP <-FUNCTION DEFINITION IS NOT EXECUTABLEPage 1 {LOC.PRIMPHONE <-FUNCTION DEFINITION IS NOT EXECUTABLE Fax: {LOC.FAXPHONE <-FUNCTION DEFINITION IS NOT EXECUTABLE
{DATESTAMP() <-FUNCTION DEFINITION IS NOT EXECUTABLE
{if (match(PRINT_TITLE,"~")>0) then "" else fmt("Patient: ", "B,1") + fmt(PATIENT.LABELNAME, "N") + HRET endif <-FUNCTION DEFINITION IS NOT EXECUTABLE {if (match(PRINT_TITLE,"~")>0) then "" else fmt(PRINT_TITLE,"B,4") endif <-FUNCTION DEFINITION IS NOT EXECUTABLE
But if I print this SAME Handout from the [Handouts] menu bar button, the LOC.... are recognized and print properly.
~~~~~~~~~~~~~
What ?!? is happening ? This is making me crazy. I have called my VAR, and they cannot figure it out. Just that there are sometimes problems using the PRINTHANDOUT(...) function. Anyone else see this or have a suggestion on how I can get LOC symbol to be recognized?
I thought it might be a memory issue, but it is somehow related to that particular user. I have logged into EMR from their computer (when the bug presents itself), and it will not occur for me (with the SAME patient), but if I log in as the user, then the bug occurs....until it randomly just stops happening. ARGH!
Any suggestions ?
- Beverly
Same intermittent problem with MEL errors in header when printing via PrintHandout(), not from menu. LOC symbol not referenced. Very interested in solution.
I did a MEL trace. It is like MEL just loses its mind and gets lost...
10/08/2015 16:25:44.439-execute>>Done with trigger
10/08/2015 16:25:44.439-execute>>MEL Parse Error: \{DATESTAMP() <-FUNCTION DEFINITION IS NOT EXECUTABLE
10/08/2015 16:25:44.439-execute>>Done with trigger
10/08/2015 16:25:44.439-execute>>MEL Parse Error: \{LOC.ADDRESS1 <-FUNCTION DEFINITION IS NOT EXECUTABLE
10/08/2015 16:25:44.439-execute>>Done with trigger
10/08/2015 16:25:44.439-execute>>MEL Parse Error: \{LOC.ADDRESS2 <-FUNCTION DEFINITION IS NOT EXECUTABLE
10/08/2015 16:25:44.439-execute>>Done with trigger
etc...
- Beverly
Are you by chance using Citrix? We are in a Citrix environment with our organization, and even though we have CPS12.0, not EMR9.8, I thought I'd mention this. On occasion we have odd printing issues that seem to be tied to one specific user and if we delete their Citrix profile and have it rebuilt the odd printing issue goes away.
@blackmanb, I am not having this problem, but I would be curious to see a MEL trace when you don't get the error also.
Having this same issue, does anyone know a solution? Our providers are unable to print the patient instructions without errors it is VERY frustrating. Please let me know! Thank you
The workaround is to print HANDOUTS from the [Handouts] button on the EMR toolbar. Then the LOC symbols are recognized and print properly. - Beverly
Thank you, I will try that. hope there is an actual fix soon
May not help at all but check your VFE settings for Build and see if under Speed Optimizations Clinical Function References is checked. If so, try rebuilding the form and see if that helps.
Thanks David! That may have been it actually. A few weeks ago, I rebuilt the form, exactly how I built it the form time just in a new form, and the problem disappeared Interesting.
Thanks for reaching out, appreciated!
Has anyone found a solution to this issue? It started to crop out with a couple of our users.
No solution that I know of yet unfortunately