Interoperability mandates pushed most payers to deploy FHIR APIs. However, simply meeting the technical requirement no longer sets organizations apart. Today, the leaders are those treating FHIR as core enterprise infrastructure. They use it to drive operational efficiency, support AI readiness and unlock long-term strategic value. To understand where the market stands, Becker’s Healthcare spoke with Mike O’Neill, CEO of MedicaSoft.
FHIR Moves Beyond Compliance
How the Payer Conversation Has Shifted
A few years ago, most payers viewed FHIR primarily as a compliance requirement. The focus centered on meeting CMS Interoperability and Prior Authorization Rule deadlines. Organizations stood up APIs to satisfy regulatory obligations — and little more. In reality, those early implementations were tactical and standalone. They technically exposed data but did not integrate into broader operational or business strategies.
More recently, the mindset has changed. Payers now see FHIR as more than a compliance framework. Furthermore, many organizations use FHIR APIs to retrieve clinical data directly from providers. This replaces slow, document-based workflows. Additionally, payers build analytics and reporting capabilities — including quality measurement and population health programs — directly on FHIR-based data models.
Persistent Gaps Still Exist
Despite this progress, significant challenges remain. Many organizations can technically exchange FHIR data. However, underlying processes stay fragmented. Data completeness and consistency are ongoing problems. Moreover, workflow transformation lags behind technical deployment. The organizations making the most progress treat data interoperability as an enterprise strategy. They invest in governance, reusable platforms and operational redesign — not just IT projects.
How Payer Readiness Varies Across the Market
A Divided Landscape
The payer market is unevenly prepared for interoperability mandates. A small group of digitally mature payers invested early in API infrastructure. As a result, those organizations are in strong shape. Many others, however, are still catching up. The challenge runs deeper than technology deployment. The CMS rule requires workflow redesign across the entire organization.
What Separates Leaders from Laggards
Organizations most likely to succeed share common traits. They maintain enterprise API strategies, strong governance and executive sponsorship. Moreover, they collaborate closely with providers and EHR vendors to test real-world workflows. In contrast, organizations that struggle typically face fragmented legacy systems, siloed ownership and overly manual authorization processes. Many also underestimate the operational change management the rule demands. Ultimately, the differentiator is not who deploys APIs fastest. It is who operationalizes them effectively at scale.
Where FHIR Investments Deliver Measurable ROI
Clinical Data Exchange and Care Management
FHIR-enabled clinical data exchange directly improves care management and utilization review. When payers leverage FHIR interoperability, teams make faster decisions with less manual effort. Data becomes more accessible and more timely. Consequently, care managers spend less time chasing records and more time acting on them.
Quality, Risk Adjustment and Prior Authorization
More complete clinical data supports HEDIS performance, Stars ratings and value-based care programs. NCQA’s shift to HEDIS digital quality measures lets payers compute measures directly on FHIR data. This further leverages existing FHIR investments. Additionally, prior authorization automation — though still in early stages — reduces manual reviews, phone calls, faxes and turnaround times. Over time, these gains generate meaningful operational savings.
AI Readiness as a Strategic Advantage
FHIR-based architectures also create significant AI readiness value. They produce accessible, high-quality data with clear provenance and governance. This level of curated healthcare data enables more powerful AI applications. Furthermore, organizations with FHIR-native data strategies can operationalize AI far more effectively than those relying on raw, unstructured legacy data.
Build, Buy or Partner: Choosing the Right Approach
Avoiding the Technology Procurement Trap
The biggest mistake payers make is treating interoperability as a simple technology procurement. Instead, organizations must focus on workflow orchestration, governance, analytics and business process optimization. These elements must integrate with architecture and technology decisions — not follow them.
Evaluating the Right Model
API infrastructure, FHIR servers and terminology services are increasingly available. However, assembling them into an end-to-end data flow requires deliberate effort. Organizations must address patient matching, data deduplication and data quality improvements. Where internal capabilities are strong and there is clear differentiating value in keeping operations in-house, a build approach makes sense. Otherwise, partnering with a platform vendor on architecture and implementation proves more effective. A hybrid strategy is also workable and often practical for large, complex payer organizations.
The Future of FHIR in Payer Organizations
From API Layer to Native Data Model
In the coming years, FHIR will shift from an external API layer to a native data model inside payer organizations. Currently, many payers still use FHIR as a layer sitting on top of legacy systems. That approach worked when compliance drove priorities. However, as organizations seek to leverage more data for analytics and automation, FHIR-native architectures become essential. They offer far greater flexibility for quality measurement, workflow automation, care management and AI.
FHIR-Native Platforms on the Rise
One of the most significant coming changes is the growth of FHIR-based operational and analytical platforms. Rather than constantly transforming data between proprietary models and FHIR formats, payers will store and work with clinical and administrative data directly in FHIR. This creates a more standardized, reusable foundation across the enterprise. AI will accelerate this transition. AI applications depend on clean, structured and contextual data. FHIR provides a more consistent framework for representing clinical information than most legacy payer data models.
What Payer Leaders Should Prioritize Now
Payer leaders must develop a long-term FHIR data strategy — not just a compliance roadmap. That means investing in scalable FHIR-native platforms. It also means improving data quality and terminology management. Additionally, leaders must build governance models that support consistent enterprise-wide use. High-value use cases deserve immediate attention. Quality measurement, prior authorization automation and AI-enabled analytics all benefit directly from native FHIR data. The organizations that stay ahead will treat FHIR as foundational infrastructure for digital operations and future innovation — not simply an API compliance checkbox.
