Somewhere in a tribal health department this week, a director is reading a health IT vendor comparison chart and trying to work out which column applies to a four-provider clinic with a dental suite, a behavioral health program, a pharmacy, and a community health representative who drives 90 miles to do home visits. That chart wasn’t written with the clinic in mind. It was written for a 400-bed system with a CIO, a contracts office, and three people whose entire job is interfaces. The gap isn’t a formatting problem. It decides which questions get asked during procurement, and which ones nobody thinks to ask until year three, when the answer is expensive.
Who the market data is actually counting
Health IT market share gets measured in hospitals and inpatient beds. That single choice of denominator explains most of what feels off about vendor rankings when you read them from a tribal clinic.
KLAS’s 2026 US acute care EHR market share report put Epic at 43.7% of U.S. acute care hospitals and 56.9% of inpatient beds, with Oracle Health at 21.9%, Meditech at 14.7%, and TruBridge at 7.6%. Epic added 77 acute care hospitals over the year while Oracle Health shed 56. Only two health systems with more than ten hospitals made an enterprise-wide EHR decision at all, and both picked Epic.
Read that carefully and you’ll notice what it doesn’t measure. A health center with no inpatient beds contributes nothing to those percentages. Neither does a health station, an Alaska village clinic, or a mobile dental unit. The vendors at the top of the table earned their position by winning multi-hospital enterprise deals, which is a genuine achievement at a genuinely different problem than the one in front of a tribal health program.
So when a chart says a vendor is dominant, the honest translation is narrower: dominant among organizations that count their sites in dozens and their beds in hundreds. That tells you who has capital and staying power. It tells you almost nothing about who will show up in Fort Yukon.
What a vendor roundup can and can’t tell you
Vendor roundups are still worth reading, as long as you read them for what they are. They rank by revenue, headcount, client logos, and hospital counts, which makes them a decent map of the incumbents and the acquisition history behind them. A published list of top healthcare software companies is one such snapshot of scale, useful in the same way a market-share table is useful: it shows how the industry maps itself, and it tells you which names will still exist in eight years.
Scale is also the axis a tribal health program has least in common with. A roundup organized around company size will not answer the things that decide whether an implementation succeeds on a reservation or in a village:
- Whether the vendor has ever configured a system for a program that bills third parties, runs Purchased/Referred Care, and reports to a tribal epidemiology center
- What the implementation team looks like at your size, as opposed to the team a 12-hospital system gets
- Who owns the clinical data, where it physically lives, and what leaving costs
- Whether the product treats dental, behavioral health, and community health as first-class modules or as afterthoughts bolted onto an acute care core
None of that is a knock on the companies listed. It’s a mismatch between what a ranking is built to compare and what you actually need compared. Use the roundups to build your longlist and to understand the field. Don’t let them set your criteria.
Your facility mix is not their facility mix
The shape of the Indian health system makes the mismatch concrete. Under Indian Self-Determination and Education Assistance Act contracts and compacts, tribes and Alaska Native corporations administer 22 hospitals, 330 health centers, 76 health stations, and 146 Alaska village clinics, alongside a federally operated system of 21 hospitals, 53 health centers, and 25 health stations. Roughly 40% of the IHS appropriation is administered by tribes.
Count those sites: the overwhelming majority are ambulatory, and most of them are tribally run. Any vendor evaluation that starts from an inpatient-centric feature list is already measuring the wrong thing for most of Indian Country.
That’s the backdrop for the federal modernization now underway. In November 2023, IHS selected General Dynamics Information Technology to build and maintain a new enterprise EHR on Oracle Cerner technology, named Patients at the Heart, or PATH, replacing the Resource and Patient Management System after four decades. The award was structured as a ten-year contract with a ceiling above $2.5 billion, and the program’s life-cycle cost estimate, the figure tribal leaders have repeatedly raised in budget testimony, runs from roughly $4.5 billion to $6.2 billion across those ten years.
A self-governance tribe is not obligated to follow that path. That’s the point of 638 authority: the decision belongs to the tribe, not to a federal program office. But choosing your own system means owning the interoperability question yourself, including how records move between your facility and the IHS-operated hospital your patients get referred to, and how your reporting obligations get met without a federal integration team behind you. Either choice carries real cost. The difference is who controls the timeline.
Questions to put on the table before the demo
A demo is designed to show you the product at its best. The way to get past that is to arrive with questions the sales engineer can’t answer from a slide. These are the ones worth asking first:
- Name three programs of our size and service mix that you’ve implemented in the past three years, and give us their contacts.
- Walk us through third-party billing as it works for a tribal facility, including the reimbursement pathways specific to services delivered through an IHS or tribal site.
- Who owns the data in this contract? Where does it reside, who can access it, and can we audit that access?
- If we terminate, what format do we get our records in, how long does extraction take, and what does it cost?
- What does exchange with PATH and with IHS-operated facilities look like, in production, today?
- During implementation, how many of your people are physically on site, for how many weeks, and how many of our staff will be pulled off clinical duty?
- How does the system handle Purchased/Referred Care, and dental and behavioral health documentation, without a separate product?
Get the answers in writing, and get them before price comes up. A vendor that can’t name a comparable tribal client is asking you to fund their learning curve.
What to do with this
Vendor rankings are a starting point for a longlist, not a shortlist. The scale that puts a company at the top of a market-share table is the same scale that shapes its implementation model, its pricing floor, and its assumptions about your staffing.
Three things worth acting on: build your evaluation criteria from your own service mix before you look at any ranking; make data ownership and exit terms contract language, not a verbal assurance; and ask every finalist for tribal references at your size. Sovereignty over your health data starts with the questions you ask before you sign.
