EHR integration explained: how practice software connects to your records (2026)

Almost every practice runs on an electronic record now. ONC's final count, published in June 2026, puts 95% of office-based physicians on an EHR and 99.4% of hospitals on a certified one. The record itself is no longer the problem. The problem is everything else the practice uses: the online booking tool, the reminder texts, the intake forms, the payment terminal, the reporting. Each of those either talks to the record or it does not, and when it does not, somebody at the front desk is typing the same thing twice.

That is what EHR integration means in practice: the connection that lets other software read from and write to the patient record. It is also where most practices are still stuck. In the 2024 National Electronic Health Records Survey, only 42% of physicians said their EHR integrates outside information automatically; 47% said outside records often arrive as a scanned document, and only 21% said they are often integrated as data. In Weave's 2026 survey of 285 owners, office managers and front desk staff at dental, medical, optometry and veterinary practices, 70% said they are not running an integrated software stack, and 63% said staff spend an hour or more a day on manual data entry.

This guide explains what EHR integration is, how it differs from the practice management system, how integrations are actually built in 2026 (and why dental is different), what the federal rules now require, and how to judge the software you are about to buy by how deeply it connects.

What EHR integration means

An EHR integration is a live connection between a practice's record system and another piece of software, so the two share the same patient data without anyone re-entering it. A good one does three jobs:

• Schedule. It reads the real appointment book and writes to it, so an online booking or a confirmation text lands on the schedule staff already look at.
• Chart. It reads patient demographics and history and writes new information back: a health history from an intake form, an updated phone number, a signed consent.
• Ledger. It reads balances and writes payments, so a text-to-pay or a terminal swipe posts to the account instead of being keyed in later.

The word "integration" covers a wide range of depth, and the depth is what to ask about. From shallowest to deepest: a PDF drop saves a document into the chart's document center and leaves the data entry to staff; a one-way read pulls patients and appointments out of the record, for reminders and reports, but never writes anything back; a two-way sync reads and writes the schedule, chart and ledger; and a real-time two-way sync does that within seconds rather than in a nightly batch, so a cancellation at 9:02 is open to the waitlist at 9:03.

EHR vs. practice management system vs. EMR

Three terms get mixed up, and the mix-up matters when you ask a vendor what it integrates with.

• EMR (electronic medical record) is the digital chart for one provider or practice: history, diagnoses, medications, treatment plans.
• EHR (electronic health record) is the same chart designed to be shared across providers, with lab results, imaging and outside records. In everyday use the two words mean the same product, and this guide uses EHR.
• Practice management system (PMS) runs the business side: scheduling, patient demographics, insurance, billing and the ledger.

In medical practices the EHR and the practice management system are often two products or two modules from one vendor (athenahealth, eClinicalWorks and NextGen all sell both). In dental practices one product does everything, and it is called the practice management system: Dentrix, Eaglesoft, Open Dental, Curve Dental, Denticon and the rest hold the schedule, the chart, the perio and the ledger in one place. So "EHR integration" for a dental office means integration with the PMS, and a vendor that says "we integrate with all major EHRs" may mean medical systems only. Ask for your system by name.

How EHR integrations are built in 2026

There are four ways software connects to a record system today. Which one a vendor uses determines how much of the three jobs it can do and how much it costs.

1. Standard FHIR APIs on certified EHRs

Since the 21st Century Cures Act rule took effect, every ONC-certified EHR has to offer a standardized API built on HL7 FHIR R4, with the USCDI data set (version 3 since January 2026), SMART app launch for sign-in and bulk export for populations. Certified vendors had to ship it by the end of 2022, and more than 95% did. Epic publishes its FHIR APIs free at open.epic, with an optional vendor support subscription at $1,900 a year; athenahealth's Marketplace exposes more than 800 API endpoints and charges its clients no interface or setup fees. The catch is scope: the required API is built for patient access and population data, mostly read-only, and the data set is clinical. Writing an appointment to the schedule or a payment to the ledger usually needs the vendor's proprietary API, and in a 2024 JAMIA study of 141 digital health companies, surveyed by UCSF and ONC, 47% named high EHR API fees as a substantial barrier and 52% said proprietary integrations took substantial effort.

2. HL7 v2 interfaces

The older standard still runs most of the plumbing in hospitals and large groups: HL7 reports that more than 95% of US healthcare organizations use v2 messages for admissions, orders, results, scheduling and charges, and ONC's survey of health information exchanges found 96% receive HL7 v2 admission feeds. A v2 interface is point to point, built and priced per connection, and is more common in health systems than in a three-chair dental office.

3. Vendor developer programs

