CMS Interoperability Compliance

CMS-0057-F compliance consulting, Prior Authorization API development, Patient Access API implementation, and Da Vinci implementation guide conformance — meeting your regulatory obligations before the January 2027 deadline.

CMS Compliance Toolkit

Six APIs We Build for CMS Rules

Pick a tab to dive into the FHIR profiles, Da Vinci implementation guides, and X12 transactions behind each CMS-9115-F and CMS-0057-F obligation.

CMS-9115-F · Live since 2021

Patient Access API

FHIR R4 Patient/Coverage/ExplanationOfBenefit server with USCDI v3 data classes and SMART on FHIR OAuth — the API that lets members pull claims and clinical data into third-party patient-facing apps.

  • FHIR R4 Patient + Coverage + EOB
  • USCDI v3 data classes
  • CARIN Blue Button IG
  • SMART on FHIR OAuth 2.0
  • Da Vinci PDex profiles
Explore FHIR APIs
CMS-9115-F · Da Vinci Plan-Net

Provider Directory API

Public, machine-readable Plan-Net IG directory of in-network Practitioners, Organizations, Locations, HealthcareServices — no auth gate, refreshed from credentialing systems.

  • Da Vinci Plan-Net IG
  • Practitioner / PractitionerRole
  • Organization / Location
  • HealthcareService / InsurancePlan
  • NPI sync from credentialing
CMS-0057-F · January 2027

Electronic Prior Authorization

Three-step Da Vinci chain replacing fax/phone PA: CRD coverage discovery, DTR documentation gathering, PAS claim submission with Claim/ClaimResponse/Task. 72-hour urgent / 7-day standard SLA.

  • Da Vinci CRD (coverage)
  • Da Vinci DTR (questionnaire)
  • Da Vinci PAS (submit + decide)
  • X12 278 bridge
  • PA metrics public reporting
CMS-0057-F · January 2027

Payer-to-Payer Data Exchange

When a member changes plans, 5 years of claims and clinical history move between payers via Bulk FHIR $export with member matching, opt-in consent capture, and inbound deduplication.

  • Da Vinci PDex IG
  • Bulk FHIR $export
  • 5-year lookback window
  • Member matching + dedup
  • Opt-in consent capture
$export · NDJSON · Flat FHIR

Bulk FHIR Export

SMART Backend Services-authorized population extracts for risk adjustment, HEDIS, quality reporting, and provider access. Async Task polling with NDJSON output and group-scoped filtering.

  • SMART Backend Services
  • Group-scoped $export
  • NDJSON output streams
  • Async Task polling
  • Provider Access API
837 · 835 · 270/271 · 278 ↔ FHIR

X12 EDI ↔ FHIR Bridge

Bidirectional translation between X12 EDI (claims, eligibility, prior auth) and FHIR resources (Claim, ClaimResponse, Coverage, Patient, Task) — clearinghouse infrastructure runs on X12 today, FHIR is required by 2027, both must coexist.

  • X12 837 / 835 / 270 / 271 / 278
  • HIPAA TR3 conformance
  • Da Vinci PAS X12-FHIR mapping
  • Availity / Change / Waystar
  • Denial-code translation
2027 Compliance Window

Where the Deadlines Land

CMS interoperability rules cluster around a January 2027 enforcement wave. Here's what is already live, what is coming, and which Da Vinci IGs satisfy each requirement.

2021
LIVE
CMS-9115-F

Patient Access & Provider Directory APIs

FHIR R4 Patient Access API (claims, clinical, USCDI) and public Provider Directory API (Da Vinci Plan-Net). Already enforced for Medicare Advantage, Medicaid, CHIP, and Federally-facilitated Exchange QHPs.

  • FHIR R4
  • USCDI v3
  • SMART on FHIR
  • Plan-Net IG
  • CARIN Blue Button
Jan 2027
DEADLINE
CMS-0057-F

Prior Authorization API (Da Vinci CRD → DTR → PAS)

