Solution Comparison

You're migrating EHRs. Does the phone setup go back to square one?

What happens to call flows, intake questions and routing rules when a practice moves from Tebra to AdvancedMD, or ends up running both after an acquisition — and which part of the setup is actually EHR-specific.

By MedReception AI, physician-built by Paul Toomey, MDPublished Aug 6, 2026Updated Oct 20, 2026

Call flows, intake questions and routing rules are configured on the AI, not inside the EHR, so they are not lost in a migration
The EHR-specific piece is the connector: appointment write-back and new patient creation (name, DOB, phone) repointed at the new system
Tebra and AdvancedMD are both named integrations, so neither end of the move is a first-of-its-kind build
Clinical intake comes back as a structured summary for staff review on either EHR, so the filing habit your team learned does not change
Access is granted with OAuth or API keys by your administrator, so a cutover never involves handing over EHR usernames and passwords
Specialty call flows already built for urology, orthopedics, primary care, dermatology, surgical centers and urgent care carry across the move

How it pays back

The migration is a connector change, not a rebuild

The months of work in an AI receptionist are the call flows, the intake questions and the routing rules. None of that lives in the EHR, so none of it is thrown away when the EHR changes underneath it.

An acquisition that arrives on the other EHR is not a dead end

Practices rarely change EHRs by choice; they inherit one. Both Tebra and AdvancedMD being named integrations means the inherited system is a supported destination rather than a reason to run two phone setups.

Nothing your staff learned has to be relearned

Intake still arrives as a structured summary for review and filing. The desk workflow your team built around that does not change because the chart behind it did.

Your administrator controls access at both ends

Access is granted through your EHR's integration settings using OAuth or API keys, and you control what can be read and written. Turning off the old connection is something your administrator does, not something you have to request.

9 named EMR integrations

Tebra, athenahealth, eClinicalWorks, Elation, Cerbo, Hint, ModMed, TherapyNotes, Accuro, pMD, PS Suite, Nextech

Appointment and demographic sync

Bookings and new patient data (name, DOB, phone) written to EHR; clinical intake returned as structured summary

HIPAA compliance built-in

Encrypted data transmission, secure call recording, audit trails

Frequently asked questions

We're moving from Tebra to AdvancedMD. What actually has to be redone?

The connector. Appointment write-back and new patient creation are repointed at AdvancedMD, and the mapping is tested. Call flows, intake forms and routing rules stay as they are, because they were never stored in Tebra in the first place.

We acquired a practice that runs the other EHR. Can one setup cover both?

Both Tebra and AdvancedMD are supported natively, so neither site needs a different vendor. Whether a single deployment spans both systems or each site keeps its own connector depends on how your locations and instances are structured, and that is worth working through on a discovery call rather than assuming.

Do we hand over our EHR login during the switch?

No. Access uses secure OAuth or API keys rather than a username and password. Your administrator grants it through your EHR's integration settings, and you control what the system can read and write.

Do our intake questions have to be rewritten for the new EHR?

No. Intake questions belong to the call flow, not the chart. On either EHR the clinical portion of intake comes back as a structured summary for your team to review and file, so the questions and the review step both survive the move.

Our specialty workflow was configured for the old system. Does that configuration move?

Yes. Specialty call flows and intake customization sit on the AI side. Urology, orthopedics, primary care, dermatology, surgical centers and urgent care configurations carry across a connector change rather than being rebuilt against the new EHR.

Bring this to your practice

See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.

Book a Demo Contact Us

Want the numbers first? See plans and pricing