Upcoming Meaningful Use Hardship Exception Deadline

Summer’s here, and the July 4 holiday weekend is around the corner. Before packing your bags or lighting up the grill, take a moment to review the meaningful use hardship exception guidelines. The deadline to apply for a hardship exception and avoid a 2016 payment adjustment is July 1 at 11:59 pm ET.

You do not need to file a hardship exception if any one of these scenarios applies to you:

  • You successfully demonstrated meaningful use in 2014;
  • You’re a hospital-based provider; or
  • You’re a new eligible professional who didn’t file Medicare or Medicaid claims in 2014.

You can only file for a hardship and avoid the payment adjustment if you weren’t able to achieve and report meaningful use due to circumstances outside of your control. For example, if you used a vendor prior to coming to Eyefinity who was not able to get their EHR software certified in time, you might qualify for a hardship.

The timeline for hardship exceptions and payment adjustments can be confusing since the payment adjustments occur two years after the participation year.

If you failed to participate in this calendar year… File for a hardship exception by this date… To avoid a payment adjustment in this year…
2014 July 1, 2015 2016
2015 July 1, 2016 2017
2016 June 30, 2017 2018

To help you determine if a hardship exception is right for you, use the Hardship Exception Tool. For more information about filing a hardship exception, refer to CMS’ Payment Adjustments and Hardship Exceptions page.

EHR: Your Transition Tool to ICD-10

By Robert L. Bass, OD, FAAO; and Robert Day, Jr., OD

Robert Bass

Robert L. Bass, OD, FAAO

dr_bob_day_web

Robert Day, Jr, OD

The transition to ICD-10 represents a steep challenge for many practices.

Robert L. Bass, OD, FAAO, owner of Optometric Associates, PC, in Manassas, Va., and Robert Day, Jr., OD, owner of Broadway Eye Center in Garland, Texas, recently shared with ROB how they are using their electronic health record solutions to ease the transition to ICD-10 coding by the mandated October 1, 2015, deadline.

Dr. Robert Bass uses Eyefinity EHR, a cloud-based solution. Dr. Day uses ExamWRITER a server-based solution.

Read the rest of this article here: EHR: Your Transition Tool to ICD-10

Reprinted with permission from Review of Optometric Business.

EHR_recordedWebinar

Is Your Software Up-To-Date?

software updateMaintaining your car, home, appliances, and personal health is important to ensure optimal performance. Your software is no different! Are you protected from computer security risks? Is your technology allowing you to run a profitable business while delivering a great customer experience?

If you are using Eyefinity Practice Management or Eyefinity EHR, you don’t have to worry about software updates. Being “in the cloud” means Eyefinity maintains your software, ensuring that you are always using the most up-to-date version of your cloud-based software.

If you are using one of our on-premises solutions, like OfficeMate/ExamWRITER, then you need to download and install the newest software update, OfficeMate/ExamWRITER 12.0. This version will prepare you for ICD-10. It’s a great idea to download and install this version by July 2015, so that you are prepared for the government’s ICD-10 cut over well before the October 1, 2015, deadline.

Keeping up to date with software partner patches is also important. For Example, if you are using the ExamWRITER ePrescribing Interface, there is an update that needs to be installed by June 30, 2015. Partners like DrFirst, make changes to upgrade their functionality which can impact the eprescribing integration with ExamWRITER. Small patch updates only take a few minutes to download and run and are important in preventing interruptions in services you depend on.

We all agree that there are benefits to be gained from the 30K, 60K, and 100K mile car tune ups. Annual physical and optometric exams are something you recommend to your own patients. Don’t forget about the importance of maintaining your software, too!