Switching EHRs in an Orthopaedic Practice: How to Protect Your Revenue Cycle Before, During, and After Go-Live

An orthopaedic EHR migration puts the revenue cycle at risk in predictable places: surgeon and clinic productivity drops for weeks to months after go-live, charges lag while templates and fee schedules are rebuilt, legacy accounts receivable get neglected while staff learn the new system, and payer enrollments for electronic remittance and claims must be redone.

Practices that protect revenue plan for all four at least six to twelve months ahead, reduce clinic volume deliberately at go-live, run the legacy A/R down on a defined schedule, validate coding and charge capture in the new system before trusting it, and track a short list of daily revenue metrics until they are back at baseline. The evidence on duration is sobering. A study at Duke's outpatient adult reconstruction clinics published in the Journal of Bone and Joint Surgery found labor cost per visit rose from $36.88 to $46.04 two months after an EMR go-live and took about six months to return to baseline.

This guide is written for orthopaedic CEOs, CFOs, and administrators who are evaluating a new EHR, have signed a contract, or are integrating acquired practices onto a single platform.

Why orthopaedic groups are switching

EHR change is common. In a March 2025 MGMA Stat poll, 23 percent of practice leaders said they expected to switch or significantly update their EHR within the next 12 months. Respondents frequently mentioned moves to Epic and platform changes driven by mergers and acquisitions.

For orthopaedics, consolidation is a major driver. Research published in 2022 identified 41 orthopaedic practices acquired by private equity and investment firms between 2004 and 2019, with 70.7 percent of those deals occurring from 2017 to 2019. Since 2022, activity has shifted toward recapitalizations and add-on acquisitions. Advisors to orthopaedic platforms note that acquired groups typically integrate into the platform practice's EHR, accounting, and practice management systems, and orthopaedic industry observers describe combining multiple EHRs as one of the hardest parts of consolidation. In June 2026, for example, ModMed announced that U.S. Orthopaedic Partners was rolling out a single platform across more than 55 locations, replacing nine legacy systems.

The market itself is also moving. KLAS research on independent ambulatory organizations found Epic with more than twice the mindshare of any other vendor among practices with more than 75 physicians, driven largely by Epic Community Connect, while athenahealth led among smaller practices. KLAS's February 2026 report on ambulatory EHR and practice management suites found that nearly all organizations with 11 or more physicians still supplement their core platform with third-party tools, most often because of missing or immature functionality.

Whatever the reason for the switch, the revenue cycle is where the cost shows up first.

What the evidence says about the go-live dip

The research is mixed on the long term but consistent on the short term: expect a dip.

• Orthopaedic clinics: The JBJS study at Duke's adult reconstruction clinics used time-driven activity-based costing across 143 observed visits at baseline, two months, six months, and two years after an enterprise EMR implementation. Labor cost per visit rose about 25 percent at two months, surgeon face time with patients fell from 14.65 to 10.03 minutes, and costs returned to pre-implementation levels by about six months.
• Primary care practices: An AHRQ-funded study of 26 practices in Texas found work RVUs and visits per physician each fell about 8 percent in the first six months and were still 4.5 percent below baseline at 12 months, while practice expense rose by about $1,650 per physician FTE per month.
• Ambulatory practices over two years: A 2015 study in the Journal of the American Medical Informatics Association tracking 30 practices found productivity fell by about 18 patients per physician per quarter after implementation, and six practices had not recovered by the end of the study, although reimbursement rose because of increased billing for ancillary services.
• Large systems: MD Anderson attributed much of a $405 million drop in adjusted income over ten months in 2016 to its Epic implementation, citing higher expenses and lower patient revenue.

Not every study finds losses. A Weill Cornell study of 203 physicians found productivity and charges rising after adoption, with gains growing over time. The difference is usually planning, training, and how quickly the organization catches revenue cycle problems. HFMA notes that organizations commonly take about 90 days to return to revenue baseline after a conversion, and some well-prepared organizations exceed their pre-conversion baseline within weeks.

