DrChrono

Last reviewed: July 2026

Overview

Integuru's DrChrono integration provides production-ready HTTP API access to DrChrono, the cloud-based EHR and medical billing platform, covering 4 actions across DrChrono's full action surface: patient creation via create_patient, paginated patient listing via list_patients, allergy record retrieval via list_patient_allergies, and medication history access via list_patient_medications. All 4 actions carry richer documentation. Integuru is HIPAA-compliant and signs BAAs at no additional cost. Calls complete in under 3 seconds with a 99.9%+ success rate via direct HTTP requests rather than browser automation.

No public write API for key workflows. DrChrono exposes a limited official API, but key clinical data workflows such as programmatic patient creation with full demographic capture, allergy status filtering, and paginated medication history retrieval are not reliably available through the official surface. Integuru connects to the same internal endpoints DrChrono's web application uses, giving healthcare engineering teams a stable, production-ready API surface for the full set of covered actions.

The integration spans core patient data management: list_patients retrieves the paginated roster with name search and phone filtering; create_patient creates new patient records with a comprehensive demographic and clinical field set; list_patient_allergies returns active or filtered allergy records per patient; and list_patient_medications returns paginated medication histories with optional status filtering. See the eClinicalWorks integration for another large ambulatory EHR, or browse the full integrations catalogue.

---

Use Cases

Integuru's DrChrono integration covers the patient record and clinical data workflows that healthcare engineering teams need to automate.

• Patient roster retrieval: Call list_patients with optional query (name search), phone (phone number filter), sort_column, sort_order, and page to retrieve a filtered, paginated patient list. Omit all parameters for the full roster.
• Patient creation: Call create_patient with first_name and last_name required; pass any combination of the 40+ optional demographic, contact, employer, identity, and clinical fields. If doctor is omitted, Integuru auto-detects the logged-in provider's ID.
• Allergy record retrieval: Call list_patient_allergies with a patient_id (numeric chart ID) to retrieve allergy records. Pass status to filter to active, inactive, or other allergy states; defaults to active if omitted.
• Medication history access: Call list_patient_medications with patient_id to retrieve the medication list. Use page (integer, starts at 1) to paginate through large histories and status to filter by medication status.
• Patient matching and sync pipelines: Combine list_patients (name/phone search) with list_patient_allergies and list_patient_medications to build cross-system patient matching and clinical data sync workflows without maintaining browser scripts.
• AI agent tooling for clinical data: All four actions serve as reliable read and write tools for healthcare AI agents that need to create patient records, look up medication lists, or check allergy flags programmatically within clinical decision workflows.

---

Setup Notes

Integuru's DrChrono integration authenticates against https://<SUBDOMAIN>.drchrono.com/. Configure your practice's specific subdomain once during Integuru setup. For accounts accessed via https://app.drchrono.com/accounts/login, Integuru handles that login flow as well; configure the appropriate base URL for your deployment during setup. Integuru manages session authentication automatically.

For create_patient, only first_name and last_name are required. For list_patient_allergies and list_patient_medications, patient_id (the numeric DrChrono chart ID) is required; all other parameters are optional. For list_patients, all parameters are optional.

All 4 actions carry richer documentation available via the Integuru dashboard after setup. Full parameter documentation is available for actions marked with the docs badge in the action table above.