Summary
Ask which EHRs by name, and ask whether the integration is a native API or a browser extension. Those are different products and both get called integration.
Some scribes push through a Chrome extension, sometimes in beta and on the top tier only. Some put push-to-chart above the entry plan. Some use SMART on FHIR. A few are native in the large US hospital records systems and were built for people who have an IT department. If your answer is none of the above, you are copying and pasting.
See it in your clinicA native two-way sync, so the briefing is assembled from your record rather than only from the room.
Request a demoWhat integration means
The word covers three different things and vendors rarely separate them.
A browser extension watches your EHR in a Chrome tab and pastes text into fields. It works, it needs your record open in the browser, and it breaks when the EHR ships a UI change.
SMART on FHIR is a standard. It reaches a wide set of records without a bespoke connector for each and it is how at least one scribe reaches several of the large US records systems. What it can read and write depends on what each site has enabled, which is worth checking rather than assuming.
A native integration is built against one EHR's own API. It is deeper, it keeps working when the EHR ships a UI change, and it costs the vendor a great deal to build and maintain. The scribes that have this inside the large US hospital records systems are also enterprise products with procurement cycles and no published price.
What to ask before you buy
Name your EHR and ask whether it is supported today, in general availability, not on a roadmap and not in beta. Ask whether the note pushes into the correct encounter or arrives as an attachment somebody has to file. Ask whether coding goes with it. Ask which tier it is on, because on some products the answer is not the one you were quoted.
Then ask whether it reads as well as writes. A push-only integration puts the note in the chart. It cannot tell you the eGFR came back at 45 on Thursday, because it has never read anything.
Ask us for your EHR by name
wai Clinician Plus syncs both ways natively. Reading matters as much as writing, because the briefing that opens before the patient sits down is assembled from the record, and the coding attaches to the right problem because the system can see what the problem is. The number no scribe on this page reaches is the code. Up to 19 percent of E/M visits are undercoded at roughly $37 each, and Medicare Advantage downcoding runs a reported $28,000 to $74,000 a physician a year without ever showing as a denial.
We are not going to publish a support matrix here, because this part of the category changes monthly and a list on a blog post is out of date before you read it. Send us your EHR by name and we will tell you yes, no, or roadmap, and put it in writing.
Do the same to everyone else on your shortlist. A survey of 121 AI scribe products found 42 percent require a demo before disclosing anything, and brand-to-manufacturer discrepancies made even regulatory status hard to trace.1Kaczmarek K, et al. Trust Me, I Might be a Medical Device, The Problem with AI Scribes. Research Square, preprint, March 2026. Survey of 121 AI scribe products.
Reading, not just writing
The briefing opens before the patient sits down, built from the chart. Fourteen months since retinal screening. eGFR 45 on Thursday. Metformin never titrated. None of it was said aloud in the room, and a microphone would not have caught any of it.
A push-only integration cannot do this at any price. Writing into the chart and reading out of it are different engineering problems, and most of this category has only solved the first.
What we are not claiming
Nobody in this category integrates with everything, ourselves included. If your record is not on our list, we are not the right purchase and a browser extension may genuinely be the best available answer for you.
Integration depth does not settle whether these tools work. The only randomised trial found the best product cut note-writing time by about 41 seconds and neither product reduced after-hours record time, and one of the two has the deepest integration in the market.2Lukac PJ, et al. NEJM AI 2025;2(12).
Availability
wai Clinician runs a 7-day trial. Pricing is on one page.
Frequently asked questions
Which AI scribes integrate with the large US hospital records systems?
Two enterprise scribes have native integrations with the largest US hospital records system, and one reports the deepest in the category across 300 or more health systems. Both are enterprise products sold through procurement with no published price, so for an independent practice the integration exists and the product is not available to you. Another reaches that system through SMART on FHIR, which is a standard rather than a bespoke connector, and what it can read and write depends on what your site has enabled. Ask any vendor whether support for your system is in general availability today rather than on a roadmap.
What is the difference between a Chrome extension and a native EHR integration?
A browser extension watches your EHR in a Chrome tab and pastes text into fields. It requires your record open in the browser and it breaks when the EHR ships a user interface change. A native integration is built against the EHR own API, keeps working through interface changes, and costs the vendor a great deal to build and maintain. The more useful question is whether the integration reads as well as writes. A push-only integration puts the note in the chart but cannot tell you a result came back on Thursday.
What should I ask a vendor about EHR integration?
Name your EHR and ask whether it is supported today, in general availability, not in beta and not on a roadmap. Ask whether the note pushes into the correct encounter or arrives as an attachment somebody has to file. Ask whether coding goes with it. Ask which tier the integration sits on, because on some products it is the top tier and on others it is above the entry plan. Then ask whether it reads as well as writes. Verify all of it directly, including with us, because this part of the category changes monthly.
Ask us about your EHR by name.
Start the trial and push a note into your own record on day one. If it works, the 90-day pilot reports revenue, hours saved and patients cared for from your clinic. If it does not, you have lost a week.
About this article. Written and published by wai, which sells one of the products described. Integration claims about other products are drawn from their own published material or independent reporting, and this part of the category changes monthly. Confirm your own EHR directly with any vendor before buying, including us. All names are marks belonging to their owners. wai has no peer-reviewed clinical trials published to date and does not claim any.
Partner with us
See it on your own patients, then build it with us
Thirty minutes on your own patients, doctors and rules, in your market. We reply within one working day, and the clinics that partner with us early shape what we build next.
See what wai does between the visits