Incoming referral intake and routing
An agent reads incoming referrals from fax inboxes and email, extracts the key administrative details into the intake queue, flags missing documents, and routes each referral for staff to schedule.
The use case
Specialty practices receive referrals by fax, email, and portal, often as scanned documents with inconsistent layouts. Front-desk staff spend hours retyping patient and referring provider details, and referrals with missing insurance information or notes sit unnoticed. The agent reads each incoming referral in a HIPAA-eligible environment, extracts administrative fields such as patient name, date of birth, insurance, referring provider, and requested specialty or location, and creates an intake record. It checks a practice-defined list of required documents and flags anything missing. It routes the record to the right scheduling queue based on location and specialty rules. Staff verify the extracted details, contact the referring office for missing items, and schedule the patient. The agent does not judge clinical urgency or make triage decisions; any urgency flags come from the referring provider.
Example workflow
- Referrals arriving by eFax, email, or portal are saved to a HIPAA-eligible document storage location covered by a business associate agreement.
- The agent extracts administrative fields and the referral reason text as written, without interpreting it.
- It compares attached documents with the practice's required-document list for that referral type and flags gaps.
- It creates or updates an intake record in the practice management system or a HIPAA-eligible tracker and routes it by location and specialty.
- Staff verify the extracted details, request missing documents from the referring office, and schedule the patient.
- Referrals not scheduled within the practice's target time appear on a daily follow-up list for staff.
Tools
- eFax or RingCentral Fax
- Practice management system
- Google Workspace (with BAA)
- Claude (HIPAA-eligible setup)
- Airtable (with BAA)
Risks and guardrails
- PHI is processed in tools without a business associate agreement — guardrail: every tool in the workflow is HIPAA-eligible and covered by a signed BAA before any patient data is used.
- Details such as date of birth are misread from scanned documents — guardrail: staff verify key fields against the original document before scheduling.
- The agent appears to set clinical priority — guardrail: it never ranks referrals clinically; urgency comes only from what the referring provider wrote, reviewed by staff.
- Referrals are routed to the wrong location — guardrail: routing rules are kept in a simple table, and staff can reassign records.
Related recipe
Provider Credentialing Packet Tracker and Reminder Drafts: An agent tracks provider licenses, DEA, board certs, malpractice COIs, CAQH attestations, and payer enrollment, flags expirations and gaps, and drafts reminders for staff to approve.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Google Workspace extension (official page): github.com/gemini-cli-extensions/workspace (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Airtable MCP server (official page): support.airtable.com/articles/9897799762-using-the-airtable-mcp-server (checked 2026-11-09)