Notifications
Clear all
Topic starter
We are upgrading from Version 11 to Version 12 on July 26th. Has anyone had any issues with custom forms in VFE making there way into version 12? This is a huge concern for us as more than half of our forms were made in VFE.
Also, any other little surprises I should expect with the upgrade?
-Katie
Posted : July 2, 2014 1:29 am
kkopp said:
We are upgrading from Version 11 to Version 12 on July 26th. Has anyone had any issues with custom forms in VFE making there way into version 12? This is a huge concern for us as more than half of our forms were made in VFE.
Also, any other little surprises I should expect with the upgrade?
-Katie
I would strongly encourage the use of a test server in advance of any upgrade. Our upgrade went really well and CPS 12.0.3 seems to be very solid (based on our experience and use since 6/19). There were issues prior to 12.0.3 which have been addressed and we haven't discovered anything new. We do get some of those pesky 0xC0000005 errors though, but that is normal for us.
As for your VFE part of the question, that is where the testing comes in. We had to update our CQIC templates/versions at the same time we upgraded to CPS 12. We also did several updates in advance of CPS 12 for Meaningful Use. I would not be surprised if you had to do some sort of update to your VFE install/templates but testing in your clinic with your templates/content would be the only way to know for sure.
On the CPS12 media is the ability to install a single user DB which would be sufficient for testing VFE functionality.
Mike Zavolas
Tallahassee Neurological Clinic
Posted : July 2, 2014 3:38 am
kkopp said:
We are upgrading from Version 11 to Version 12 on July 26th. Has anyone had any issues with custom forms in VFE making there way into version 12? This is a huge concern for us as more than half of our forms were made in VFE.
Also, any other little surprises I should expect with the upgrade?
-Katie
All of the forms we use were developed in VFE, and we have not experienced any issues with these forms in CPS 12. As indicated above, you should certainly test your forms before-hand on a test server.
CPS 12 had a lot of issues with system stability - users were reporting constant crashes. We upgraded to CPS 12.0.3 last week; so far, this product seems much more stable than the base CPS 12.
RE: Other little surprises. A new feature was introduced in CPS 12 where the Update Medications screen throws an error message when (1) Prescribing Method = Electronic; (2) No Qty is listed in the Prescription section. This error message tells you to add a Prescription Quantity. As most patients have a preferred pharmacy, and most pharmacies now e-prescribe, the prescribing method will automatically be Electronic for the majority of patients. This can lead to issues when you are performing a medication reconciliation and adding medications prescribed by other physicians. If the user tries to add a medication, he/she will be prompted to add a quantity...if a quantity is added, the medication will be e-prescribed. Instead, users should change the Prescribing Method to Historical. This is easy enough once you know this, but if you are unaware, you can easily inadvertently e-prescribe medications, as the system is telling you that the only way to get to the next screen is to add a quantity. SPR# 59543.
Posted : July 6, 2014 11:35 pm
We are still having a lot of freezing/crashing after cps 12.0.3 upgrade. Do you mind sharing your cps setup? it seems to me that using a fat client is a little more stable than using terminal servers.
Posted : July 7, 2014 1:16 am
lic08 said:
We are still having a lot of freezing/crashing after cps 12.0.3 upgrade. Do you mind sharing your cps setup? it seems to me that using a fat client is a little more stable than using terminal servers.
The crashing is better than it was at our site, but it is still not perfect. I experienced a crash this morning switching between Chart and Administration, but this is expected as it is a known bug (SPR 54616). I have had 5 other users report crashes today, but nowhere near the same frequency as prior to the upgrade.
During our upgrade to CPS 12.0.3, we also ran Windows Update on most machines, which sometimes included the most recent driver for the network card. I doubt that the lack of the latest driver was causing the crashes, but it was one of the things we changed, so I wanted to put this out there in the interest of full disclosure.
Also during upgrade to CPS 12.0.3, we ran the Reset User Defaults script in Server Setup. We had never run this before. I had a GE Support Tech tell me last week that we should probably run this once a month for best results. If you have never run this, it might be worth it to run this, although I believe that all users need to be out of the system to run it.
RE: Our CPS Setup: We have a pretty basic CPS setup: FAT Client, Servers running on VMWare, one server for DB, one server for App Server, one server for SMPP/DM/DocuSign, one server for eRX/DTS/Qvera. Qvera not currently running as we have yet to apply the SP3 Qvera Patch. We use all custom forms, no CCC. Our servers meet the tech specifications issued by GE, even though we would argue these specifications are excessive. Some users are wired, some wireless. Any computer that connects wirelessly is setup to always connect wirelessly, even when the user is at a desk and could connect in via cable. Reason: CPS is not fault tolerant at all, and that split second in switching from wired/wireless or wireless/wired is enough to crash CPS. All users are trained that after a crash, they need to Reset CPS Process before attempting to login.
Let me know if you have any other questions about our setup.
Posted : July 7, 2014 5:43 am
We run terminal servers so our environment is different. I did noticed CPS runs better on a fat client but 98 percent of our users use thin clients so i can't really test it out.
Posted : July 7, 2014 5:47 am
[email protected] said:
lic08 said:
We are still having a lot of freezing/crashing after cps 12.0.3 upgrade. Do you mind sharing your cps setup? it seems to me that using a fat client is a little more stable than using terminal servers.
The crashing is better than it was at our site, but it is still not perfect. I experienced a crash this morning switching between Chart and Administration, but this is expected as it is a known bug (SPR 54616). I have had 5 other users report crashes today, but nowhere near the same frequency as prior to the upgrade.
During our upgrade to CPS 12.0.3, we also ran Windows Update on most machines, which sometimes included the most recent driver for the network card. I doubt that the lack of the latest driver was causing the crashes, but it was one of the things we changed, so I wanted to put this out there in the interest of full disclosure.
Also during upgrade to CPS 12.0.3, we ran the Reset User Defaults script in Server Setup. We had never run this before. I had a GE Support Tech tell me last week that we should probably run this once a month for best results. If you have never run this, it might be worth it to run this, although I believe that all users need to be out of the system to run it.
RE: Our CPS Setup: We have a pretty basic CPS setup: FAT Client, Servers running on VMWare, one server for DB, one server for App Server, one server for SMPP/DM/DocuSign, one server for eRX/DTS/Qvera. Qvera not currently running as we have yet to apply the SP3 Qvera Patch. We use all custom forms, no CCC. Our servers meet the tech specifications issued by GE, even though we would argue these specifications are excessive. Some users are wired, some wireless. Any computer that connects wirelessly is setup to always connect wirelessly, even when the user is at a desk and could connect in via cable. Reason: CPS is not fault tolerant at all, and that split second in switching from wired/wireless or wireless/wired is enough to crash CPS. All users are trained that after a crash, they need to Reset CPS Process before attempting to login.
Let me know if you have any other questions about our setup.
What kind of wireless infrastructure do you have? Ruckus? Cisco? Are you doing any IPSec beyond WPA2?
I am asking because I think my time is near where I may need to introduce some fat wireless and thinking of doing it via RDP to the Windows 7 workstation in the clinic. I have Ruckus APs with a controller but in the building I need to do this in is also has a MRI with lead walls but it is in the corner of the building at least.
Mike Zavolas
Tallahassee Neurological Clinic
Posted : July 7, 2014 11:42 pm
tnc said:
[email protected] said:
lic08 said:
We are still having a lot of freezing/crashing after cps 12.0.3 upgrade. Do you mind sharing your cps setup? it seems to me that using a fat client is a little more stable than using terminal servers.
The crashing is better than it was at our site, but it is still not perfect. I experienced a crash this morning switching between Chart and Administration, but this is expected as it is a known bug (SPR 54616). I have had 5 other users report crashes today, but nowhere near the same frequency as prior to the upgrade.
During our upgrade to CPS 12.0.3, we also ran Windows Update on most machines, which sometimes included the most recent driver for the network card. I doubt that the lack of the latest driver was causing the crashes, but it was one of the things we changed, so I wanted to put this out there in the interest of full disclosure.
Also during upgrade to CPS 12.0.3, we ran the Reset User Defaults script in Server Setup. We had never run this before. I had a GE Support Tech tell me last week that we should probably run this once a month for best results. If you have never run this, it might be worth it to run this, although I believe that all users need to be out of the system to run it.
RE: Our CPS Setup: We have a pretty basic CPS setup: FAT Client, Servers running on VMWare, one server for DB, one server for App Server, one server for SMPP/DM/DocuSign, one server for eRX/DTS/Qvera. Qvera not currently running as we have yet to apply the SP3 Qvera Patch. We use all custom forms, no CCC. Our servers meet the tech specifications issued by GE, even though we would argue these specifications are excessive. Some users are wired, some wireless. Any computer that connects wirelessly is setup to always connect wirelessly, even when the user is at a desk and could connect in via cable. Reason: CPS is not fault tolerant at all, and that split second in switching from wired/wireless or wireless/wired is enough to crash CPS. All users are trained that after a crash, they need to Reset CPS Process before attempting to login.
Let me know if you have any other questions about our setup.
What kind of wireless infrastructure do you have? Ruckus? Cisco? Are you doing any IPSec beyond WPA2?
I am asking because I think my time is near where I may need to introduce some fat wireless and thinking of doing it via RDP to the Windows 7 workstation in the clinic. I have Ruckus APs with a controller but in the building I need to do this in is also has a MRI with lead walls but it is in the corner of the building at least.
Mike Zavolas
Tallahassee Neurological Clinic
Hi Mike,
We are using Cisco with authentication through WPA2 Enterprise. We do not have any users utilizing RDP; our wireless coverage extends through our clinic and administrative areas, so theoretically, a user could take his/her laptop, walk throughout our entire facility, and never lose coverage. I can understand why you would want to use RDP and think it could be a great solution. RDP is much more fault tolerant to wireless network drops than CPS, and CPS might even run faster on RDP, as opposed to running CPS on a wireless fat client. The biggest issue we had with wireless was when users switched from wireless > wired or wired > wireless. Our laptops all have (wired) docking stations, so the act of docking a workstation was causing a lot of CPS crashes. Let me know if you have any other questions.
Posted : July 8, 2014 1:55 am
