DrChronoAutomation & Integration
Build scoped DrChrono workflows for patients, scheduling, clinical data, and billing.
DrChrono's OAuth 2.0 API exposes patients, appointments, clinical records, documents, and billing data according to the application's scopes and provider permissions.
Representative workflow
DrChrono
EHR & Clinical
- 01
Apply the project workflow
Patient records created from intake when approved scopes and endpoints allow
Project destination
The system or person selected for this workflow
How I use DrChrono
A DrChrono provider authorizes a registered application through OAuth 2.0, and both the requested scopes and that user's in-product permissions govern access. Supported endpoints cover patient records, appointments, clinical notes, medications, problems, allergies, procedures, documents, and billing transactions. Create and update support varies by endpoint, and integrations must account for hourly rate limits and smaller pages on expensive clinical responses.
A practical starting point
Patient records created from intake when approved scopes and endpoints allow
Workflow blueprint
From DrChrono to useful action
A representative implementation pattern. The project determines the exact fields, logic, access, and destination.
DrChrono
EHR & Clinical
- 01
Use the required platform data
Patients, demographics, and insurance
- 02
Apply the project workflow
Patient records created from intake when approved scopes and endpoints allow
Project destination
The system or person selected for this workflow
What the integration supports
Facts checked
Authentication and access
DrChrono uses OAuth 2.0 authorization code flow. A provider authorizes a registered application, which exchanges the code for scoped access and refresh tokens.
Useful data and actions
- Patients, demographics, and insurance
- Appointments and calendar data
- Clinical notes and note fields
- Medications, problems, allergies, and procedures
- Patient documents and billing transactions
Constraints to confirm
- Both OAuth scopes and the authorizing user's DrChrono permissions apply; practice sharing settings govern visibility across providers.
- The default application limit is 500 calls per hour, with 429 responses above the limit; higher limits require approval.
- Pagination varies by endpoint, and expensive responses such as verbose records or clinical notes use smaller page sizes.
- Create, update, and delete support is endpoint-specific; clinical-note retrieval has additional filter and permission requirements.
What I automate with DrChrono
Patient records created from intake when approved scopes and endpoints allow
Post-visit follow-up sequences triggered by appointment completion
Billing transactions prepared for accounting workflows
Appointment reminders via SMS and email from DrChrono schedule data
Scoped clinical data routed to authorized review tools
Industries
Related integrations
Ready to integrate DrChrono into your workflows?
Every project starts with a free call. We'll figure out what's worth automating and what isn't.
Book a Free Call