Key takeaways
- Integrates with your EHR can mean anything from a nightly file to real-time two-way updates; make the vendor name the level.
- Ask separately what the tool can read, what it can write, how often, and what happens when the connection fails.
- Small practices are less likely to run a market-leading EHR, so confirm the connector exists for your exact system and version.
- Test in a sandbox with fictional patients and watch the chart, not the vendor's screen.
Integration is a spectrum, not a checkbox
Almost every front office tool claims to integrate with your EHR: online booking, reminders, intake forms, payment links, phone systems, call answering. The word covers very different things. Some tools send a PDF to a document folder once a night. Others read the live schedule and write appointments back within seconds. Before you compare features, pin down which level you are actually being offered.
| Level | What it means | What staff still do |
|---|---|---|
| No integration | Separate system with its own patient list | Retype everything; reconcile two lists |
| File or PDF drop | Documents land in the chart as attachments | Read the PDF and key the data |
| One-way read | Tool reads demographics or schedule from the EHR | Enter anything the tool collects |
| One-way write | Tool writes data into the EHR but cannot see changes | Fix conflicts the tool cannot see |
| Two-way, near real time | Tool reads and writes through an API within minutes | Review exceptions only |
None of these is wrong for every tool. A reminder service may only need one-way read access. An online booking tool that cannot see same-day changes will double book. The point is to match the level to the job and get the vendor to commit to it in writing.
Why the answer depends on your EHR
By 2024, 91% of US office-based physicians used a certified EHR, and a further 4% used a non-certified one[1]. So the question is rarely whether you have an EHR. It is which one, which version, and whether the vendor has built and maintained a connector for it.
- Using a certified EHR 91%
Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[1]
Show the data
| Item | Value |
|---|---|
| Using a certified EHR | 91% |
Smaller practices face a harder version of this question. Only 32% of physicians in solo practice used an EHR from one of the five market-leading developers in 2024, compared with 90% in practices with more than 50 physicians[1]. Vendors usually build for the largest systems first. If you run a smaller or specialty EHR, ask for the names of current customers on your exact system and call one of them.
Read access: what can the tool see?
- Which data does the tool read: demographics, insurance, appointments, provider schedules, appointment types, balances?
- Does it read only what it needs, or the whole chart?
- How does it match a caller, form or message to the right patient, and what happens when two patients share a phone number?
- Can we limit what it reads by location, provider or department?
A good answer names fields, not categories. Patient information is not an answer. Name, date of birth, mobile number and next appointment is.
Write access: what can it change?
Write access is where integrations save the most time and cause the most damage. A tool that books appointments, updates addresses or posts payments is changing your legal record and your schedule. Ask exactly what it writes and how a person can tell.
- Which records can the tool create, update or cancel?
- Does every change carry a user or system label in the audit log so staff can see what the tool did?
- Does it respect your scheduling rules: visit lengths, provider templates, blocked times, new-patient limits?
- What does it do when the data it wants to write conflicts with what is already there?
- Can we switch write access off for one function without losing the others?
Sync timing and failure
Ask how often data moves in each direction and what happens when the link breaks. A real-time API, a polling job every five minutes and a nightly batch all get called integration. The difference shows up at 8:05 on a Monday when the schedule changed overnight.
- How long from a change in the EHR to the tool seeing it, and the other way round?
- If the connection is down, does the tool stop, queue the change or carry on with stale data?
- Who gets alerted, and how fast? Is it us, the vendor or nobody?
- Is there a status page and an incident history we can read?
Example: a fictional two-physician internal medicine practice bought an online booking tool described as integrated. The schedule synced once a night. When a physician blocked an afternoon for a family emergency, the tool kept offering those slots until the next morning, and staff spent an hour calling patients to rebook. The practice now asks every vendor to state sync timing in minutes.
Who maintains the connection
Integrations break when either side changes. Your EHR releases an update, a field gets renamed, a security certificate expires. Find out who is responsible before it happens.
- Is the connector built by the tool vendor, the EHR vendor or a third-party integration company?
- Who do we call first when data stops flowing, and what is the response time?
- Does the EHR vendor charge an interface or API fee, and who pays it?
- How much notice do you get of EHR updates, and do you test against them before release?
- Do we need an IT person on our side to keep it running?
Security, BAA and access control
Any vendor that reads or writes patient data through your EHR is handling protected health information on your behalf. A covered entity may let a vendor do that only with satisfactory assurance, in a business associate agreement, that the vendor will safeguard it[2]. If a vendor says it does not need a BAA but wants chart access, stop there.
- Does the tool use its own service account, separate from staff logins, with the minimum permissions needed?
- Can we see a log of every record the tool read or changed?
- Where is data stored, and is it deleted when we leave?
- Who at the vendor can see our patient data, and is that access logged?
Why this matters most for phone work
Phone tasks are where shallow integrations hurt. Practice leaders named eligibility and prior authorization (45%) and scheduling (31%) as the most time-consuming phone tasks for staff[3]. Both depend on live data: the right coverage, the right open slot. A phone or scheduling tool that works from a copy of yesterday's data adds a step to every call instead of removing one.
Clinicians feel the same problem from the other side. Primary care physicians in one study spent 5.9 hours of an 11.4-hour workday in the EHR, including 1.4 hours after clinic[4]. Tools that dump attachments into the chart add to that load. Integrations that write clean, structured data reduce it.
Test it in a sandbox before you sign
Ask for a test environment
Most EHRs offer a sandbox or test practice. Insist the demo runs against it, not against the vendor's own mock-up.
Create fictional patients
Include shared phone numbers, a hyphenated name, a patient with two insurance plans and one with a pending balance.
Run the daily jobs
Book, reschedule and cancel; submit a form; post a payment. Then open the chart and check every field.
Break it on purpose
Change a provider template in the EHR and see how fast the tool notices. Ask the vendor to simulate an outage.
Read the audit log
Confirm each change shows who or what made it and when.
Write down the results
Attach the test notes to the contract as the expected behavior, so a later failure is a breach, not a misunderstanding.
Red flags in the answers
- The vendor says it integrates with every EHR but cannot name a live customer on yours.
- Sync timing is described as regular or frequent instead of a number of minutes.
- Nobody can say who gets alerted when data stops flowing.
- Write access is all or nothing, with no way to switch off one function.
- Changes made by the tool appear in the audit log under a staff member's name.
- The exit plan is a spreadsheet export with no field definitions.
One red flag is a reason to ask a follow-up question. Two or three usually mean the integration is thinner than the sales deck suggests, and your staff will make up the difference by hand.
Questions for your own EHR vendor
The other side of the connection has answers too. Ask your EHR account manager which APIs your contract includes, whether third-party apps need approval, what fees apply per connection, and how they notify connected vendors of upgrades. Keep a one-page register of every connected tool, what it reads and writes, who maintains it and when the contract renews. That register becomes the first thing you check when something goes wrong.
Frequently asked questions
What is the difference between EHR integration and an API?
An API is the technical doorway a system offers for other software to read or write data. Integration is what a vendor builds using that doorway, or using older methods like file transfers. Ask which method a vendor uses and how often data moves.
Is write-back to the EHR always better?
Not always. Write-back saves the most staff time but carries more risk, because the tool is changing your record and schedule. Use it where it removes real retyping, and make sure every change is labeled in the audit log.
Do we need a business associate agreement for an integrated tool?
If the tool reads or stores protected health information on your behalf, yes. Sign the agreement before connecting it to real patient data.
How do we check an integration before buying?
Run it against your EHR's sandbox with fictional patients, perform the daily tasks it is meant to handle, then check the chart and the audit log field by field.
References
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) โ
Legal Information Institute, Cornell Law School (current). 45 CFR ยง 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) โ
Medical Group Management Association (MGMA) (2026). Phones are still a bottleneck costing medical practices time they can't afford (opens in a new tab) โ
Annals of Family Medicine (2017). Tethered to the EHR: Primary Care Physician Workload Assessment Using EHR Event Log Data and Time-Motion Observations (opens in a new tab) โ