Skip to main content
This document covers drchrono_get_appointment_documentation, the native DrChrono clinical documentation tool exposed through the Agents Platform.

​
Authentication

DrChrono tools use the DrChrono OAuth connector. The platform injects access_token.

​
drchrono_get_appointment_documentation

Fetches clinical documentation for a DrChrono appointment, including appointment metadata, structured clinical notes, patient problems, and medications. When a locked clinical-note PDF URL is available, the URL is returned for downstream PDF-to-markdown conversion by the existing doc_converter tool. The tool is read-only.

​
Inputs

Required:
  • appointment_id: DrChrono appointment ID.
Optional:
  • patient_id: Patient ID if already known from the summary step.
  • doctor_id: Doctor ID if already known from the summary step.

​
Execution Flow

​
Output

Common failure reasons:
  • drchrono_not_connected
  • appointment not found
  • clinical note not locked or unavailable

​
Human-readable text

The tool emits markdown for the feed: an ## Appointment Documentation summary table, an ## Appointment field table, and ## Clinical Notes, ## Problems, ## Medications, and ## Errors sections. Full note bodies stay in structuredContent.

​
Agent Instruction Guidance

Run this only after summary-level and alert-driven skip checks pass. For DrChrono coding, pass the returned clinical notes, problems, and medications into coding_diagnosis, then coding_cpt_generation, coding_charge_reviewer, and coding_format_validation. If a locked PDF URL is available, route it through doc_converter before the coding tools.