Referral leakage occurs when a patient who has been referred for care never arrives at the intended provider and instead receives treatment at a competing facility. In the United States, healthcare industry analyses estimate that hospitals lose roughly $150 billion annually due to referral leakage and incomplete referral workflows. (The Hidden Impact of Referral Revenue Leakage)
Research published in JAMA Network Open and the Journal of General Internal Medicine shows that referral completion rates are often far lower than expected. In large health systems, a substantial share of specialist referrals are never scheduled or never completed, creating financial loss for providers and delays in care for patients. (Gaps in the Outpatient Referral Cascade; Closing the Referral Loop)
One overlooked driver of referral leakage is document intake latency.
Many hospitals still rely on cloud fax systems to receive patient records, referral forms, and clinical documentation. However, most cloud fax platforms deliver documents using a batch model, meaning the receiving system cannot access any pages until the entire fax transmission has finished.
A large patient history or referral packet can take 30 to 50 minutes to arrive as a complete document. During that time, admissions teams cannot verify insurance, confirm patient eligibility, or contact the referring provider.
The result is a narrow but critical operational gap. A competing facility that can begin reviewing the referral immediately may accept the patient first.
Fax Streaming on Fax.Plus solves this problem by delivering each fax page in real time as it is decoded, allowing healthcare teams to start processing referrals the moment the first page arrives.
Related reading What Is Fax Streaming? Real-Time Fax Page Delivery with Fax.Plus →Referral leakage happens when a referred patient ends up receiving care at a competing or out-of-network facility instead of the intended provider. The financial consequences are documented across healthcare industry research.
These numbers are not theoretical. They reflect the daily operational reality inside hospitals, behavioral health facilities, and specialty clinics across the country.
A surprising portion of that revenue leakage is caused not by clinical issues, but by document processing latency.
Digital fax solved many problems created by analog machines. Reliability improved. Documents became searchable. Audit trails became possible.
However, most cloud fax systems still operate using a batch delivery model.
In this architecture, a multi-page fax is transmitted page by page, but the receiving system receives nothing until the final page has finished transmitting.
For short documents, the delay may be small. For large referral packets containing discharge summaries, lab reports, insurance documents, and intake notes, the delay can easily reach 30 to 50 minutes.
During that entire time:
Meanwhile, another facility with faster document intake can begin reviewing the referral immediately.
By the time the batch completes on your system, the patient may already be admitted elsewhere.
Fax Streaming is a feature available through the Fax.Plus API that removes this batching delay entirely. Instead of waiting for the entire document, the system delivers each page individually the moment it is decoded.
When Fax Streaming is enabled, the API triggers a webhook event called fax_page_received every time a single page is decoded, rather than waiting for the fax session to finish.
The webhook payload includes:
Each page can be downloaded immediately as a single-page TIFF file through the Fax.Plus API. While the remaining pages are still transmitting, your application can already process the first page.
A fax in progress carries the status in_progress, which allows applications to retrieve partial files during transmission. This event-driven webhook architecture is what differentiates Fax Streaming from traditional polling-based fax APIs.
Full technical reference: Fax API documentation · Webhook documentation.
A behavioral health facility processing 20,000 fax pages per month may receive more than 10,000 inbound referral pages from hospitals requesting immediate placement decisions.
In behavioral health and emergency medicine, placement speed directly affects referral capture. Hospitals often require an answer within minutes. If an admissions team cannot review the referral immediately, the patient may be placed elsewhere.
With Fax Streaming, the workflow changes:
Emergency departments and behavioral health intake teams were among the first healthcare groups to request this capability.
Some cloud fax vendors gate real-time document visibility behind premium enterprise add-ons. In practice, this means a hospital cannot see the first page of an incoming fax until the entire document finishes transmitting, unless an expensive feature bundle is purchased.
For organizations processing tens of thousands of fax pages each month, this pricing model can significantly increase operational costs.
Fax.Plus takes a different approach. Fax Streaming is included in Enterprise accounts, not sold as an additional upgrade. Enterprise plans can be customized for high-volume healthcare environments without requiring additional automation bundles simply to access real-time fax visibility.
Speed is irrelevant in healthcare if security is compromised. Every page delivered through Fax Streaming is protected by the same infrastructure used across the Fax.Plus platform:
Alohi is headquartered in Geneva, Switzerland, and operates under the Swiss Federal Data Protection Act (FADP), with 20+ data residency locations globally. Full details in the Alohi Trust Center.
Fax Streaming is especially valuable for organizations where:
Outside healthcare, the same architecture is valuable in legal document review, financial services, and insurance claims processing.
Fax Streaming is available as an on-demand feature within the Fax.Plus platform. Once enabled, every account with an assigned fax number automatically receives streaming page events.
Developers can configure webhook endpoints to receive fax_page_received events and retrieve individual pages through the Fax.Plus API. Full reference: webhook docs · fax object docs.
Enterprise teams evaluating a migration can contact the Alohi sales team to review volume requirements, BAA availability, and integration options.
Healthcare has accepted fax latency as an unavoidable operational constraint for decades. The technology to eliminate that delay already exists.
For organizations competing for time-sensitive referrals, real-time Fax Streaming can determine whether the patient arrives at your facility or somewhere else.
And it should not cost extra to see the first page of an incoming fax.
Fax streaming delivers each page of an incoming fax individually and in real time, rather than waiting for the complete document to finish transmitting. This allows admissions teams to begin triage on page one while the rest of the document continues to arrive.
Referral leakage occurs when a competing facility accepts a patient faster because their team had the information first. With fax streaming, intake coordinators receive patient demographics on page one and can begin insurance verification immediately, closing that window of vulnerability.
Yes. The Fax.Plus fax streaming API is fully HIPAA compliant. PHI is encrypted with AES-256 at rest and TLS 1.2+ in transit. PHI is also omitted from webhook payloads entirely. BAAs are available for all covered entities.
U.S. hospitals collectively lose an estimated $150 billion per year to referral leakage. (The Hidden Impact of Referral Revenue Leakage) Research covering 247,000+ referral cases found that only 54.1% of referrals are ever completed. (Gaps in the Outpatient Referral Cascade)
fax_page_received is a Fax.Plus API webhook event that fires the moment a single fax page is decoded, before the full session is complete. It enables applications to process incoming fax pages in real time without polling, and is the technical foundation of the Fax Streaming feature.