Each record system also runs its own partner program with its own API. On the dental side, Henry Schein One's API Exchange covers Dentrix and Dentrix Ascend, lists 140-plus vendors and about 1,000 endpoints, and requires a security review; Open Dental publishes its API fees per location, from a free read-only tier to $35 a month; Planet DDS runs an API program with about 75 partners across Denticon and Cloud 9. On the medical side, NextGen, Oracle Health, ModMed and Veradigm all run developer portals, free to join, with paid tiers for deeper access. Every one of these is a separate build, a separate review and a separate fee schedule.

4. Integration platforms and unified APIs

The fourth road is to let one company maintain all of those connections and expose a single API. For hospital and health-system data, that market is crowded: Redox connects to more than 100 EHRs, Health Gorilla and Kno2 are TEFCA networks, Zus, Particle and Metriport aggregate outside records, and Rhapsody and Mirth are the integration engines hospitals run themselves. Almost none of them touch dental. Of twelve platforms we checked in October 2026 (the nine in the table below plus Particle Health, Kno2 and Flexpa), none lists a dental practice management system, apart from Keragon's coverage of Open Dental, Dentrix Ascend and Planet DDS. NexHealth's Synchronizer is the exception built for practice systems: one API that reads and writes schedule, chart and ledger data across 15 dental and medical systems, used by NexHealth's own products and by hundreds of developers building for practices.

Why dental is different

Dental practice management systems have, in the American Dental Association's words to CMS in June 2026, "largely evolved outside" the ONC certification program. Most are not certified health IT, most have no FHIR endpoint, and the ADA says current FHIR profiles do not yet consistently support tooth numbering, surface-level restorations, periodontal measurements or odontograms. HL7 published a Dental Data Exchange guide and the ADA demonstrated a full dental record moving over FHIR at a 2024 connectathon, but no dental standard is federally required. The most recent national count we found, a 2019 ADA and Maryland Health Care Commission survey of 645 dentists, had 56% using an EHR at all. That is why integration depth varies so much more in dental, and why the question "which of my forms write fields into Dentrix, and which drop a PDF" gets different answers from every vendor.

What the rules require now

• You have a right to your data. The information blocking rules apply to providers, certified EHR developers and health information networks. Developers and networks face civil penalties of up to $1 million per violation; a practice that blocks access can lose its Promoting Interoperability score under MIPS (about a quarter of the MIPS total) under the disincentives rule HHS finalized in June 2024. HHS issued an enforcement alert in September 2025, and more than 2,000 complaints had been filed by mid-2026, though no penalty had been announced as of October 2026.
• The required data set is USCDI v3. ONC's HTI-1 rule made it the baseline, with the older v1 retired on January 1, 2026. A later proposal to move to v4 was withdrawn in December 2025, and the HTI-5 proposal to cut 34 of 60 certification criteria was still a proposed rule in October 2026.
• TEFCA is live. Eleven qualified networks, including Epic Nexus, eClinicalWorks, Oracle Health and Health Gorilla, connected more than 71,000 sites and exchanged 464 million documents by the end of 2025. It moves clinical documents between organizations; it does not put an online booking on your schedule.
• Payer APIs arrive in 2027. Under the CMS interoperability and prior authorization rule, Medicare Advantage, Medicaid and exchange plans must offer FHIR APIs for patient access, provider access and prior authorization by January 1, 2027, after shorter prior-auth decision deadlines that started January 1, 2026.

None of these rules require a dental PMS to open up, and none of them make a scheduling or payments integration happen. They do mean a medical practice can insist on access to its own records.

What integration does for the practice

The point of integration is that the record stays the single source of truth while patients and staff stop retyping into it. Concretely:

• Online booking that lands on the real schedule. The patient sees true openings and the appointment appears in the book, with no "request" form for staff to call back on.
• Reminders and confirmations from the real schedule. A confirmation by text marks the appointment confirmed in the system; a cancellation opens the slot to the waitlist.
• Intake forms that write to the chart. Demographics, medications, allergies and conditions land as fields, with the signed PDF filed alongside, before the patient sits down.
• Payments that post to the ledger. Text-to-pay, statements and terminal payments post to the account with no end-of-day reconciliation.
• Insurance verified from tomorrow's schedule. Eligibility runs automatically for everyone booked, and the result is on the patient before they arrive.
• Recall from real last-visit data. Overdue patients are the ones the record says are overdue, not a list someone exported last quarter.

The time at stake is real. Primary care physicians in a 2025 JAMA Network Open study spent a median of 3.8 hours a day in the EHR, and a 2023 study of 307 primary care physicians measured 36 minutes of EHR time for every 30-minute visit. At the front desk, 80% of practices in Weave's 2026 survey said duplicate data entry affects their workflow. Patients feel the gap from the other side: 92% told Kyruus Health in 2024 they want to complete pre-visit forms online, which only works if the form reaches the chart.

