Notifications
Clear all
Topic starter
As we're gearing up to attest, we noticed that our NQF 0013 report from GE is showing over 100% for many of our providers. Has anyone else run into this? Any solutions or ideas?
I've pulled apart all of the logic in Crystal Reports and I don't even see a place where they reference the BP obs terms, let alone where they're counting one for each visit with bp sys and bp dia recorded.
It also looks like the report is adding the whole docCount to EncCount when docCount is over 2, instead of just adding 1 for the unique patient.
How did other people attest on this measure? Did you all use MQIC instead of the Crystal Reports to track your data?
Thanks in advance 😀
Rachael
Posted : April 6, 2012 7:49 am
Did you check the subreport for the BP OBS terms?
Posted : April 8, 2012 3:07 pm
I had this same issue occur, I attested showing 100%. The only reason I can think this might be happening is when multiple vitals signs are taken during one office visit.
Posted : April 9, 2012 12:38 am
Topic starter
Unfortunately I'd already checked the obs terms for the more-than-one situation before I posted this.
I will try taking a look at the sub report - I didn't notice it before.
Cross your fingers! 🙂
Posted : April 9, 2012 1:59 am
Topic starter
Just heard back from GE support. Known issue. SPR 49534
When we get a new updated shiny report I'll post here to let you guys know.
Posted : April 9, 2012 2:00 am
Hi Rachael,
Are you going to use MQIC for NQF0013 then?
Tonya Racine
Posted : July 3, 2012 7:59 am
Topic starter
Because we attested with dates that did not line up with MQIC dates, we just reported 100% for the providers that had over 100% on the report.
-Rachael
Posted : July 9, 2012 2:42 am
I'm having the exact opposite by my provider showing all 0. I've added the observations that we use to the sub report. This worked in the version of the report prior to the v1.9 release; anyone with this same issue?
Posted : September 6, 2012 1:06 am
When we had that problem I called support and they installed an upgraded version of that MU report, solved the issue.
Posted : September 27, 2012 8:12 am
