Medical Referral Letter: Template, Examples, and a Sending Checklist

A medical referral letter asks another clinician or service to assess a patient, answer a clinical question or take on specified care. Lead with what you need and how urgently, then supply the history, findings and results that explain the request. Finish with the patient's needs, the attachments and who will follow up.

The letter is one part of the referral: drafted, sent, received, accepted and completed are different states. This guide gives referring clinicians, specialist teams and referral coordinators fictional examples of an opinion request, a corrective addendum and an ongoing-care transfer, plus separate letter and tracking templates.

Sources checked October 21, 2026. Primary care, specialist and referral-coordinator review is pending.

For an emergency or immediate clinical concern, use the local urgent-care or escalation pathway; do not wait for a letter in an outpatient queue.

Jump to the copyable referral letter template.

Referral letter example: a clear question comes first

RL-01 is fictional. The source packet supplies the history, findings and decisions used in the finished letter. Names and contact details are placeholders.

Source packet

• Encounter: October 21, 2026; adult patient RL-01, age 42. The clinician recorded a three-month history of itchy, cracked skin on both hands, interfering with wearing work gloves.
• Findings: Examination that day recorded scaling and superficial fissures on both palms. No other examination findings were supplied.
• Treatment history: The patient reports trying fragrance-free emollient daily for six weeks and over-the-counter hydrocortisone 1% twice daily for seven days in September. Itching improved during that course and returned afterward. Current use is emollient only; medication reconciliation records no other medicines. Allergy status was checked at the visit: no known drug allergies reported.
• Investigation: The one-page September 30 laboratory report for a September 28 skin scraping states that no fungal elements were seen on microscopy. No culture result is supplied. A photograph dated October 21 is available as one file for sharing with the patient's agreement.
• Clinician's decision: Persistent hand dermatitis, cause not established. Request routine dermatology assessment to clarify the diagnosis and advise whether further investigation, including patch testing, is appropriate. The clinician has not ordered patch testing or assigned a contact-allergy diagnosis.
• Patient and follow-up: The patient agrees to the referral and sharing the photograph, prefers portal contact and wants to discuss the effect of work gloves. The primary care clinician retains interim care and sets October 23 as this referral's receipt-check date. The coordinator will check then and escalate missing acknowledgment to that clinician.

Finished referral letter

Date: October 21, 2026 · Referral: RL-01, version 1
To: Dermatology referral service [verified destination]
From: [Referring clinician, practice and callback details]
Re: [Verified patient identifiers and contact details], age 42

Request and priority: Routine dermatology assessment of persistent hand dermatitis. Please advise on the diagnosis and whether further investigation, including patch testing, is appropriate. Symptoms continue to interfere with wearing work gloves despite the measures described below.

Relevant history and findings: The patient reports three months of itchy, cracked skin affecting both hands. On October 21, examination showed scaling and superficial fissures on both palms. The cause remains uncertain.

Treatment and medicines: The patient reports six weeks of daily fragrance-free emollient and a seven-day course of hydrocortisone 1% twice daily in September. Itching improved during that course but returned afterward. Emollient is the only current treatment; no other medicines were reported at reconciliation. No known drug allergies were reported when checked today.

Results: Microscopy of the September 28 skin scraping found no fungal elements, as reported September 30. No culture result is available in this referral packet.

Patient discussion and ongoing care: The patient agrees to referral and photograph sharing, prefers portal contact and would like to discuss work-glove exposure. Primary care retains interim care. Please return acceptance or decline and anticipated appointment information to [practice contact]. Our coordinator will check receipt on October 23 and raise missing acknowledgment with the referring clinician.

Enclosures: September 30 microscopy report, one page; October 21 hand photograph, one file.
Approved by: [Referring clinician, signature and date]

The request is explicit, while the conclusion remains appropriately open. “Please consider whether patch testing is appropriate” asks for an opinion; “patch testing ordered” would invent an action. Similarly, a negative microscopy finding does not become “all fungal testing negative.” The letter preserves the test, sample date and reported result without expanding its meaning.

What to include in a medical referral letter

A useful letter is a focused clinical communication, not a copy of the entire chart. Ontario's CPSO Transitions in Care policy calls for written referrals that identify the parties, explain the request and urgency, and summarize relevant history, medicines and investigations. Check the receiving service's specific requirements as you prepare the letter.

Use these prompts to decide what the recipient needs to act:

