AI for dental practices without replacing Dentrix or Open Dental
A practice does not need a new practice management system to use AI. It needs the door the current one already has, and a rule about what goes through it. This is where the door is for Dentrix, Dentrix Ascend, and Open Dental, the four places AI fits without touching the chart, and the boundary that keeps patient data inside the clinic.
Keep the practice management system and add AI at its edges through the official API: Henry Schein One's programs for Dentrix and Dentrix Ascend, or Open Dental's published REST API. AI fits in four places without replacing anything: the phones and intake, clinical documentation, imaging, and payments and claims. Every tool signs a Business Associate Agreement, takes only the data its job needs, and hands uncertain cases to a person. Our own build posts ACH payments into Dentrix Classic with patient identity kept on the clinic workstation.
Why replacing the system is the wrong first move
The pitch arrives every quarter: move to the new cloud platform and AI comes with it. Sometimes that is right, years from now, on its own merits. It is never the right way to get a first AI result. A practice management migration is months of work, retraining for every person at the desk, and a period where the schedule and the ledger are the least trustworthy they will ever be. The AI feature that motivated it will be one line in a release note by the time the migration ends.
The practice management system is where the chart, the schedule, and the ledger live, and that is exactly why it should stay put. AI belongs at the edges: on the phone before the appointment exists, in the operatory while notes are being spoken, in the imaging queue, and between the ledger and the bank. Every one of those is reachable through the door the current system already has.
Where the door is
| System | The door | What a vendor has to do |
|---|---|---|
| Dentrix (on-premise) | Dentrix Developer Program | Apply, pass a use-case review, sign the API agreement, pay a registration fee per direction and a monthly royalty |
| Dentrix Ascend (cloud) | API Exchange | Hold SOC 2 Type II, use OAuth 2.0, pass a security assessment; more than 140 vendors are listed |
| Open Dental | Published REST API, plus a separate FHIR API for medical interoperability | Read the public specification, register as a developer, pay the API permission tier; phone support is limited and the developer forum is primary |
From the Dentrix Developer Portal, the Henry Schein One API Exchange, and the Open Dental API specification.
The point of the table is the third column. A tool that "works with Dentrix" has either been through one of those programs or it has a workaround: a login it uses to click through your software, or a copy of your database. Ask which. The first is an integration. The second is a liability with a demo.
Four places AI fits without touching the chart
1. The phones and intake
An AI receptionist answers, books into the schedule through the API, and hands anything clinical or uncertain to a person. Intake forms get read into demographics instead of retyped. The chart is untouched; the schedule gains an appointment. We wrote a buying guide for this category, and the short version is: official API, signed BAA, a hand-off list you have tested by calling it.
2. Clinical documentation
AI scribes turn spoken notes and perio readings into charting, and the ones worth considering write into the practice management system rather than into a separate app. DeepCura's 2026 comparison lists the integrations by tool: Bola AI, Denti.AI, DentScribe, and VoiceboxMD name Dentrix, Eaglesoft, and Open Dental; several others have no dental integration and export text instead. The published prices for the integrated ones run from $49 to $199 a month, with Bola quoting per location.
3. Imaging
Radiograph analysis sits beside the chart, not inside it. Medix Dental's 2026 guide lists Overjet with 12 FDA clearances, Pearl with 8, and VideaHealth with 4, all priced by quote. This is the one place where the AI is making a clinical suggestion, which is why the clearance count matters and why the dentist's read still decides.
4. Payments and claims
Between the ledger and the bank is where practices lose money quietly: card fees on recurring payments, claims that bounce on a code, payments that sit unposted. This is the gap products cover least and custom work covers best, because the workflow is specific to how the office runs. It is where our own dental work sits.
The rules that keep it safe
Four rules, and a practice can write them on one page before talking to any vendor.
- Every tool signs a Business Associate Agreement. ai.dentist, written by a practicing dentist, puts it in one sentence: every third-party tool connecting to your system must sign a BAA and demonstrate equivalent security measures.
- Minimum necessary data. A scheduler gets appointment times and contact details, not clinical notes. A payment poster gets payment events and account references, not the chart. The same source gives the example and the principle.
- Patient identity stays inside the clinic where it can. In our build, the cloud carries only opaque payment information. Patient linkage, account context, and every exception record stay on the clinic workstation. Not every tool can be built that way. Every tool can be asked.
- The system stops on uncertainty. An ambiguous match, a clinical question, a reversal. Those go to a person with the detail attached, or the tool is guessing in a clinic.
Find the edge where the hours go.
The ten questions ask about a normal week: what gets retyped, what gets rebuilt, what crosses systems. For a practice, the answer is usually the phones, the notes, or the ledger, and the result says which.
What we built
Our dental payment integration is the fourth edge, built for a practice on Dentrix Classic. Recurring patient payments moved to ACH, which is a fraction of card fees. A clinic-side service on the practice's Windows workstation retrieves each cleared payment, matches it to the patient account locally or stops for staff, enters the payment into Dentrix through the existing interface, and reads the ledger back to confirm. The practice management system was not replaced, not migrated, and not given a second administrative system beside it. It is running in production. We do not publish a savings figure, because the practice has not shared one we can stand behind. The productized version is Chomp.
The patient presentation automation is the same idea at a different edge: clinical inputs assembled into presentations locally, with missing inputs left visible to the operator instead of filled in.
How to start
- Name the edge. Phones, notes, imaging, or the ledger. Where do the hours or the fees go in a normal week?
- Find the door. Which program does your system have, and is the vendor you are considering listed in it?
- Write the four rules on one page and hand them to every vendor before the demo.
- Buy if a product covers the edge. Phones, notes, and imaging usually have one. Test it against the rules.
- Build if the edge is a gap. The ledger and the bank, the lab and the chart, the plan and the processor. That is custom work, and it is scoped after someone has watched the workflow.
The system you have is the system that holds the chart. Keep it, and put the AI where the chart is not.
What to hold on to
- Keep the practice management system. A migration is months of risk for a feature that will be a release note by the time it ends. AI goes at the edges.
- Every system has a door. The Dentrix Developer Program, the Ascend API Exchange, the Open Dental REST API. A vendor is in the program or has a workaround.
- Four edges. Phones and intake, clinical documentation, imaging, and payments and claims. The last is the gap products cover least.
- Four rules on one page. A signed BAA, minimum necessary data, patient identity inside the clinic where possible, and a stop on uncertainty.
- Our build is the fourth edge. ACH payments posted into Dentrix Classic with matching kept on the clinic workstation, running in production.
Questions owners ask us
Can a dental practice use AI without replacing its practice management software?
Yes. Dentrix, Dentrix Ascend, and Open Dental each expose an official API, and AI tools connect through it to book appointments, write clinical notes, analyze images, or post payments while the chart, schedule, and ledger stay where they are. The practice keeps its system and adds AI at the edges.
Does Open Dental work with AI tools?
Yes. Open Dental publishes a public REST API specification, plus a separate FHIR API for medical interoperability, and developers register for permission tiers. AI receptionists and scribes that name Open Dental in their integration list connect through it. Every one should sign a Business Associate Agreement and take only the data its job needs (ai.dentist).
What AI can a dental practice add first?
Whichever edge costs the most in a normal week. Missed calls point to an AI receptionist. Charting time points to a scribe that writes into the practice management system. Unposted payments and card fees on recurring plans point to a payment integration. Imaging AI is a clinical decision for the dentist, with FDA clearances as the first check.
Is it HIPAA compliant to connect AI tools to Dentrix?
It can be, and only under conditions the practice controls: the vendor signs a Business Associate Agreement, connects through the official program rather than a workaround, accesses the minimum data the job needs, and keeps patient identity inside the clinic wherever the design allows. Compliance is the contract and the setup, not the software.
How do I know if a vendor really integrates with Dentrix?
Ask which program it is in, the Dentrix Developer Program for on-premise Dentrix or the API Exchange for Dentrix Ascend, and look for it on Henry Schein One's approved-vendor list. A vendor that is in neither is using a login to click through your software or a copy of your database, and should say so.
What did Prometheus build for a dental practice?
A payment integration for a practice on Dentrix Classic. Recurring patient payments moved to ACH; a clinic-side service matches each cleared payment to the patient account on the clinic workstation, posts it into Dentrix through the existing interface, and reads the ledger back. Uncertain matches stop for staff. It is running in production, and Chomp is the productized version.
Sources
Program facts come from the vendors' own pages; tool lists and prices from two 2026 guides; the build from our record. We have no commercial relationship with any tool named. Checked September 5, 2026.
- Dentrix Developer Portal, "API Exchange Program FAQs" and the Henry Schein One API Exchange. Programs, requirements, and fees for Dentrix and Dentrix Ascend.
- Open Dental, API Specification. The public REST API, the FHIR API, and developer permission tiers.
- ai.dentist, "Open Dental API Integration: HIPAA-Compliant AI Tool Setup". March 26, 2026, by Dr. Jordan Thomas. Business Associate Agreements and minimum-necessary access.
- DeepCura, "Best AI Scribe for Dentists (2026)". August 17, 2026. Scribe tools, prices, and integrations. DeepCura is a vendor in the comparison.
- Medix Dental, "8 Best Dental AI Software Tools for Practices and DSOs (2026)". August 31, 2026. Imaging tools and FDA clearance counts.
- Dental payment integration and patient presentation automation, our records, and Chomp.