A hospital value analysis committee (VAC) is a multidisciplinary group that decides whether a product, technology or service earns a place in the health system. It weighs clinical, operational and financial evidence before anyone signs a purchase order. The process usually runs: request, triage, clinical and technical review, cost-benefit analysis, trial, vote, then contracting. If you sell into hospitals, this is the room where your deal is won or quietly parked.
This guide explains how the process works, who sits at the table, what evidence persuades them and why submissions get deferred. It is written for healthcare SaaS founders, physician leaders and the investors who back them.
TL;DR
- A VAC is a formal, multidisciplinary body that evaluates products on clinical, operational and financial grounds so that no single stakeholder decides alone.
- The typical path is submission, triage, clinical and technical review, cost-benefit analysis, trial, committee vote and contracting.
- Outcomes are rarely a simple yes or no: approval, limited adoption, a time-boxed evaluation, deferral or denial are all common.
- Physician sponsorship gets you in the door, but finance and supply chain stakeholders decide whether the case holds.
- Timelines vary by health system. Plan for weeks at minimum, and ask each hospital for its own policy early.
Table of Contents
- What a value analysis committee actually does
- Who sits on the committee
- The review process, step by step
- What evidence persuades a committee
- How committees decide: approve, defer or reject
- A founder's checklist before you submit
- Our perspective: the committee is a clinical conversation with a financial spine
- Preparing with a physician leader at your side
- FAQ
- Sources
What a value analysis committee actually does
The committee's job is to turn "a clinician wants this" into "the organization has examined this." According to one industry guide, a VAC evaluates products across clinical, operational and financial dimensions specifically to prevent single-stakeholder decisions.
The pressure behind these committees is real. A peer-reviewed paper on hospital value committees describes them as aiming to improve care quality, reduce costs and optimize value, and notes that some systems manage surgical preference items that account for 40-60% of hospital supply costs. The same authors observe that surgeons could once adopt technology largely on the strength of sales and marketing. Modern committees exist to make those decisions transparent and evidence-based.
That shift matters if you are a software vendor. Your champion's enthusiasm is necessary. It is no longer sufficient.
Value analysis committee vs. new products committee
The two terms get blurred, and the difference shapes your strategy.
| New products committee | Broader value analysis function | |
|---|---|---|
| Focus | Gating the entry of new products | Existing products: standardization, cost, ongoing audits |
| Posture | Reactive: responds to requests | Proactive: reviews what is already in use |
| What it asks | "Should we bring this in?" | "Is what we already buy still the best value?" |
This distinction comes from the same industry guide. In practice many hospitals fold both into one structure, sometimes with specialty subcommittees. One example is the University of Toledo's Surgical and Procedural Services committee, which operates as its own value analysis body for that service line. Ask which body will see your product before you build your materials.
How common are VACs?
Very. A 2015 survey of decision-makers at 76 U.S. hospitals, presented at ISPOR, reported that VACs had become effectively universal among participants. It is a small sample and now a decade old, so treat it as direction, not a precise count. The takeaway for founders is simple: assume a committee exists, even at a smaller system.
Who sits on the committee
Participants typically include physicians, nurses and other clinical staff, supply chain or procurement directors, finance analysts and administrators, per that same overview. Each brings a different question:
- Physicians and nurses: Does it work, is it safe, will staff actually use it?
- Supply chain and procurement: How does it compare with what we already contract for, and what does the contract look like?
- Finance: What is the total cost, and what is the return?
- Administrators and executives: Does it fit strategy and the organization's priorities?
The role of the clinical champion
Physicians usually act as sponsors who initiate the request. Some policies make this formal. At Covenant HealthCare, requests from residents or interns must be sponsored and championed by an attending privileged physician or employed clinical staff member who attends the meeting.
Read that carefully. The champion is not a reference you collect. They are a participant who must show up and speak for your product. If your champion is not prepared to do that, find out before you submit.
Leadership matters too. Premier's value analysis guide argues that senior leadership support is essential in the early development of a hospital's value analysis policy to secure organization-wide adherence. A committee with executive backing can say no to a favored vendor. One without it often cannot.
The review process, step by step
Policies differ by system, but the sequence is consistent. A common outline is request submission, triage and routing, clinical and technical review, cost-benefit analysis, trials, a committee vote and contracting. Here is what each stage means for you.
- Request submission. A clinician or sponsor files an intake form, often in a software platform. Expect to supply the clinical or scientific rationale, product specifications, comparable products already in use, a preliminary cost estimate and the name of the physician champion, as described in this process guide.
- Triage and routing. An administrator checks completeness and decides which committee or subcommittee should review. At UCSF Health, the administrative director appends regulatory status, financial impact and clinical efficacy to physician proposals before they go to members. Your submission may be summarized by someone who has never met you. Write it so the summary is hard to get wrong.
- Clinical and technical review. Clinicians examine the evidence. For software, technical review also raises integration, security and workflow questions that purely clinical products avoid.
- Cost-benefit analysis. Finance and supply chain test the numbers against current spend and alternatives.
- Trial or evaluation. Many systems run a defined-period pilot before committing.
- Committee vote. The group decides. Some use a simple majority, as the University of Toledo's surgical committee does.
- Contracting and onboarding. If approved, the product often proceeds to negotiation of final terms such as pricing and purchase frequency with the vendor representative, according to Symplr's overview.
One rule from Covenant's policy is worth remembering. Any product that enters the organization without a purchase order or prior committee approval is considered a donation. Free pilots handed to an enthusiastic physician can bypass the process and then stall for exactly that reason.
How long does it take?
There is no national standard. Covenant's 2022 policy routes new requests to an administrator for an initial review that typically requires at least 21 business days. That is the initial review only, before trials, votes or contracting. Committees also meet on a schedule, so missing a cycle can cost you a month or more. Ask each hospital for its meeting calendar and its written policy, then build your sales forecast around them, not around your own quarter-end.
What evidence persuades a committee
Committees draw on several kinds of evidence. Covenant's policy points to clinical evidence, ideally independent of the manufacturer, reimbursement impact, return on investment calculations and clinical validation tools, plus operational factors such as training requirements, storage needs and alignment with existing safety protocols.
For a SaaS product, translate those categories like this:
| Evidence type | What a SaaS vendor can offer |
|---|---|
| Clinical | Outcome data, ideally from an independent or peer-reviewed study; a clear clinical use case |
| Operational | Training time, workflow changes, EHR integration effort, support model |
| Financial | Total cost of ownership, ROI model built on the hospital's own volumes, reimbursement impact |
| Safety and regulatory | Regulatory status, security posture, how the product fits existing protocols |
A clear clinical use case is the foundation. We cover how to build one in our guide to developing a clinical use case for SaaS. If your product touches decision support, regulatory documentation is part of the review too, which is why we wrote about the documents FDA reviewers want for clinical decision support.
Build the value case for finance, not just the champion
One analyst argues that manufacturers must prepare a comprehensive value case that appeals specifically to finance and supply chain stakeholders, not just the physician champion. We agree with the principle: your champion will carry the clinical argument, and your spreadsheet has to survive people who have never seen a patient chart.
That spreadsheet is only as good as the data under it. Hospitals with a well-structured hospital data management system can pull their own volumes and cost figures quickly, which makes it easier to test your assumptions against their reality. Ask your champion who can supply baseline numbers, and build the model on those.
Keep in mind that definitions of value differ. The authors of the Journal paper note that value is broadly the ratio of quality to cost, but the specific definition and metrics vary significantly among stakeholders. Do not assume the nurse manager and the CFO mean the same thing by the word.
How committees decide: approve, defer or reject
Outcomes are more nuanced than a yes or no. Covenant's policy lets the committee approve, deny or defer, and after evaluation it may choose full or limited adoption, an evaluation for a defined period, postponement or decline. UCSF's committee uses four outcomes: approved, denied, provisionally approved or tabled for more information.
Some systems score requests. Covenant uses a scorecard that generates a recommended decision on a scale of 0-27. If a hospital uses a scorecard, ask for it. It tells you exactly what the committee will measure.
Why submissions get deferred
The research does not give a ranked list of rejection causes, so we will not invent one. What the policies above do show is where a deferral typically starts: missing information, no sponsoring clinician, no comparison with the product already on the shelf, or no cost estimate. These are all items the intake form asks for. A deferral is often a completeness problem, not a verdict on your product.
Turning a deferral into a yes
- Ask the administrator, in writing, what specific information the committee wanted.
- Return with that information, and nothing that was not requested.
- Offer a time-boxed evaluation with agreed success metrics, since limited adoption is a recognized outcome.
- Keep your champion informed so they can speak at the next meeting.
Sophisticated programs go further after approval. According to the Journal paper, clinically integrated value analysis programs can track new technology adoption and measure real-world impact against predicted clinical, financial and operational outcomes. Assume that what you promise in the submission will be checked later, and promise only what you can show.
A founder's checklist before you submit
- Identify the committee that will review you and get its written policy and meeting schedule.
- Secure an attending physician or clinical leader who will attend and present.
- Document the clinical rationale and any independent evidence.
- Name the product or workflow you replace, and compare honestly.
- Build a cost model on the hospital's numbers, with finance in mind.
- Prepare the operational answers: training, integration, support, security.
- Do not place the product in clinical use before approval and a purchase order.
- Plan the contracting conversation. Our 30/90/180 day hospital contracting playbook covers what follows approval.
For the broader picture of why these committees carry so much weight, see our post on making hospital value analysis committees count. If your go-to-market plan has not accounted for committee timelines, common healthtech go-to-market mistakes is a good place to check it.
Our perspective: the committee is a clinical conversation with a financial spine
We see founders treat the VAC as a procurement hurdle. It is better understood as a clinical conversation with a financial spine. The clinicians want to know whether the product helps patients and fits their day. The finance team wants to know whether the organization can afford to say yes. A submission that answers only one of those questions gets deferred.
The most common gap we see is between the clinical story and the economic story. The founder knows the product is good and cannot translate that into a hospital's language of volumes, workflow minutes and avoided costs. That is the gap a fractional Chief Medical Officer is built to close. A physician leader who has sat on the clinical side of these decisions can pressure-test the use case, sharpen the evidence and prepare the champion before the committee ever meets.
If something in your submission feels misaligned, I would welcome a conversation.
— Paul Bergeron MD, MBA
Preparing with a physician leader at your side
The StartUp MD is a healthcare advisory firm, and we support healthcare SaaS and digital health companies with Fractional Chief Medical Officer and advisory services. That includes clinical strategy, product evaluation, market readiness assessment and investor support. For a company heading into its first value analysis review, that means someone with clinical and business experience helping you shape the clinical case, anticipate committee questions and prepare your champion. Pricing is scoped to the engagement, so reach out through our site to discuss your situation.
FAQ
What is the difference between a value analysis committee and a value analysis team?
The terms are often used interchangeably, and structures vary by hospital. Some systems have a system-level committee with smaller teams or subcommittees for specific service lines. Ask the hospital which body will review your product and request its written policy.
How do I submit a product to a hospital value analysis committee?
Submissions typically go through an intake form or software platform, usually filed by a clinical sponsor. Expect to provide the clinical rationale, specifications, comparable products in use, a preliminary cost estimate and a physician champion. Ask your champion or the supply chain office for the hospital's current form and process.
Do I need a physician champion?
In most systems, yes in practice, and some policies require it formally. Covenant HealthCare, for example, requires sponsorship by an attending privileged physician or employed clinical staff member who attends the meeting. A champion who understands both the clinical and financial case is far more effective than one who only likes the product.
How long does value analysis take?
It depends on the system. One published policy puts the initial administrative review at a minimum of 21 business days, before any trial, vote or contract. Build in committee meeting cycles and any pilot period, and confirm the schedule with each hospital.
Sources
- Hospital Value Committees: The Role of the Surgeon in New Technology Adoption
- Hospital Value Analysis Committees and GPOs: How US Medical Device Access Works
- Value Analysis Committee: How Hospital Approval Works
- Quick Guide to Understanding the Hospital Value Analysis Committee
- Clinical Quality Product Value Analysis Policy, Covenant HealthCare
- Surgical & Procedural Services CVA, University of Toledo
- Improving the Technology Adoption Process, University of California San Francisco
- Value Analysis Guide, Premier Inc.
- The Best Reasons to Design a Valuable Hospital Data Management System