Notifications
Clear all
Topic starter
I have a form that does not populate all the text into the document until it is placed on hold then opened again. The problem is that the form may get filled out and signed immediately. Can anyone help me out as to why it is doing that?
I would upload the form, but it won't let me for some reason. I can email to anyone willing to help....
Posted : June 3, 2014 11:19 pm
Can you give more details on the problem ?
Is it that you are entering text into a "box" on the form, and that text does not appear in the chart note (document) ?
If you click outside of the box after entering the text, you should then see it appear in the chart note.
OR
Is it that some listboxes are loaded by dynamic variables, and the listbox contents are not showing ?
regards,
Beverly
Posted : June 10, 2014 8:32 am
Topic starter
It is a home blood sugar form and it has several boxes for sugars or insulin doses to be entered. Even if the whole form is filled out, only the first column populates the text, even if you click outside the box. The form is built of document variables that I then converted to obs terms. It just won't populate all text until placed on hold and opened again. I am a novice MEL person so I may be missing something....
Also, any idea why I can't upload the form here??
Posted : June 10, 2014 10:24 pm
Did you go through the information on how to upload a file ?
It is described elsewhere on the forums….review "Usage Presentation".
Forums
Main Category
How To's
Usage Presentation – Web Site Tips And Tricks
See if you can upload your dlg file so people here can help you with it
Posted : June 11, 2014 3:39 am
Topic starter
Yes, I have previously posted forms before. It just all the sudden won't let me. I wasn't sure if something had changed. I go through all the steps and when I click insert it just goes blank and won't load.....
Posted : June 11, 2014 11:18 pm
Take a look at one of the fields that is not printing (until after put on hold etc).
Look at the "text translation", and see if it has anything like this...
{ if document.somename=="" then "" else CFMT(....) endif }
Perhaps there is a document variable that controls printing to the chart note, that is not getting set right away... just taking a shot in the dark here...
Posted : June 12, 2014 4:28 am
Topic starter
There is a lot of lines like that and they all start like this one:
if EVAL("DOCUMENT.BED"+field_count) <> "" AND (comment_field <> "") then
comment_trans = numtoascii(9) + comment_field
What does the EVAL mean/do?
Posted : June 18, 2014 11:21 pm
EVAL(...) is a MEL function that "evaluates" what is inside the (...) as a MEL statement.
So "DOCUMENT.BED" + field_count
must refer to a bunch of form fields (or document variables) that are most likely named like this...
BED1
BED2
etc...
So somewhere on your form OR in the MEL coding area,
there must be a field_count variable that gets updated, probably like this...
field_count = field_count + 1
Also, somewhere on your form (or document variable within the MEL coding area) you will find a field or document variable named "comment_field".
You will have to search through the MEL coding area (or search on the form) to find field_count and comment_field, and then follow the logic to figure out what is going on.
Also, I always preface variables with "document.", document.field_count or document.comment_field. So not sure if that is causing you a problem.
Posted : June 19, 2014 3:00 am
Topic starter
I have this before each series of EVAL (different terms in each)
!fn CommentTrans(field_count)
{local comment_trans =
""local comment_field =""comment_field = EVAL("DOCUMENT.COMMENT"+field_count)
if (comment_field ="") then comment_trans =""
else
But, what in this would cause it not to fire instantly?
I didn't write any of this, I modified it to connect to obs terms, but haven't been able to get it to fully populate when filled out before placing on hold. I am not an expert MEL writer. Which is probably fairly obvious!!
Posted : June 19, 2014 3:07 am
Malissa,
!fn CommentTrans(field_count)
{
local comment_trans =""
local comment_field =""
comment_field = EVAL("DOCUMENT.COMMENT"+field_count)
if (comment_field ="") then
comment_trans =""
else
What you have above is part of the definition of a function named CommentTrans(...). I am assuming you only posted part of it, because you are missing the endif
If you want CommentTrans(...) to fire immediately, then you will need to put a ! symbol in front of it, like this...
{!CommentTrans(field_count)}
or something like that.
It would help if you could get this form uploaded 🙂
Posted : June 19, 2014 3:25 am
Ok, this might be a form refresh issue, try this...
At the end of each of these functions, insert these JUMP_TO_TAB() :
fn ...trans(field_count)
{
...
JUMP_TO_TAB("Insulin Dosage Instructions")
JUMP_TO_TAB("Home Blood Sugars")
return ..._trans
}
I haven't looked too hard at this form yet, but try the above first.
Posted : June 19, 2014 4:43 am
Topic starter
Thank you for trying to help me. No, it didn't work.
Posted : June 19, 2014 4:50 am
I am having the same issue on a form. We have noticed this since upgrading to EMR 9.8. If I am using document variables or observations the text translation goes right into the note. If I have a function and I am displaying results of the function in a data field I have to use the JUMP_TO_TAB command to get the data display to refresh and show all of the content but the text translation does not go into the note until the encounter is put on hold and opened back up. I have not found anything that works to get the translation in the note immediately.
Posted : June 23, 2014 2:28 am
Malissa,
This isnt working for you because there is nothing in the chart note field for each item to get it to evaluate when you are changing a field, if you put the whole variable name in there, like "document.br_dose1" instead of "1" (without the quotation marks) then it would work. Since "1" is not the name of a variable that is being changed, the field isnt re-evaluating. I hope that makes sense...
The JUMP_TO_TAB() trick works when you use a built in function that does not evaluate continuously. The new MEL_LIST_FHX() functions are a good example of this...
Posted : June 23, 2014 3:51 am
Page 1 / 2
Next
