Streamlining Prior Authorization: CMS’s 2026 Proposed Rule
Recent developments in healthcare underscore the growing importance of prior authorization (PA) processes among medical providers and insurers. Traditionally, PA has involved care providers submitting clinical documents to insurers for coverage evaluation before treatment begins. Despite the advance towards digital health systems, many PA tasks remain paper-based, contributing to administrative burdens and delays.
The Centers for Medicare and Medicaid Services (CMS) has responded by introducing the 2026 Interoperability Standards and Prior Authorization for Drugs Proposed Rule (CMS-0062-P). This proposed rule aims to streamline the PA process by incorporating interoperability standards, though its effectiveness will depend on overcoming regulatory and operational challenges.
Implementing API-Based Interoperability
CMS-0062-P mandates that entities such as Medicare Advantage organizations, Medicaid, Children’s Health Insurance Program (CHIP) administrators, and some Qualified Health Plan issuers deploy Application Programming Interfaces (APIs). These APIs facilitate real-time data exchange, creating digital connections for sharing clinical information between providers, payers, and other stakeholders.
Following previous rules establishing API-based interoperability for non-drug services, the proposed 2026 rule extends these requirements to drugs and biologics. If implemented, electronic health records and software could simplify PA procedures from request submission to decision notification, while payers could swiftly assess medical necessity without relying on manual processes.
Addressing PA Workflow Challenges
The proposed framework suggests separate workflows based on whether a medical or pharmacy benefit is in use. For medical benefits, APIs will use the Fast Healthcare Interoperability Resources (FHIR) standard, while pharmacy benefits will employ the National Council for Prescription Drug Programs (NCPDP) standards. These bifurcated methodologies, however, may complicate PA determinations due to varying insurance benefit designs.
Additionally, the proposal marks a shift in HIPAA-related compliance, favoring FHIR standards over the traditional X12N 278 format for PA transactions. Although this could streamline operations, the dual-standard system may increase complexity and compliance costs within the industry.
Stakeholders are encouraged to participate in the public comment period to address concerns and explore questions about API implementations and extensions to other health IT certifications. While the changes aim to revolutionize PA, the breadth and tight deadlines raise questions about achieving the proposed benefits in the healthcare landscape.