All articles

Beyond the SOAP Note: How AI Can Automate Referral Letters

Referral letters take 8–15 minutes to draft manually. AI can generate them from the same encounter data that drives the SOAP note — without the physician touching a keyboard.

Referral Letter Automation with AI

The Referral Letter Is Physician Time That Doesn't Have to Be Physician Time

The referral letter sits at an interesting intersection in the clinical workflow. It is clinically important — the quality of information transferred from referring physician to specialist directly affects the quality and efficiency of the specialist consultation. It is legally important — the referral letter often becomes part of the evidentiary record if care outcomes are questioned. And it is almost entirely derivative work: the information needed to write a good referral letter is already present in the physician's clinical assessment and plan. The physician isn't generating new clinical content. They are reformatting existing content for a new audience.

The time cost is real. Physicians who are asked to estimate the time they spend on referral letters typically say 8 to 15 minutes per referral, depending on the complexity of the patient and how much of the letter they compose from scratch versus how much they copy from existing notes. For a physician who writes 5 to 10 referrals per week — common in internal medicine and family medicine with complex panels — that is 40 to 150 minutes per week of documentation time that is, in principle, automatable from information already documented in the encounter.

What a Good Referral Letter Contains

Before discussing automation, it's worth being specific about what referral letter quality actually means — because a poorly structured referral letter that is produced quickly is not an improvement over a well-structured one that takes longer. The specialist receiving the referral needs, at minimum:

  • The reason for referral, stated clearly and specifically (not "further evaluation" but "evaluation of progressive dyspnea with exertional component, 3-month course, no improvement with empiric bronchodilator trial")
  • Relevant history: diagnosis history, prior workup for this problem, pertinent comorbidities that affect the specialist's differential
  • Current medications, especially those relevant to the referral indication
  • Recent labs, imaging, or diagnostic results relevant to the presenting problem
  • The referring physician's clinical question — what they specifically want the specialist to address
  • Urgency framing — is this a routine referral, urgent, or does the patient need to be seen within a specific timeframe?

A referral letter that omits the referring physician's specific clinical question — that doesn't say "please evaluate for pulmonary hypertension given RV strain on ECG" — sends the specialist into a consultation without a clear brief. The result is a consultation note that answers the specialist's interpretation of the referral rather than the referring physician's actual question. This mismatch is a documented source of care coordination inefficiency and patient dissatisfaction.

How AI Generates Referral Letters from Encounter Data

The technical approach for AI-generated referral letters is grounded in the same encounter data that drives SOAP note generation. When an ambient documentation system has captured the clinical encounter, it has access to the full conversation between physician and patient, including the physician's clinical reasoning about why they're sending the referral and what they want the specialist to address. The referral letter is, in a well-designed system, an extraction and reformatting task applied to that data.

The key components the AI extracts and reformats:

Reason for referral: Derived from the physician's Assessment and Plan discussion during the encounter. If the physician explicitly stated "I'm referring you to cardiology for evaluation of this palpitations pattern," that statement — and the clinical context around it — drives the referral reason.

Clinical summary: Drawn from the Subjective (patient-reported history) and Objective (exam findings, vital signs) sections of the encounter, filtered to information relevant to the specialist's field. A cardiology referral letter doesn't need the patient's current ophthalmology follow-up status; it does need recent EKG findings and the results of any prior cardiac workup.

Medication list: Pulled from the medication reconciliation data, filtered for medications relevant to the referral indication.

Diagnostic results: Pulled from pending or completed orders associated with the encounter, with reference values and abnormal flags.

The letter is then structured in the professional register appropriate for specialist-to-specialist communication — clinical and specific, not consumer health language — and addressed to the specialty and referring context.

A Family Practice Implementation Example

A six-physician family medicine practice — call them Harborview Family Practice — tracked referral letter production before and after implementing AI-assisted referral generation as part of their ambient documentation workflow. Before implementation, referral letters averaged 11 minutes of physician time each; physicians produced an average of 7 referrals per week each. After implementation, physician review time for AI-generated referral letters averaged 2 minutes — the physician reviewed the draft for accuracy, added any clinical context the system had missed, and adjusted the tone where needed. The practice tracked specialist feedback informally: referring specialists noted that referral letters from the practice had become more complete, particularly in the diagnostic workup summary and the explicit statement of the clinical question.

Where AI Referral Generation Requires Physician Input

There are specific components of a referral letter that AI cannot generate without physician input, or that require physician judgment to generate accurately. The explicit clinical question — what the referring physician specifically wants the specialist to determine or address — is the most important. If the physician didn't state it clearly during the encounter, the AI system will produce a referral reason that's accurate as far as it goes but may not capture the specific diagnostic question the physician has in mind. This is an argument for physicians to state their referral question explicitly during the encounter conversation, which the ambient system will then capture and incorporate.

Urgency framing is another component that requires physician judgment. The difference between "please see this patient in the next 2 weeks" and "please see this patient this week given the clinical trajectory" is a clinical decision that depends on the physician's assessment of severity and trajectory. AI systems can flag encounter elements associated with urgency — certain vital sign abnormalities, the physician's tone in discussing the referral — but the final urgency determination should be physician-made and physician-reviewed.

We are not saying AI referral generation replaces physician judgment. We are saying it removes the time-intensive reformatting work that has nothing to do with physician judgment. The physician's clinical thinking is captured in the encounter. The AI structures it into the letter. The physician reviews for accuracy and adds any nuance the system missed. That division of labor is appropriate and efficient.

Integration with EHR Referral Workflows

The value of AI-generated referral letters depends partly on how well they integrate with the EHR's referral workflow. In Epic, for example, referral management is handled through the Referrals module, which manages the referral order, the referral letter, and the communication to the specialist. An AI documentation system that generates a standalone text document requires the physician to copy the content into the EHR's referral workflow — which adds steps rather than removing them.

The most effective implementations push the AI-generated referral letter content directly into the EHR's referral order, pre-populating the letter field so that the physician's review and signature is the only required step. This requires the AI system to have write access to the EHR's referral module, which is a more complex integration than note delivery alone, but it is the integration pattern that produces the largest physician time savings.

Tracking whether specialist practices receive and act on referrals — referral closure in the EHR — is a separate workflow that AI documentation tools don't currently address. But the referral letter quality improvements from AI generation create a downstream benefit: specialists who receive more complete, well-structured referrals are less likely to return them with information requests or to perform duplicate workup because the referring physician's diagnostic thinking wasn't communicated.

Ready to reduce your documentation time?

Try Notevyx with your own patients in a structured 30-day pilot.