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

Switching to CCDA 2.1

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

8 Posts

6 Users

0 Reactions

75 Views

RSS

Aniemann

(@aniemann)

Posts: 10

Eminent Member

Topic starter

We are currently on CPS 12.3.1 and CCDA 1.1. We'd like to make the switch to 2.1 relatively soon and I was hoping someone may be able to provide me with a little guidance in regards to how I'd prepare for that transition. We have a significant amount of data that gets processed through Qvera (including CQR, Mass Hiway, Immunization Registry, Radiology rpts, lab rpts, etc.) on a constant basis. My Current understanding of CCDA 2.1 installation is that to turn it on, it's a quick flip of the switch within the Admin module of CPS. What I don't understand and where I can properly make any modifications or do any testing that would prevent all the CCDA's both coming in and going out from being misconfigured or erring out. My other concern is how the switch to 2.1 will affect our patient portal. And, how I can prepare the portal so that we don't see any issues there either. Any guidance you could provide in that regard would be greatly appreciated.

Posted : April 5, 2019 1:28 am

Luladin

(@luladin)

Posts: 25

Eminent Member

I've had a case going with Virence / Athena after our switch and they are telling us to revert back to 1.1 until SP3 is released. While we are able to receive CCDAs we get an error with each regarding a 'CANNOT_RECONCILE' and it not counting towards MU.

Outside of that we didn't experience any other issues with the switch but with Virence / Athena recommending to revert back we'll be doing that until the summer SP release.

Posted : April 5, 2019 1:42 am

swestfisher

(@swestfisher)

Posts: 132

Estimable Member

When we upgraded to 12.3.2 we just threw the switches - and nobody noticed.
I believe you can enter " 2.1\n" in the correct place in QIE for testing - check https://www.qvera.com/kb/index.php/1794/what-steps-need-occur-qie-support-the-new-calls-get-either-ccda?show=1794#q1794.
Steve

Posted : April 5, 2019 1:45 am

jtlewis

(@jtlewis)

Posts: 35

Eminent Member

Do you have this case number for this? I would like to follow up with GE on this to get a complete rundown of the issue. We are about to upgrade this upcoming weekend in order to becoming MU compliant, but it sounds like GE is saying that MU won't work until SP3 is released?

Posted : April 8, 2019 3:32 am

Luladin

(@luladin)

Posts: 25

Eminent Member

Case # 03279969.

Posted : April 8, 2019 3:37 am

tdimitrov

(@tdimitrov)

Posts: 43

Eminent Member

I thought that the prerequisite for CCDA 2.1 (and API Patient access) is to also have Azure AD integration...and maybe you've already had that in place...

Posted : April 10, 2019 4:26 am

swestfisher

(@swestfisher)

Posts: 132

Estimable Member

That is part of the process - so yes, we already had the Azure AD integration running.
steve

Posted : April 10, 2019 5:56 am

lic08

(@lic08)

Posts: 286

Reputable Member

So can we enable ccda 2.1 without sp3 or should we wait until we upgraded first then enabled ccda 2.1? Thanks

Posted : July 9, 2019 8:27 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