Has anyone else who upgraded to SP11 CEMR seen an increase in their Masterlocked charts? We used to have 1 every six months and we now have 2+ a day. GE said they have not had reports of this. I know on a prior release we had a large number as well then it cleared up. Users say they aren't getting kicked out. But I thought I would just ask. Our case # is 1-798485076
Thanks
Dawn
We are seeing the same, I reported a few weeks ago and said they hadn't seen others with that issue yet either. I've been removing also - maybe 10 or so within a few weeks. It seems like when there are multiple unsigned notes in the chart and it wants them to deal with interactions in the older one but prompts them in the new and then they can't as there is a lock. They get stuck in a loop especially with refills. We have gotten error that they are unable to sign clinical list changes and some times the "too much data, retry?" Our ticket is 1-786705397 and I was able to reproduce and send them trace files but haven't heard anything back. We have not applied Drug Interaction patch yet because that essentially turns it off I think and we want it to work but may need to if this continues. Thx. Jen
YES, we are seeing the same as well. I just reported to GE today and was asked to send a trace file, no ticket number yet. We have seen a significant increase in our calls on this issue since upgrading to SP11 a couple of weeks ago. We have had mixed error messages with little EMR crash/shutdown messages, but essentially the user is unable to continue working.
Yes, we've seen the Masterlock volumes increase -- don't know that we opened a ticket on it, as it was a lower priority than the Sign button. Seems related to the "other user in document" mentioned in another post.
While we have multiple users getting this we have on practice that gets it multiple times a day. Thre locked message most always refers to a refill done since the upgrade that has created a masterlock on the chart. I still don't know what is happening but I fear this is going to be HUGE. My OB practice is the one with most of the issues now, and they see their patients frequently. To those of you who ran the trace, were you able to replicate the work-flow that created the masterlock, or did you just run the trace after it was discovered?
Thanks
Dawn
I ran trace after we discovered patient and I am not sure the workflow yet. I thought it was mostly when refills came in and/or when there was more than one unsigned note in the chart but I'm not sure based on one I looked at yesterday and why some would be issues and not others. It does seem like one of my practices gets many more than others and they were "denying new to follow" with almost all their scripts for some reason. I queried for all masterlocks and found we had almost 300. I removed all and am watching today to see what gets created and not released. Our test db has over 300 locks since after updating to SP11 with almost no activity from end users. I updated task and still waiting to hear back from GE. I will post here if I find more. Sorry. Jen
Jen,
How did you get that list of Masterlocked chart?
I had a SQL script to clear one at a time using a PID and GE said that one was fine to use so I decided to modify to look for all and clear after people were done documenting for the day. They left me voice mail after I had already done suggesting that we do basically same thing and I sent them script I used for "approval". I haven't gotten paged today but will be monitoring new locks to see what clears by tomorrow and what doesn't. I'll post more if GE and I connect and have any other info. I do know it has been escalated to the DB team at GE. Thanks. Jen
To get list of all masterlocks:
SELECT PID,PATIENTID,SEARCHNAME,DB_UPDATED_DATE, MASTERLOCK FROM PERSON WHERE MASTERLOCK>0 ;
To clear all masterlocks:
UPDATE PERSON SET MASTERLOCK=0 WHERE MASTERLOCK>0;
commit;
That script is ok to use per GE. Thx. Jen
Yes we have had a lot of masterlocks. I think it had something to do with the drug interaction issue. I have gotten pretty good at clearing them unfortunately.