top of page
Search

What Works (and What Doesn't) When States Try to Connect Behavioral Health to Their HIE

There is a persistent fantasy in health IT circles that connecting behavioral health providers to a state HIE is fundamentally the same problem as connecting any other provider. Just get them on the platform, map the data, and the interoperability fairy handles the rest.


If only!


The reality, as anyone who has spent serious time working with behavioral health systems knows, is that HIE connectivity in this sector requires a completely different playbook. Different funding logic. Different legal architecture. Different provider culture. Different consent workflows. Different everything.


A recent study from the HHS Office of the Assistant Secretary for Planning and Evaluation, conducted in partnership with RTI International, examined six states working to integrate behavioral health data into their state HIE infrastructure. The findings are both encouraging and instructive. No two states approached it the same way. All of them ran into predictable walls. And the pattern of what separates progress from stagnation is clear enough that the field should stop pretending it is a mystery.


The Foundational Problem: Behavioral Health Was Left Out on Purpose

Before diagnosing what is not working, it is worth acknowledging why behavioral health providers are behind. They did not fall through the cracks. They were excluded from the EHR incentive programs that accelerated digital adoption everywhere else. Behavioral health clinicians were largely excluded from the EHR Incentive Program and the current Promoting Interoperability Program and were therefore not incentivized to go digital, which explains the persistent lag in adoption compared to other provider types.


That exclusion had cascading consequences. When hospital systems and physician practices were digitizing and connecting to emerging HIE infrastructure in the 2010s, behavioral health providers were still on paper or barely off of it. By the time the field recognized this as a structural equity problem, the gap had already hardened into architecture.


The result is that states building toward integrated behavioral health HIE today are not working from a clean slate. They are retrofitting. And retrofitting is always harder, more expensive, and more politically complicated than building right the first time.


What the ASPE/RTI Study Actually Found

The ASPE/RTI study examined six states that implemented a range of initiatives to support integration of behavioral health data systems into state HIEs, finding that each state adopted its own unique strategies, policies, and funding mechanisms, reflecting the diverse needs and resources of different regions. Rather than pointing to a single scalable model, the research underscores how deeply context-dependent this work is.

That is not a criticism. It is actually the honest answer to a question the field has been asking poorly. The question is not "what is the right model?" The question is "what levers matter most, and under what conditions do they work?"


The study identifies four primary areas of opportunity: legislative frameworks that reduce data sharing barriers, investment in interoperability technologies and standards, targeted financial incentives and technical support for behavioral health providers, and enhanced privacy and consent mechanisms that give patients meaningful control over their data.


Each of those deserves unpacking.


Lever One: Legislation That Removes Barriers (Not Just Authorizes Exchange)

There is a significant difference between legislation that authorizes behavioral health data sharing and legislation that actively clears the path for it. Most states have some version of the former. Far fewer have done the harder work of the latter.


The thorniest terrain involves the intersection of HIPAA, state mental health confidentiality laws, and 42 CFR Part 2. Provider confusion at the intersection of 42 CFR Part 2, the HIPAA Privacy Rule, and the Cures Act information blocking requirements remains a documented barrier to behavioral health exchange adoption, and this confusion is not just an education problem. It reflects genuine ambiguity that state legislative frameworks can resolve, but often have not.


The states that have made the most progress tend to be those that made deliberate policy choices to align their state privacy laws with federal floors rather than layering additional restrictions on top of them. They also invested in clear, published guidance for providers, rather than leaving them to parse federal regulations without support.


In the CMS State Innovation Models Round 1 evaluation, policy and technical barriers to health information exchange impeded progress in almost all six test states, with the patient consent requirements for substance use related information under 42 CFR Part 2, combined with misaligned data systems, making it difficult to share data between behavioral health and primary care providers.


The February 2026 implementation of the updated 42 CFR Part 2 single-consent framework is the most significant regulatory shift this sector has seen in decades. States that have already embedded compliant consent workflows into their HIE architecture are positioned to move faster. Those that have not are now operating with compliance risk layered on top of an already complex onboarding problem.


Lever Two: Funding That Treats Behavioral Health Providers as a Special Case

In the six states examined in the ASPE/RTI case studies, stakeholders were nearly unanimous in their belief that adequate funding is the primary determinant of EHR uptake and HIE connection among behavioral health providers.


This should not surprise anyone. Behavioral health providers operate on notoriously thin margins. Many are small nonprofits, FQHCs, or community-based organizations running on Medicaid reimbursement rates that have not kept pace with inflation, staff turnover, or technology costs. Asking them to fund HIE connectivity out of operating budgets is asking them to choose between interoperability and payroll. They will choose payroll every time.


The states making the most progress have recognized this and acted accordingly. Arizona's Health Care Cost Containment System leveraged CMS-funded programs to support its Whole Person Care Initiative, providing financial incentives to providers who completed a set of milestones tied directly to connectivity and data sharing readiness. That kind of milestone-based incentive structure, where funding is tied to measurable progress rather than just enrollment, is a model worth replicating. ASPE

At the national level, the CMS Innovation in Behavioral Health Model provides state Medicaid agencies with cooperative agreement funding to develop the infrastructure and capacity needed to implement integrated care, including per-person-per-month payments to support screenings, assessments, and social factor evaluations. Three states are currently active in that model, with more to be added over the life of the program through 2032. The infrastructure funding embedded in that model is exactly the kind of sustained, structured investment that drives real connectivity. CMS

Lever Three: Technical Assistance That Meets Providers Where They Are

Behavioral health providers are not a monolith. A large behavioral health managed care organization with its own IT department has fundamentally different needs than a five-clinician outpatient SUD treatment program. State HIE strategies that treat these as the same stakeholder will fail one of them, and usually both.


RTI identified barriers to health IT adoption and interoperability among behavioral health providers that include concerns with patient confidentiality, cost, and gaps in technical training, along with the policies that providers can leverage to improve use of health IT. The technical training gap is especially stubborn because the behavioral health workforce has high turnover, which means that training investments need to be institutionalized, not delivered as a one-time event. RTI International

New York State has demonstrated what is possible when technical investment is paired with a serious commitment to semantic interoperability. New York's Office of Mental Health developed a hybrid semantic interoperability framework powered by FHIR, incorporating terminology mapping across SNOMED CT, ICD-10, and the Gravity Project, along with metadata tagging and consent controls, to enable cross-system data exchange across 22 provider teams operating on heterogeneous EHRs. The technical lift was substantial, but the result is a model that handles the messy reality of a multi-EHR behavioral health ecosystem rather than pretending all providers are on the same platform.


Lever Four: Consent and Privacy Infrastructure Built for Trust

This is the lever that gets the least attention in HIE strategy conversations and causes the most operational failures in execution.


Behavioral health data is different. Patients know it is different. Providers know it is different. The legal framework knows it is different. A state HIE connectivity strategy that does not account for this is not a strategy. It is a hope.


The ASPE/RTI study identified enhanced privacy and consent mechanisms that allow patients to easily control their data as a core area of opportunity, and that framing is exactly right. The emphasis on "easily" matters. Consent frameworks that are technically compliant but operationally burdensome result in consent fatigue, provider avoidance, and patients who disengage from the very systems designed to serve them.


The most effective state approaches have invested in consent management infrastructure that is embedded directly into the care workflow, rather than treated as a separate administrative step. When a patient's ability to selectively share their SUD history or mental health records is as intuitive as checking a box in a patient portal, participation rates go up. When it requires a separate form, a separate system, and a separate explanation, participation rates collapse.


The Divergence Problem: States as the Locus of Innovation and Inequity

One of the more uncomfortable findings across this body of research is that the growing reliance on state-level leadership is simultaneously the field's greatest asset and its most serious structural risk.

States are increasingly determining access, equity, and innovation in behavioral health. In states moving toward integration, there is momentum around integrated systems, parity enforcement, and SDOH-driven care. In others, policy retrenchment and reduced infrastructure investment are widening existing disparities.


This is not a theoretical concern. It is already visible in the data. States that made deliberate policy and funding choices to support behavioral health HIE connectivity are pulling ahead. States that did not are falling further behind. And the populations who pay the price for that divergence are consistently the same: people with serious mental illness, substance use disorders, complex comorbidities, and limited ability to navigate fragmented systems on their own.


Value-based payment models that tie reimbursement to outcomes, readmissions, and care coordination favor organizations with robust data infrastructure, interoperable systems, and integrated care capabilities, while posing challenges for smaller or under-resourced providers. That dynamic accelerates the divergence. HIE-connected behavioral health systems will be better positioned to participate in value-based arrangements. Disconnected systems will be priced out of them.


What the Best State Strategies Have in Common

Across the research, several patterns emerge in states that have made meaningful progress:

They tied HIE connectivity to a clinical use case with visible stakes. Discharge follow-up alerts for high-risk patients. Medication-assisted treatment continuity. Crisis response coordination. The states that framed behavioral health HIE connectivity as a clinical imperative, not an IT project, got more traction with providers and policymakers alike.


They built governance before they built technology. The states that struggled most tended to be the ones that led with infrastructure investment before resolving the policy, consent, and data governance questions. You cannot tech your way out of a trust problem.


They treated behavioral health providers as partners, not passengers. The most effective state programs involved behavioral health providers in governance, in design, and in decision-making from the beginning. The ASPE/RTI study highlighted that these individualized approaches reflect the diversity of needs across regions, and that complex care integration requires states to tailor their efforts to fit local contexts and priorities. Local context knowledge comes from the providers doing the work on the ground.


They treated quality measurement as a driver, not an afterthought. A NASHP expert roundtable found that making behavioral health integration measurement meaningful in practice requires timely and reliable data, stronger integration of claims and clinical information, and clear strategies for using results to drive improvement and accountability. States that embedded quality metrics into their HIE governance structures created accountability loops that sustained momentum beyond initial implementation.


The Bottom Line for HIEs

If you are running a state or regional HIE and behavioral health connectivity is still a backburner priority, the window for comfortable incrementalism is closing. Federal pilots are generating evidence that will shape the next generation of standards. State-level divergence is accelerating. Value-based payment structures are beginning to reward connectivity in ways that will be very visible very quickly.


The good news is that the barriers are well documented and the levers are known. Funding. Legislative alignment. Technical assistance scaled to provider type. Consent infrastructure built for trust. Governance that includes behavioral health voices from the start.


None of this is easy. All of it is possible. And for HIEs serious about the last mile of interoperability, it is not optional.

 
 
 
bottom of page