What we do
Tools
Industries
Department
How we workLet's talk →
Home/DrChrono
DrChrono

What You Can Build on the DrChrono API, and How Access Actually Works

Patients already fill in a web form before they arrive, and somebody at the desk still types it into DrChrono. DrChrono, now an EverHealth company, publishes a documented REST API that a practice can use on its own account, so that gap is fixable. Registering the app takes minutes. The work is in choosing scopes, keeping tokens alive and not creating a second copy of every patient.

Where DrChrono stops

It ships with an open API, but most practices never use it, so intake, billing and referrals stay manual.

Stuck on DrChrono? Let's solve it →

From a DrChrono login to your first patient request

These follow DrChrono's own API tutorial. A free DrChrono account is enough to build and test against.

  1. 1

    Create the API application

    Account Other Settings API New Application

    Give it a name and add at least one redirect URI, the address in your code that receives the authorization code. Save, and DrChrono shows the client ID and secret.

  2. 2

    Send the provider through authorization

    Redirect them to app.drchrono.com/o/authorize/ with your client ID, redirect URI and a space-separated scope list. If they cancel, you get error=access_denied back instead of a code.

    Watch for: leaving scope out. DrChrono then requests every scope, which is more access than an intake form ever needs.

  3. 3

    Swap the code for tokens right away

    The code works once and expires fast. Post it to /o/token/ and store both the access token and the refresh token that come back.

  4. 4

    Refresh inside the 48-hour window

    Access tokens last 48 hours. Before that runs out, post the refresh token with grant_type set to refresh_token (no redirect URI this time) and save the new pair.

  5. 5

    Read every page, not just the first

    List endpoints come back in pages. Keep following the next URL and collecting results until next is null.

  6. 6

    Pin the API version

    DrChrono lists versions v0 to v4, and new apps default to the latest. Set the version on the app's settings page or per request with the X-DRC-API-Version header, so an upgrade happens when you choose it.

One practice connecting its own account, or a product for many practices

Your own practice

An integration for the account you run

  • A provider in your practice authorizes the app once, against your own DrChrono account.
  • Typical jobs: web intake into patient records, a billing worklist, referral source tracking.
  • You decide the scopes, where tokens live and who can see the output.
A product

An app other DrChrono practices will install

  • Every practice authorizes separately, and you keep a token pair for each one.
  • Reaching accounts outside your own falls under DrChrono's API development terms, so read those and talk to DrChrono before planning a launch.
  • Version pinning and paging matter more, because one change breaks every customer at once.

A practice connecting its own account is the first case above, and that's the work n-frames takes on.

Why a DrChrono integration that worked in March is silent by May

Nobody saved the new refresh token

How you'll know: Calls start failing about two days after the last successful refresh, and re-authorizing fixes it until it happens again.

Fix: Store the token pair the refresh returns every time, in one place, and have a single job do the refreshing.

Only the first page ever got read

How you'll know: Newer patients or appointments never show up downstream, but a test with five records looked perfect.

Fix: Loop on the next URL until it's null. Test with a date range that returns more than one page.

Fields changed under an unpinned version

How you'll know: A field you rely on is missing or renamed, and nobody touched the code.

Fix: Set the version explicitly, and move to a newer one on purpose, after testing.

Intake creates a second chart for returning patients

How you'll know: The desk keeps merging duplicate patient records after web forms come in.

Fix: Search for an existing patient before creating one, and send anything that only half matches to a person instead of guessing.

Webhooks pointed at an endpoint that never proved itself

How you'll know: Events are switched on in the API app, but your endpoint sees nothing, or sees requests it can't trust.

Fix: Webhooks are set up on the API application with a secret token you choose. Use DrChrono's webhook docs to pass its verification step and check each delivery against that secret.

A solo specialist with an iPad in every room

One provider · DrChrono at the front desk and in each exam room

Before

New patients filled in a paper form in the waiting room, and the medical assistant typed it into DrChrono between appointments.

Overdue balances sat in a billing report nobody opened until month end, when someone finally started calling patients one at a time.

After

Patients fill in a web intake form before they arrive, and it creates or updates their DrChrono record through the API.

Any balance that passes 30 days appears on the front desk's worklist inside the practice, so follow-up starts then instead of at month end.

Questions people ask

What is DrChrono, and who uses it?

Cloud EHR and practice management software designed around iPad charting, mostly used by smaller independent practices. Scheduling, e-prescribing and billing sit alongside the clinical record. Its patient portal, OnPatient, is covered on our OnPatient page.

How much does DrChrono cost per month?

DrChrono sells tiered subscriptions that vary with practice size and the billing and clinical features you need, and the plans change from time to time. Its pricing page or sales team has today's numbers. Building and testing against the API only needs a free account, according to DrChrono's tutorial.

Does DrChrono have an API, and is it open to practices?

Yes. DrChrono documents a REST API with OAuth 2.0 authorization, paginated list endpoints, versioning and webhooks. A practice can register its own API application from its account settings and connect it to its own data.

Is there a DrChrono mobile app for the iPad?

Yes. DrChrono was built for the iPad first, so charting, scheduling and billing run on a tablet in the exam room rather than through a desktop system with an app added later.

Is DrChrono good for a small practice?

It's known for its tablet-first design and its open API, which few EHRs its size can match. Whether it suits you depends more on your workflow and how complicated your billing is than on general reviews.

Who builds and maintains a DrChrono API integration?

That's the part n-frames takes on: the API app and scopes, the intake connection, the billing worklist, token refresh and version upgrades, and checking it keeps running after launch. Patient details stay in DrChrono and the systems you already use for them.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.