AI for dental practices, strictly assistive, never clinical.

No. The systems we build for dental practices are strictly assistive. They handle intake, scheduling, insurance verification, recall reminders, and operational chat. They do not interpret radiographs, suggest treatment plans, or support diagnostic conclusions. Any software that contributes to a clinical decision is regulated as a medical device under EU MDR, and we do not build to that surface. The qualified dentist keeps the pen, every time.

Patient records are processed on EU infrastructure under EU jurisdiction, encrypted at rest and in transit, with signed DPAs that include zero-retention and no-training clauses for inference traffic. We produce a written DPIA before any system goes live, covering lawful basis under Article 9(2), retention periods, data subject rights, and a documented breach response. Patients can exercise rights of access and erasure against the AI deployment, and the audit log proves it.

Yes. We ship integrations with the major dental PMS platforms: Dentrix, Open Dental, Eaglesoft, Software of Excellence, Carestream, and the EU-specific systems used in Lithuania, Germany, and France. For systems without modern APIs, we build a queue-based bridge with idempotent writes and a manual reconciliation interface. The audit log writes regardless of where the data lands.

Eligibility verification stays a deterministic API call against the payer's real-time benefits feed; AI does not invent coverage. What the AI does is structure the inbound patient brief into the fields each payer expects, surface mismatches, and flag prior authorisations the front desk would otherwise miss. Every eligibility decision cites the payer response that produced it.

Multi-location groups are the strongest fit. We deploy with location-aware routing, per-clinic calendar and operator pools, and a central audit and reporting layer. Each location keeps its own brand voice and protocols while the back-office benefits from shared verification, recall, and intake infrastructure.

Yes. Under EU AI Act §50 transparency rules, any AI-assisted patient communication discloses the nature of the system at the start of the interaction. The disclosure language is reviewed by your DPO and clinical leadership before launch. Patients can request a human at any point and the handoff is built into the flow.

First engagements target one workflow with a measurable baseline, run 4 to 10 weeks to production, and land as a single signed-off system inside one PMS surface. Common scopes are: intake automation across new patient flows; insurance verification across one or two payer mixes; recall reminders across one or two recall categories. Submit a project with the workflow you have in mind.

Pricing is set after the discovery sprint, against your specific workflow, location count, and PMS surface. We do not publish a flat rate because the scope variation across dental groups is wide. Submit a project with the workflow and rough patient volume, and we come back with a discovery proposal within one business day.