DrChrono

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.

Can I limit what my agent is allowed to do with the DrChrono API?

Yes. DrChrono issues OAuth tokens with granular scopes such as patients:read and billing:read, and because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. You can grant only the scopes the needed operations require, for example limiting the agent to checking insurance eligibility or listing clinical notes while withholding write actions like creating medications or billing notes. Your DrChrono client secret and refresh tokens stay stored in your own instance and are exchanged for scope-limited access tokens at execution time, so the agent can only call the operations you allow.