EHR integration best practices: eight questions before you buy

• Which of my systems, by name and version? "Integrates with all major EHRs" is not an answer. Get Dentrix G7.4 or athenaOne in writing, and ask what happens when you upgrade or switch.
• Read, write, or both? Ask for a demo in which a patient books online and the appointment appears on your schedule, a form lands in the chart as fields, and a payment posts to the ledger. Anything that stays in the vendor's dashboard is a one-way read.
• How fast? Real time, every 10 minutes, or overnight. The difference is whether a cancellation gets filled today.
• What writes as fields and what arrives as a PDF? Especially in dental, the same vendor may write demographics but drop the health history as a document.
• Who built and maintains the connection? A vendor that built its own integration can fix it when the record system updates; one that borrowed it from a third party will wait.
• What does it cost, all in? Some record systems charge the vendor per location for API access, and some vendors pass that through. Ask for the price per location per month including the integration.
• What does my team have to do? Software to install on your server, a vendor security review, an IT visit. The best integrations are set up by the vendor and need staff to log in only to answer patient messages.
• Is there a signed BAA and an audit trail? Any vendor reading your record is a business associate under HIPAA. The agreement comes before the connection, and you should be able to see who accessed what.

Common EHR integration challenges

• Compatibility. The vendor supports your system but not your version, your hosting (on-premise vs. cloud) or your second location's different system.
• Shallow integration sold as deep. A PDF drop or a nightly one-way read described as "fully integrated". The demo in the question above exposes this in ten minutes.
• Cost and API fees. Some record systems charge developers for API access, and the JAMIA study above found fees to be the most-cited barrier; those fees can show up in your bill.
• Staff adoption. If the integrated tool still needs a tablet at the desk or a second login, staff will fall back to the clipboard. Integration should remove steps, not add a screen.
• Data migration. Switching record systems means the integrations have to move too. Ask every vendor what a PMS switch costs before you sign.
• Security. Every connection is another business associate with access to the record. The 2025 breach reports to HHS showed a large share coming through business associates, so the BAA, the access log and the vendor's security attestations are part of the integration, not paperwork around it.

EHR integration software

Two kinds of products carry the label. The first is what a practice buys: patient-facing software that arrives already connected to the record. The second is what a developer buys: a platform that connects their product to many records at once.

For practices: software that comes integrated

For developers: platforms that connect you to many records

If you are building a product for dental or medical practices, the second table is the short version of the problem: the record-network platforms were built for hospital data, and the practice systems your customers run on are mostly not on them.

Frequently asked questions

What does EHR integration mean?

A live connection between a practice's electronic record and another piece of software, so schedule, chart and ledger data move between them without re-entry. The useful question is how deep it goes: whether it reads only, writes back, and in real time.

What is the difference between an EHR and a practice management system?

The EHR is the clinical chart; the practice management system runs scheduling, insurance and billing. Medical practices often have both; dental practices usually have one product, called the practice management system, that does both. For a dental office, "EHR integration" means integration with that PMS.

How do you integrate with an EHR?

Four ways: the standard FHIR API every certified EHR must offer (mostly read-only clinical data), an HL7 v2 interface (common in hospitals), the record vendor's own developer program (one build per system, often with fees), or an integration platform that maintains many connections behind one API. For dental systems, which mostly sit outside federal certification, the last two are the only roads.

How long does EHR integration take?

For a practice buying integrated software, setup is typically days: the vendor connects to your system and your staff keep using it as before. For a developer building a new integration from scratch, each record system is its own project, with a security review and a fee schedule, which is why unified APIs exist.

Is EHR integration HIPAA compliant?

Any vendor that reads or writes your record is a business associate and must sign a BAA before connecting. Integration itself does not create or remove compliance; the vendor's safeguards, your access controls and the audit trail do.

Do dental practice management systems have FHIR APIs?

Mostly not. The ADA told CMS in 2026 that dental systems largely evolved outside the ONC program, and that FHIR profiles do not yet consistently support tooth numbering, surfaces or perio measurements. Dentrix, Open Dental and Denticon run their own API programs instead.

See your schedule, chart and ledger connected

NexHealth is the patient experience platform for 20,000+ dental and medical practices: online booking, reminders, forms, texting, insurance verification and payments, all reading from and writing to the record system you already use, in real time. Book a demo to see it running on your system. Building software for practices? The NexHealth Synchronizer gives you one API across 15 dental and medical systems, with a free sandbox to start.