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

CQR - CMS 138 Tobacco Use

MU, CQR, PQRS, etc.

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

64 Views

RSS

kmarsh

(@kmarsh)

Posts: 85

Estimable Member

Topic starter

Is anyone else on EMR 9.8.10_5 (2092) / DB 9.8.10_5 and having the results for the Tobacco Use measure coming back 0%. This happened shortly after switching the measurement period from 2017 to 2018 in mid-March. We resent the 2018 data. We have reviewed our forms. We see nothing in the CQR documentation that gives us a hint as to what might have happened. The year is almost half over and we have patients returning for a 2nd or 3rd office visit so we should have started seeing percentages by now. At each visit the patient's smoking status is screened and if a tobacco user the patient receives intervention. We are using the SMOK STATUS and SMOK ADVICE observation terms. Data Mapping seems appropriate (but who really knows). We have asked for clarification but haven't gotten any futher with understanding what we are doing wrong. There is apparently a fix for this measure if you are on 9.12 but nothing has been mentioned about fixing 9.8. Has GE abandoned 9.8 even though according to CMS cert 2014 is still ok to use this year? We are frustrated and confused.

Posted : June 19, 2018 10:00 am

mcarlo

(@mcarlo)

Posts: 66

Trusted Member

Hi,

We are affected by this as well. After much back and forth with GE we were told the following.

I have a little more information on the issue with CMS138 that is specific to EMR customers. It appears the SORTVALUE column in the ObsMapping view is malfunctioning and causing the data sent to CQR to be Unmet instead of Met. We have been told it is resolved in EMR 9.12 SP2.

Hope this helps! Misty

Posted : June 19, 2018 10:11 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