A note on sourcing before anything else. Everything factual below comes from vendor documentation, vendor product pages, or the Canadian Dental Association, and it describes the state of things as of July 2026. Software changes. Where something could not be verified from a primary source, it is not stated here, and you will find no pricing on this page because dental software pricing is almost universally quote-based and would be wrong within months. Dentx is a dental marketing agency. We are not affiliated with, and do not resell, any of the systems described here.
What a practice management system does
The practice management system is the system of record. One database holds the appointment book, the clinical chart, the patient ledger, insurance claims and estimates, recall and recare, and treatment plans. Everything else in the practice connects to it: imaging, patient messaging, online booking, payments, and any analytics or marketing tool you bolt on.
That is why the choice is heavier than it looks. The practice management system determines what you can measure, how easily you can move your data if you leave, and which third-party tools you can use at all. It is also where the results of everything else get proven, because production, collections, new patient counts and treatment acceptance are recorded there and nowhere else. If you have ever tried to work out whether your marketing is paying for itself, you were reading numbers that came out of this system. Our guide to the dental office KPIs worth tracking is effectively a guide to reading its reports well.
What "open" actually means
The phrase "moving from closed systems to open" gets used constantly in this category, and it hides three different things. Keeping them separate is the difference between a decision you can defend and a sales pitch you have absorbed.
- Deployment. Is the software installed on a server in your office, or do you reach it through a browser? This is the axis most people mean, and it is the least related to how open your data is. A cloud system with no published API is more closed, in the ways that matter, than a locally installed one with a documented database.
- Data access. Is there a published API a third party can build against? Can anyone query the underlying database directly? Is there any documented way to get a complete copy of your own data out? This is the axis that decides which tools you can use and how painful leaving will be.
- Source availability. Can anyone read the actual program code? In dental practice management this is essentially always no. Even Open Dental, whose name suggests otherwise, states that its source code is only sometimes made available to certain large customers under a signed non-disclosure agreement.
Read a vendor comparison with those three columns in mind and most of the marketing language sorts itself out quickly.
The main systems, one by one
Dentrix and Dentrix Ascend (Henry Schein One)
Henry Schein One sells these as two separate products. Dentrix is the long-established product installed in the practice. Dentrix Ascend is described by the company as cloud-native practice management software, and its product page makes the contrast explicit: you no longer need to be tied down to a computer or server in the office. Moving from one to the other is a data conversion, not a version upgrade.
On data access, Henry Schein One runs an API Exchange covering both Dentrix and Dentrix Ascend, which it describes as open to all and simple to join, and which it says exposes roughly 700 endpoints across about 100,000 practices, handling in the order of six billion data requests a year. There is a public developer portal. Integration vendors are authorized rather than simply self-serving, which is the permissioned pattern that runs through this whole category.
Eaglesoft and Fuse (Patterson)
Patterson runs the same split as Henry Schein One, and its own documentation shows it clearly. Patterson markets Fuse as, in its words, the intuitive, cloud-based practice management system for dental practices. Eaglesoft, meanwhile, has published hardware and network requirements built around a server in the office: the document lists Windows Server 2016, 2019, 2022 and 2025 Standard as supported operating systems and notes that a dedicated Eaglesoft server is recommended for six or more workstations. Two products, two architectures, and the same practical consequence. If you are on Eaglesoft and want browser access, you are looking at a different product and a data conversion.
Open Dental
Open Dental is the system most often held up as the open one, and the reputation is deserved on the data axis rather than the code axis. It runs on a MySQL or MariaDB database with published schema documentation, and it publishes a full REST API specification supporting the usual create, read, update and delete operations.
The details are worth knowing precisely. A developer applies to Open Dental for a developer key, which the company says takes one to three business days, and then each individual practice pastes a customer key into its own setup screen to authorize that vendor. Direct database reads are normal practice, which is why Open Dental has such a strong custom-reporting culture, but the company states that direct queries which change the database are strictly forbidden and are actively blocked by its database integrity feature. Writes go through the API. And, again, this is not open-source software: source access is NDA-gated and limited to certain large customers.
Curve Dental
Curve is cloud-native rather than a cloud version of an older desktop product. The vendor describes Curve Hero as running on a PC or a Mac through a Google Chrome browser with no need for servers or backup systems, hosted on Amazon Web Services. Curve also states it has converted data from over 90 other practice management products, which tells you something about who its buyers are: practices leaving a server behind.
On data access, Curve publishes a partner and integration list. As of July 2026 it does not publish a self-serve public developer portal in the way Open Dental and Henry Schein One do, so integrations generally run through its partner programme.
ClearDent
ClearDent is a Canadian system and the one most relevant to Canadian readers here. It is unusual in offering all three deployment models at once: ClearDent On-Premise, ClearDent Cloud, and ClearDent Link, a hybrid that connects an on-premise installation to the cloud. The vendor markets the cloud product as Canada's first true cloud-based dental software, which is its claim rather than an independently verified one.
For Canadian practices the concrete details matter more than the marketing: ClearDent Cloud runs on Microsoft Azure with continuous backups in three Canadian data centres and 256-bit AES encryption, which speaks directly to data residency, and ClearDent appears on the CDA's certified vendor list with support for CDAnet attachments. Its dashboards cover production, recalls, chair utilization and accounts receivable.
ABELDent
Another Canadian option running the two-product pattern: ABELDent Cloud, hosted on Microsoft Azure and described as SOC 2 Type 2 certified, and ABELDent Local Plus, the in-office version, which the vendor notes includes Microsoft SQL Server. It serves both Canadian and US practices and is on the CDA certified list with attachment support.
Denticon (Planet DDS)
Denticon is cloud-based and aimed squarely at multi-location groups and DSOs, sold as part of what Planet DDS calls its DentalOS platform alongside its imaging and orthodontic products. In July 2024 the company announced an Open API Program for DSOs and partners, which is a useful marker of where competitive pressure in this category now sits. Denticon does not appear on the CDA's CDAnet certified vendor list, which is the kind of detail a Canadian group needs to check early rather than late.
The rest of the Canadian field
The names above are not the whole market, particularly in Canada, and thin coverage of a system is worse than none. The CDA's own certified vendor list is the most reliable public inventory of software actually in use in Canadian offices, and it includes Tracker from Bridge Network, MaxiDent, ADSTRA, Paradigm, Akitu One, Consult-PRO, Oryx, Progident/Clinique, Dentitek, and Power Practice and axiUm from Exan, among others. If you are shopping in Canada, start from that list.
Not sure your practice data is telling you the truth about your marketing?
Book a free 15-min call and we'll show you where you stand vs. local competitors.
Book a Free 15-Min CallSide by side
The three axes again, applied. Read the deployment and data access columns as separate questions, not as one.
| System | Deployment | Published data access | On CDA certified list |
|---|---|---|---|
| Dentrix | Installed in the practice | API Exchange, public developer portal | Yes |
| Dentrix Ascend | Cloud-native, browser | API Exchange, public developer portal | Not listed |
| Eaglesoft | Windows server in the practice | No public developer portal published | Not listed |
| Fuse | Cloud-based, browser | No public developer portal published | Not listed |
| Open Dental | Installed locally | Public REST API spec, published MySQL schema, reads direct | Yes |
| Curve Hero | Cloud-native, browser | Partner and integration list | Yes |
| ClearDent | On-premise, cloud, or hybrid | No public developer portal published | Yes |
| ABELDent | Local Plus or Cloud | No public developer portal published | Yes |
| Denticon | Cloud, multi-location focus | Open API Program announced 2024 | Not listed |
"No public developer portal published" means exactly that and nothing more: no publicly documented developer programme was found for that product as of July 2026. It is not a statement that no integration is possible, and several of these vendors integrate widely through direct partnerships. Certification status is taken from the Canadian Dental Association's published certified vendor list, checked in July 2026. It is the authoritative source and it is public, so check it yourself before you decide anything on it.
What reports each system produces
Here is the part that surprises people who are shopping: at the level that matters, the reports are remarkably similar. Nearly every system produces the same financial and operational core, because the same set of numbers runs a dental practice.
- A day sheet or daily transaction summary, the record of what happened today.
- Production and collections by provider, usually with adjustments broken out separately.
- Aging of accounts receivable, normally in 30, 60 and 90 day buckets.
- New patient counts over a period.
- Recall or recare status, including patients due and patients not scheduled.
- Unscheduled or presented treatment, which is where treatment acceptance is read.
- Insurance claim aging and outstanding claims.
What differs is the packaged management reporting layered on top of that core, and how much work it takes to get an answer the software did not anticipate.
Dentrix publishes a Daily Huddle Report covering production, collections, case acceptance, new patients and scheduling, designed to be run in a morning meeting, along with a Practice Advisor Report. Both depend on a Practice Advisor setup where you define how the active patient base is calculated and which providers count as dentists or hygienists, which is a genuinely important detail: if two practices define the active patient base differently, their reports are not comparable. Henry Schein One also sells Jarvis Analytics as a separate analytics product.
Eaglesoft documents a Day Sheet, a Provider Productivity report, Production and Collections Reconciliation reports for tying the numbers together, and an Accounts Receivable by Responsible Party report.
Open Dental splits reporting into Standard Reports, which include Production and Income, Aging of Accounts Receivable, a Receivables Breakdown, Treatment Plan Presentation Statistics and Procedures Not Billed to Insurance, and Graphic Reports for visual output by provider or clinic. Because the database schema is published and direct reads are permitted, it also has a strong custom query culture, which is its real reporting advantage over most of the field.
Curve names its key indicators explicitly: accounts receivable, collections, production, new patients, recare, and treatment plan value.
ClearDent presents real-time dashboards covering production, recalls, chair utilization and accounts receivable, with comparison reporting across multiple locations.
The practical lesson is that you should not choose a system on its report list, because the core list is the same everywhere. Choose on two things instead: whether the reports let you define terms the way your practice actually works, and whether you can get at the underlying data when the packaged report does not answer the question. The second one is where the open data axis earns its keep. If you want the numbers worth pulling once you have them, start with dental office KPIs and the collection rate and case acceptance benchmarks.
The Canadian layer: CDAnet and ITRANS
Canadian practices carry a requirement most US comparisons never mention. Electronic dental benefit claims run through CDAnet and the CDA ITRANS claims service, and the Canadian Dental Association states that the service is accessed through CDA-certified practice management software in the office. There is no additional fee for eligible member dentists, but the software has to be on the list.
That makes the CDA's certified vendor list the single most useful document in a Canadian software search, and it is publicly available. It also distinguishes between products that are CDAnet certified and products that additionally support CDAnet attachments, which matters if you send radiographs with claims. One timing note worth knowing: CDAnet Version 2 was retired in February 2024, and all claims processors now support Version 4 transactions.
Vendors handle the Canadian layer with varying depth. Open Dental, as one documented example, lists itself as ACDQ Express, CCDWS through Telus and Instream, CDAnet, CDHAnet and DACnet certified or approved, integrates ITRANS 2.0 for dentists and Claimstream for independent hygienists and denturists, and supports CDA codes and regional fee guide imports, while noting that the RAMQ clearinghouse in Quebec is not available within the software. That last caveat is a good illustration of why a Quebec practice and an Alberta practice can reach different conclusions about the same software.
CDAnet is also the most interesting thing in this whole article from an openness standpoint, because it is genuine, vendor-neutral, standardized interoperability, and it has existed in Canadian dentistry for decades. The industry already knows how to agree on a standard when there is a shared reason to.
Where the category is heading
You do not need a market forecast to see the direction. It is visible in what the vendors themselves now sell.
Every major desktop vendor now sells a cloud product beside its legacy one. Henry Schein One has Dentrix and Dentrix Ascend. Patterson has Eaglesoft and Fuse. ClearDent offers on-premise, cloud, and a hybrid link between them. ABELDent has Local Plus and Cloud. These are not upgrades of the old products, they are separate products, which tells you the vendors expect the transition to take years and to be a migration rather than a patch.
Openness has become a marketing claim, which is itself the signal. Henry Schein One describes its API Exchange as open to all and publishes endpoint counts. Planet DDS launched something it explicitly named an Open API Program in July 2024. Open Dental publishes its full API specification and database schema in the open. Ten years ago the competitive claim was the feature list. Now a meaningful part of it is what you are allowed to connect.
But open still means permissioned, and honesty about that matters. Open Dental approves developer keys individually and blocks direct database writes outright. Henry Schein One authorizes integration vendors. Curve routes integrations through partnerships. No major dental practice management system gives arbitrary third parties unrestricted access to a practice's clinical database, and given that this is patient health information, none of them should. The realistic reading of the trend is a move from closed to documented and governed, not from closed to unrestricted.
Group practice is the force underneath all of it. The clearest, most explicit API commitments in the field are aimed at DSOs and multi-location groups, which is exactly what you would expect: a single-location practice can tolerate a system that does not talk to anything, and a forty-location group cannot. As groups take more of the market, the pressure toward interoperability comes with them. Our DSO marketing guide covers the wider shift.
What this means for your practice
If you are choosing or reconsidering a system, the questions that actually separate the options are narrower than the feature grids suggest.
- What happens to your data if you leave? Ask for the specific export path before you sign, not after. This is the question with the longest tail and the one most often skipped.
- Which of your existing tools are supported? Imaging, messaging, payments and booking are the usual casualties of a switch, and finding out afterward is expensive.
- In Canada, is it on the CDA certified vendor list? Check the list yourself. It is public.
- Can you answer a question the packaged reports do not anticipate? If the answer is no, you are limited to the questions the vendor thought of.
- How complete is the data conversion? Conversions routinely carry over the ledger and the schedule while losing detail elsewhere. Get the specifics in writing.
One last point, and it is the reason a marketing agency wrote this. Whatever system you run, it is where your marketing gets judged. New patient counts, production, treatment acceptance and recall all live there, and a practice that cannot read its own numbers cannot tell a working campaign from a wasted one. You do not need to change software to fix that. You need to know which reports answer which question, and to be honest about what the numbers say.
To be clear about our own position: Dentx does not resell, install, support or integrate with any practice management system, and we do not need access to yours. What we do is make sure the practice is found, trusted and chosen in the first place. If you want a concrete read on where your practice stands online today, our paid $297 Website Diagnostic reviews your website, your local visibility, and one leading local competitor.
Frequently Asked Questions
What is dental practice management software?
It is the system of record for the practice. One database holds the schedule, the patient chart, the ledger, insurance claims, recall and treatment plans, and the reports built on top of them. Imaging, patient messaging, payments and marketing tools then connect to it. Because production, collections, new patients and treatment acceptance are all recorded there, the practice management system is also where the performance of everything else in the practice is measured.
What is the difference between Dentrix and Dentrix Ascend?
They are two separate products from the same company, Henry Schein One. Dentrix is the long-established product installed in the office. Dentrix Ascend is described by Henry Schein One as cloud-native practice management software, where the company says you no longer need to be tied down to a computer or server in the office. Moving between them is a data conversion, not an upgrade, so the choice matters. Patterson runs the same pattern with Eaglesoft, whose published hardware requirements are built around a Windows server in the office, and Fuse, which Patterson markets as its cloud-based practice management system.
Is Open Dental actually open source?
No, and this is the single most common misunderstanding in the category. Open Dental states on its own site that the source code is sometimes made available to certain large customers under a signed non-disclosure agreement. What is genuinely open is the data layer: it runs on a MySQL or MariaDB database with published schema documentation, and it publishes a full REST API specification. That combination is why it has a reputation for openness, but source-available under NDA is not the same claim as open source.
Which dental software has an open API?
Several publish one, with different front doors. Open Dental publishes a public REST API specification and issues developer keys on application, with each practice pasting a key in to authorize a vendor. Henry Schein One runs an API Exchange covering Dentrix and Dentrix Ascend that the company describes as open to all and simple to join, and states it exposes around 700 endpoints. Planet DDS announced an Open API Program in July 2024 covering its platform, which includes Denticon. Curve Dental publishes a partner and integration list rather than a self-serve public developer portal. In every case access is documented and permissioned, not unrestricted.
What reports do dental practice management systems generate?
Almost all of them produce the same financial and operational core: a day sheet or daily transaction summary, production and collections by provider, an aging of accounts receivable, adjustments, new patient counts, recall or recare status, unscheduled treatment, and insurance claim aging. Where they differ is in the packaged management reports layered on top. Dentrix, for example, publishes a Daily Huddle Report covering production, collections, case acceptance, new patients and scheduling, plus a Practice Advisor Report. Eaglesoft documents a Day Sheet, Provider Productivity, and Production and Collections Reconciliation reports. Curve names accounts receivable, collections, production, new patients, recare and treatment plan value as its key indicators.
Do I need CDAnet certified software in Canada?
If you want to submit dental benefit claims electronically through CDAnet or the CDA ITRANS claims service, yes. The Canadian Dental Association states that the service is accessed through CDA-certified practice management software in the dental office, and it publishes the certified vendor list. That list is the fact to check before switching systems in Canada, because not every widely used system appears on it. CDAnet Version 2 was retired in February 2024 and all claims processors now support Version 4.
Should a practice move from a server to the cloud?
It depends on what the move is meant to solve, not on the label. Cloud systems remove the in-office server, the backup routine and the version upgrades, and they make multi-location and remote access straightforward, which is why growing groups favour them. A locally installed system keeps the data and the hardware under the practice's direct control and does not depend on the office internet connection. The harder questions are usually the ones underneath: how complete the data conversion will be, whether your imaging and third-party tools are supported on the new system, and how you get your own data out later.
