CMS Proposes FHIR Mandate for Drug Prior Authorization by 2026

CMS expands FHIR requirements to drug prior authorization

CMS's proposed 2026 Interoperability Standards and Prior Authorization for Drugs rule (CMS-0062-P) would require affected payers to support electronic prior authorization, meet shorter decision timeframes, publish interoperability API endpoints and usage metrics, and adopt updated HL7 FHIR implementation guides.

The proposal extends interoperability requirements to HIPAA-covered providers, health plans and clearinghouses for electronic prior-authorization transactions. It mandates the HL7 FHIR Da Vinci Clinical Data Exchange (CDex) Implementation Guide for clinical attachments—moving beyond generic FHIR compatibility to specific, testable profiles.

For health plans and health systems, this means budgeting for API upgrades, FHIR implementation-guide conformance, clinical-attachment exchange, endpoint reporting and audit capabilities. Vendor claims of "FHIR support" are insufficient. Buyers should require testing against the proposed CMS/HHS profiles, including CDex, before contract signature.

The rule increases pressure on payer technology suppliers and prior-authorization platforms—including incumbent clearinghouses, EHR-integrated vendors and FHIR-native API providers—to support standardized exchange rather than proprietary workflows. It also raises the importance of conformance to specific FHIR implementation guides, not merely API availability.

University Hospitals connects 21 hospitals with 300-plus EMS agencies

University Hospitals (UH) expanded its arrangement with ESO for ESO Prehospital Intelligence and ESO Health Data Exchange. UH's existing ESO HDE deployment has connected 21 hospitals with more than 300 agencies across 16 counties since July 2025.

The exchange connects prehospital clinical data with Epic and returns discrete EMS-encounter information—including lab results, imaging, detailed vital signs and procedure notes—to EMS teams. This is bidirectional workflow rather than conventional document-only exchange.

The deployment positions ESO against health-information exchanges, EHR-native interoperability tools and emergency-care data platforms. Its differentiator is granularity: discrete data elements integrated into Epic can support clinical handoffs and post-acute feedback more effectively than PDF or CCD document exchange.

Health systems evaluating interoperability should assess measurable network scale—hospitals, agencies and counties connected—as well as the granularity of returned data. The UH–ESO announcement does not disclose pricing, implementation cost or clinical-performance benchmarks, so the commercial case remains incomplete. Buyers should request metrics on data-delivery latency, match rates, failed transactions, clinician adoption and measurable effects on emergency-department throughput before treating the deployment as proof of ROI.

What this means for procurement

The CMS proposal is the more important near-term budget signal. It points toward standardized FHIR-based prior authorization, clinical attachments and public API-usage reporting. Procurement teams should avoid building solely to draft language—the proposal remains a rulemaking item rather than a final compliance deadline—but new platform purchases should include contractual commitments to accommodate updated CMS standards without major reimplementation.

The UH–ESO deployment supplies a concrete operational example with 21 hospitals and 300-plus EMS agencies, but its undisclosed pricing and outcomes mean buyers should seek independent implementation and ROI data before committing. Ask vendors for measurable network scale, data granularity, delivery latency and clinical adoption metrics. Anecdotal deployment announcements are not purchasing justification.

For health plans, the CMS rule raises the cost of compliance and the risk of vendor lock-in. Evaluate whether your current prior-authorization platform can meet CDex conformance or whether you will need to switch vendors or add a FHIR gateway. For health systems, the rule increases the value of EHR-native interoperability and raises the cost of maintaining proprietary clinical-attachment workflows. Budget for testing, conformance validation and endpoint monitoring infrastructure in 2026 and 2027.