Prerequisites
- Your location count now and in three years, and whether growth is acquisition or de novo
- Your actual and planned entity count. Many groups use one professional entity per state, but the architecture is state-specific.
- Whether you’ll want programmatic access to your data
- A shortlist from the PMS directory
The two divides in the dental PMS market
Server legacy vs cloud. The installed base of American dentistry runs on on-premise, Windows-server systems: Dentrix (Henry Schein One), Eaglesoft (Patterson), and Open Dental. Everything built since roughly 2018 is cloud multi-tenant: Denticon (Planet DDS), Dentrix Ascend, Curve, Fuse (Patterson), tab32, and newer entrants.1 A server system means a Windows server in every office, a 5–7 year hardware refresh, and VPN topology to see across sites; the cloud argument for a group is one patient database, one scheduling and reporting plane, and no per-site infrastructure.1 Single-office versus multi-site design. This is separate from cloud versus on-premises architecture. Dentrix and Eaglesoft were designed around one office, while Denticon was built for groups. Planet DDS positions Denticon as its enterprise DSO platform and reports 14,500 practices, with its products used by more than half of the 60 largest North American DSOs. Those figures come from the vendor.2 Open Dental uses an on-premises architecture but is also used by DSOs, in part because its MySQL database is accessible, it offers an API, and its per-office cost is comparatively low.3 If you are building a group, weight the second divide more heavily than the first. A great single-office system multiplied by ten offices is ten databases, ten configurations, and no consolidated recall report.The criteria, in priority order
1. Multi-location architecture
Can the system run all offices in one installation with central patient records, cross-location scheduling, and consolidated reporting, or does each office require its own instance? Test the answer against your growth plan. For example, ask the vendor to show the hygiene reappointment rate across three locations in one report.2. Imaging integration
Imaging supports both clinical care and the attachment workflow used in billing. Products take different approaches: Eaglesoft ships with integrated imaging; Dentrix Ascend and Curve include cloud imaging; Denticon pairs with Planet DDS-owned Apteryx XVWeb; and Open Dental relies on third-party imaging bridges.1 Confirm that your sensors and CBCT work with the candidate system. Also test whether images can be exported to your clearinghouse’s attachment service without rescanning.3. Clearinghouse and attachment flexibility
Before signing, ask whether the system permits your choice of clearinghouse and whether you can change later. Put the answer in the contract because some systems embed a clearinghouse and make switching difficult. Ask how attachments flow, whether the PMS integrates with NEA FastAttach or an equivalent service, and how the vendor plans to support X12 275 for the 2028 attachments mandate. See Choose a clearinghouse.4. Data export rights
Read the data-access clause closely. You will need data for analytics, financing or sale diligence, and acquisition conversions. Ask what you can export, in which formats, on what timeline, and at what cost. Put those terms in the contract. A cautionary tale on assuming access: Open Dental changed its license from GPL to proprietary at version 24.4. Pricing didn’t change, but a DSO that built tooling against the open source no longer has the license terms it built on.3 Whatever system you choose, your rights to your data should rest on your contract, not on the vendor’s current posture.5. ERA auto-posting quality
This determines how many hours a week your biller spends posting manually. Test it with a messy dental 835: a downgraded posterior composite, a frequency-limit disallowance, and a PLB takeback. Every system posts the clean lines; the difference is whether the downgrade lands as patient responsibility or silently becomes a write-off. See Bill dental claims for why that distinction carries money.6. Eligibility and benefits
Look for integrated, real-time 270/271 checks at scheduling that cover your payer mix. Ideally, the response should show the remaining annual maximum, rather than only an “active” status. No PMS captures the full plan design automatically; see Verify eligibility and benefits for the information that still requires staff review.7. Reporting
Ask the vendor to produce, without a spreadsheet export, the hygiene reappointment rate, recall effectiveness, unscheduled treatment plans, production versus collections by provider and payer, PPO write-off percentage by plan, days in AR, and AR aging. These measures support routine management and acquisition or sale diligence.8. Multi-entity support
Specific to DSO-PC groups and routinely overlooked:- Can it run multiple legal entities with separate Tax IDs and separate group NPIs?
- Can claims for each PC carry that entity’s billing provider information correctly?
- Can payments settle to different bank accounts per entity?
- Can you report per entity and consolidated?
9. Pricing model
Per location or per provider per month is predictable. Be cautious of percentage-of-collections pricing from a software vendor: it scales your cost with your success for a product whose cost to serve doesn’t.Migration is a conversion, not an upgrade
Two facts matter when considering a switch. First, moving from Dentrix to Dentrix Ascend is a full data conversion because Ascend is a separately built cloud product, even though both products are in the Henry Schein family.4 Second, an acquisition strategy means converting each acquired practice from its existing PMS. Evaluate the vendor’s conversion tools, timeline, and track record with Dentrix, Eaglesoft, and Open Dental before selecting the system. See Acquire a dental practice.Steps
1
Write your requirements before you take demos
Ten to fifteen must-haves, ranked, with multi-location architecture and imaging near the top. Demos are designed to reframe your requirements around the product’s strengths.
2
Shortlist three systems that match your scale trajectory
A single office planning to stay single shops a different list than a group planning ten locations.
3
Demo with your own scenarios
A crown with an attachment. A downgraded composite on the 835. Your multi-entity structure. A consolidated recall report.
4
Ask the contract questions in writing
Clearinghouse flexibility, data export, imaging compatibility, 275 roadmap, price escalation, term, termination.
5
Talk to reference customers at your scale
For a group: a customer who has converted an acquired practice onto the system. Ask what broke and how long the conversion really took.
6
Negotiate
Term length, escalation caps, implementation and conversion fees, and data export terms are all negotiable.
Verify it worked
- Requirements written before demos
- Multi-location architecture tested against the growth plan
- Imaging hardware compatibility confirmed
- Clearinghouse flexibility confirmed in the contract
- Data export rights specified in the contract
- ERA posting tested with a downgrade and a PLB
- Multi-entity support tested with your actual structure
- Conversion track record checked with references
- Term and escalation negotiated
Common failure modes
Sources
- Henry Schein One, Dentrix or Dentrix Ascend; Patterson Dental, Eaglesoft and Fuse; Curve Dental, multi-location groups. Vendor lineup
- Planet DDS, Denticon; Planet DDS release, enterprise DSO position. Market claims are vendor-reported.
- Open Dental, license (proprietary as of v24.4; GPL before) and MySQL documentation.
- Henry Schein One, Dentrix or Dentrix Ascend. The products have separate codebases, so migration requires a conversion.