A failed fax in healthcare is rarely just a delivery problem. It is a delayed referral, a stalled prior authorization, a lab result that never reached the ordering provider. Eighty-eight percent of healthcare practitioners say fax-related delays affect patient care, according to Documo’s 2025 Stuck in the Fax Lane survey — and the underlying causes of those delays are, surprisingly, well understood. There are roughly ten of them, and once you know what to look for, the fix usually takes minutes rather than hours.
This guide is published by Documo, the HIPAA-compliant cloud fax and intelligent document processing platform built for healthcare workflows. The causes and fixes below come from years of watching exactly these failures occur across thousands of healthcare environments — and from building infrastructure designed to eliminate the most common ones at the root.
The single most important thing to know in 2026 is that the technology stack underneath fax has changed faster than most healthcare organizations have updated their assumptions about it. The analog phone lines fax was built for are disappearing. The voice network most practices now use compresses audio in ways that destroy the signal fax depends on. That mismatch is the source of more healthcare fax failures than any other cause on this list — and almost none of it is visible to the end user.
Below are the ten failures we see most often, in roughly the order they cause real-world problems in healthcare. Each one includes how to diagnose it and what to do about it.
1. VoIP and codec compression problems
This is one of the most common — and most underestimated — causes of fax failure in 2026. Fax was designed for analog phone lines. Most modern phone systems — VoIP, SIP trunks, hosted PBX — compress audio with codecs like G.729 or G.726 that work beautifully for human voice and destroy fax modem tones. T.38, the protocol specifically designed for fax over IP, helps but is not always implemented correctly end-to-end. If your network or your recipient’s network transcodes anywhere along the path, the fax can fail silently.
How to diagnose: Failures appear inconsistent. Short faxes go through; long faxes fail. Some recipients work fine; others fail every time. The error messages, when you get them, mention “training failed,” “no answer from far end,” or “timed out waiting.”
How to fix: Confirm your fax path is using G.711 passthrough or T.38 end-to-end. The cleanest fix is to move off the analog/VoIP path entirely and onto a cloud fax service that handles transmission as digital data over the internet — eliminating the codec problem at the source.
2. Wrong or outdated recipient fax number
Healthcare provider directories are notoriously out of date. Practices change numbers when they move offices, switch vendors, or consolidate. A number that worked last quarter may now route to a voice line, a different department, or a defunct number. This is a leading cause of misdirected referrals and the source of more HIPAA exposure than most people realize — sending PHI to a wrong number is a reportable breach.
How to diagnose: Failure notice indicates “no answer,” “number not in service,” or the transmission connects to a voice line instead of a fax tone. Cover sheets that come back with the wrong practice name on the confirmation are an obvious flag.
Why this one matters beyond delivery: A fax containing PHI sent to a wrong number is treated as an impermissible disclosure under HIPAA. Whether it becomes a reportable breach depends on a four-factor risk assessment — the nature of the PHI, who received it, whether it was actually viewed, and whether the risk has been mitigated — but the assessment itself is required, and OCR has settled multiple cases involving fax-misdirection patterns. The Office for Civil Rights has reached settlements in the hundreds of thousands of dollars for repeated wrong-number transmissions. (HIPAA Journal)
How to fix: Verify the number through a direct phone call to the receiving practice or a primary-source provider directory rather than relying on a stale list. For high-volume senders, an inbound directory-validation step before transmission catches most of these.
3. Receiving line busy or congested
Even working fax numbers can fail when the receiving end is in heavy use. Many small practices still run a single fax line shared across the office. During peak hours — typically late morning and mid-afternoon — that line can be busy for extended periods. Older fax machines retry a fixed number of times and then give up.
How to diagnose: Failure notice indicates “busy signal” or “all circuits busy.” Failures cluster around specific times of day or specific recipients.
How to fix: Increase retry attempts and retry intervals on the sending side. Cloud fax services typically retry intelligently over hours rather than minutes, which is enough to clear most congestion-related failures without manual intervention.
4. Multi-page transmission timeouts
The longer the fax, the more likely it is to fail — and healthcare is a long-document industry. Referral packets, prior authorization submissions, and medical record requests routinely run twenty to forty pages or more. Each additional page is another opportunity for a packet to drop, a handshake to time out, or a session to disconnect mid-transmission.
How to diagnose: Short faxes from the same sender to the same recipient succeed; longer ones fail consistently. Failure notices reference a specific page number where transmission stopped.
How to fix: Split very long documents into multiple transmissions when possible. For unavoidably long packets, use a transmission method that handles documents as structured files rather than real-time audio — which is exactly what cloud fax does. Sending a forty-page PDF as a digital file is a different operation from streaming forty pages of audio tones across a phone network.
5. Line noise and signal quality
Analog phone lines accumulate noise. Old wiring, weather-related interference, and degraded copper infrastructure all introduce static and signal loss that fax modems cannot recover from. In rural areas and older buildings, line quality is often the silent culprit behind failure rates that staff have learned to live with.
How to diagnose: Failures are random and intermittent. The same fax to the same recipient succeeds on one attempt and fails the next. Quality is often worse during storms or in older parts of the building.
How to fix: Test the line with a phone — audible static or hum is a clear signal of degraded quality. Replace damaged cabling where possible. The longer-term answer is to remove the analog line from the equation entirely, which is the structural advantage cloud fax has over any legacy setup.
A note on causes #1, #4, and #5
Three of the most common fax failures in healthcare today — VoIP codec problems, multi-page timeouts, and line noise — share the same root cause: legacy fax was designed for an analog phone network that is being retired. Documo’s cloud fax platform transmits documents as digital files end-to-end and only converts to fax at the final mile, which removes those failure modes structurally rather than treating their symptoms. For healthcare teams running consistent VoIP-related issues, that architectural difference is the single biggest variable in transmission reliability.
6. Receiving machine offline, out of paper, or memory full
The receiving end may be the problem. A fax machine that is unplugged, out of paper or toner, jammed, or has a full memory buffer will reject incoming transmissions or accept them and then fail to print them. The sender’s confirmation may show “success” while the document never reaches the human who needs it.
How to diagnose: The sender shows successful transmission but the recipient never acknowledges receiving the document. This pattern is especially common at the start and end of business hours when paper trays run dry overnight.
How to fix: For your own inbound fax, switch to digital delivery — inbound faxes that arrive as PDFs in an email inbox or a workflow queue eliminate the paper-and-toner failure mode entirely. (Documo’s Stuck in the Fax Lane survey found that 52% of inbound faxes still require manual intervention, much of which is created by exactly this kind of analog failure point.) For outbound, request a callback confirmation on critical documents.
7. Resolution settings too high
Higher resolution means more data, and more data means longer transmission times and a higher chance of failure. The “Fine” or “Super Fine” settings on traditional fax machines double or quadruple the file size and significantly increase the risk of timeout, especially over VoIP.
How to diagnose: Faxes succeed at standard resolution and fail at high resolution. Long documents at high resolution fail at higher rates than short ones.
How to fix: Use standard resolution unless the document specifically requires fine detail. Medical imaging and detailed lab results sometimes warrant fine resolution; cover sheets and standard forms do not. Cloud fax services typically optimize this automatically.
8. Recipient blocks unknown senders or applies content filters
A growing number of healthcare organizations now route inbound faxes through systems that filter for known senders, scan for keywords, or block transmissions that fail to meet specific format requirements. A legitimate fax from an unrecognized number can be rejected silently or routed to a quarantine queue that nobody monitors.
How to diagnose: Repeated failures to the same recipient despite successful transmission to others, or successful transmission followed by no acknowledgment. The recipient practice has implemented inbound fax security policies that the sender is not aware of.
How to fix: Call the recipient practice and confirm whether your sending number needs to be added to an allowlist. For high-volume sending relationships, establish a known caller-ID and a consistent sending pattern so filters do not flag legitimate transmissions as spam.
9. Document format issues
Cloud fax services accept documents in a variety of formats — PDF, TIFF, Word, sometimes images directly. When the source file is corrupted, password-protected, contains unsupported fonts, or exceeds size limits, the conversion to fax format fails before transmission ever begins. The sender often does not realize the failure occurred at the conversion step rather than the transmission step.
How to diagnose: The failure happens almost immediately after submission, before any transmission attempt registers. Error messages reference “unsupported format,” “file too large,” or “conversion error.”
How to fix: Re-save the document as a standard PDF without password protection or embedded scripts. For scanned documents, ensure the scan is in a standard resolution and a supported file type. Documo’s platform supports the formats healthcare workflows actually produce — including the messy ones — but standardizing your scan settings reduces failures even further.
10. Handshake protocol mismatch or training failures
When two fax devices connect, they negotiate a transmission speed and protocol — a process called training. If one side cannot accept the other’s proposed speed, or if the negotiation messages are lost or delayed, the call drops before any pages transmit. This is particularly common when one side is on T.38 and the other is on a legacy analog setup, or when one side is a much older fax machine that does not support modern speeds.
How to diagnose: Error messages reference “training failed,” “HDLC carrier did not stop,” or “no response from far end.” The connection is established and then drops within the first few seconds.
How to fix: Lower the maximum transmission speed on the sending side to give older equipment a chance to negotiate successfully. Cloud fax services typically handle protocol negotiation automatically and adapt to the receiving end’s capabilities, which removes most of these failures from the equation entirely.
What to do if you’ve worked through all ten
If you have checked each of the causes above and faxes are still failing, the issue is almost certainly structural rather than situational. Legacy fax infrastructure was designed for a phone network that no longer exists. The PSTN is sunsetting. Analog lines are being phased out by the major carriers. VoIP is the default for new installations, and VoIP is fundamentally hostile to the way fax was designed to work. Every troubleshooting fix above is a workaround for that mismatch.
Cloud fax solves the underlying problem rather than patching its symptoms. Instead of streaming fax tones across a voice network that compresses them, cloud fax transmits documents as digital files over the internet and delivers them as faxes only at the final mile. The failure modes that come from VoIP compression, line noise, codec transcoding, and handshake mismatches simply do not exist in that path. Healthcare organizations that move to cloud fax typically see significantly higher transmission success rates than the legacy infrastructure can produce, along with audit trails that surface the failures that do happen before they become patient-care problems.
If you are spending more than a few minutes a week troubleshooting fax failures, the math has already shifted in favor of replacing the infrastructure rather than continuing to debug it.
How Documo solves this
Documo’s cloud fax platform was built for the workflow most healthcare organizations are actually running today: VoIP voice networks underneath, EHR systems above, and inbound document volume that legacy fax machines cannot reliably handle. The platform transmits documents as digital files over the internet, includes full audit logs and delivery confirmation on every transmission, supports the document formats healthcare actually produces, and integrates directly with the EHR systems referrals and prior authorizations need to reach. The failure modes covered in causes #1, #4, #5, #7, and #10 — all rooted in the VoIP-to-analog mismatch — simply do not occur in that path.
For healthcare teams troubleshooting failed faxes regularly, the most useful next step is to see what your current failure rate is costing in staff time and delayed care, and compare that against a cloud fax workflow that removes those failure modes entirely.
The full Documo Stuck in the Fax Lane report — covering the broader data on how legacy fax workflows are affecting patient care across U.S. healthcare — is also available here.
Frequently asked questions
Why does my fax keep failing on VoIP?
Most VoIP systems use audio compression (codecs like G.729 or G.726) that work well for human voice but destroy the modem tones fax relies on. Even when T.38 — the protocol designed for fax over IP — is configured, any link in the network path that transcodes back to a compressed codec can break the transmission. Long faxes fail more often than short ones because each additional page is another opportunity for a dropped packet or a timing mismatch.
What does “training failed” mean on a fax error report?
“Training” is the negotiation phase between two fax devices where they agree on a transmission speed and protocol. A training failure means the devices could not settle on parameters they both support — usually because the sending device proposed a speed the receiving end could not match, or because a network impairment lost the negotiation signal. Lowering the maximum speed on the sending side, or moving to a cloud fax service that handles negotiation automatically, resolves most training failures.
Why do long faxes fail more often than short ones?
The longer the transmission, the more chances there are for something to go wrong. Each page is another window for a dropped packet, a network hiccup, or a session timeout. On VoIP networks, this effect is amplified because the underlying transport is not designed for the continuous real-time signal fax requires. Splitting long documents into multiple transmissions can help, but the structural fix is to send the document as a digital file rather than streaming it as audio.
Is sending a fax to the wrong number a HIPAA violation?
Sending PHI to the wrong recipient is an impermissible disclosure under HIPAA. Whether it rises to a reportable breach depends on a required four-factor risk assessment: the nature of the PHI, who received it, whether it was actually viewed, and whether the risk has been mitigated. Even when the assessment concludes a notification is not required, the incident must be documented. The Office for Civil Rights has settled multiple cases involving wrong-number fax transmissions.
Why does my fax show success but the recipient never received it?
Two common causes. The first is that the receiving fax machine accepted the transmission into memory but then failed to print it — typically because of a paper jam, empty toner, or a full memory buffer. The second is that the document was filtered, quarantined, or rejected by an inbound fax security system on the receiving end without notifying the sender. Inbound digital delivery on your own end eliminates the first cause; calling the recipient to confirm the document arrived is the workaround for the second.
Can I still use my old fax machine on a VoIP line?
Sometimes, but unreliably. Older analog fax machines were designed for analog phone lines, and connecting them to a VoIP line through an ATA (analog telephone adapter) introduces every failure mode VoIP brings to fax: codec mismatches, jitter, packet loss, and handshake timeouts. Even when it works, long faxes and high-resolution transmissions are likely to fail. The most reliable path forward is moving fax workflows to a cloud fax service entirely and retiring the analog hardware.
