CMS Embeds FHIR Standards in FY 2027 Hospital Payment Rule, Forcing API Upgrades

CMS ties FHIR APIs to Medicare payments, shifting compliance from optional to mandatory

The Office of the National Coordinator for Health IT finalized adoption of specific FHIR-based standards in the FY 2027 Hospital Inpatient Prospective Payment System final rule (CMS-1849-F), embedding interoperability requirements directly into Medicare payment policy for hospitals. The standards mandate FHIR APIs for electronic prior authorization transactions, administrative and clinical data exchange between payers and providers, payer drug formularies, and payer provider directories.

This moves FHIR compliance from a competitive differentiator to a regulatory prerequisite for any hospital dependent on Medicare reimbursement. The rule specifies four use cases with concrete implementation requirements, not optional guidance. For hospital IT budgets, this means capital previously allocated to bespoke integrations must now shift toward FHIR API enablement and prior authorization modernization or risk falling out of compliance with payment policy.

EHR and payer vendors face immediate roadmap pressure

Epic, Oracle Health, MEDITECH, and other EHR vendors must align certified modules with the finalized FHIR profiles to remain viable for IPPS-participating hospitals. On the payer side, platforms including Availity, Edifecs, Cognizant's TriZetto, and Optum must expose or consume these APIs to support the mandated workflows. Vendors that marketed CMS and FHIR compliance before this rule—such as 1upHealth, Health Gorilla, Redox, and Zus Health—now hold a positioning advantage as pre-aligned infrastructure, but all players face tighter procurement scrutiny.

RFP language is already tightening around demonstrated support for the specific FHIR implementation guides referenced in CMS-1849-F and vendor commitments to maintain compatibility as ONC updates its Standards Version Advancement Process list. Prior authorization automation becomes a regulatory necessity rather than an efficiency play, intensifying competition between API-first platforms and traditional clearinghouses still reliant on X12 and EDI workflows.

1upHealth packages CMS prior auth compliance into standalone product

1upHealth launched 1up Gateway in August 2026, targeting health plans that already have FHIR infrastructure but need a faster path to CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) compliance. The product positions itself as middleware for plans that do not want to build custom compliance solutions from scratch, competing against consulting firms like Accenture, Deloitte, and Cognizant that offer bespoke implementations and against other FHIR vendors including Health Gorilla, Smile Digital Health, and Verinovum.

The move reflects a broader shift in the market: CMS-0057-F compliance is a regulatory deadline cost center, and productized paths reduce the total cost of ownership compared to multi-year custom builds. Procurement teams evaluating 1up Gateway and its competitors will demand mapping documentation showing how each CMS-0057-F requirement is satisfied and compare subscription-plus-integration pricing against the capital expense of SI-led builds. Vendors that can demonstrate shorter implementation timelines while working within existing FHIR infrastructure will win deals from plans racing to meet CMS deadlines.

Budget implications: capital shifts from integration to API compliance

For hospitals participating in IPPS, the FY 2027 rule forces a re-prioritization of IT capital. Projects that do not map cleanly to the adopted FHIR implementation guides lose budget priority. Expect increased spend on FHIR gateways, API security, and workflow orchestration tightly integrated with provider EHRs. Systems still relying on custom portals, fax, or proprietary APIs face both a compliance disadvantage and a provider-relations problem as regulatory expectations harden.

Risk management shifts from managing interoperability friction to managing regulatory and financial exposure. Buyers will demand contractual SLAs around FHIR support and roadmap alignment with ONC and CMS updates. Vendors that cannot commit to maintaining compatibility with evolving standards face contract risk and customer churn as hospitals consolidate around platforms that reduce compliance overhead.

What to watch: ONC standards updates and vendor roadmap commitments

The Standards Version Advancement Process will continue to evolve, and vendors must prove they can keep pace without forcing disruptive migrations on customers. Watch for RFPs that explicitly require demonstration of support for the four FHIR use cases finalized in CMS-1849-F and for contractual language that holds vendors accountable for maintaining compatibility with future ONC updates. Health plans evaluating CMS-0057-F compliance vendors should compare implementation timelines, total cost of ownership against custom builds, and the vendor's track record with previous CMS interoperability mandates.

The rule eliminates the option to delay FHIR adoption. Hospitals and payers that treat this as a checkbox exercise rather than a foundational infrastructure shift will find themselves locked out of modern workflows as the market consolidates around API-first architectures.