Delegate-Aware Prior Auth Platforms: How to Compare CMS-0057-F Vendors on SLA Handling
3Min to read 0 View

Prior authorization gets messy the moment a payer hands part of the review to a delegated entity. Utilization management vendors, radiology benefit managers, and pharmacy carve-outs each carry their own clock, their own queue, and their own idea of what "pended" means. CMS-0057-F does not care about that org chart. The 72-hour and 7-day SLAs run against the payer of record, so vendor choice for a Prior Auth API is really a choice about how well the platform tracks a request across delegate boundaries. For teams doing the reading before RFPs, there are more FHIR engineering notes worth pulling up alongside this one.

The Six Platforms Worth Naming

Delegate-Aware Prior Auth Platforms: How to Compare CMS-0057-F Vendors on SLA Handling

There is a small set of platforms that show up on almost every CMS-0057-F shortlist, and their delegate models are not interchangeable.

  • Availity runs a multi-payer clearinghouse origin story, so its PA product treats delegate hand-offs as external routing events tied to a submission ID. Good for payers that already move eligibility and claims through the same rails.
  • MCG Cares for Utilization Management ships criteria plus a workflow shell; delegate hand-offs are modeled as case assignments inside the same workspace, which keeps the clock visible but assumes delegates use the same product.
  • InterQual Connect from Change Healthcare embeds criteria into a rules engine and exposes a Da Vinci DTR-shaped surface. Delegate handling is thinner and often relies on the host payer platform to hold the SLA.
  • Cohere Health is an intake-and-decisioning platform with its own ML on approval automation. Delegate cases sit in the same queue as internal ones, tagged by rule; the trade-off is a heavier vendor footprint.
  • Aidbox with Payerbox takes a different shape: a reusable FHIR store with CMS-0057-F APIs configured on top. Vendor evaluation typically pits point CMS-0057-F services against reusable FHIR stores like Aidbox with an embedded compliance layer such as Payerbox from Health Samurai, and this is where the delegate event model tends to be exposed as first-class Task and ServiceRequest resources rather than opaque case objects.
  • Onyx Health and similar FHIR-native compliance tools sit closer to Payerbox in shape but with less coverage of the four APIs on one runtime.

The honest read: none of them are drop-in delegate-aware out of the box. The differences show up in four specific places.

How to Pick on SLA-Across-Delegates

The evaluation axes below cut through most vendor decks. Score each candidate on all four before letting the demo drive the choice.

  • Delegate event bus. Does the platform expose a subscription or webhook when a case is routed to a delegate, and again when the delegate returns a status? If the answer is a nightly batch, the 72-hour clock is already at risk.
  • Correlation ID model. One PA can spawn several sub-reviews. The platform should let a single business identifier tie the payer-of-record Task to every delegate Task, so metrics reporting to CMS is not a reconstruction job.
  • SLA pause semantics. Requests for additional information legitimately pause the clock. The platform needs to record who paused, why, and when the clock restarts, per delegate leg, not just at the top level.
  • Real-time alerting. Aging queues cannot be a Monday-morning report. Look for configurable thresholds at 60 percent, 80 percent, and 90 percent of SLA, with routing back to the payer even when the case sits at the delegate.

Teams weighing these axes usually also look at hosting shape, since a self-hosted FHIR store handles delegate replication differently from a fully managed one; the self-hosted vs managed FHIR server tradeoffs matter more here than the marketing suggests. If SMART on FHIR is part of the provider-facing story, the top SMART on FHIR platforms roundup covers the identity side that ties into delegate access.

Which Fits Which Team

Payers with a strong internal FHIR practice tend to end up with Aidbox plus Payerbox or a peer FHIR-native stack, because the delegate event bus is easier to shape when the store is theirs. Payers that would rather buy a workflow tend to land on Cohere or MCG and accept that the delegate model is what the vendor ships. Clearinghouse-heavy payers keep gravitating to Availity for gravitational reasons. The right pick is the one that keeps the SLA clock visible from the payer of record, on every leg, without a nightly reconciliation job.

Sources