Notifications
Clear all
Topic starter
Is anyone seeing an increase with locked documents, after upgrading to 9.8? We have had several this week, where a provider is in a note, and Logician just freezes. The note says in progress, but is locked. Each user was in a different part of the encounter, so no similarities, other than the document freezes. Thank you.
John Mazurowski
Posted : December 4, 2014 9:05 am
Yes, we saw that with out recent EMR 9.8.6 upgrade (from 9.5).
Issues:
1. EMR 9.8 crashes occasionally
2. For us, the Oracle jobs.exe processes weren't running automatically after the upgrade to SP6. (Oddly, they worked fine when we upgraded a separate system earlier in the year from 9.5 to 9.8 SP3.) Secondly, they worked fine when manually run within jobs.exe
3. Because the jobs didn't auto-update, In Process documents never auto-cleared. That Service is supposed to run every two minutes. I had disabled and re-enabled the jobs to no effect and ultimately, GE was able to resolve this (thank you, Saeed).
In Oracle's dba_jobs...
show parameter job_queue_process
alter system set job precesses = 2 where 0
Posted : December 4, 2014 9:33 am
We just upgraded to CPS12 and have experienced that same issue. Usually if the document is actually locked by another user, it will state their name. When this happens it doesn't, just says its locked. Called GE and they said they needed to get into the sql server to fix the issue cause they had some sort of document by document patch that would unlock it. It didn't work. What was worse is we couldn't get into the patient's chart to make any modifications because this was an office visit document that was open. I escalated it to our IT team so I don't know how it got resolved but allegedly it did. Its happened a few times since the upgrade.
Posted : December 4, 2014 12:04 pm
This is an issue with the Jboss, the way it operate and some values for the display data that jboss doesn't accept.
When those values are presented by the database to the Jboss, Your session on the application display crash.
The issue that you are having with those document, is the fact that some data field were not written in the document table because of the crash or because the document was left open for too long and the temp session ended living no data in those field.
Posted : December 5, 2014 11:18 am