Three-step Da Vinci chain replacing fax-based prior auth: coverage discovery, documentation gathering, claim submission. 72-hour urgent / 7-day standard SLA. Public reporting of PA metrics required.

  • Da Vinci CRD
  • Da Vinci DTR
  • Da Vinci PAS
  • X12 278 bridge
  • Electronic prior auth
Jan 2027
DEADLINE
CMS-0057-F

Payer-to-Payer Data Exchange

When members change plans, 5-year clinical and claims history must move between payers within scope. Member-initiated, opt-in consent, USCDI data classes via Bulk FHIR $export.

  • Da Vinci PDex
  • Bulk FHIR
  • 5-year lookback
  • Member matching
  • USCDI v3
Continuous
ONGOING
21st Century Cures Act

Information Blocking Compliance

HIT developers, providers, HIEs, and HINs must not interfere with the access, exchange, or use of EHI. Civil monetary penalties up to $1M per violation for HIT developers and HIE/HIN actors.

  • EHI scope
  • 8 exceptions
  • OIG enforcement
  • USCDI alignment
Compliance Pillars

What CMS Compliance Means in Practice

Three foundational obligations every payer must satisfy — and the regulatory framework, deadline, and Da Vinci IGs that define each one.

01
CMS-9115-F · 2021

Patient + Provider Access

FHIR R4 Patient Access API and public Provider Directory API. USCDI v3 data classes, SMART on FHIR OAuth, Da Vinci Plan-Net IG.

  • FHIR R4
  • USCDI v3
  • Plan-Net
  • CARIN BB
02
CMS-0057-F · Jan 2027

Electronic Prior Authorization

Three-step Da Vinci CRD → DTR → PAS chain replacing fax-based PA. 72-hour urgent / 7-day standard SLA. Public reporting of PA metrics.

  • Da Vinci CRD
  • DTR
  • PAS
  • X12 278 bridge
03
CMS-0057-F · Jan 2027

Payer-to-Payer + Bulk Data

5-year clinical and claims history exchange when members change plans. Bulk FHIR $export, Da Vinci PDex, member matching with consent.

  • Da Vinci PDex
  • Bulk FHIR
  • 5-year lookback
  • USCDI v3
What We Offer

CMS Interoperability Compliance Services

Full-scope compliance consulting for CMS interoperability and prior authorization rules — from gap analysis and architecture design through Da Vinci API development, testing, and attestation.

The Patient Access API gives health plan members standardized access to their claims, encounter, clinical, and coverage data through third-party applications. Required for Medicare Advantage, Medicaid, CHIP, and QHP issuers under CMS-9115-F, the Patient Access API must conform to FHIR R4 with specific Da Vinci implementation guides. We build and deploy Patient Access APIs that handle the full scope of required data — claims and encounter data, provider network information, formulary and drug pricing, and clinical data where available.

  • FHIR R4 Patient Access API development conforming to CARIN Blue Button and Da Vinci PDex IGs
  • Claims and encounter data exposure using ExplanationOfBenefit FHIR resources
  • Coverage, formulary, and provider directory data via FHIR endpoints
  • OAuth 2.0 and OpenID Connect authorization for third-party app access
  • Patient-facing developer documentation and API registration workflows
Implementation Timeline

CMS Compliance Implementation

Our five-phase approach takes your organization from initial gap analysis through production-ready CMS-compliant APIs — structured to meet the January 2027 deadline with time for testing, remediation, and attestation.

2–3 weeks

Gap Analysis & Requirements

We assess your current state against CMS-0057-F and CMS-9115-F requirements — evaluating existing API infrastructure, FHIR capabilities, payer data systems, prior authorization workflows, and provider directory management. The gap analysis produces a detailed findings report with a prioritized remediation plan, effort estimates, and a compliance timeline that accounts for your organization's technical maturity and the January 2027 deadline.

2–4 weeks

Architecture & Design

