The question comes up in almost every demo. Sometimes it's the first question. "Does InsureIQ integrate with my PMS?" Open Dental, Dentrix, Eaglesoft, Curve, Carestack — whichever one the practice is running, the question is the same. And the honest answer is no, it doesn't integrate with your PMS. Not today, not because we couldn't, but because we don't think your PMS is the right place to integrate.
That answer makes some people uncomfortable, and we get it. "PMS integration" has been sold to dental practices for so long that it sounds like a requirement instead of a design choice. So let's actually break this down. Why does that question dominate dental software evaluation? What does PMS integration actually deliver — and what does it not deliver? And what is InsureIQ doing instead that we think is the better answer for an independent practice?
What "PMS integration" actually means in dental
When a vendor says they integrate with your PMS, they usually mean one of two things. The first is that they can pull patient data — names, dates of birth, insurance plan info, appointment schedules — out of your PMS automatically, so your team doesn't have to retype it. The second is that they can push data back — verification results, treatment notes, recall confirmations — into the PMS so your records stay current in one place.
Both sound great in a sales pitch. In practice, they break a lot. The reasons are technical but the symptoms are operational: a Dentrix update changes a field name and the sync stops working overnight. Eaglesoft installs on a local server and the integration needs middleware that adds cost per location. Open Dental has the friendliest API in the industry, but the practice still needs to configure tokens, endpoints, and security rules that most office managers have no business administering. We've talked to practices who paid for integrations that worked for a year and then broke after a software update, and they've been retyping ever since.
So the question we'd push back with — gently — is this: what is the integration actually supposed to accomplish? If the answer is "save my team from retyping the patient list," that's a real and solvable problem, but it's a one-time problem (we'll come back to this). If the answer is "give me real-time, accurate insurance information," then the PMS isn't actually the right source. Which brings us to the more uncomfortable truth.
Your PMS doesn't know what your patient's insurance covers today
This is the part that surprises people. Your PMS stores what was entered the last time someone called the insurance company. That could have been last week, last month, or a year ago. Between then and now, your patient's deductible has potentially been met (or not), their annual maximum has been partially used (or fully used), their plan year may have reset, their employer may have changed carriers, and their coverage breakdown by procedure category may have shifted. None of that updates in your PMS unless somebody picks up a phone and re-verifies — which is exactly the work InsureIQ exists to eliminate.
The eligibility answer lives at the payer. Delta Dental knows what your patient's deductible is right now. MetLife knows whether their annual max is exhausted. Aetna knows whether the missing tooth clause applies. Your PMS is downstream of that information. It's a record of what was true at some past moment, stored locally for your team's convenience.
So if InsureIQ "integrated with your PMS" in the conventional sense, all we'd be doing is helping you trust slightly-less-stale data faster. That's not what your front desk needs. What they need is the truth, right now, before the patient sits in the chair.
Where InsureIQ actually goes — Availity, the dental clearinghouse
InsureIQ doesn't go to your PMS for eligibility data. It goes directly to Availity, which is the standard dental clearinghouse used by virtually every dental payer in the United States. Think of Availity as the connective tissue between dental practices and insurance companies — when you call a payer to verify benefits, the back end of that conversation often travels through Availity infrastructure. We've cut out the phone call.
When you click verify in InsureIQ, here's what happens behind the scenes. We send Availity a structured eligibility request with the patient's information and the date of service. Availity routes that to the payer in real time. The payer responds with a raw eligibility data block — a long, structured document called a 271 response that's technically standard, practically unreadable, and historically what your office manager has been trying to translate into a usable patient summary for years.
That's where Claude comes in. Claude reads the raw 271 response and produces a structured, plain-English summary in seconds. Annual maximum and amount used. Deductible and amount met. Coverage breakdown by category (preventive, basic, major, orthodontic). Frequency limitations on cleanings and X-rays. Waiting periods. Missing tooth clause. Coordination of benefits. Plus an alert layer that surfaces anything unusual — "this patient has a $0 annual max remaining" or "this plan requires a missing tooth clause check before crown work."
And then it caches the result for four hours, so if the same patient is verified twice in the same morning, we don't ping Availity twice. The cached version is available as a clean PDF for the chart and a patient-facing email if you want to send one.
The actual workflow, end to end
Here's what running InsureIQ looks like from the office side, with no fluff. There are two ways to get patient data into the system, and you can use either or both depending on how your practice operates.
Path one: CSV upload at onboarding
During practice setup, your office can export a patient roster from your PMS — Open Dental, Dentrix, Eaglesoft, Curve, all of them support some form of CSV export — and upload it directly into DentalIQ. That gives InsureIQ the full patient list with insurance info from day one, so batch verification of tomorrow's schedule works immediately. This is the high-leverage option for practices that want everything available before they start using the platform daily.
Path two: Manual entry, progressive enrichment
If a full export isn't practical — and for many practices it isn't, because PMS exports can be messy or incomplete — InsureIQ supports adding patients on the fly. When a new patient appears on tomorrow's schedule, you add them to InsureIQ in about 30 seconds (name, date of birth, member ID, payer) and run the verification. After that first entry, the patient lives in DentalIQ and never needs to be re-entered. Over a few weeks of normal use, your active roster becomes complete without a big-bang import.
What happens after the data is in
From there, the workflow is the same regardless of how the patient got into the system. The morning of a patient's appointment — or the night before, if you run batch verification — InsureIQ pings Availity for each patient on the schedule, Claude interprets each response, and your front desk gets a clean dashboard view of who's covered, who has issues to flag, and what each patient is realistically responsible for. Verification PDFs are one click. Patient emails are one click. The treatment plan tool, AcceptIQ, reads from the same verification data to produce a patient-friendly cost breakdown when treatment is presented.
The whole loop runs without your PMS being involved at all. Which means it runs the same way for every PMS on the market.
Your PMS, our InsureIQ — how it works for each system
Because InsureIQ doesn't depend on PMS-specific integrations, the experience is the same across systems. The only real difference is how easy it is to get your patient list out of the PMS for the initial CSV import. Here's where each major system stands today.
Open Dental. The friendliest case. Open Dental has clean exports and the most open data structure of any major PMS. Tech-forward independent practices love it for exactly this reason. CSV import into InsureIQ is straightforward and most practices have their full roster in within an hour of onboarding.
Dentrix. Exports work, though Dentrix's local-server architecture means the office manager usually has to run the export from a specific workstation. Once exported, the CSV imports cleanly. Day-to-day operation is identical to Open Dental — InsureIQ doesn't care that Dentrix lives on-prem.
Eaglesoft. Similar to Dentrix — local install, export-from-workstation pattern. CSV import works fine. The verification workflow afterward is the same as everyone else.
Curve Dental. Cloud-native, so exports are quick and patient data is well-structured. Curve practices typically have the fastest onboarding into DentalIQ because the data is already cleanly organized.
Carestack. Cloud-based, exports supported, onboarding is comparable to Curve. Some Carestack practices choose to skip the CSV path entirely and let their roster build up through manual entry — the choice usually comes down to whether the office wants to front-load the work or spread it across a few weeks.
Other systems. Dolphin, Practice-Web, Denticon, Cloud9 — same pattern. If your PMS can export a list of patients with names, dates of birth, insurance plans, and member IDs to CSV, InsureIQ works. If your PMS can't, the manual-entry path always works, regardless of what you're running.
What's coming next: IntegrateIQ, starting with Open Dental
We'll be honest about the roadmap. The "one-time problem" of retyping the patient list is a real friction point, and we're solving it directly. IntegrateIQ is the module in development that will provide native, bidirectional PMS connections — starting with Open Dental, because its API is the cleanest in the industry and the practices that use it tend to be the earliest adopters of new technology. When IntegrateIQ ships, Open Dental practices will be able to skip the CSV step entirely. Patient demographics, insurance info, and tomorrow's schedule will pull automatically, and verification PDFs will push back into the patient record as a Document.
Dentrix, Eaglesoft, Curve, and Carestack adapters will follow. We're approaching them in order of API friendliness rather than market share, because the practices that benefit most from these tools are the ones whose owners are willing to be early on something new — and historically, that's Open Dental first, cloud-native systems second, legacy on-prem systems third.
What won't change when IntegrateIQ ships is the source of truth for eligibility data. Even when InsureIQ can pull patient demographics from your PMS automatically, the actual coverage answer will still come from Availity, because that's still where it lives. Direct PMS integration is a convenience layer; it isn't the verification engine. We're building the convenience layer because practices ask for it. We just don't want anyone to confuse it for the thing that's already working today.
The bigger principle
"Real-time" beats "integrated" when the data lives elsewhere. PMS integrations that promise to keep your patient records current with insurance information are promising to keep stale data slightly less stale, faster. That's not the same as showing your front desk what's true right now. InsureIQ goes to where the truth lives — the payer, through Availity — and uses Claude to put it in language a human can act on in under ten seconds.
The architectural decision behind this looks familiar if you've watched how the best B2B software has evolved in the last decade. Slack didn't replace your email server, your file storage, your project tracker, or your CRM. It sat alongside them and connected to whichever ones you happened to use, working the same way for everyone. Notion didn't replace your existing docs. Stripe didn't replace your bank. The pattern is consistent: don't fight the existing system of record, sit next to it, and bring something the existing system can't. InsureIQ brings real-time eligibility from the payer, interpreted in plain English. Your PMS keeps doing what your PMS does.
The bottom line for your practice
If you're tired of dental software that promised PMS integration and delivered three months of broken sync, InsureIQ is built differently on purpose. It doesn't depend on your PMS staying frozen in time. It doesn't break when Dentrix patches itself or Eaglesoft updates a field name. It works the same way the first day you turn it on and the day after your PMS vendor pushes a release you didn't ask for.
If you're specifically waiting for direct Open Dental integration — and we get that some practices have made that a hard requirement — that's coming through IntegrateIQ, and Open Dental is first in the queue. In the meantime, the CSV import takes about an hour, and most of the practices who tried InsureIQ thinking they'd need direct integration to be happy ended up finding the manual path was faster than the integration migrations they'd done with previous vendors.
Try it for yourself with the 14-day free trial — no credit card, no PMS configuration, no IT project. Run a few verifications against your real schedule and decide based on what you see, not what we wrote.
Run your free practice audit first: dentaliq.app/auditiq.