Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Data, Analytics & AI · Health Information Exchange

Health Information Exchange in Medical Data Collection: Forms, Interoperability Standards and Governance

Health Information Exchange (HIE) is the set of standards, agreements and technical infrastructure that allows clinical data to move between the electronic systems of different organisations. It is increasingly used by research teams to assemble real-world datasets without re-collecting data already captured in routine care.

Pubrica AcademyWritten by a health data infrastructure writer Reviewed bya clinical informatics reviewer Published10 October 2026 Last checked10 October 2026 Reading time8 minutes Sources10 peer-reviewed

Health Information Exchange (HIE) is the electronic movement of health-related information across organisations according to nationally recognised standards, allowing clinicians, patients, and, increasingly, researchers to access relevant clinical data regardless of which organisation originally captured it. In the United States, the Office of the National Coordinator for Health Information Technology (ONC) describes three core forms of exchange, directed, query-based, and consumer-mediated, each solving a different data-movement problem, and each with distinct implications for how research teams can access and use the data flowing through it.

Learning objectives

  • The three recognised forms of health information exchange and the problem each addresses
  • Why interoperability standards like HL7 FHIR matter for research-grade data collection specifically
  • How HIE-sourced data collection differs from a purpose-built research database in its governance obligations

Common misconceptions

  • “If a hospital has an electronic health record system, its data is automatically exchangeable with other systems.” The existence of electronic records within one organisation’s system does not make those data interoperable with another organisation’s system; exchange requires shared technical standards (such as HL7 FHIR), legal data-use agreements, and often a dedicated HIE network or intermediary to translate and route the data correctly.

Definition of health information exchange

Health Information Exchange is the capability for health care information to move electronically across organisations within a region, community, or hospital system, so that a patient's relevant clinical history is available to an authorised party regardless of where in the system it was originally recorded1. It is distinct from simply having an electronic health record, because an EHR by itself only stores data within one organisation's system; exchange requires a separate layer of technical standards and governance agreements that let one organisation's system send, request, or make data queryable by another's1. The ONC's 21st Century Cures Act interoperability and information-blocking rule reinforced this by setting specific requirements for how certified health IT must support this kind of exchange and penalising practices that unreasonably block it2.

Exchange is a capability rather than a single piece of software. In a given region, exchange may be implemented through a dedicated regional HIE organisation operating a shared platform, through point-to-point connections directly between large health systems, or through a national network of networks that allows credentialed participants to query across many such regional systems at once. The practical consequence for those seeking access to data through exchange is that the specific technical route, and the governance agreement attached to it, varies by region and by the organisations involved; a research team therefore cannot assume that one region’s exchange arrangement generalises to another.

The three recognised forms of exchange

Directed exchange is the electronic sending of patient information, such as a referral or discharge summary, directly from one known provider to another, functioning much like secure email between care sites1. Query-based exchange allows a provider to search for and retrieve information about a patient from other organisations, typically used in unplanned care situations, such as an emergency department needing a patient's medication history from an unfamiliar system1. Consumer-mediated exchange gives patients themselves the ability to access, manage, and in some cases direct where their own health information is sent, which is the form most directly tied to patient-facing research recruitment and patient-reported data collection1.

These three forms are not mutually exclusive within a single network; a large regional HIE commonly supports directed exchange for routine referrals, query-based access for emergency and unplanned care, and a consumer-facing patient portal that enables consumer-mediated exchange, all running on the same underlying infrastructure. For a research team evaluating a potential data source, identifying which specific form (or combination) a given network supports is a necessary first step, since the practical access pathway, and the consent model attached to it, differs meaningfully between a network built mainly for directed referral traffic and one built around broad, query-based retrieval.

Relevance of HIE to research data collection

For research teams, HIE infrastructure increasingly functions as a source of real-world data that would otherwise require separate, duplicative collection, enabling studies to assemble longitudinal clinical histories drawn from the multiple care settings a participant attended, rather than only the single site that enrolled them3. The FDA's guidance on using electronic health records and medical claims data to support regulatory decisions explicitly addresses this kind of multi-source, exchange-derived dataset, setting expectations for how data provenance, completeness, and reliability should be documented when such data is used to support a regulatory submission3. This is a different data-quality problem from a purpose-built research database, because the data was captured for clinical care, not research, and arrives through an exchange pathway the research team did not design.

