CMS-0057-F Platform Overview.
What the rule requires and how Redix covers the core APIs and prior authorization workflow.
Compliance deadline: January 1, 2027. This document provides an executive overview of CMS-0057-F implementation requirements.
Looking for the compliance suite? CMS-0057-F Compliance Suite - Want to try the workflow? PAS Demo
Key distinction. CMS requires impacted payers to host the required APIs. Providers are users of PAS and Provider Access API, not hosts. Regulatory responsibility stays with the payer. This is critical for implementation planning.
What CMS-0057-F Requires
Core API Suite
- Patient Access API - Members access PA history and coverage data
- Provider Access API - Providers query PA status and patient data
- Payer-to-Payer API - Consent-based data exchange when members switch plans
- Da Vinci PAS - PA submission, inquiry, update, and cancel via FHIR
Operational Requirements
- Expedited PA decisions within CMS-defined timeframes (payer-type dependent)
- Standard PA decisions within CMS-defined timeframes (payer-type dependent)
- Public reporting / metrics required beginning in 2026
Scope note. Provider Directory API is required for certain payer types under CMS interoperability rules; it is not included in this suite at this time.
Primary integration path: X12 278 to FHIR. For organizations without existing X12 infrastructure, RMap to FHIR is supported as an alternative input path.
How Redix Covers the Core APIs
Redix acts as the core translation and compliance layer behind your FHIR API. Built for payers, platform teams, and systems integrators (SIs), we handle the positional X12 translation so you can focus on portal orchestration.
Da Vinci PAS
- $submit, $inquire, $cancel, $update
- FHIR-based PAS workflows with optional X12 278
- ClaimResponse + Provenance tracking
Patient Access API
- Member access to PA history
- Claims and EOB exposure
- FHIR R4 + customer-managed auth
Provider Access API
- PA status queries
- Patient clinical data access
- Attribution-based access control
Payer-to-Payer API
- Member consent management
- Bulk data export ($export)
- Coverage transition support
CRD - Coverage Requirements
- CDS Hooks integration
- "Is PA required?" real-time check
- EHR workflow integration
DTR - Documentation Templates
- FHIR Questionnaire server
- Dynamic form rendering
- Pre-populated data fields
Who Deploys What
Understanding regulatory responsibility is critical for implementation planning.
| API | Payer Hosts | Provider Role |
|---|---|---|
| Patient Access API | Required | N/A |
| Provider Access API | Required | Client only |
| Payer-to-Payer API | Required | N/A |
| Da Vinci PAS | Required | Client only |
One Suite, Two Use Cases
Payers Use the Suite To
- Host the core APIs (payer-hosted) for CMS-0057-F workflows
- Receive and process PA submissions
- Expose Patient Access for members
- Enable Payer-to-Payer data exchange
- Host CRD/DTR for coverage requirements
- Support X12 278 integration where required - including FHIR to X12 conversion (available via private technical review)
Providers Use the Suite To
- Submit PAS via payer-hosted APIs, using X12 278 to FHIR as the primary workflow
- Use RMap to FHIR as an alternative path when X12 is not available
- Call payer's CRD to check if PA is required
- Call payer's DTR to get required forms
- Submit, inquire, update, cancel PAs
- Track ClaimResponse + Provenance
Implementation Timeline
Exact dates and API applicability vary by payer type.
(varies by payer type)
milestones
(varies by payer type)
Evaluate Redix for Your Platform
Whether you are building a custom prior authorization gateway, integrating with an existing portal, or looking for an OEM translation component, we can help you scope the correct boundaries for your CMS-0057-F architecture.
Forward X12-to-FHIR conversion is available for immediate sandbox testing. Reverse FHIR-to-X12 evaluation is conducted via a guided technical review using your synthetic fixtures.
Related Documentation
Architecture
Technical architecture for your engineering team.
Test Workflow
Step-by-step integration and testing guide.
Compatibility Matrix
Detailed compliance mapping against CMS requirements.
API Reference
Endpoints, authentication, and code samples.
Product Page
CMS-0057-F Prior Authorization Suite overview.
PAS Demo
Try the Da Vinci PAS workflow with sample data (no PHI).