CMS-0057-F Compatibility Matrix.
What Redix covers versus customer responsibility. A decision tool for compliance officers and procurement teams.
Redix API v2.1.1 · Document revised October 2026
Want to see the workflow in action? PAS Demo →
CMS-PAS Docs:
Product
Overview
Architecture
Test Workflow
Compatibility Matrix
API Reference
Live Demo
4
CMS-0057-F API Areas Covered
2.0.1 / 2.1.0
Da Vinci PAS
R4
FHIR Version
7+
X12 Transactions
CMS-0057-F Implementation Coverage
Available Available conversion capability
Demo Demonstration capability
Scoped Customer-specific implementation
Customer Customer responsibility
| Requirement | Coverage | Customer Responsibility | Notes |
|---|---|---|---|
| Patient Access API | Demo | Connect data sources | Demonstrated on sample data; production implementation scoped per customer; you connect member claims/coverage sources |
| Provider Access API | Demo | Connect PA/clinical sources | Demonstrated on sample data; production implementation scoped per customer; you connect clinical/PA sources and define access policies |
| Payer-to-Payer API | Demo | Consent management | Consent API demonstrated; consent logic and production deployment are yours |
| Da Vinci PAS | Demo | Clinical decisions | $submit and $inquire demonstrated with simulated decisions (updates and cancellations through $submit); you make PA decisions |
| Expedited PA timeframe | Customer | Workflow execution | Your review process meets the timeframe; Redix carries request priority and decision fields |
| Standard PA timeframe | Customer | Workflow execution | Your review process meets the timeframe; Redix carries request priority and decision fields |
| Public Metrics Reporting | Customer | Reporting & publication | Redix provides conversion logs and FHIR Provenance in converted output; your systems hold the decision data, and you compile and publish reports |
| X12 278 Conversion | Available | — | X12 278 to and from FHIR R4 for supported content; RMap to FHIR supported when X12 is not available |
| CRD (Coverage Requirements) | Demo | Rule configuration | CDS Hooks service demonstrated with sample rules; your coverage rules and EHR integration are scoped per customer |
| DTR (Documentation Templates) | Demo | Form configuration | Questionnaire service and SMART launch demonstrated; your questionnaires, CQL and EHR registration are scoped per customer |
| Production integration | Scoped | Hosting, security, data connections | Production scope, security and integrations are agreed for each customer |
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.
Build vs. Buy Comparison
Estimates vary by integration scope, data availability, and deployment model.
| Capability | Build In-House | Redix Suite |
|---|---|---|
| Time to production | Depends on scope and team | Estimated after requirements and interface assessment |
| FHIR R4 expertise | In-house FHIR and X12 expertise required | Reduced (API-first; integration scope dependent) |
| X12 278 conversion | Build from scratch | Built on AnyToAny Engine |
| Da Vinci PAS conformance | Interpret IG, build, test | Tested sample output passed PAS 2.0.1 and 2.1.0 validation (evidence available during evaluation) |
| Ongoing maintenance | Your team, indefinitely | Redix support + updates |
| Audit trail | Build audit trail system | FHIR Provenance (resource origin) in converted output; access and event audit logging defined for the deployment |
| Estimated cost | Estimated after requirements and interface assessment | Licensed software; implementation estimated after requirements and interface assessment |
Technical Specifications
| Category | Supported |
|---|---|
| FHIR Version | R4 (4.0.1) |
| Da Vinci PAS IG | 2.0.1 (STU 2); tested sample output also passed 2.1.0 (STU 2.1) validation |
| X12 Transactions | 278, 270/271, 276/277, 837 (P/I/D), 835, 834, 999/TA1 |
| Deployment | On-premises and Docker for the conversion services; private cloud and Kubernetes assessed per customer |
| Databases | SQLite in the demo; customer database options assessed per deployment |
| Authentication | API keys for the demo; production authentication agreed for the deployment |
| Encryption | TLS 1.2+ required |
CMS-0057-F Timeline
Exact dates and API applicability vary by payer type.
Jan 1, 2026
Operational requirements start
(varies by payer type)
(varies by payer type)
Mar 31, 2026
Initial public reporting
milestones
milestones
Jan 1, 2027
API requirements start
(varies by payer type)
(varies by payer type)
Related Documentation
Platform Overview
What CMS requires and where Redix fits.
Architecture
Deployment models, components, and integration patterns.
Test Workflow
Step-by-step integration and testing guide.
API Reference
Endpoints, authentication, and code samples.
Product Page
CMS-0057-F Prior Authorization Suite overview.
PAS Demo
Preview the ePA workflow with sample data — CRD, DTR, PAS submission and tracking.