Notifications
Clear all
Topic starter
We have one provider in our clinic who uses a scribe and has been complaining that CPS frequently crashes when he is trying to prescribe medications during a visit. Nor myself or his scribe and I together have been able to replicate the issue to try and determine what is causing it to crash.
I know it has to be a workflow issue and am wondering if any other facilities have experienced this with their providers who use a scribe.
Both the provider and the scribe work within the document at the same time. The provider is just viewing information until he goes to enter a prescription. The scribe continues to document on the forms as the provider is entering the prescriptions. Sometimes it crashes, sometimes it doesn't.
I guess what I am looking for is help in trying to determine what workflow they should use/avoid to prevent this from happening.
Posted : May 30, 2018 4:21 am
We do not recommend that two users attempt to enter data at the same time in a specific document. I know that was supposed to be resolved some time ago but we still intermittently have issues with this same thing occurring and we can not recreate upon demand. So best practice for us is to avoid, however we do not use scribes.
Posted : May 30, 2018 5:24 am
Two people in a document simultaneously, has been problematic for GE CPS & EMR. While possible, odd results (or crashing) has been known to occur.
Posted : May 30, 2018 5:29 am
I agree. GE claims they resolved this issue, but if there are multiple users in the same chart more than likely one if not both are going to have issues at some point. We have tried scribes in the past and had them hold to provider to do prescriptions and orders, then hold it back to the scribe.
Posted : May 30, 2018 5:33 am
We also have made a big effort to lock down two users in the same document at the same time - even if they are using different forms. There are two VFE forms we allow MA's to access for documentation if the status is "In Process" rather than "On Hold" (after determining there are no global variables used in these forms and testing multiple times/ways). But for every other circumstance, we advise users NOT to open the document if the status is "In Process" (because someone else has it open. Over time, we've noted more problems with concurrent users rather than less. In my opinion, the worst problem has to do with lost vaccine documentation. As many of you have probably experienced, it's not always clear when that popup occurs about keeping your changes or the other user's changes what the "right" answer is and it doesn't seem to always do what you think it will do even if you choose the "right" answer.
Posted : June 5, 2018 1:14 am
