Health information exchange (HIE)
Also known as: HIE, health data exchange
A health information exchange (HIE) is a system or network that lets different healthcare organizations share patient information electronically: lab results, medication lists, hospital discharge summaries, and imaging reports.
It means an emergency doctor can see the tests your family doctor ordered last week. While HIEs exist in every Canadian province in some form, patients and clinicians still regularly hit gaps, because sharing depends on technology, funding, privacy rules, and vendors' willingness to connect.
Health information exchange (HIE), explained at three levels
At home
Think of an HIE as an interlibrary loan system for health records. Each clinic, hospital, and lab keeps its own records, but the exchange lets an authorized clinician request or view what another organization holds. So an emergency doctor can see the bloodwork your family doctor ordered last week, instead of relying on your memory, a phone call, or a fax.
At work
A health information exchange is the system, network, and set of agreements that let separate healthcare organizations share patient information electronically. It delivers lab results, medication histories, discharge summaries, and imaging reports to clinicians at the point of care. For organizations, it reduces duplicate tests, medication errors, and delays, but it requires shared governance and lasting funding.
At home
Exchanges are built in three main ways. A centralized model copies key data from each source into one shared repository. A federated model leaves data where it is and fetches it from each source when a clinician asks. A hybrid keeps a central index of where records live and pulls the details on demand. In Canada, provincial viewers such as ConnectingOntario and Alberta Netcare let clinicians see labs, drugs, and reports from many sources.
At work
An HIE needs several core services. A master patient index matches the same person across systems. A record locator tracks which organization holds which documents. Consent management enforces patient choices, and audit logging records every access. Content moves through IHE profiles such as XDS for document sharing, HL7 v2 feeds, or FHIR APIs, with shared terminologies such as LOINC and SNOMED CT so results mean the same thing everywhere.
At home
Without a universal identifier, systems match patients by comparing names, birth dates, health card numbers, and addresses, and each of those can be misspelled, outdated, or shared. Matching algorithms weigh how closely the fields agree. Set them too strict, and records split into duplicates; too loose, and someone else's results land in your chart. In my opinion, patient identity is the unglamorous foundation every exchange depends on.
At work
HIEs fail more often on governance than on technology. Custodians need data-sharing agreements defining who may access what and who is liable for errors. Funding must outlast start-up grants, as many US exchanges learned. Vendors need mandates or incentives to connect, such as US information blocking rules, TEFCA, and Canada's proposed Connected Care for Canadians Act. Measure success by clinician use in workflows, not record counts, and plan for patient access through portals and apps.
Real-world examples
At home
Nadia visited an emergency department in a different Alberta city while travelling. The doctor pulled up her recent blood test and medication list through the provincial system, avoiding a repeat test and a risky drug interaction.
At work
Jerome is a digital health lead at an Ontario family health team. Connecting the clinic's EMR to hospital discharge summaries through a regional exchange meant doctors saw summaries within a day instead of waiting a week for faxes.
How it compares
| feature | Health information exchange (HIE) | Electronic Health Record (EHR) |
|---|---|---|
| Scope | Shares data between organizations | Stores data within an organization or system |
| Main users | Many organizations' clinicians | One organization's clinicians |
| Key challenge | Governance and patient matching | Usability and documentation burden |
| Example | Provincial clinical viewer | A hospital's records system |
An EHR keeps records. An HIE moves them between those who need them.
For analysts
When evaluating a clinical system, I'd ask which provincial and regional exchanges it connects to today, not which it could connect to. Integration promises are cheap; working connections are what save clinicians time.
History & origin
Regional health information organizations formed in the US in the 1990s and 2000s, many failing when grant funding ran out. Canada created Canada Health Infoway in 2001 to fund electronic health records and provincial repositories for labs, drugs, and imaging. Ontario launched ConnectingOntario and other clinical viewers, while provinces such as Alberta built Netcare. In the US, the 21st Century Cures Act of 2016 banned 'information blocking,' and the national TEFCA framework went live in December 2023. In Canada, the federal Connected Care for Canadians Act, reintroduced as Bill S-5 in 2026, aims to prohibit data blocking by health IT vendors. In my view, the technology for HIE has existed for years; the real obstacle is that no one is paid to share data.