In ONC's words, the USCDI sets the foundation for the access, exchange and use of electronic health information. It groups data elements into data classes by common theme, such as allergies, medications or laboratory results, without limiting how they can be used. USCDI names the data; other standards say how to represent and send it.
How versions work
ONC publishes a new USCDI version annually. A draft comes out in January for public comment and a final version follows later in the year, targeted for July. Draft v7, released January 29, 2026, proposed 29 new data elements, one significantly revised element (Tobacco Use) and two new data classes, Adverse Events and Healthcare Information Attributes. Check ONC's site for which version is final at the time you read this.
Publishing a version does not make it mandatory. The HTI-1 final rule adopted USCDI v3 as the baseline for the ONC Health IT Certification Program as of January 1, 2026. In March 2025 ONC used enforcement discretion for certain v3 data elements and then released v3.1 without them; the HTI-5 proposed rule would adopt v3.1. Developers can also move to newer versions voluntarily. For the standardized API criterion, USCDI v5 is an approved advanced version.
USCDI and US Core
HL7's US Core implementation guide turns USCDI into concrete FHIR profiles. Its mapping table pairs USCDI v3.1 with US Core 6.1.0, v4 with 7.0.0, v5 with 8.0.1 and v6 with 9.0.0.
Why it matters
If you are buying or building an app that reads from certified EHRs, USCDI tells you which data you can count on being available through their APIs. Anything outside it may exist in one EHR and not another.
Example: a care management product plans a feature that depends on a data element first added in a recent USCDI version. Before promising it to customers, the team checks which version added the element and whether the EHRs it targets certify to that version or to the v3 baseline only.