Selling software to a US hospital system runs in seven stages. It starts with discovery with a clinical or operations leader and ends with launch at one site. A business associate agreement (BAA) must be signed before a pilot touches patient data.
Who owns the deal?
A chief medical information officer (CMIO), chief nursing officer (CNO) or service line vice president usually champions the deal. A CFO, COO or system executive holds the budget.
Check early where the decision sits. Of 5,121 US community hospitals, 3,567 belong to a system (AHA, 2024 survey data, updated February 2026). A site champion often cannot sign.
What are the seven stages?
The stages follow the enterprise B2B sales cycle. Each stage ends at one exit point.
- Discovery. The champion confirms the workflow problem and today's numbers, and names the economic buyer.
- Technical scoping. EHR analysts, integration and privacy agree the pilot plan. Sign the BAA if the pilot touches patient data.
- Pilot in one unit. The champion and unit leader sign results against metrics agreed before the start.
- MOU or LOI. The economic buyer signs the scope, success criteria, timeline, signers and committee dates.
Then come the hospital's own reviews:
- Commercials. The value analysis committee approves, and supply chain and finance agree terms.
- Legal, security and AI governance. Legal, the CISO, privacy and the AI committee clear the final BAA. Both sides sign.
- Launch and expansion. One site goes live. A review names the next site.
Stage 3 differs most from selling an AI agent product. A vendor may handle protected health information (PHI) only with written assurances (45 CFR 164.502(e)).
So start the BAA and the first security review in stage 2.
What starts a software project at a hospital system now?
An EHR upgrade, a contract renewal, a staffing cost line or a new governance duty starts it. Value analysis reviews often follow contract renewals (HealthTrust, 2024). Ask for the renewal date of the tool you would replace.
Four external changes matter on 8 November 2026:
- The HTI-5 final rule removes model card requirements from health IT certification (Holland & Knight, October 2026). Expect hospitals to ask you for training data, validation and limits.
- The Joint Commission and the Coalition for Health AI issued guidance on 17 September 2025. The guidance is not binding. It asks hospitals to get validation evidence and agree who monitors the tool (National Law Review, October 2025).
- Covered entities must try to find decision tools that use race, sex or age (45 CFR 92.210). They must reduce the risk of discrimination. The duty applied from about 1 May 2025, by our count (45 CFR 92.1).
- HHS moved the HIPAA Security Rule overhaul from May 2026 to July 2027 (Paubox; Coalfire). Sell to the rule in force today.
Use MEDDPICC to find the champion's number, such as documentation minutes per shift, denial rate or length of stay.
What should the pilot prove?
The pilot proves that clinicians use the tool and that one named number moves. Run predictive tools in silent mode first, with output going only to evaluators.
- Adoption: the share of eligible clinicians who use the tool each week.
- Time: minutes per encounter or shift, against a baseline from before the pilot.
- Safety and override: reported events, and how often clinicians reject the output.
- Performance by patient group: accuracy across the groups in section 92.210.
What goes into the MOU?
Name the unit, thresholds, timeline, signers and committee dates. HealthTrust advises that less than 10% of a value analysis agenda should go to new products (HealthTrust, 2024). Ask the champion to request a slot when the MOU is signed.
How do hospital systems price and approve software?
Vendors price per bed, provider or encounter, or as a site subscription, with a system-wide rate on expansion. The committee checks that the product works at least as well as current options (HealthTrust, 2024). It judges total value along with unit price.
Bring the pilot result as dollars of labour or denials saved. Ask if the money is capital or operating, because each follows its own approval calendar.
What do legal, security and AI governance check?
- The BAA. It sets permitted uses, safeguards, breach reporting and subcontractor duties (45 CFR 164.504(e)). It also requires return or destruction of data at the end. List each model and cloud subprocessor that touches PHI.
- FDA status. Software stays outside device rules only if it meets four criteria (FDA, January 2026). It avoids analysing a medical image or signal, displays medical information, supports a professional, and lets that professional check the basis.
- Time-critical tools may fail that last test (Covington, January 2026). Write a one-page position with counsel before stage 2.
- Data use. Agreements should define permitted uses, ban re-identification and let the hospital audit you (National Law Review, October 2025). State in writing if customer data trains your models.
- NHS buyers. England uses the Digital Technology Assessment Criteria. NHS England set 6 April 2026 to move to the updated form (NHS Innovation Service, March 2026).
What does launch at one site look like?
Train super-users before go-live. Review the first full month against the MOU thresholds. A second site can need its own EHR build, so scope it before you quote a date.
To reach the clinical and operations leaders with a dated reason to change a workflow, get five named buyers, free.