Skip to content

Pre-launch · Controlled practice pilots and additional PMS integrations in preparation

Chairside AI

For practice management system product, integration, and engineering teams

Built to work with the PMS, not around it.

Chairside depends on the practice management system and does not seek to displace it. We pursue authorized access, request only the scope a validated use case requires, preserve source-of-truth boundaries, and make integration health visible.

Start an integration review

Reviewer summary

Stage
Pre-launch, active development
Category
Human-guided dental AI for reviewable operational workflows
PMS role
Authoritative for core patient, scheduling, clinical, and financial records
Integrations
First PMS connection live in controlled validation
Clinical boundary
Does not diagnose; does not replace provider judgment
Trust posture
Human review is the starting point for sensitive workflows
Compliance
HIPAA-aligned; BAAs before covered PHI; SOC 2 Type II readiness underway
The same three layers at narrow width: office systems above, Chairside as a thin layer, the practice management system as the unchanged foundation YOUR OFFICECALLSVISITSCOVERAGECLAIMSRECALLCHAIRSIDE AIcontext · review · audit trailauthorizedwritescopedreadYOUR PMSSYSTEM OF RECORD — UNCHANGEDIllustrative — not the product interface.
Office systems in a band above, Chairside AI as a thin layer between, the practice management system as a thick unchanged foundation YOUR OFFICECALLSVISITSCOVERAGECLAIMSRECALLCHAIRSIDE AIcontext · review · audit trailauthorized writescoped readYOUR PMSSYSTEM OF RECORD — UNCHANGEDIllustrative — not the product interface.

Where PHI is concerned, we expect to be checked.

Chairside handles operational and clinically adjacent data for dental practices, and we assume any platform we connect to will want that examined. We encrypt in transit and at rest, scope access to what a validated use case requires — access to one endpoint is not permission to use every field — and keep a tamper-resistant record of what was generated, what a person changed, and who approved it. We sign business associate agreements before covered PHI is processed. SOC 2 Type II readiness is underway.

Send us your security questionnaire, your data-handling requirements, or your integration checklist. We would rather answer your questions than guess at them.

Our full security posture is on the Trust and security page.

Start an integration review

The PMS keeps the record. Chairside keeps workflow context.

Core records remain authoritative in the PMS. Chairside maintains only the additional workflow state, review history, and audit context required to support the contracted use case. When data cannot be written, Chairside is designed to queue the action, show the status, and resolve conflicts visibly. It does not silently discard work, and it does not display a successful state that never reached the PMS.

We list support only after it is real.

Our first PMS integration is live in controlled validation. Additional platforms are being pursued through their authorized programs. Chairside will not describe a platform as supported until access, data behavior, testing, monitoring, support ownership, and an onboarding path are ready.

Detailed platform status, requested scopes, and vendor-specific technical materials are provided privately during review.

What we provide during a review.

Subject to the appropriate confidentiality agreement, Chairside provides:

  • company and leadership information
  • detailed use-case description
  • data-flow and source-of-truth map
  • requested objects, endpoints, and scopes
  • read-versus-write behavior
  • customer authorization model
  • audit and approval behavior
  • security and BAA posture
  • subprocessor inventory
  • error, queue, and recovery design
  • test, support, and escalation plan
Request integration materials

Integration availability depends on vendor authorization, technical validation, and product readiness.