A proposed rule published April 10, 2026 establishes separate ePA architectures for medical benefit and pharmacy benefit drugs, with an October 2027 compliance deadline that most pharmacy teams are not planning for.
By Shan Siddique, PharmD | TheraIntel | April 2026 | 8 min read
Introduction
On April 10, 2026, CMS published the Interoperability Standards and Prior Authorization for Drugs proposed rule in the Federal Register. The rule formally separates drug prior authorization into two distinct technical tracks — one for drugs covered under the medical benefit, one for drugs covered under the pharmacy benefit — and mandates compliance with specific electronic standards by October 1, 2027. Public comments are due June 15, 2026.
This is not an incremental update to the January 2024 Interoperability and Prior Authorization Final Rule. That rule established FHIR-based APIs for non-drug prior authorization requests. It explicitly excluded pharmacy benefit drugs. This proposed rule fills that gap — and it does so with a completely different set of standards.
If your compliance team has been treating the 2024 PA rule as covering pharmacy benefit drugs, it doesn’t. Your pharmacy benefit drug PA workflow is unaddressed by the 2024 final rule and now subject to a separate proposed mandate with an October 2027 compliance date. [CMS, 2026; Federal Register, 2026]
Clinical Context
Prior authorization as currently implemented is functionally broken. Medicare Advantage plans alone processed 52.8 million PA determinations in 2024, denying 4.1 million — 7.7% of all requests. [CMS OIG, 2025] Of those denials, only 11.5% were ever appealed. When appeals were filed, 80.7% succeeded.
That gap between “denied” and “appealed” represents patients who gave up on medications they should have received.
The pharmacy-side numbers are equally clear. 88% of pharmacists report that prior authorization often or always delays treatment. 38% cite PA burden as a significant driver of professional burnout. [Surescripts, 2025; MGMA, 2025] For pharmacy operators managing high-volume Medicaid populations, PA delay is a throughput bottleneck that determines how many patients a pharmacist can actually serve per shift.
The January 2024 Interoperability and Prior Authorization Final Rule addressed PA for durable medical equipment, home health, and outpatient services. It built a FHIR-based API framework for non-drug requests. Drugs processed through the pharmacy benefit were explicitly out of scope. [CMS, 2024]
This proposed rule closes that exclusion.
Key Findings
-
CMS formalizes a dual-track ePA architecture. The rule creates a technical split: drugs covered under the medical benefit use HL7 FHIR-based Prior Authorization APIs, consistent with the 2024 final rule framework. Drugs covered under the pharmacy benefit — retail-dispensed prescriptions, mail-order fills, specialty medications — use three NCPDP standards. These are architecturally separate. A system that supports FHIR PA APIs does not automatically satisfy the pharmacy benefit requirements in this proposed rule. [Federal Register, 2026]
-
Three NCPDP standards become mandatory for pharmacy benefit drugs by October 1, 2027. The SCRIPT standard handles ePA request-and-response transactions at the point of prescribing. The Formulary & Benefit (F&B) standard allows payers to communicate formulary tiers, step-therapy requirements, and PA triggers at the health plan level. The Real-Time Prescription Benefit (RTPB) standard — the most operationally significant of the three — enables patient-specific eligibility, formulary coverage, and estimated cost-sharing information to surface at the prescribing moment, before the patient ever reaches the pharmacy counter. Impacted payers include Medicare Advantage organizations, Medicaid managed care plans, CHIP agencies, and QHP issuers on federally-facilitated exchanges. [CMS, 2026]
-
Decision timelines compress significantly. CMS proposes a 24-hour maximum turnaround for standard prior authorization requests for covered outpatient drugs under Medicaid and CHIP fee-for-service programs. For QHP issuers on federally-facilitated exchanges, the proposal sets 72 hours for standard drug requests and 24 hours for expedited requests. These are stricter than what most state-level Medicaid programs currently require. Achieving them at scale requires automated intake, automated review against coverage criteria, and electronic decision transmission — none of which is possible if any step in the PA workflow is still fax-based or requires manual chart review. [CMS, 2026; Federal Register, 2026]
-
All pharmacy benefit drug PA denials must include specific reasons. The proposed rule eliminates vague denial language — “not medically necessary,” “does not meet coverage criteria” — and requires that payers provide a specific clinical reason for every denial. This creates an auditable documentation trail and significantly strengthens the basis for appeals. For pharmacy teams, the downstream effect is that you need to capture and log denial reasons at the point of receipt, not as an afterthought during the appeals process. [CMS, 2026]
“When formulary coverage and prior authorization requirements surface at the prescribing moment, the pharmacy counter stops being the place where PA surprises happen. For pharmacy platforms, that is not a compliance investment. It is a throughput investment.”
Operational Impact
For pharmacy operators and pharmacy directors, this proposed rule creates three immediate action items — none of which should wait for the final rule to publish.
Audit your NCPDP SCRIPT ePA version support now.
Multiple versions of the NCPDP SCRIPT standard exist, and not all support ePA transaction types. Ask your pharmacy management system vendor directly: which version do you support, and are ePA request and response transactions live in your current build? If you don’t have a clear answer by Q3 2026, you’re too late to make a meaningful vendor decision before the compliance window narrows.
Verify your PBM’s Real-Time Prescription Benefit implementation status.
The RTPB standard has the lowest adoption rate of the three mandated standards. It’s the newest, the most operationally complex, and the one most pharmacy technology vendors have deprioritized. The RTPB only delivers value if your PBM is actively transmitting patient-specific benefit data. If your PBM isn’t live on RTPB, you can’t use it — and CMS’s October 2027 deadline doesn’t distinguish between technology failures on the payer side versus the pharmacy side.
Map your PA workflow against the 24-hour turnaround requirement.
If any step in your current PA process involves a fax, a phone call, or manual documentation, it cannot survive a 24-hour compliance clock at volume. Pharmacy platforms processing hundreds of PA requests per day need automation at intake, routing, and decision notification — not just at one step in the middle of the process.
For multi-state pharmacy operators, the complexity compounds. Medicaid managed care plan configurations vary by state, and the proposed rule applies differently to fee-for-service programs versus managed care within the same state. A single national compliance standard doesn’t exist here — you need a state-by-state readiness map.
TheraIntel Perspective
The October 2027 date creates a false sense of time.
Pharmacy IT procurement cycles run 12 to 18 months from initial vendor evaluation through contract, implementation, testing, and staff training. Any pharmacy organization that doesn’t begin NCPDP SCRIPT ePA and RTPB capability evaluation before Q3 2026 is executing against an October 2027 deadline with no realistic margin for vendor delays or implementation failures.
This rule doesn’t exist in isolation. CMS launched the WISeR Model in January 2026, using AI and machine learning to screen Medicare PA requests for fraud, waste, and abuse across six states. The 2024 Interoperability and PA Final Rule built FHIR-based PA infrastructure for non-drug items. This proposed rule extends the same logic to pharmacy benefit drugs. Federal PA policy is moving in one direction: electronic, standardized, and faster.
Organizations treating each of these rules as a separate compliance event will build three disconnected systems. The ones treating them as a unified redesign of PA infrastructure will build something durable — and will avoid paying for the same implementation twice.
There is also a strategic advantage hiding inside the RTPB standard that most pharmacy leaders haven’t quantified. When formulary coverage and PA requirements surface at the prescribing moment, the pharmacy counter stops being the place where PA surprises happen. For pharmacy platforms — where pharmacist capacity is the binding constraint on patient throughput — eliminating that friction point has direct operational and revenue implications. That’s not a compliance cost. That’s a competitive position.
Comment on this rule before June 15, 2026. CMS is explicitly requesting stakeholder input on whether October 2027 is achievable. Pharmacy operators with real workflow data — PA volume per pharmacist, manual step count, average time-to-decision — will shape what the final rule actually requires. If you miss the comment window, you give up your right to object to a timeline CMS sets without your operational reality in the record.
Conclusion
CMS’s April 2026 proposed rule is the most pharmacy-specific prior authorization mandate in years. It creates a new compliance track for pharmacy benefit drugs, mandates three NCPDP standards that most health system vendors have not fully implemented, compresses PA decision timelines to 24 hours, and requires specific denial documentation for every denial.
Audit your NCPDP SCRIPT ePA capability this week. Confirm your PBM’s RTPB status before summer. Submit comments before June 15, 2026.
Connect with TheraIntel to review your current PA infrastructure against the proposed rule’s requirements and build a compliance roadmap before the comment period closes.