Prior Authorization Automation Requires More Than Just a New Interface

Prior authorization remains one of the most visible, widespread, administratively frustrating, and costly challenges in the U.S. healthcare system. Prior authorization, defined as the process by which payers determine the medical necessity of specific procedures before allowing clinicians to provide the service, is estimated to account for $35 billion of U.S. healthcare administrative spending. ^1,2

Providers experience it as delay, rework, and uncertainty. Health plans experience it as a high-volume process that must balance coverage requirements, medical necessity, policy compliance, and cost stewardship. Patients experience it most directly: According to the American Medical Association (AMA), 94% of patients experience delays in care, and 78% abandon treatment altogether. ³

The healthcare industry is rightly focusing on prior authorization reform. The growing attention is long overdue. Streamlining automation, reducing the burden of manual work, improving timeliness, and supporting more predictable workflows are shared goals across payers, healthcare providers, policymakers, technology vendors, and standards organizations.

But meaningful prior authorization automation will require more than promoting one technology format over another. The real question is not whether the industry needs modernization. It does. The more important question is how to modernize in a way that builds on what is already implemented, scales across the healthcare system, and addresses the operational barriers across the broader ecosystem that continue to keep prior authorization stuck in portals, phone calls, faxes, and manual follow-up.

X12’s 278 Standard is Already Implemented

As the industry evaluates new approaches to prior authorization, it is important to start with the facts.

The 005010 version of the X12 implementation guide for Healthcare Services Review Request for Review and Response, is the HIPAA-mandated transaction used for defined prior authorization business usages. X12 recommends the guide’s newly updated 008060 version for adoption.

Available industry data shows meaningful X12 transaction volume. Clearinghouses are processing more than 7 million X12 transactions per month, or more than 83 million per year. These figures do not reflect all clearinghouses in the healthcare ecosystem, which means they should not be interpreted as the full universe of transaction activity. Even with that caveat, the numbers demonstrate that this X12 transaction standard is moving substantial volume today. ⁴

The DataSpring CAQH Index, a trusted industry benchmark for administrative transaction adoption and cost savings, shows measurable prior authorization automation through the X12 standard. In the 2024 Index data, 95 million authorizations were fully electronic using X12 transactions, representing 35% of the volume. Another 123 million were partially electronic, representing 43% of volume. Fully manual authorizations dropped to 54 million, and automation helped the industry avoid $966 million in costs. ⁵

Notably, the 2025 Index data shows even greater acceptance. Fully electronic X12 authorizations increased to 102 million, representing 38% of volume. Partially electronic authorizations increased to 126 million, representing 46% of volume. Fully manual authorizations dropped to 44 million, and automation-related cost avoidance increased to $1.2 billion.

Those figures do not suggest that prior authorization automation is complete. Far from it. They show there is still significant room for improvement. But they also show that the X12 prior authorization is widely and actively used to support efficient and effective payer-provider administrative exchange, processing millions of transactions — and growing.

Mature Does Not Mean Stagnant

A common misconception in technology policy discussions is that a mature standard is somehow outdated simply because it is not new. In healthcare administrative exchange, maturity is not a weakness. It is often what empowers adoption at scale.

The business of healthcare is conducted through a complex network of health plans, providers, clearinghouses, vendors, intermediaries, and technology systems. Standards used across this environment must support repeatable, reliable exchange at national scale. They must also evolve as business requirements, regulations, and implementation needs change.

Satisfied organizations that have already invested in X12 electronic prior authorization workflows should not be asked to abandon functioning infrastructure simply because a newer format is gaining policy attention. At the same time, the industry should continue to identify where adoption can improve, where implementation guidance can be strengthened, and where complementary technologies can help reduce the burden.

Modernization should not require choosing between practical progress and existing standards. The industry can recognize the value of newer API-based approaches, which are important and valuable, while also acknowledging the real-world role of X12 standards, their proven use cases, and even the possibility of hybrid approaches.

It is also important to challenge the assumption that a new API approach, by itself, even using X12 standards will solve current problems associated with prior authorization. If the underlying authorization policies and rules for different service lines, network cohorts, programs, and more are not clear, structured, computable, and consistently available, the industry will still face friction.

A different syntax does not automatically resolve uncertainty about whether authorization is required, what documentation must be submitted, what criteria apply, or how a response should be interpreted and acted upon. The hard work of prior authorization automation is not only technical. It is operational.

To automate prior authorization effectively, the industry needs standards and technology. But technology alone cannot make unclear requirements clear, inconsistent rules and data consistent, or unavailable information computable.

Prior authorization needs accessible data, consistent implementation, clear documentation requirements, aligned operating rules, and a practical path for organizations that vary widely in technical readiness.

