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

12.3.2 Prescription Form Slowness

General Discussion

Last Post by batman 5 years ago

8 Posts

3 Users

0 Reactions

74 Views

RSS

jtlewis

(@jtlewis)

Posts: 35

Eminent Member

Topic starter

We upgraded to 12.3.2 a month back and one of our nonstop complaints is how terrible the prescription form is since we have upgraded. Our providers are complaining that it takes forever once they sign prescriptions for it to proceed.

Just wanted to reach out and see if anyone else has experienced these issues. If so, have you found a fix? From what we can tell our environment is running optimally and has plenty of resources allocated. We do use fat clients over WiFi, but have minimal issues outside of the prescription form slowness.

Thanks,

Jonathan

Posted : May 23, 2019 3:25 am

batman

(@batman)

Posts: 12

Active Member

Hi Jonathan - All the html forms go through your JBoss server. Sometimes the default Java memory setting is not enough and slowness can occur. In that case you modify the wrapper.conf file and allocate more RAM to Java. A restart of the JBoss service is required after the change is made. The memory will get reset back to default after each upgrade/re-install of Jboss however. If you need help with this just let me know and I can walk you through it. Contact info below:

Brad Batman

Senior Solutions Architect

Intelligent Systems Services

541-610-2746

[email protected]

http://www.iss-integration.com

Linux Foundation Member - https://www.linuxfoundation.org/membership/members/

ISS STORCIUM(R) - Unlimited Scalability Data Storage, VMWare Certified

ISS Disaster Readiness and Backup Solutions - Be Ready with ISS

Posted : May 23, 2019 4:49 am

jtlewis

(@jtlewis)

Posts: 35

Eminent Member

Topic starter

Sadly we are already rocking a 9 gb configuration for that. We have approximately 250 active users, but GE's example configurations, even for 1000 users, only recommends 12 gb.

Our server is allocated with 32 gb, so I will try bumping it up some to see if we gain performance boosts.

Posted : May 23, 2019 5:02 am

batman

(@batman)

Posts: 12

Active Member

If your JBoss server has 32Gb you can safely increase the wrapper.conf to 24G (75%) leaving 8G for the OS. I personally don't think 9G is enough for 250 users. Let me know how that works out for you.

Batman

Posted : May 23, 2019 5:08 am

jtlewis

(@jtlewis)

Posts: 35

Eminent Member

Topic starter

I will definitely let you know, we are going to start with an 18 gb allocation (we always error on the side of caution) and see what that does for us.

Posted : May 23, 2019 5:10 am

batman

(@batman)

Posts: 12

Active Member

Just curious if adding more memory to JBoss helped at all?

Batman

Posted : May 30, 2019 12:57 pm

dmontgomery

(@dmontgomery)

Posts: 59

Trusted Member

Batman, would you be able to elaborate on how to update the allocated memory? I'm thinking it would be by modifying the debug-wrapper.conf file but wasn't sure.

The lines I was looking at are

# Initial Java Heap Size (in MB)
#wrapper.java.initmemory.percent=10

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory.percent=75

Are you saying you would uncomment the lines that specify the min/max?

I didn't see any reference to memory in the wrapper.conf file itself. Both are located at

C:\Program Files\Centricity Practice Solution\jboss\jsw

Thanks,

Davy

Posted : December 5, 2019 3:32 am

batman

(@batman)

Posts: 12

Active Member

Hi Davy - It's a different file. Feel free to reach out to me at your convenience and I can walk you through it.

Batman

541-610-2746

[email protected]

Posted : December 5, 2019 4:58 pm

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 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