Your champion tells you the product is “going to value analysis.” Many medical device reps hear that as the last step. In practice it is the point where the deal is least in your hands: a meeting you will not attend, a group of people you mostly have not met, and a date that was set long before your product came along.
A value analysis committee is not a price negotiation. It is a structured request for evidence that the rep is usually asked to supply on a deadline they did not set.
This guide explains what these committees review, how evaluation is layered across health systems, and what you should have ready before submission — in many cases before the trial even starts. For the full path from clinical interest to purchase order, see how medical devices actually get bought by hospitals. This page covers the committee only.
What a Value Analysis Committee Is
“Value analysis committee” (VAC) is the term most widely used in US hospitals. It describes a multidisciplinary group, typically drawing on supply chain, clinical and finance, that manages which medical and surgical products are used across a hospital or health system. Other hospitals call it a new product committee, a product evaluation group or a value management committee. In many health systems outside the US, the name is different again — but almost every hospital has some body that decides whether a new product can come in.
One thing reps rarely realize: new products are a small part of the committee’s work. HealthTrust advisers describe value analysis as mainly a proactive review of the hospital’s existing product portfolio, and suggest that new product introductions take up less than 10% of the agenda. Your product is competing not only with other products, but for the committee’s time. An incomplete submission is the easiest item to push to next month.
Evaluation Often Happens at Two Levels
In many health systems, a new device is evaluated twice: once at the system or national level, and once inside the hospital.
System level: health technology assessment. Some systems run national evaluations of medical technologies. In England, NICE’s Medical Technologies Evaluation Programme evaluates new devices and simple diagnostics to help the NHS adopt efficient, cost-saving technologies more rapidly and consistently. In Singapore, the Agency for Care Effectiveness evaluates medical technologies to support evidence-based subsidy recommendations by the Ministry of Health’s advisory committee.
Institution level: adoption. A positive system-level evaluation does not mean every hospital adopts. The same Singapore research notes that adoption of medical technologies depends heavily on the organizational feasibility of each institution, and NICE’s recent expansion of device evaluations was framed explicitly as a response to long-standing inequalities in technology adoption across NHS regions. The hospital committee still decides whether the product fits its budget, workflow and existing contracts.
| Setting | System-level evaluation | Hospital-level decision | What the rep should watch |
|---|---|---|---|
| Hospitals using a VAC model (common in the US) | Usually none for most products | Value analysis or new product committee, often alongside GPO or system contracts | Whether the product sits on the hospital’s existing contract |
| Systems with a national HTA body for devices | National guidance or subsidy recommendations | Hospital still decides on adoption, budget and workflow | Evidence prepared for both audiences |
| Systems with central purchasing | Central contracts or frameworks | Hospital evaluates and requests within those contracts | Whether the product is, or can be, on the central contract |
| Private hospitals and groups | Rarely | Internal committee rules set by the group | The committee’s structure and calendar, confirmed account by account |
Wherever you sell, the hospital-level questions below are remarkably consistent.
The Timeline of One Review
The details vary by hospital. The structure rarely does:
| Step | What the rep should confirm | Typical delay |
|---|---|---|
| Request | Which department and clinician submits it, and whether department sign-off is required | The department head has not signed |
| Document review | Regulatory status, classification, safety and compliance documents | One missing document sends the request back |
| Clinical evaluation | Who runs the trial, for how long, and how results are recorded | The trial ends and nobody writes it up |
| Submission | The deadline for this meeting cycle, and who submits | Missed by days; the request waits for the next cycle |
| Committee review | The meeting date and when decisions are published | A committee question with no answer in the file |
| Activation | Who raises the purchase or item request once approved | Approved, but nobody starts the purchase |
Two points stand out. First, almost every deadline belongs to the hospital. Your job is to know those dates and make sure nothing you own becomes the delay. Second, approval is not an order. Approval usually means the product may be bought; someone in the department still has to request it, and in systems with central contracts, the product may also need to be on the right one.
What the Committee Asks, and What to Prepare
The committee will not send you its questions, but they are predictable. The checklist below is organized by the committee’s own questions, not by your sales materials.
| The committee’s question | What to prepare | When to start |
|---|---|---|
| Is it approved and safe for this use? | Regulatory approval for this market, device classification, safety documentation | Before you enter the account |
| Does it improve outcomes? | Clinical evidence, published literature, usage records and feedback from the trial | Before and during the trial |
| What does it cost compared with what we use now? | Cost per use and total cost comparison, including consumables and equipment | Before the trial |
| Will it disrupt current workflow? | Workflow description, differences from current practice, issues found during the trial | During the trial |
| How much training does it need? | Training plan, time required, who delivers it | Before the trial |
| Can we rely on supply and service? | Supply continuity, lead times, consumable and service commitments | Before submission |
| Does it conflict with existing contracts? | Whether a comparable product is already on contract, and a transition plan if so | Before you enter the account |
| How is it disposed of or reprocessed? | Disposal requirements or reprocessing options | Before submission |
Most of these cannot be assembled the week before submission. They accumulate during the trial, and some must exist before the trial starts. When the committee meets, the trial report is already final. There is no chance to add “the nurses really liked it.”
Cost: where most submissions stall
Of all the questions, the cost comparison is the one most likely to push a submission to the next meeting. The committee does not want your unit price. It wants to know whether switching costs more or less than what it already buys. That means understanding the current product, its usage volume and its contract terms — and including consumables, training and service in the comparison. Without it, even a supportive committee member has nothing to argue with.
The Interaction Record You Need Before Submission
The committee reads documents, but the documents come from months of conversations. By the time you submit, you should be able to answer these immediately:
- Who raised the need, and why? Which clinician or department first asked for it, and what problem they described.
- Who in the department supports it, and who has doubts? If sign-off is required, who signs and when.
- Who used it during the trial, and what did they say? Not “feedback was positive,” but which nurse described which benefit or problem, in which situation.
- What concerns came up, and how were they resolved? The committee is likely to raise the same ones.
- Who is writing up the trial, and by when? This is where most delays actually start.
- Who will request the product once approved, and through which contract? Confirm it before approval, not after.
Over a trial of several weeks or months, these details scatter across visits, calls and messages. Looking for them the week the submission is due is usually too late. For a practical way to capture them as you go, see how to track every client interaction in B2B sales.
A Deferred Submission, Read on a Timeline
Hypothetical scenario. A rep is introducing a new negative-pressure wound dressing at a large teaching hospital. The surgical ward trialled it for two months, and the nurses found dressing changes faster. The rep is confident and waits for the committee’s decision.
The product is deferred to the next cycle. When the rep asks why:
- The nurse manager compiling the trial results was on leave before the deadline. The file arrived a few days late, landed at the end of the agenda, and was not discussed.
- A committee member asked how the total cost per dressing change compares with the product already on contract. The file had no comparison.
- The current wound-care contract still had a year to run. Members were concerned about the conflict, and the file did not explain how a transition would work.
None of these are problems with the product. They are problems with preparation. Had the rep confirmed the submission deadline at the start of the trial, and built the cost comparison and transition plan during it, the outcome could have been different.
After Approval
Committee approval means the product may be bought. Procurement, contracting and budget still follow, and each can stop the deal again. Why procurement so often holds a deal for months, and how to read each kind of silence, is covered in hospital procurement: why clinical approval is not the finish line. If your trial went well and nothing has happened since, see also from pilot to purchase: why successful trials do not close.
Keeping Every Piece of Evidence Findable
The evidence a committee needs is spread across months of visits, trials and messages: who raised the need, who supports it, which nurse mentioned which benefit, who asked about cost, who owns the write-up. Most CRMs remember how many times you visited, not what was said.
VINEQRA is an iOS app that keeps the interaction history for each stakeholder in an opportunity. Before you submit, you can look back across meetings to find the evidence and concerns gathered along the way, see what is still missing, and check where each department stands.
Download VINEQRA on the App Store
Frequently Asked Questions About Value Analysis Committees
What does a value analysis committee do?
It decides whether a new medical product should be introduced, weighing clinical outcomes, total cost compared with current products, the effect on workflow and training, supply and service reliability, and conflicts with existing contracts. Many committees also spend much of their time reviewing products already in use.
Who sits on a value analysis committee?
Membership varies, but committees are typically multidisciplinary, drawing on clinical staff, supply chain and finance. Some include physician leaders, nursing representatives and other departments affected by the product.
Do all hospitals have a value analysis committee?
The name is most common in US hospitals, but most hospitals have some equivalent body that approves new products. In some health systems, there is also a national evaluation of medical technologies, and the hospital still makes its own adoption decision afterwards.
Can sales reps attend value analysis committee meetings?
Usually not. The committee works from written submissions and trial results, so a rep’s influence lies in preparation: complete documents, specific trial feedback, a credible cost comparison, and a submission that arrives before the deadline.
Does committee approval mean the hospital will buy the product?
Not necessarily. Approval usually means the product may be purchased. Someone in the department still needs to request it, and procurement, contracting and budget must still follow. Confirm who will raise that request before approval.