Behind much of the recent progress in U.S. health-data exchange sits a deceptively simple artifact: a published list of the data elements that systems are expected to be able to share. The U.S. Core Data for Interoperability (USCDI) names those elements — demographics, problems, medications, allergies, laboratory results, clinical notes, and more — grouped into data classes. It is a list, not a transport protocol, and that is precisely its power.
Why a list matters
For exchange to work, two systems must agree not only on how to move data but on what data to move. Before a common data list existed, every interface negotiated its own scope. USCDI sets a floor: a defined baseline that conformant systems should support, so that a receiving organization knows what it can reasonably expect to receive. The FHIR US Core Implementation Guide is the technical expression of that baseline — it constrains FHIR resources to carry USCDI elements in an expectable shape.
The expanding cadence
USCDI is revised on a roughly annual rhythm, with new data classes and elements added through a public process. Each expansion broadens what can be exchanged in a standardized way — recent attention has included richer clinical context and data relevant to health equity. The corresponding US Core IG releases track those additions, which is why “current US Core” is a moving target that implementers should re-check rather than assume frozen.
What it means for Arizona implementers
The annual cadence is a feature, not a nuisance. It means the data baseline grows deliberately and predictably rather than through ad hoc one-off interface requests. For an Arizona health system or clinic, the practical discipline is to track which USCDI version their certified systems support and to plan for the additions rather than be surprised by them.
The convener’s role
AzHeC does not set USCDI — that is a federal process — but we help Arizona stakeholders read it accurately and understand how the list, the FHIR profiles, and the exchange frameworks fit together. Start with the plain-language overviews in our Standards work area and the glossary of Health IT terms.