Save the Date for the 2027 Annual Conference – September 27-29, 2027, St. Louis, Missouri

Build the Asset Once for Reusable Infrastructure

Share:

Health Information Exchanges (HIEs) already do the hardest part of population health data work. They bring together records from dozens, sometimes hundreds, of contributors, match records to the right person, and make inconsistent codes usable, all within established frameworks for data governance, privacy, security, and appropriate data use. Those safeguards are essential, but they also demonstrate that this kind of trusted data infrastructure is already within reach. Too often, HIEs repeat much of the underlying data work for each new customer.

The opportunity is straightforward: build this core data asset once, with strong governance, privacy, and security at its foundation, then use it to serve multiple authorized needs.

Many HIEs already clean and reconcile data for several customers under separate contracts. A single, reliable and appropriately governed dataset could support multiple use cases while maintaining the safeguards required for each. And the demand is real: federal programs are now asking exchanges for this capability directly.

Five Customers, One Job

HIE customers arrive separately and sign different contracts for different use cases, but their needs often overlap. Payers, for example, purchase quality data, including certified supplemental data for HEDIS, as well as notifications that support care management. Public health agencies use HIE data for surveillance; 86 percent of health information organizations report a connection to a public health agency [4]. Medicaid agencies use the data for program analytics. These needs will likely grow when eligibility redeterminations for the Medicaid adult group move to every six months in 2027 under the 2025 reconciliation law [5]. Hospitals need evidence behind the health information exchange measures they attest to in the Promoting Interoperability Program. Researchers need data to identify and study specific groups of patients.

Today, many organizations build each request separately, by data source, customer, and use case. Yet data normalization is already among the services health information organizations report offering [7]. The work has value and a market. The question is how often an HIE should have to repeat it.

Beneath those separate contracts is the same core job: match each person’s records, understand the population, and standardize clinical terms so data from different contributors can be compared.

Payers, public health agencies, Medicaid programs, hospitals, and researchers all need that foundation; it’s critical infrastructure for health improvement.

The Demand is Here

Two federal research programs have worked with exchanges in the past two years, and both identified a need for the same core data asset.

One example comes from the FDA’s Sentinel Innovation Center. In a pilot with Civitas Networks for Health® (Civitas) member MyHealth Access Network in Oklahoma, the exchange identified more than 177,000 people who started two classes of diabetes medication over eight years and linked their records to claims from three health plans [1]. EHR data helped identify most patients and added clinical information, such as laboratory results, vital signs, and body mass index, that claims do not include. The pilot also revealed common data gaps. One-third of patients had no laboratory result, and a quarter or more had no recorded race. The authors recommended creating a network of exchanges that uses a shared data model and consistent quality standards. A feasibility study for that network is underway [1].

The NIH All of Us Research Program faced a different challenge: retrieving authorized participant records at scale [2]. Working through Civitas member eHealth Exchange, Manifest MedEx answered 78,000 authorized queries and returned records for more than 48,000 participants. About 17,000 of those participants had no EHR data in the program beforehand. The effort demonstrated what national networks can make possible. It also revealed practical barriers involving data-use permissions, privacy settings, and differences among bulk extracts, C-CDA documents, and FHIR resources.

Both programs needed the same three capabilities:

  1. A reliable count of the population
  2. A way to match each person’s records across contributors
  3. Standardized clinical terms that allow data from different sources to be compared

Together, those capabilities form a reusable data asset. Build it once, and an HIE can use the same foundation to answer questions about quality, public health, Medicaid programs, and research.

The sector has been measured by what it moves. It should be measured by what it can see.

Where the Health Data Utility Capability Model Already Points

The Health Data Utility Capability Model, developed by the Consortium for State and Regional Interoperability (CSRI) in partnership with Civitas, includes the building blocks for this asset [6]. The model addresses common data models, terminology and code mapping, chronic disease surveillance, and payer quality measurement. The model offers an important underlying goal: creating reliable, reusable data that can serve multiple purposes ultimately as a public good.

