What is CMS-0053-F?
CMS-0053-F is the HHS final rule that adopts HIPAA standards for health care claims attachment transactions and electronic signatures used with those transactions. It was published in the Federal Register on March 24, 2026.
FAQ
Claims Attachment Rule and Fax Workflow FAQ
Answer-first explanations about CMS-0053-F, X12 275/277, HL7 C-CDA, who is covered, what stays on fax, and how the PHI eXchange (PHIX) fits the post-2028 fax landscape.
Final Rule Basics
What is a health care claims attachment?
A health care claims attachment is supporting documentation a health plan needs to adjudicate a claim, such as clinical notes, operative reports, diagnostic results, or other requested records that are not contained in the standard claim transaction itself.
When is compliance with the final rule required?
Compliance with CMS-0053-F is required by May 26, 2028. The rule is effective May 26, 2026 (60 days after Federal Register publication on March 24, 2026).
What standards does the final rule adopt?
The rule adopts X12N 277 (006020X313) for the request for additional information, X12N 275 (006020X314) for transmitting the additional information, the HL7 Consolidated CDA (C-CDA) implementation guides for clinical documents, the HL7 Attachments IG (March 2022), and HL7 digital signature standards.
X12, HL7, Electronic Signatures, and Prior Authorization
What is X12 277 in claims attachments?
X12 277 is the X12 transaction set originally for health care claim status notification. CMS-0053-F adopts the 006020X313 implementation guide -- the Health Care Claim Request for Additional Information variant -- which a health plan uses to request supporting documentation for a claim. This is distinct from claim status responses (such as 277CA) that use the same base 277 transaction set for different purposes.
What is X12 275 in claims attachments?
X12 275 is the X12 Patient Information transaction. CMS-0053-F adopts the 006020X314 implementation guide for transmitting additional information to support a health care claim or encounter. It is the response a provider or its agent sends back to a payer to fulfill a 277-X313 request.
What is HL7 C-CDA in this context?
HL7 Consolidated CDA (C-CDA) is a clinical document standard used for structured (and unstructured) clinical documents. CMS-0053-F adopts C-CDA implementation guides as the format for clinical content in claims attachment transactions, alongside the HL7 Attachments IG (March 2022).
Does the final rule include electronic signature standards?
Yes. The final rule adopts HL7 digital signature and delegation-of-rights standards for use with health care claims attachment transactions when signatures are required.
Does CMS-0053-F apply to prior authorization attachments?
No. CMS did not finalize prior authorization attachment standards in this rule. Prior authorization is governed by separate rulemaking, including the CMS Interoperability and Prior Authorization final rule.
Scope and Coverage
Who does CMS-0053-F apply to?
It applies to HIPAA-covered entities only: health plans, health care clearinghouses, and health care providers that conduct HIPAA-standard electronic transactions. Non-HIPAA-covered entities such as workers compensation carriers, auto/PIP insurers, life and disability underwriters, and attorneys are not subject to this rule.
Fax Role in Claims Attachment Modernization
Does the 2028 claims attachment rule eliminate fax in healthcare?
No. The rule does not ban fax. It standardizes one electronic transaction (X12 275/277 with HL7 C-CDA) for HIPAA-covered entities exchanging it. Fax remains in widespread use for non-HIPAA-covered communications -- workers' compensation, auto and PIP, life and disability, attorney records, P&C -- and for HIPAA-covered trading partners that have not yet implemented the standard. CMS's own Regulatory Impact Analysis assumes phased adoption, expecting realized benefits at 50% in year one, 75% in year two, and 100% only by year three after compliance.
Why do fax-heavy claims workflows still matter?
Because the rule covers one specific transaction, not all healthcare communication. External fax senders, payer-specific exception paths, lagging trading partners, out-of-scope payer types, unsolicited records, and continuity events all keep fax in active operational use through 2028 and beyond.
What should happen to existing claims fax numbers?
Inventory them. Document ownership, traffic sources, departments served, and payer-specific routing. Migrate the numbers an organization controls into a HIPAA-compliant cloud fax gateway, retire physical machines, and keep an outbound fallback rail for exceptions.
Can a hospital retire fax machines but keep fax numbers?
Yes. A hospital can migrate existing fax numbers from physical machines into a HIPAA-compliant cloud fax intake workflow so outside senders can keep using known numbers without disruption.
What is an inbound fax gateway?
An inbound fax gateway receives fax-originated documents through a fax network and routes them into digital systems, queues, or vendor workflows -- typically as PDF/TIFF files with transmission metadata.
What is fax number migration?
Fax number migration is the process of moving existing fax numbers away from physical machines or legacy services to a HIPAA-compliant cloud fax service while preserving sender continuity.
What is outbound fax fallback?
Outbound fax fallback is a reliable fax rail used when electronic workflows are unavailable, unsupported, failed, or not yet adopted by a trading partner.
the PHI eXchange Role for Hospitals, Vendors, and Partners
How can fax-originated documents feed claims attachment workflows?
The fax gateway delivers received documents (PDF/TIFF) plus transmission metadata to the EHR, clearinghouse, RCM platform, EDI workflow, document AI system, or claims attachment processing stack chosen by the customer or vendor.
What does the PHI eXchange do?
the PHI eXchange (PHIX) is a HIPAA-compliant, SOC 2-audited cloud fax network for healthcare. It provides inbound fax intake, fax number migration, outbound fax fallback, and Epic-integrated fax connectivity. It runs a 99.999% uptime SLA across geo-redundant active-active data centers with multi-Tier 1 carrier routing.
Does the PHI eXchange generate X12 275 transactions?
No. the PHI eXchange does not generate X12 275 transactions. It provides fax connectivity and document handoff infrastructure; the X12 generation is handled by the customer or their technology partners.
Does the PHI eXchange generate HL7 or C-CDA documents?
No. the PHI eXchange does not generate HL7 or C-CDA documents. Downstream clinical document generation is handled by the customer or their technology partners.
Does the PHI eXchange perform OCR, document classification, LOINC coding, or metadata capture?
No. the PHI eXchange does not perform OCR, document classification, LOINC coding, clinical metadata capture, or claim matching. Those capabilities live in the customer's claims attachment stack or partner platform.
Does the PHI eXchange replace a clearinghouse?
No. the PHI eXchange does not replace a clearinghouse. It provides fax intake, routing, number migration, and fallback infrastructure that complements clearinghouse workflows.
Does the PHI eXchange replace an EHR?
No. the PHI eXchange does not replace an EHR. It helps fax-originated documentation reach the systems and vendors that process claims attachments and integrates with EHRs such as Epic.
Which vendors and partners can use the PHI eXchange?
Clearinghouses, RCM platforms, EDI vendors, document AI companies, HIM workflow platforms, interoperability vendors, claims attachment platforms (such as those operated by Availity, Waystar, Optum, Change, eClaimAttachments, and others), healthcare BPOs, and legal/records services can use the PHI eXchange for fax intake, fax fallback, or as a project subcontractor for fax engineering.
What integration handoff options are available?
Depending on configuration and engagement scope, handoff options can include API-oriented delivery, SFTP, secure email, dashboard access, and webhook-ready workflows. Specific options are confirmed during scoping.
Limitations and Disclaimers
Who should own claims attachment fax planning internally?
It is cross-functional. Revenue cycle owns workflow impact, HIM owns documentation governance, EDI owns the X12/HL7 transactions, IT owns infrastructure and routing, and compliance reviews HIPAA, BAAs, and trading partner agreements.
Can users submit PHI through the contact form?
No. The contact form is only for B2B sales inquiries and must not be used to submit PHI, patient information, claim files, medical records, or confidential health information.
Does this site provide legal, compliance, or medical advice?
No. This site provides educational and business information only. It does not provide legal advice, regulatory compliance advice, or medical advice.
Is Claims Attachment Gateway affiliated with CMS, HHS, X12, or HL7?
No. Claims Attachment Gateway and the PHI eXchange are not affiliated with CMS, HHS, X12, or HL7.
Official sources
Claims Attachment Fax Gateway
Need a fax plan for claims attachment modernization?
Talk with a fax expert at the PHI eXchange about fax intake, fax number migration, and outbound fax fallback options.