Healthcare still runs on fax because a fax number is the one address almost every clinic, hospital, lab, pharmacy and payer shares. Electronic exchange works well inside one network or one EHR, but between unaffiliated organizations the fax line is still the channel both sides know will be answered, so referrals, results and records keep arriving that way.
Why does fax still count as a trusted channel for patient records?
Fax still counts as a trusted channel for patient records because it is simple, universal and leaves a paper-like trail. A sender dials a number, the receiver gets an image of the signed page, and both machines log the transmission. No account, no portal login and no shared software is needed on either side.
That simplicity matters most between strangers. A primary care office that refers a patient to a specialist across town may have no shared EHR, no exchange agreement and no portal access with that practice. Both offices do have a fax number printed on their letterhead. The fax is the lowest common denominator, and in a hand-off between two organizations that have never worked together, the lowest common denominator wins.
The HIPAA Privacy Rule does not forbid the hand-off itself. Under 45 CFR 164.506 on uses and disclosures for treatment, payment and operations, a covered entity "may disclose protected health information for treatment activities of a health care provider." The rule says nothing about which channel to use. What it does require, in the safeguards standard at 45 CFR 164.530(c), is "appropriate administrative, technical, and physical safeguards to protect the privacy of protected health information," whatever form that information takes.
One definition in the HIPAA rules also touches fax directly. The definitions section at 45 CFR 160.103 says that certain transmissions, "including of paper, via facsimile," are not considered transmissions via electronic media "if the information being exchanged did not exist in electronic form immediately before the transmission." That is a narrow technical point about paper pages, not a statement that fax is safe. A fax that lands in a digital inbox is saved as a file on a computer, and the same definition lists hard drives and other storage material as electronic media. The HIPAA and PHI category covers what the rules ask of each transmission method in more depth.
Signatures are the other reason. Many orders, certifications and consent pages need a wet or visible signature, and a fax carries the image of that signature intact. A structured data message carries values, not a picture of a signed form, so the receiving side often asks for the signed page by fax even when the data itself has already arrived another way.
Healthcare hand-offs that still travel by fax
The healthcare hand-offs that still travel by fax are the ones that cross organizational lines: referrals between unaffiliated practices, orders sent to outside labs and suppliers, results returned to the ordering clinic, records requests, prior authorization paperwork with payers, and discharge papers sent from a hospital to a patient's own doctor.
The table below lists the common ones. The "why it cannot be pulled" column describes the usual situation between organizations that do not share a system; a practice with a direct electronic connection to a partner may not see some of these by fax at all.
| Hand-off | Usual sender | Usual receiver | Why the receiver cannot pull it electronically |
|---|---|---|---|
| Specialist referral | Primary care office | Specialist practice | No shared EHR or exchange agreement between the two practices |
| Consult note back to the referrer | Specialist practice | Primary care office | The specialist's system has no address for the referrer's inbox |
| Outside lab result | Reference lab or hospital lab | Ordering clinic | The clinic has no interface with that lab |
| Hospital discharge summary | Hospital | Patient's primary care office | The hospital does not know which system the office uses |
| Prior authorization request and reply | Clinic and health plan | Health plan and clinic | The plan accepts several channels and the clinic has no API connection |
| Records request and response | Another practice, attorney or insurer | Medical records staff | The requester is not connected to any exchange network |
| Refill request | Pharmacy | Prescriber's office | The pharmacy's message did not reach an electronic prescribing inbox |
| Home health or equipment orders for signature | Home health agency or supplier | Ordering provider | The agency needs a signed page back, not just data |
Each row has the same shape: two organizations, no shared pipe, and a fax number both sides already have. That pattern explains most of what shows up in a clinic's inbox on a given morning.
The prior authorization row is changing for some payers. The CMS Interoperability and Prior Authorization final rule fact sheet says impacted payers, such as Medicare Advantage organizations and state Medicaid and CHIP fee-for-service programs, must implement a Prior Authorization API starting January 1, 2027. The same fact sheet notes that denial decisions "may be communicated via portal, fax, email, mail, or phone," so fax stays on the list of channels a payer may use.
Interoperability gaps that keep the healthcare fax machine running
Interoperability gaps keep the healthcare fax machine running because electronic exchange is strongest inside one network and weakest between organizations that never set up a connection. Two practices on different EHRs, a small lab without an interface, or a payer outside a clinic's portal list all fall back to the one channel they share.
The federal answer to this gap is a national framework rather than a single network. The ASTP/ONC page on the Trusted Exchange Framework and Common Agreement (TEFCA) describes it as "a nationwide framework for health information sharing" built as a network of networks. The same page says it aims to remove "the need to join multiple networks or create one-off, point-to-point connections." That goal is a fair description of the problem fax solves today: without a common framework, every new partner is a one-off connection, and a fax number needs no setup at all.
Several practical gaps sit underneath the policy picture:
- Addressing. A sending system needs to know where to deliver a record. A fax number is printed on every referral form and website. An electronic address for the same office is often unknown or out of date.
- Partial adoption. A hospital may exchange records electronically with large practices and still fax the small ones, because each connection has to be set up on both ends.
- Document types without a standard message. Signed orders, handwritten forms and scanned outside records do not map neatly to a structured message, so they travel as images.
- Fallback habits. When an electronic send fails or the receiver cannot confirm it arrived, staff resend by fax because they know it will land somewhere.
Direct secure messaging is the most common electronic alternative clinics hear about, and it has its own adoption story. The comparison post explains why Direct addresses have not replaced the clinic fax number and where Direct beats fax for referrals.
What fax volume costs a clinic front office
Fax volume costs a clinic front office staff time: someone has to open each fax, work out what it is and who it belongs to, attach it to the right chart and route it. The cost scales with pages and with how hard each page is to identify, not with how many fax machines the clinic owns.
No national figure fits every clinic, so the useful number is your own. The worked example below uses made-up inputs for a fictional four-provider clinic. Replace each value with a count from your own inbox.
| Input (example values) | Value |
|---|---|
| Faxes received per working day | 60 |
| Average minutes to identify, index and route one fax | 3 |
| Minutes spent per day | 180 (60 × 3) |
| Working days per week | 5 |
| Hours per week | 15 (180 × 5 ÷ 60) |
In this example, fax handling takes 15 staff hours a week, close to two working days. The figure leaves out the slow cases: an illegible page that needs a call to the sender, a fax filed to the wrong patient that has to be found and moved, or a missing page that delays a referral appointment.
To get your own baseline, count faxes for two normal weeks and time a sample of 20 of them from opening to filed. That gives you pages per day and minutes per fax, which is all the arithmetic needs. The automation post walks through a fuller calculation in its section on fax automation ROI for clinics, with a worked calculation, including the costs that are easy to leave out.
The time is not spread evenly. Mornings after a weekend, the days after a hospital discharge run and the start of a new referral partnership all spike the inbox. A daily routine that sorts by urgency rather than arrival order keeps those spikes from burying the pages that need action first, which is what the guide to triaging a clinic fax inbox lays out.
Is healthcare fax going away any time soon?
Healthcare fax is unlikely to disappear soon because it falls only when every sender a clinic depends on has a working electronic path to that clinic. A single practice can modernize its own systems, but it cannot make its outside labs, hospitals, payers and referral partners switch on the same day.
Several things would have to be true before fax volume falls in a given office:
- Most senders can reach you electronically. That means a known address on a network your EHR uses, for each hospital, lab and referral partner that faxes you today.
- Signed documents have an accepted electronic form. Orders and certifications that need a signature would need an electronic signature process both sides accept.
- Payers you work with offer an electronic channel for each step. The CMS rule moves some payers toward a Prior Authorization API from 2027, but it covers named payer types, not every plan.
- Fallback no longer means fax. When an electronic message fails, the sender's habit has to be a retry on the same channel, not a resend by fax.
None of these is under one clinic's control. That is why fax volume tends to fall slowly and unevenly: a large hospital partner may switch to electronic exchange while a dozen small senders keep faxing. Expect a mixed inbox for years, with fax and electronic channels arriving side by side.
When replacing the clinic fax number is the wrong goal
Replacing the clinic fax number is the wrong goal when your senders are not ready to stop using it. Turning off a fax line that partners still dial means lost referrals and missing results. A better target is handling inbound fax well: sorted by type, attached to the right chart and routed to the right person quickly.
A clinic that waits for fax to go away still has to process every page that arrives in the meantime. The practical work is on the receiving side:
- Sort by type and urgency. A critical result and a junk advertisement should never wait in the same queue in arrival order.
- Match each fax to a patient before it is filed. A page on the wrong chart is worse than a page not yet filed.
- Route by document type. Referrals go to the referral coordinator, results go to the ordering provider, refill requests go to the prescription queue.
- Keep a person on the uncertain pages. Handwritten orders and faint scans need human eyes, whatever software sits in front of them.
The step-by-step guide to processing medical faxes automatically covers how those receiving-side stages fit together and where a reviewer stays involved.
Many faxed pages are document types that can be turned into data once they are in the inbox. Schema Care does not take faxes in, but it reads lab reports, discharge summaries, prescriptions and intake forms into fields with a confidence score each, and the list of document types it reads shows the fields it returns for every one.
Fax is also a target for unwanted traffic, such as advertisements, which adds to the sorting load even though the FCC rule at 47 CFR 64.1200 on unsolicited fax advertisements restricts them. The classification post covers how to give junk and other odd faxes their own class so they leave the queue fast.