What are the CMS Promoting interoperability Programs?

The CMS Promoting Interoperability Programs are federal initiatives designed to encourage hospitals and clinicians to use certified electronic health record (EHR) technology to improve patient care coordination, safety, and data exchange. Formerly known as the "Meaningful Use" or EHR Incentive Programs, these programs set performance measures for secure electronic health information sharing.

Program Overview & History

• Origins: Established in 2011 under the HITECH Act.
• Goal: Drive healthcare quality and efficiency by prioritizing the exchange of health data.
• Evolution: The Medicaid program ended in 2021, while the Medicare portion continues for hospitals, and clinician requirements were moved into the Quality Payment Program's Merit-based Incentive Payment System (MIPS).

Core Requirements

Participants must use Certified Electronic Health Record Technology (CEHRT) and report on key objectives:

• Electronic Prescribing: Sending prescriptions digitally.
• Health Information Exchange: Sharing patient records safely across providers.
• Provider-to-Patient Exchange: Giving patients secure electronic access to their health information.
• Public Health and Clinical Data Exchange: Submitting required data to public health registries.

The four levels of interoperability, as defined by the HIMSS, are foundational, structural, semantic, and organizational.

1. Foundational Interoperability

• Definition: The most basic level of connectivity.
• Function: It allows one system to safely send data to another, and the receiving system to receive it.
• Detail: The receiving system does not need to interpret or process the data.
• Example: Sending a PDF or a scanned lab report through a secure message.

2. Structural Interoperability

• Definition: The formatting and syntax level of data exchange.
• Function: It standardizes the format, structure, and organization of the data.
• Detail: This ensures fields line up correctly so that different systems can read and parse the payload, even if they do not fully understand the clinical meaning yet.
• Example: Exchanging structured data fields using protocols like HL7 or FHIR.

3. Semantic Interoperability

• Definition: The shared understanding of data.
• Function: It ensures that the exact meaning, context, and intent of the data are preserved and interpreted correctly by the receiving system.
• Detail: It relies on standardized vocabularies and code sets (like SNOMED CT or RxNorm) so different programs define medical terms identically.
• Example: System A records a drug as "penicillin" and System B records "PCN," but both systems correctly translate and recognize them as the exact same medication.

4. Organizational Interoperability

• Definition: The human and policy level that brings everything together.
• Function: It aligns governance, legal rules, workflows, and policies between different groups.
• Detail: This level focuses on trust frameworks, user consent, and secure operational procedures so data is safely and legally shared across different entities.
• Example: Inter-agency data sharing agreements that comply with privacy laws like HIPAA.

Participating in the CY 2026 Medicare Promoting Interoperability Program for eligible hospitals and Critical Access Hospitals (CAHs) requires using certified electronic health record technology (CEHRT), achieving a minimum total score of 80 points, and submitting specified electronic clinical quality measures (eCQMs) over a continuous 180-day reporting period.

Core Requirements for CY 2026

• Reporting Period: Use CEHRT for a continuous 180-day reporting period during calendar year 2026.
• Scoring Threshold: Earn a minimum total score of 80 out of 105 available points and receive a non-zero score on every required measure.
• eCQM Submission: Report eight eCQMs spanning all four quarters of CY 2026—consisting of five CMS-selected measures (Safe Use of Opioids, Cesarean Birth, Severe Obstetric Complications, Severe Hypoglycemia, and Severe Hyperglycemia) and three self-selected measures.
• Public Health Exchange: Report four public health and clinical data exchange measures (Syndromic Surveillance, Immunization Registry, Electronic Case Reporting, and Electronic Reportable Laboratory Results) unless an exclusion applies.
• Attestations: Provide required "Yes" attestations, including an expanded Security Risk Analysis (covering both risk analysis and ongoing risk management activities) and annual self-assessments using the 2025 SAFER Guides.
• Bonus Points: A 5-point bonus is available for Trusted Exchange Framework and Common Agreement (TEFCA) participation.

Submission Details

• Deadline: Submit data through the Hospital Quality Reporting Secure Portal by March 1, 2027 (11:59 p.m. PT).
• Critical Access Hospitals (CAHs): Must meet all eCQM and program requirements to avoid having their Medicare reimbursement reduced from 101% to 100% of reasonable costs.

The CMS Interoperability Framework is a voluntary federal blueprint created by the Centers for Medicare & Medicaid Services to accelerate secure, standards-based health data exchange between patients, providers, and payers.

Core Elements

• Patient and Provider Focus: Designed to let patients access clinical, claims, and prior authorization data via apps of their choice, while giving providers full medical histories at the point of care.
• Technology Standards: Relies on modern protocols like HL7 FHIR APIs for data structuring, SMART on FHIR for authorization, and the United States Core Data for Interoperability (USCDI).
• CMS-Aligned Networks: A voluntary designation for health data networks and tech platforms that meet specific infrastructure criteria without imposing new regulatory enforcement burdens.
• Ecosystem Goals: Part of a broader push—including the "Kill the Clipboard" initiative—to replace paper check-ins with digital applications, support AI tools, and streamline prior authorizations.

The Centers for Medicare & Medicaid Services (CMS) interoperability requirements mandate that impacted payers implement standardized Application Programming Interfaces (APIs) using Fast Healthcare Interoperability Resources (FHIR) to improve the secure exchange of patient health and claims data.

Impacted Payers

The rules apply to "impacted payers," which include:

• Medicare Advantage (MA) organizations
• State Medicaid and CHIP fee-for-service (FFS) programs
• Medicaid managed care plans and CHIP managed care entities
• Qualified Health Plan (QHP) issuers on the Federally-facilitated Exchanges (and small group market QHP issuers on the FF-SHOP)

Required APIs and Core Mandates

Impacted payers must build and maintain several distinct FHIR-based APIs:

• Patient Access API: Allows enrollees to easily access their adjudicated claims, encounter data, capitated provider data, and certain clinical data (including lab results) via third-party apps within one business day.
• Provider Access API: Enables providers to retrieve patient claims and clinical data for treatment purposes (subject to patient consent and validation like NPI matching).
• Payer-to-Payer API: Facilitates the transfer of historical patient data—including prior authorization statuses—from one payer to another when a patient changes health plans.
• Prior Authorization API: Streamlines the prior authorization process by letting providers electronically submit requests, check requirements, and receive decisions faster.

Technical Standards

• HL7 FHIR: The foundational framework for data exchange.
• USCDI (United States Core Data for Interoperability): Mandates standard versions (such as USCDI v3) for structured clinical notes, conditions, medications, and labs.
• Security & Authentication: Utilizes modern identity standards like SMART/OAuth 2.0 and OpenID Connect to protect patient privacy.

For comprehensive context and official policy details, review the CMS Interoperability Overview.