Prior authorization has long been one of the biggest administrative headaches in healthcare. Surveys consistently show that over 90 percent of physicians say PA delays patient care, and nearly 30 percent say those delays have led to serious adverse events.
That is changing. CMS issued a final rule (CMS-0057-F) in January 2024 requiring major payers to implement electronic prior authorization APIs. For providers, this means faster decisions, less manual work, and more visibility into the process.
This guide explains what the rule requires, what it means for your Connecticut practice, and how to position your office to take full advantage of it.
Prior authorization denials costing you time and revenue? ConnecticutMed Bill handles PA submissions and follow-up for providers across CT. Get a free consultation at connecticutmedbill.com.
What Is a Prior Authorization API?
An API, application programming interface, is software that lets two systems talk to each other directly. A prior authorization API allows your electronic health record (EHR) or practice management system to communicate with a payer’s system without manual portal logins, faxes, or phone calls.
With a PA API in place, your staff can:
- Check whether prior authorization is required for a specific service
- Identify what documentation the payer needs
- Submit the PA request electronically from within the EHR
- Track the status in real time
- Receive the decision directly in the practice management system
The goal is to move PA from a fax-and-phone process into an automated, real-time workflow, reducing administrative cost and cutting wait times for patients.
CMS-0057-F: What the Rule Requires
Who Is Affected
The rule applies to federally regulated payers, including:
- Medicare Advantage organizations
- Medicaid fee-for-service programs
- Medicaid managed care plans
- Children’s Health Insurance Program (CHIP) managed care entities
- Qualified Health Plan issuers on the Federally Facilitated Exchanges
Traditional Medicare fee-for-service is not covered by this rule. Commercial plans not on federal exchanges are also not directly impacted, though the industry expects these standards to spread over time.
The Four APIs Payers Must Implement
By January 1, 2027, impacted payers must implement and maintain four APIs:
- Patient Access API, Gives patients electronic access to their claims, clinical data, and prior authorization information
- Provider Access API, Allows in-network providers to retrieve patient data, including claims and PA status, directly from their EHR
- Payer-to-Payer API, Enables data sharing when a patient switches plans or has dual coverage
- Prior Authorization API, The core of the rule: allows providers to determine PA requirements, submit requests, and receive decisions electronically
New Decision Timeframe Requirements
Effective January 1, 2026, before the API deadline, payers must meet faster turnaround times:
- Standard (non-urgent) requests: decision within 7 calendar days
- Expedited (urgent) requests: decision within 72 hours
This is a meaningful reduction from previous timelines. Payers must also provide specific, actionable reasons for any denial, not just generic codes.
Public Reporting of PA Metrics
Starting March 31, 2026, impacted payers must publicly post prior authorization metrics for calendar year 2025. Required data includes approval and denial rates, appeal outcomes, average decision times, and the volume of PA requests by service type.
For providers, this is significant. You will be able to compare payers on their PA performance, and use that data when negotiating contracts or managing patient expectations about access to care.
What This Means for Your Connecticut Practice
Faster Decisions on Routine Cases
Once payers implement the Prior Authorization API, routine PA requests that meet clinical criteria can be processed automatically, often in real time. Services with clear, established coverage criteria (imaging, certain specialist referrals, standard DME) are candidates for near-instant approval.
Complex cases, new therapies, high-cost procedures, specialty drugs, will still require clinical review. But even those follow the new 72-hour or 7-day timelines.
Less Time on the Phone and Portal
Your staff spends hours each week on PA work: checking requirements, filling out forms, uploading clinical notes, calling to follow up. When your EHR integrates with payer APIs, much of that becomes automated.
The Coverage Requirements Discovery API, one component of the PA framework, tells your system in real time whether a PA is needed before you even schedule the patient. That alone can eliminate dozens of retroactive PA surprises per month.
MIPS Incentives for Electronic PA Adoption
CMS added a new electronic prior authorization measure to the MIPS Promoting Interoperability performance category. Eligible clinicians who attest to submitting at least one electronic PA using a FHIR-based API through their certified EHR will receive credit toward their MIPS score starting in 2027, affecting the 2029 payment year.
If your practice participates in MIPS, electronic PA adoption becomes both a patient care improvement and a financial incentive.
FHIR: The Technical Standard Behind the APIs
All four APIs under CMS-0057-F are built on HL7 FHIR, Fast Healthcare Interoperability Resources. FHIR is a modern, web-based data standard that makes health data more portable and readable across systems.
You do not need to be a developer to use these APIs. Your EHR or practice management vendor will build FHIR connectivity into their platform. Your job is to make sure you are using an EHR that is certified for electronic prior authorization and that you have activated the payer connections available in your system.
Ask your EHR vendor directly: which payers do you currently have Prior Authorization API connections with, and what is your roadmap for January 2027 compliance?
The WISeR Model: An Additional PA Change Affecting Some Providers
In June 2025, CMS launched the Wasteful and Inappropriate Service Reduction (WISeR) Model, a tech-driven pilot program for PA and early claims review covering 17 service categories. The model runs from January 2026 through December 2031.
WISeR currently operates in six states: New Jersey, Ohio, Oklahoma, Texas, Arizona, and Washington. Connecticut is not currently in scope, but providers working with patients who receive care in those states, or providers with multi-state operations, should be aware of it.
WISeR services include categories flagged as vulnerable to fraud, waste, or inappropriate use. If CMS expands the model geographically, Connecticut providers may be affected in a future phase.
How to Prepare Your Practice Now
Audit Your Current PA Workflow
Map your current process end-to-end: how do you determine whether PA is required, how do you submit, how do you follow up, and how do you track approvals and denials? Identify where staff time is being spent and where approvals are being delayed.
Check Your EHR’s Electronic PA Capabilities
Not all EHR systems have built FHIR-based PA connectivity yet. Find out which payers your system connects to today, and ask your vendor specifically about their CMS-0057-F readiness roadmap. Plan to pilot electronic PA with one or two payers before scaling.
Train Staff on New Workflows
Electronic PA changes the workflow for front desk, clinical staff, and billing. Staff who are used to portal-based or fax-based PA will need to learn how to use the PA tools in your EHR. Designate a PA coordinator and schedule training before the January 2026 operational rules take effect.
Start Tracking Your PA Data
Payers will now publish their denial rates and turnaround times. You should track yours too. Know which payers deny most often, which service categories generate the most PA work, and what your average approval turnaround looks like. That data helps you identify workflow problems and gives you leverage in payer conversations.
Connecticut Medical Billing manages prior authorization workflows for busy CT practices. Let us handle the submissions, tracking, and follow-up so you can focus on patient care. Free consultation at connecticutmedbill.com.
Common Prior Authorization Problems, and How to Avoid Them
Forgetting to Check Before Scheduling
PA requirements change. A service that did not require authorization last year may require it now. Build a verification step into every scheduling workflow, not just for high-cost services.
Submitting Incomplete Clinical Information
Most PA denials are not clinical decisions, they are administrative. The request lacked required documentation, the wrong service code was submitted, or the clinical notes were not included. Submit the full clinical record with every PA request.
Missing the Urgent PA Window
Under the new CMS rules, payers must respond to urgent requests within 72 hours. But they can only start the clock when they receive a complete request. Incomplete urgent requests do not trigger the 72-hour clock.
Not Appealing Denials
Most PA denials are appealable. Many overturn on first appeal, especially when additional clinical documentation is provided. Build an appeals step into your denial management process, do not simply accept a PA denial and cancel the service.
FAQs: Prior Authorization API
When do payers have to implement the Prior Authorization API?
Impacted payers (Medicare Advantage, Medicaid managed care, CHIP, and QHPs on federal exchanges) must implement the PA API by January 1, 2027. The faster decision timeframes, 7 days for standard, 72 hours for urgent, take effect January 1, 2026.
Does this rule apply to traditional Medicare?
No. Traditional Medicare fee-for-service is not subject to CMS-0057-F. The rule covers Medicare Advantage plans, Medicaid programs, CHIP, and QHP issuers on the federally facilitated exchanges.
What is FHIR and why does it matter for PA?
FHIR (Fast Healthcare Interoperability Resources) is the technical standard that makes PA APIs possible. It allows your EHR to send and receive PA data in a standardized format that payer systems can read. Without FHIR compliance, electronic PA cannot work. Ask your EHR vendor whether their system is FHIR R4 compliant.
Will the PA API make all decisions automatic?
No. The API automates the submission and tracking process and may enable real-time approvals for routine cases. But complex cases, high-cost services, new therapies, clinically ambiguous situations, still require human clinical review. The API speeds up the process; it does not remove clinical judgment.
How will providers know which payers have the API in place?
CMS requires impacted payers to post implementation details and documentation publicly. Your EHR vendor’s payer directory will also indicate which payers have live API connections. As of January 2027, all impacted payers must have the APIs active.
What are the MIPS incentives for electronic PA?
CMS added electronic prior authorization as a measure under the MIPS Promoting Interoperability performance category. Eligible clinicians who attest to submitting at least one electronic PA via a FHIR-based API using certified EHR technology in 2027 will receive credit toward their MIPS score, affecting the 2029 payment year.
What is the WISeR model and should Connecticut providers care about it?
WISeR is a CMS pilot launching in January 2026 covering 17 service categories in NJ, OH, OK, TX, AZ, and WA. Connecticut providers are not currently in scope. However, CT providers with patients who receive care in those states, or who operate in multiple states, should monitor CMS for geographic expansion announcements.
Connecticut Medical Billing is ready to help your practice navigate the PA changes ahead. Schedule a free consultation at connecticutmedbill.com, and get ahead of the administrative burden before it gets ahead of you.