For an orthopaedic group, each lost clinic slot also delays downstream surgical, imaging, and physical therapy revenue, so the dip is larger than the E/M volume alone suggests.

The four revenue cycle risks in an orthopaedic EHR migration

1. Productivity and throughput

Surgeons and APPs slow down while they learn new documentation workflows, and medical assistants take longer to room patients. The AMA recommends reducing clinical volume during go-live, accepting lower early productivity, and adding patient access capacity before the switch so that the backlog does not compound.

2. Charge capture and coding

This is where orthopaedic migrations quietly lose the most money. Visit templates, procedure pick lists, and order sets are rebuilt from scratch, and small errors multiply across thousands of encounters. Common problems include:

• Procedure templates that omit anatomic modifiers (RT, LT, F and T modifiers) or default to modifier 59.
• Injection and DME charges that do not carry the drug units, waste modifiers, or HCPCS codes the old system produced.
• E/M templates that change how medical decision making is documented, shifting the distribution of visit levels.
• Global period tracking that does not carry over, so post-operative visits are billed or missed incorrectly.
• Fee schedules and charge master entries mapped incorrectly, so charges drop or post at the wrong amount.

The AAPC has documented conversions where a provider signature did not transfer to the images sent to the billing team, holding up coding and delaying significant revenue. Testing with real encounters before go-live is the only reliable defense.

3. Legacy A/R

When staff are learning a new system, the old receivables stop getting worked. HFMA's guidance on legacy A/R conversions recommends deciding in advance whether to work legacy accounts in the old system or convert them, backfilling subject matter experts, planning retention for staff who know the legacy system, setting liquidation KPIs, and watching for the risk of staff constantly switching between two systems. MGMA has also noted that many practices keep legacy systems running for years after conversion, with ongoing license and hardware costs that should be budgeted.

4. Payer connectivity and prior authorization queues

Changing practice management systems often means changing clearinghouses. Medicare requires a signed electronic remittance advice enrollment before a provider receives 835 remittances, allows remittances to go to only one designated receiver, and requires advance written notice to the MAC when a provider changes billing agents or clearinghouses. Commercial payers have their own enrollment processes and timelines, which vary. If ERA enrollment lags, payments post manually, denials go unnoticed, and cash appears to stall.

Orthopaedics adds work queue complexity. Open prior authorizations for surgery, advanced imaging, and DME must migrate intact. Medicare's prior authorization program for orthoses now covers a growing list of knee, spine, and other bracing codes, with additional codes added in April 2026 and more scheduled for October 2026. A missed authorization in the transition becomes a CARC 197 denial weeks later.

A revenue protection plan for orthopaedic EHR migrations

Six to twelve months before go-live

• Baseline your revenue cycle. Capture at least three months of charges per working day, charge lag, clean claim rate, initial denial rate by reason, days in A/R, E/M level distribution by provider, and procedure volume by CPT family. You cannot detect a dip without a baseline.
• Plan the legacy A/R strategy. Decide what will be worked in the old system, for how long, by whom, and what the liquidation targets are.
• Start payer and clearinghouse enrollments early. Build a payer-by-payer tracker for ERA, EFT, eligibility, and claim enrollment, and do not assume any enrollment is instant.
• Inventory orthopaedic-specific workflows. Surgery scheduling, imaging and PACS integration, DME dispensing, in-house PT, ASC billing, workers' compensation, and injection drug inventory all need owners.
• Confirm data export rights. Certified EHRs must support export of electronic health information under the ONC certification criterion 170.315(b)(10), and Medicare requires medical records to be retained for seven years from the date of service. Plan access to legacy records accordingly.

Ninety days before go-live

• Test coding and charge capture with real encounters. Run a sample of recent E/M visits, injections, fracture care, arthroscopy, and joint replacement cases through the new templates and compare the resulting codes, modifiers, units, and charges to what was billed in the old system.
• Validate fee schedules and charge master mapping line by line for your highest volume and highest dollar codes.
• Build a cash reserve plan with your CFO and lender based on your own baseline and a realistic dip scenario.

