Claims Attachment Gateway Powered by the PHI eXchange

Claims Attachment Fax Gateway · powered by the PHI eXchange

Yes, CMS is moving claims attachments off fax. Here is what stays.

CMS-0053-F is real, the May 26, 2028 deadline is real, and standardized X12 275/277 attachments are coming. They cover one transaction, between HIPAA-covered entities, when both sides are ready. Everything else still runs on fax. The Claims Attachment Fax Gateway, powered by the PHI eXchange, keeps that fax layer reliable, HIPAA-compliant, and routed into your modern claims stack.

  • Inbound fax gateway for claims-related document workflows
  • Fax number migration without losing external senders
  • Outbound fax fallback when electronic workflows are unavailable
Talk to a Fax Expert Read the 2028 Claims Attachment Guide
Fax-originated documents Outside senders & legacy numbers
HIPAA-compliant fax network Intake, routing, audit trail
Your claims stack EHR · clearinghouse · RCM · document AI

The fax network behind some of healthcare’s most demanding workflows

99.999%Uptime SLA
SOC 2Third-party audited
HIPAABAA-backed by default
Geo-redundantActive-active data centers
Multi-carrierTier 1 intelligent routing
Epic-integratedSend/receive from inside the EHR
BillionsOf faxes handled annually
Zero retentionDocuments purged after delivery

Answer-First

What CMS-0053-F actually does — and what it does not do.

What changes by May 26, 2028

  • Health plans and providers exchanging claim attachments must use X12N 275 (006020X314) and X12N 277 (006020X313) where applicable.
  • HL7 C-CDA implementation guides become the standard for clinical document attachments.
  • Electronic signature standards apply to those transactions.
  • Applies to HIPAA-covered entities only: health plans, clearinghouses, and HIPAA-transacting providers.

What does not change

  • Fax is not banned. The rule standardizes the electronic transaction, not the medium of every healthcare communication.
  • Workers’ compensation, auto/PIP, life and disability, attorney record requests, and P&C are out of scope and stay on fax.
  • Trading partners that have not implemented X12 275/277 will continue to fax during transition.
  • Prior authorization attachments are not finalized in this rule.

The honest summary: CMS standardized one transaction. Healthcare fax volume gets smaller. It does not go to zero by 2028 — and the surface area that remains has to stay reliable, audited, and HIPAA-compliant.

Where the PHI eXchange Fits

We are the fax network layer. Your stack handles the rest.

The Claims Attachment Fax Gateway routes fax-originated documentation into the systems and vendors that process claims attachments — without trying to replace them.

1 Fax-originated documentation Claims records, notes, and external documentation received by fax
2 the PHI eXchange fax network HIPAA-compliant intake, routing, number migration, audit trail
3 PDF/TIFF + metadata + audit trail Transmission-level information for intake and handoff
4 Your claims attachment stack EHR, clearinghouse, RCM, EDI, document AI, claims attachment workflow

We do not generate X12 or HL7 transactions, perform OCR, classify documents, code LOINC, match claims, or replace EHRs and clearinghouses. We do the part we are best in the world at: healthcare fax.

Three Offerings

Inbound intake, number migration, and outbound fallback.

Inbound Fax Gateway

Receive fax-originated claims documentation through a HIPAA-compliant healthcare fax network and route it into your processing platform, document workflow, or claims attachment stack.

Fax Number Migration

Retire the machine, keep the number. Route existing claims-related fax numbers into modern digital workflows without disrupting outside parties who still send by fax.

Outbound Fax Fallback

When electronic attachment workflows are unavailable, unsupported, or fail, the PHI eXchange provides reliable outbound fax fallback with transmission history and delivery tracking.

Built for Healthcare Organizations

Your X12 plan still needs a fax number plan, an exception plan, and a continuity plan.

Hospitals and health systems trust the PHI eXchange to run the fax connectivity layer that complements their EDI team, clearinghouse, RCM platform, and EHR — not compete with them.

Hospitals & Health Systems

Retire claims fax machines without losing fax connectivity.

Map existing claims-related fax numbers, identify high-volume external senders, and migrate fax intake into a HIPAA-compliant gateway that feeds your modern workflow.

  • Inventory and migrate claims fax numbers
  • Route fax-originated documents into your EHR, RCM, or vendor stack
  • Maintain reliable outbound fax fallback for exceptions
  • Keep transmission-level audit trail through the 2028 transition
Healthcare Organization Playbook

Other Audiences

Building a product or selling to hospitals?

If you are a vendor embedding fax into your platform, or a partner who wants to bring the PHI eXchange in as the fax expert on customer projects, start here.

Free Resource

2028 Claims Attachment Fax Readiness Checklist

A practical worksheet for inventorying claims-related fax numbers, identifying non-HIPAA-covered fax traffic that will not move, and mapping the fax intake plan that has to live alongside X12 275/277.

Get the Readiness Checklist See All Resources

FAQ Preview

Short answers for claims attachment fax planning.

Does the 2028 CMS-0053-F rule eliminate fax in healthcare?

No. CMS-0053-F adopts standards for the electronic claims attachment transaction (X12 275/277 with HL7 C-CDA) and applies only to HIPAA-covered entities exchanging that specific transaction. Fax remains in widespread use for workers' compensation, auto and PIP, life and disability underwriting, attorney records requests, property and casualty claims, payer trading partners that have not yet implemented the standard, unsolicited records, and exception workflows. CMS's own Regulatory Impact Analysis assumes some providers and vendors will continue manual processes during the transition.

Who does CMS-0053-F apply to?

The rule applies to HIPAA-covered entities: health plans, health care clearinghouses, and health care providers that conduct HIPAA-standard electronic transactions. Workers' compensation carriers, auto/PIP insurers, life and disability carriers, attorneys, and other non-HIPAA-covered parties are out of scope and continue to rely on fax for medical records exchange.

What does the PHI eXchange do?

the PHI eXchange (PHIX) is a HIPAA-compliant, SOC 2 cloud fax network for healthcare. We provide inbound fax intake, fax number migration, outbound fax fallback, and Epic-integrated fax connectivity. We do not generate X12 or HL7 transactions, perform OCR, classify documents, or replace clearinghouses or EHRs. We are the fax network layer behind your modern claims attachment stack.

Why work with a fax expert instead of a generic cloud fax provider?

Healthcare fax has higher stakes than generic fax: BAAs, HIPAA technical safeguards, transmission auditability, EHR integration, and uptime that hospital revenue cycle teams can rely on through 2028 and beyond. the PHI eXchange runs a 99.999% uptime SLA, geo-redundant active-active data centers, multi-Tier 1 carrier routing, and a team of healthcare-fax engineers who have spent careers on this problem.

Read the Full FAQ

Claims Attachment Fax Gateway

Talk to a fax expert about your 2028 claims attachment plan.

Discuss fax intake, number migration, and outbound fax fallback for your hospital, health system, or healthtech platform.

Talk to a Fax Expert Read the 2028 Claims Attachment Guide