Overview
USCDI (United States Core Data for Interoperability) is the standardized set of health data classes and data elements required for interoperable exchange under Office of the National Coordinator for Health IT (ONC) regulations. USCDI provides a common core of data that healthcare organizations must support for exchange, enabling structured patient data to flow between providers, payers, patients, and researchers across disparate IT systems.
History and structure: ONC introduced USCDI in 2020, replacing the prior Common Clinical Data Set (CCDS). USCDI is organized into Data Classes (e.g., Allergies and Intolerances, Medications, Problems, Procedures, Laboratory, Vital Signs) each containing specific Data Elements with defined vocabulary and format. ONC updates USCDI annually, progressively expanding required elements based on industry feedback, clinical need, and interoperability goals. USCDI v1 (2020) established foundational elements; subsequent versions (v2, v3, v4) have added elements including clinical notes, care team members, provenance, goals, and social determinants of health.
Regulatory integration: ONC 21st Century Cures Act regulations require EHR certification against USCDI support — certified EHRs must demonstrate ability to exchange USCDI data. CMS regulations require payer APIs to expose USCDI data to patients and authorized applications. Information-blocking rules apply to USCDI data elements, requiring providers and payers to share USCDI data without blocking. USCDI serves as the standardized floor for interoperability across ONC and CMS regulatory frameworks.
Version cadence: ONC moves from USCDI v1 to v2 to v3 to v4 etc. through a deliberate process — proposing additions, soliciting comment, and finalizing versions. Updates typically occur annually; implementation timelines for new versions are staggered (certified EHRs must support new versions within defined transition periods). Healthcare organizations monitor version updates to plan technology and workflow readiness.
For interoperability, USCDI ensures consistent data elements across organizations. When Provider A sends a patient's data to Provider B, both organizations can expect the transfer to include USCDI data classes and elements in standardized formats. This consistency enables meaningful data exchange without custom mapping for every data source. USCDI elements are typically exchanged as FHIR resources (US Core Implementation Guide maps USCDI to FHIR), C-CDA documents, or other structured formats.
Clinical and operational applications: USCDI data supports continuity of care during transitions (hospital discharge to primary care, PCP to specialist), population health (aggregated USCDI data supports quality measurement, risk stratification), research (USCDI provides consistent data elements for clinical research), and patient-mediated exchange (patients can authorize USCDI exchange through apps under the CMS Patient Access API).
Implementation considerations at provider organizations include: EHR configuration to populate all USCDI elements (some elements require specific workflow design — e.g., social determinants capture, care team documentation), data quality for USCDI elements (completeness, accuracy, timeliness), exchange infrastructure (FHIR APIs, C-CDA document generation, HIE connectivity), and vendor certification (confirming EHR certification covers required USCDI versions).
For RCM operations, USCDI data supports eligibility verification, prior authorization (Da Vinci CRD/DTR/PAS use USCDI), coverage coordination, and claims attachments. Structured USCDI data improves electronic attachment workflows and reduces manual document exchange. Practices whose EHRs support current USCDI versions have operational advantages in electronic exchange with payers and other providers.
Future trends include: expanded USCDI scope (behavioral health, social determinants, specific clinical specialties), deeper integration with payer APIs (CMS-0057-F prior authorization expansion, TEFCA Common Agreement), and enhanced patient-mediated exchange capabilities. USCDI evolution shapes the trajectory of US healthcare interoperability.
Industry benchmark
USCDI versions: v1 (2020) → progressively expanded annually. ONC certification: required for EHRs supporting exchange. CMS API requirements: based on USCDI.
Worked example
A primary care EHR undergoes ONC certification against USCDI v4. The certification process validates support for all USCDI v4 data classes including expanded elements for care team members, clinical notes, and social determinants. Post-certification, the EHR can exchange USCDI v4 data via FHIR US Core APIs and C-CDA documents with other certified systems, payer APIs, and patient-authorized applications. The practice uses USCDI-based exchange for referral coordination, hospital transitions, and patient portal access.
Frequently asked questions — USCDI (United States Core Data for Interoperability)
What's the difference from USCDI and US Core?
USCDI is the standardized data set (classes and elements) required for exchange. US Core is the FHIR Implementation Guide mapping USCDI to FHIR resources for API-based exchange. USCDI defines what data; US Core defines how to exchange it in FHIR format.
How often does USCDI update?
Annually. ONC publishes draft versions for comment, finalizes updates, and establishes implementation timelines for certified EHRs and exchange frameworks.
Is USCDI required for certification?
Yes for ONC-certified EHRs under 21st Century Cures Act regulations. Certification criteria require support for USCDI data classes and elements at specified versions.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.