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

PQRS Submission Issues

General Discussion

Last Post by jamesedward 10 years ago

4 Posts

3 Users

0 Reactions

66 Views

RSS

gruhlin

(@gruhlin)

Posts: 72

Estimable Member

Topic starter

Is anyone still having issues with submitting your PQRS data? If so did you use appends to add the snomed codes. If you did use this method when did you complete your appends?

Posted : February 20, 2015 5:35 am

jamesedward

(@jamesedward)

Posts: 257

Reputable Member

Rather than placing SNOMEDS onto old documents (like from last April), I added HPIs into the data mapper: GE Functional Measures>GE Seen By>SNOMEDCT 308335008. It seemed to work after a refresh in terms of setting a reasonable full-year denominator (or CQR quietly did something similar on its side). I suppose you could use any flowsheet item that's in all your OVs.

Posted : February 20, 2015 5:43 am

lkeith

(@lkeith)

Posts: 457

Honorable Member

James, just wondering, I added the HPI obsterm to the data mapper as you did. We have done the refresh process for the SOP codes after I had changed the data mapping but it doesn't seem to have made a difference. When you said that you 'set a reasonable full-year denominator' what are you referring to? Just want to make sure that I didn't miss something else that I need to do.

Thanks,

Linda

Posted : March 3, 2015 6:25 am

jamesedward

(@jamesedward)

Posts: 257

Reputable Member

I compared the CQR population count to an Inquiry for Patients, with Appointment Status not Canceled, in the 2014 Calendar Year. The numbers were close enough for me to live with. Re-export 2014 data back over to PQRS after any mapping (via Inquiry). Note also that there's a separate post on CHUG comparing whether Document Type or SNOMEDs really drive the denominator. I don't know whether the HPI or CQR on the back-end made the real difference. GE also has a Orders Insert patch script for some of these PQRS issue which could assist you.

Posted : March 3, 2015 6:36 am

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