1. Who and where: Correct patient identifiers, referring clinician, intended service, callback route and usual primary care clinician if different. Verify the actual destination, not just a familiar organization name.
2. Question and requested role: Is this a one-time opinion, a procedure request, shared care or a transfer of a particular problem? Name the requested decision rather than asking the recipient to infer it.
3. Course and impact: Describe onset, change over time, relevant positives and assessed negatives, and the effect on daily function. Keep reported history separate from observed findings.
4. What has already happened: Include relevant treatment, dose and duration where applicable, response and current status. “Prescribed” and “taken” can differ; preserve that difference.
5. Evidence and uncertainty: Give dates and the actual findings from relevant tests. Identify information that is pending, unavailable or disputed. Attach the correct version of a report when the receiving team needs it.
6. The person and the next step: Include communication or access needs, the patient's priorities, the information-sharing discussion and interim responsibilities.

In RL-01, the unsuccessful treatment course and work impact help explain the request. An unrelated historical note about a resolved illness would add volume without clarifying that question. Conversely, omitting the current treatment status could leave the recipient unsure whether the hydrocortisone course is ongoing.

The ACP care-coordination toolkit separates generic referral information from condition-specific information. Its pertinent data sets illustrate why a generic letter cannot substitute for the receiving specialty's requirements. Check the current local pathway rather than ordering extra investigations simply to fill every heading.

Write the clinical question and urgency together

“Please see this patient” names an activity but not its purpose. A stronger opening links the problem, evidence and requested help:

“Please assess persistent hand dermatitis and advise whether further diagnostic investigation is appropriate. Symptoms affect work-glove use; the documented topical course produced only temporary improvement.”

That wording does not demand a particular procedure or claim that a diagnosis is settled. It lets the specialist understand why the referral exists before reading the chronology.

Urgency needs the clinician's reason, not just a label. Record the requested priority, the information supporting it and any direct conversation already completed. If a local pathway uses a required form or triage category, carry the same meaning into that field. A routine field paired with an urgent narrative is a discrepancy to resolve before sending.

Distinguish three clocks: clinical reassessment, administrative acknowledgment, and the consultation appointment. A clinic's receipt-check date does not determine how long it is clinically safe to wait. If a patient reports a change while waiting, route that information for clinical review rather than simply restarting the administrative timer.

In Ontario, CPSO requires timely acknowledgment, urgently where necessary and no later than 14 days from receipt, with its stated absence provisions. This concerns acceptance or decline and appointment/wait information—not a universal appointment deadline or permission to defer urgent follow-up. For urgent consultations, the policy allows verbal referral followed by a written request. CPSO referral and acknowledgment requirements

Consent, privacy and patient communication

Record what the patient understands, what information will be shared, and any relevant objection or communication restriction. Agreement to see a specialist, permission to include a photograph and the legal basis for sharing records are related but distinct matters. Do not prefill “patient consented” before a discussion has occurred.

The UK GMC expects patients to understand why they are being referred, who is responsible for their care, what happens next and whom to contact. It also addresses explaining the information being passed on and responding when a patient objects to essential disclosure. GMC delegation and referral

In the United States, HHS OCR explains that HIPAA permits disclosure to another provider for treatment without a separate patient authorization. That does not remove other applicable legal restrictions or mean every record category follows the same rule. HHS: records sent to a treating specialist. Keep local privacy questions with the practice's privacy lead; do not apply the U.S. rule as an Ontario consent rule.

For the fictional RL-01 patient, an understandable message would be:

“We are asking dermatology to assess the hand problem and advise on further investigation. We will include the laboratory report and the photograph we discussed. Our practice remains your contact while you wait. We will check receipt on October 23 and update you through the portal. An appointment has not been confirmed.”

This message makes the next administrative action visible without promising a booking. A contact preference also needs to work operationally: if the person cannot access the portal, agree an alternative and record it. Avoid sending sensitive information to a shared contact channel merely because it was used successfully once.

Copyable medical referral letter template

Copy either blank output into an approved clinical workspace. Both have no prefilled normal findings, consent statements or urgency assignments. The two copy buttons are independent: copying the letter does not include the internal tracking checklist. These read-only fields do not accept patient information.

Outgoing referral letter

This is the document for the receiving clinician or service. Replace its prompts with verified information before approval and sending.

Internal tracking checklist

Keep this separate in the sending practice's record. It tracks delivery, acceptance and follow-up; it is not part of the outgoing letter.

If automatic copying is unavailable, choose Select text for the required output, then use your device's Copy command. Each field scrolls independently and can be resized; check which output you selected before pasting.

Use the receiving service's required form when one exists. For a shorter letter-only layout, see the referral letter template.

Sending checklist: verify the package, not just the letter

Treat the final letter and its enclosures as a single package. An attachment named in the text may still be missing from the transmission. Check the following before sending:

