The 72-hour expedited and 7-day standard decision SLAs in CMS-0057-F took effect on January 1, 2026, before the rest of the API requirements. That order is intentional. CMS wanted the operational discipline in place before the public-facing endpoints went live. For health plans evaluating FHIR ePA platforms in 2026, the SLA question is no longer "can we technically respond in 72 hours" but "can we prove we do, automatically, across every submission channel and every delegated entity". Here are the FHIR solutions that meet that bar in production. For broader context, CMS-0057-F readiness coverage sets the larger frame.
The Real Operational Question
A 72-hour clock is easy to claim and hard to maintain when work crosses delegate boundaries. A typical Prior Auth submission lands in the FHIR PAS endpoint, gets routed to the payer UM system, may be delegated to a specialty benefit manager, comes back through a clinical reviewer, and finally returns as a CommunicationRequest or Communication resource. Each handoff is a point where the SLA can quietly run over. Platforms that handle SLA tracking well treat the FHIR Task resource as the system of record and never let the clock be invisible.
Smile CDR with Native Task Tracking
Smile Digital Health uses FHIR Task as the primary operational resource for Prior Auth tracking. Each PAS submission generates a Task, status transitions are auditable, and the SLA clock is computed against Task.authoredOn rather than the back-office UM timestamp. The reporting layer reads the same Task history for the CMS public metrics report. The integration with FHIR Subscriptions makes it straightforward to wire delegate handoffs into the timeline.
InterSystems IRIS for Health (Workflow Engine)
InterSystems IRIS for Health includes a workflow engine that handles PA routing with SLA awareness baked in. The engine supports timer-based escalations, delegate-aware routing, and CMS-aligned reporting outputs. For larger payers with complex delegation arrangements (carve-out behavioral health, specialty drug benefits, dental), the IRIS workflow engine handles the routing complexity that lighter FHIR stacks leave to the customer.
Edifecs Smart Trading with FHIR ePA Layer
Edifecs Smart Trading provides SLA tracking that inherits from the X12 era and was extended to the FHIR ePA layer in 2024. The strength is end-to-end visibility from the FHIR Bundle into the X12 278 / 275 chain, including clearinghouse acknowledgments. The trade-off is that the SLA dashboards still feel X12-shaped; FHIR-native teams sometimes find the model harder to query than they expect.
1upHealth ePA with FHIR Subscriptions
1upHealth implements SLA tracking through FHIR Subscriptions and Task resources, similar to Smile but with a different operational philosophy. The platform leans on event-driven notification, so every state change emits a Subscription event the payer can route into existing alerting infrastructure. The model fits cloud-native payer operations teams well.
Open-Source Reference Pattern (Da Vinci + Custom Workflow)
A few payers, often the larger ones with engineering capacity, build their SLA tracking layer on top of the HL7 Da Vinci reference implementations using a custom workflow service (Camunda, Temporal, or similar). The build cost is high. The benefit is full control over the SLA model, reporting, and integration. This path makes sense only when the payer's PA volume justifies the engineering investment and the in-house team can own the operational maturity.
What CMS Actually Wants in the Annual Report
The CMS annual report due each March 31 asks for approval rate, denial rate, average decision time, and appeal volume across the PA program. The platforms above all capture the underlying data; the difference is how much engineering work it takes to produce the report. Solutions that ship the report as a built-in capability avoid the recurring engineering line item. Solutions that capture data but require custom dashboards leave the work on the payer.
For the medical-necessity rule side of the SLA equation, the Top 5 CQL Engines for Medical Necessity Decisions in Prior Auth covers the runtime layer. For provider-side workflow integration, the SMART App Launch tools for ePA inside the EHR covers the entry point.