Notifications
Clear all
Topic starter
Had the CRAZIEST call today with support after raising hell about all the problems we've had for the last month since upgrading from 10.1.3 to 12.0.5.
We were told that while there is not an SPR yet, we should stop allowing users to log off and return to chart as another user, ie, our MAs go into a room, start an encounter, leave, and another MA or provider comes in behind them, logs on and continues. We were told that this has been discovered by development to be a primary source of crashes and slowness and a huge bug in their code. They are in the process of working on what it is and creating an SPR and that no service pack of CPS 12 is unaffected.
Their recommended work around is that if someone leaves the room they need to close CPS totally, IE window and all, and re-login, until they have a workaround for this. Being ortho and having the huge volume we do, there is no way for us to do this and get through clinic in a reasonable time.
Is that not crazy???? There is no way humanly possible for us to change our workflow to this way. Very frustrated.
Posted : October 17, 2014 10:39 am
That is not a possible workflow in our practice either. Oh dear....
Posted : October 17, 2014 10:42 am
We are still holding off on 12 until we finally hear reports of a stable version, so this is...good?
I know you were just talking to a support tech and not a developer, but was there any indication of when they might be releasing a fix? Even a ballpark time would help us develop our strategic roadmap.
Posted : October 20, 2014 10:17 am
Topic starter
They didn't give us any concrete. He basically said it was a top priority for what it's worth.
We have had problems trying to upgrade now from 12.0.5 to 12.0.6 in our test environment but I think we have it figured out now.
Posted : October 20, 2014 1:11 pm
Yeah this is also a severe issue for our clinic as well. We have what we call Kiosk PCs in the rooms. Those PC are super locked down PCs that have printers installed and allow for the use of CPS. The PCs as kiosks are always logged into the PCs desktop with a generic locked down account.
The MA comes into the Room logs into CPS starts the visit and puts the visit on hold and logs out. The Dr then comes in and opens up the visits that was on hold and finishes it out.
Guess we are going to have to wait for whatever version fixes this, thanks for the heads up!
Posted : October 22, 2014 11:14 am
We use the same workflow with CPS 12.0.3 but I can't say that this is happening to us. Not sure how that is possible. We are definitely getting a lot of the 0xc0000005 errors on a few provider's computers but they don't logout/login like that. I have been told that 12.0.6 should fix this problem.
After reading this I am wondering if I am safe to upgrade to 12.0.6 now. I don't want to introduce a problem which I don't currently have by applying a SP. Is there a certain number of steps I would need to do to see if this happens on my 12.0.6 test server? Would I need to start an update on a patient, put on hold, logout, login different user, open same patient (take off hold)?
Posted : October 29, 2014 5:29 am
I was recently told by GE that significant issues are being experienced with cps12 sp6...enough such that it was recommended that I hold off. Can anyone offer information from their experience? Locking and freezing were two things that were mentioned.
Thanks,
Diane
Posted : October 29, 2014 6:03 am
my practice is experiencing constant issues with 12.0.6. CPS crashes for most of our users at least once a day. sometime much, much more. i would hold off until next month with SP 7 is supposed to be released.
Posted : November 21, 2014 1:21 pm
From my experience with GE, I would bet that "logging out and back in" is not really the source of the problem. They are probably just blaming it on that because they don't know the real cause?
I'm not a software developer, but over the years I have gotten the feeling that most of the crashing and freezing are caused by two main flaws in Centricity's overall design. First, overtaxing the PC's resources (hence GE's recommendation for i7 cpus, enormous amounts of RAM, and standalone video cards). And second, unstable connections to the SQL database. Even the smallest loss of connection to the SQL server seems to make CPS crash. (Since the day we got CPS, 8 years ago, our fat clients have crashed whenever a laptop roams to a new Wifi AP)
Posted : November 24, 2014 8:25 am
This happens because of a temporary profile table created when you log in. This is never ever going to change. I have been talking about this for years and looking at it from a developmental standpoint they would have to rip out the backbone of their software code to fix this.
Basically when you log in and start working on something it's saved into a temporary table. If you idle out this table gets 'lost' so to speak. When you log in again, it has a heck of a time finding anything you were working on.
If you are logging out and in as someone else, the same type of problem will occur. The new session isn't able to identify the temp table you were working in
It's like the age old problem with working on attachments in emails. If you don't save (hold or sign in this case) what you are working on and something happens all your work is lost or everything slows to a crawl.
Posted : December 2, 2014 5:08 am
We upgraded from CPS 10 to 12.03 and had application performance issues. Slow, errors, crashes etc
(We upgraded to cps 12 due to our meaningful use attestation obligations).
Upgrades to SPK 5 and SPK 6 were problematic.
We finally has a successful upgrade to SPK 7. There are still errors showing that were supposed to be addressed in the previous service packs but at this point we are happy to have a somewhat stable system.
Posted : December 8, 2014 7:16 am
