Home Forums Discussions Meaningful Use WARNING: Version 9.1 Bug Sabotaging MU Attestation $$$$

There is a bug in Version 9.1 that I found accidentally after upgrading to 9.3.1 six weeks post our 9.1 upgrade. MU OBJECTIVE 8: Timely access (VDT) View, Download, Transmit. WITH VERSION 9.1 EACH INDIVIDUAL CLINICAL SUMMARY MUST BE MANUALLY SENT TO THE PATIENT'S PORTAL OR YOU RECEIVE NO CREDIT!!! Our practice has taken pride in maintaining a 95-98% compliance rate until our 9.1 upgrade 12/23/16. Looking at an MU Report today, 2/3/17 immediately after upgrading to 9.3.1, our compliance % had dropped 1/1 thru 2/3, 2017, from 95-98% to 5%!!! Had our Administrative Option preference changed with the upgrade? No. As had been the case prior to both upgrades, "Automatically send a Clinical Summary to the patient's portal account when signing off on an encounter" remained checked throughout all three versions of AC in use over the past three months. I immediately contacted AC support via CHAT. They had no idea what I was referring to and suggested I reach out to MU Support. MU Support responded within an hour and informed me of "the bug" which has allegedly been addressed/fixed in Version 9.3.1.

I said, "Prior to upgrading and now after finding this gross error, I have pored over all the Release Notes for both upgrades, 9.1 and 9.3.1 and could find no mention/warning of this! If I had been made aware, I would have started to manually send the summaries over. How was I supposed to know? Now my MU Report shows a total failure!"

I was told that "a letter" had been sent out in October. October, three months before I had even considered upgrading. I have since reviewed every email this office received 10/1 thru 10/31, 2016: Backup confirmation, Training announcements, Sales pitches for PM, PriMed info, Webinars, Payment AC info, CME contests, and finally, perhaps the most official announcement of what to look for or be beware of in AC, the October Newsletter. The Version 9.1 bug that sabotages MU Attestation was not mentioned.
I am certain I will never hear from AC regarding this, but a letter citing their failure to notify trusting clients should be forthcoming both as a ?mea culpa? and documented proof that the MU failure was not the fault of the medical practice, but the Amazing Charts EHR.

since this will have bearing on several clients that are considering moving to 9.3.1, let me restate this to make sure I understand what you are stating.

There was a bug in 9.1 that reported MU Objective 8 as compliant/accomplished, but the reality is that is only scored as accomplished if it was done MANUALLY. By upgrading to 9.3.1, the scoring and requirements are applied and only MANUAL transmission are scored as compliant/successful.

Do I have that correct?

Yes I had same bug on 9.1. Luckily, I discovered it in October by running test MU reports. We then did the clinical summary to portal manually.

Anyone know if we need to keep doing this in 2017 with MACRA/MIPS/MU?

For what it is worth, this was reported here by AC. The post was put up in late October:

"Meaningful Use (MU) reporting bug ? In Versions 9.0, 9.1 and 9.2 there is a bug that impacts your MU reporting. If you have set the option to automatically send the CCDA to the patient portal when an encounter is signed off, those CCDAs will not be automatically counted in the MU calculation. They ARE being counted correctly when sending them manually after each encounter. This issue be fixed in the next version (9.3) of Amazing Charts. Please be sure to send CCDAs manually for the time being if you?re on an affected version."