Ten Days to Comment.
Here’s What CMS-0062-P Actually Requires.
The drug prior authorization proposed rule extends electronic PA to drugs using two different technical standards — FHIR for medical-benefit drugs, NCPDP for pharmacy-benefit drugs. The same specialty drug may require both.
Plans that are managing this as a drug PA rule are not managing it as the systems architecture question it is.
CMS published the CMS-0062-P proposed rule on April 14, 2026. The comment period closes June 15. That leaves ten days for plans to decide whether and how to comment — and to begin mapping what the final rule will require them to build.
The rule extends electronic prior authorization interoperability requirements to drugs. It is easy to read that description as a technical follow-on to the 2024 CMS-0057-F final rule, which addressed non-drug PA interoperability, and to assign it to the IT queue. That framing understates the complexity.
CMS-0062-P proposes a dual-standard architecture: HL7 FHIR standards for drugs covered under the medical benefit, and three NCPDP standards for drugs covered under the pharmacy benefit. The same drug — depending on how it is billed and administered — may require two different technical workflows, two different API implementations, and two different vendor relationships to process its prior authorization electronically. Plans that are managing this as a drug workflow update are not managing it as the systems architecture question it is.
CMS is not proposing one drug PA standard. It is proposing two parallel tracks determined by benefit type.
Specialty drugs — same molecule, different standard depending on site of administration and benefit billing
The applicable standard is determined by whether the drug is covered under the medical or pharmacy benefit — not by the drug itself.
This is not a drug workflow update. It is a dual-standard architecture problem.
CMS-0062-P builds on two predecessor rules: the 2020 CMS Interoperability and Patient Access final rule (CMS-9115-F), which established the foundational interoperability API framework, and the 2024 CMS Interoperability and Prior Authorization final rule (CMS-0057-F), which required electronic PA implementation for non-drug items and services using HL7 FHIR standards. CMS-0062-P extends that framework to drugs — but with a critical structural difference.
Medical-benefit drugs — drugs administered in clinical settings and billed under the medical benefit — use the FHIR-based Prior Authorization API, built on the same Da Vinci CRD, DTR, and PAS implementation guides as CMS-0057-F. Plans that completed CMS-0057-F implementation have a foundation here.
Pharmacy-benefit drugs use three NCPDP standards — NCPDP SCRIPT, Formulary and Benefit, and Real-Time Prescription Benefit — that operate in different technical environments from FHIR. The pharmacy-benefit drug PA workflow is not a FHIR extension. It is a separate standards track with its own vendor ecosystem, implementation requirements, and governance framework.
The operational implication: the same specialty drug — a biologic that can be infused in a clinical setting or self-administered through a specialty pharmacy, covered under either benefit depending on site of administration — may require two different electronic PA pathways. Plans that designed their CMS-0057-F FHIR implementation as the architecture for all PA going forward must now account for a parallel NCPDP track that FHIR does not cover.
The requirements go deeper than a vendor implementation. They require operational and staffing redesign.
72-hour standard. 24-hour urgent. Previous: 14 days / 72 hours.
CMS proposes compressing the drug PA timeliness window from 14 days (standard) and 72 hours (urgent) to 72 hours (standard) and 24 hours (urgent). For plans currently operating manual or semi-automated drug PA processes built around multi-day clinical review queues, this is not a technical implementation problem alone. It is a fundamental redesign of staffing, queuing, and clinical decision workflow. The API is the compliance threshold. The operational model is what makes meeting that threshold possible without clinical quality degradation.
October 1, 2027 for NCPDP pharmacy-benefit standards
CMS proposes an October 1, 2027 compliance date for the three NCPDP pharmacy-benefit standards. Plans have approximately 16 months from now to complete NCPDP implementation — alongside concurrent CMS-0057-F non-drug PA FHIR implementation obligations. For plans in multiple lines of business, this runs simultaneously across MA, Medicaid managed care, CHIP, and commercial product portfolios. IT capacity constraints are real; 16 months maps against current implementation backlogs, not theoretical capacity.
Applies to MA organizations, Medicaid managed care, CHIP, and QHP issuers
The proposed rule applies to Medicare Advantage organizations, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the FFEs. Plans in multiple lines of business are managing this across their entire product portfolio simultaneously. A plan with MA, Medicaid managed care, and commercial QHP products has three compliance tracks in three regulatory frameworks — all pointing to the same October 2027 NCPDP implementation deadline.
Comment period closes June 15 — 10 days from this edition
Plans that have specific concerns about the dual-standard architecture, the proposed timeliness compression, the scope of the pharmacy-benefit definition for specialty drugs, or the interaction with state-level PA interoperability mandates have ten days to put those concerns on the formal record. A well-documented comment identifying specific implementation challenges can influence how CMS structures compliance dates, transition provisions, and technical guidance in the final rule. Plans that do not comment have no formal basis to raise those concerns after publication.
The gray zone: same drug, different standard — and most plans haven’t mapped it
Specialty drugs that can be administered in clinical settings (medical benefit, FHIR track) or dispensed through specialty pharmacy (pharmacy benefit, NCPDP track) create the most operationally complex scenarios under CMS-0062-P. Oral oncology agents, specialty injectables, and biologics with both site-of-administration options are the gray zone. Plans with high-volume specialty drug PA need to map which of those requests route under medical-benefit FHIR workflows versus pharmacy-benefit NCPDP workflows — before implementation design begins. This is a benefit-design and utilization management architecture question, not just an IT question.
Source: CMS CMS-0062-P Fact Sheet; Federal Register April 14, 2026; CMS-0057-F 2024 Final Rule
What plan leadership needs to do before June 15 and after
Decide whether and how to comment
Commenting on a proposed rule is a technical record, not a political act. Plans with specific concerns about the dual-standard architecture, the timeliness compression, the specialty drug benefit-type definition, or interactions with state PA interoperability mandates have ten days to put those concerns on the formal record. Comments that identify specific implementation challenges — with evidence — can influence compliance date structure and technical guidance in the final rule. Plans that do not comment have no formal basis to raise those issues after the final rule publishes.
Map the dual-standard architecture against your current implementation state
Plans that completed or are completing CMS-0057-F FHIR PA implementation for non-drug items and services may assume the same architecture extends to drug PA. It does not — not fully. The pharmacy-benefit drug PA track requires NCPDP implementation in a separate vendor ecosystem. Plans should assess: which drug PA volume is pharmacy-benefit versus medical-benefit, what vendor capabilities exist for NCPDP SCRIPT and related standards, and what the interaction is between PBM relationships and the NCPDP implementation obligation.
Address the timeliness compression in operations, not just IT
The shift from 14-day standard to 72-hour standard for drug PA is not exclusively a technology problem. A plan that currently queues drug PA requests for clinical review over multiple days cannot automate its way to 72-hour turnaround without also redesigning the staffing model, the clinical decision logic, and the escalation pathway for requests requiring human clinical judgment. The technical API implementation is the compliance threshold. The operational redesign is what makes meeting that threshold possible without clinical quality degradation.
The comment period closes in ten days. The compliance date for pharmacy-benefit NCPDP standards is sixteen months away. The choices plans make in both windows will shape their implementation posture for one of the most consequential PA interoperability expansions CMS has proposed.
PCOOB Weekly — June 5, 2026Why this matters — by function
The comment period is a compliance governance opportunity, not just a technical task
Plans with documented concerns about implementation timelines, benefit-type definitions, or state law interactions can formally shape the final rule. Plans that do not engage have no basis to raise those concerns after publication.
This is two implementation projects, not one
FHIR for medical-benefit drug PA and NCPDP for pharmacy-benefit drug PA are separate standards tracks with different vendor ecosystems, APIs, and implementation governance. Plans managing this as a single extension of CMS-0057-F have not mapped the full architecture.
NCPDP implementation runs through the PBM relationship
The NCPDP SCRIPT and pharmacy benefit standards operate in the pharmacy vendor ecosystem. Plans whose PBMs manage pharmacy-benefit PA workflows need to assess how the NCPDP implementation obligation maps against existing PBM contracts and technical capabilities.
The timeliness compression requires operational redesign, not just automation
Moving from 14-day standard to 72-hour standard for drug PA requires changes to staffing models, clinical queue design, and escalation logic. Plans that automate the API without redesigning the clinical review workflow will fail to meet the turnaround requirement.
High-volume specialty drugs may require both PA tracks
Specialty drugs administered in clinical settings route under FHIR. The same drugs dispensed through specialty pharmacy route under NCPDP. Plans with high specialty drug PA volume need to classify their current volume by benefit type before implementation design begins.
The obligation runs across MA, Medicaid, and commercial simultaneously
CMS-0062-P applies to MA organizations, Medicaid managed care plans, CHIP entities, and QHP issuers. Plans in multiple product lines are managing parallel compliance tracks with the same October 2027 deadline across all of them.
Questions leaders should be asking now
Have we mapped which of our drug PA volume is pharmacy-benefit versus medical-benefit? Do we know the split for specialty drugs that can be administered under either benefit?
Has our IT team assessed whether our CMS-0057-F FHIR implementation covers the medical-benefit drug PA track — and separately mapped what NCPDP implementation requires for pharmacy-benefit drug PA?
Do we have a position on whether to submit comments before June 15? Are there specific implementation concerns — timeliness compression, benefit-type ambiguity, state law interactions — that belong on the formal record?
What is our current standard drug PA turnaround time? What operational redesign — staffing, queue logic, clinical decision criteria — is required to meet a 72-hour standard?
How does our PBM contract address NCPDP implementation obligations for pharmacy-benefit drug PA? Is NCPDP capability within scope of the current contract?
Does our implementation roadmap account for concurrent CMS-0057-F non-drug PA FHIR obligations alongside the new CMS-0062-P requirements? Is October 2027 achievable against current IT capacity?
- CMS-0062-P, published April 14, 2026, extends electronic PA interoperability to drugs. Comment period closes June 15, 2026 — ten days from this edition.
- The proposed rule creates a dual-standard architecture: FHIR for medical-benefit drug PA and NCPDP for pharmacy-benefit drug PA. The same specialty drug may require both depending on site of administration and benefit billing.
- CMS proposes compressing drug PA timeliness from 14-day standard and 72-hour urgent to 72-hour standard and 24-hour urgent. This requires operational redesign — not just technical API implementation.
- Proposed NCPDP compliance date: October 1, 2027 — 16 months from now, alongside concurrent CMS-0057-F non-drug PA obligations across all applicable product lines.
- Plans that do not comment before June 15 have no formal basis to raise implementation concerns when the final rule publishes. Documenting specific technical or operational challenges is a governance act, not just a regulatory formality.
Sources
-
1
CMS — CMS-0062-P Fact Sheet (2026) Confirms: Rule extends PA interoperability to drugs; dual standard framework (FHIR medical-benefit, NCPDP pharmacy-benefit); timeliness compression to 72-hour standard, 24-hour urgent; NCPDP compliance date October 1, 2027. Tier 1.
-
2
Federal Register — CMS-0062-P (April 14, 2026) Full proposed rule text. Applicability to MA organizations, Medicaid managed care plans, CHIP managed care entities, QHP issuers on FFEs. Comment period closes June 15, 2026. Tier 1.
-
3
CMS — CMS-0062-P Resource Page Comment submission procedures; relationship to CMS-0057-F and CMS-9115-F predecessor rules. Tier 1.
-
4
CMS — CMS-0057-F 2024 Final Rule (predecessor) FHIR-based PA interoperability requirements for non-drug items and services; Da Vinci implementation guide framework; baseline from which CMS-0062-P extends. Tier 1.