CMS wants to move parts of healthcare off the fax machine and onto FHIR-based APIs, with targets pointed at around October 1, 2027. That’s real, and it’s worth planning for. But roughly 75% of medical communication still travels by fax today, and CMS itself keeps fax as a controlled backup channel. Your fax server software isn’t going anywhere for years.
What CMS actually proposed
The signal here is the prior authorization push, including the CMS-0062-P proposed rule covering prior authorization for drugs. The comment window on that proposal closed on June 15, 2026, and the implementation targets land around October 1, 2027. The direction is clear: CMS wants payers and providers to exchange certain data through standardized FHIR APIs instead of faxes and portals.
Read carefully, though, and this is a phased shift for specific workflows, not a switch that turns fax off across healthcare. Prior authorization is one slice of clinical communication. Referrals, records requests, lab orders, pharmacy exchanges, and a long tail of partner-to-partner documents still ride on fax, and nothing in the proposal makes those disappear on a deadline.
Why 75% of healthcare still faxes
Fax persists in medicine for boring, durable reasons. It’s a legal record. It works between any two organizations without shared software. It doesn’t depend on both sides having modernized their systems. And it’s trusted by staff who’ve relied on it for decades. Those aren’t nostalgic habits, they’re the reasons fax survived every prior attempt to kill it.
FHIR adoption also isn’t uniform. A large hospital network may stand up API exchange quickly, while a small specialty clinic, a rural provider, or a records vendor takes years. Until both ends of every exchange are on FHIR, fax is the interoperability fallback that actually reaches everyone. You can’t API to a partner who isn’t there yet.
- Legal and records value: faxes create a defensible paper trail for audits and disputes.
- Universal reach: any provider with a fax number can receive a document, no integration required.
- Partner readiness gaps: many organizations won’t have FHIR endpoints ready by 2027.
- Regulatory backup: CMS keeps fax as a controlled secondary channel even as APIs roll out.
Modern fax server software is not the old machine
The fax that’s dying is the standalone machine and the analog line. What replaces it isn’t FHIR alone, it’s server-based faxing that lives on your network and inside your workflows. Modern fax server software handles transmission digitally, keeps audit logs, and connects to email and clinical systems, so it fits a HIPAA program instead of fighting it.
ICTFax is fax server software built for that reality, running on the same FreeSWITCH and ICTCore engine with HIPAA-capable features: secure transmission, audit logs, and access controls. It supports email-to-fax, T.38 for clean IP transport, and multi-tenant separation for groups that need it. In practice, choosing HIPAA compliant fax software is less about the fax standard and more about how the server is configured and operated. If you want the specifics on what makes server faxing meet the standard, see the guide on what makes a fax server HIPAA compliant.
How to plan for the transition without panic
Treat 2027 as a milestone, not a deadline to abandon fax. The smart move is to run both channels in parallel: build FHIR exchange for the partners and workflows that support it, and keep a modern fax server for everyone else. As adoption climbs, your fax volume drifts down on its own, and you retire lines only when the traffic genuinely dries up.
A capable fax server makes that graceful. Digital transmission, email integration, and clean audit logs mean fax stops being a liability and becomes a controlled fallback you can defend in an audit. If you’re still framing your policies, the primer on what HIPAA fax means is a useful starting point.
Frequently Asked Questions
Is CMS actually banning fax in 2027?
No. CMS is steering specific workflows like prior authorization toward FHIR APIs, with targets around October 1, 2027. It isn’t banning fax across healthcare, and it keeps fax as a controlled secondary channel. Most clinical communication will still involve fax well past that date.
Should we stop investing in fax server software now?
No. With roughly 75% of medical communication still on fax and uneven FHIR adoption, you’ll need reliable faxing for years. A modern fax server is a bridge during the transition, not a sunk cost. Retire it when the traffic disappears, not before.
What makes ICTFax suitable during this shift?
ICTFax offers HIPAA-capable features like secure transmission, audit logs, and access controls, plus email-to-fax, T.38, and multi-tenant support. That lets you keep serving fax-only partners while your FHIR capability grows alongside it.
Will FHIR and fax have to coexist?
Yes, for a long stretch. Not every partner will have FHIR endpoints ready by 2027, and legal and records use cases keep fax relevant. Running both channels side by side is the realistic operating model through the late 2020s.
Does fax still count as a compliant channel?
It can, when it runs on properly configured fax server software with encryption, access controls, and audit logging. The compliance comes from how you deploy and operate the system, not from the fax standard itself.
If you want fax that stays dependable while the rest of healthcare shifts to APIs, take a look at ICTFax fax server software and plan a transition that keeps every partner reachable.