• Patient and recipient: Match identifiers across the letter and every enclosure. Confirm the service and transmission destination from an approved directory or verified contact.
• Clinical approval: The referring clinician checks the question, urgency, relevant findings, medicine status and unresolved information. A coordinator can prepare the package without making those clinical decisions.
• Attachments: Open each file. Compare its patient, date, version, page count and contents with the manifest. A report placeholder or inaccessible external link is not an attached report.
• Patient communication: Verify that the discussion and contact needs recorded in the letter actually occurred. Resolve restrictions through the appropriate privacy process.
• Rendered output: Inspect the final PDF, fax image or submitted form for truncation, missing symbols and omitted paragraphs. Check the copy that leaves the system, not only the editable draft.
• Delivery evidence: Record when, how and where the package was sent, retaining the transmission reference. Mark the actual delivery state rather than automatically declaring acceptance.
• Next owner: Assign the receipt check, backup coverage and escalation route. Keep pending investigations linked to their clinical owner and forwarding task.

HHS permits treatment communication by fax, email or telephone with reasonable safeguards, including attention to the correct destination. A permissible channel is not automatically a verified recipient. HHS treatment-communication safeguards

RL-02: correct a referral without losing its history

This fictional continuation uses the same patient and clinical request as RL-01 to show how to recover a missing attachment.

Additional supplied facts: At 14:10 on October 21, the coordinator sends version 1. At 10:00 on October 22, dermatology confirms receiving the letter and photograph but not the microscopy report. It has not yet accepted the referral. At 10:20, the referring clinician approves an addendum attaching the missing one-page report. The clinician makes no change to the question or priority. At 10:35 the coordinator sends the addendum; at 11:05 the receiving coordinator confirms receipt of that report. Clinical triage remains pending. The referring clinician sets an October 23 status check with the referral coordinator, backed up by the covering coordinator, and asks that unresolved acceptance be raised with the clinician then.

Corrective addendum example

October 22, 2026 — Addendum to RL-01, sent October 21
Re: [Same verified patient identifiers]
To: [Same verified dermatology destination]

Your team confirmed this morning that the microscopy report listed in our original enclosure list was not received. Attached now is the one-page report issued September 30 for the September 28 skin scraping: no fungal elements seen on microscopy. No culture result is supplied.

The clinical question and requested routine priority are unchanged. Please associate this report with RL-01 and return your acceptance/decline and appointment or wait information to [practice contact]. Primary care retains interim care.

Approved by: [Referring clinician, signature and date]
Enclosure: September 30 microscopy report, one page.

Internal record after sending: “11:05, October 22: receiving coordinator confirmed the report is attached to RL-01. Referral remains awaiting clinical triage; acceptance and appointment unconfirmed. Receipt task completed. Referral coordinator to check acceptance on October 23 and raise unresolved status with the referring clinician; covering coordinator provides backup.”

Notice that correcting the missing attachment closes one task, not the whole referral. The original sent version and its transmission evidence remain in the history. The addendum identifies exactly what was supplied later; it does not falsely imply the original package was complete.

Review the inaccurate completion message

Flawed entry: “Referral completed; dermatology has the report and will manage the patient.”

Three claims exceed the source. Receipt of an attachment does not establish acceptance. No appointment or consultation is documented. No agreement transferring ongoing management has been supplied. Replace that entry with the dated receipt confirmation and retain the outstanding acceptance task. If the system has only a single “completed” checkbox, it cannot represent this distinction without an additional status or linked work item.

For a true clinical correction—such as a changed result or priority—the clinician must also consider whether direct contact and retriage are needed. Simply overwriting the local letter leaves the recipient with the old information. See the medical documentation guide for preserving corrections and chronology.

RL-03: request transfer of defined ongoing care

RL-03 is fictional. Unlike RL-01's request for an opinion, it asks another clinic to take on ongoing follow-up of one established problem after a patient moves. The source packet defines the requested responsibilities and the clinician's existing plan.

Supplied facts and requested responsibilities

• Context: On October 21, patient RL-03, age 58, asks the current primary care practice to transfer hypertension follow-up to a new primary care clinic near their home. The patient agrees to share the relevant records and prefers telephone contact.
• Clinical record: Hypertension was diagnosed in 2023. The October 21 visit records blood pressure of 136/82 mmHg. Medication reconciliation confirms reported use of amlodipine 5 mg orally once daily, no other medicines reported, and no known drug allergies reported. The clinician records no treatment change at that visit. A September 30 laboratory report is available as a two-page attachment; its values are not supplied in the source packet.
• Proposed scope: The current clinician requests routine transfer of blood-pressure review and related prescribing, subject to the new clinic's assessment and acceptance. For this patient, the clinician's existing plan calls for a review on November 4. No appointment has been made.
• Work retained: An unrelated investigation ordered by the current practice on October 19 remains pending. Its ordering clinician retains result review and patient communication. It is not included in this transfer request.
• Continuity and package: The current clinician retains the requested follow-up and prescribing until the agreed effective handover date, not merely until acceptance arrives. The referral coordinator will check on October 23 and raise unresolved acceptance or an unavailable November 4 review with that clinician. Enclosures are the October 21 medication/allergy reconciliation, one page, and the September 30 report, two pages.

