Practice Technology

Switching EHRs: Protecting the Front Desk

Protect the front desk during an EHR switch: pre-load schedules, check converted data, train early, reduce templates at go-live and staff the phones.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why the front desk carries the go-live
  2. The timeline: 90 days out to 30 days after
  3. Check the converted data by hand
  4. Train early, on real tasks
  5. Lighter schedules and extra coverage at go-live
  6. Keep patients informed
  7. Keep reminders and confirmations running
  8. The go-live issue log
  9. Frequently asked questions
  10. References
Practice Technology: Switching EHRs: Protecting the Front DeskArticle coverPRACTICE TECHNOLOGYSwitching EHRs:Protecting the FrontDeskAva Medical IntakeInsightsPractice Technology: Switching EHRs: Protecting the Front DeskArticle coverPRACTICE TECHNOLOGYSwitching EHRs:Protecting the FrontDeskAva Medical Intake

Key takeaways

  • The front desk feels an EHR switch first: every booking, check-in and phone call slows down while staff learn new screens.
  • Convert and check future appointments, demographics and insurance before go-live, and pre-load schedules so day one starts clean.
  • Train front desk staff early, on their real tasks, and name super users who can help colleagues at the desk.
  • Plan lighter schedules and extra phone coverage for the first weeks, and tell patients what to expect.

Why the front desk carries the go-live

An EHR switch is often discussed as a clinical project, because documentation changes the most. But the first people to feel it are at the front desk. On go-live morning they must find patients, check them in, take payments and answer phones on screens they have only seen in training, while the waiting room fills up.

Almost every practice has been through at least one EHR implementation. By 2024, 91% of US office-based physicians used a certified EHR, with another 4% using a non-certified one[1]. Many are now on their second or third system. The lessons are consistent: problems at go-live usually come from converted data that nobody checked, staff who trained too late and schedules that stayed full.

Staff stability adds risk. In May 2026, 29% of US medical group leaders reported higher staff turnover than a year earlier, 39% about the same and 30% lower[2]. A difficult go-live can push a stretched front desk team over the edge, so protecting them is also a retention decision.

US medical group staff turnover in 2026 compared with 2025MGMA Stat poll, May 2026
US medical group staff turnover in 2026 compared with 2025Stacked bar chart. Higher: 29%; About the same: 39%; Lower: 30%.Higher: 29% (30%)About the same: 39% (40%)Lower: 30% (31%)US medical group staff turnover in 2026 compared with 2025Stacked bar chart. Higher: 29%; About the same: 39%; Lower: 30%.Higher: 29% (30%)About the same: 39% (40%)Lower: 30% (31%)
  • Higher 29%
  • About the same 39%
  • Lower 30%

Source: Medical Group Management Association (MGMA), 2026[2]

Show the data
ItemValue
Higher29%
About the same39%
Lower30%

The timeline: 90 days out to 30 days after

  1. 90 days before: map front desk tasks

    List every task the desk does in the current system, from booking a new patient to closing the day. This list becomes the training plan and the test script.

  2. 75 days before: decide what converts

    Agree with the vendor exactly which data moves: future appointments, demographics, insurance, guarantors, balances, recall dates and alerts. Decide what stays behind and where staff will look it up.

  3. 60 days before: build templates

    Recreate provider templates, appointment types and rules in the new system. Have schedulers check them against real weeks.

  4. 45 days before: name super users

    Choose one or two front desk staff to train first and deepest. They test the build, help write quick guides and support colleagues at go-live.

  5. 30 days before: test conversion

    Run a trial conversion and check samples by hand: appointments, names, dates of birth, phone numbers, insurance and balances.

  6. 21 days before: train everyone

    Role-based training on real tasks, followed by practice time on a test system. Repeat the hardest tasks a week later.

  7. 14 days before: reduce templates

    Lighten schedules for the first weeks after go-live and move non-urgent visits where needed.

  8. 7 days before: tell patients

    Let patients booked in the first weeks know that check-in may take longer and that they may need to complete new forms.

  9. Go-live: final conversion and pre-load

    Convert future appointments, check the first week's schedule against the old system line by line, and open the doors.

  10. 30 days after: review

    Review the issue log, retire workarounds and plan follow-up training.

Check the converted data by hand

Data conversion errors are the most common cause of front desk pain at go-live. A future appointment that converts to the wrong provider or time, or a patient whose insurance did not move, becomes a problem at the desk with a patient standing there. Sampling before go-live catches most of them.

  • Future appointments: compare the first two weeks in both systems, every appointment, by provider and time.
  • Demographics: check a random sample of records for names, dates of birth, addresses, phone numbers and preferred language.
  • Insurance: check primary and secondary plans, subscriber details and effective dates for a sample.
  • Balances: check that patient balances match for a sample, and decide how old balances will be shown.
  • Alerts and preferences: check that flags such as interpreter needs, accessibility requirements and communication preferences moved.
  • Recall: confirm that recall dates and types converted, or plan how the recall list will be rebuilt.