Our engineers design the technical architecture for your CMS-compliant API infrastructure — FHIR R4 server selection, Da Vinci implementation guide conformance strategy, OAuth 2.0 authorization model, data source integration patterns, and deployment topology. We produce architecture decision records, API specifications, data mapping documents, and a testing strategy that covers functional, conformance, and performance validation for all required APIs.

8–12 weeks

API Development (Da Vinci IGs)

We build your CMS-required APIs against the Da Vinci implementation guides — Patient Access (CARIN BB, PDex), Provider Directory (Plan Net), Prior Authorization (PAS), and Payer-to-Payer exchange (Bulk Data). Development includes FHIR resource mapping from your claims, clinical, network, and utilization management source systems, OAuth 2.0 authorization implementation, and integration with your existing data infrastructure. Each API is built incrementally with continuous conformance validation against Da Vinci IG requirements.

3–5 weeks

Integration Testing & Validation

Comprehensive testing against Da Vinci IG conformance requirements, including FHIR resource validation, search parameter behavior, authorization flows, error handling, bulk data export performance, and end-to-end workflow testing with simulated provider and member scenarios. We run Touchstone conformance tests, validate against the Da Vinci reference implementations, and conduct security testing to ensure your APIs meet both CMS requirements and industry security standards.

2–4 weeks

Go-Live & Compliance Attestation

Coordinated production deployment of all CMS-required APIs with monitoring, alerting, and performance baselines established from day one. We prepare your compliance attestation documentation, configure prior authorization metrics collection pipelines, implement public reporting disclosures, and provide post-go-live support through the initial operating period. Our team remains available for ongoing compliance monitoring, Da Vinci IG version updates, and annual attestation support as CMS requirements evolve.

Regulatory Comparison

CMS Interoperability Rules at a Glance

CMS has issued two major interoperability final rules. CMS-9115-F (2020) established foundational API requirements, while CMS-0057-F (2024) significantly expands the scope with prior authorization APIs, payer-to-payer exchange, and compliance reporting obligations.

CMS-0057-F builds on CMS-9115-F requirements. Organizations must comply with both rules. CMS-0057-F operational requirements (denial reasons, response timeframes) take effect January 2026; API and reporting requirements take effect January 2027.
Feature CMS-9115-F (2020) CMS-0057-F (2024)
Effective Date July 2021 (phased) January 2026 / January 2027
Required APIs Patient Access, Provider Directory Prior Auth, Provider Access, Payer-to-Payer, enhanced Patient Access
Applies To MA, Medicaid, CHIP, QHP MA, Medicaid, CHIP, QHP
FHIR Version FHIR R4 FHIR R4
Da Vinci IGs CARIN BB, PDex, Plan Net, Formulary PAS, CRD, DTR, PDex, Plan Net, CARIN BB, Bulk Data
Prior Auth API
Payer-to-Payer Exchange
PA Response SLA Not specified 72 hrs urgent / 7 calendar days standard
Metrics Reporting
Public Reporting
Readiness Assessment

Compliance Readiness Checklist

CMS interoperability compliance spans technical infrastructure, operational workflows, and documentation. Use this checklist to assess your organization's readiness across all three domains.

Technical Requirements

  • FHIR R4 server deployed and operational
  • OAuth 2.0 and OpenID Connect authorization flows
  • Da Vinci PAS implementation guide conformance
  • Da Vinci PDex and CARIN Blue Button conformance
  • Da Vinci Plan Net provider directory implementation
  • FHIR Bulk Data Access ($export) for payer-to-payer exchange
  • SMART on FHIR scopes and launch context support
  • FHIR resource validation against US Core and Da Vinci profiles
  • API rate limiting, throttling, and monitoring infrastructure
  • Production hosting with uptime SLAs and disaster recovery

