Has anyone found their data in CQR in accurate? The denominators for my providers is less than twenty for most of the measures for out 90 attestation period.
HA! I just responded to your CHUG email but why not throw it on here too.
No, GE just recently sent out yet another patch to fix their issues with MU and PQRS. They have also sent at least 3 emails apologizing for their system not calculating properly. We just installed the last patch over the weekend but at this point it seems moot. We are going to be filing for the hardship as the CMGMA email suggested being that the government will be granting it to anyone who applies, partially due to the fact that they didn’t get the final ruling out until the 4th quarter.
We have already submitted our MU data for 2015 and GE keeps updating CQR. I have printed all communications sent from GE about the CQR upgrades and added that to my MU folders in case of an audit.
Yes, we've found variable accuracy. We are not using it for PQRS, but even on core/final rule measures it is variable. An example is medication reconciliation denominator being way off...when it has been accurate before. We think it's related to a data resend GE requested, but have had a hard time getting in touch with anyone to verify/troubleshoot since we noted this last week.
This year our numbers look pretty good. But last year our PQRS denominators were low for a couple measures (under 20), so they excluded those measures from our Value based Modifier which kept us from hitting our+ 1 standard deviation bonus which is about an additional 2% of Medicare allowables payment. Not sure what I can do about it at this point other than make sure I don't have the same issues with 2015 PQRS data. Once again, GE has cost us money....
We had to resubmit after installing SP11 - our denominators for "seen by" measures dropped to single digits from 1000+ for Q4 2015.
In addition to the data ingest failing we had to work with GE to create a script to map some G codes that did not map correctly to SNOMED codes - about 9000 visits were affected by this.
After the resend, our denominators were back to normal again. I just dread to think how groups without dedicated Qvera interface experts and SQL DBAs figure this stuff out.