Ask a clinic how their fax triage works and you'll usually get a name. “Oh, Susan handles the faxes.” That answer contains the whole problem. The clinic runs a document-routing system that processes twenty to fifty items a day, touches referrals, results, prescriptions, and legal requests — and the system is one person's judgment, applied item by item, from memory, between phone calls.
Nobody designed it. It accreted. And because it never fails loudly — it fails as a referral that quietly never lands — it never makes it onto anyone's fix list.
What the un-designed system costs
The visible cost is time: one to three MOA hours a day, spent deciding what each document is and where it goes, with the urgent items formatted exactly like the junk. The invisible cost is worse. When triage lives in one person's head, the clinic has a single point of failure with a vacation schedule. When there's no log of what arrived and where it went, there is no way to answer “did we ever get that referral response?” except by searching, calling, and hoping. The patient usually finds out first.
The designed version has four parts
Rules, written down. What are the document types you actually receive, and where does each go? The first pass takes an hour with your MOA and produces the most valuable page of process documentation the clinic owns. If Susan won the lottery tomorrow, this page is the difference between a bad week and a bad quarter.
An owner per item, not per pile.Triage assigns every document to a person with a deadline, instead of leaving a shared pile everyone assumes someone else is watching. “Whoever's free” is not an owner.
A tracking layer for the ones that leave.Outbound referrals need a follow-up date the moment they're sent. A referral without a follow-up date isn't sent — it's released into the wild.
Automation for the mechanical parts. Classifying, filing, naming, assigning, and reminding are exactly what software is for. This layer can run alongside your EMR without touching the patient record — a digital fax line, a small workflow engine, and your existing shared drive and task tools are enough. The judgment stays human; the sorting stops being a career.
Start smaller than you think
The whole rebuild is a one-to-two-week job, but the first step is an afternoon: write the routing rules down, and start a simple log of what arrives. Even that much converts the queue from folklore into a system — visible, teachable, and measurable. Then measure the MOA hours before and after. That number is how you'll know whether the rest was worth it, and it usually is.
— Himanshu, for TOSC · July 2026