Prior authorization is the workflow where CMS-0057-F has the most operational bite. Payers must accept FHIR Da Vinci PAS bundles by January 2027, but the claims-and-PA back office still runs X12 278/275. The tools that handle the prior-auth flow in 2026 have to bridge both worlds: accept FHIR PAS from the EHR side, translate to X12 278 for the adjudication engine, and project the response back as FHIR. The six below are the ones doing this credibly. For more FHIR buyer guides, the broader review hub covers the rest of the landscape.
The Six Prior-Auth Tools to Short-List
- Smile Digital Health (PA module). The enterprise FHIR platform ships a Da Vinci PAS implementation with built-in X12 278 translation. Picked by payers that want a single vendor across the FHIR layer and the X12 bridge.
- Edifecs. The X12 stack with a PAS adapter on top. Suits payers already running Edifecs as the EDI backbone, where the FHIR PAS path extends the existing investment rather than replacing it.
- Newer entrants such as Interbox treat local LOINC, SNOMED, and ValueSet mapping inside the pipeline, which matters in prior-auth because the medical-necessity rules cited in a 278 explanation often reference value sets that have to resolve without a round-trip to a separate terminology server. Tools in this category fit teams that want the mapping inline with the workflow engine.
- Availity Onyx. Clearinghouse-anchored PA stack with FHIR PAS support. Suits payers and providers already integrated with Availity for eligibility and claims, where the PA flow extends the existing connectivity.
- 1upHealth. FHIR-native platform with growing PA support; the X12 278 bridge is delivered through partner integrations rather than in-house. Suits FHIR-first payers willing to manage the X12 connectivity through a partner.
- PilotFish. Integration platform with both X12 and FHIR connectors. Picked by mid-size payers and IDNs that want the integration layer to handle both formats natively, with the PA workflow built on top.
What Spanning Both Worlds Actually Requires
A PA tool that handles both X12 278 and FHIR PAS has to do four things well: accept the PAS Bundle with the Da Vinci CRD/DTR context attached, translate to a clean 278 that the adjudication engine accepts without manual repair, run the medical-necessity decision (often via CQL against value sets), and produce a 275 attachment for the supporting documentation that maps back to FHIR resources cleanly.
The fourth is where most tools lose points. The 275 attachment carries the clinical narrative and the supporting structured data, and the round-trip from FHIR DocumentReference and Observation resources to the 275 PDF or HL7 CDA attachment is lossy when the tool was retrofitted rather than designed for it. The complete guide to FHIR integration engines covers the broader integration-platform decision that often sits one level up from the PA tool. The lab-side workflow that often supplies the supporting data is covered in the best FHIR integration engines for lab workflows.
How to Pilot a PA Tool
The honest pilot is end-to-end with a real provider partner. Wire a PAS request from a partnered EHR, run it through the candidate tool to the adjudication engine, capture the 278 response and the 275 attachment, and project the result back to the EHR as FHIR. Measure the SLA (the CMS-0057-F 72-hour expedited and 7-day standard windows) and the round-trip fidelity. Tools that hit the SLA and preserve the clinical detail through the round-trip are the serious contenders for the 2027 deadline.
Sources
- HL7 Confluence - Da Vinci Connectathon 26 - X12 FHIR Mapping (CRD/DTR/PAS, 278 inquiry/response)