A practical consequence is that a study drawing on exchange-sourced data requires an explicit plan for handling the same patient appearing in multiple source systems under slightly different demographic details, a problem commonly termed patient matching, since an imperfect match either fragments one patient’s history into separate, incomplete records or incorrectly merges the histories of two different patients. ONC’s work on patient-matching standards exists because this is a persistent, unsolved technical challenge across the health IT ecosystem rather than an isolated data-cleaning issue, and a research team should allocate adequate analytic time to it rather than assuming that exchange-derived identifiers are already reliably resolved.

Data quality considerations for exchange-sourced data

Data flowing through an exchange network were captured by many different clinicians, at many different organisations, often using different EHR systems and local coding conventions; their completeness and structure can therefore vary considerably even for the same clinical concept. A diagnosis recorded as a structured, coded field at one site and as free text in a clinician’s note at another will not be equally usable for automated research extraction, even though both represent the same clinical fact, so a research team drawing on exchange data should anticipate substantial effort in reconciling such structural inconsistency before analysis rather than assuming that the exchange layer has already normalised it.

Temporal completeness is a related and often underappreciated issue: a patient’s exchange-visible record reflects only the care episodes that were captured and shared through the network, so care received outside the network’s participating organisations, at an out-of-network specialist, or during travel, will be absent rather than flagged as missing. A research team should document which organisations and time periods a given exchange network covers, and should disclose gaps in that coverage explicitly as a limitation, rather than treating the absence of a recorded event in the exchange data as evidence that the event did not occur.

Governance, privacy and interoperability standards

Exchange at any meaningful scale depends on a common technical standard for structuring the data itself, and HL7's Fast Healthcare Interoperability Resources (FHIR) has become the dominant standard for representing clinical data in a form different systems can exchange and parse consistently4. Governance sits on top of this technical layer: HIPAA's Privacy Rule governs how protected health information may be used and disclosed, including through exchange networks, and any research use of HIE-sourced data must satisfy HIPAA's requirements for authorisation, de-identification, or a qualifying waiver, independent of whatever technical standard moved the data5. Where exchange crosses international borders, or involves EU residents' data, the General Data Protection Regulation imposes its own, separate legal basis requirements that a research use must also satisfy6.

A research team should treat these governance requirements as layered rather than redundant: satisfying HIPAA does not automatically satisfy GDPR where both apply, and a technical standard such as FHIR does not by itself determine whether a given use of the data it carries is legally authorised. Mapping explicitly, before any data are extracted, which governance regime covers which part of a planned exchange-sourced dataset prevents a research team from discovering a compliance gap only after analysis is under way. This mapping exercise is also an appropriate point at which to consult an institutional privacy or compliance officer, who can often confirm whether a planned data flow has already been reviewed and approved for a similar prior use, thereby avoiding duplication of a governance review that has effectively already been completed. Incorporating this governance map into the project timeline from the outset, rather than treating it as a one-off compliance requirement before analysis, also facilitates later changes, since adding a new data source or participating site partway through a study is a considerably smaller task when the governance mapping approach is already established and requires only extension.

Key points

Key points

Health Information Exchange is the standards-and-governance layer that lets clinical data move between organisations' systems, and using it for research means satisfying both the technical interoperability standard and the separate legal and privacy requirements that govern the underlying data.

Practical application

Practical application

  1. Identify the form of exchange through which the study data will flow. Directed, query-based, and consumer-mediated exchange have different access patterns and will shape what data is realistically obtainable for a given study design.
  2. Confirm that the data are structured to a shared standard before assuming they are usable. Check for HL7 FHIR compliance or an equivalent mapping before building analysis plans around multi-source exchanged data.
  3. Document data provenance and completeness explicitly if the dataset will support a regulatory submission. Follow FDA real-world data guidance on documenting where each data element came from and how complete and reliable it is judged to be.

Frequently asked questions

