The Patient Access API is the oldest of the four CMS-0057-F endpoints and the one with the most production deployments under CMS-9115-F. That maturity is deceptive, because CMS-0057-F adds new scope that the 2021 implementations did not cover. Prior Authorization decisions must now flow to Patient Access within one business day. Annual API usage metrics are due each March 31. The platforms that handled CMS-9115-F well do not all extend cleanly to CMS-0057-F. Here are five worth a real evaluation in 2026. For broader context, more on CMS-0057-F compliance covers the larger picture.
1. Smile Digital Health (Smile CDR Patient Access)
Smile Digital Health has shipped Patient Access in production with multiple US payer customers since CMS-9115-F. The platform supports CARIN BB v2.0, PDex v2.1, and US Drug Formulary v2.0.1 out of the box. The PA-data-into-Patient-Access pipeline uses FHIR Subscriptions, which keeps the one-business-day window straightforward. The member-facing SMART app gallery and developer portal ship as part of the platform rather than as a custom build.
2. 1upHealth Patient Access
1upHealth came from the patient and provider API side and has one of the cleanest developer experiences in this category. The platform exposes Patient Access with full Inferno conformance and PMPM pricing that scales naturally with member count. Smaller and mid-size plans evaluating Patient Access often shortlist 1upHealth early. The developer portal and third-party app registration flow are well-engineered.
3. InterSystems IRIS for Health (Patient Access Module)
InterSystems IRIS for Health includes a Patient Access module that integrates with the broader IRIS data platform. The strength is the unified store; Patient Access reads from the same FHIR data layer that powers analytics and care management. The trade-off is enterprise pricing and a longer integration runway, typically 9 to 18 months on a brownfield deployment. Larger payers with significant on-premise hosting needs end up here.
4. Edifecs (with FHIR Layer)
Edifecs is X12-native and added a FHIR Patient Access layer for CMS-9115-F. The X12-to-FHIR conversion handles claims and EOB cleanly. The CARIN BB and PDex conformance is solid; the developer portal and member SMART app gallery were added later and feel less polished than at the FHIR-native vendors. Payers with strong existing Edifecs relationships tend to stay; payers without that history rarely add Edifecs purely for Patient Access.
5. MuleSoft Healthcare Accelerator
MuleSoft Healthcare Accelerator (Salesforce) ships a Patient Access pattern as part of the Anypoint healthcare suite. The platform fits payers who already standardize on Salesforce and MuleSoft for non-healthcare integration. The patterns are conformant; the developer portal is thin compared with the FHIR-native vendors, and the member SMART app gallery is a custom build. Best fit when MuleSoft is a strategic platform rather than a single-purpose buy.
The Operational Differences That Actually Matter
These platforms all pass Inferno. The differences appear in three operational dimensions. First, how quickly PA decisions reach the Patient Access API after the payer-side determination; the best implementations measure in minutes, the weaker ones in hours. Second, how the platform handles SMART app gallery curation; payers that have to vet every member-facing third-party app individually under CMS-0057-F appreciate platforms that ship a managed gallery. Third, how the audit logs map to the annual API usage metrics due to CMS each March 31; platforms that capture unique-patient and repeat-transfer counts natively avoid a recurring engineering line item.
The Flexpa November 2025 Patient Access API report is a useful external benchmark; the top-scoring payer implementations in that report cluster around the FHIR-native platforms above, with Edifecs deployments showing more variance.
How This Connects to Other CMS-0057-F APIs
Patient Access cannot be evaluated in isolation. The PA-data inflow comes from the Prior Authorization API. The claims data overlaps with the Payer-to-Payer Data Exchange API. Vendors that handle all of CMS-0057-F coherently end up easier to live with than vendors that solve Patient Access well but punt on the other three.
For the IG-level question of CARIN BB versus PDex for Patient Access, the PDex vs CARIN BB comparison breaks down which profile fits where. For deeper CARIN BB implementation coverage, the Top 5 CARIN BB IG implementations reviews the leading patterns.