CMS-0057-F Vendor Readiness Matrix: Who's Ready for January 2027

Thesis

For pharma services buyers, the rule matters even though it is payer-facing. Hub vendors, FRM teams, and PA automation partners will be judged by how well they can operate in a mixed environment where Medicare Advantage and Medicaid move toward FHIR APIs while pharmacy benefit, commercial, ERISA, and complex specialty exceptions still require phone, fax, portal, and human escalation.

Executive Summary

CMS-0057-F (see CMS-0057-F: Interoperability & Prior Authorization Final Rule) requires impacted payers — Medicare Advantage, Medicaid/CHIP, and FFE QHP issuers covering ~135 million Americans — to deploy five FHIR-based APIs by January 1, 2027, with operational PA timeframe requirements taking effect January 1, 2026. Most payers will meet the mandate by licensing vendor platforms rather than building in-house.

The vendor ecosystem has split into three clear readiness tiers as of Q2 2026. The April 10, 2026 CMS-0062-P drug-prior-auth proposal raises the stakes further by pushing buyers to ask not only “who is ready for the 2024 final rule?” but also “whose platform can extend cleanly into drug PA if the proposal is finalized?”

Tier 1 — Production Ready: Have live FHIR API deployments with at least one payer customer in production; claim compliance against all four net-new Da Vinci IGs (CRD, DTR, PAS, PDex). Winners: Cohere Health, Availity, Edifecs, CareEvolution.
Tier 2 — Adjacent + Retrofitting: Strong in pharmacy ePA or payer portal infrastructure; building FHIR-based medical benefit PA capabilities but not yet in full production against all IGs. Status: CoverMyMeds, Surescripts, HealthEdge, Inovalon, Smile Digital Health (Smile CDR).
Tier 3 — Complementary / Long-Tail: Solve the “unstructured PA” problem that FHIR APIs don’t address (phone/fax PA, complex specialty cases, peer-to-peer negotiation). Not FHIR API vendors, but will coexist with the mandate: Infinitus Systems, SuperDial, Rhyme, Cohere Health (on the AI auto-determination side), eviCore by Evernorth (the dominant incumbent UM vendor that could be disrupted).

Bottom line for pharma services buyers: Manufacturers evaluating hub vendors, FRM teams, or PA automation tools in 2026-2027 should favor partners with validated FHIR API integrations against payers in the RFP footprint. Vendors without production FHIR deployments by Q4 2026 will miss the initial compliance wave and may consolidate or exit.

The Regulatory Clock

Milestone	Date	Implication
Final rule published	Jan 17, 2024	Rule codified; 36-month ramp begins
PA decision timeframes effective	Jan 1, 2026	72h expedited / 7 calendar days standard
First public PA metrics due	Mar 31, 2026	Comparison shopping becomes possible
CMS-0062-P proposed	Apr 10, 2026	Drug prior-auth expansion moves from speculation to active rulemaking
FHIR APIs in production (all 5)	Jan 1, 2027	Payer non-compliance exposure begins
Proposed drug-PA compliance date	Oct 1, 2027	If finalized, drug PA APIs and related standards broaden the compliance scope
Second annual PA metrics due	Mar 31, 2027	YoY trends visible; laggards exposed
2028+ market phase	2028+	Finalization of drug proposals and possible broader commercial convergence become the watch items

Industry commentary (Firely, CareEvolution, Tegria) consistently reports typical implementation timelines of 12-18 months end-to-end for payers moving from zero FHIR footprint to full IG conformance. That means any payer that has not signed a vendor or committed internal engineering resources by Q3 2026 is at material risk of missing January 2027.

Required APIs vs. Implementation Guides

The rule mandates five APIs. Each API must conform to a specific HL7 Da Vinci or CARIN Implementation Guide (IG). IGs are the technical specifications — they define the FHIR resources, profiles, operations, and security requirements.

API	Required IG	Key Standards	Net New in CMS-0057-F?
Patient Access (enhanced)	CARIN BB 2.0 + PAS (for PA data)	FHIR R4, USCDI v3	Existed in CMS-9115-F; now must include PA data
Provider Access	HL7 Da Vinci PDex	FHIR R4, USCDI v3, patient opt-out	New
Payer-to-Payer	HL7 Da Vinci PDex	FHIR R4, patient opt-in	New (replaces attestation-based version)
Prior Authorization	HL7 Da Vinci CRD + DTR + PAS	FHIR R4; CDS Hooks	New (flagship capability)
Provider Directory	HL7 Da Vinci Plan-Net	FHIR R4	Existed in CMS-9115-F; continues

