DrChrono

Name: DrChrono API
Brand: DrChrono
Availability: InStock

✓ Official Vendor SpecHealthcareEhr Emroauth2310 EndpointsREST

For Agents

Query patient records, schedule appointments, submit billing claims, manage prescriptions, and run insurance eligibility checks across a complete EHR and practice management platform with 310 endpoints.

Install Jentic One Beta

Connect the DrChrono to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DrChrono, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DrChrono API.

Schedule appointments with custom fields, recurring rules, and multi-provider support

Submit and track insurance claims with full billing code management and payment posting

Order labs and manage results with sub-vendor routing and result document tracking

GET STARTED

Start building with DrChrono API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DrChrono API for, with concrete tasks.

★ AI Agent Practice Management

AI agents access DrChrono's 310 endpoints through Jentic to automate practice workflows spanning scheduling, billing, and clinical documentation. An agent searches for operations by intent, loads the schema, and executes calls to check eligibility, book appointments, or pull clinical notes without manual endpoint mapping. Jentic manages OAuth 2.0 token refresh and scope enforcement transparently.

Search for patient Jane Smith by name, verify her insurance eligibility, then schedule a follow-up appointment with her primary care provider for next Tuesday at 2 PM

Clinical Documentation Workflow

Create and retrieve clinical notes with structured templates tied to specific encounters. The API supports batch retrieval of notes by date range, provider-signed attestation workflows, and custom vitals tracking. Clinical notes include diagnosis codes, procedures performed, and follow-up instructions that feed directly into billing.

Retrieve all clinical notes for patient ID 5678 from the last 30 days, extract the ICD-10 diagnosis codes, and list pending follow-up actions

Insurance Eligibility and Billing

Run real-time insurance eligibility checks and submit claims with CPT codes, modifiers, and charge amounts. The API connects eligibility verification to charge capture and claim submission in a single workflow. Supports daysheet reporting for reconciliation and payment posting for received remittances.

Run an eligibility check for patient ID 1234 using their primary insurance, then create a claim for CPT code 99213 with a charge amount of $150

Lab Order Management

Create lab orders routed to specific sub-vendors, track order status, and retrieve structured results when available. The API supports the full lab lifecycle from order creation through result attachment to the patient chart. Integration with multiple reference labs allows practices to route orders based on test type and patient preference.

Create a CBC lab order for patient ID 9876 routed to sub-vendor Quest Diagnostics, then check the order status after 24 hours

Key Endpoints

310 endpoints — access a full-featured ehr and practice management platform covering clinical documentation, patient records, appointment scheduling, billing, lab orders, prescriptions, and insurance eligibility across 310 endpoints.

METHOD

PATH

DESCRIPTION

GET

/api/patients/{id}

Retrieve patient demographics and details

POST

/api/appointments_list

Search and filter appointments

GET

/api/eligibility_checks

Run insurance eligibility verification

POST

/api/claim_billing_notes

Create billing notes for claims

GET

/api/clinical_notes_list

Retrieve clinical notes in batches

POST

/api/lab_orders/{id}

Create or update lab orders

POST

/api/medications

Create patient medication records

GET

/api/day_sheet_charges

Retrieve daysheet charges report

GET

/api/patients/{id}

Retrieve patient demographics and details

POST

/api/appointments_list

Search and filter appointments

GET

/api/eligibility_checks

Run insurance eligibility verification

POST

/api/claim_billing_notes

Create billing notes for claims

GET

/api/clinical_notes_list

Retrieve clinical notes in batches

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DrChrono OAuth 2.0 credentials (client ID, secret, and refresh tokens) are stored encrypted in the Jentic vault (MAXsystem). Agents receive scope-limited access tokens with automatic refresh — raw secrets and refresh tokens never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'check insurance eligibility') and Jentic returns matching DrChrono operations with their input schemas including required patient IDs and scope requirements, so the agent can call the correct endpoint without parsing 310 operations manually.

Time to first call

Direct DrChrono integration: 5-10 days for OAuth setup, scope configuration, and endpoint mapping across 310 operations. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using DrChrono API through Jentic.

What authentication does the DrChrono API use?

The DrChrono API uses OAuth 2.0 with the authorization code grant flow. Scopes control access to specific data categories: billing:read, patients:read, clinical:read, and others. Through Jentic, OAuth tokens are managed in the MAXsystem vault with automatic refresh, and agents receive scoped tokens without handling client secrets.

Can I run insurance eligibility checks with the DrChrono API?

Yes. The GET /api/eligibility_checks endpoint runs real-time eligibility verification against a patient's insurance plan. You provide the patient ID and insurance details, and the API returns coverage status, copay amounts, and deductible information. Results are stored and searchable for future reference.

What are the rate limits for the DrChrono API?

DrChrono enforces rate limits per OAuth application. Standard limits are approximately 100 requests per minute for most endpoints. Batch endpoints like /api/clinical_notes_list and /api/appointments_list return paginated results to manage large datasets without hitting limits.

How do I retrieve clinical notes through Jentic?

Search Jentic for 'retrieve clinical notes DrChrono' to discover the clinical_notes_list endpoint. The agent loads the schema for GET /api/clinical_notes_list which accepts date range, patient, and provider filters. Install via pip install jentic and use the search-load-execute flow to pull notes without manual endpoint configuration.

Does the DrChrono API support ePrescribing?

Yes. The POST /api/medications endpoint creates prescription records with drug details, dosage, frequency, and pharmacy routing. The API integrates with ePrescribing networks to send prescriptions electronically. You can also retrieve a patient's active medication list via GET /api/medications.

Can I generate billing claims from encounter data?

Yes. After documenting a clinical encounter, use POST /api/claim_billing_notes to attach billing notes with CPT codes and charge amounts. The GET /api/day_sheet_charges endpoint provides daysheet reports for reconciliation. Claims flow from clinical documentation through charge capture to submission.

DrChrono

Connect the DrChrono to your agent

Capabilities

Start building with DrChrono API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs