The surgeon loved the demo. The nurse manager wants to trial it next week. For a medical device rep, that is the best moment in the cycle — and often the moment a deal starts to go quiet. For months afterwards, the clinical side stays supportive, and nobody can tell you where the purchase actually stands.
Clinical preference starts the process. It does not finish it. The units that finish it usually never meet the rep.
This guide lays out the full path a medical device takes from clinical interest to a signed purchase order: what each unit needs, what evidence satisfies it, where it typically stalls, and how much a rep can realistically influence it.
One caveat before the detail. Every hospital is different. Academic medical centers, integrated delivery networks (IDNs) and community hospitals run the process with different levels of formality, and public and private systems follow different rules. The path below reflects the common structure in US hospitals; the section on other systems explains how it changes elsewhere.
Before the Hospital: Two Conditions Set Elsewhere
Two things are decided before any hospital unit looks at your product, and both shape how every unit will judge it.
Market authorization. The device must be cleared or approved for the intended use in that market. No committee will evaluate a product that cannot legally be used for the procedure in question.
How the hospital gets paid. Whether the procedure is reimbursed, and how, changes the financial case entirely. A device that adds cost to a bundled payment is judged very differently from one that enables a separately reimbursed service. Reps who cannot explain the payment picture leave finance to guess.
The Full Path, Node by Node
The table below maps the decision units a typical capital or new-product purchase passes through. Not every deal touches every node, and the order varies by hospital. But most long-cycle device deals meet most of them.
| Node | What it needs | Evidence that satisfies it | Typical sticking point | Rep’s realistic influence |
|---|---|---|---|---|
| Clinical champion (physician, nurse leader) | A clear benefit to patients or workflow | Demo, clinical literature, peer experience | Supportive but no time to drive internal process | High |
| Department or service-line head | A reason to spend the department’s requests and budget on this | Clinical need statement, comparison to current product | This year’s requests already submitted | Medium to high |
| Clinical evaluation or trial | Real-world use inside the hospital | Trial protocol, usage data, staff feedback | Trial ends; nobody writes up the results | Medium |
| Value analysis committee | Justification against cost, outcomes and existing alternatives | Outcome evidence, total cost comparison, contract impact | Deferred to the next meeting cycle | Low to medium |
| Clinical engineering (biomed / HTM) | Safety, serviceability, lifecycle cost | Service plan, parts availability, training commitment | Service terms or parts support not agreed | Medium |
| IT and security (if connected) | Integration and acceptable security risk | Interface specs, MDS2 security disclosure | Not in IT’s project queue | Medium |
| Supply chain / procurement | A compliant purchase path | GPO contract status, pricing, vendor documentation | Product not on the hospital’s contract | Low |
| Finance / capital committee | Funds in the right budget and fiscal year | Capital request, ROI or budget impact | Missed the annual capital planning cycle | Low |
| Legal / contracting | Acceptable terms | Warranty, liability, data and exit terms | Hospital paper conflicts with vendor terms | Low to medium |
Clinical champion and department head: where it starts
This is the part reps know best and influence most. But a clinician who likes the product is not the same as a clinician with the time and standing to walk it through internal process. The request usually becomes formal through a department or service-line leader, who has to decide whether this product deserves one of the department’s limited requests and budget lines.
Trial and value analysis: from “we like it” to “approved for use”
New products commonly go through a clinical evaluation and then to a committee that decides whether they can be introduced. In US hospitals this is usually a value analysis committee (VAC) or a new product committee. VACs are multidisciplinary groups that manage which medical and surgical products are used across a hospital or IDN, typically drawing on supply chain, clinical and finance. Some health systems route every new product through a formal request; UCI Health, for example, runs new product requests through a multidisciplinary value management committee that weighs clinical efficacy, product evaluation and financial impact.
The committee’s question is rarely “is this a good product?” It is “is this worth adding, compared with what we already use and already have on contract?” What committees ask and what a rep can prepare is covered in detail in value analysis committees: what they ask and how to prepare.
Clinical engineering and IT: the two technical gates
Clinical engineering — often called biomed or healthcare technology management — cares less about clinical outcomes than about what happens over the device’s life in the building: safety, maintenance, service response and parts. Reps underestimate this gate until warranty or service terms hold up the deal.
If the device connects to the network, integrates with the EHR or runs software, IT and security become a decision unit too. A common artifact here is the MDS2, a standardized form in which manufacturers describe a device’s security and privacy controls so hospitals can manage risk. Having it ready before IT asks removes one of the most avoidable delays in the path.
Procurement, finance and legal: the units reps rarely meet
Most US hospitals buy a large share of their products through group purchasing organizations. GPOs negotiate contracts with vendors on behalf of hospitals, covering everything from commodity supplies to pacemakers and stents. Whether your product sits on the hospital’s GPO or IDN contract changes what procurement can do quickly, and what requires an exception.
Capital equipment adds another layer: it usually competes for a slot in an annual capital plan, reviewed by finance or a capital committee alongside every other request in the building. Miss that cycle, and clinical support may not matter until the next one. Why procurement so often holds a deal for months — and how to read each kind of silence — is the subject of hospital procurement: why clinical approval is not the finish line.
How the Path Changes Outside US Private Hospitals
The nodes above exist in most health systems. The rules around them do not.
| System | What changes |
|---|---|
| US private and non-profit hospitals | VAC or new product committee; heavy use of GPO and IDN contracts; annual capital planning |
| US federal facilities | Federal acquisition rules apply to purchasing |
| England (NHS) | Trusts often buy through national frameworks run by NHS Supply Chain, and certain high-cost specialised devices are directed through a national supply route |
| Public hospitals in many other countries | Public procurement law governs the purchase; specifications usually go to open tender, which limits brand-specific requests |
The practical rule: identify early whether the hospital is bound by public procurement rules, and whether it buys this category through a central contract. Both decide how much a clinician’s preference can shape the final outcome.
Reading a Stalled Deal by Node
Hypothetical scenario. A rep is selling a connected smart infusion pump to a 400-bed community hospital that belongs to a regional IDN. Nursing leadership is enthusiastic and a unit trial went well. The CRM shows “Trial complete” — for four months.
| Node | Status | Unmet condition |
|---|---|---|
| Nursing leadership (champion) | Cleared | — |
| Clinical trial | Complete | Trial results not yet written up for committee |
| Value analysis committee | Not scheduled | Needs the trial summary and a cost comparison with current pumps |
| Clinical engineering | Not started | Service plan and parts commitment not provided |
| IT and security | Not started | MDS2 and EHR interface specs not provided |
| Procurement | Waiting | Pump not on the IDN’s current contract |
| Capital committee | Waiting | Not in this fiscal year’s capital plan |
Read by stage, the deal is stuck. Read by node, it is stuck in five different places, each with a different next action: help nursing write up the trial, send the service plan to clinical engineering, send the MDS2 and interface specs to IT, ask procurement what an off-contract purchase requires, and find out when the next capital cycle opens. None of those is solved by another visit to the champion.
What the Rep Can Actually Do
Most of these nodes are out of reach. Plenty is still in reach:
- Settle the two outside conditions first. Authorization and reimbursement frame every internal evaluation.
- Learn the hospital’s calendar early. When does the VAC meet? When does the capital plan close? One well-timed request beats ten visits at the wrong time.
- Route evidence to the unit that needs it. Literature to clinicians, the service plan to clinical engineering, the MDS2 to IT, the cost comparison to value analysis. Each document has a destination.
- Use your champion to see inside rooms you cannot enter. You will not attend the VAC or the capital committee, but your champion can tell you where the request sits and what it is missing.
- Track status by unit, not just by stage. A hospital deal can run more than a year. Contacts change, committees reschedule, and memory alone loses the picture fast.
Hospitals are one case of a broader pattern. The same logic in any industry is covered in complex B2B sales: how long-cycle deals actually progress. If a trial went well and nothing has moved since, see from pilot to purchase: why successful trials do not close. To map influence inside each unit systematically, see sales stakeholder mapping.
Keeping Every Node Visible
A hospital deal involves clinical, engineering, IT, procurement and finance at once, each moving at its own pace. Most CRMs give you one stage field, which makes it hard to see which unit has not cleared.
VINEQRA is an iOS app built for deals like this. It represents a hospital opportunity as the decision units inside the hospital, each with its own status, and keeps the interaction history with each one. When a unit stops moving, VINEQRA flags where the process appears stuck and suggests a next action based on the blocker. The suggestion is a starting point: you know the account, and you decide.
Download VINEQRA on the App Store
Frequently Asked Questions About the Medical Device Sales Process
What are the steps in the medical device sales process?
Common steps are clinical interest, a formal request by the department, clinical evaluation or trial, value analysis or new product committee review, clinical engineering and IT review where relevant, procurement and contract checks, capital or budget approval, and contract negotiation. The order and scope vary by hospital and by product type.
How long is the medical device sales cycle?
It varies widely. Consumables, capital equipment and software follow different paths, and a hospital’s committee and capital calendars set much of the pace. Missing an annual capital cycle can delay a purchase by a year, regardless of clinical support.
What is a value analysis committee?
A multidisciplinary hospital committee — typically including clinical, supply chain and finance members — that reviews whether new products should be introduced, weighing clinical outcomes, cost and existing alternatives.
Why do hospital deals stall after clinicians say yes?
Because clinical support satisfies only one unit. Value analysis, clinical engineering, IT, procurement or finance may each still have an unmet condition, and those units rarely tell the rep what it is.
Do GPO contracts affect whether a hospital can buy a device?
They affect how easily it can. If a product is on the hospital’s GPO or IDN contract, procurement usually has a ready path. If it is not, the purchase may need an exception, a new agreement or additional review.