The hardest lift is the Prior Authorization API because it requires three distinct but interlocking IGs (CRD, DTR, PAS) plus integration with external provider systems (EHRs via CDS Hooks, EHR-embedded FHIR clients, or external PAS endpoints). Payers that previously only implemented Patient Access and Provider Directory under CMS-9115-F cannot simply extend existing infrastructure — the PA API is a net-new engineering effort.

Vendor Readiness Matrix

Tier 1: Production-Ready FHIR API Vendors

These vendors have live FHIR API deployments against all four net-new Da Vinci IGs (CRD, DTR, PAS, PDex) and public customer references as of Q1 2026.

Cohere Health — Cohere Connect

Position: AI-native payer-side PA platform; full FHIR API suite branded as “Cohere Connect”
IGs covered: CRD, DTR, PAS, PDex (full suite)
Customer footprint: 12M+ PA requests/year across 600,000+ providers; payer customers include major regional and national MA plans (specific names not publicly disclosed)
Differentiator: AI auto-determination (~85% real-time approval rate) layered on top of FHIR APIs — most competitors offer APIs without intelligent decisioning
Weakness: Payer-only; does not serve providers or pharma manufacturers directly
CMS-0057-F readiness score: High — production deployments, full IG coverage, AI capability above baseline API plumbing

Availity — CMS-0057-F Interoperability Suite

Position: Largest real-time health information network in the U.S. (serves 95%+ of commercial claims volume); launched CMS-0057-F Interoperability Suite in 2024
IGs covered: CRD, DTR, PAS, PDex, Plan-Net, CARIN BB
Customer footprint: 2M+ provider users, 95%+ of U.S. commercial payers; national scale on payer portal infrastructure
Differentiator: Multi-payer network already in production; existing payer relationships reduce onboarding friction for CMS-0057-F extensions. Combines FHIR APIs with workflow automation and data orchestration.
Weakness: Legacy portal business is a large installed base that may slow pure-FHIR strategy; some payers use Availity for claims but procure CMS-0057-F from a specialist
CMS-0057-F readiness score: High — production toolkit live, payer relationships in place

Edifecs — Interoperability & CMS Compliance

Position: Payer-focused interoperability middleware; long history in Medicare Advantage encounter data and HIPAA transactions
IGs covered: All five CMS-0057-F APIs with certified FHIR deployments
Customer footprint: 20+ of the top 25 U.S. health plans; embedded in Medicare Advantage encounter and RAPS workflows
Differentiator: Deep payer technical operations expertise; integrates with legacy claims systems more effectively than pure-cloud FHIR platforms
Weakness: Not a PA decisioning platform — typically deployed alongside a UM vendor (Cohere, eviCore, Carelon) or payer’s internal UM team
CMS-0057-F readiness score: High — production payer deployments; compliance-track record

CareEvolution — MyFHR / MyDataHelps / Orchestrate

Position: Mid-market payer and provider FHIR platform; strong presence in academic medical centers and Medicaid programs
IGs covered: All five APIs; Da Vinci reference implementation contributor
Customer footprint: Dozens of Medicaid MCOs and regional payers; public-sector strength
Differentiator: Participates in Da Vinci Project working groups; often first-to-spec on new IG releases
Weakness: Smaller scale than Cohere, Availity, or Edifecs; less brand recognition in commercial MA market
CMS-0057-F readiness score: High — technically mature; may lack sales bandwidth for late-onboarding payers

Tier 2: Adjacent + Retrofitting

These vendors dominate adjacent workflows (pharmacy ePA, payer portal, core admin) and are building FHIR-based medical benefit PA capabilities. As of Q2 2026, most have partial IG coverage or beta deployments but not full production against all four net-new IGs.

CoverMyMeds — Dominant Pharmacy ePA, Medical Benefit Expansion

Position: ~90% of U.S. pharmacy ePA transactions; $4B revenue segment within McKesson RxTS; free-to-provider model subsidized by pharma manufacturer services
CMS-0057-F fit: Strong pharmacy benefit PA automation — but CMS-0057-F is primarily a medical benefit rule. CoverMyMeds’ core NCPDP SCRIPT-based workflow does not address the FHIR-based medical PA APIs.
FHIR strategy: Expanding into medical benefit PA via the broader McKesson RxTS platform; progress visible but not publicly branded as a CMS-0057-F compliance suite
Pharma services implications: Remains dominant for specialty Rx hub integrations and manufacturer-funded PA support programs. Medical benefit PA (J-code oncology, infusions, DME) will need a different vendor.
CMS-0057-F readiness score: Medium — adjacent leader; medical benefit FHIR is a work in progress

