CMS-0057-F added Da Vinci PAS as a required Prior Authorization API, but it did not retire X12 278 / 275. Both will live side by side inside US health plans through 2027 and beyond. The strategic question for a payer in 2026 is not "FHIR or X12" but "which one becomes the system of record". The answer reshapes vendor selection, integration cost, and the long-term shape of the UM stack. This comparison lays out the practical trade-offs so FHIR vendor evaluation guides can be applied with eyes open.
The Short Answer
For most US health plans in 2026, the right architecture treats the FHIR layer as the public-facing API surface and keeps X12 278 / 275 as the internal back-office protocol, with a clean converter sitting between them. The exceptions are small and depend on the size of the existing X12 investment and the appetite for replatforming.
Where X12 278 Still Wins
X12 278 has decades of operational maturity. Clearinghouse contracts assume it. UM-system vendors built their adjudication engines around it. EDI pipelines, audit logs, and back-office reporting all speak X12 fluently. For payers with these investments, replacing X12 inside the back office means rebuilding multiple integrations at once, which is the wrong scope for a CMS-0057-F deadline.
X12 also handles attachment-heavy PA submissions (clinical documents, imaging) more straightforwardly than a clean FHIR-Bundle-and-DocumentReference pattern. Payers whose denial logic depends heavily on attachment review tend to keep X12 as the canonical format and FHIR as a translation surface.
Where Da Vinci PAS Wins
Da Vinci PAS wins on the provider experience. The Coverage Requirements Discovery (CRD) and Documentation Templates and Rules (DTR) pillars are FHIR-native by design and use SMART App Launch to render the payer-specific form inside the provider EHR. Trying to deliver the same workflow over X12 alone is awkward; the CDS Hooks pattern that makes CRD valuable does not have an X12 equivalent.
Da Vinci PAS also wins on the reporting side. CMS-0057-F requires public PA reporting metrics (approval rate, denial rate, decision time, appeal rate). FHIR Bundles carry the structured data needed for these metrics cleanly. X12 transactions are not built for that kind of analytical readout, and most payers end up extracting the same fields into a separate data warehouse before they can report.
The Hybrid Architecture That Works
The architecture that survives the CMS-0057-F deadline cleanly in 2026 has three layers. The outer surface is Da Vinci PAS (and CRD / DTR), exposed to providers and consumed by their EHRs. A conversion layer turns FHIR Bundles into X12 275 attachments and back, with a translation cache for performance. The inner system stays X12 278 going into the UM adjudication engine, with the decision flowing back out the same path.
This architecture lets a payer ship the FHIR API for CMS conformance without disrupting the back-office decision pipeline. Edifecs, Smile Digital Health, InterSystems IRIS, and 1upHealth all support this pattern, with different opinions about which layer owns the canonical record.
How the Choice Affects Vendor Selection
The two ends of the spectrum land on different vendors. Payers that decide FHIR is the new system of record gravitate toward FHIR-native platforms with X12 connectors bolted on; Smile Digital Health and 1upHealth fit this profile. Payers that decide X12 stays primary and FHIR is the public API surface tend to stay with X12-native vendors that added FHIR layers on top; Edifecs and Rhapsody fit this profile. Hybrid stacks where neither layer dominates are usually built around InterSystems IRIS for Health, which is comfortable at both ends.
The Renewal-Decision Test
A useful test during 2026 vendor renewal is to ask the incumbent which layer they consider the system of record. The answer reveals more than feature lists do. Vendors that hedge or claim "both equally" often have neither, and the integration pain shows up in months three through six of the deployment.
For a tighter look at the FHIR-native platforms specifically, the Top 5 Da Vinci PAS implementation tools covers the leaders. For the X12-side question, the FHIR ePA solutions that handle X12 278 / 275 round-trip breaks down where each integration sits.