Written and maintained by CASRAI Editorial Board
Last updated
The Indiana Health Information Exchange (IHIE) is one of the oldest and largest statewide clinical health data utilities in the United States, managing the Indiana Network for Patient Care (INPC) originally architected by Clement McDonald, MD, and biomedical informatics researchers at the Regenstrief Institute in 1994 and formally incorporated as IHIE in 2004. For clinical informatics architects, population health researchers, and health system compliance teams evaluating Health Information Exchange (HIE) architectures across state jurisdictions, comparing IHIE with regional and statewide networks—including Maryland’s CRISP, New York’s SHIN-NY, North Carolina’s NC HealthConnex, and California’s Data Exchange Framework (DxF)—clarifies how regional clinical repositories, state participation mandates, and TEFCA QHIN participation interoperate.
How Do State and Regional Health Information Exchanges (Such as IHIE, CRISP, and SHIN-NY) Operate?
A statewide or regional HIE functions as a multi-institutional clinical data fabric that normalizes, links, and delivers longitudinal patient records across otherwise unaffiliated hospitals, ambulatory clinics, reference laboratories, radiology centers, and state public health agencies. Taking the Indiana Health Information Exchange (IHIE) as the canonical reference architecture, core operational services include:
- Indiana Network for Patient Care (INPC) & CareWeb Portal: A federated-to-centralized clinical data repository linking over 100 Indiana hospitals and tens of thousands of clinicians. Authorized care teams access aggregated medication histories, laboratory panels (standardized with LOINC, originally developed at Regenstrief), pathology reports, radiology narratives, and discharge summaries through the web-based CareWeb viewer or embedded SMART on FHIR EHR widgets.
- DOCS4DOCS Clinical Message Routing: High-volume clinical result delivery infrastructure that routes structured HL7 v2 ORU (Observation Result) and MDM (Medical Document Management) messages from hospitals and laboratories directly into ordering physicians’ ambulatory EHR inboxes.
- Admission, Discharge, and Transfer (ADT) Event Notification Services (ENS): Real-time HL7 v2 ADT^A01/A03/A04 feed ingestion that notifies primary care providers, Accountable Care Organizations (ACOs), and care managers whenever an attributed patient presents to an emergency department or is admitted/discharged statewide.
- Public Health & Research Data Stewardship: Automated electronic laboratory reporting (ELR), syndromic surveillance feeds to state health departments, and de-identified or IRB-approved longitudinal cohort extraction brokered in partnership with the Regenstrief Institute Data Core.
Which U.S. States Mandate Hospital and Clinic Participation in a State HIE?
While Indiana achieved near-universal hospital adoption through voluntary clinical utility and payer value-based incentives, other U.S. states have enacted statutory or regulatory mandates requiring healthcare facilities to connect to designated state or regional networks to satisfy healthcare interoperability and Medicaid oversight goals:
| State / Regional HIE Network | Governing Authority / Statute | Participation Mandate & Technical Architecture |
|---|---|---|
| Indiana — IHIE (INPC) | Non-profit health data utility (IHIE / Regenstrief Institute) | Voluntary statewide participation encompassing >100 hospitals; INPC clinical repository, CareWeb, and DOCS4DOCS |
| Maryland, DC & West Virginia — CRISP | Maryland Health Care Commission (MHCC) & COMAR 10.25.18 | Mandatory acute-care hospital ADT and clinical data submission; operates state PDMP integration and regional ENS across MD, DC, WV, and partner states |
| New York — SHIN-NY | NY Dept. of Health (10 NYCRR Part 300) & NY eHealth Collaborative (NYeC) | Mandates licensed hospitals and regulated providers to connect and contribute clinical records to regional Qualified Entities (QEs) linked statewide |
| North Carolina — NC HealthConnex | N.C. Gen. Stat. § 90-414.4 (NC HIEA) | Statutory mandate requiring all hospitals, physicians, and providers receiving state funds (including NC Medicaid and State Health Plan) to submit clinical and demographic data |
| California — CalHHS DxF & Regional HIEs | Cal. Health & Safety Code § 130290 (AB 133 Data Exchange Framework) | Mandates signatory Data Sharing Agreement (DSA) execution for acute hospitals, physician practices, clinical labs, and health plans across regional networks (Manifest MedEx, LANES, SacValley MedShare, Santa Cruz HIE, Dignity Health HIE nodes) |
| Florida, Hawaii, Idaho & Nevada HIEs | AHCA Florida HIE, Hawaii HIE (HHIE), Idaho Health Data Exchange (IHDE), HealtHIE Nevada | Statewide ENS/ADT alerting (such as Florida’s statutory hospital ENS rules) and regional C-CDA/FHIR clinical query portals |
How Do State HIEs Connect to National Frameworks Like TEFCA and eHealth Exchange?
Historically, querying a patient record across state borders required bilateral legal agreements between individual state HIEs. Modern interoperability links state HIEs into nationwide health information networks while maintaining compliance with United States Core Data for Interoperability (USCDI) data classes and ONC Information Blocking Rules (45 CFR Part 171):
- eHealth Exchange Hub-and-Spoke Federation: IHIE, CRISP, NC HealthConnex, and dozens of state/regional HIEs participate in the eHealth Exchange, utilizing Integrating the Healthcare Enterprise (IHE) Cross-Community Patient Discovery (XCPD) and Cross-Community Access (XCA) profiles to exchange C-CDA documents with other states and federal agencies (VA, DoD, SSA, and CMS).
- TEFCA Qualified Health Information Networks (QHINs): Under Section 4003(b) of the 21st Century Cures Act (42 U.S.C. § 300jj-11(c)), state HIEs connect as Participants or Subparticipants to designated TEFCA QHINs (such as eHealth Exchange, Konza National Network, Kno2, Epic Nexus, Health Gorilla, CommonWell, or MedAllies). When an emergency physician in Chicago queries a patient visiting from Indianapolis, TEFCA routes the IHE/FHIR query through the QHIN backbone to IHIE’s INPC repository under the single Common Agreement.
Frequently Asked Questions
How do state and regional Health Information Exchanges (such as IHIE, CRISP, and SHIN-NY) operate?
State and regional Health Information Exchanges (HIEs) operate as health data utilities (HDUs) that aggregate HL7 v2 Admission, Discharge, and Transfer (ADT) alerts, LOINC-coded laboratory results, C-CDA continuity of care documents, and HL7 FHIR resources across competing health systems using an Enterprise Master Patient Index (EMPI).
Which U.S. states mandate hospital and clinic participation in a state HIE?
Several U.S. states enforce statutory HIE participation mandates: North Carolina (N.C. Gen. Stat. § 90-414.4 requiring Medicaid and state-funded providers to connect to NC HealthConnex), California (Health & Safety Code § 130290 Data Exchange Framework under AB 133), New York (10 NYCRR Part 300 requiring hospitals to connect to SHIN-NY Qualified Entities), and Maryland (CRISP hospital ADT and PDMP reporting mandates).
How do state HIEs connect to national frameworks like TEFCA and eHealth Exchange?
State and regional HIEs connect to national interoperability frameworks by acting as Participants or Subparticipants in Trusted Exchange Framework and Common Agreement (TEFCA) Qualified Health Information Networks (QHINs) and eHealth Exchange hubs, using IHE XCA (Cross-Community Access) and HL7 FHIR APIs to resolve cross-state patient queries.
Sources
- Indiana Health Information Exchange (IHIE) & Regenstrief Institute. Indiana Network for Patient Care (INPC) Data & Technical Overview. https://www.ihie.org/
- Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT (ASTP/ONC). Trusted Exchange Framework and Common Agreement (TEFCA). https://www.healthit.gov/topic/interoperability/policy/trusted-exchange-framework-and-common-agreement-tefca
- North Carolina General Assembly. N.C. Gen. Stat. § 90-414.4 — Required participation in Health Information Exchange Network. https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_90/GS_90-414.4.html