Operational Requirements

  • Prior authorization request and response workflows automated
  • 72-hour urgent and 7-calendar-day standard PA response SLAs enforced
  • Denial reason codes mapped to X12 and FHIR value sets
  • Provider directory data synchronized from credentialing systems
  • Payer-to-payer member data exchange processes established
  • Member opt-in/opt-out consent management implemented
  • Prior authorization metrics collection pipeline operational
  • Public reporting of PA approval, denial, and turnaround metrics
  • Staff trained on information blocking compliance obligations
  • Vendor and trading partner onboarding procedures documented

Documentation Requirements

  • CMS compliance attestation prepared and reviewed
  • API documentation published for developer onboarding
  • Da Vinci IG conformance test results archived
  • Security assessment and penetration testing evidence
  • Data mapping specifications for all FHIR resource types
  • Error handling and exception processing documentation
  • Business continuity and failover procedures documented
  • Change management process for Da Vinci IG version updates
  • Audit trail and logging configuration documented
  • Annual compliance review and re-attestation schedule
Technical Expertise

Da Vinci Implementation Guide Expertise

CMS interoperability compliance depends on correct implementation of HL7 Da Vinci implementation guides. Our team has hands-on experience building against every Da Vinci IG required by CMS rules.

CMS-0057-F · Prior Authorization API

Da Vinci PAS

Prior Authorization Support implementation for real-time PA request submission, status queries, and decision responses using FHIR Claim, ClaimResponse, and Task resources. We integrate PAS APIs with your utilization management platform for automated and manual review workflows.

  • FHIR Claim
  • ClaimResponse
  • Task polling
  • UM platform integration
Da Vinci PAS submits Claim to payer; payer returns ClaimResponse via Task polling FHIR Claim use: preauth type: imaging PAYER UM policy + criteria ClaimResponse decision: approved PA #4297-X Task POLL in-progress → complete ✓ 72-hour urgent · 7-day standard SLA
CMS-9115-F + CMS-0057-F · Payer Data

Da Vinci PDex

Payer Data Exchange implementation for member clinical and claims data sharing using ExplanationOfBenefit, Coverage, and clinical FHIR resources. PDex enables the Patient Access API and payer-to-payer exchange required under both CMS-9115-F and CMS-0057-F.

  • ExplanationOfBenefit
  • Coverage
  • Patient Access
  • Payer-to-Payer
Da Vinci PDex exchanges ExplanationOfBenefit and Coverage resources between payers and to member apps PAYER A prior plan PAYER B new plan PDex $export EOB · Coverage 5-year lookback · Bulk FHIR transport · member-initiated
Consumer-directed exchange

CARIN Blue Button

Consumer-directed exchange implementation for member access to claims data via third-party apps. CARIN Blue Button defines the ExplanationOfBenefit profiles that power the Patient Access API, with FHIR R4 conformance and OAuth 2.0 authorization.

  • EOB profiles
  • OAuth 2.0
  • SMART on FHIR
  • 3rd-party apps
Member uses third-party app to authenticate via OAuth and retrieve CARIN Blue Button claims data 3RD-PARTY APP OAuth CARIN BLUE BUTTON EOB.Inpatient EOB.Outpatient EOB.Pharmacy EOB.Professional Member-authorized · OAuth 2.0 · ExplanationOfBenefit profiles
CMS-9115-F · Provider Directory API

Da Vinci Plan-Net

Provider Directory API implementation using Plan-Net profiles for Practitioner, Organization, Location, and HealthcareService resources. Plan-Net directories serve both CMS compliance requirements and operational provider search use cases.

  • Practitioner
  • PractitionerRole
  • Organization
  • Location
  • HealthcareService
Da Vinci Plan-Net resource hierarchy with Practitioner, PractitionerRole, Organization, Location, HealthcareService, and InsurancePlan Practitioner name · NPI · specialty PractitionerRole network · plan Organization network membership HealthcareService covered services Location address · hours · accessibility PUBLIC API no auth gate Refreshed from credentialing · machine-readable
Bulk Data Access · Flat FHIR

FHIR Bulk Data ($export)