Surescripts — Transaction Network, Expanding to FHIR

Position: Dominant clinical messaging network (e-prescribing, formulary, benefit check); ~2B transactions/year
CMS-0057-F fit: Network infrastructure plays well for Payer-to-Payer and Provider Access APIs; building CRD/DTR/PAS capabilities on top of existing payer connectivity
FHIR strategy: Heavy investment in FHIR-based real-time benefit check (RTBC) and moving into PA. Existing 1M+ provider/EHR integration is a natural on-ramp.
Pharma services implications: If Surescripts wins FHIR-based PA market share, could become the dominant ePA network across both pharmacy AND medical benefits — a much larger moat than CoverMyMeds’ pharmacy-only dominance.
CMS-0057-F readiness score: Medium — strong infrastructure position; full FHIR PA API production unclear as of Q1 2026

HealthEdge — HealthRules Payer + FHIR Modules

Position: Modern core admin platform for health plans (payer’s system of record for membership, claims, adjudication); replacing legacy systems at mid-market and upmarket payers
CMS-0057-F fit: Built-in FHIR API capabilities; CAQH CORE aligned; natural compliance path for payers already on HealthRules
Customer footprint: 80+ health plans; growing MA/Medicaid share
Differentiator: Integrated compliance — payers using HealthRules can check CMS-0057-F as a platform feature rather than buying a separate middleware layer
Weakness: Only covers HealthRules customers; not a standalone CMS-0057-F vendor for payers on other core admin platforms (Cognizant TriZetto Facets, Oracle, custom)
CMS-0057-F readiness score: Medium-High for HealthRules customers; irrelevant to others

Inovalon — Data + Analytics + FHIR

Position: Payer data and analytics platform; SaaS revenue model with MA quality (HEDIS, RADV) as anchor use case
CMS-0057-F fit: Building FHIR-based compliance suite leveraging existing payer data integrations
Customer footprint: Most large MA plans; Medicaid MCOs
Differentiator: Data analytics depth — CMS-0057-F transparency metrics will need reporting infrastructure Inovalon can provide
Weakness: Not historically a PA workflow vendor; compliance positioning less established than Cohere or Availity
CMS-0057-F readiness score: Medium — partial coverage; analytics layer strong

Smile Digital Health (Smile CDR) — Open-Source HAPI FHIR Commercial Distribution

Position: Leading commercial distribution of HAPI FHIR (open-source Java FHIR server); deployed by payers building in-house
CMS-0057-F fit: Provides the FHIR server substrate for payers who don’t want to license a full stack
Customer footprint: Dozens of payers and HIEs; strong Canadian and U.S. adoption
Differentiator: Open-source foundation; avoids vendor lock-in; suitable for payers with strong internal engineering
Weakness: Does not include IG-specific business logic (CRD rules, DTR questionnaire engines) — payers must build these themselves or buy from a partner
CMS-0057-F readiness score: Medium — strong technical foundation; partial solution

Tier 3: Complementary / Long-Tail PA Automation

These vendors do not compete for the CMS-0057-F FHIR API mandate directly but solve the ~40% of PAs that remain phone, fax, or portal-based — either because the payer hasn’t deployed FHIR APIs, or because the case requires human negotiation (complex specialty drugs, peer-to-peer appeals, out-of-network approvals).

Infinitus Systems — “Eva” Voice AI

Position: AI-powered voice agent that calls payers to complete PA and benefit verification; 6M+ calls, 100M+ automated minutes
CMS-0057-F fit: Complementary — Infinitus automates phone-based PA for payers that lack FHIR APIs or for complex cases where FHIR alone doesn’t close the loop. As FHIR adoption grows, Infinitus addresses the shrinking-but-persistent long tail.
Pharma services implications: Hub vendors will increasingly blend FHIR API-first routing with Infinitus voice fallback. Together they cover a much higher percentage of PA volume than either alone.
Positioning in 2027: Still highly relevant — commercial and ERISA plans outside CMS-0057-F will continue to rely on phone PA

SuperDial — Provider-Side Voice PA

Position: AI voice automation for provider PA calls; 1M+ calls, 4x productivity lift for billing teams
CMS-0057-F fit: Complementary — same thesis as Infinitus but provider-side
Differentiator: Partnered with Omega Healthcare (March 2026) for BPO channel distribution
Positioning in 2027: Grows alongside FHIR APIs; different buyer (provider back office vs. payer platform)

Rhyme (formerly Infinitus — note: different companies with similar names) — AI-Powered PA Submission

