Has anyone had issues to information in a text box disappearing? The only programming is this is set to an observation term. There is nothing on the white board referencing this box and nothing in the translation. When it happens they state that they can even go in and retype in the text box and it will continually disappear. It does not happen on every patient which is why I am thinking it might not be the programming. Maybe a GE known issue??
If the observation term is misspelled or not found in the database, then the "text" typed into the textbox will disappear. Check your obsterm. - Beverly
We are experiencing the same- here is my post and 1 answer from last week:
Is anyone else experiencing issues with text disappearing from CCC forms when the document is signed? We are especially seeing this with the HPI form. My physicians are pretty frustrated especially when they see a complicated new patient and type in the HPI, view it in the text translation only to have it disappear when signed.
A:
Do you have a VFE form in your encounter that hits the same obs as your CCC form? VFE and CCC do not play well together when sharing obs. It will appear to work fine but then when you put it on hold, everything is gone.
Good Luck!
I do have a VFE form in the template but I am pretty sure it does not share any obs- it is a lab order form with problems and orders. I think I may remove it and see if it is the culprit.
Thanks!
Cheryl
Is this a new form or an existing form that suddenly started misbehaving? If existing, have there been any changes to the EMR (version/service pack)? If existing, have other forms in the update been changed just prior to the issue? These answers may aid in narrowing your search.
If it is a new form, there are many culprits that may be causing this issue. As Beverly indicated, a missing obsterm (either misspelled or simply not present) can cause text to disappear, however this one is the easiest to identify since the text (or selection if it is a something like a radio button) will immediately disappear after the user clicks elsewhere on the form.
It is important to realize that MEL is present in more than just forms. Check your banner and any text components that may be inserted into the udpate as well as any 'start up' files being loaded when the EMR fires up to fully rule out potential collisions.
The first step is to see if the issue can be recreated with only the affected form in the update. If yes, then you know the issue is between that form and the MEL code loaded with the EMR. A MEL trace would be helpful for discovering the cause and potential fix.
If it does not occur with just the form, then it becomes painful. Theoretically, you would want to trace the entire update, but I do not recommend that approach as it can cloud the issue and take much longer to identify the culprit. I recommend adding forms to the udpate one at a time until the issue appears. You can choose to trace then or opt to see if it occurs with just the 'affected form' and the 'form that triggered the issue' only. Over time, you will get the sense of when to use which approach.
A MEL trace of the event occuring is the key to shedding light on the culprit. Since it is reported that once it happens, it continues to happen in the update, you should be able to capture it (and count yourself lucky!).
If you are able to capture the event and post the MEL trace (zipped) to this thread, I will be happy to review it and post my findings here.
In this case I know that the obs is not misspelled because it does work sometimes.
Thank you Lee-Cooper. I never thought about running a trace. I have not yet tried it with just the form either. Lots to think about/test. Thanks again.
We are not using CCC in this update but I might have a duplicate obs. However, you woul dthink if that were the case it would update both at the same time...hmmm....lots to think about.
Are they received and error when they are signing the encounter?
Are they receiving an error or crash when signing the document?
Is the user signing the encounter receiving a error or crash when the encounter is signed?