The work to standardize policies and rules is independent of, and should not be confused with, the role that proven transaction standards play in supporting the process.

Parallel Approaches Can Add Complexity

Healthcare rarely has the luxury of replacing one process with another overnight. During transitions, organizations often support multiple workflows simultaneously. In some cases, that flexibility is necessary.

However, replacing functioning electronic workflows and starting over with a single new format deemed incompatible would undermine prior investments, snowballing into unnecessary cost, complexity, and disruption across the healthcare ecosystem — and especially for organizations that rely heavily on X12-based automation.

If one trading partner requires one format and another requires a different format, all participating stakeholders may need to support both. That can create more translation, more mapping, more testing, more maintenance, and certainly much more administrative and operational burdens, including overhead. It may also add friction for organizations that have already implemented electronic workflows and now must support additional pathways to accommodate varying partner requirements.

This does not mean the industry should avoid innovation. It means modernization should be practical, coordinated, and grounded in resolving operational realities that close gaps for all parties involved. The goal should be to reduce administrative burden, not shift or multiply it.

The Bigger Automation Question

From X12’s perspective, the barrier is not always the absence of a transaction standard. In many cases, the larger barrier is the availability and consistency of the information needed to automate the process.

For automation to work effectively, systems need to know when prior authorization is required, what information and documentation must be included to make decisions, what criteria determine approval, and how responses should be returned and acted upon. If those requirements vary widely or are difficult to access in structured form, even the best technology will struggle to deliver fully automated results.

That is why prior authorization reform must look beyond format alone. It must focus on the full administrative workflow.

A successful national approach should ask:

• What standards are already implemented?
• Where is adoption growing?
• Where do manual processes remain?
• What operating rules or implementation support are needed?
• What are some better uses of existing data (e.g., the DataSpring CAQH Index) to inform policy?
• How can payer requirements become clearer, more structured, and more consistently available?
• How can the industry modernize without imposing unnecessary cost on organizations that have already automated parts of the process?

These and other questions will help determine whether prior authorization reform produces measurable improvements for patients, providers, and health plans.

Build on Existing Standards to Forge a Constructive Path Forward

The national focus on prior authorization reform is welcome and overdue. Patients should not wait unnecessarily for needed care. Providers should not be forced into avoidable manual work. Health plans should be able to administer requirements efficiently and consistently. Policymakers should expect measurable progress.

Rather than “throwing out the baby with the bathwater” and starting over, progress could begin with a clear view of what is already working, where adoption is gaining traction, and what barriers need to be addressed.

Documented transaction usage confirms that the mandated X12 278 transaction standard is actively used for prior authorization request and response workflows. Industry data shows meaningful electronic volume, year-over-year growth, and substantial cost avoidance. At the same time, the data reveals that there is more work to do.

X12 supports practical administrative simplification grounded in implemented, proven standards, reliable data, scalable adoption, and collaboration among all parties.

Prior authorization automation requires technology. It also requires clear rules, coordinated approaches, consistent and practical implementation, operational alignment, policy transparency, and a willingness to build on what already exists and works.

Ensuring those pieces are in place will support efficient and effective prior authorization processing, regardless of the transaction standard used to facilitate the exchange.

Cathy Sheppard, X12 CEO

Citations

1. Sahni NR, Carrus B, Cutler DM. Administrative simplification and the potential for saving a quarter-trillion dollars in healthcare. JAMA. 2021;326(17):1677–1678. 10.1001/jama.2021.17315 [DOI] [PubMed] [Google Scholar]
2. Sahni NR, Mishra P, Carrus B, Cutler DM. Administrative simplification: how to save a quarter-trillion dollars in US Healthcare. McKinsey & Company; 2021. Accessed July 14, 2024. https://www.mckinsey.com/industries/healthcare/how-we-help-clients/center-for-us-healthcare-improvement
3. Pickern JS. Prior authorizations and the adverse impact on continuity of care. Am J Manag Care. 2025 Apr;31(4):163-165. doi: 10.37765/ajmc.2025.89721. PMID: 40227395. [DOI] [PubMed]   
4. X12, “Basis of a Statement on Use of the 278,” X12 Update / WEDI Conference, May 2026; X12 Prior Authorization Blog Project Overview, May 22, 2026.
5. CAQH CORE, 2024 CAQH CORE Index, as cited in X12, “Basis of a Statement on Use of the 278,” X12 Update / WEDI Conference, May 2026. See also DataSpring, powered by CAQH, The 2025 Index Report, https://www.dataspring.com/advisory-services/index-report, and Erin Weber, “The Path Forward for Prior Authorization Reform,” July 2, 2025, https://www.dataspring.com/blog/the-path-forward-for-prior-authorization-reform