Position: AI PA submission, tracking, and appeal generation for provider offices
CMS-0057-F fit: Complementary — automates provider-side submission against payer portals; will benefit from FHIR but not dependent on it
Positioning in 2027: Strong provider-side workflow tool; may partner with Cohere, Availity, or Epic for FHIR-first handoff

Cohere Health (AI Auto-Determination Layer)

Position: Listed in Tier 1 for its FHIR API suite; listed here for its payer-side AI auto-determination capability
CMS-0057-F fit: Cohere’s AI runs on top of the FHIR API infrastructure — competitors that ship only API plumbing without AI decisioning leave payers with the hardest problem (actually making the PA decision faster). This is Cohere’s defensible moat.
Positioning in 2027: The combination of API + AI could drive Cohere to become the dominant CMS-0057-F category leader if execution holds

eviCore by Evernorth — Incumbent Outsourced UM at Scale

Position: Dominant outsourced UM/PA vendor covering 100M+ lives; 120M+ annual clinical determinations
CMS-0057-F fit: Incumbent under disruption — eviCore performs the clinical determinations that CMS-0057-F APIs are designed to enable faster. Its margins depend on human clinical review; AI auto-determination (Cohere-style) could erode the core business.
Positioning in 2027: Major open question. eviCore will almost certainly roll out FHIR APIs but will need to defend against AI-native entrants. Evernorth (parent) has scale and distribution to invest, but incumbent innovation has been slow.
Risk flag: eviCore’s 13% wrongful denial rate per OIG 2022 is precisely the evidence base that motivated CMS-0057-F. Transparency metrics in 2026-2027 could accelerate share loss.

Tier 4: Provider-Side EHR and Point-of-Care FHIR

The demand side of the CMS-0057-F ecosystem — EHRs that must consume the APIs and expose them to clinicians.

Epic — MyChart + Payer Platform; FHIR-first by design; 2027-ready for most use cases. The strongest CMS-0057-F consumer.
Oracle Health (Cerner) — FHIR roadmap committed; execution uneven post-acquisition
Athenahealth — Cloud-native; FHIR roadmap in progress
eClinicalWorks — Mid-market; FHIR capabilities developing
Greenway, NextGen — Lagging; risk of losing share to FHIR-forward competitors

Buyer Decision Framework

For pharma manufacturers, hub vendors, and FRM teams evaluating partners in 2026-2027, here is a decision framework for assessing CMS-0057-F readiness:

For Hub Vendors Evaluating PA Automation Partners

Does the partner have FHIR API deployments against your top-3 payers by volume? If no, time-to-value suffers.
Does the partner handle both pharmacy benefit (NCPDP SCRIPT) AND medical benefit (Da Vinci CRD/DTR/PAS)? Pharma services increasingly require both workflows.
What is the PA decision speed improvement with and without the partner’s platform? Benchmark against pre-FHIR baselines.
Does the partner have a voice AI fallback for non-FHIR payers? Commercial, ERISA, and Part D are still phone-based.

For Manufacturers Evaluating Field Reimbursement (FRM) Programs

Does the FRM vendor’s training curriculum include CMS-0057-F FHIR PA workflows for MA/Medicaid populations?
Does the FRM vendor maintain a live dashboard of payer-specific PA decision times tied to the new transparency metrics?
Are FRMs trained on the difference between pharmacy benefit (out of scope) and medical benefit (in scope) PA?

For Payers Selecting a CMS-0057-F Platform

Is the vendor in production with at least one payer against all four net-new IGs (CRD, DTR, PAS, PDex)?
Does the vendor provide AI auto-determination or just API plumbing? API-only vendors leave the hardest problem unsolved.
Can the vendor integrate with your core admin system (HealthRules, Facets, proprietary)?
What is the estimated 2-year TCO including licensing, implementation, ongoing maintenance, and compliance reporting?
What is the vendor’s roadmap against CMS-0062-P if the drug proposal is finalized, and how much of that roadmap is reusable for future commercial or Part D convergence?

Implications

For hub and patient-services buyers: FHIR readiness should become an explicit RFP scoring item for PA-heavy products, especially medical-benefit therapies. Buyers should ask whether the hub can consume payer API responses, route exceptions, and preserve status visibility for patients, prescribers, field teams, and specialty pharmacy partners.

For FRM programs: FRM playbooks need to distinguish medical-benefit FHIR workflows from pharmacy-benefit ePA. The strongest vendors will train teams on payer-by-payer decision timing, API availability, documentation requirements, and escalation paths when the standard API flow fails.