Go-live through day 90

• Reduce clinic templates for the first weeks and add capacity before, not after.
• Watch daily metrics: charges and encounters per day against baseline, unbilled encounters, claim rejections at the clearinghouse, denials by reason code, and cash posted.
• Hold daily huddles between clinical, coding, and billing leads for the first several weeks to fix template and mapping problems as they surface.
• Protect legacy A/R with dedicated staff hours so older balances do not age out past timely filing and appeal deadlines.

Day 90 and beyond

• Compare E/M level distribution and procedure coding patterns by provider to the baseline. A shift is often a template problem rather than a clinical one.
• Retire or archive the legacy system on a defined schedule once A/R is liquidated and record access is secured.

Regulatory changes worth factoring into an EHR decision

Two federal changes are relevant to orthopaedic groups choosing a platform in 2026.

• Electronic prior authorization. CMS's Interoperability and Prior Authorization final rule (CMS-0057-F) requires Medicare Advantage, Medicaid, CHIP, and federal exchange plans to support prior authorization APIs by January 1, 2027. ONC's HTI-4 final rule added certification criteria for electronic prior authorization. Ask vendors how and when they will support these workflows.
• Information blocking enforcement. HHS announced a crackdown on information blocking in September 2025, and provider disincentives, including a zero score in the MIPS Promoting Interoperability category, took effect in 2024. Make sure your migration plan preserves patients' and other providers' access to legacy records.

Frequently asked questions

How long does revenue take to recover after an EHR go-live?‍

It varies by practice and preparation. HFMA notes that organizations commonly take about 90 days to return to revenue baseline, while research in orthopaedic clinics found labor cost per visit took about six months to normalize, and a primary care study found productivity still 4.5 percent below baseline at 12 months.

What is the biggest revenue risk when an orthopaedic practice switches EHRs?‍

For most orthopaedic groups it is charge capture and coding. Rebuilt templates can drop modifiers, units, and charges or shift E/M level distribution across thousands of encounters before anyone notices. Testing real encounters before go-live and monitoring coding patterns by provider afterward are the most effective safeguards.

Should we reduce clinic volume during an EHR go-live?‍

Yes. The AMA recommends reducing clinical volume during go-live and adding patient access capacity beforehand. Planned reductions are less costly than unplanned backlogs, missed charges, and burned-out staff.

What should we do with legacy accounts receivable?‍

Decide before go-live whether legacy A/R will be worked in the old system or converted, assign dedicated staff, and set liquidation targets. HFMA's guidance recommends planning retention for staff who know the legacy system and tracking KPIs until the balance is resolved.

Do we need to re-enroll with payers when we change EHR or clearinghouse?‍

Often yes, especially if the practice management system or clearinghouse changes. Medicare requires a signed ERA enrollment before 835 remittances are received and advance notice to the MAC when billing agents or clearinghouses change. Commercial payer timelines vary, so start early and track every payer.

How does PE consolidation affect EHR decisions?‍

Acquired orthopaedic groups are commonly moved onto the platform practice's EHR and practice management systems, and combining multiple systems is one of the most difficult parts of integration. Standardizing coding logic and revenue cycle metrics across locations early makes the financial effect of each conversion visible.

Keep coding consistent while the EHR changes

The one part of the revenue cycle that should not have to be rebuilt during a migration is coding logic. Maia's AutoCoder works as an agent inside athenahealth, eClinicalWorks, Epic, ModMed, NextGen, and Tebra, reading the note and recommending CPT, ICD-10, and modifier combinations with clinical justification before a human coder touches the chart.

Because the same orthopaedic coding rules apply regardless of which EHR the note was written in, groups consolidating onto a new platform get a consistent coding baseline before, during, and after go-live, which makes shifts in coding patterns easier to catch. Orthopaedic groups including OrthoIndy, OrthoIllinois, Midwest Orthopaedics at Rush, Bone and Joint Institute of Tennessee, and Health Plus Management use Maia today.

See how Maia's AutoCoder supports orthopaedic practices. Book a demo at usemaia.com.