← All Articles · Healthcare & RHTP ·Nov 11, 2026 ·7 min read

The hardest part of a state Epic instance is getting everyone to yes

What it takes for rural hospitals, state agencies and Epic to commit to one shared record

By Eli Brodsky · Co-Lead · Healthcare Innovation, Technology & Strategy
The hardest part of a state Epic instance is getting everyone to yes — What it takes for rural hospitals, state agencies and Epic to commit to one shared record

A 25-bed hospital has never been able to buy Epic on its own. The license, the hosting and the team to run it cost more than most rural hospitals clear in a good year, so the choice has been to join a large health system's instance or stay on an older system.

The Rural Health Transformation Program changes that math. It sends $50 billion to states over 5 years, and every state is spending part of it on technology. For the first time there is a buyer large enough to purchase an enterprise record on behalf of hospitals that could not: the state itself, or a group organized with state money.

Epic has noticed. KLAS puts Epic at 43.7% of acute care hospitals and 56.9% of beds, and it leads nearly every hospital segment except the smallest standalone hospitals. Those are the hospitals RHTP was written for.

I spent most of 2026 working on this from the state side in Louisiana. The technology was rarely the hard part. Agreement was.

What a state gets out of it

States have worried about 2 things in rural health IT for a long time. Records do not follow patients between a rural hospital, the referral center 90 miles away, the public health clinic and Medicaid. And small providers run expensive systems at volumes too low to carry them.

A shared instance answers both at once. Every participant is on one record, so exchange with public health and Medicaid is built once instead of 30 times. Hosting, upgrades, security and support are bought once and spread across everyone's volume.

I heard the same wish from hospital leaders, public health staff and Medicaid colleagues, each in their own words. Hospitals want less reporting overhead. Public health wants its clinics on a modern record that talks to the hospitals its patients use. Medicaid wants quality data it can pay on. One well-governed instance can serve all 3.

There is a federal limit to plan around. CMS caps spending on replacing certified EHRs at 5% of each annual award, and the money ends after FY30. Whatever a state builds has to stand on participant fees by then.

It is already happening, in 4 different shapes

Epic's hosted offering for this market is called Orchard: each customer gets its own instance on a shared foundation, with Epic handling hosting, upgrades and most third-party contracts. The first known buyers look nothing alike.

WhereWho boughtWhat stands out
Washington3 state agenciesChose Orchard over a systems integrator model to cut cost, time and complexity. Rural providers come in later waves.
WisconsinThe state health department$40 million of RHTP money for a statewide Epic system, with provider costs offset for 5 years. Contract still in negotiation in July.
PennsylvaniaThe health center associationA subsidiary owned by the association contracts with Epic directly. 3 health centers and 35 sites are live.
North DakotaA 2-hospital rural systemThe first acute care system on Orchard. Its CIO says building the implementation team was the hard part.

A state, an association and a rural hospital have each found a way in. What none of them has shown yet is a group of independent rural hospitals coming on together. That is the piece RHTP is supposed to pay for, and it is where the struggle is.

Why consensus is the hard part

A shared instance needs 5 parties to say yes at roughly the same time: the hospitals, the state program office, the agencies that will connect to it, the host that holds the contracts, and Epic. Each one is waiting on another.

  1. Hospitals will not commit without a price, and the price depends on how many hospitals commit. Epic prices by volume. Interest is easy to collect and worth little until a board votes.
  2. Boards approve a ceiling. A CEO cannot take "the state is covering most of it" to a board. They need their own number for each of the next 5 years and a maximum it cannot exceed.
  3. Independence cuts both ways. The hospitals most interested in a state instance are the ones that chose not to join a large system. They are just as wary of a state that decides their IT for them.
  4. There is always an alternative. A nearby health system will offer a seat on its own Epic instance, faster and with less risk. A state offer has to be better on governance or cost, and clearly so.
  5. States are not built to sell or staff this. Recruiting participants is a sales job and running an implementation is a delivery job. A grant office has neither team.
  6. Standard vendor terms and public procurement rules were written for different worlds. Reconciling them takes months that a 1-year budget period does not have.

