EHR Vendor Intelligence
Which certified EHR systems hospitals actually run: vendor share, hospital finder, upgrade and switch signals, migrations, a territory planner, partner ecosystems, shared IT systems and vendor certification health.
Open EHR Intelligence -- in the sidebar under Markets.
Knowing which EHR an account runs changes how you sell to it, integrate with it, and support it. This view is built on the HealthIT.gov hospital Promoting Interoperability CHPL linkage, which records the certified health IT each hospital attested to using. It is joined to the ONC CHPL certified-products file (versions, certification dates, certifying bodies, vendor contacts) and to the CMS facilities file by CCN (ownership, county, phone and emergency services).
KPI band
Hover any figure for how it is counted.
| Metric | Meaning |
|---|---|
| Hospitals linked | Distinct facilities in the linkage file, and how many of them name a certified developer |
| EHR vendors | Distinct developers holding at least one hospital as its primary system. Names are normalized across acquisitions and rebrands, so Cerner and Oracle count as Oracle Cerner and Allscripts and Veradigm count as one. |
| Top-3 concentration | Share of hospitals held by the three largest vendors combined |
| Meet PI criteria | Share of facilities flagged as meeting CMS Promoting Interoperability criteria on at least one record |
| Upgrade signals | Hospitals carrying at least one platform-change signal (see Upgrade radar) |
| EHR switches | Facilities whose dominant developer changed between the first and the last reported year, counting only those with at least four certified modules in both years |
A hospital's primary EHR is the developer behind most of its certified modules.
Links under the band open the Facilities directory, the full EHR Linkage table and the Certified Health IT table.
Tabs
Market share
EHR vendor market share, in four views:
- Vendor share -- the vendor leaderboard (hospitals in the first and latest year), concentration of the top 3 against the tail, and the movers between years.
- By state -- the dominant vendor in each state, Locked markets (dominant share 50% or more) and Most fragmented (lowest dominant share). This is where entrenchment shows: a vendor with a modest national share can hold most of one state.
- By hospital type and By ownership -- the vendor mix in each segment.
Each view exports as CSV. Vendor names open the vendor profile.
Hospital finder
Search by hospital name, city, county, state or CCN and filter by State, Vendor and Flags (Any, Flagged only, Clean only). Select a hospital for:
- Identity: CCN, phone, county, hospital type, ownership and emergency services
- Primary EHR -- the certified stack summary, number of certified modules and switch risk
- Certified module stack -- every certified module it attests to, with Export stack as CSV
- Add to list -- adds the hospital to a lead list as a facility, when it matches the facilities file
Export downloads the current result set as CSV.
Upgrade radar
Hospitals with a concrete reason to be talking to a vendor. Each hospital gets a risk score from 0 to 100: the sum of the points for each signal it carries, capped at 100. 30 and above is Moderate, 60 and above is High.
| Signal | Points | Meaning |
|---|---|---|
| Legacy platform | 30 | Runs a MEDITECH generation older than Expanse (MAGIC, Client/Server or 6.x) |
| Old release | 24 | Newest certified Epic listing is release 28.1 or earlier |
| Lapsed attestation | 22 | Did not appear in the most recent reporting year in the file |
| Stale certification | 18 | The newest certified listing it attests on was certified in 2022 or earlier |
| Certification pulled | 16 | Attests on a listing withdrawn by the certifying body, or terminated or suspended by ONC |
| Never met PI | 14 | Never flagged as meeting Promoting Interoperability criteria on any record |
| Losing vendor | 10 | Its incumbent vendor loses more hospitals than it wins across the file |
| Thin stack | 6 | Two or fewer certified modules in its latest reported year |
The first six are the platform-change signals that put a hospital on the radar; Losing vendor and Thin stack add to the score but do not flag a hospital on their own.
Filter by State, Incumbent, Type, Min risk and by signal. The tab shows the risk distribution, Incumbents at risk and Flagged accounts ranked by risk. Export downloads the filtered account list as CSV. The score ranks how much reason there is to expect a platform change, not how likely a hospital is to buy, and it reflects the state of the file rather than a live event feed.
Migrations
EHR migrations: who changed EHR developer between the first and the latest reported year, who entered or left the linkage file, and who still carries the most reason to move.
- Displacement flows -- which vendors lost hospitals to which, and net flow per vendor
- Hospital lists: Core replacements (confirmed switches with at least four certified modules in both years), Thin evidence (a dominant-developer change on a thinner record), Dropped out, New in file, Never linked and Switch risk
- Filter by state and by Vendor (either side)
A hospital mid-migration is an unusually good moment to engage.
Territory
Territory planner: pick your own EHR system, then narrow by state, county, hospital type and displacement tier. What is left is every hospital in scope running something else, ranked by switch risk, with city and phone on the row.
| Tier | Meaning |
|---|---|
| Greenfield | Never met PI criteria -- certified software on paper, never attested in use |
| Displaceable | Met PI, switch risk 50 or more |
| Contested | Met PI, risk under 50, and its incumbent vendor is losing more hospitals than it wins |
| Entrenched | Met PI, risk under 50, incumbent not net-losing |
Headline figures: Hospitals in scope, Your footprint (hospitals already on your system, excluded from targets), Rip targets, Greenfield and Top incumbent. Export downloads the targets with full address and contact detail; hospitals can be added to a lead list from their row.
Ecosystem
Stack ecosystem: which third-party developers ride along with each core EHR. Pick a Core EHR to see Partner attach rate (the share of its hospitals that also list a partner on a separately certified module), top-partner attach across core EHRs, Stack depth (certified modules per hospital), and Category coverage and whitespace -- the separately certified categories each installed base has left open.
Systems
System fingerprints: hospitals reporting the same CEHRT ID attest on an identical certified-technology bundle, which commonly means one IT organization standardized them. The tab lists these shared-stack Bundles with their core vendor, hospital count and states covered.
Vendors
Vendor directory and certification health: every developer that is the primary system at one or more hospitals, joined to its ONC CHPL record -- headquarters, certified listings and published contact details. Sort by Hospitals, Certified listings, Open non-conformities or PI met (lowest first), and select a vendor for its contact record and certification health. Developers that only supply bolt-on modules are not listed here; they appear on the Ecosystem tab and have their own profile pages.
Vendor profiles
Click any vendor name to open its profile. The profile has five tabs:
| Tab | What it shows |
|---|---|
| Footprint | Install base by state, hospital type and ownership, the states where it leads, and what else its hospitals run |
| Hospitals | Named accounts |
| Releases | Platform and release spread: versions in the field and hospitals per version |
| Movement | Hospitals won and lost and the net, year over year |
| Certification | The developer and certification record, certification health, and the certified products its hospitals run |
A module developer (one that only supplies bolt-on modules) gets a simpler profile: hospitals listing it, share of all linked hospitals, states and certified products.
Important: the data model
This is the single most misread dataset in Qope. Read this before quoting a number from it.
- One row is a facility plus module, not a facility plus EHR. A hospital attesting to several certified modules produces several rows, per reporting year. Qope deduplicates by facility for every count on this page, but the EHR Linkage table does not.
- The Meets PI Criteria values are
YandN, notYES. Filtering the raw table forYESreturns nothing. - Bed-weighted analysis is not supported. The linkage file and the facilities file carry no usable hospital bed counts, so vendor share is by hospital count, not by beds or patient volume.
Coverage note
The footnote under the tabs names the sources: how many linkage records and reporting years, how many CHPL listings, and how many hospitals matched the facilities file. If it says Partial sample, not every linkage row loaded, so treat state-level shares as indicative rather than exact.
Related tables
- EHR Linkage -- the raw hospital-to-EHR rows.
- Certified Health IT -- the CHPL product certifications themselves.
- Facilities -- the facility directory these link to.
Opening the page uses one credit. See Usage and Limits.