DrChrono API
DrChrono runs a public developer program: an OAuth 2.0 REST API (v4) plus SMART on FHIR endpoints, with webhooks and sandbox accounts. Production access is not self-serve; it starts with an email to api@drchrono.com and partner approval for marketplace distribution.
Frequently asked questions
DrChrono scores D+ on Supergood's API Report Card. DrChrono runs a public developer program: an OAuth 2.0 REST API (v4) plus SMART on FHIR endpoints, with webhooks and sandbox accounts. Production access is not self-serve; it starts with an email to api@drchrono.com and partner approval for marketplace distribution.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
DrChrono is a cloud-based, mobile-first ambulatory healthcare platform that bundles an Electronic Health Record (EHR), practice management (PM), medical billing / revenue cycle management (RCM), telehealth, patient portal (OnPatient), and a patient-payments stack into a single SaaS product.
Vertical: Healthcare (ambulatory EHR + practice management + revenue cycle management). Front-office staff use DrChrono to check patients in on an iPad, run real-time eligibility/benefits, collect copays, and schedule follow-up appointments.
In the broader US ambulatory EHR market DrChrono is a mid-tier player (well behind Epic, Athenahealth, eClinicalWorks, and NextGen) but is highly visible in the small-practice / iPad-EHR segment and has been voted #1 mobile EHR multiple years running.
Yes, DrChrono is the system of record for nearly everything an ambulatory practice does day to day.
Founded in 2009 by Michael Nusimow and Daniel Kivatinos and based in Sunnyvale, CA. DrChrono was the first EHR on iPad (launched alongside the original iPad in 2010) and was an early Y Combinator alumnus.
Default 500 calls/hour rate limit is restrictive for any non-trivial integration; per-second and per-10-minute throttles are non-configurable. No machine-to-machine (M2M) / client-credentials OAuth flow, developers report DrChrono has no current plans to add it, forcing human-in-the-loop auth for backend syncs. Full sourced list under Sources below.
Common alternatives include Athenahealth, Epic Systems, eClinicalWorks, Tebra (Kareo + PatientPop), NextGen Healthcare, AdvancedMD. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official DrChrono MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. DrChrono doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.