Rule of thumb: if the sample shows more than a handful of errors in any area, stop and fix the conversion mapping before go-live. Fixing records one by one after go-live costs far more time.

Train early, on real tasks

Front desk staff often get the shortest training slot, late in the project. Reverse that. Their work touches every patient, and their speed sets the pace of the day.

  • Train on the practice's own task list, using realistic fictional patients, not the vendor's generic demo data.
  • Keep sessions short and hands-on, with practice time on a test system afterwards.
  • Give each person a one-page quick guide for their top ten tasks, written by your super users.
  • Time key tasks in practice: registering a new patient, finding the next slot, checking in, taking a payment. Retrain where times are far above the old system.
  • Include phone scripts for the questions patients will ask about the change, such as new portal logins.

Lighter schedules and extra coverage at go-live

Reduced templates feel expensive, but full schedules during go-live cost more in overtime, errors, long waits and unhappy patients. Plan the reduction and the recovery together.

Example: a fictional five-provider clinic cuts each provider's template by about a quarter for the first week and by about a tenth in the second, protects urgent slots and adds a sixth person at the front desk for two weeks. Visits removed from the first week are rebooked into extended sessions in weeks three and four.

  • Lengthen check-in slots, or stagger arrivals, so the desk is not hit by several patients at once.
  • Add phone coverage, because patients call more during a change: new portal logins, form questions and appointment checks.
  • Keep a super user free of patient tasks at the desk during peak hours to solve problems.
  • Have the vendor's support on call during clinic hours for the first week, with a direct line.

Costs are already rising for most practices: 84% of US medical groups reported year-to-date operating costs above the same point in 2025[3]. A go-live plan that avoids weeks of overtime and rework is part of cost control, not a luxury.

Keep patients informed

Patients cope well with change when they hear about it first. Tell them what will be different and what they need to do.

Message to patients: 'We are moving to a new records system on [date]. Your appointments are not changing. You may be asked to fill in a short form or set up a new patient portal login; we will send you a link. Check-in may take a little longer for a few weeks. Thank you for your patience.'

Patients have rights to their records throughout. A covered entity must act on a patient's request for access no later than 30 days after receipt, with one extension of up to 30 days[4]. Make sure staff know how to fulfill requests for records that stay in the old system.

Keep reminders and confirmations running

Reminder systems are often connected to the old EHR or PM system. If they stop during the switch, no-shows rise just when the schedule is fragile. Confirm with each vendor how reminders will be handled before, during and after go-live, and test a reminder from the new system before the old one is switched off. See patient engagement platforms for how these tools connect.

The go-live issue log

Keep one shared log for every problem raised at the desk: what happened, which patient or task, who owns the fix and when it is closed. Review it at a short daily huddle for the first two weeks and weekly for the rest of the month.

  • Group issues by type: conversion errors, build problems, training gaps and vendor bugs.
  • Fix build problems such as wrong appointment lengths centrally, not by individual workarounds.
  • Turn repeated questions into quick-guide updates.
  • Close the log formally at 30 days, and plan the next round of training.

For choosing a system in the first place, see the practice management software checklist, and for dental offices, dental practice management software.

Frequently asked questions

How much should we reduce schedules for an EHR go-live?

It depends on the practice and how well staff are trained. Many practices lighten schedules for the first week or two and add extended sessions afterwards to catch up. Plan the reduction with your vendor and super users.

What data should convert to the new system?

At a minimum, future appointments, demographics, insurance, guarantors and alerts. Agree the full list in writing with the vendor, and decide where staff will look up anything that stays behind.

When should front desk staff be trained?

Early enough to practice, but close enough to go-live that they remember. Training a few weeks before, with practice time and a refresher, works well for many practices.

Who are super users?

Staff who train first and deepest on the new system, help test it and support colleagues during go-live. Every front desk should have at least one.

References

  1. Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) โ†‘

  2. Medical Group Management Association (MGMA) (2026). Stabilized but not solved: Staff turnover in medical practices looking no better, no worse in 2026 (opens in a new tab) โ†‘

  3. Medical Group Management Association (MGMA) (2026). Operating costs keep climbing for medical practices in 2026 (opens in a new tab) โ†‘

  4. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR ยง 164.524 - Access of individuals to protected health information (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo