What are rural primary care clinics going to look like in 2031?
Here’s what we imagine. The building looks better than it did five years ago. It also has some sweet new features. A brand new telestroke consulting room connects with neurologists 180 miles away. Two of the three providers came out of a rural residency program that the state funded in 2028, and they stayed because the loan repayment was worth it.
The EHR got upgraded in 2027 and now talks cleanly to the state health data utility. There's a chronic disease management program running out of a converted supply closet. The waiting room has new furniture. Everything looks better.
The problem is that the clinic still can't make its numbers work.
Denial rates are still over 15%. A third of the practice’s inbound calls still go unanswered. Credentialing lag still means new providers spend their first ninety days seeing patients but not getting paid. The practice is still subsidizing itself out of a shrinking operating reserve.
And the federal Rural Health Transformation Program funding that paid for the telestroke room, the residency, and the EHR upgrade ended on September 30, 2030.
The clinic is on its own now.
I’ve spent 30 years working with healthcare organizations. I've also lived all across rural America, in Oregon, North California, Montana, and Arkansas. You can thank Continuant for that experience. In fact, I was the company’s first employee.
I’ve watched HITECH, the ACA exchanges, the provider relief funds, and multiple rounds of rural grants come and go. The pattern remains the same: whatever the funding paid for stays in a physical sense. The buildings are still there. The equipment sits on the depreciation schedule. The residents finish their commitment and leave for the city.
What doesn’t stay is the operating subsidy. When it disappears, the economy reasserts itself. That means the EHR, the equipment, the whole improved infrastructure becomes one more thing the practice can’t afford to maintain.
This is what I think state administrators and rural health leaders need to be talking about right now, in April 2026, before another five years of federal money starts flowing into patterns that won't outlast it.
Let me be specific about what I'm calling a cliff. The Rural Health Transformation Program, authorized under Section 71401 of Public Law 119-21, distributes $10 billion per year for five years (FY2026 through FY2030). Oklahoma secured $223.5 million in first-year funding. South Dakota secured $189.4 million. New Mexico got $211.5 million. These are meaningful sums, and they're going to do real work.
But the legislation does not extend beyond FY2030. There is no year six. There is no phased reduction. On October 1, 2030, the tap closes.
Whatever initiatives states built with RHTP dollars have to be self-sustaining by then or they stop. I recently spoke with a hospital COO in Wyoming and while the State of Wyoming tried to allocate some RHTP funds into a trust to pay for additional recurring expenses beyond 2030, the federal government killed the idea. The cliff remains undefeated.
States know this. Oklahoma's own RHTP project narrative explicitly names the problem: "By FY2031, all initiatives will operate on sustainable funding models — through billable services, payer reimbursement, cost sharing, or braided public and private funding." \
That sentence is doing an enormous amount of work. It's the state committing on paper that every dollar spent between 2026 and 2030 must produce something that can pay for itself afterward. It's an unambiguously correct goal. The question is whether the specific initiatives being funded today can actually meet it.
Telestroke networks are a good example. They address a real symptom — rural patients experiencing strokes don't get fast enough specialist consultation; outcomes suffer. A telestroke network solves that.
But a telestroke network does not fix why the rural hospital that installed it was already struggling financially. The hospital was struggling because its reimbursement per case doesn't cover its fixed costs at rural patient volumes. Adding a telestroke service line generates some incremental revenue but doesn't change the underlying math.
When the RHTP subsidy for the telestroke infrastructure ends, the hospital still has to pay for the equipment, the connectivity, the vendor contract, and the staff time. The telestroke line item moves from grant-funded to operating-budget-funded, and the operating budget was already insufficient.
Residency placements are another example. Training rural physicians is a real need, and the evidence is good that physicians who train rural tend to practice rural, at least for the first few years.
But a residency placement doesn't change the economics of the practice the resident eventually joins. If a family medicine practice in rural Oklahoma couldn't profitably employ a physician in 2025 — because of denial rates, missed patient demand, credentialing friction, payer mix, or uncompensated care — it can't profitably employ one in 2031 either. The state funded the training, but the training produces a physician who still needs a practice that works. If the practice doesn't work, the physician leaves.
EHR upgrades are a third example. EHR modernization is important and, in some cases, overdue. But an EHR is a cost, not a revenue generator. It's something the practice has to maintain. If the practice wasn't making enough money to afford a modern EHR in 2025, buying it a modern EHR in 2027 with grant money doesn't fix the underlying problem — it just gives the practice one more thing it can't afford to maintain in 2031.
Microgrants, workforce pipelines, transportation support, behavioral health integration, community wellness hubs — I don't want to dismiss any of these. They're all good uses of money and they all serve real needs. But in almost every case they are addressing downstream symptoms of a single upstream disease: rural practices and rural hospitals, at rural patient volumes, do not generate enough collectable revenue to cover the cost of running a modern healthcare operation.
That is the root cause. Everything else is a symptom.
Taking the lack of revenue into account, the only class of investment that can survive the cliff in year six is one that changes the revenue side of the equation — and does so fast enough that the investment is paying for itself well before the RHTP window closes.
I want to describe what that looks like concretely, because this is the part of the rural health conversation that has not been happening and needs to start happening.
A typical rural practice or critical access hospital is leaking revenue in three categories simultaneously, and those three categories interact in ways that a fragmented vendor stack cannot see.
The first category is missed patient demand at the access layer. Phones ring unanswered. Appointment requests get lost in voicemail. Insurance verification fails at intake, and the patient walks out. No shows aren't proactively rebooked because nobody has time to chase them. The hospital never bills for this care because the care never happened — not because the patient didn't need it, but because the access infrastructure couldn't convert demand into visits. In a typical rural primary care practice, somewhere between 20% and 35% of inbound patient demand is lost at this layer. That's not a soft number. Those are real patients with real needs and real reimbursement attached to them, walking away from the practice because the front of the funnel is broken.
The second category is leaked collections at the operations layer. This is dollars the hospital already earned but didn't collect. Credentialing lag means new providers are seeing patients but not getting paid by half the payers for 60 to 90 days. Denials arrive and don't get appealed because the appeal window closed before anyone noticed. Claims get submitted with preventable errors because nobody is scrubbing them against payer-specific rules. Denial patterns concentrate in specific procedure codes with specific payers, and nobody traces them back to root cause because nobody is looking across the whole revenue cycle from a single vantage point. The services were delivered. The patients were seen. The money just leaked through operational fragmentation.
The third category — and this is the one that most rural administrators underestimate — is the compounding cost of operational blindness. A rural hospital typically runs its patient access, its clinical scheduling, its revenue cycle, and its supply chain as four separate systems with four separate vendors and four separate data layers. The problems that matter most for rural profitability live in the gaps between those systems, and none of the individual systems can see them.
The clinic has three days of unscheduled capacity next week that nobody has noticed, while simultaneously turning away patients calling for the same days because the scheduler has no visibility into clinical capacity. The hospital is paying a staffing premium for Tuesday coverage when Tuesday is actually the lightest day on the clinical calendar.
The practice is underperforming with a specific commercial payer not because the payer is hostile but because denial patterns are concentrated in one procedure code that nobody has traced. A surge in diabetic management visits is coming over the next six weeks based on population-level signals, but nobody knows it's coming, so consumables run short and reorders happen at premium shipping rates.
High-risk patients aren't being proactively outreached because the clinical system doesn't know which patients in the panel are high-risk. A provider in the network is about to leave because the satisfaction signals have been visible for six months, but no retention strategy has been triggered because nobody was watching.
Every one of these is invisible to any single system. An integrated AI operating platform that unifies data across access, staffing, revenue cycle, and supply chain — with a predictive intelligence layer reading across the unified data — sees all of them. It identifies underperforming providers and matches them to retention strategies before attrition happens. It forecasts demand for specific services and aligns staffing and supplies accordingly, eliminating both overtime expense and stockouts. It clusters patients into cohorts for targeted outreach on high-risk conditions. It simulates facility performance scenarios to identify which service lines are profitable and which are bleeding cash. It scores asset readiness and automates supply workflows so procedures don't get delayed by missing inventory. This is not speculative technology. This is AI that exists today, and when it's deployed properly at a rural hospital or practice, the revenue recovery is measurable within weeks.
Here's what the math looks like for a typical rural hospital adopting an integrated platform of this kind. The platform is a real expense, a line item on the operating budget, paid monthly, just like any other vendor. It’s not free. What distinguishes it from every other RHTP-funded investment is the time to positive return.
Based on the deployment economics of integrated operating platforms at rural hospitals, a typical facility crosses the break-even point around month three. From that point forward, every additional month of deployment widens the gap in the hospital's favor, because the recovered revenue and the operational efficiency gains keep compounding while the platform cost stays flat. By the end of year one, the hospital is cumulatively net positive. By the end of year five — which is when RHTP funding ends — the hospital has captured multiples of the platform cost in recovered revenue and avoided expense, and the platform has entirely paid for itself many times over without any remaining subsidy requirement.
This is what a cliff-proof investment actually looks like. Not an expense that has to be maintained forever without generating revenue. An investment that becomes self-funding inside the first year of deployment and stays self-funding through the RHTP window and beyond.
Here is the structural issue I think state RHTP administrators need to confront in the next few weeks.
Most states have structured their RHTP applications around discrete initiatives that map to CMS's five strategic goals — prevention, sustainable access, workforce, innovative care, technology innovation. Those initiatives are then procured through separate RFPs or Notice of Funding Opportunity releases, one per initiative. A state will run one RFP for telestroke networks, another for workforce pipelines, another for EHR expansion, another for microgrants, and so on. Each RFP asks for vendors who can deliver that specific initiative.
An integrated operating platform doesn't fit any of those RFPs cleanly, because it isn't a single initiative. It touches patient access, credentialing and RCM, data intelligence, supply chain, and care model transformation simultaneously. A vendor offering an integrated platform can't respond coherently to a telestroke RFP or an EHR RFP — the fit is partial at best and the evaluation criteria don't match what the platform actually does.
The consequence is that integrated operating models get structurally excluded from RHTP procurement, not because states have evaluated them and rejected them, but because the procurement architecture doesn't have a pathway for them. And once that architecture is set in April and May of 2026 for the first year of RHTP funding, it tends to calcify for the remaining four years. States that procure initiative-by-initiative in FY26 will keep procuring initiative-by-initiative through FY30. States that build in a pathway for integrated-platform procurement in FY26 will have that option for five years.
This is a procurement design decision that's being made right now, this spring, by state health department officials across fifty states. Most of them don't know they're making it. They think they're just releasing the first round of RFPs for the initiatives they committed to in their approved RHTP plans. They are not thinking about whether the architecture of those RFPs leaves room for a different class of solution.
I am asking for a specific, bounded, measurable action.
Create a Rural Sustainability Pilot Pathway inside your RHTP procurement architecture. The pathway funds year-one deployment of integrated operating platforms at a cohort of ten to twenty rural hospitals or critical access facilities, with one non-negotiable evaluation criterion: the platform must demonstrate net positive revenue impact within twelve months of deployment. Recovered revenue must exceed platform cost by the end of year one, measured against a rigorous pre-deployment baseline the state helps establish.
The structure of the pathway answers the cliff problem directly. RHTP funds year one. The measured outcomes from year one determine whether the pilot expands in year two. Hospitals that meet the criterion continue operating the platform from their own budgets in years two through five, because the platform is now generating more revenue than it costs — exactly the sustainable funding model that Oklahoma's own RHTP narrative commits to achieving by FY2031.
At Oklahoma's allocation level, a twenty-hospital pilot would require somewhere between $20 and $40 million in year-one funding, which is roughly 10-15% of the state's annual RHTP allocation. It is not a new spending category competing with the state's existing initiatives. It is a single dedicated pilot that tests a specific thesis — that integrated operating platforms can deliver cliff-proof rural sustainability — with a clear success criterion and a clear off-ramp if the thesis doesn't hold up. If the pilot succeeds, the state has a proven pathway for the remaining four years of RHTP funding. If the pilot fails, the state has spent a modest portion of one year's allocation to learn that integrated platforms don't deliver what they claim, and can redirect in year two.
The pathway is open to any vendor that can demonstrate the twelve-month revenue criterion. This is not a sole-source argument. It is a category argument. Any qualifying integrated platform should be eligible to compete, and the outcomes-based evaluation criterion protects the state from vendor overpromising because the criterion is measured in actual collected revenue at actual hospitals, not in slide-deck projections.
The alternative is to structure all RHTP procurement as initiative-by-initiative RFPs, address the symptoms the state originally committed to address, and arrive in October 2030 with a rural healthcare system that still doesn't work economically — only now it has better telestroke coverage, more recent EHR installations, and a decade of residency graduates who have mostly left for urban practices because rural ones couldn't afford to keep them.
I don't think that's what anyone intends. I think that's what happens by default if procurement architecture isn't deliberately designed to include integrated operating models as a distinct category with their own evaluation pathway.
In Oklahoma, the Community-Led Wellness Hubs Microgrants NOFO closes on April 13. The next round of solicitations will follow shortly after. In South Dakota, the first RFP has already released and subsequent ones are in preparation. Pennsylvania's first RFPs were announced in early April. Colorado is still in advisory committee mode but expects to begin procurement this spring. Every state is moving through the same compressed timeline, because CMS is requiring first-year funding to be obligated quickly.
If I had one message for every state RHTP administrator reading this, it would be: before your next RFP releases, spend thirty minutes asking whether your procurement architecture has a pathway for integrated operating-model solutions — and if it doesn't, build one. Not because you've been sold on a specific vendor, but because the sustainability language in your own RHTP plan requires investments that change unit economics, and unit economics rarely change unless the operating model changes. The Rural Sustainability Pilot Pathway I've described is one way to create that pathway without disrupting anything else you've committed to. Other structures are possible. The specific mechanism matters less than the recognition that the category needs to exist inside your procurement architecture, and that it needs to exist before the next round of RFPs releases and the architecture calcifies for the remaining four years of the program.
Five years goes faster than anyone thinks. The cliff in year six is not hypothetical. It's already scheduled. The only question is what's standing when it arrives.