Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Windows 10 and Billing module freeze-ups and crashes

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

6 Posts

5 Users

0 Reactions

80 Views

RSS

glamontagne

(@glamontagne)

Posts: 89

Estimable Member

Topic starter

Hello all,

We are starting to roll out Windows 10 to our users in anticipation for the end of life in January. One of our billing people has been experiencing freezing and crashes in the billing module since I installed Windows 10, build 1903. Is anyone else experiencing this issue? Our CPS build is 12.3.1.3046

Thanks,
Gary

Posted : July 23, 2019 5:53 am

slansing

(@slansing)

Posts: 14

Active Member

Gary,

I think this is about 12.3, not about Windows 10. Supposedly SP3, or version 12.3.3 should address the billing module problems. I found that every time we opened up a billing entry, the program would consume about 4MB more RAM, and never release it, even if you repeatedly open up the same billing entry. Eventually, around 550MB total RAM used usually, the program would freeze.

The only fix short of this latest service pack has been to have the user completely exit CPS, all the way to the desktop, and restart. That would release that memory.

Again, this is supposedly fixed with 12.3.3, but I have not rolled it out yet.

Posted : July 23, 2019 6:11 am

tonyeder

(@tonyeder)

Posts: 10

Active Member

IS your staff working with Batch Closing Override on? I've noticed more crashing if that is enabled.

I originally found the missing Farpoint files from 12.3.2 that they believed was the issue (even released them with the SupportTool) but in the end just reverted the code back to VB from C# for 12.3.3.

Posted : July 24, 2019 2:32 pm

lkeith

(@lkeith)

Posts: 457

Honorable Member

We are currently on CPS 12.3.2. Will that version run correctly on Windows 10? Any gotchas that we need to watch if we start deploying Windows 10?

Thanks,

Linda

Posted : August 14, 2019 6:21 am

hdebree

(@hdebree)

Posts: 2

New Member

I think it might be a combination of Windows 10 and CPS. We are currently on version 12.3.2. We were not having any issues with random crashes and freezes (at least that was reported to me, users have a habit of not telling IT when things go wrong) in Windows 7. We started moving users over to Windows 10 a couple weeks ago, a few front office and medical assistants at first and then we started billing users. And all the billing users we moved over so far have issues with random app freezes and crashes in various parts of the billing a patient registration modules.

Upgrading to a new version is such a pain since we have to touch every local PC to update them manually. Takes a full Saturday if we have extra bodies to help. If not, then all weekend. If someone knows a better way of updating CPS clients that would be super.

Posted : August 21, 2019 7:46 am

slansing

(@slansing)

Posts: 14

Active Member

I have confirmed the memory leak in the billing module for Windows 7 and Windows 10. If you open enough billing entries in a row, you will eventually freeze/crash the program.

As for updating workstations, mRemote is a decent way to remotely connect to 5 or so workstations at once and put them through the upgrade in batches like that. You can keep track of where you are by renaming the connections within mRemote as you go, adding an * or something to the name as you complete them. Takes a little setup, but two people could do 80 workstations in 4 or 5 hours.

I tried extracting the installers for the plug-ins but they resisted my efforts to automate them, or even to run them manually from the command line with any kind of switch to install them silently.

Seems like the sort of thing that will be improved now that a real software company is in charge. We'll see.

Posted : August 26, 2019 11:11 pm

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0