This is only applicable for eCW browser…
After upgrading to Version 11 in October, I have received a lot of complaints from our front-office staff that eCW becomes sluggish some time after logging on and using it for a while.
As a part of troubleshooting the sluggish performance, one of our IT techs asked me to take note of the JavaScript heap size found in Chrome Developer Tools > Memory > JS Heap Size when a user complains of slowness. What I have found is that the heap size is way over 100mb (sometimes close to or even over 200mb) whenever the complaints come in. The heap size hovers around 40-50mb right after first launching eCW. It seems like there is a correlation that higher the heap size, the slower the application becomes! Refreshing eCW by hitting F5 brings the heap size back down to 40-50mb.
I am wondering if anyone else has noticed the JS heap size?
There was a new feature introduced in Version 11 that pretty much automatically hits the F5 refresh button after the user has navigated through N number of pages (item key Application Refresh Threshold 4033_VAOE). This is great for users who during their session navigate through different pages that count for the set threshold. This works great for the clinical staff because they are going in and out of progress notes all the time and each progress note count as 1 page. Once they reach the refresh threshold, their eCW session refreshes. But our front-office staff generally stays on the Resource Schedule page to make appointments, check in/out patients, collect payments, etc. They may do a lot of actions from within the Resource Schedule but they hardly leave the page, and thus never reach the refresh threshold.