Bulk Data Access implementation for payer-to-payer exchange, population health data export, and large-scale data extraction. We build FHIR $export operations that handle millions of resources with proper authorization, filtering, and error recovery.

  • $export operation
  • NDJSON streams
  • SMART Backend Services
  • Group-scoped
  • Async Task polling
Bulk FHIR $export returns NDJSON streams of Patient, Observation, Condition, MedicationRequest resources REQUEST POST /Group/X/$export 202 Task complete URLs ready NDJSON OUTPUT Patient.ndjson Observation.ndjson Condition.ndjson MedicationRequest.ndjson DiagnosticReport.ndjson Coverage.ndjson SMART Backend Services · group-scoped · streaming
TEFCA exchange purposes alignment

TEFCA Alignment

CMS rules increasingly reference TEFCA as an exchange framework for cross-organizational data sharing. We help payers align their CMS API implementations with TEFCA exchange purposes and prepare for QHIN connectivity where applicable.

  • QHIN connectivity
  • Common Agreement
  • Exchange purposes
  • Sub-Participant onboarding
CMS Da Vinci IGs align with TEFCA QHIN network and exchange purposes CMS DA VINCI IGs PAS · PDex · Plan-Net align TEFCA QHIN network 6 exchange purposes PAYER ROLE Sub-Participant via QHIN Common Agreement Bridge CMS APIs to QHIN federated query
Payer Integration

Healthcare EDI & Clearinghouse Connectivity

CMS interoperability compliance layers FHIR-based APIs on top of existing healthcare EDI infrastructure. Saga IT supports both traditional X12 EDI transactions and modern FHIR endpoints — connecting payers, providers, and healthcare clearinghouses across the full spectrum of administrative data exchange.

X12 837P · 837I · 837D

837 Claims Submission

The 837 file is the standard X12 EDI transaction for submitting healthcare claims from providers to payers. We integrate 837 Professional (837P), Institutional (837I), and Dental (837D) claim submissions through medical claims clearinghouse platforms — ensuring clean claims, proper validation, and real-time 999/277CA acknowledgment processing.

  • 837P (professional)
  • 837I (institutional)
  • 837D (dental)
  • Availity / Change Healthcare / Waystar
  • 999 + 277CA acknowledgments
  • Da Vinci PAS bridge to FHIR Claim
X12 835 · ERA · revenue cycle

835 Remittance Processing

835 files deliver electronic remittance advice (ERA) from payers back to providers, detailing payment amounts, adjustments, and denial reasons for submitted claims. We build 835 ingestion pipelines that parse remittance data, reconcile payments against submitted claims, and surface denial patterns for revenue cycle optimization.

  • ERA parsing + reconciliation
  • Payment-to-claim matching
  • CARC/RARC denial codes
  • Revenue cycle dashboards
  • FHIR ClaimResponse mapping
X12 834 · 270/271 · 278

834 Enrollment + Eligibility

The 834 transaction handles member enrollment and disenrollment between employers, health plans, and government programs. Combined with 270/271 eligibility and 278 prior authorization transactions, these EDI exchanges form the foundation that CMS-0057-F is modernizing with FHIR-based APIs.

  • 834 enrollment/disenroll
  • 270/271 eligibility verify
  • 278 prior auth (legacy)
  • FHIR Coverage + Patient mapping
  • Da Vinci PAS replaces 278
Explore FHIR APIs

Need help meeting the January 2027 CMS interoperability deadline? Our compliance team can assess your readiness and build a remediation plan.

Book a Consultation
Frequently Asked Questions

Common Questions

Related Services

Explore More Services

Keep reading

Related resources

Book a Consultation

Start Your CMS Compliance Assessment

From gap analysis to API implementation — meet your CMS interoperability requirements before the 2027 deadline.

  • 15 min conversation
  • Healthcare IT engineers, not sales
  • Reply within one business day
Send a Message

Book a 30-min call · or email us and we'll reply within one business day.

Intent
Details
Contact
How can we help?

Pick whichever fits best — we'll take it from there.