Choosing a dental practice management system is a 5–10 year decision. Migration cost is high; muscle memory is sticky; and the workflows the software shapes — scheduling, billing, charting, recall — are the clinic's actual operating model. The decision is worth one focused afternoon of evaluation work upfront.
This article is a vendor-neutral checklist for APAC dental clinic owners and office managers evaluating PMS in 2026. Twelve questions, ordered roughly by how often they get under-asked. Use them on every vendor shortlist call — the same ones, the same order — so the comparison is genuinely apples-to-apples.
Hosting and data residency
1. Where, exactly, is patient data stored?
“Cloud” is not an answer. The answer should name a region: asia-southeast1, ap-southeast-1, or equivalent. For Singapore patient records, that should be a Singapore-region availability zone with no cross-border replication unless explicit consent is captured per patient.
Why it matters: PDPA expects patient records to be continuously protected, including during cross-border transfer. A vendor whose primary region is US or EU and whose Singapore presence is “coming soon” is a future problem.
2. What does tenant isolation look like at the database layer?
The right answer is concrete. Postgres row-level security per clinic. Schema-per-tenant. Database-per-tenant. Vague answers like “we isolate at the application layer” mean a single SQL injection or an over-permissive query can leak across clinics.
Ask to see the actual implementation. A vendor confident in their isolation will walk you through the pattern. A vendor that reaches for a security marketing page is hiding something.
Workflow fit
3. Is the schedule something the front desk drives, or consults?
Watch a reschedule on a demo. If it's “open the appointment, change the time, save the form, close the dialog” — that's 10–15 seconds per change, and the front desk does this 50+ times a day. Drag-and-drop reschedule is the modern bar; insist the demo shows a 10:00 → 14:00 move in three seconds, with the timezone-correct commit holding on a page reload.
4. Does billing pull from the chart, or do treatment lines need re-entry?
Same-day-bill rate is the number that distinguishes good clinics from average ones. The mechanism is the chart-to-bill auto-population: when the dentist marks a procedure complete, that procedure code and fee should appear in the patient's ledger automatically, not be re-keyed by the front desk. Re-entry kills same-day-bill rate; auto-population enables it.
5. Does the chart open to the patient's last visit, or a blank state?
A clinical convenience question with a usability story behind it. The “last visit” default saves 5–10 seconds per chart open and signals whether the PMS was designed by people who've actually sat next to a clinician.
Multi-clinic and operator scale
6. If we add a second location, what changes?
For multi-clinic operators, this is the highest-stakes question. The wrong answer is “you install a second instance and reconcile reports.” The right answer is “you create a second clinic in the same tenant, and reports consolidate automatically.”
Ask specifically: chair utilisation across both clinics in one dashboard? Recall coverage across both clinics in one digest? Front desk staff who rotate across locations on a single login? Each of these is a workflow that breaks down quickly under multi-database consolidation models.
7. How are upgrades coordinated across clinics?
Continuous deployment (every clinic on the same version every week) is the modern bar. Anything else introduces version drift between clinics, and version drift is the silent killer of multi-clinic operations: reports stop reconciling, staff who rotate clinics learn slightly different products, support cases get harder to triage.
Integrations
8. Which sensor brands does the imaging integration cover, and how?
Carestream, Dexis, Sopro, Schick are the four most common in APAC clinics. A PMS that integrates equally well with all four is rare; a PMS that integrates well with one and poorly with three is common. If you have existing sensors, the integration quality with your sensors is the only one that matters — but a sensor-vendor-neutral PMS gives you the option to switch sensors later without redoing the imaging integration.
9. What patient communication channels are supported, and where do they route?
WhatsApp Business API matters in APAC the way SMS matters in the US — it's the default channel for patient communication. Ask specifically about Singapore-region routing (vs US-region routing for WhatsApp messages, which is a real PDPA exposure). Ask about templated message support (required by WhatsApp's Business API for outbound recall) and about audit logging on conversations.
Compliance and audit
10. Show me an actual audit log query.
Most PMS claim to have audit logs; few have ones that survive a real query. Ask the vendor to demo: “Show me everyone who accessed patient X's chart in the last month.” If the answer requires engineering involvement or a CSV export to Excel, the audit log is not operationally usable.
For more on what regulators and auditors actually look at, see the dental audit logs article.
Pricing fine print
11. What is the fully-loaded cost over 12 months?
Headline price plus: per-seat charges, per-feature gating, mandatory support tier, training fees, implementation fees, integration fees (often per-sensor or per-channel), data-export fees on departure, contract minimum-term penalties. Get every line item before signing. A flat-priced PMS at $200/clinic/month is rarely the most expensive option once you total the line items at a tiered competitor.
12. What happens if I leave?
The two specific questions to ask: (a) what data export formats are available, and how quickly, and (b) what is the field-mapping document for porting to a successor PMS. If the answer is “we provide a CSV” without specifics on schema or timing, that export will be painful when you actually need it. The vendor that commits to a documented field-mapping is the vendor that's thought through the “what if” honestly.
What to do with this list
Send the same 12 questions, in the same order, to every vendor on the shortlist. Ask for written answers. Compare the answers side-by-side. The vendors that answer concretely (named regions, specific Postgres patterns, demo-able audit log queries) are the ones who've actually built the thing they're selling. The ones that answer with marketing prose are selling something else.
If you're evaluating Oralstack as one of the shortlist, the comparison hub gives you our line-by-line answers against Plato, Open Dental, Dentrix, Eaglesoft, and Carestream. The security posture page documents the hosting and tenant-isolation answers in detail. And a 30-minute demo with one of our engineers will walk you through the actual workflows on a sample dataset matched to your clinic's shape.