Selling to health systems and payers
Your forecast sits in security review and next year’s budget.
You sell software or services to health systems, physician groups and payers, and you could name every account. A clinician loves the demo, then the CISO, finance or legal reopens it. Payback and the budget line are checked after the demo, so the verbal yes waits for the next fiscal year.
- US health systems
- 639
- NHS trusts in England
- 207
- US health insurer entities
- 1,156
Updated 5 October 2026 · Based on Panelhop research, October 2026
The short answer
How do software vendors sell to health systems and payers?
Software vendors sell to healthcare providers and payers through committee sales: by Panelhop’s estimate, a significant health system purchase involves 5–12 people, several with a veto, and runs 6–24 months. Buyers can be listed: 639 US health systems, 1,554 independent US hospitals, 207 English NHS trusts and 1,807 German hospitals. Winning vendors act on dated triggers and engage every approver.
Healthcare · How a deal really moves
Your champion said yes. The committee hasn’t. Security, the EHR roadmap and the budget line still decide. The same deal, with every veto seat named. Security before terms, and close dates on the buyer’s calendar.
One health system, 5–12 people (several with a veto) and an estimated 6–24 months from first signal to signature.
What opens a deal
- CMS-0057-F, 1 January 2027: Regulation · US
- Hospital merger or acquisition: Consolidation · US
- EHR, EPR or KIS replacement: Technology
- New CIO, CFO or CEO: Leadership
- Ransomware or outage at a peer: Security
- Budget planning opens: Budget · US, UK
Signal Desk · weekly: In-market accounts, scored and mapped
Your buyer and who decides
A health system
IDN, NHS trust, German hospital or payer
639 US health systems · 207 NHS trusts
Panel Check · coverage baselined
- CEO or COO, can Veto: A failed go-live or a breach with the system’s name on it.
- CFO and finance, can Veto: Unbudgeted spend on thin margins, and surprise fees.
- CIO and EHR or EPR team, can Veto: Another integration for a team that is already backlogged.
- CMIO or CNIO, can Veto: Decisions made without clinical input.
- Operational champion: Extra rollout work, and lost credibility if it fails.
- CISO and vendor risk, can Veto: A breach or outage that starts at a vendor.
- Privacy and legal, can Veto: Non-standard BAA terms that set a precedent.
- AI governance committee, can Veto: AI claims that nobody can verify.
How the deal moves
Targeting
Demand generation
First meeting
Discovery
- Where it stalls
- Great demo with one clinician, then silence
- With Panelhop: Leak Fix
- A role map names finance, IT, security, legal and AI seats on every deal
Evaluation Typical time: 1–2 months
- Where it stalls
- ‘Our EHR vendor is building this’
- With Panelhop: Leak Fix
- No evaluation closes without payback against the EHR’s own module
First phase Typical time: 2–6 months
- Where it stalls
- An unscoped first phase with no end date
- With Panelhop: Leak Fix
- A first phase enters the forecast only with an owner, threshold and date
Security and procurement Typical time: 1–4 months
- Where it stalls
- This quarter’s deals sit in security review
- With Panelhop: Leak Fix
- Security, privacy and legal on the deal, trust pack asked before terms
Approval and contract Typical time: 2–10 months
- Where it stalls
- ‘We’ll put it in next year’s budget’
- With Panelhop: Leak Fix
- Each account’s fiscal year end and board dates become deal fields
Go-live
Renewal and expansion Typical time: 9–18 mo out
Panel Ops · monthly: Scores and plays tuned against the baseline
Illustrative Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; Agency for Healthcare Research and Quality; Bennett Institute for Applied Data Science, University of Oxford; Centers for Medicare & Medicaid Services; the services as described on the Services page. Note: Durations, panel sizes and cycle lengths are Panelhop estimates from our research, not measurements.
At a glance
| Typical deal | €33–445k a year for patient access and revenue cycle platforms at US hospitals Illustrative |
|---|---|
| Sales cycle | 6–24 months at large US health systems, payers and DACH public hospitals Illustrative |
| Buying panel | 5–12 people, with several seats that can veto Illustrative |
| How deals start | A dated trigger or budget window, then a peer referral or a demo request (a demo or contact form is the main call to action at 19 of 20 healthcare vendors we analysed) |
| Main triggers | EHR and EPR go-lives, mergers, new CIOs and CFOs, CMS-0057-F, NHS business-case season and KIS replacement in DACH |
| Segments | Health systems and hospitals, academic medical centres, physician groups, payers, integrated care boards (ICBs) in England, post-acute and behavioural health |
Source: Panelhop research, October 2026. Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.
Your deals leak long before the account list runs out.
Where do vendors lose health system software deals?
Vendors lose health system software deals when public triggers reach reps late and one clinical champion sells alone. Marketing counts contacts while sales forecasts accounts. Security review starts after the verbal yes, the budget line is checked after the demo and the first live site rarely spreads across the system.
Where the pipeline leaks: 6 points across 10 stages.
Your reps hear about the go-live after the shortlist
- What you see
- Reps hear about an EHR go-live or a merger after adjacent vendors are chosen, and tenders arrive with requirements already written.
- Why it happens
- Triggers sit in board papers, tender portals, CMS files and trade press, and nobody owns them. No vendor stack we analysed shows a healthcare-specific trigger source.
Stage Targeting
Form-fill targets are met and pipeline stays flat
- What you see
- Form-fill targets are met while new health system opportunities stay flat, and the same systems hear from you through the wrong people.
- Why it happens
- Marketing automation or CRM tags show at 16 of 20 healthcare vendors we analysed and gated content at 14 of 20. Both are built around individual contacts, in a market of named accounts.
Stage Demand generation
A great demo with a clinician ends in silence
- What you see
- A strong demo with a physician or nurse leader is followed by silence, then IT security or finance reopens the evaluation.
- Why it happens
- Deals are often single-threaded through the champion, and only 2 of 20 healthcare vendors we analysed publish content for more than one buying-group role.
Stage Discovery
This quarter’s deals sit in security review
- What you see
- Deals forecast for the quarter sit ‘in security review’, and each new customer repeats the same review from scratch.
- Why it happens
- The CISO, privacy and legal are not mapped at discovery, and no vendor we analysed offers a downloadable trust pack. Our analysis flags security review as a likely stall for 16 of 20 vendors.
Stage Security and procurement
A verbal yes slips to next year’s budget
- What you see
- A verbal yes turns into ‘we’ll put it in next year’s budget’, and forecast slips cluster at buyers’ fiscal year ends.
- Why it happens
- Pricing is hidden at 18 of 20 healthcare vendors we analysed, so payback and the budget line are qualified late, and reps rarely know each account’s fiscal year.
Stage Approval and contract
One hospital is live. The other sites restart procurement.
- What you see
- Many customers have one hospital or department live inside a much larger parent system, and expansion restarts procurement.
- Why it happens
- Nobody keeps a whitespace map by hospital, service line and module. Our analysis flags a first site or department that stalls before system-wide rollout as a likely problem for 8 of 20 healthcare vendors.
Stage Renewal and expansion
Dated, public events open and freeze healthcare budgets.
What triggers a health system or payer to buy new software?
Health systems and payers buy new software after compliance deadlines, mergers, core-system replacements, cyber incidents, new executives, budget windows and funding rounds. Most are public and dated. The gap is a field in your CRM and an owner who acts on it.
The 8 events that open or close the window for a deal.
Regulation
CMS-0057-F payer API deadline
- What happens
- Medicare Advantage, Medicaid, CHIP and federal exchange plans must meet CMS-0057-F’s API requirements, primarily by 1 January 2027.
- Where to spot it
- The CMS rule page, plan association vendor showcases and payer developer portals.
- Window
- By our estimate, Q4 2026 is the late-buyer window: plans still behind favour vendors with live, compliant connectivity and short go-lives.
Consolidation
Hospital merger or acquisition
- What happens
- US hospitals and health systems announced 18 mergers and acquisitions in Q2 2026, and acquirers usually move their targets onto their own EHR and contracts, often on a timeline written into the deal.
- Where to spot it
- Quarterly M&A reports, state regulator filings and press releases.
- Window
- IT decisions start at or before close; by our estimate, EHR conversion follows 6–18 months after close.
Technology
EHR, EPR or KIS replacement
- What happens
- A provider signs for or goes live on a new core record system, and every adjacent product is reassessed around it.
- Where to spot it
- Find a Tender award notices, trust board papers, KLAS market share reports and German tender portals.
- Window
- By our estimate, adjacent tools are decided 12–24 months before go-live.
Technology
KIS tender wave in Germany
- What happens
- In a 2025 survey of German hospital leaders, the largest group, 46%, expects the main KIS tender wave in 2027, as many hospitals face a forced change of core system.
- Where to spot it
- TED and German tender portals and the hospital IT trade press.
- Window
- By our estimate, tender and selection take about 12 months before a multi-year implementation, so adjacent vendors engage before tenders are written.
Security
Ransomware or outage at a peer
- What happens
- Ransomware or an IT failure takes down EHRs, portals or phones at the organisation or a nearby peer, and the board funds resilience.
- Where to spot it
- The HHS breach portal, incident update pages and local news.
- Window
- Immediate for incident response; by our estimate, 3–12 months for resilience programmes.
Leadership
New CIO, CFO or CEO
- What happens
- A new executive inventories the inherited vendors, contracts and renewal dates, and resets IT governance.
- Where to spot it
- Executive-move news and job changes at target accounts.
- Window
- By our estimate, months 3–12 after arrival, when incumbents lose their protection.
Budget cycle
Budget planning windows
- What happens
- US academic medical centres start department budget planning in Q3 of the prior fiscal year, Medicare Advantage bids are due on the first Monday in June and NHS business cases run September to December.
- Where to spot it
- Each account’s financial statements and board calendars, the Medicare Advantage bid rules and NHS planning guidance.
- Window
- Engage before planning opens; a deal that misses the window needs off-cycle approval or waits for the next fiscal year.
Funding
Rural Health Transformation Program awards
- What happens
- US states distribute $50bn over 5 years to rural providers, with health IT among the eligible uses.
- Where to spot it
- The NRHA state-by-state tracker and state health department pages.
- Window
- Award to purchase takes 3–9 months by our estimate, inside federal fiscal-year budget periods.
Many seats can stop a health system deal.
Who signs off on a software purchase at a health system?
Finance signs off on health system software purchases, with the CFO approving larger contracts and the board approving the largest or public ones. A clinical or operational champion starts the deal, and IT, security, legal and the AI governance committee can each stop it. In a HIMSS Media survey of 211 respondents, 95% said their organisation involves IT in technology purchasing, and 73% said it involves finance.
At a US health system, 5–12 people sit on the panel and most seats can stop the deal.
At a US health system, with NHS and German equivalents: 5–12 people
Finance
Can Veto
CFO · VP Revenue Cycle · Kaufmännische Direktion (DE)
- Cares about
- Hard-dollar payback inside the fiscal year and one total-cost number.
- Worries about
- Unbudgeted spend on thin margins, and surprise fees.
Executive sponsor
Can Veto
CEO · COO · Chief Strategy Officer
- Cares about
- Fit with this year’s system priorities, proven at peer systems of similar size.
- Worries about
- A failed go-live or a breach with the system’s name on it.
IT leadership
Can Veto
CIO · Chief Digital Officer · EHR Applications Director
- Cares about
- Fewer vendors and a realistic integration with the incumbent EHR.
- Worries about
- Another integration for a team that is already backlogged.
Clinical informatics
Can Veto
CMIO · CNIO · CCIO (NHS)
- Cares about
- Less documentation burden and fewer clicks at the bedside.
- Worries about
- Decisions made without clinical input.
Operational champion
Director of Patient Access · Director of HIM or Coding · Service Line Director
- Cares about
- A fix for a concrete pain: denials, access, throughput or staffing.
- Worries about
- Extra workload during rollout, and losing credibility if it fails.
Security and third-party risk
Can Veto
CISO · Third-Party Risk Manager · SIRO (NHS)
- Cares about
- SOC 2 Type II or HITRUST evidence, a recent pen test and a subprocessor list.
- Worries about
- A breach or outage that starts at a vendor.
Privacy, compliance and legal
Can Veto
Chief Compliance Officer · General Counsel · Caldicott Guardian (NHS)
- Cares about
- A BAA with subcontractor flow-down and clear terms on AI data use.
- Worries about
- Non-standard terms that set a precedent.
AI governance committee
Can Veto
AI Governance Committee Chair
- Cares about
- Validation evidence, model monitoring and how patient data is used.
- Worries about
- AI claims that nobody can verify.
Every enterprise healthcare buyer can be listed by name.
Who buys software in healthcare?
Software vendors in healthcare sell to health systems, hospitals, physician groups, payers and integrated care boards, and the enterprise core of each segment can be listed from public registers. The decision usually sits with the parent system, trust or insurer, so tier the parent rather than each site.
The enterprise core is a list: 639 US health systems and 1,554 independent hospitals, 207 NHS trusts and 1,807 German hospitals.
Health systems, NHS trusts and hospital operators
Multi-hospital health systems and IDNs, NHS trusts and German hospital operators (Träger), the largest IT budget pool. Of 5,121 US community hospitals, 3,567 belong to a system, where the parent usually decides, and 1,554 buy on their own.
- US639 systems and 1,554 independent hospitals
- UK207 NHS trusts in England
- DACH1,807 hospitals in Germany
Academic medical centres and university hospitals
Teaching hospitals and academic health systems with the most complex IT estates and separate IT, informatics and capital committees. Legal is the usual bottleneck, and one win becomes a reference for the wider market.
- USmore than 400
- DACH37 VUD members in Germany
Physician groups and ambulatory providers
Medical groups, management services organisations (MSOs) buying for private-equity-backed practices, GP practices in England and medical care centres (MVZ) in Germany. Just over 42% of US physicians worked in private practice in 2024, so purchasing is moving to systems and MSO head offices.
- UK6,143 GP practices in England
Payers and health plans
Commercial, Medicare Advantage and Medicaid managed care plans in the US, and statutory and private insurers in DACH. The 1,156 US insurer entities roll up to far fewer parent groups, which buy against plan years, Medicare Advantage bids and CMS-0057-F and usually prefer best-of-breed tools to suites.
- US1,156 insurer entities
- DACH93 statutory funds in Germany
Integrated care boards in England
The NHS bodies that plan and pay for care for a population and buy shared care records, population health analytics and care management. ICBs merge again on 1 April 2027 and a Health Bill before Parliament would fold NHS England into the Department of Health and Social Care, so decisions slow, then concentrate in fewer, larger boards.
- UK36 ICBs from 1 April 2026
Post-acute, behavioural health and care homes
Skilled nursing, home health, hospice, behavioural health and care home operators: many small, owner-run buyers where cost decides first. Full account-based work rarely pays here, except at chain head offices that buy for many sites.
No sourced count
Data behind this chart
| Segment | Region | Accounts |
|---|---|---|
| Health systems, NHS trusts and hospital operators | US | 639 systems and 1,554 independent hospitals |
| Health systems, NHS trusts and hospital operators | UK | 207 NHS trusts in England |
| Health systems, NHS trusts and hospital operators | DACH | 1,807 hospitals in Germany |
| Academic medical centres and university hospitals | US | more than 400 |
| Academic medical centres and university hospitals | DACH | 37 VUD members in Germany |
| Physician groups and ambulatory providers | UK | 6,143 GP practices in England |
| Payers and health plans | US | 1,156 insurer entities |
| Payers and health plans | DACH | 93 statutory funds in Germany |
| Integrated care boards in England | UK | 36 ICBs from 1 April 2026 |
| Post-acute, behavioural health and care homes | – | No sourced count |
Buyers ask about payback, integration and risk first.
What do health system and payer buyers ask vendors during a deal?
Health system and payer buyers ask about payback, integration capacity and security before they ask about features. These questions come from our research into how providers and payers buy, in their words.
CFO or VP Finance
What is the payback in our numbers, inside this fiscal year?
Is this in this year’s budget, or does it displace something already there?
What is the one total cost, implementation included?
CIO or CMIO
Our EHR vendor is building this. Why shouldn’t we wait?
IT has no capacity for another integration. Who runs it on your side?
Which systems of our size and EHR can we call?
CISO or compliance
Do you have SOC 2 Type II or HITRUST, a recent pen test and a BAA?
Where is patient data hosted, and is it used to train your AI?
Can we see model documentation and validation results for the AI features?
NHS or DACH procurement
Is it on G-Cloud or another framework, and is DTAC done?
Do you hold a C5 Type 2 attestation and host in the EU?
Deals stall after the champion is convinced.
What are the stages of a health system software deal?
A health system software deal moves from budget planning through a peer-led shortlist, demos, an optional first phase, security review and approval to go-live and renewal. By our estimate, physician practices decide in 1–9 months and academic medical centres take about 18 months. The durations show the buyer’s side.
Stage by stage: what you do, what the health system does, and what changes at the 5 stages where deals stall.
| Stage | What you do | What the health system does | Today | With Panelhop |
|---|---|---|---|---|
| Targeting Typical time: 1–6 months to reach an approved budget | Works inbound demo requests, with no visible tiers by parent system, EHR or payer mix. | A sponsor frames the problem and tries to get it into next year’s capital or operating budget. | Inbound demo requests with no account tiers. | A Panel Check tests whether your motion fits your deal size and drafts account tiers from your closed-won and closed-lost data. Tiers use parent system, EHR, ownership and payer mix where your data holds them. Panel Check GTM audit · 2–3 weeks |
| Demand generation Typical time: 1–3 months to a shortlist | Runs gated content, webinars and nurture built around individual contacts. | Builds a long list from peers, KLAS data, conferences and advisers, then a shortlist. | Nurture waits for an individual to download something. | Each week, accounts with a live trigger (an EHR go-live, a merger, a new CIO) arrive in your CRM, scored, with the signal that fired. Signal Desk In-market accounts, weekly |
| First meeting | Sends cold sequences or follows up whoever stopped at the conference booth. | Takes meetings through peer referrals, matched references and associations such as CHIME and HFMA. | Cold sequences to executives who rarely reply. | Each account brief names the trigger, the buying-group seats to approach and a recommended play. Your rep writes and owns the first touch. Signal Desk In-market accounts, weekly |
| Discovery | Scopes the problem with one clinical or operational champion. | A buying group forms around the champion as IT and finance join, and the funding route is checked. | One champion, usually clinical or operational. Stalls: One clinical champion. An enthusiastic clinician or department head cannot carry the deal through security review, the budget line or legal, so it stalls after a strong demo. | A role map per tier tracks finance, IT, security, legal and AI governance contacts on every account, and coverage is reported per open deal. Leak Fix We build the fixes |
| Evaluation Typical time: 1–2 months, plus 1–3 months of AI governance review where it applies | Runs scripted demos and lines up reference calls. | Scores demos, asks for a payback model and calls peers of matching size, specialty and EHR. | Value is argued in the vendor’s numbers, and AI review starts late. Stalls: ‘Our EHR vendor is building this’. About 6 in 10 providers take an EHR-first approach, so the incumbent EHR’s own module or roadmap can end an outside evaluation. | Stage exit criteria require a payback model in the buyer’s numbers, set against the EHR’s own module. A named finance contact and, for AI products, the AI governance contact are needed before an evaluation can close. Leak Fix We build the fixes |
| First phase Typical time: 2–6 months | Agrees an unscoped first phase, sometimes unpaid, to get started. | An innovation team runs it under a BAA, often without an operational budget owner. | Open-ended trials counted as pipeline. Stalls: A first phase with no owner or end date. Without a budget owner, a success threshold and a decision date, a successful first phase never becomes an enterprise contract. | A budget owner, a success threshold and a decision date become stage exit criteria, and first phases without them sit outside the forecast. Leak Fix We build the fixes |
| Security and procurement Typical time: 1–4 months, or a few weeks with the evidence ready | Answers a long security questionnaire after the verbal yes. | Security, privacy and legal review SOC 2 or HITRUST evidence and the BAA, plus DTAC and DSPT in the NHS or C5 Type 2 in Germany. | The security questionnaire arrives after the price is agreed. Stalls: Security review after the verbal yes. Every health system runs its own third-party risk review, so deals forecast for this quarter sit in the security queue. | Stage exit criteria require security, privacy and legal contacts on the opportunity and the trust pack request before terms are discussed. Leak Fix We build the fixes |
| Approval and contract Typical time: 1–7 months for approval, then 1–3 months to sign | Negotiates the BAA and master terms, then waits for signature. | Finance approves; large or public contracts go to the board, NHS England or a supervisory board. | Close dates ignore fiscal years and board meetings. Stalls: Not in this year’s budget. Hospitals set operating and capital budgets before the fiscal year starts, so a larger purchase that missed the plan needs slower off-cycle approval or waits for the next fiscal year. | Forecast tracking carries each account’s fiscal year end and board dates as deal fields, so close dates follow the buyer’s calendar. Leak Fix We build the fixes |
| Go-live | Waits for the customer’s EHR or EPR team to enable the integration. | Fits the interface build into an IT queue that is often months long. | What sales promised about integration lives in one rep’s notes. | A handoff document, built from the deal, records the integration scope, the customer’s EHR or EPR team owner and the agreed go-live date. Leak Fix We build the fixes |
| Renewal and expansion Typical time: Engage 9–18 months before expiry | Renews one site or department and waits for the system to roll it out. | Rationalises applications, re-tenders at term end or moves acquired hospitals onto the parent’s contracts. | Renewals depend on whoever remembers the term date. | Panel Ops checks every week that renewal and expansion tasks have run, re-scores accounts each quarter and reports account progression against the baseline every month. Panel Ops We run it monthly |
Every health system deal stage gets a baseline.
How does Panelhop change the way a health system deal moves?
Panelhop changes how a health system deal moves by putting every stage on a baseline, then working the stages that leak. A Panel Check (GTM audit) sets the baseline from your own CRM data. Signal Desk (in-market accounts, weekly), Leak Fix (we build the fixes) and Panel Ops (we run it monthly) then do the work.
What we baseline and report
- Buying-group coverage: open health system deals with a named contact in every seat that can veto, against the baseline
- Days each deal spends in security, BAA and AI governance review, against the baseline
- Share of forecast slips that land at a buyer’s fiscal year end, against the baseline
Read the pipeline for your vendor type.
Which vendor types sell to health systems and payers?
These are the vendor types we map in healthcare, each with its own buying panel, pipeline and triggers.
- Vendor type
Patient access and front-office automation
Scheduling, intake, eligibility, financial clearance and AI call handling for health systems, hospitals and physician groups.
Read the pipeline - Vendor type
Revenue integrity, coding and claims software
AI coding, claim scrubbing, charge capture, risk adjustment coding and denial prevention for providers and billing companies.
Read the pipeline - Vendor type
Health system operations and care delivery platforms
Capacity, patient flow, asset tracking, care coordination, pharmacy and workforce platforms for large health systems.
Read the pipeline - Vendor type
Interoperability and integration infrastructure
Integration engines, FHIR APIs and data exchange for NHS trusts, German hospitals, US payers and health information exchanges.
Read the pipeline
The words your buyers use, defined.
What do terms like “Health system and IDN” and “EHR-first” mean in healthcare?
Plain definitions of the terms that come up when you sell to health systems and payers.
- Health system and IDN
- A parent organisation that owns or manages hospitals and physician groups; an integrated delivery network (IDN) adds ambulatory and post-acute care. Buying decisions usually sit with the parent, not the site.
- EHR-first
- A buying rule where a provider uses its EHR vendor’s own module whenever it is good enough, and asks an outside vendor for a clearly higher return.
- Revenue cycle management (RCM)
- Everything between scheduling a patient and collecting payment: patient access, coding, claims, denials and collections. A VP revenue cycle usually holds its budget.
- Trust pack
- The security evidence a vendor sends before it is asked: a SOC 2 Type II or HITRUST report, a recent pen-test summary, a subprocessor list and its BAA position.
- BAA
- A business associate agreement under HIPAA. A US provider signs one with every vendor that handles patient data, and hospital counsel often insist on their own template.
- AI governance committee
- A cross-functional group, usually including the CIO and often the CMIO, legal and risk, that reviews validation, monitoring and data use before an AI tool goes live at a health system.
- DTAC and DSPT
- The NHS baseline assurance for digital suppliers. The Digital Technology Assessment Criteria (DTAC) cover clinical safety, data protection, security, interoperability and usability; the Data Security and Protection Toolkit (DSPT) is an annual self-assessment.
- KIS
- Krankenhausinformationssystem: the core hospital information system in Germany, Austria and Switzerland. KIS choices at public hospitals go through formal tenders and shape every adjacent purchase.
- Business-case season
- September to December, when NHS trusts write business cases to commit this financial year’s capital, which is lost if not committed by the year end. Contracts are then signed from January to March.
- CMS-0057-F
- The US Interoperability and Prior Authorization Final Rule. It requires Medicare Advantage, Medicaid, CHIP and federal exchange plans to run FHIR APIs, primarily by 1 January 2027.
Answers before your next health system deal.
What do vendors ask about selling to health systems and payers?
How long does it take to sell software to a hospital or health system?
Selling clinical or EHR-integrated software to a large US health system takes an estimated 6–24 months, typically about 12 months, and scope sets the pace. By our estimate, non-clinical tools without EHR integration close in 4–6 months, academic medical centres take about 18 months and physician practices 1–9 months. Payers and DACH public hospitals also take an estimated 6–24 months, and NHS trusts 3–24 months.
Who is on the buying committee when a health system buys software?
A health system’s buying committee usually has 5–12 people, by our estimate. A clinical or operational champion starts the deal and finance signs it off, while IT, information security, privacy and legal, the AI governance committee and the board can each stop it. In a HIMSS Media survey of 211 respondents, 95% said their organisation involves IT in technology purchasing, 76% executive leadership and 73% finance.
How do you get a meeting with a hospital CIO or CFO?
A matched reference is the most reliable route to a health system CIO or CFO: a peer system of similar size and EHR that already uses your product. Associations such as CHIME and HFMA, KLAS visibility and advisers also open doors. Time the approach to a dated trigger, such as a merger, an EHR go-live or a new executive, because health system executives rarely answer cold email.
How long does a hospital security review take for a software vendor?
A health system security review takes an estimated 1–4 months, or a few weeks with the evidence ready, and vendors often start it after the verbal yes. The review asks for SOC 2 Type II or HITRUST evidence, a recent pen test, a subprocessor list and a BAA. NHS trusts add DTAC and DSPT, and German buyers need C5 Type 2 for cloud services. Bringing the CISO, privacy and legal in at discovery shortens the wait.
How do you turn a hospital pilot into a paid contract?
A hospital pilot becomes a paid contract when it runs as a phased first scope with success criteria. That means an operational budget owner, a success threshold in the hospital’s own metrics and a date that forces a decision. Trials run by innovation teams without those terms often succeed and still never convert. Many health systems now prefer this paid, phased route to an open-ended trial.
How do software vendors sell to US health plans?
Software vendors sell to US health plans through a matrixed buying group with several champions. A business owner such as the VP of care management, utilisation management or quality usually starts the deal, and compliance, actuarial, IT security, legal and the medical management committee then review it. Health plans usually buy best-of-breed tools, time go-lives to the plan year and take an estimated 6–24 months to decide.
When do hospitals and NHS trusts set their IT budgets?
Hospitals set IT budgets before their fiscal year starts, so larger purchases must be in the plan. US academic medical centres start department budget planning in Q3 of the prior fiscal year. NHS trusts write business cases from September to December and sign from January to March, because capital not committed by year end is lost. German hospitals fix budgets for the calendar year, with investment money from the federal states (Länder) and the Transformationsfonds, and Hospital Future Act (KHZG) penalty deadlines set the timing of digital projects.
Does intent data work for selling to health systems?
Generic intent data works poorly on its own for vendors selling to health systems. It misses the triggers that open healthcare buying windows: EHR go-lives, mergers, new CIOs and CFOs, CMS-0057-F deadlines, KIS tenders and NHS award notices. Track those as dated fields on each account, with an owner who acts that week. In Panelhop’s analysis of healthcare vendor websites, 3 of 20 run an account-identification or intent tool, and none of those vendors shows sales development or account-based marketing hiring to act on it.
Where the numbers come from.
Sources
Sourced figures link to their source below. Figures marked Illustrative, and figures given as estimates, are inferred from Panelhop research. Vendors appear only as types, never by name.
- Agency for Healthcare Research and Quality, Compendium of U.S. Health Systems, 2023 (2024)
- American Hospital Association, Fast Facts on U.S. Hospitals, 2026 (2026)
- NAIC, U.S. Health Insurance Industry Analysis Report, 2025 Annual Results (2026)
- Bennett Institute for Applied Data Science, University of Oxford, Understanding NHS trust types (2026)
- Healthcare Leader, Changes to English ICB footprints go live (2026)
- NHS England, Implementing integrated care board mergers and boundary changes to take effect in April 2026 and 2027 (2025)
- Statistisches Bundesamt (Destatis), Krankenhäuser 2025 nach Trägern und Bundesländern (2026)
- GKV-Spitzenverband, Die gesetzlichen Krankenkassen (2026)
- Association of American Medical Colleges, Medical School Enrollment Reaches 100,000 Students for the First Time (2025)
- Deutscher Bundestag, Lobbyregister, Registereintrag Verband der Universitätsklinika Deutschlands (VUD) (2025)
- Healthcare Dive, Share of physicians working in private practice continues to fall: AMA (2025)
- British Medical Association, Pressures in general practice data analysis (2026)
- HIMSS Media, HIT Buyer’s Survey (January 2025) (2025)
- Bain & Company with KLAS Research, Healthcare IT Investment: AI Moves from Pilot to Production (2025)
- Centers for Medicare & Medicaid Services, CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) (2024)
- Healthcare Dive, Hospital M&A sustains momentum in Q2: report (2026)
- Roland Berger, Krankenhaus IT-Monitor 2025 (2025)
- American Hospital Association, CMS announces state distribution of $50 billion in rural health funds (2025)
- Bundesministerium der Justiz, Gesetze im Internet, § 393 SGB V: Cloud-Einsatz im Gesundheitswesen (2025)
- Legal Information Institute, Cornell Law School (US Code of Federal Regulations), 42 CFR § 422.254: Submission of bids (2026)
- Plastic and Reconstructive Surgery Global Open (PubMed Central), Budgets: How They Are Planned, Prepared, and Managed (2024)
- Nuffield Trust, What’s in the new Health Bill? (2026)
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers in healthcare, from public sources. Vendor names are not published.
Find where your pipeline to health systems and payers leaks.