Transfer-request letter

October 21, 2026 — RL-03, version 1
To: [Verified new primary care clinic]
From: [Current clinician and callback details]
Re: [Verified patient identifiers and telephone contact], age 58

Request: Please consider accepting ongoing hypertension follow-up and related prescribing following this patient's move. We request routine transfer of these defined responsibilities, with the arrangements below to be agreed.

Relevant information: Hypertension was diagnosed in 2023. Blood pressure recorded on October 21 was 136/82 mmHg. At medication reconciliation, the patient reported amlodipine 5 mg orally once daily, no other medicines and no known drug allergies. No treatment change was made at this visit. The September 30 laboratory report is enclosed for your review.

Continuity: Our existing plan calls for review on November 4. Please confirm whether your clinic can accept the requested care, the effective start date and the review arrangements. Our clinician retains this follow-up and prescribing until the agreed effective handover date. We also retain review and communication of the unrelated investigation we ordered on October 19; that pending work is not transferred by this letter.

Patient discussion and response: The patient requested this move, agrees to the relevant record sharing and prefers telephone contact. Our coordinator will check acceptance on October 23 and escalate any unresolved handover or unavailable review arrangement to the referring clinician.

Enclosures: October 21 medication/allergy reconciliation, one page; September 30 laboratory report, two pages.
Approved by: [Referring clinician, signature and date]

A later supplied response: At 15:00 on October 23, the receiving clinician confirms acceptance of hypertension review and related prescribing from October 28 and a review appointment on November 4. The referring clinician confirms that arrangement, retains the October 19 result task, and the coordinator explains the agreed contact arrangements to the patient by telephone at 16:00. The tracking record now records accepted, effective October 28, the agreed scope and appointment; it does not record the November 4 visit as already completed.

The distinction is the requested role: RL-01 asks “What is your opinion?”; RL-03 asks “Will you accept these named continuing responsibilities, from when?” A requested transfer alone does not establish an agreed handover. The UK GMC referral guidance emphasizes communicating the purpose of transfer, relevant information and who is responsible. Match the information to the receiving service's requirements.

Close the loop with evidence, not a sent label

The IHI/NPSF 2017 expert-panel referral guide describes a multi-step process involving communication, tracking and accountability.

The following is an original tracking example. Each row asks for evidence of a different event; software may use different labels.

For RL-01, a later fictional consultation could be recorded as attended, with its report received and reviewed. If that report requests an investigation, the investigation needs its own accepted owner and follow-up plan. The referral episode can have a documented consultation outcome while the patient's care remains active; neither “closed” nor “specialist seen” means every recommendation is complete.

Use distinct closure reasons. “Consultation completed and recommendations reconciled” is different from “patient declined after discussion” or “service declined; alternate plan arranged.” If the patient cannot be reached, record the attempts and route the unresolved situation for the agreed clinical review. Do not quietly convert absence of a response into a patient decision.

When teams share responsibility, document the boundaries. The referring clinician's interim care, the coordinator's tracking work and the specialist's accepted tasks should be visible to one another. The patient should have a contact route without becoming the only safeguard against a lost referral. For concise direct communication during escalation, the SBAR examples demonstrate a request followed by the receiver's actual response.

Review the letter against the source

Before approval, make two passes. First, check each claim in the letter against a dated source. Second, work from the source toward the letter and ask what important information disappeared. A letter can contain only accurate sentences and still omit the question, an allergy, a pending result or the person responsible for the next step.

Apply that method to RL-01:

• Supported: Bilateral hand symptoms, the October 21 findings, treatment duration and temporary response, microscopy dates, uncertainty, agreed photograph sharing and the requested opinion.
• Unsupported: A confirmed contact allergy, a negative culture, patch testing already ordered, an unperformed examination or a specialist appointment already booked.
• Important omissions: The work impact, current-versus-completed treatment distinction, the missing culture status, the receipt-check owner or the attachment manifest.

This review is different from spelling correction. The clinical note examples develop the same distinction between supplied evidence and polished but unsupported text.

If you use a template or AI drafting tool, ask it to organize the supplied material while preserving attribution and unknowns. Do not ask it to infer urgency, fabricate a consent discussion or fill missing findings with normal values. After editing, check the exported letter again: the final version can lose a paragraph even when the editor looks correct. Draft generation also does not prove that reports were attached, the referral was delivered or another clinician accepted care.

The practical endpoint is a letter the receiving team can understand and a record the sending team can act on. A specific question, an honest account of what is known, and a named next owner do more work than an impressive-looking page of copied history.