The referral log: sent, seen, note received
Summary
Track every referral through three states — sent, seen, note received — in a single log, whether that's your EHR's referral module or a plain spreadsheet. A referral that's only 'sent' isn't documented care coordination, it's an open question. Set a default follow-up window, usually a few weeks, past which an unreturned consult note triggers a call to the specialist's office rather than sitting quietly in the chart as an assumed completion.
By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.
Three states, one log: sent, seen, note received
A referral closes when three things are true and documented: you sent it, the patient was seen, and you have the consult note in hand. Track those three states explicitly, in one place, rather than inferring the loop closed because enough time has passed or because the patient hasn't complained.
A spreadsheet with five columns — patient, specialist, date sent, date seen, date note received — does the job for most solo practices; an EHR referral module does the same thing with less manual entry if yours has one. What matters is that "sent" and "closed" are visibly different states in whatever you're using, so a referral can't quietly sit in the sent column for months without anyone noticing.
Why an open loop is a real risk, not paperwork
An unreturned referral is a genuine care gap, not an administrative loose end — the patient may not have gone, may have been seen and had a finding you never learned about, or the specialist's office may have simply lost the fax. Any of those outcomes looks the same from your side of the log: silence.
The liability exposure runs in the direction you'd expect: a referral you sent and then never followed up on reads, in a chart review, exactly like a referral you never sent. Documenting that you tracked and escalated a nonresponsive referral is what actually distinguishes the two, and it only exists if you built the tracking step into your workflow deliberately.
Building the log as its own template
Treat the referral log the same way you'd approach template craft for a note: a structured field for each of the three states, with a date, rather than a free-text line you'd have to reread to reconstruct the timeline. A well-built log answers "is this referral still open" in one glance, without requiring you to open the patient's full chart.
If your EHR supports it, build the log as one of your standard templates rather than a side spreadsheet — a referral tracked inside the chart is visible to anyone, including a covering colleague, who opens that patient's record, where a standalone spreadsheet is only visible to whoever remembers it exists.
Getting the note back: what's changed and what hasn't
Electronic exchange has made it easier for a specialist's note to reach you automatically rather than requiring a phone call or fax follow-up — TEFCA now establishes a national floor for network-to-network exchange between participating systems, which is closing more loops passively than it used to 1Ref 1Office of the National Coordinator / ASTP (2026).TEFCA — Office of the National Coordinator for Health Information Technology.Establishes that TEFCA creates a national floor for network-to-network exchange, supporting why consult notes increasingly return electronically without manual chasing..
That infrastructure doesn't close every loop by itself. The information-blocking rule treats the specialist as an actor obligated not to interfere with sharing your patient's information back to you, and treats you the same way in reverse 2Ref 2Office of the National Coordinator / ASTP (2026).Information Blocking.Establishes that both the referring and receiving clinician are actors obligated not to interfere with sharing the consult note, framing why a missing note is a process gap rather than a permitted default., but a rule against blocking access isn't a guarantee the note arrives unprompted. Confirm whether your EHR is actually connected to a health information exchange or TEFCA-participating network before assuming a missing note means the specialist is sitting on it; sometimes it means the two systems were never actually talking.
The escalation timeline
Set a default follow-up window and hold to it consistently rather than deciding case by case — a common convention is a call to the specialist's office if no note has arrived within a few weeks of the scheduled appointment, followed by a second call and a note in the patient's own chart if a month passes with still nothing.
Urgent referrals need a shorter window than routine ones; a referral for a same-week symptom that produces no note within two weeks deserves a call well before the routine-referral clock would trigger one. Whatever window you set, write it down as a practice policy rather than relying on memory to flag which referrals are overdue.
Documenting the loop once it closes
Once the note arrives, your job isn't finished at filing it — record-keeping guidelines expect the consult's findings to actually inform the ongoing plan, not just sit in the chart as an attachment 3Ref 3American Psychological Association (2007).Record Keeping Guidelines.Supports that a received consult note is expected to actually inform the ongoing documented plan, not just be filed.. A note that sits unread in the chart is functionally the same as a note that never arrived; the loop isn't closed until you've actually acted on what it says.
Update the problem list with anything the specialist found, and note in your own next entry that you reviewed the consult and what it changed about the plan — that's what makes the closed loop part of the defensible note rather than just a filed PDF. Occasionally the note comes back through the patient instead of the specialist's office; treat patient-supplied paper the same way you'd treat an electronic consult note, reviewed and summarized into your own documentation, not just scanned in. If the note itself carries a signature question, for instance an unsigned consult from a covering associate, the same authentication expectations that apply to your own notes apply to what you're relying on here 4Ref 4Centers for Medicare & Medicaid Services (2023).Complying with Medicare Signature Requirements.Supports that authentication expectations apply to a relied-upon consult note the same way they apply to the referring clinician's own documentation..
If the log itself lives in a vendor's referral-tracking tool
A dedicated referral-management add-on or a third-party care-coordination platform handling PHI on your behalf is a business associate under HIPAA the same as any other vendor touching the chart, which means a signed agreement needs to exist before patient data starts flowing through it 5Ref 5HHS Office for Civil Rights (2026).Business Associates.Establishes that a third-party referral-tracking platform handling PHI is a business associate requiring a signed agreement before use..
Before adopting one, check whether it actually integrates with your EHR's own audit logs and referral records or creates a second system you'll have to reconcile against the first — a referral tool that duplicates rather than replaces your existing tracking adds a second place a loop can quietly stay open. If interoperability with your core EHR isn't contractually guaranteed, that's exactly the kind of data-access term ONC's EHR-contracting guide recommends negotiating before you sign 6Ref 6Office of the National Coordinator (2016).EHR Contracts Untangled: Selecting Wisely, Negotiating Terms, and Understanding the Fine Print.Supports negotiating interoperability/data-access terms before signing a referral-tracking or EHR vendor contract.. Ask the vendor directly how a referral record moves between the two systems, and what happens to your tracking history if you ever switch tools — a log you can't export is a log you'll eventually have to rebuild from memory.
Common questions
Run your practice on Gale
The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.
Start or manage a practice →References
- 1.Office of the National Coordinator / ASTP (2026). TEFCA — Office of the National Coordinator for Health Information Technology. HealthIT.gov. link ✓Establishes that TEFCA creates a national floor for network-to-network exchange, supporting why consult notes increasingly return electronically without manual chasing.
- 2.Office of the National Coordinator / ASTP (2026). Information Blocking. HealthIT.gov. link ✓Establishes that both the referring and receiving clinician are actors obligated not to interfere with sharing the consult note, framing why a missing note is a process gap rather than a permitted default.
- 3.American Psychological Association (2007). Record Keeping Guidelines. American Psychological Association. link ✓Supports that a received consult note is expected to actually inform the ongoing documented plan, not just be filed.
- 4.Centers for Medicare & Medicaid Services (2023). Complying with Medicare Signature Requirements. CMS Medicare Learning Network (MLN905364). link ✓Supports that authentication expectations apply to a relied-upon consult note the same way they apply to the referring clinician's own documentation.
- 5.HHS Office for Civil Rights (2026). Business Associates. U.S. Department of Health and Human Services. linkEstablishes that a third-party referral-tracking platform handling PHI is a business associate requiring a signed agreement before use.
- 6.Office of the National Coordinator (2016). EHR Contracts Untangled: Selecting Wisely, Negotiating Terms, and Understanding the Fine Print. HealthIT.gov (ONC). link ✓Supports negotiating interoperability/data-access terms before signing a referral-tracking or EHR vendor contract.
https://www.gale.care/for-providers/cde-closing-referral-loops · 6 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.