Blog
/
November 17, 2026

The Questions That Matter Most in Value Analysis Are Often Asked Too Late

The Hidden Complexity Behind Healthcare Decisions

Healthcare organizations bring together an extraordinary range of expertise to make complex decisions. Clinicians understand the impact on patient care. Supply chain leaders bring insight into sourcing, contracts, utilization, and cost. HTM and BioMed teams understand what it takes to maintain and support equipment throughout its lifecycle. IT teams evaluate security, infrastructure, and integration requirements. Finance leaders consider both immediate costs and long-term value.

Value Analysis plays an important role in bringing these perspectives together. But even having the right people involved does not always make a complex decision straightforward. Information may be incomplete. Perspectives may be siloed. Important supporting information may be difficult to access or interpret. The people with the most relevant insight may not be involved until the process is already underway. And sometimes, the expertise needed to evaluate a decision simply does not exist within the organization.

The challenge, then, is not just having the right people in the room. It is making sure the organization has access to the information and expertise it needs and can bring those elements together early enough to meaningfully shape the outcome.

That timing matters.

In a Value Analysis process, some of the most consequential considerations can sound deceptively practical. Will staff need additional training? Are there IT or cybersecurity implications? Does HTM or BioMed need to be involved? Is a service contract required? Are comparable products or technologies already in use? What information supports the need and intended outcome? What operational impact will follow if the organization moves forward?

These are not minor details to resolve after a decision has been made. They can determine whether a request moves forward with confidence, requires additional review, or creates challenges that surface only after implementation is underway.

And too often, these questions are asked too late.

A product request may begin with strong clinical interest. A standardization initiative may have broad support. A technology or equipment need may initially appear straightforward.

As the request moves through Value Analysis, new considerations may surface—from training and service requirements to IT implications, clinical considerations, existing contracts, and standardization opportunities.

Consider a technology request that appears clinically compelling but requires new infrastructure, a cybersecurity review, specialized training, and ongoing service support. If those requirements surface only after the request has gained momentum, the organization may find itself revisiting questions that could have been addressed at the outset.

These discoveries do not necessarily mean the original request was flawed. They simply reveal how interconnected healthcare decisions have become.

A product is rarely just a product. A device is rarely just a device.

Each decision can carry clinical, financial, operational, technical, and logistical consequences that may not be visible at the beginning. What appears to be a straightforward product decision can ultimately affect staffing, training, contracts, infrastructure, maintenance, cybersecurity, utilization, standardization, and the resources required to support the decision over time.

The work of Value Analysis, then, is not simply to determine whether something should be approved. It is to understand what the decision will require from the organization before momentum builds around a path that may later need to be reconsidered.

The strongest Value Analysis processes surface critical considerations while there is still time to act on them.

Building a Process That Supports Better Decisions

A structured Value Analysis process should not treat every request the same way. Some decisions are routine and require relatively little cross-functional review. Others carry broader implications for patient care, training, technology, standardization, facilities, contracts, or lifecycle support.

The goal is to recognize those differences early and respond accordingly.

That starts with understanding the full context of the request.

Not simply, “What does this cost?” or “Who requested it?” but questions such as:

  • What problem is this request intended to solve?
  • What information supports the request and intended outcome?
  • What alternatives exist?
  • Are comparable products or technologies already in use?
  • What teams could be affected?
  • What resources will be required after approval?
  • How does the request align with organizational standards and strategic priorities?

A more effective process creates a consistent way to capture the reason for the request, define the problem being solved, review the supporting information, and determine the level of review appropriate for the type and complexity of the request.

It also makes important information easier to access before the discussion advances too far. Supporting information, product alternatives, existing contracts, utilization insights, standardization considerations, lifecycle costs, service requirements, and implementation needs should be brought into the process early rather than uncovered one at a time as the request advances.

This is where a structured workflow can make a practical difference. By giving organizations a consistent way to capture requests, organize supporting information, engage the right stakeholders, and maintain visibility throughout the process, workflow technology can help turn a sound Value Analysis methodology into a more repeatable practice.

When key information and stakeholders are brought into the process earlier, teams can spend less time tracking down information, resolving questions late in the review, or revisiting decisions as new considerations emerge. This can help reduce unnecessary delays, improve time to decision, and create a more efficient review process.

The goal is not simply to move requests through Value Analysis faster. It is to improve the quality of the decision before it moves forward—while creating a more efficient path to get there.

Better Decisions Depend on Better-Timed Information

Health systems are operating in an environment where financial pressure, labor constraints, supply disruption, technology complexity, and rising expectations for clinical and operational performance are all competing for attention.

In that environment, a poorly understood decision can have consequences far beyond the Value Analysis committee. It can affect implementation timelines, stakeholder trust, resource planning, contract strategy, standardization efforts, and the organization’s ability to deliver change effectively.

Relevant information plays an important role in creating clarity.

When important information is introduced late, it can become a point of validation or debate after opinions have already formed and a preferred direction has begun to emerge. When that information is available earlier, it can help shape the conversation before the organization becomes committed to a particular path.

The right information can help teams determine whether a product request addresses the intended need, whether alternatives should be considered, what tradeoffs may be involved, whether safety or outcomes data support the request, and how the decision aligns with organizational standards and priorities.

The same is true of cross-functional input. A decision that appears sound from one perspective may create training, service, financial, technical, or operational implications elsewhere. Surfacing those considerations earlier gives teams more opportunity to address concerns, evaluate alternatives, and adjust plans—often reducing rework and surprises later in the process.

Because better decisions do not come from more information alone. They come from information that is available when it can still influence the outcome.

At its best, Value Analysis becomes more than a process for reviewing requests. It helps the organization understand tradeoffs, anticipate downstream impact, and align decisions with broader goals. The measure of a mature process is not simply how quickly a request moves from submission to approval, but how well the organization understands what it is approving—and what will be required to make the decision successful.

At Staritas, we help healthcare organizations bring greater structure and cross-functional visibility to Value Analysis. Our Value Analysis Workflow provides a consistent framework for capturing requests, organizing supporting information, engaging the right stakeholders, and maintaining visibility throughout the review process. This helps teams surface key considerations earlier, create a more efficient path forward, and make informed decisions with greater confidence.

In healthcare, the quality of a decision depends not only on the outcome, but on how well the organization understood the decision before moving forward.

Discover how Staritas’s Value Analysis Workflow can help you bring greater structure, collaboration, and visibility to decision-making.

Related Posts

Medline Bed Safety Alert and Market Exit: Key Considerations for Healthcare Supply Chain Leaders

The recent U.S. Food and Drug Administration (FDA) safety alert involving Medline-branded beds has brought…

The Hardest Capital Decisions Aren’t Always About the Equipment

Discover five insights from healthcare supply chain leaders on capital planning, equipment replacement, prioritizing investments,…

When Is It Really Time to Replace Capital Equipment?

How can healthcare leaders prioritize competing capital investments? Explore strategies for evaluating business cases, funding…