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

Gamma CQR Certificate Error (Expired 2017?)

MU, CQR, PQRS, etc.

Last Post by Anonymous 1 second ago

4 Posts

2 Users

0 Reactions

105 Views

RSS

hinks2000

(@hinks2000)

Posts: 50

Trusted Member

Topic starter

Hi,

Our CQR feed on Gamma has been erroring out since last night (2/13/19) with an invalid certificate. For some reason the https://gamma-data.cqr.gehealthcare.com upload site seems to be serving out a certificate that expired in 2017. I also confirmed by opening the URL in Chrome to ensure it wasn't some configuration issue in QIE. Our vendor said to change QIE to allow all certificates. I don't agree. There is a security configuration error and this should be resolved by Virence. I would not suggest circumventing security with patient data without confirmation from Virence of the issue.

Anyone else on Gamma CQR seeing this behavior?

Thanks,

Jake

Posted : February 14, 2019 10:32 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Yep. The web server is using an old cert that expired in 2017 for some reason. I just re-enabled the old cert on our side (by checking the box to enable it in QIE).

If you don't have the old cert, you could download it and install it for QIE, or disable cert checking if that's an option.

-dp

Posted : February 14, 2019 10:46 am

hinks2000

(@hinks2000)

Posts: 50

Trusted Member

Topic starter

It makes me a little nervous to be submitting PHI to a web site whose security is not up to snuff. Something changed and without some sort of acknowledgement from Virence about the issue is enough for me to hold off submitting until the issue is resolved.

Seems odd it's been like this for over 2 days now with no communication from Virence (or my VAR).

Jake

Posted : February 16, 2019 3:19 am

hinks2000

(@hinks2000)

Posts: 50

Trusted Member

Topic starter

It appears this issue is now resolved. The upload site is using the cert that expires in 2020 again.

Posted : February 18, 2019 10:15 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