RHTP and Health Information Exchanges
States are spending rural health money on 3 different pieces of the patient data problem, and the order matters more than the vendor.
A rural patient can pass through a clinic, a critical access hospital and a referral center 2 hours away in the same week, and the record often does not make the trip. The Rural Health Transformation Program (RHTP) is the largest pool of money in years aimed at that problem, with $10 billion a year going to all 50 states.
States are not buying the same thing with it. Across the 9 states where I could verify a data or exchange project, I see 3 different bets. Which one a state places first will matter more than which vendor wins the contract.
Most states have an exchange. Fewer have one rural providers use.
Counting exchanges makes the country look well covered. Definitive Healthcare counted 15 active health information exchanges (HIEs) in California and 12 in Texas in October 2024. New York, New Jersey and Pennsylvania had 8 each. Only Iowa, New Hampshire and Wyoming had none.
A high count is not coverage. California and Texas have the most exchanges and neither has a single statewide one. A 2024 state-by-state assessment prepared for Nevada's Medicaid advisory group rated use as well as existence. Grouping its ratings, 26 states have a statewide or federated exchange in moderate or high use, 20 have regional-only coverage, low use or limited services, and 4 had no working statewide exchange: Illinois, Mississippi, New Hampshire and Wyoming.
Even where an exchange is strong, rural sites are often outside it. Missouri surveyed its rural facilities this year and found that 92.4% have an EHR and 33.8% are connected to an HIE. That is the gap RHTP money is being asked to close: the record exists, and it does not move.
Explore the data
RHTP HIEs: Nine states, three bets on the same gap
8 of the 9 states are funding exchange. Only 4 have reached the platform layer.
Each shaded state has at least 1 verified RHTP project on health information exchange, EHRs or data platforms. Use the approach filter to see who is funding what. Tap or hover a state for its projects.
- 8 of the 9 states with a verified RHTP data project are funding health information exchange.
- Of 16 verified opportunities, 3 are awarded, 4 closed without a winner announced, 6 are open and 3 are planned.
- Sequence matters: capture a usable record at each site, connect it across care settings, then apply AI and applications on pooled data.
The explorer has 5 views. The map shows which states have a verified project and which approach each is funding. HIE coverage shades every state by its number of exchanges, with a switch to coverage and use. The money shows the opportunities that carry a public dollar figure. Three approaches lists every project with its status. Sequencing lays out one possible order.
Three bets on the same gap
Each approach buys a different piece of the patient's data.
| Approach | What it buys | Where it shows up |
|---|---|---|
| The clinical record | A complete history in one chart: notes, labs, imaging | Mississippi is replacing EHRs for small rural providers. Oklahoma is asking EHR vendors for information. Virginia made 25 provider awards worth $14.39 million. |
| The connected journey | One patient followed across care settings | Mississippi went to bid on a statewide HIE. Iowa replaced its statewide operator. Maryland pays rural providers up to $40,000 each to connect to CRISP. West Virginia put $855,400 into its exchange. |
| The AI and application platform | A layer that runs tools on pooled patient data | West Virginia bid out a statewide Data Spine. Utah offered up to $11 million for a semantic data model. North Dakota asked vendors about population health tools. |
Some states are placing more than 1 bet at once. Utah has money out under all 3. West Virginia is funding its exchange and a platform in the same year.
A lot is under way, and some is still being planned
Of the 16 opportunities I could verify, 3 are awarded, 4 closed without a winner announced yet, 6 are open and 3 are planned. Exchange is furthest along. The platform layer has no award yet: West Virginia's Data Spine and Utah's data model are both in review, and North Dakota's request was for information only.
What is open now is mostly record and exchange money for providers. Utah's technology and data exchange application closes November 20. Mississippi's EHR replacement program closes November 23. Oklahoma's vendor request for information closes December 1 and its help connecting to the state exchange runs through December 31.
Public dollar figures are scarce. Only 6 of the 16 carry one, and Utah accounts for 3 of them, with up to $31.9 million across all 3 approaches. Most statewide exchange and platform bids, including Mississippi's and West Virginia's, have not published a contract value.
Sequence matters more than the choice
The 3 bets are layers, and they stack in one order.
- Capture. A usable record at each rural site. Without it there is nothing to exchange.
- Connect. Exchange across care settings, so the record follows the patient.
- Apply. AI and applications working on pooled data.
The platform is the only bet that cannot stand alone. It needs patient data that the record and the exchange supply. A state that buys the top layer first is betting the lower layers fill in fast enough to feed it.
A federal deadline is about to help the middle layer. On January 1, 2027, the CMS interoperability and prior authorization rule requires Medicare Advantage plans and state Medicaid programs to run Provider Access, Payer-to-Payer and Prior Authorization APIs. Claims and authorization data will start moving through standard connections. The same Medicaid agencies that must meet that deadline are often the ones running RHTP data investments, which is a reason to plan the 2 together.
Technology is the easier half. In my experience working with rural hospitals, public health and Medicaid, agreeing on who governs shared data takes longer than installing it.
What about Louisiana?
Louisiana's starting point is different, and it is why I believe the order matters. The state has 2 exchanges with different capabilities and uneven data quality, and neither is reliably comprehensive. The largest pools of patient data sit outside both of them: Epic holds a large share of the state's clinical records, and Medicaid holds the claims for every Medicaid beneficiary in Louisiana. The natural response to that fragmentation is to keep building, a new platform for each problem, each with its own data model and its own vendor. That is how a state ends up with more systems and less exchange than it started with.
A single, complete exchange is the stated goal in most states, and it was ours. It also runs into a structural problem: RHTP is rural money, and the data problem is not rural. The referral center 2 hours away is usually in a city, and a record that stops at the parish line has not made the trip that matters.
The work in front of Louisiana is to map it all out. Before funding new connections, we need to see where the data already lives, which systems could actually exchange with each other, and where the gaps are. To find gaps, the question we need to keep asking is not how many interfaces the state bought, but which patient journeys are broken and why.
Alongside the record and exchange work, Louisiana is building the measurement layer at the same time: a rural health data atlas and the reporting structure that ties RHTP dollars to the providers receiving them and the outcomes those dollars are supposed to move. That only works if the underlying data is standardized enough to compare across sites. Where the record stays fragmented, a state can report what it spent, but not what the spending changed.
What to watch in early 2027
- Mississippi expects to sign its statewide HIE contract on December 30 and start services in January. It is the clearest case of a state with no working exchange using RHTP to build one.
- Texas estimates a January 12 deadline for 2 initiatives: patient portals run through clinically integrated networks, and AI and telehealth. Both dates are state estimates.
- Virginia's next provider interoperability round is expected in March.
- West Virginia and Utah still have to name winners for their platform bids. Those awards will show what a state-level AI and application layer costs.
- The January 1 payer API deadline will show how many Medicaid programs are ready, and how many will need help.
Sources and method
Project status is as of November 12, 2026 and includes only items confirmed on a state or program page. Exchange counts are from October 2024. The coverage groups are my reading of a 2024 assessment that rates use by state, and the 2 sources do not always agree.
- Definitive Healthcare, number of HIEs by state
- HIE landscape by state, Nevada Medicaid advisory group
- CHI Health, HIE by state
- Missouri RHTP digital readiness report
- NRHA, RHTP RFP status by state
- Utah DHHS RHTP funding opportunities
- Mississippi RHT Program funding
- Oklahoma RHTP funding
- CRISP Rural Health Connectivity Program
- Virginia Health Care Foundation, October 2 awards
- West Virginia Data Spine and WVHIN award
- Iowa statewide HIE operator
- Texas HHSC RHTP
- CMS-0057-F fact sheet
The hardest part of a state Epic instance is getting everyone to yes
Related EHR analysis: A 25-bed hospital has never been able to buy Epic on its own. RHTP gives states the buying power to change that, but a shared instan…
RHTP: Most states are getting ready for value-based care. Few are paying for it yet.
Related Medicaid analysis: Most states are spending their first year of Rural Health Transformation Program money getting rural providers ready for value-based…
The patients are there. The specialists aren't.
Of the 444 critical access and other rural hospitals in Texas, Louisiana, Mississippi, Alabama, Georgia, Florida and Arkansas, 380 a…