Yes, open source fax servers still matter in 2026, and in healthcare they matter more than ever. Fax refuses to die because every clinic, lab, and payer still accepts it. Self-hosting an open source fax server software stack lets you carry protected health information over T.38 FoIP on your own network, keep it out of a vendor’s hands, and audit every line of the path.

Fax has been declared dead for two decades. It keeps working anyway. When you need to send a referral to a specialist or a claim to an insurer, fax is the one channel that always lands. So the real question is not whether to fax, but how to run it in a way that respects modern privacy rules and modern infrastructure.

Why fax refuses to leave healthcare

Healthcare runs on a shared expectation: everyone accepts a fax. A hospital can send records to a rural clinic, a lab can push results to a physician, and a billing team can reach any payer, all without asking whether the other side supports some new API. That universal reach is why fax outlived the technologies meant to replace it.

Regulation reinforces the habit. Fax has a long, understood compliance story, and switching a whole industry to something else is slow. So instead of fighting the format, the smart move is to modernize how the fax actually travels. That is where fax over IP comes in.

What T.38 FoIP actually changes

Old fax needed a physical phone line and a modem screeching down copper. T.38, often called Fax over IP or FoIP, carries that same fax session across a SIP connection instead. The fax image gets packaged for IP networks in a way that tolerates the timing quirks that would normally break a fax mid-page.

Run T.38 over SIP and you get pure FoIP. No analog board, no dedicated copper line, no modem card to babysit. An analog PSTN line stays available as an optional fallback for the rare carrier that still wants it, but it is no longer the backbone. The diagram below shows how a fax moves from a sender through the server and out over IP.

ICTFax speaks T.38 for clean IP faxing and falls back to G.711 audio-based fax when a route needs it. Because it is built on the FreeSWITCH media engine, the fax session gets the same mature signaling and media handling that carries voice traffic at scale.

Self-hosting keeps PHI inside your walls

Here is the privacy math that pushes hospitals toward self-hosting. Every time protected health information leaves your network for a cloud fax vendor, that vendor now holds your patients’ data. You need a signed business associate agreement, and you are trusting their staff, their controls, and their breach history with records you are legally responsible for.

Self-host the fax server and that trust boundary shrinks. The PHI stays on servers you own, inside a network you audit, protected by keys you hold. No third party sits in the middle of a patient record on its way to a referral. The comparison below makes the difference concrete.

Fewer parties touching the data means fewer places it can leak and a smaller compliance surface to defend. For a security or privacy officer, that is the whole point.

Why open source wins for regulated fax

Closed cloud fax hands you a black box. You cannot read the code, you cannot see exactly how the data is stored, and you cannot change behavior to fit your policy. Open source flips all of that.

With an open source fax server software stack you can audit the code path a fax takes, encrypt storage and transport to your own standard, and wire faxing into your EHR or claims system through the API instead of a manual dance. You are not waiting on a vendor’s roadmap to add the integration you need. You build it, or your team does, on software you can inspect.

ICTFax supports email-to-fax, web-to-fax, T.38 and G.711, and a REST API, so the pieces you need to embed fax into a clinical workflow are already there. You can read the email-to-fax and fax-to-email setup or wire it straight into your own apps through the fax REST API.

Self-hosted open source vs third-party cloud fax

Factor	Self-hosted open source fax	Third-party cloud fax
Where PHI lives	Your own network	The vendor’s cloud
External BAA	Not required	Required with every vendor
Code and audit	Fully inspectable	Closed black box
Encryption keys	You hold them	Vendor holds them
Integration	Open REST API, build what you need	Limited to vendor features
Transport	T.38 FoIP, analog optional	Vendor decides

Putting an open source fax server into production

A working self-hosted setup comes down to a few decisions. Pick SIP trunks that support T.38 so your faxes ride IP end to end. Decide whether you want inbound faxes to arrive as email or land in a queue your systems poll through the API. Set retention and encryption to match your compliance policy, since now you own that choice instead of accepting a vendor default.

ICTFax covers the common front doors: web-to-fax for staff who send from a browser, email-to-fax for the ones who live in their inbox, and the REST API for anything automated. FoIP and ATA device support are documented on the FoIP and ATA page if you still have a physical fax machine to bridge. AI-assisted features are on the roadmap and coming soon, but the core faxing you need today is already shipping.

If you want a hand planning a self-hosted rollout, open a ticket at service.ictinnovations.com and the team can walk through it with you.

Frequently asked questions

Is fax really still used in healthcare in 2026?

Yes, widely. Fax remains the common denominator that every clinic, lab, and payer accepts, so it stays the reliable way to move referrals, results, and claims. The format persists even as the transport underneath it moves to IP.

What is the difference between T.38 and G.711 fax?

T.38 is a fax-specific protocol that carries the fax session over IP and handles network timing gracefully. G.711 sends fax as regular audio, which works but is more fragile on lossy links. ICTFax supports both and prefers T.38 for clean IP faxing.

Do I still need an analog phone line for FoIP?

Usually no. With T.38 over SIP your faxing runs fully on IP. An analog PSTN line is only an optional fallback for the rare carrier or endpoint that still requires copper.

How does self-hosting help with HIPAA and PHI?

Self-hosting keeps protected health information on servers you own instead of sending it to an outside vendor. That removes the need for an external business associate agreement for the fax path and keeps the data inside your own audit and access controls.

Can I connect an open source fax server to my other systems?

Yes. That is a core reason to pick open source. ICTFax exposes a REST API plus email-to-fax and web-to-fax, so you can wire faxing into an EHR, a claims system, or any internal app without waiting on a vendor.

Related resources

Want to run fax on your own terms? Explore the open source fax server at ictfax.org.

Open-Source Fax Servers in 2026: Self-Hosting PHI over T.38 FoIP