The receiving specialist has about one page to answer a practical question: why is this patient here, and what does the referring clinician need from me?
A long chart export does not answer that question. Neither does a referral letter filled with copied history and no request. The useful letter is a routing document with a clinical point of view. It shows the receiving team what changed, what has already been tried, what evidence matters, and who owns the next step.
A one-page referral structure
Use the template below as a drafting frame, then adapt it to the patient, specialty, payer process, state law, and your organization’s policy.
REFERRAL DATE: ____________________
PATIENT
Name: ____________________
DOB: ____________________
Identifier used by your approved workflow: ____________________
Contact and access needs: ____________________
FROM
Referring clinician and credentials: ____________________
NPI when required: ____________________
Practice: ____________________
Direct clinical contact or approved queue: ____________________
TO
Receiving clinician or service: ____________________
Approved destination: ____________________
REFERRAL REASON
State the problem and why specialty input is needed now:
________________________________________________________________
REQUESTED ACTION
Name the requested consultation, opinion, evaluation, co-management,
transfer, or other action:
________________________________________________________________
CLINICAL SNAPSHOT
Current problem and dated course: ____________________
Pertinent findings and source dates: ____________________
Treatments tried and response: ____________________
Conditions relevant to this request: ____________________
Current medications and allergies: ____________________
ATTACHMENTS
List named reports, images, note dates, medication list, and any required
insurance or authorization material:
________________________________________________________________
URGENCY AND SAFETY
Requested timeframe: ____________________
Specific concern and approved escalation path: ____________________
FOLLOW-UP OWNER
Person or team tracking receipt, scheduling, result, and patient communication:
________________________________________________________________
CLINICIAN REVIEW
Reviewed by and credentials: ____________________
Signed date and time: ____________________Do not use the template as a reason to repeat the whole record. Its value comes from selection and ordering.
Put the request above the history
The referral reason should identify the clinical problem and the reason for specialty input. The requested action should tell the recipient what response would complete the handoff.
Compare these two lines:
Knee pain. Please evaluate.
Six weeks of right knee pain after a twisting injury, persistent despite activity modification; please assess the suspected meniscal injury and advise on imaging and treatment.
The second line is fictional, not medical advice. It works as a template example because it supplies a course, response to an initial step, working concern, and requested decision. A clinician would replace every detail with verified patient-specific facts.
Do not manufacture certainty to make the letter sound decisive. If the diagnosis is uncertain, say so. The specialist needs the actual question, not a polished answer that the record cannot support.
Build the snapshot around the decision
Every item in the clinical snapshot should help the recipient triage, evaluate, or act on the request.
For a medication-related referral, current medications, prior trials, reactions, renal or hepatic information, and the relevant test results may matter. For a surgical opinion, the functional effect, prior treatment, imaging location, and perioperative risks may matter. The referring clinician decides what is pertinent.
Use dates. “Recent MRI” forces the receiving office to search. “MRI right knee, September 12, 2026; report attached” points to a specific artifact. If the image itself is available through a separate exchange path, name that path instead of implying the letter contains it.
Separate attached facts from summarized facts
A referral letter can summarize a report, but a summary is not the report. Mark the difference.
| Content in the letter | Supporting artifact |
|---|---|
| ”CBC on September 10 showed…” | Named lab result and date |
| ”Prior therapy did not improve function” | Therapy notes or verified patient history |
| ”Imaging raised concern for…” | Radiology report and image-access instructions |
| ”Medication stopped because of…” | Medication record and documented reaction |
When the source conflicts with the summary, stop and reconcile it before sending. Copying both versions into the referral merely transfers the ambiguity.
Handle HIPAA accurately
HHS explains that treatment includes coordination, consultation, and referral between health care providers. The HIPAA Privacy Rule generally permits a covered entity to use or disclose protected health information for treatment without a separate authorization under that federal rule (HHS treatment guidance, 45 CFR 164.506).
HHS also states that provider-to-provider disclosures and requests for treatment are exempt from the Privacy Rule’s minimum necessary standard (HHS minimum necessary guidance). Do not turn that exception into a rule to send everything. The treatment team still needs accurate information, reasonable safeguards, correct routing, and compliance with any stricter law, agreed patient restriction, or organization policy that applies.
Use the approved exchange channel. Verify the destination. Avoid placing sensitive details in an unapproved cover message. If the referral includes records subject to a separate federal or state confidentiality rule, follow the rule and your privacy team’s procedure.
Make urgency operational
“Urgent” without a reason, timeframe, or contact path leaves the receiving office to guess.
Write the observable concern and the requested action. For example: “New progressive weakness documented at today’s visit; referring clinician requests same-day triage through the approved direct number.” This is a fictional wording example. The actual patient assessment and disposition belong to the treating clinician.
Emergency care should not depend on a routine referral queue. Your workflow should state when staff use emergency services, a direct clinician handoff, or another local escalation path.
Give the loop an owner
Sending is an event. Referral completion is a workflow.
Record the destination, channel, timestamp, sender, and attachments. Track whether the receiving office accepted the referral, whether the patient was scheduled, and whether a report or other response returned. Route exceptions to a named role rather than a shared queue with no service rule.
A practical status set might include drafted, clinician-approved, sent, receipt-confirmed, scheduled, completed, report-received, and exception. Define what evidence changes each status. An automated “sent” flag should not be relabeled “received” unless the channel actually supplies that confirmation.
Review an AI-generated draft line by line
An AI draft can reduce retyping. It can also carry forward an old medication, turn a tentative assessment into a diagnosis, omit a failed treatment, attach the wrong time frame, or address the wrong recipient.
The signing clinician should verify patient identity, referral reason, requested action, chronology, medications, allergies, test dates, attachments, urgency, recipient, and follow-up owner. This is a content review and a routing review. Both matter.
Patient Square’s public US pricing describes an AI medical scribe, review-ready SOAP notes, ICD-10 suggestions, eRx drafts, scheduling, messaging, and EHR-ready exports (Patient Square pricing). It does not establish unsupervised referral sending or replace the clinician’s responsibility for the letter.
Review the published product scope.
The best medical referral letter is not the longest record. It is the shortest accurate path from the referring clinician’s question to the receiving clinician’s next decision, with the supporting evidence and follow-up ownership still attached.