The next step is to make that connection explicit. The dataset created for research can also support payer and public health needs.

One Step Any HIE Can Take Now

Any HIE can start with one practical test:

  1. Choose a condition, such as diabetes or hypertension.
  2. Ask one contributing health system how many patients it identifies with that condition.
  3. Run the same count through the exchange.
  4. Compare the results and share what the differences reveal.

And if your HIE is already doing this work, share your results.

Utah’s Department of Health and Human Services and Civitas member Utah Health Information Network (UHIN) took this approach with 72,000 matched patients [3]. The exchange captured laboratory results well but missed many blood pressure readings. Its estimates for diabetes and hypertension were also lower than the state survey.

Publishing those gaps made the study especially useful. It showed other networks where data was missing and what they should work to improve first. Organizations that openly share this kind of evidence can become trusted peers for the field.

The HDU learning community that CSRI leads with support from Civitas brings together about 30 member organizations to work through self-assessment of the model. It is a natural place to continue this conversation.

Oklahoma, California, and Utah show that this data asset can be built. Now we must go further in explaining its value in terms that public programs can support and fund once, allowing many customers to benefit from the same trusted data foundation.

About the Author

Davera Gabriel, RN, FHL7, FAMIA is VP Semantic Interoperability at Evidentli and primary author of the HL7 Vulcan FHIR to OMOP Implementation Guide. She was inaugural co-chair of the HL7 Terminology Services Management Group, and is co-author of “Converge or Collide? Making Sense of a Plethora of Open Data Standards in Health Care” (JMIR, 2024), along with numerous academic, industry, and standards publications including peer-reviewed papers, HL7 standards, and policy papers. Disclosure: Davera Gabriel works for Evidentli, a health care data harmonization company whose products include normalization of health data to a common data model. The views in this article are her own.

References

  1. Khurshid A, Kendrick D, Pillai HS, Sun J, Oliveira E, Jaquish A, et al. Health Information Exchanges (HIEs) as Novel Sources for Population-Based Post Marketing Surveillance of Medical Products: A Pilot Study from the FDA Sentinel Innovation Center. Drug Saf. 2026. doi:10.1007/s40264-026-01669-3. PMID 41975169. Preprint: medRxiv 2025, doi:10.1101/2025.08.13.25333515
  2. eHealth Exchange. It Worked for All of Us: acquiring EHR data for research through national networks. Panel presentation, eHealth Exchange Annual Meeting; November 2025. Available from: https://ehealthexchange.org/wp-content/uploads/2025/12/1300_WillowPond_ItWorkedForAllOfUs_Panel_FINAL.pdf
  3. Horth RZ, Wagstaff S, Jeppson T, et al. Use of electronic health records from a statewide health information exchange to support public health surveillance of diabetes and hypertension. BMC Public Health. 2019;19:1106. doi:10.1186/s12889-019-7367-z
  4. Office of the Assistant Secretary for Technology Policy. National survey reveals new insights on health information organizations. HealthIT.gov blog. Available from: https://healthit.gov/blog/interoperability/national-survey-reveals-new-insights-on-health-information-organizations/
  5. Centers for Medicare & Medicaid Services. State Medicaid Director Letter SMD #26-001: Eligibility redeterminations under Public Law 119-21. March 6, 2026. Available from: https://www.medicaid.gov/federal-policy-guidance/downloads/smd26001.pdf
  6. Consortium for State and Regional Interoperability. Health Data Utility Capability Model. Revised May 2026. Available from: https://thecsri.org/the-csri-health-data-utility-capability-model/
  7. Adler-Milstein J, Rosenthal S, Patel V, Kendrick D. National HIO Survey Results. Civitas Networks for Health; November 27, 2023. Available from: https://civitasforhealth.org/wp-content/uploads/2023/11/National-HIO-Survey-Results-Civitas-Networks-for-Health-Presentation.pdf

Share: