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

dbo.FM_CPOE_LabRadEvent Process exessive CPU usage

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

3 Posts

2 Users

0 Reactions

61 Views

RSS

krstevens

(@krstevens)

Posts: 26

Eminent Member

Topic starter

This process caused our CPU usage to spike from 9% to 100% on 7/20/2016. After killing the proc/process 6 more appeared. After a few hours the CPU and IO issue stopped. Usage was back down to 9 to 10% again.

I found that this process was included in CPS 12.0.11 release as a fix to "Functional Measure CPOE Lab & Rad measure."

Any idea as to what this process does and how we can avoid this from happening again?

Posted : August 3, 2016 9:34 am

mikeseale

(@mikeseale)

Posts: 344

Reputable Member

I believe this is for CQR. It may have been trying to resend all of your data again starting from a certain date. This is all set within the subscriptions in Adminstration, so if anyone changed any of the settings on those subscriptions, it could cause a data resend.

Another reason could be because that stored procedure was stuck and couldn't finish. Which could be due to some blocking or a bug with the stored procedure.

The reason you couldn't just kill the process is because your JBOSS was continuing to create these as you killed them. You would need to stop the JBOSS service, kill those processes, and start JBOSS back up. Although, if you haven't figured out what was wrong with the LabRadEvent proc, then you might have it happen again.

Posted : August 3, 2016 10:36 am

krstevens

(@krstevens)

Posts: 26

Eminent Member

Topic starter

When this issue occurred, we were having problems with our Subscriptions in Admin > Interoperability. As of 8/2/2016, subscriptions, QIE, and CQR are in working order.

According to the information you provided, this shouldn't happen again (since we resolved the subscriptions issue).

I really appreciate you responding and steering me in the right direction!

Posted : August 4, 2016 2:55 am

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