Three decades after HIPAA first mandated a standard for electronic claims attachments, we now have CMS-0053-F. This final rule establishes the first-ever national standard for the electronic exchange of clinical documentation supporting claims — finally phasing out the fax. It is projected to save the healthcare industry roughly $781 million annually, and aims to lift significant administrative burden.
And I want to be clear: This is worth celebrating. CMS Administrator Dr. Oz said it memorably in the press release: “The 1980s called, and they want their fax machines back.” It’s a good line. It captures the frustration everyone in healthcare administration feels every day.
But I would be doing healthcare a disservice if I didn’t also say the quiet part out loud: The fax machine was never the problem … at least not all of it. It just symbolizes issues that are perhaps more nuanced than Dr. Oz’s cute tag line implies.
What CMS got right (and what it missed)
A proper standard for document transmission was long overdue, but fax is not the villain. It simply transmits documents from one place to another. The reason healthcare clung to it for so long — through decades of EHR adoption, through HIPAA, through the 21st Century Cures Act, through waves of interoperability mandates — was never because providers loved fax machines. It was because fax was the path of least resistance for transmitting the thing that healthcare actually runs on: unstructured data.
A referral letter. A discharge summary. A stack of clinical records assembled by a billing coordinator. These documents are the lifeblood of the healthcare system and its claims process. They do not emerge as clean, structured data. They are human-generated narratives — rich with clinical nuance and deeply resistant to standardization. Communication built by humans intended for humans to consume.
CMS-0053-F replaces the transmission medium. It basically says, “instead of faxing those documents, wrap them in an XML header, package them in an X12N 275 transaction, and route them electronically through a clearinghouse.” The documents themselves? Still unstructured.
So what has changed? The envelope.
The problem just moved
Under the old fax workflow, the problem was on the receiving end. Say a payer received a fax. A human got it, read it, determined what type of document it was, matched it to the right claim, and handed it to an adjudicator. Manual, slow, and error-prone.
Under the new electronic workflow, the problem is distributed more broadly and in some ways it is more complex.
On the provider side, someone still has to pull the right clinical content from the EHR, assemble it, apply the correct LOINC document type, and generate a C-CDA document with a properly coded header. This might be automated for large health systems with, say, mature Epic or Cerner implementations. But for the independent practices, specialty groups, and community hospitals that make up the majority of the provider landscape, this is a new technical burden with a 24-month clock.
On the payer side, the C-CDA document arriving in an X12 275 transaction now needs to be ingested, parsed, and routed into an adjudication workflow. That means a payer system needs to read an XML header, verify the LOINC code matches the document, validate the C-CDA structure, and then — here is the part nobody is talking about — reconcile a machine-readable wrapper around an unstructured document body. In practice, this can be harder to process programmatically than a human simply reading a fax, because the system is now expected to do something automated with content that was never designed for automation. The XML header creates an expectation of structure that the document inside often cannot fulfill.
The problem was never the medium, it was the work the medium creates
Clinical documentation is unstructured by nature. It reflects the messiness of human illness, the variability of clinical judgment, the idiosyncrasies of human communication, and the diversity of healthcare settings. A discharge summary from a community hospital in rural Ohio does not look like a discharge summary from an academic medical center in Boston. Both are valid. Neither is easily machine-readable without significant processing. The manual work that arrives with every document — regardless of how it was transmitted — is the actual problem. Not the fax machine.
What the healthcare industry has been quietly building toward — and what regulators are circling around but haven’t yet mandated — is not just standardized electronic transmission.
It’s intelligent document processing: The ability to electronically receive a document in any format, recognize what it is, extract the clinically and administratively relevant information from it, match it to the appropriate record, and route it to the right workflow with minimal human intervention.
CMS-0053-F creates conditions for that capability to matter more, not less. The rule mandates that a structured and properly coded C-CDA header accompany every claims attachment identifying the document type. For institutions with systems that cannot generate such headers natively — which is most of the market — something has to do the classification work and assemble the compliant structure. The rule doesn’t expressly mandate intelligent document processing, but it effectively assumes it will underpin healthcare IT infrastructure in the ability to receive a document from any source, infer the correct LOINC document type classification, assemble a compliant C-CDA wrapper, and route it into the appropriate electronic transaction — whether that’s an X12N 275 for claims adjudication, a Direct Secure Message for provider-to-provider communication, or a FHIR document for TEFCA-enabled exchange.
The 24-month compliance window creates necessary urgency. But the celebration should be measured. We are not, as the press release suggests, killing the problem that fax created. We are migrating it into a format that carries a higher expectation of automated processing — without yet having solved the underlying challenge that made automation hard in the first place.
The right response to CMS-0053-F is not to assume that fax’s administrative burden is solved. It is to implement the intelligence layer that finally makes it solvable. The fax machine is going away. The work it created is not — unless we build something to replace it.
Photo: kutubQ, Getty Images
Denis Whelan is the CEO of Documo, a leading provider of cloud fax and Intelligent Document Processing (IDP) solutions for healthcare organizations. With a deep understanding of healthcare workflows and compliance requirements, he helps organizations modernize document processes, reduce administrative burden, and accelerate patient care. Denis is passionate about bridging the gap between legacy systems and modern automation, transforming fax-driven and manual processes into secure, streamlined, and actionable workflows. His work focuses on advancing AI-driven solutions that improve efficiency, reduce errors, and give healthcare organizations greater operational visibility-so care teams can focus on what matters most: delivering better patient outcomes.
This post appears through the MedCity Influencers program. Anyone can publish their perspective on business and innovation in healthcare on MedCity News through MedCity Influencers. Click here to find out how.
