Dental Software Integration: What Connects, What Breaks, Who Fixes It

The reminders stopped going out on Monday. The texting company says its sync program on your server is offline. The practice software's support line says it does not support that add-on. Your computer person has never heard of it. Meanwhile the front desk is confirming tomorrow's schedule by phone, one patient at a time.

The add-ons keep arriving, in sales calls, emails and social media ads, and each one promises that it integrates with your system. This guide maps every connection in a typical dental office, explains the methods in plain words, quotes what the practice software makers themselves say is safe (their pages were read on 12 November 2026), and gives you a checklist to send to any vendor before you buy an add-on. It is written for the office manager who gets the call when two systems stop talking.

What is dental software integration?

Dental software integration means two separate programs exchange information without anyone retyping it: the chart tells the imaging program which patient is in the chair, the schedule tells the texting tool whom to remind, the card terminal tells the ledger a payment went through. Each exchange is a connection with its own method, owner and failure points.

Three plain definitions help with every vendor conversation that follows:

• • Practice management software (PMS): the system that holds the schedule, charts, ledger and insurance, such as Dentrix, Eaglesoft, Open Dental or Curve. Almost every integration in the office has the PMS at one end.
• • Read and write: a tool that only reads copies information out of the PMS. A tool that writes changes your records, for example by booking an appointment or posting a payment. Writing carries more risk than reading.
• • One-way and two-way: one-way sends data in a single direction (the schedule goes to the reminder tool). Two-way also brings something back (the patient's "confirmed" reply appears on the appointment).

An "integrated" product can mean any of these. A demo rarely says which, so the rest of this guide gives you the questions that do.

How do the systems in a dental office connect?

A dental office runs several connections at once, and nearly all of them start at the practice management software. The table lists the nine found in most offices, with the usual connection method, what it leaves installed in your office, the first sign that it has broken, and the first call to make when it does.

Two things stand out. Most connections leave something running on a computer in your building, even when the product is sold as "cloud". And the first sign of failure usually shows at the front desk or chairside, far from the server where the cause sits.

What are the ways two dental systems can be connected?

There are six common methods: an API, a built-in integration made by the PMS maker, a bridge that launches another program, scheduled database reads, direct database writes, and file or print-based exports. They differ in what they can change, what they install, and how easily you can switch them off to test.

Open Dental publishes the clearest plain-language description of these methods, and it is useful whichever PMS you run. Its integration guide says that "generally the only safe way for third parties or larger Dental Support Organizations (DSOs) to write data to the Open Dental data tables is through the Application Programming Interface (API)", and that writing straight to the database "is unsafe, often insecure, and does not allow the office to know what program or user made the change."

The same page explains bridges: program links "do not write data back to Open Dental but allow you to launch the third-party software using a button within Open Dental, often with data included." It adds: "Bridges to imaging software are the most common." That is why the X-ray button behaves differently from a texting tool. The bridge only opens another program. The texting tool reads your schedule and may write to it.

What do the practice software makers say about integrations?

Each PMS maker sets its own rules for who may connect and how. Open Dental and Henry Schein One both publish lists of vendors that use their approved route and say which methods they consider unsafe. Check the maker's current list for any product before you sign, because the lists change.

A place on a maker's list tells you about the method. It does not tell you whether the product is good, or whether the module you are buying works with your setup. Open Dental also lists vendors that use its API "but do not have activity logged in the last 60 days", a reminder that these lists describe connections, and connections go quiet.

The makers are also clear about who carries the paperwork. Open Dental's guide says "Customers are responsible for establishing contracts with these third parties that specify what data is being accessed or written, and for what purpose." In other words, the office, not the PMS maker, decides which outside companies may touch patient data.

What breaks at each connection?

Integration failures often trace back to a change nobody linked to the integration: a Windows update, a replaced computer, a new password, a server that went to sleep, a PMS upgrade. The symptom appears in the add-on, and the cause sits in the environment around it. The patterns below cover the common connections.

Imaging bridges

A bridge depends on a program path and settings that must match on every clinical computer. A replacement workstation set up without them, or a Windows permission change, breaks the button on that machine only. Open Dental's manual gives a typical first test: "If a bridge to an imaging program is not behaving well, first start Open Dental by running as an admin." Our guide to dental imaging integration troubleshooting walks through the whole chain, layer by layer.

Sensors, cameras and scanners

Devices talk to the imaging program through drivers. A Windows feature update can replace or disable a driver, and a different USB port can make a sensor appear as a new device. If one room fails and the others work, the cause is on that computer. See what to do when a sensor stops working after a Windows update, and check driver support before buying with our dental X-ray sensor buying guide.

Phones and AI answering

A phone integration matches the caller's number to a chart and, at deeper levels, writes calls and texts back. It fails quietly: calls still ring, but the screen pop is empty. Common causes are a stopped connector, a changed PMS login, or a phone-system change on the vendor's side. An AI receptionist or answering service that books appointments needs write access to the schedule, so ask which method it uses.

Patient texting, reminders and online forms

These tools read the schedule and often write confirmations and completed forms back. Many rely on a background program on your server. If that computer is off, asleep or mid-update when the sync is due, messages go out late or not at all. For the products themselves, see dental patient communication software compared.

Card payments

An integrated terminal sends the result of each transaction to the ledger. When the link drops, the card is charged but the payment is not posted, and the day will not balance. Terminals also sit on your network, so a router or firewall change can cut them off. Ask the processor how to tell a terminal fault from a posting fault.

Claims, eligibility and attachments

Claims and payment reports usually move through a service on the server, and attachments travel from your imaging software to the clearinghouse. A stopped service or an unsupported image format stalls them. Our guides to dental clearinghouses and dental insurance verification software cover both paths.

Analytics, dashboards and AI tools

Reporting tools read large amounts of data on a schedule. Open Dental warns that "It is not unusual for third-party automated queries to work fine for a long time and then suddenly cause problems." If the PMS slows down at the same time each day, a scheduled reader is a suspect. See dental practice analytics software and AI tools for dental practices for what each one connects to.

Who fixes a broken integration: the vendor or IT?

The add-on vendor fixes its own product and account. The PMS vendor fixes the PMS and its built-in integrations. Your IT provider fixes everything they run on: the server, Windows, services, drivers, the network, logins and backups. When the cause is unclear, IT should diagnose first, because the environment is the one part every integration shares.

This is the gap that general computer support often leaves open, and it is the reason to use dental IT support that knows the practice software and the imaging chain. The wider boundary between the two kinds of help is set out in dental software support vs IT support.

Before any call, collect four facts. They shorten every conversation:

1. 1. What changed. A Windows update, a new computer, a password change, a PMS upgrade or a new staff login in the past week.
2. 1. How wide it is. One computer, one room, one user, or the whole office.
3. 1. The last time it worked. A date and time, even a rough one.
4. 1. The exact words on screen. A photo of the error is better than a description.

For a fuller triage list, see our guide to common dental IT problems and who to call.

The IT side: what an integration adds to your server and network

Every integration adds something your IT provider has to look after: a background service, a login, a key, a firewall rule or a set of drivers. None of it appears in the vendor's demo. If nobody records these pieces when the add-on is installed, they are found later, during an outage.

A computer that has to stay awake. Open Dental's own connector is a good example of the pattern. Its manual says "The eConnector machine should always be on and awake. If turned off, hibernating, or in sleep mode, eServices will not work until the computer wakes up." The same page says to "Only install the eConnector on one machine (typically the server)." Many third-party sync programs behave the same way. Power settings, update restarts and a front-desk computer used as a "server" are common causes of missed reminders.

Background services. A service is a program that runs without a window. It can stop after an update or a crash, and nobody notices until the add-on goes quiet. Each one should be on a monitoring list, so a stopped service raises an alert instead of a patient complaint.

Keys and logins. An API key or database login is the add-on's access to your records. Open Dental's developer page notes that "The customer has the ability to enable or disable a key." Know where that switch is for each integration, who can use it, and which keys belong to vendors you no longer use.

Firewall and network rules. Card terminals, phone connectors and cloud sync tools each need a path through the firewall. A new router or internet provider can close that path without warning.

Windows updates and drivers. Updates are necessary, and they are also a common trigger for bridge and sensor faults. A dental IT patch management routine tests updates against your imaging devices before they reach every operatory.

Backups. Some add-ons keep their own data: recorded calls, signed forms, images. Ask where each one stores it and whether your backup or the vendor's covers it.

Leavers. Each add-on has its own user list. When someone leaves, their logins in the texting tool, the phone portal and the payment portal need closing as well as their Windows account. Our employee IT onboarding and offboarding checklist lists the accounts to cover.

This daily watching, of services, keys, updates and backups, is the core of managed IT services for dental practices, as opposed to help that arrives only after something breaks.

The off switch

One line in Open Dental's guide deserves a place in every vendor contract. It says of third-party tools that read your data, "you should be able to easily turn it completely off, temporarily", because that is how you prove or rule out the integration as the cause of a problem. Ask every vendor how to pause its connection, and write the steps down while the system is working.

What should you check before buying a software add-on?

Before you sign, confirm in writing how the add-on connects to your exact PMS version, what it installs, what it can change in your records, who supports the connection, and how you switch it off. A vendor that answers these clearly is usually a vendor whose integration is well built.

1. 1. Method. Which of the six methods above does it use with our PMS and version?
2. 1. Maker's list. Is it on the PMS maker's published list of approved integrations today?
3. 1. Read or write. What exactly can it change in our records: appointments, ledger entries, patient details, documents?
4. 1. Installed pieces. What is installed, on which computer, and does that computer have to stay on?
5. 1. Access. Which key or login does it use, and who can switch it off?
6. 1. Load. How often does it read data, and at what times of day?
7. 1. Updates. After a PMS upgrade, how soon is the integration confirmed to work, and who tells us?
8. 1. Support boundary. Who do we call when the connection fails, and will the vendor work with our IT provider on the same call?
9. 1. Paperwork. Will the vendor sign a business associate agreement before any patient data moves?
10. 1. Exit. How do we remove it cleanly, and how do we get our data back?
11. 1. Cloud plans. If we move to a cloud PMS later, does the integration still work?
12. 1. Test. Can we run it against a copy of our data or a short pilot before going live?

On point 9, Open Dental's manual says "We recommend having a Business Associate Agreement (BAA) in place with a third-party before enabling a program link." The federal rule text, 45 CFR 164.502(e), says a covered entity may disclose protected health information to a business associate "if the covered entity obtains satisfactory assurance that the business associate will appropriately safeguard the information." Ask your compliance adviser how that applies to each vendor; this guide does not interpret the rule.

Then score what you were told:

How do you add an integration without breaking the schedule?

Add one integration at a time, on a quiet day, with a backup taken first and a written test to pass before the team relies on it. Skipping the test and the rollback plan is how a small fault becomes a morning of cancelled appointments.

1. 1. Record the starting point. PMS version, the add-on's version, and a fresh, verified backup of the PMS database.
2. 1. Confirm the method and the list. Re-check the PMS maker's vendor list on the day; it may have changed since the demo.
3. 1. Agree the install with IT. Which computer runs the service, which account it uses, which firewall rule it needs, and how it will be monitored.
4. 1. Install outside patient hours. An afternoon without patients gives time to undo it.
5. 1. Run the acceptance test. Use a test patient: create an appointment, trigger the add-on (a reminder, a form, a payment of a small amount, an X-ray launch), and confirm the result appears in the right chart on a second computer.
6. 1. Test the off switch. Pause the integration, confirm the PMS still runs normally, then turn it back on.
7. 1. Watch the first week. Check the service each morning, and ask the front desk to report anything that looks different.
8. 1. Write it down. Add the integration to your inventory with the vendor's support number and the steps to pause it.

The integration inventory

Keep one page that lists every integration. It is the document that gets a vendor call moving quickly. For each connection record:

• • The product, the vendor and its support contact
• • The method (API, built-in, bridge, database read, export)
• • The computer that runs its service, if any
• • The key or login it uses, and who can disable it
• • The date it was installed and last tested
• • Whether a signed business associate agreement is on file
• • The steps to pause it

If you are changing practice software altogether, every row on that page has to be rebuilt or retired; the dental software migration checklist covers the sequence.

Does a cloud practice system remove integration work?

No. A cloud PMS moves the database out of your building, but imaging devices, drivers, card terminals, phones and printers stay local and still have to connect. Cloud also narrows which integration methods work, because a vendor can no longer install a program beside the database. Check each add-on again before moving.

Open Dental's page on its cloud version makes the point directly. It lists the integrations expected to work and adds "Not all integrations have been tested." It also says that many API vendors are available to cloud customers, but "Vendors who install a separate program, however, may not be compatible." Our guide to Open Dental Cloud covers that move, and whether you still need a server with cloud dental software explains what stays in the office.

How should a dental group handle integrations across locations?

A group should keep one approved list of integrations, one method standard and one inventory per location. Without them, each acquired office brings its own add-ons, logins and sync programs, and nobody at the center knows which outside companies can write to patient records.

Three habits keep it manageable. Review the inventory of every new location before its systems are joined to the group. Standardize on integrations that use the PMS maker's approved route, so one upgrade plan fits every office. And hold the keys centrally, so an integration can be paused for one location without a site visit. Groups planning this at scale can read more about DSO IT support.

What to ask your IT provider about integrations

A provider that works with dental offices every day should answer these without checking. If you are still comparing providers, the same questions fit into how to choose a dental IT company, and our list of the best dental IT companies shows who publishes what.

For the after-hours question, our guide to the 24/7 dental IT helpdesk sets out what a helpdesk should and should not handle.

How Legend Networking can help

Legend Networking is a Dallas-based dental IT company that has served over 3,500 practices since 2004. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. That environment is where bridges, drivers, sync services and keys live.

The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. You can see the groundwork on a documented technology installation covering computers, networking, dental software and imaging integrations, read about dental practice management software support, or find dental IT in your city.