The Da Vinci PAS implementation guide has been around since 2021, but 2026 is when health plans are actually shipping it, not just demoing it. With the CMS-0057-F production deadline at January 1, 2027, vendor selection is happening fast, and the gaps between products that pass the Inferno conformance suite and products that survive contact with a real claims system have become obvious. Here are five Da Vinci PAS implementation tools worth a serious look for related Prior Auth API guides and procurement shortlists in 2026.
These are not ranked. Each one fits a different payer profile, and that profile matters more than feature checklists.
1. Edifecs PAS
Edifecs comes out of the X12 world and has the deepest 278 / 275 chain on the list. For health plans whose UM systems are already X12-native, Edifecs PAS is the path of least resistance, because the round-trip from FHIR Bundle to 275 attachment to back-office UM and back happens inside one stack. The cost is that the FHIR-native experience (SMART app rendering, CDS Hooks, real-time FHIR Subscriptions) is bolted on rather than first-class. Mid-size payers with existing Edifecs licenses tend to default here for renewal continuity.
2. InterSystems IRIS for Health
InterSystems IRIS for Health is the enterprise FHIR platform with the longest health-payer reference list outside of the X12 incumbents. PAS support is part of a broader interoperability suite, and the data store is reusable for analytics and care management beyond compliance. The trade-off is enterprise pricing and longer integration timelines, often 12-18 months on a brownfield deployment. Larger payers with on-premise hosting requirements gravitate here.
3. Smile Digital Health (Smile CDR PAS)
Smile Digital Health was the first commercial Da Vinci PAS implementation to ship in production with multiple US payer customers. The Smile CDR data platform handles the FHIR storage layer, and PAS sits on top with the full CRD / DTR / PAS triad. Smile is strong on FHIR conformance, weaker on the legacy X12 round-trip without third-party converters. Mid-market plans that are FHIR-first rather than X12-first usually evaluate Smile early.
4. 1upHealth PAS Module
1upHealth approached PAS from the patient and provider API side rather than from claims. The 1upHealth platform was already a Patient Access leader, and the PAS module extends that into the provider-facing workflow. PMPM pricing makes the math simple for small payers and pinches for large ones. CDS Hooks support is among the cleanest, and the developer documentation is the most accessible of the group.
5. MuleSoft Healthcare Accelerator
The MuleSoft Healthcare Accelerator (Salesforce) is the integration-platform answer to Da Vinci PAS. It gets bought when a payer already runs MuleSoft for other integrations and treats PAS as one more pipeline rather than a dedicated FHIR application. The strength is fitting into existing Salesforce/MuleSoft estates without adding a new vendor; the weakness is that PA-specific features (CQL engine, DTR SMART app rendering, public reporting dashboards) are thin and end up needing custom development.
How to Shortlist for Your Plan
A clean way to narrow these five fast is to score each one against the eight categories in the cmspriorauth.com RFP framework. The deltas show up quickly. A plan that wants a 3-6 month go-live timeline tends to land on Smile or 1upHealth. A plan that wants to keep its X12 chain intact and minimize change to the UM system tends to land on Edifecs. A plan that already has an InterSystems data lake or a large MuleSoft footprint usually keeps its incumbent. A plan with no FHIR investment at all has the widest open field.
For the deeper architectural question of whether to stay on X12 278 or move to Da Vinci PAS first-class, the comparison of Da Vinci PAS vs Legacy X12 278 breaks the trade-off down step by step. And if you are still mapping the CRD / DTR / PAS landscape end-to-end, the CRD DTR PAS platforms guide is the right next read.