Quick answer: Healthcare keeps faxing because fax is the one channel every clinic, lab, and payer already accepts. In 2026, federal rules are pushing health data toward standardized electronic exchange, and that does not kill the fax. It raises the bar for it. An open source fax server gives you faxing that is auditable, encryptable, self-hosted, and tied into your own systems through an API, so you can keep talking to the fax-only world while you modernize everything behind it. ICTFax runs on FreeSWITCH and ICTCore with T.38, which keeps the protected data on hardware you control.
People have predicted the death of the fax for twenty years. It has not happened, because fax solves a stubborn problem: it is the lowest common denominator that every healthcare counterparty already supports. A small clinic with no integration budget can still receive a referral. That is why fax volume in healthcare stays high even as the rest of the stack moves on.
What is changing in 2026 is the regulatory pressure to standardize how clinical documents move electronically. Rather than making fax obsolete, that shift makes the quality of your fax infrastructure matter more. This is where an open source fax server earns its place.
What the 2026 Standardization Push Means
Federal regulators have adopted the first standardized formats for electronic health-care claims attachments, with a multi-year window for the industry to comply. The goal is to replace ad hoc document exchange with structured, predictable transactions. Most organizations will run a hybrid for years: standardized electronic exchange where both sides support it, and fax everywhere else.
That hybrid is the whole point. You cannot drop fax until every counterparty has moved, and they will not all move at once. So the practical question is not “fax or electronic.” It is “how do I run a fax channel that is secure, logged, and connected to my systems while the transition plays out.”
Why Open Source Fits This Moment
A self-hosted open source fax server gives you three things the standardization push rewards: control over where protected data lives, an API to wire fax into your own workflows, and a transparent codebase you can audit. ICTFax was built around exactly that.
The data stays on your infrastructure
When you self-host, faxes carrying protected health information never pass through a third party’s cloud. The server, the database, and the stored documents all sit on hardware you control, which makes the security picture far simpler to reason about and to document for an audit.
An API turns fax into a workflow step
ICTFax exposes a REST API and supports email-to-fax and fax-to-email. That means a fax stops being a manual chore and becomes a step your other systems can trigger and track. A referral comes in as a fax, gets routed to the right inbox automatically, and the event is logged like any other transaction.
Transparency you can audit
Open source means you, or your security team, can read exactly how the software handles documents and connections. There is no vendor black box between you and the protected data, which is a real advantage when you have to demonstrate how the system works.
Related reading:
HIPAA compliant fax server · Email to fax, the open source way · Open source fax API
Frequently Asked Questions
Is fax going away in healthcare?
Not soon. The 2026 push standardizes electronic exchange where both sides support it, but fax remains the fallback that every counterparty accepts. Most organizations will run both for years, which is why fax quality and security still matter.
What is T.38 and why does it matter?
T.38 is the standard for sending faxes reliably over IP networks. It handles the timing and error correction that fax needs, so a fax sent over a modern SIP trunk arrives intact. ICTFax uses T.38 with SpanDSP for this.
Why choose an open source fax server over a cloud fax service?
Self-hosting keeps protected data on your own infrastructure, gives you an API to integrate fax into your workflows, and lets you audit the code. A cloud service puts your documents on someone else’s servers and hides the implementation.
Is ICTFax built on Asterisk or FreeSWITCH?
ICTFax runs on FreeSWITCH with the ICTCore framework and SpanDSP. That stack handles the fax media and signaling while the web interface and API manage documents, routing, and multi-tenant accounts.
Can ICTFax handle high volume across departments?
Yes. It is multi-tenant, so separate departments or client organizations get isolated fax queues and accounts on a single install, each with its own routing and logging.
Get Started
Want to stand up a self-hosted fax server that fits a modernizing stack? Open a support ticket and we will help you plan the deployment.