For payer technology selection: Demand production references and implementation timelines, not generic conformance claims. API-only vendors may satisfy compliance but leave clinical decisioning, exception handling, and transparency reporting as separate workstreams.

For market structure: Vendors without production deployments by late 2026 face consolidation risk. Vendors that bridge FHIR APIs, AI auto-determination, NCPDP pharmacy workflows, and unstructured phone/fax fallback are positioned to capture the broader commercial PA modernization wave if rules converge beyond CMS-0057-F.

Competitive Dynamics 2026-2028

Consolidation scenarios:

Availity + Edifecs — Natural consolidation candidates; both are payer-focused middleware with overlapping customer sets. A merger would create a dominant CMS-0057-F category leader but regulatory scrutiny is possible.
Cohere Health strategic exit — $200M+ funding, unicorn trajectory, could be acquired by a major payer (UnitedHealth, Humana), a core admin platform (HealthEdge), or a health tech platform (Epic, Oracle Health)
Surescripts medical benefit expansion — Either organic build or acquisition of a Da Vinci-focused vendor (CareEvolution, Smile CDR) to round out medical PA capabilities
eviCore disruption — Evernorth may double down, spin off, or allow share loss; the outcome depends on internal AI investment pace

New entrants to watch:

Epic as FHIR platform — If Epic productizes its Payer Platform for CMS-0057-F, it could capture payer customers directly, squeezing middleware vendors
Microsoft + Cohere Health — October 2025 partnership for ambient PA; could enable Cohere to reach physician-in-the-loop PA via Copilot/Dragon
Startups building on Smile CDR — Open-source FHIR foundation enables rapid entrants; watch for vertical-specific solutions (oncology PA, rare disease, behavioral health)

Failure scenarios:

Vendors with partial IG coverage and no production deployments by Q4 2026 will miss the initial compliance wave and likely consolidate
Payers that delay vendor selection past Q2 2026 face near-certain non-compliance in Jan 2027 given 12-18 month typical implementation timelines

CMS-0057-F: Interoperability & Prior Authorization Final Rule — Underlying regulatory concept
FHIR (Fast Healthcare Interoperability Resources) — API/resource standard underlying the rule and vendor readiness claims
Prior Authorization in Specialty Pharma — Market context
AI Disruption in Pharma Services — Broader AI PA automation landscape
Hub Services Market Analysis — Hub vendors must integrate with FHIR APIs

Analyst Notes

The “all-in-one vs. best-of-breed” question is the most important for payers. Cohere Health offers API + AI in one stack; Availity/Edifecs offer API without AI decisioning. Payers choosing API-only vendors will need to pair with a UM vendor (eviCore, Carelon) or invest in internal clinical logic. The all-in-one play is appealing but concentrates vendor risk.
Pharma services vendors are the downstream beneficiary. Hub vendors (AssistRx, CareMetx — now operating the legacy Lash Group hub post Apr-2026 Cencora divestiture, Valeris) that integrate with payer FHIR APIs will deliver faster time-to-therapy than competitors still reliant on fax and phone. Expect hub RFPs in 2026-2027 to include FHIR integration scorecards.
Drug prior-auth expansion is no longer hypothetical. CMS-0062-P, released April 10, 2026, already proposes a next step into drug PA. That materially raises the strategic value of vendors that can bridge NCPDP pharmacy workflows, drug-level reporting, and FHIR-based payer APIs rather than treating CMS-0057-F as a purely non-drug project.
Commercial PA reform is the much larger prize. ~160M commercially insured lives are outside CMS-0057-F. State-level action (TX, LA, NY) has started; federal commercial PA reform under ERISA authority would require new legislation but is on advocacy agendas. Any vendor positioned as multi-payer (Availity, Cohere, Surescripts) benefits if commercial rules converge.
eviCore is the most at-risk major incumbent. Dominant market share, but its economics depend on human clinical review at volume. AI auto-determination + FHIR API + CMS transparency metrics is a three-front attack. Watch Evernorth investor commentary on eviCore margins in 2027 earnings.
Confidence caveat: Vendor claims of “production-ready” CMS-0057-F deployments vary in specificity. Several vendors claim IG conformance but have not published HL7 Da Vinci testing harness results. Buyers should demand verifiable production references and pilot-to-prod timelines before contracting.
Confidence level: Medium. Based on public vendor marketing, analyst coverage (Firely, CareEvolution, Tegria), and CMS rulemaking documents. Specific payer-vendor contracts and production status are not always publicly disclosed; actual readiness is an evolving picture through 2026.