FHIR API Integration
FHIR R4 APIs, US Core profiles, and Da Vinci implementation guides.
Explore FHIR API IntegrationCMS-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.
Achieve CMS-0057-F compliance with Patient Access API, Provider Directory API, and Prior Authorization API development using FHIR R4 and Da Vinci implementation guides. Our team builds the FHIR R4 APIs and integration infrastructure payers need to meet the January 2027 deadline — from gap analysis through production deployment and attestation.
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.
CMS requires payers to publish a publicly accessible FHIR-based Provider Directory API that exposes in-network provider information — including names, specialties, locations, accepting-patient status, and network affiliations. The Provider Directory API uses the Da Vinci PDex Plan Net implementation guide, which defines FHIR resources for Organization, Practitioner, PractitionerRole, Location, HealthcareService, and InsurancePlan. We implement Provider Directory APIs that are fully conformant with Da Vinci Plan Net, pull from your credentialing and network management systems, and stay current through automated data synchronization.
CMS-0057-F mandates that payers implement a FHIR-based Prior Authorization API that allows providers to submit, check status, and receive decisions on prior authorization requests electronically. The API must conform to the Da Vinci Prior Authorization Support (PAS) implementation guide and return decisions within 72 hours for urgent requests and 7 calendar days for standard requests. We implement Prior Authorization APIs that integrate with your utilization management systems, automate decision workflows where clinically appropriate, and expose real-time status to requesting providers through FHIR R4 endpoints.
When a member transitions between health plans, CMS-0057-F requires the new payer to request and receive the member's claims, encounter, and clinical data from the previous payer through a FHIR-based bulk data exchange. This payer-to-payer exchange must occur within a specified timeframe of member enrollment and cover a minimum lookback period. We implement payer-to-payer exchange workflows using FHIR Bulk Data Access, including member matching, consent management, data request orchestration, and inbound data ingestion into your claims and clinical data warehouses.
The 21st Century Cures Act information blocking provisions prohibit healthcare actors from knowingly and unreasonably interfering with the access, exchange, or use of electronic health information. Payers, providers, health IT developers, and health information networks must evaluate their data sharing practices against eight recognized exceptions and remediate any practices that constitute information blocking. We help organizations assess their current data sharing posture, identify practices that may constitute information blocking, implement compliant data access workflows, and document exception applicability where restrictions are justified.
CMS interoperability rules require payers to attest to their compliance status and report on prior authorization metrics including approval rates, denial rates, average response times, and overturn rates. Beginning in 2027, payers must publicly report these metrics on their websites and submit them to CMS. We help organizations prepare attestation documentation, implement metrics collection pipelines that capture the required data points from your prior authorization systems, and build reporting dashboards that satisfy CMS disclosure requirements.
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.
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.
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.
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.
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.
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.
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.
| 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 |
CMS interoperability compliance spans technical infrastructure, operational workflows, and documentation. Use this checklist to assess your organization's readiness across all three domains.
Need help meeting the January 2027 CMS interoperability deadline? Our compliance team can assess your readiness and build a remediation plan.
Get StartedCMS 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.
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.
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.
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.
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.
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.
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.
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.
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 including Availity, Change Healthcare, and Waystar — ensuring clean claims, proper validation, and real-time acknowledgment 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 file ingestion pipelines that parse remittance data, reconcile payments against submitted claims, and surface denial patterns for revenue cycle optimization.
The 834 transaction handles member enrollment and disenrollment between employers, health plans, and government programs. Combined with 270/271 eligibility verification and 278 prior authorization transactions, these healthcare EDI exchanges form the foundation that CMS interoperability rules are modernizing with FHIR-based APIs.
Real-world CMS interoperability implementations — from Patient Access APIs to prior authorization automation.
A national payer built a FHIR Patient Access API to give members standardized access to claims, clinical, and coverage data through third-party applications — meeting CMS-9115-F and CMS-0057-F requirements with CARIN Blue Button and Da Vinci PDex conformance.
Information blocking is a practice by a healthcare actor that is likely to interfere with, prevent, or materially discourage access, exchange, or use of electronic health information (EHI). Under the 21st Century Cures Act and the ONC Information Blocking Final Rule (45 CFR Part 171), four categories of actors are subject to information blocking provisions: healthcare providers, health IT developers of certified health IT, health information exchanges (HIEs), and health information networks (HINs). The rule defines eight exceptions where interfering with EHI access is permissible — including preventing harm, protecting privacy, security concerns, recovering reasonable costs, responding to infeasibility, licensing terms, content and manner conditions, and health IT performance. When a practice does not fall within a recognized exception, it constitutes information blocking. Penalties include civil monetary penalties of up to $1 million per violation for health IT developers, HIEs, and HINs, while provider violations are subject to appropriate disincentives determined by HHS.
CMS-0057-F — formally titled the CMS Interoperability and Prior Authorization Final Rule — is the most comprehensive CMS interoperability rule to date. Published in January 2024, it requires Medicare Advantage, Medicaid, CHIP, and Qualified Health Plan (QHP) issuers to comply in two phases: operational requirements by January 1, 2026, and FHIR API implementation by January 1, 2027. Beginning in 2026, payers must provide specific denial reasons for prior authorization decisions and meet response timeframes of 72 hours for urgent requests and 7 calendar days for standard requests. By 2027, payers must implement a Prior Authorization API (Da Vinci PAS), a Provider Access API for provider data sharing, payer-to-payer data exchange using FHIR Bulk Data Access, and enhanced Patient Access API requirements building on CMS-9115-F. The rule also introduces prior authorization metrics reporting — payers must publicly report approval rates, denial rates, average decision timeframes, and overturn rates on their websites and to CMS. CMS-0057-F represents a fundamental shift toward API-first, FHIR-based data exchange for the payer industry.
The CMS Prior Authorization API is a FHIR R4-based API that CMS-0057-F requires impacted payers to implement by January 2027. The API must conform to the HL7 Da Vinci Prior Authorization Support (PAS) implementation guide and enable providers to electronically submit prior authorization requests, query the status of pending requests, and receive approval or denial decisions with reason codes. The Prior Authorization API uses FHIR Claim resources for request submission, ClaimResponse resources for payer decisions, and Task resources for asynchronous status tracking. Payers must respond to prior authorization requests within 72 hours for urgent requests and 7 calendar days for standard requests. The API must also support attachment submission for clinical documentation and return structured denial reasons mapped to standardized code sets. This API is designed to replace phone and fax-based prior authorization workflows that currently consume significant administrative resources for both providers and payers.
The ONC Information Blocking Final Rule defines four categories of actors subject to information blocking provisions. Healthcare providers include hospitals, physicians, and other clinical professionals as defined under 42 USC 300jj. Health IT developers of certified health IT are companies that develop, maintain, or offer certified electronic health record technology — this includes major EHR vendors and health IT platforms that hold ONC certification. Health information exchanges (HIEs) are organizations that facilitate the electronic exchange of health information between providers and other stakeholders in their region or network. Health information networks (HINs) are entities that determine, oversee, or administer policies and procedures for electronic health information exchange among a broad set of participants. Each actor category faces different enforcement mechanisms — health IT developers, HIEs, and HINs face civil monetary penalties of up to $1 million per violation, while healthcare providers face appropriate disincentives through existing CMS and OIG enforcement frameworks.
The ONC Information Blocking Final Rule establishes eight exceptions under which interfering with EHI access, exchange, or use is permissible. The Preventing Harm exception allows restrictions to protect patients or others from substantial harm. The Privacy exception permits restrictions required by state or federal privacy law, including patient consent preferences. The Security exception allows restrictions necessary to protect EHI from cybersecurity threats. The Infeasibility exception applies when fulfilling a request is technically infeasible or imposes an undue burden. The Health IT Performance exception allows temporary restrictions to maintain system availability or performance. The Content and Manner exception permits actors to establish reasonable content standards and delivery methods for EHI. The Fees exception allows recovery of reasonable costs for EHI access and exchange. The Licensing exception permits reasonable licensing terms for interoperability elements. Each exception has specific conditions that must be satisfied — actors must document their rationale and demonstrate that their practice meets the exception requirements to avoid information blocking liability.
Da Vinci is a collaborative project within HL7 International that develops FHIR implementation guides specifically designed for payer-provider data exchange in the United States. The Da Vinci project brings together payers, providers, health IT vendors, and government agencies to create standardized, FHIR-based specifications that solve real-world interoperability challenges — from prior authorization and claims data exchange to care gaps reporting and risk adjustment. Da Vinci implementation guides are critical because CMS has adopted them as the technical standard for compliance with interoperability rules. CMS-0057-F specifically requires conformance with Da Vinci PAS (Prior Authorization Support), PDex (Payer Data Exchange), Plan Net (Provider Directory), and other Da Vinci IGs for payer API implementations. Key Da Vinci IGs include PAS for prior authorization, PDex for member data exchange, Plan Net for provider directories, Alerts for admission and discharge notifications, CRD for coverage requirements discovery, and DTR for documentation templates and rules. As CMS continues to expand interoperability requirements, Da Vinci implementation guides will remain the foundation for compliant payer-provider data exchange.
Healthcare EDI (Electronic Data Interchange) refers to the standardized electronic exchange of administrative and financial transactions between healthcare organizations — primarily using the ASC X12 transaction sets mandated under HIPAA. Key healthcare EDI transactions include the 837 (claims submission), 835 (electronic remittance advice/payment), 270/271 (eligibility inquiry and response), 278 (prior authorization request and response), and 834 (enrollment and disenrollment). Healthcare EDI has been the backbone of payer-provider administrative data exchange for decades, running through clearinghouses like Availity, Change Healthcare, and Trizetto that handle transaction routing, validation, and translation. CMS interoperability rules are now layering FHIR-based APIs on top of existing EDI infrastructure — the CMS-0057-F Prior Authorization API (Da Vinci PAS) is designed to complement, and eventually replace, the X12 278 transaction for prior authorization. Organizations pursuing CMS compliance need to maintain existing EDI connectivity while building new FHIR endpoints, which is why Saga IT's integration approach supports both FHIR R4 and X12 EDI in parallel.
A healthcare clearinghouse is an intermediary that processes and routes electronic administrative transactions between providers and payers. Under HIPAA, clearinghouses serve as covered entities that receive non-standard or standard EDI transactions, validate them against HIPAA transaction formats, and forward them to the appropriate payer or provider. Major healthcare clearinghouses include Availity, Change Healthcare (Optum), Trizetto, and Waystar. Clearinghouses handle claims submission (837), eligibility verification (270/271), claim status inquiries (276/277), remittance processing (835), and prior authorization (278) — collectively processing billions of transactions annually. For CMS interoperability compliance, clearinghouses are evolving to support both traditional X12 EDI and FHIR-based API exchange. Many clearinghouses now offer FHIR-enabled APIs that translate between X12 and FHIR formats, enabling providers and payers to adopt CMS-mandated FHIR APIs without abandoning existing EDI infrastructure. Saga IT integrates with all major clearinghouse platforms for both EDI and FHIR connectivity.
Related Services
Resources
From gap analysis to API implementation — meet your CMS interoperability requirements before the 2027 deadline.