EHR Implementation Steps For Your ENT Practice

EHR Implementation Steps For Your ENT Practice

dr_EHR / June 7, 2016

Whether transitioning to electronic health records (EHR) for the first time or switching between systems, the implementation of an EHR places significant requirements on an ENT practice making the change.

Download 10 Implementation Mistakes to Avoid

Any transition requires and assessment of goals and objectives, along a change in behavior and workflow for both providers and staff.

Here is a brief overview of the steps your Otolaryngology practice will take during an EHR transition:

Assess Your Practice

The assessment phase establishes all of the other implementation steps. It involves examining the current state of your ENT practice, your practice needs, and a readiness assessment of financial, technological and training requirements.

Is your practice actually ready to make such a large change in process? What issues must be tackled before a change can be considered? If it is concluded that the practice is capable of changing its operating procedures without major problems, then the practice may be ready for an EHR implementation.

Plan Your Goals

One of the major advantage of an EHR system change is that it allows providers and staff the opportunity to break free from existing workflow inefficiencies. If done properly, providers and staff will adapt their workflows to take advantage of the EHR productivity advantages.

To do this, specific goals must be defined for every element of the practice. An ENT practice has different needs than other types of medical providers. What are the current clinical and surgical workflow processes? How will the EHR change specific procedures and improve efficiency? What adaptions and changes to the workflow will occur in financial, operational and clinical aspects of the practice – and how will they be handled?

Mapping out what is required for the transition includes determining the specific tasks and sequence of tasks required, roles of people involved in the plan, how the EHR will impact and improve existing process, along with continuity of care and timing issues.

In addition to creating a project plan, a project transition team will need to be created. That team typically includes:

  • EHR Project Lead
  • Physician Champion
  • Data Administrator
  • Vendor Implementation Specialist
  • Practice Change Leader
  • Key Users

Establishing realistic goals and assigning the right people will go a long way to making sure the implementation is successful.

Select Your EHR

Choosing an EHR for your ENT practice is a decision that will affect your practice for years to come. It requires a careful evaluation of multiple EHR vendors.  Some practices choose an EHR first and adjust their goals to the chosen system. However, most practices develop their goals and use them as the criteria for the EHR, and then finalize their plans after they have made their selection.

Several important question include:

  • Does the EHR platform meet your needs? How easy is the system to use? How does it integrate with other systems, such as practice management, billing systems and public health registries? Is the system server-based or cloud-based? What are the costs?
  • Does the EHR match your specialty? A specialty-specific EHR for ENTs is designed to meet the needs and workflows of Otolaryngologists. They include built-in forms and templates such as thyroid evaluation, sleep apnea, sinusitis, hearing loss and more.
  • How will the transition be handed? How long will it take to complete? What training is involved? How will data be migrated to the new system? How will billing and communications be effected?
  • Is it Meaningful Use certified? Your EHR should be certified for all stages of Meaningful Use, particularly if your practice plans to participate in federal EHR incentive programs.


Vendors provide training and assistance during an EHR implementation, but this training will only work if all of the staff that will use the EHR are involved. This is where the process comes together. Training should not be limited to the time before implementation. After the launch, follow-up and ongoing training will be required to keep up with new features and processes.

Go Live

The ‘go-live’ time refers to when all the planning and preparation is put into place. It is the first day the EHR is used in a patient care setting. Here are some tips to make your go-live launch go smoother:

  • Prepare and plan. Develop a full list of requirements needed to go live, detailing each step of the patient care delivery process. This will help eliminate some of the workflow problems that may occur during the switchover.
  • Conduct testing and rehearsals for each step in the workflow. Test to ensure that staff are familiar with what they need to do for each step of the patient care, from initial intake, to surgical workflow, and all the way through billing.
  • Have disaster recovery procedure in place. Plans should be in place in the case of a major problem, such as a hardware or data issue. These contingencies should not only be for the go-live date, but also for when the new system is fully in place.
  • Plan for more time. When an EHR is first rolled out, providers will still be learning to use the EHR and will need additional time for patient encounters. There will be an initial workflow slowdown while physicians and support staff adjust to the transition. 

Post-implementation Follow-up

The final phase involves evaluation of the implementation and the ongoing process of ensuring that the system meets the practice goals and provides effective patient care. Post-implementation results are often different than what was originally planned. Continuous evaluation will help achieve the practice goals and improve workflows, all while leveraging the advantages of the EHR.

Implementing a new EHR for your ENT practice is an ongoing process, not a one-time event. A successful switchover can only be achieved when there is a commitment to the project by all involved parties and it is carried out to completion.

Download 10 Implementation Mistakes to Avoid