As healthcare organizations work toward the January 1, 2027, CMS-0057-F implementation date, they should also be looking ahead. Proposed CMS-0062-P could expand interoperability requirements to more payers, bring drug prior authorization further into the picture, and affect workflows across payers, providers, and clearinghouses.
The 2026 CMS Interoperability Standards and Prior Authorization for Drugs Proposed Rule, which we’ll refer to as CMS-0062-P, continues CMS’s effort to improve electronic prior authorization, reduce costs, shorten turnaround times, and increase transparency for patients. It builds on the foundation established by CMS-9115-F and CMS-0057-F.
Important: CMS-0062-P is a proposed rule. Requirements may change before a final rule is approved.
One proposed change would expand which payers are subject to interoperability requirements. CMS is proposing to add small group market Qualified Health Plan (QHP) issuers offering plans through the Federally-facilitated Small Business Health Options Program (FF-SHOP) to the impacted payer groups covered by the previous interoperability rules and these new proposals.
Source: CMS-0062-P Fact Sheet
CMS-0057-F focused on prior authorization for non-drug items and services. CMS-0062-P would extend many of those requirements to drugs, bringing electronic drug prior authorization further into the interoperability framework.
FHIR, X12, and Prior Authorization
Another major proposal is for HHS to adopt FHIR as the standard for electronic prior authorization transactions under HIPAA, replacing the current X12 standard for these transactions. Implementers, take note.
There is an important exception: drugs covered under a pharmacy benefit would continue to use NCPDP standards rather than FHIR. Drugs covered under a medical benefit would use the FHIR Prior Authorization API.
These proposed HIPAA changes would reach beyond the payers directly affected by CMS interoperability rules. They would apply to HIPAA-covered entities that exchange prior authorization information electronically, including providers, health plans, and clearinghouses. That could mean substantial work for organizations that are not otherwise directly affected by CMS-0062-P.
HHS is also proposing to adopt the HL7 Da Vinci Clinical Data Exchange (CDex) Implementation Guide (IG) as the attachment standard for prior authorization transactions. CDex provides a standard way to request and exchange the additional clinical information needed to support a prior authorization request, including structured data and documents such as PDFs.
Organizations using X12 or still building their FHIR infrastructure would have time to prepare. Under the proposal, most covered entities would have 24 months after the final rule’s effective date to comply with the HIPAA changes, while small health plans would have 36 months.
For Drug Prior Authorization, Is It FHIR or NCPDP?
The answer depends on how the drug is covered.
Drugs covered under the medical benefit would be added to the FHIR Prior Authorization API organizations are already building for CMS-0057-F. CMS notes that existing workflows already support these drugs. The work would largely involve adding the appropriate drug coverage and documentation requirements, rather than creating an entirely new workflow.
Drugs covered under the pharmacy benefit would continue to use NCPDP standards. CMS is proposing NCPDP SCRIPT for electronic prior authorization, along with NCPDP standards for formulary, benefit, and real-time prescription benefit information.
So, CMS is not proposing to rebuild pharmacy prior authorization around FHIR.
Proposed Implementation Guides
CMS is proposing the following IGs for the interoperability APIs:
- HL7 FHIR CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®):Version 2.0.0-STU 2, proposed to expire January 1, 2028, or Version 2.2.0-STU 2.2
- HL7 FHIR Da Vinci Payer Data Exchange (PDex):Version 2.1.0-STU 2.1
- HL7 FHIR Da Vinci PDex US Drug Formulary: Version 2.0.1-STU 2, proposed to expire January 1, 2028, or Version 2.1.0-STU 2.1
- HL7 FHIR Da Vinci PDex Plan Net:Version 1.1.0-STU 1.1 US, proposed to expire January 1, 2028, or Version 1.2.0-STU 1.2
- HL7 FHIR Da Vinci Coverage Requirements Discovery (CRD):Version 2.0.1-STU 2, proposed to expire January 1, 2028, or Version 2.2.1-STU 2.2
- HL7 FHIR Da Vinci Documentation Templates and Rules (DTR):Version 2.0.1-STU 2, proposed to expire January 1, 2028, or Version 2.2.0-STU 2.2
- HL7 FHIR Da Vinci Prior Authorization Support (PAS):Version 2.0.1-STU 2, proposed to expire January 1, 2028, or Version 2.2.1-STU 2.2
Source: CMS-0062-P Fact Sheet
If you have been keeping up with CMS-9115-F and CMS-0057-F, many of these should look familiar. C4BB, PDex, PDex Plan Net, CRD, DTR, and PAS are already part of the conversation.
There is a technical distinction worth calling out: some of these IGs were previously recommended rather than explicitly required in the way CMS-0062-P now proposes. Being ready for CMS-0057-F does not necessarily mean there is no additional work.
The workflows may already be in place, but organizations should confirm that their implementations align with the proposed requirements.
Prior Authorization API Endpoint Reporting
CMS is proposing that impacted payers report their interoperability API endpoints so CMS can make them available in a centralized location. Under the proposal, endpoints would need to be reported no later than 60 days after the final rule’s effective date.
The proposal includes endpoints for the Patient Access, Provider Directory, Provider Access, Payer-to-Payer, and Prior Authorization APIs.
Decision Timeframe Updates
This could become challenging for organizations whose prior authorization workflows are not automated or are difficult to scale.
Medicaid and CHIP already generally require a 24-hour turnaround for covered outpatient drugs. CMS is proposing changes to close some remaining gaps. For marketplace plans, CMS proposes a maximum of 72 hours for standard drug prior authorization requests and 24 hours for expedited requests.
CMS is also proposing that marketplace plans meet the same deadlines for non-drug items and services: 7 calendar days for standard requests and 72 hours for expedited requests.
If finalized, these changes would take effect October 1, 2027.
How difficult those timelines will be to meet depends heavily on how automated an organization’s prior authorization workflows are today.
Communication About Drug Prior Authorization Denials
CMS is proposing that applicable impacted payers provide providers with a specific reason when a drug prior authorization request is denied. More consistent denial information would help providers decide whether to resubmit a request or appeal the decision.
The proposal would take effect October 1, 2027.
API Usage Metrics
CMS is proposing new prior authorization metrics for drugs. The proposal would also add the Provider Access, Payer-to-Payer, and Prior Authorization APIs to the list of APIs for which usage metrics must be reported to CMS.
Reporting would begin in 2028 using data from 2027. Reporting requirements and deadlines would vary by payer type:
- Medicare Advantage organizations:Report at the contract level by March 31 each year.
- Medicaid and CHIP fee-for-service programs:Report at the state level by March 31 each year.
- Medicaid managed care plans and CHIP managed care entities:Report at the plan and program levels no later than 90 days after the end of each rating period. These entities would report API usage metrics to states.
- QHP issuers on the Federally-facilitated Exchanges (FFEs): Report at the issuer level by the FFE QHP certification deadline in the following year.
Proposed Updates to Current APIs
To make drug prior authorization data available, CMS is proposing updates to the Patient Access, Provider Access, and Payer-to-Payer APIs.
The Patient Access and Provider Access APIs would include information such as:
- Prior authorization status
- Date of approval or denial
- Date or circumstance under which the authorization ends
- Approved drug or drugs, including dosage
- Specific reason for denial
Related administrative and clinical documentation submitted by the provider
The Payer-to-Payer API would include much of the same information, with one important exception: denied prior authorization requests would not be available through this API.
Impacted payers can expect a proposed go-live date of October 1, 2027, for these changes.
So, What’s Coming Next?
For organizations already deep into CMS-0057-F implementation, CMS-0062-P should not feel like starting over. Many of the building blocks are familiar: FHIR, PDex, CRD, DTR, PAS, and the Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization APIs.
The bigger shift is scope.
Drug prior authorization is moving further into the interoperability framework. Medical-benefit drugs would join the FHIR Prior Authorization API, while pharmacy-benefit drugs would remain in the NCPDP ecosystem. More payer types may be affected, prior authorization data would flow through existing APIs, decision timelines could tighten, and API reporting would expand.
For organizations that have treated CMS-0057-F as the finish line, CMS-0062-P is a clear sign that the work will continue. The infrastructure built for today’s requirements may become the foundation for what comes next, but organizations will need to assess where their workflows, data, and reporting capabilities still have gaps.
RBA helps healthcare organizations plan and implement interoperability solutions, including FHIR-based APIs, prior authorization workflows, and the data and reporting capabilities that support them. As the proposed rule moves toward finalization, RBA can help teams assess their current readiness and develop a practical path forward.
Reference Guide
- IG: Implementation Guide
- CMS: Centers for Medicare & Medicaid Services
- HHS: Department of Health and Human Services
- CMS-0057-F: CMS Interoperability and Prior Authorization Final Rule
- CMS-9115-F: CMS Interoperability and Patient Access Final Rule
- C4BB: CARIN Consumer Directed Payer Data Exchange (CARIN for Blue Button)
- PDex: Payer Data Exchange
- CRD: Coverage Requirements Discovery
- DTR: Documentation Templates and Rules
- PAS: Prior Authorization Support
- CDex: Clinical Data Exchange
- NCPDP: National Council for Prescription Drug Programs
Disclaimer
This article was developed with the assistance of artificial intelligence tools to support drafting, editing, and clarity. The core ideas, structural planning, and technical insights reflect the original thinking and professional experience of the RBA consultant who authored the piece. AI was used as a productivity aid, while all concepts, recommendations, and perspectives remain the author’s responsibility.
About the Author
Robby Sarvis
Senior Software Engineer
Robby is a full-stack developer at RBA with a deep passion for crafting mobile applications and enhancing user experiences. With a robust skill set that encompasses both front-end and back-end development, Robby is dedicated to leveraging technology to create solutions that exceed client expectations.
Residing in a small town in Texas, Robby enjoys a balanced life that includes his wife, children, and their charming dogs.