We are running EMR 9.8 and ever since updating to SP 5 we've had multiple crashes in our immunization form. The SQL, MEL and Database traces have been uploaded to GE and we've been ranked, but we're still having this issue for around 4 months. We've since updated to SP 6 but there was no change in the crashing. What we are seeing is an error about unhandled exceptions when we enter vaccinations. I thought it was with migrated immunizations from OBS terms, but it appears unrelated. I can create a new patient and enter immunizations and get a crash with no other entries. Most recently I took the vaccination record of a patient that was 13 years old and entered historical immunizations. Looking at her tables in the database she has all the immunizations entered. If it crashes it will record the immunization from the crash but won't allow you to proceed with more immunizations without closing and relaunching EMR.
Entering DTaP, Hep B and A will go fine, but then it seems to crash on MMR. However if I enter MMR then the rest I get no crash. It is not always that consistent either.
On the crashing it seems to break MEL and give the following:
12/22/2014 16:32:03.033->>
Fire trigger: {DOCUMENT.gFluVxGiven = "false"}
12/22/2014 16:32:03.033-execute>>Document.gFluVxGiven = "false"
12/22/2014 16:32:03.033-results>>ERROR: 32786 COULDN'T FIND THE SYMBOL
12/22/2014 16:32:03.033-execute>>Done with trigger
12/22/2014 16:32:03.033-execute>>MEL Parse Error: {DOCUMENT.gFluVxGiven = "false" <-COULDN'T FIND THE SYMBOL
12/22/2014 16:32:03.033-execute>>Done with trigger
12/22/2014 16:32:03.033-execute>>MEL Parse Error: {DOCUMENT.gPneumoVxGiven = "false" <-COULDN'T FIND THE SYMBOL
12/22/2014 16:32:03.033-execute>>Done with trigger
12/22/2014 16:32:03.033-execute>>MEL Parse Error: {MEL_Update_Content("1727625415914340","GE.USRPREF.Username.DefaultCustomList^^Pediatrics^^^^^^") <-COULDN'T FIND THE SYMBOL
12/22/2014 16:32:03.033-execute>>Done with trigger
12/22/2014 16:32:03.033-execute>>MEL Parse Error: {RELEASE_CLINICAL_LOCK("IMMUNIZATIONLOCK") <-COULDN'T FIND THE SYMBOL
The first two errors about not finding the symbol seem to be normal for successful vaccines, but the last one seems consistent with crashing. GE seems to think this points in a direction of a buffer overflow but the database has been checked multiple times by GE. Any advice?
Todd, not 100% sure if the exact same issue, but we had a VERY similar issue in terms of behavior in the immz after our upgrade from 9.8.3 to 9.8.6, and ended up being due to the issues with the sequence of our knowledgebase updates and SP6 install... (though we followed directions). It took us weeks to figure out the solution & get the right people on the call. The things we did first that did not work: restarting Jboss, reloading the Html content, truncating the immz data tables, re-migrating the immz data. It wasn't until we reloaded the recent knowledgebase updates (Sept, oct, Nov) that the crashing of the immz forms & the script errors went away.
Please feel free to reference this SR number we had open in case it's a similar issue. 1-551119500
Good luck
So you re-uploaded September, October and November to make it work? We've done KB Updates since the SP5 and SP6, but we haven't re-uploaded the old KB updates.
We are having the same issues and are on CEMR 9.8.6 with November KB. Getting ready to install Dec KB this weekend. Has anyone installed the Dec KB yet to see if it fixes the issue without having to reinstall Sept - Nov? If we reinstall the September KB before we install the December KB, would that be enough or is there something in the October and November incrementals that would cause us to have to apply those as well?
Any help is appreciated!
If you can get into the form check for special characters. Even on the back end when your setting up. The form doesn't seem to like special characters at all. for example
We came across this is first after numerous calls of the form not documenting, Immunization history view showing MEL vomit, and random crashing when using the form.
When I used IMMUN_GETLIST() in chart to get the raw field I found the special character, usually “@” in the comments (our folks use it alot for example done @ CVS).
So then I open the form do and update on the vaccine affected and remove the special charter and the documentation is back, history view is fine and quits crashing.
We did all the incremental KB updates and it had no effect. I also did the December full update with no change. GE has a copy of our database but has not offered any updates in the almost two weeks it has been in their possession.
We experienced crashing across all of our databases with the SP6 immunization content and rolled all of them back to the SP3 content for stability. KB's did not change any behavior that we saw. It looks to be the text translation of the chart note with the new form because it occurs when the done button is clicked and the chart translation writes to the note. The data does flow to the immunization table though.
There are also other issues with crashing and immunization content as someone previously mentioned. GE can help you run scripts to remove characters that migrated and are now having issues in the new table if you're experiencing that. You'll want to look at the data in the table for any patients crashing. they are characters such as ~, @, etc.
Also, there are additional immunization fixes coming in 9.8 SP8 GA version.
We received confirmation from GE that the issue is related to a back end process for MEL language cleanup failing with too much MEL code. It seems to be primarily affecting pediatric patients since they have lots of immunizations. If you look at the captures of the MEL Trace on a patient when you submit an immunization it reprocesses all the code every time you enter or view the immunizations. So you pull it up once when you view it, then enter the immunization then pull it up again. In addition it pulls code for every month for the patient's age. So you then see a command running for every month that patient has been alive seemingly multiple times for viewing the table.
They have expressed that this particular issue, which fits our problem description, will be fixed in SP8. SP8, from what I am told, is already in limited release.