Key Takeaways
- Interoperability lets your EHR send, receive, and use data from labs, registries, health information exchanges, and other providers without faxing or retyping.
- Standards such as HL7 and FHIR make data readable across systems. Networks such as HIEs, Carequality, and TEFCA make it reachable.
- Behavioral health organizations face added hurdles, including standalone telehealth tools and 42 CFR Part 2 consent rules for substance use disorder records.
- The HTI-5 final rule (October 2026) removed 14 federal certification criteria, but information blocking rules still apply to providers, developers, and HIEs.
- When you compare vendors, ask them to demonstrate live connections with your actual partners during the demo.
EHR interoperability is the ability of your electronic health record (EHR) to securely exchange patient information with other systems and use that information once it arrives. Those systems include hospital and clinic EHRs, laboratories, pharmacies, immunization registries, and health information exchanges (HIEs). When it works, a lab result or screening entered in one system lands in the right chart elsewhere, with no fax and no re-keying.
For public health and behavioral health teams, interoperability is what makes whole-person care practical. It gives everyone on a care team the same history, screenings, and care plans. It also cuts duplicate testing and frees staff from chasing records. This guide covers how interoperability works, where it breaks down in behavioral health, which federal rules shape it in 2026, and what to ask EHR vendors.
What Is EHR Interoperability?
EHR interoperability means different health IT systems can exchange data automatically and put it to use without manual work. The National Academy of Medicine (NAM) describes it as sharing information across time and place, from many devices, sources, systems, and organizations.
Two layers make that possible. Standards define how data is structured so the receiving system can read it. Networks define who can connect and under what agreements. Most organizations need both.
- HL7 messaging: A long-standing standard from Health Level Seven International for sending structured clinical messages. Example: sending vaccine doses to a state immunization registry.
- FHIR (Fast Healthcare Interoperability Resources): An HL7 standard for exchanging data through an application programming interface (API), a defined way for software to request and return data. Example: pulling payer data or connecting a patient-facing app.
- Health information exchange (HIE): A regional or state network that pools records across facilities. Example: importing a hospital discharge summary into the chart.
- Carequality: A national, consensus-built framework that links many data-sharing networks. Example: requesting records from a provider outside your region.
- TEFCA (Trusted Exchange Framework and Common Agreement): A federal network-of-networks framework run through Qualified Health Information Networks (QHINs). Example: exchanging data for treatment or public health purposes across networks.
How Does Interoperability Help Health Departments and Behavioral Health Organizations?
Interoperability gives each team the data it needs at the point of care without extra steps. Health departments get complete immunization histories and easier reporting. Behavioral health organizations get faster coordination with primary care, crisis services, and community partners.
For Public Health Departments
When the EHR connects to the state immunization registry, nurses can see a patient's full vaccine history during the visit and record new doses once. TEFCA lists public health as a permitted exchange purpose, which supports data sharing between health departments and providers across networks. Connections to programs such as the Special Supplemental Nutrition Program for Women, Infants, and Children (WIC) and home visiting also give staff a fuller view of each patient's needs.
For Behavioral Health Organizations
Through an HIE or Carequality, a counselor may be able to see depression or substance use screenings completed during a client's primary care visit. Crisis plans and care updates can reach housing services, mobile crisis teams, and emergency medical services (EMS) partners, with client consent where required. Each fax that a connection replaces also removes a delay when a client moves between levels of care.
What Are the Biggest EHR Interoperability Challenges in Behavioral Health?
The biggest hurdles are disconnected tools, outside partners that aren't ready to exchange data, and stricter consent rules for substance use disorder (SUD) records. Each one pushes staff back to faxes, phone calls, and manual entry.
Standalone telehealth platforms. Many behavioral health organizations run telehealth on a separate platform. Clinicians then copy session details, histories, and visit summaries into the EHR by hand, which adds documentation delays and raises the risk of errors and missed follow-ups.
Partner readiness. An exchange only works if the lab, hospital, or HIE on the other end can connect. Ask whether your EHR vendor has live connections with the partners you rely on, or only supports the standards in theory.
Part 2 consent rules. Federally assisted SUD programs must follow 42 CFR Part 2, which limits when SUD records can be shared. The 2024 final rule allows one client consent to cover future uses for treatment, payment, and health care operations, and compliance was required by February 16, 2026. Your EHR needs to record which consent applies and flag Part 2 records before they leave the system.
Administrative load. Without reliable exchange, front-desk and records staff fax documents, re-enter data, and search several systems for one answer. That time comes directly out of client support.
How Does an EHR Support Behavioral Health Integration (BHI)?
Behavioral Health Integration (BHI) means primary care and behavioral health providers treat the same person as one coordinated team. An EHR supports BHI with built-in screening tools, shared care plans, referral tracking, and automated follow-up, so patients don't fall into the gap between two offices.
What the Research Shows
A 2016 study published in JAMA followed more than 113,000 adults at Intermountain Healthcare primary care practices from 2003 through 2013. Patients in integrated team-based practices had higher quality scores on some depression and diabetes measures, fewer emergency department visits and hospital admissions, and lower payments to the health system.
The results come with limits. Hypertension control was lower in the team-based group, and the study took place in a single large, integrated health system. It shows an association between integration and better outcomes, which is strong evidence but not proof that every practice will see the same results.
Where Integrated Care Breaks Down
Integrated care usually stalls for three reasons: primary care and behavioral health providers don't share information routinely, primary care teams lack time or staff to address behavioral health needs, and stigma keeps patients from raising concerns or providers from documenting them.
EHR Features That Support BHI
- No in-house behavioral health staff: The EHR should offer standardized screening tools for depression, anxiety, and substance use, with reporting.
- In-house behavioral health staff: The EHR should keep treatment plans and progress notes in the same record as medical care.
- Referring to outside providers: The EHR should create referrals, track their status, and send automated follow-up messages to confirm patients received care.
Which Federal Rules Shape Interoperability in 2026?
Three sets of rules matter most: the Office of the National Coordinator for Health Information Technology (ONC) HTI rules for certified health IT, Centers for Medicare & Medicaid Services (CMS) rules for payers, and 42 CFR Part 2 for SUD records. Information blocking rules under the 21st Century Cures Act apply across all of them.
ONC's Health Data, Technology, and Interoperability (HTI) Rules
ONC uses the HTI prefix for its health IT rules, numbered in the order they're released.
- HTI-1 (January 2024): Updated the certification program, added transparency requirements for algorithm-based decision support tools, and revised information sharing rules.
- HTI-2 (December 2024): Put core TEFCA provisions into federal regulation.
- HTI-3 (December 2024): Revised the Privacy and Infeasibility exceptions to information blocking and added a Protecting Care Access exception.
- HTI-4 (August 2025): Added certification criteria for electronic prescribing, real-time prescription benefit checks, and electronic prior authorization.
- HTI-5 (October 2026): Removed 14 of 60 certification criteria, revised 7, scaled back Real World Testing and reporting requirements, and set a new foundation for FHIR-based API requirements
Fewer certification criteria don't lower the bar for sharing data. Information blocking rules still apply to health care providers, developers of certified health IT, and HIEs. The U.S. Department of Health and Human Services (HHS) Office of Inspector General can investigate claims against any of them. As certification requirements shift, vendor accountability and your own oversight matter more.
CMS Interoperability Rules for Payers
The 2020 CMS Interoperability and Patient Access final rule (CMS-9115-F) requires Medicare Advantage plans, Medicaid and the Children's Health Insurance Program (CHIP), and Qualified Health Plans on the federal exchanges to offer patient access APIs. A 2024 follow-up rule (CMS-0057-F) added prior authorization data and new API requirements. These APIs can connect to a provider's EHR, which gives clinics another route to payer data.
42 CFR Part 2 for SUD Records
Part 2 applies to federally assisted programs that diagnose, treat, or refer clients for SUD. After a client signs a single consent for treatment, payment, and health care operations, HIPAA-covered recipients can share those records again as HIPAA allows, except in legal proceedings against the client. The HHS Office for Civil Rights now enforces Part 2.
How Do You Choose an EHR That Supports Interoperability?
Ask vendors to prove data exchange in your real workflows. The NAM report points to purchasing requirements, more than technology, as the biggest barrier to interoperability. That makes your selection process one of the strongest tools you have.
Use these steps during vendor evaluation:
- List your top exchange partners, such as the state immunization registry, regional HIE, reference labs, local hospitals, and crisis services. Ask which connections are live today.
- Confirm the product's certification status on ONC's Certified Health IT Product List (CHPL).
- Ask which standards and networks the vendor supports, including HL7 interfaces, FHIR APIs, HIE connections, Carequality, and plans for TEFCA.
- For behavioral health, confirm the EHR can record Part 2 consent and flag protected records.
- Watch a full referral loop in the demo: send a referral, receive the result, and trigger an automated follow-up.
- Ask how the vendor's roadmap responds to HTI-5 changes and how it supports your information blocking obligations.
FAQs About EHR Interoperability
What's the difference between integration and interoperability?
Integration usually means a custom connection between two specific systems. Interoperability means systems share common standards, so data can move between many systems and stay usable. A quick test: if adding a new partner requires a custom build, you have integration.
Are EHRs required to be interoperable?
No single law requires every EHR to be interoperable. ONC certification is a voluntary program for developers, though some federal payment programs require certified technology. Separately, information blocking rules prohibit providers, certified developers, and HIEs from unreasonably interfering with access to electronic health information.
Can behavioral health organizations share SUD records through an HIE?
Yes, under conditions. With a client's single consent for treatment, payment, and health care operations, Part 2 records can go to HIPAA-covered providers and health plans. Without consent, sharing is limited to narrow exceptions, such as medical emergencies. State privacy laws may add further limits.
What's the difference between Carequality and TEFCA?
Carequality is a consensus-built, national framework that connects existing networks through a common agreement. TEFCA is the federal framework created by ONC. It runs through designated QHINs, and The Sequoia Project manages it as the Recognized Coordinating Entity.
What does HTI-5 change for my organization?
HTI-5 mainly affects EHR developers. It removed 14 certification criteria, revised 7, and reduced testing and reporting duties. Your obligations under information blocking rules stay the same, so ask your vendor which removed criteria touched features your staff use.