Has anyone upgraded to 12.3 and if so, were there any issues? And did you upgrade on your own or via GE?
We have upgraded our test environment on our own. No problems with the GE part but there was a Visualutions issue (we are an FQHC).
We upgraded the database in place on Windows 2008 R2 but were already on SQL 2012. We did create a new appserver with Windows 2012 so jBoss went on a fresh machine. We also moved the staging directory to the database server as recommended. Remember that anything with a client needs to be Windows 2012 or equivalent - we don't have any fat clients.
Steve
Thanks so much, Steve, I appreciate it. Are you using the new Azure Active Directory, as well?
Interested in hearing other peoples experiences as well-
We went from 12.2.0 to 12.2.2 and upgraded a test database about a week ago. Other than taking almost twice as long for the actual upgrade to complete we have not seen any additional issues, but we have limited experience so far. We are planning to update a few small PM only databases a week from Friday.
Hey Steve, what was your Visualutions issue? We are also and FQHC and use VisDental, VisAnalytics, VisEDI and Billing, and VisCHC.
Honestly I am not sure. I do know at the end they corrected a licensing issue but I'm not sure if that was the only problem or not. Vis upgrade issues do not stop our process since they are so quick to respond first thing Monday morning for us. I had previously gone to 12.3 LA2 without the Vis problem.
Steve
It's synced, but we haven't done anything with it yet. We are still working on our plan for 12.3 in production.
We just upgraded from 12.0.10 to 12.3. Our upgrade was through Virtual Officeware. We did have some of our custom forms "break" and VOW is working on fixing them. Also, we had a custom ROS-CCC form that did not carry over, so make sure you print off and save all your custom items if you have them! Also any plug ins from Virtual had to be manually installed on each and every computer.
Some of the GE changes to CPS were a surprise. Color change in the billing transaction screen (awful!!) - impossible to read. Other changes were in the login screen with selecting location, editing unsigned letters, etc. These were not time-saving changes and created more "clicks"! Again, who are these GE programmers? I do not remember seeing these changes listed in the release notes and I tried to read all the ones between 12.0.10 and 12.3. The Advanced Specialty Search is still "broken". Our users cannot add DX codes to the Visit tab in the Case Management screen. We were told that this would be fixed with the upgrade because the fix was tied into a KB release that we had to install prior to upgrading.
It probably would have been better to upgrade in a test environment so that we could review everything prior to going live, but GE took so long to release 12.3 that we did not want to take more time away from the MIPS reporting.
I truly dislike upgrading the software. You end up spending days trying to get everything back to the way it was. We would not have upgraded if we did not have to. I do not see any great improvements in the software so far.
Michelle C.
Hi Steve,
You mentioned that anything with a client needs to be Windows Server 2012 equivalent. We have a lot of thick client installs, so I was wondering what you meant by this. I interpreted this as "all clients must be on Windows 8+". The documentation indicates that Windows 7 is acceptable. Have you heard something different about Windows 7 from GE and/or customers?
Thanks,
Craig
It is not supported on 2008 R2 was my real meaning since we don't have any fat clients. I would think 7 might work but you would need to check the release notes to be sure. Sorry for any confusion I may have caused.
Steve
That's what I suspected. Thanks for clarifying!
We are going to 12.3 this weekend. (fingers crossed) I was on the LA team and have tested 12.3 for months now. I am not seeing anything major to report, but I also don't have the 3rd party interface install in DEV.. We have had no issues with Vis Dental other than getting it connect to our one new training DB, but that issue has been resolved.. I am curious to the issue(s) you were having with Vis Dental.
Brian
Has anyone seen problems with using PRINTHANDOUT in an action button?
Hi David,
We have 12.3 in our test system and PRINTHANDOUT doesn't seem to work in a button. You get the 'Cannot find handout' pop-up even though the path is correct. When you run a MEL trace everything appears to be working ok.
Brad
Interesting, I have an early release version, 12.3.0.1931, and PRINTHANDOUT works fine from an action button. Running Oracle Virtualbox with client and server installed on the same VM. Printed to a network printer. I will have to upgrade to the GA release and see if that behavior changes.