Healthcare interoperability is the standardized exchange and use of electronic health data to improve patient care, coordination, and public health outcomes [1]. For a medical device or health IT team, the practical question is not whether interoperability matters but which data classes, profiles, and API requirements apply to a specific product or workflow. ONC leads and coordinates interoperability activities nationwide, including technical initiatives such as standards development and health IT certification as well as policy and programmatic initiatives [1]. CMS adds payer-facing API requirements that shape how clinical and administrative data move between systems [7]. This guide explains the current documentation, including the July 2026 release of USCDI Version 7, the FHIR US Core implementation guide, and the CMS Interoperability Framework. It then walks through a hypothetical evaluation scenario for a device category and identifies what the source documents do not establish.
USCDI v7 as the Baseline Data Contract
The United States Core Data for Interoperability is a standardized set of health data classes and data elements for nationwide, interoperable health information exchange [3]. A data class aggregates data elements by a common theme or use case, while a data element is a piece of data defined for access, exchange, or use of electronic health information [3]. ONC released USCDI Version 7 on July 23, 2026, adding 30 new data elements and one significantly revised data element, Tobacco and Nicotine Product Use, an evolution of the Smoking Status data element [8]. The standard does not limit how or in what contexts elements may be used or exchanged; it groups elements into classes such as Patient Demographics, Clinical Notes, and Encounter Information [8].
USCDI v7 introduces a new Adverse Events data class with two complementary elements. Adverse Event Condition details a change to patient condition that could be an unintended effect of clinical interventions, such as a medication or vaccination reaction [8]. Adverse Event Outcome documents the patient's clinical outcome resulting from an adverse event, with examples including hospitalized, recovered, recovered with sequelae, and death [8]. The bulletin states that this data class does not include patient safety analyses, internal risk management documentation, or patient safety work products as defined under the Patient Safety and Quality Improvement Act of 2005, and does not include Patient Safety Organization investigations, safety reviews, or facility-level reporting activities [8]. This distinction matters for device manufacturers deciding whether an event record belongs in interoperable exchange or protected safety workflows.
FHIR US Core Profiles and RESTful Interactions
The HL7 FHIR US Core Implementation Guide defines the minimum FHIR RESTful interactions for each US Core profile to access patient data [5]. FHIR itself defines how healthcare information can be exchanged between different computer systems regardless of how it is stored in those systems [2]. US Core establishes a floor of standards to promote interoperability and adoption through common implementation, allowing further standards development for specific use cases [5]. Systems may support only the US Core profiles to represent clinical information, or they may support both the profile content structure and the RESTful interactions defined for a resource [5].
The US Core actors include a Requestor, which initiates a data access request to retrieve patient data and acts as the client in a client-server interaction [5]. The guide notes that the terms Requestor and Client are used interchangeably and are not meant to limit the actor to only patient and provider apps; payers and other applications can also act in this role [5]. Profile pages include a Quick Start section documenting required FHIR RESTful search and read operations [5]. For a device vendor, the decision between profile-only support and profile plus interaction support determines whether the product can actively query patient data or only represent clinical information in a conformant structure.
Checking Terminology and Vocabulary Requirements
USCDI v7 lists applicable vocabulary standards for each data element, and the document states that standards listed are required [3]. If more than one standard is listed, at least one is required unless otherwise noted, and standards versions represent the most recent available at time of publication [3]. For example, allergy and intolerance elements reference SNOMED Clinical Terms U.S. Edition, March 2026 Release [3]. The CMS Interoperability Framework similarly requires terminology compliance, with labs in LOINC, medications in RxNorm, and conditions in SNOMED [4]. A device team should verify that its coded output matches the exact vocabulary version referenced in the applicable USCDI version and implementation guide, because a mismatch can block exchange even when the data structure is conformant.
TEFCA and the CMS Interoperability Framework
The Trusted Exchange Framework and Common Agreement establishes a universal governance, policy, and technical floor for nationwide interoperability [1]. TEFCA simplifies connectivity for organizations to securely exchange information and enables individuals to gather their healthcare information [1]. ONC describes TEFCA as facilitating secure, nationwide electronic health information sharing to connect providers, patients, public health agencies, and payers [6]. The Common Agreement and Trusted Exchange Framework are published as separate documents, with the Common Agreement available in version 2.1 as of February 2025 [1].
The CMS Interoperability Framework is a separate voluntary initiative described as a call to action for health data networks that want to move faster [4]. Networks can be listed as CMS-Aligned Networks by voluntarily meeting framework criteria, and the first cohort of early adopters reached General Availability in July 2026 [4]. The framework includes categories such as Pharmacy Systems, Access Provider, and a Diagnostic Imaging workgroup labeled "Ditch the Disk" [4]. The document states that nothing in it is intended to contravene federal and state healthcare and privacy laws, including HIPAA and the Privacy Act [4].
Payer APIs and Prior Authorization Workflows
CMS requires impacted payers to implement several interoperability APIs, each with specific standards and implementation guides [7]. The Patient Access API requires payers to make certain data available to patients, while the Provider Access API supports provider-facing data exchange [7]. The Prior Authorization Requirements, Documentation and Decision API automates the process for providers to determine whether a prior authorization is required and facilitates the exchange of prior authorization requests and decisions from EHRs or practice management systems [7]. The CMS Interoperability and Prior Authorization final rule, identified as CMS-0057-F, drives these requirements [7].
The recommended implementation guides for these APIs include the HL7 FHIR Da Vinci Payer Data Exchange IG, the CARIN Consumer Directed Payer Data Exchange IG, and the FAST Security IG [7]. CMS notes that some adopted standards and implementation guides derived from adopted standards expired on January 1, 2026, as documented in 89 FR 1192 [7]. The FAST Security IG version 3.0.0 is listed as a recommended IG under CMS-0062-P [7]. For a device vendor whose product generates data used in prior authorization, understanding which IG applies to the payer's API is a prerequisite for integration planning.
A Hypothetical Device Evaluation Workflow
Consider a manufacturer evaluating whether a home blood pressure monitor should support interoperable data exchange. The first step is to identify which USCDI v7 data elements the device produces. USCDI v7 includes a Medical Device Order data element, defined as a provider-authored request to initiate, modify, or discontinue the use of a medical device for a patient, with examples including a pacemaker, home blood pressure monitor, infusion pump, or durable medical equipment [8]. The device would also likely produce Observation data, for which US Core defines profiles such as the Average Blood Pressure Profile and the Clinical Result Profile [5].
The second step is to determine whether the device or its companion application will act as a US Core Requestor or only expose profile-conformant data [5]. If the application needs to retrieve patient data from an EHR, it must implement the RESTful interactions defined in the relevant CapabilityStatements [5]. The third step is to check whether the device data feeds a payer workflow, such as prior authorization or quality gap queries. The CMS Interoperability Framework describes open quality gap queries for data elements including blood pressure and BMI [4]. This hypothetical workflow is a suggestion for organizing an evaluation; it does not represent a tested implementation or a certification outcome.
Sources & references
- Interoperability - ONC - Office of the National Coordinator for Health Information Technology · healthit.gov
- Standards and IGs Index and Resources | CMS · www.cms.gov
- United States Core Data for Interoperability (USCDI) - July 2026 - Version 7 · isp.healthit.gov
- Interoperability Framework | CMS · www.cms.gov
- Home - US Core Implementation Guide v9.0.0 · www.hl7.org
- Standards & Technology - ONC - Office of the National Coordinator for Health Information Technology · healthit.gov
- Application Programming Interfaces (APIs) and Relevant Standards and Implementation Guides (IGs) | CMS · www.cms.gov
- ONC Standards Bulletin 2026-2 - ONC - Office of the National Coordinator for Health Information Technology · healthit.gov