The term describes both the general capability and, informally, specific regional or state-level organisations that operate exchange networks; context usually makes clear which is meant, but the underlying technical and legal requirements are the same either way.

Generally no. HIPAA's authorisation, de-identification, or waiver requirements still apply to research use of HIE-sourced data regardless of the exchange mechanism; exchange infrastructure does not substitute for the separate consent or waiver pathway research requires.

Being electronic does not mean two different systems represent the same clinical concept the same way; FHIR provides a shared structure so systems can exchange data without each side needing a custom translation built for every partner.

Most established HIE networks operate within a single country's regulatory and standards environment; cross-border exchange is technically possible but adds additional legal requirements, such as GDPR for EU-linked data.

Not automatically. It was captured for clinical care rather than research purposes, so completeness, consistency, and documentation quality typically need explicit assessment before the data is treated as research-grade.

Yes. The ONC's information-blocking provisions restrict practices that unreasonably interfere with the access, exchange, or use of electronic health information, which is relevant when a research team is negotiating access to HIE-routed data.

References

  1. Office of the National Coordinator for Health Information Technology. What is HIE? read 10 October 2026. View on HealthIT.gov
  2. Office of the National Coordinator for Health Information Technology. 21st Century Cures Act: Interoperability, Information Blocking, and the ONC Health IT Certification Program, Final Rule. 2020. read 10 October 2026. View the ONC Cures Act Final Rule
  3. U.S. Food and Drug Administration. Real-World Data: Assessing Electronic Health Records and Medical Claims Data To Support Regulatory Decision-Making for Drug and Biological Products, Guidance for Industry. 2024. read 10 October 2026. View FDA guidance
  4. HL7 International. HL7 FHIR Release 4. read 10 October 2026. View HL7 FHIR
  5. U.S. Department of Health and Human Services, Office for Civil Rights. HIPAA Privacy Rule, 45 CFR Part 160 and Subparts A and E of Part 164. read 10 October 2026. View the HIPAA Privacy Rule
  6. European Union. Regulation (EU) 2016/679, General Data Protection Regulation. read 10 October 2026. View the GDPR text
  7. World Health Organization. Global Strategy on Digital Health 2020-2025. read 10 October 2026. View the WHO strategy
  8. National Institutes of Health. NIH Policy for Data Management and Sharing. 2023. read 10 October 2026. View the NIH policy
  9. International Organization for Standardization. ISO 27799: Health informatics - Information security management in health using ISO/IEC 27002. read 10 October 2026. View ISO 27799
  10. Office of the National Coordinator for Health Information Technology. Patient matching initiative overview. read 10 October 2026. View patient matching overview

Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.

How to cite this article

Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.

Pubrica Academy. (2026, October 10). Health Information Exchange in Medical Data Collection: Forms, Interoperability Standards and Governance. Pubrica. https://pubrica.com/academy/concepts-definitions/describe-health-information-exchange-in-medical-data-collection/

This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.

HIE Data Source Assessment

Use this before relying on health information exchange data for a research dataset.

[ ] Identified which form of exchange (directed, query-based, consumer-mediated) the data will flow through
[ ] Confirmed the data's structural standard (e.g., HL7 FHIR) and any gaps needing mapping
[ ] Confirmed the legal basis for research use: authorisation, de-identification, or waiver under HIPAA
[ ] Checked GDPR applicability if any data involves EU residents
[ ] Documented data provenance and completeness per FDA real-world data guidance if regulatory use is intended
[ ] Confirmed no information-blocking restriction applies to the planned access

Pubrica AcademyWritten and maintained by Pubrica’s subject matter experts. Articles are revised when the underlying standards change, and each article states the date on which it was last reviewed.

How Pubrica can help

Pubrica's data strategy team maps health information exchange sources against HIPAA, GDPR, and FDA real-world data expectations before a research dataset is built on exchanged clinical data.

Find something else

Search the Pubrica Academy

Access is free and requires no account. Enter a topic, or open the full library to filter by category, sub-topic or resource type.

Research readiness of exchange-sourced data

A scoping assessment is free and takes two business days. It provides a written assessment of what the work requires and which specialist would undertake it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.