Dental practice management
Claude + Open Dental
Your patients, appointments, procedure logs already live in Open Dental. Connected to Claude, your team can ask questions of that data, draft from it and act on it, without copying anything between tabs. Here’s what that looks like for dental and healthcare businesses, and how we set it up.
What Claude does with your Open Dental data
Real workflows we build on top of the connection. Each one becomes a skill your team runs in one step.
Broken-appointment recovery
Find appointments broken this week and draft rescheduling messages, logging each outreach as a commlog.
Treatment-plan follow-ups
Summarize planned-but-unscheduled procedures and draft patient explanations.
Daily huddle brief
Summarize the day's appointments with balances and procedures due.
Aging report summary
Summarize the aging report and draft statements/reminders for the largest balances.
Appointment confirmations
Draft confirmation messages for tomorrow's appointments and mark confirmed appointments after replies.
How the connection works
Open Dental REST API using a developer key (from the Developer Portal, requested via vendor.relations@opendental.com) plus a per-office customer key; remote calls route through Open Dental HQ and require the office's eConnector to be running.
There isn’t an official Open Dental connector for Claude that we could verify, so we build a small, scoped MCP server on the Open Dental API and add it to your Claude workspace. Your team then uses Open Dental data inside Claude like any other tool.
Requires developer approval from Open Dental, a running eConnector at the office, and a HIPAA BAA for any PHI sent to Claude.
Open Dental developer docsData Claude can use
Getting Claude and Open Dental working together
Claude Deployment Sprint
fixed price, starting at $10,000 · 2 weeks
- Claude connected to Open Dental with the right permissions
- The workflows above built as skills on your real data
- Your other core tools connected too (email, accounting, CRM)
- Team trained by role, plus 30 days of tuning
Custom AI Agent
starting at $25,000 · 4–8 weeks
Want one of these workflows to run on its own? We build an agent that watches Open Dental, does the work, and hands it to a person to approve, with every step logged.
Scope an agentClaude skills for teams that run on Open Dental
Questions
Does Open Dental have an official Claude connector?+
We didn’t find an official Open Dental connector for Claude from Open Dental Software or Anthropic. We connect the two through the Open Dental API (limited api), usually as a small MCP server your Claude workspace can use.
What Open Dental data can Claude work with?+
Through the API, Claude can work with patients, appointments, procedure logs, claims (status), payments, commlogs and more. We scope access to read-only wherever possible, and keep a person approving anything that changes records or reaches a customer.
Do we need a developer on staff?+
No. In a Claude Deployment Sprint we set up the connection, build the skills and train your team. You’ll need an admin login for Open Dental and, if required, to approve API access with Open Dental Software.
Will our Open Dental data be used to train AI models?+
We set teams up on Claude business plans. Anthropic does not use inputs or outputs from its commercial products to train models by default.
Open Dental is a trademark of Open Dental Software. Krasa.ai is an independent implementation firm and is not affiliated with or endorsed by Open Dental Software or Anthropic.