None of these is a technology problem. Each is a question of who goes first and who carries the risk if others do not follow.

Ways through it

These are options, and different states will need different ones.

  1. Count before you buy. Spend 8 to 10 weeks collecting real volumes, current EHR costs and contract end dates from candidate sites before any license is signed. The answer may be that there is no instance here, and that is worth knowing early.
  2. Start with anchor tenants. State-run public health clinics need a modern record and do not need a board vote. Add 2 or 3 hospitals that are ready, and the first wave has a floor under it.
  3. Give every site its own number. One financial model, shown to the state, the hospitals and Epic, with cost by site and year and a 5-year maximum. Hospitals can compare it to what they pay today.
  4. Let the state pay and set rules, and let someone else build. Wisconsin procured a vendor to host and manage. Pennsylvania put the contract in an association its members already govern. A university, foundation or provider consortium can do the same job.
  5. Offer a choice. Publish the funding formula and let providers pick the state instance, a host health system or another certified system. Support that follows the provider removes the fear of being forced.
  6. Tie it to Medicaid. If the shared build produces the quality reporting Medicaid already requires, joining lowers a hospital's workload on day 1 and supports value-based payment later.
  7. Write the year-5 handoff first. Decide who owns the instance after FY30, what fees cover operations, and which local college trains the analysts who replace the contractors.

The window

RHTP has 4 budget years left. An Epic implementation takes 15 to 18 months once everyone has signed, so a state that wants hospitals live with time to stabilize before the money ends has to reach agreement in the next year.

The states that get there will be the ones that treat consensus as the project. The software will work. The question is whether 10 hospitals, 3 agencies and 1 vendor can agree on a number, an owner and a date.

Explore the Data

Interactive Data Visual · Healthcare & Policy

Epic Orchard: New Opportunities with RHTP

Where Epic Orchard has landed, and where it could go next

Epic Orchard: New Opportunities with RHTP — Where Epic Orchard has landed, and where it could go next

Epic's newest hosted offering has 3 known buyers so far, and none of them looks like the customer Epic first described. A tracker of deals, market share and what stands in the way.

  • Orchard has 3 known buyers: Washington's state agencies, a Pennsylvania health center association and a 2-hospital rural system in North Dakota. Wisconsin has chosen Epic for a statewide system.
  • 12 more states have funded rural EHR work, and most have left the vendor open.
  • No group of independent rural hospitals has come on together yet. Agreement on price, governance and timing is the barrier, not the technology.
Source: Washington HCA, HCMACS Enterprise EHR Roadmap (June 2026); Healthcare Innovation; Health API Guy (Nov 9, 2026); 229 Podcast (Oct 1, 2026); Becker’s Hospital Review; Wisconsin Health News (Jul 22, 2026); Louisiana Department of Health; Vermont and Hawaii procurement notices; Kamen Partners 50-state RHTP scan (Nov 6, 2026). Funding figures mix Year 1 and multi-year amounts, as published. Whether Wisconsin’s contract will use the Orchard model has not been stated. Analysis: Kamen Partners. Open Interactive Visual →

Eli Brodsky is Managing Partner at Kamen Partners, which advises state programs and providers on rural health transformation. An interactive tracker of Orchard deals, market share and barriers accompanies this post.

Sources

Continue Reading · Related Dispatches
Healthcare & RHTP · 7 min read

RHTP and Health Information Exchanges

Related EHR analysis: 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 r…

Healthcare & RHTP · 7 min read

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…

Healthcare & RHTP · 7 min read

RHTP: Most states are getting ready for value-based care. Few are paying for it yet.

Most states are spending their first year of Rural Health Transformation Program money getting rural providers ready for value-based…

#RHTP #Epic #Orchard #EHR #Rural Hospitals