Write down the minimum contents of every outgoing referral: tooth number with notation, urgency tier, the specific clinical question, current imaging, health history with med list, and insurance details. Print it, tape it at the front desk, and refuse to send a referral that's missing a line.
Kill the CD burner. Export the original DICOM or radiograph and transfer it office-to-office before the patient calls — Send handles multi-gigabyte CBCT zips free, encrypted end to end, and the receiving office needs no account. The patient should never be the courier.
Set up Bridge with the three offices you refer to most — two minutes at app.intake.dental/chat, free, BAA included. Send referrals with attachments in the thread, and agree on one rule: the op report comes back in the same thread, every case.
Walk through a typical referral. Your assistant faxes a one-page form to the oral surgeon. The patient leaves with a paper slip and instructions to "call this number." The pano goes along as a printout, or on a CD the patient loses in their car. Then: silence. Nobody at your office knows whether the patient scheduled. The surgeon's front desk gets a cold call from a patient who can't pronounce the procedure, with no imaging, no health history, and no insurance details on file. Weeks later you chart "referred out — status unknown," which is a polite way of writing "we lost this one." You find out at the next recall that the third molars are still there — or you find out from an ER report. Both offices lost production. The patient lost time. And the referral relationship earned nothing.
A referral that closes carries everything the receiving office needs to triage and schedule in one pass. The tooth, in a notation both sides read the same way — Universal-vs-FDI mixups are real when a chart crosses borders or software. The urgency: today, this week, or routine, stated explicitly instead of implied by handwriting pressure. The clinical question: "evaluate #17 for extraction, root proximity to the IAN canal," not "eval wisdom teeth." The actual imaging — a diagnostic-quality DICOM or the original radiograph, not a phone photo of a monitor. Health history and med list, so anticoagulants and bisphosphonates surface before the consult, not during it. Insurance details, so the specialist's team can verify eligibility before the patient even calls. When the packet is complete, the specialist can triage in minutes and schedule the patient while they're still motivated. Incomplete packets sit in trays.
Here's where most digital referrals quietly die: file size. A CBCT export from a Carestream, Planmeca, or Sirona unit runs from a few hundred megabytes to a couple of gigabytes zipped. Email tops out around 25 MB, so offices fall back to burned CDs, patient-carried USB drives, or consumer file-sharing accounts nobody signed a BAA for. Send (send.intake.dental) exists for exactly this and it's free: end-to-end encrypted transfer where the decryption key travels in the link itself and never touches our servers. The receiving office clicks a link — no account, no portal login, no plugin. It handles full CBCT DICOM zips, STL/PLY/OBJ files from iTero, 3Shape TRIOS, or Medit scanners, clinical photos, and PDFs. The surgeon opens the actual volume, not a screenshot of one. That alone upgrades most phone referrals into real ones.
Send the surgeon's office a complete packet before the patient calls: tooth number, urgency, the clinical question, current imaging in diagnostic quality, health history, and insurance details. Then give the patient the office's name and number, and follow up if you haven't seen a scheduled date within a week. A referral without imaging or a clear question usually stalls at the specialist's front desk.
Patient demographics and insurance, the tooth or area with notation specified, the reason for referral phrased as a clinical question, urgency, relevant health history and medications, and the imaging itself — attached, not "available on request." If the specialist has to call you back for basics, the letter didn't do its job.
Export the DICOM from your unit, zip it, and use an encrypted transfer service — CBCT files run hundreds of megabytes to gigabytes, far past email's ~25 MB cap. Send (send.intake.dental) is free, end-to-end encrypted, and the receiving office just clicks a link with no account. Skip burned CDs and consumer file-sharing accounts without a BAA.
Standard email is risky: most practice email isn't encrypted end to end, and attachments with PHI can sit unprotected on multiple servers. You need either an encrypted email service under a BAA or, better, a purpose-built encrypted transfer where you control access. Free tools exist for this, so there's no economic excuse for emailing a pano to a Gmail address.
It's software that replaces fax-and-phone referrals with a structured digital handoff: the tooth, urgency, and clinical question in writing, the imaging attached, and secure messaging between the two offices so the report makes it back to the referring doctor. Bridge covers the connection for free — a colleague network of dental offices plus case chat with x-ray, DICOM, and STL attachments — so the referral, the follow-up questions, and the op report live in one thread instead of a fax queue.
Secure chat between dental offices with case threads, x-ray/DICOM/STL attachments, automatic translation, and a BAA at signup. Two-minute setup, works on any op computer, and the op report comes back to the thread it started in.
A referral isn't done when the patient leaves your office. It's done when the report is in your chart. Bridge — our free secure chat for dental offices — gives both practices a shared case thread instead of a fax trail. You post the referral with the x-rays, DICOM, or STL attached. The surgeon's team asks their follow-up question in the thread instead of playing phone tag with your front desk. After surgery, the op report lands in the same thread, so "status unknown" disappears from your charting. Everything is encrypted at rest, audit-logged, and covered by a BAA at signup — and messages auto-translate between languages, which matters when your treatment coordinator and their scheduler don't share a first language. It runs in a browser on any op computer, and setup takes about two minutes. Specialists notice which GPs send complete packets. Those GPs get the referrals back.
Usually because the patient is left to make the call themselves with no context, and neither office tracks the handoff. Missing imaging forces a second records request, insurance questions delay scheduling, and by the time it's sorted the patient's motivation is gone. Referrals that arrive complete and get scheduled quickly are the ones that convert.
Traditionally by mailed or faxed letter weeks after treatment — which is why so many GP charts say "referred out, no report." A shared secure thread fixes this: the op report is posted to the same case conversation the referral started in, so it reaches the referring doctor the day it's written, with the imaging attached.
I've been on both sides of the referral fax machine: the GP who never hears back, and the specialist squinting at a photocopied pano. Most referral leakage isn't clinical — it's logistics. Missing tooth numbers, missing imaging, and a patient left to make the phone call alone. Here's the referral process that actually closes.
