Claude + DrChrono: What the Integration Can (and Can't) Do in 2026
No official Claude DrChrono connector — but this is the most connectable of the practice-management tools. DrChrono (the cloud EHR and practice-management platform, now part of EverHealth) isn’t in Anthropic’s connectors directory, and DrChrono hasn’t built its own connector. What makes it different from Jane or SimplePractice: DrChrono has a self-serve API you switch on from inside your own account, so a community-built connector has something real to talk to — and a couple exist, including one routed through Pipedream (a hosted middleware service). The blocker here isn’t the API. It’s the HIPAA wall on patient data, and the fact that anything connected to Claude only runs inside a conversation you start.
Here’s what’s actually available, the limits, and what to use if you want DrChrono work that runs on its own.
The API is self-serve — you enable it in your own account
Unlike the partner-gated tools in this vertical, DrChrono lets a practice create API credentials directly:
- Create an app from your account. Sign in and go to Account → API, select “New Application,” give it a name, and you get your own API credentials. No partner review to get started.
- A documented API. The DrChrono API covers patients, appointments, clinical records, and billing, with permissions you can scope to just what a connection needs.
- Event notifications exist. DrChrono documents a Lab API and webhooks, so events can in principle fire outbound — useful grounding for trigger workflows (on a platform that can act on them).
That self-serve API is exactly why community-built connectors exist for DrChrono when they don’t for the closed tools — there’s a real door.
What exists on the Claude side today
No first-party path exists, but the unofficial options are more real than for most vertical tools:
- A community-built connector — listed in community directories, one version runs through Pipedream (a hosted middleware service) against DrChrono. That Pipedream path is the shortcut the closed tools don’t have.
- Your own build — create an API app in your DrChrono account and have someone technical build a small connector against it.
Either adds DrChrono as a custom connector to Claude (an MCP server — the standard way outside apps plug in). The remote kind on claude.ai requires a paid Claude plan; the local kind runs through the Claude desktop app or Claude Code. Because the Pipedream path exists, you can also set one up through that middleware without building from scratch.
Separate the vendor’s own AI: DrChrono ships in-product clinical AI (ambient scribing, admin assists). That’s a DrChrono feature — not a Claude connector, and it doesn’t connect to your Claude account.
The HIPAA wall — the actual blocker
DrChrono’s API is open enough to connect; the real caution is what flows through it. Consumer Claude plans are not HIPAA-compliant and Anthropic does not sign a BAA for them, and a community-built connector (or a Pipedream-hosted one) doesn’t come with a BAA either. DrChrono holds full PHI — charts, prescriptions, demographics — and routing that through a general Claude chat via an unofficial connector means PHI is moving through systems with no business-associate agreement covering it.
So the fact that you can wire DrChrono to Claude in an afternoon doesn’t make it compliant to push live patient data through it. Keep anything you paste de-identified, and treat any connector as unofficial and un-covered.
The limits that actually matter
Even with the API connected, the shape is “an assistant you operate,” not “an agent that runs”:
- No triggers, no monitoring. DrChrono can send event notifications on lab results, but Claude only runs inside a conversation you start — there’s nothing to catch that notification and act. No “when a lab result posts, message the patient.”
- Conversation-only. Claude pulls an appointment or a record when you ask; it doesn’t sit on your practice watching the schedule and following up. Close the chat and nothing continues.
- Laptop-bound for anything scheduled. The closest thing to autonomy is Claude’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on practice agent.
So Claude is good for “summarize this week’s appointment volume” and not built for “remind every patient with an upcoming visit automatically.”
If you want DrChrono work that runs on its own: Carly
The moment you want something to happen around DrChrono without you in the chat — email a patient after a visit, send an appointment reminder, follow up on a no-show, prep the front desk’s morning schedule — you’ve crossed past what Claude is for. And given the HIPAA wall, the durable pattern is to anchor that work to the non-clinical seams: appointment times on a connected calendar and the inbox.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- When a visit wraps, Carly emails the patient an after-visit follow-up and a next-appointment prompt — 24/7, in the cloud, whether or not your laptop is awake.
- When a recall or recare is due, Carly emails the patient to book and adds the task to your list.
- When a patient no-shows, Carly nudges them to rebook and preps the front desk’s morning schedule.
- Never touches PHI it shouldn’t. A custom Claude build dead-ends at the HIPAA wall — no Anthropic BAA covers clinical data in an EHR, even with DrChrono’s open API. Carly sidesteps it by working the calendar and inbox seams around the record — reminders, recare, rebooking — so it runs the day-to-day follow-up without ever reading the chart.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, and records meetings.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations.
Claude vs Carly
| Claude (community setup) | Carly | |
|---|---|---|
| Look up appointments / records | Yes (self-serve API) | Via calendar/inbox seams |
| Summarize non-clinical info | Yes (de-identified) | Yes |
| Acts on DrChrono events | No | Yes (calendar/inbox-side) |
| Sends appointment reminders on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No — drafts only (Gmail + Outlook) | Yes |
| What it takes to set up | Switch on the API + build/community connector | Connect your calendar & inbox |
| HIPAA BAA for clinical PHI | No | Keep messages de-identified |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with a community connector is a DrChrono lookup inside a chat, with a HIPAA caveat on real data. Carly is a teammate that runs the reminders and follow-ups around visits — on the calendar and inbox seams.
Frequently Asked Questions
Does Claude work with DrChrono?
Not officially — there’s no Claude DrChrono connector and DrChrono hasn’t built one. But DrChrono has a self-serve API you switch on in your own account, and community-built connectors exist (including one via Pipedream). Live patient data through consumer Claude isn’t HIPAA-compliant, and any connection only runs inside a conversation you start.
How do I get DrChrono API access?
Create an application yourself: sign in and go to Account → API → New Application, and you get your own API credentials. It’s self-serve — no partner review to begin. (Marketplace distribution is a separate program.)
Is it HIPAA-compliant to connect DrChrono to Claude?
No. Consumer Claude plans aren’t HIPAA-compliant and Anthropic doesn’t sign a BAA, and neither a community-built connector nor a Pipedream-hosted one adds one. Real PHI shouldn’t flow through a general Claude chat. Keep anything you paste de-identified.
What if I want DrChrono to act on its own — reminders, no-show follow-ups?
That’s outside what Claude does; it responds inside a chat and doesn’t act on events. Carly fires on schedules and calendar/inbox events 24/7 in the cloud — sending reminders, prepping schedules, and handling follow-up email. AI agents start at $35/month.
More: Claude connectors · Claude + athenahealth · Claude + SimplePractice · Can Claude send emails · Claude vs Carly · Best AI personal assistants
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
