Healthcare Buyer Intelligence

Buyer Intelligence

How Hospital Procurement Actually Works

From the moment someone inside a hospital wants something to the moment a contract is signed, there are six recognizable stages. Most vendors only see two of them.

Updated September 18, 2026

The short answer

Hospital procurement runs from an internal requester, through value analysis, through security and integration review, through a sourcing decision that may or may not involve competitive bidding, into contracting and then implementation. Most vendors only see the first and last stages. The middle is where purchases are actually won and lost, and it happens in rooms the vendor is not in.

Explained at three levels

1 Plain English

Buying something at a hospital is less like buying software and more like getting a permit. Someone inside has to file the request. Committees review it against rules. Other departments get a say. There is a calendar. And at several points the whole thing can be sent back for a missing document rather than because anyone disliked it.

2 Informed buyer

The two structural facts that explain most of the behavior: nearly every stage exists to prevent uncontrolled, fragmented purchasing, and nearly every stage is a queue rather than a decision. Those are different problems with different solutions. A rule-based block is solved with documentation. A queue is solved with earlier entry.

3 Technical and professional detail

Whether a purchase requires competitive bidding depends on the organization’s own thresholds, its GPO contract coverage for that category, and whether a sole source justification can be sustained. Newer software categories frequently sit outside traditional supply contracts, which gives more routing flexibility than commodity purchasing has, and correspondingly more scrutiny on the justification.

The six stages

Stage 1: Internal identification

A problem gets named by someone who has it. A service line is losing clinician time to documentation. An imaging department cannot meet a turnaround target. A quality metric is drifting.

Note what has not happened yet: nobody has decided to buy anything. This stage produces a problem statement, and the most valuable position a vendor can occupy is being the source that helped define it. That is the entire argument for discovery-stage content, and it is why an RFI is worth answering carefully even though it is unpaid.

Stage 2: Requisition and internal sponsorship

The problem becomes a request with a name on it. The requester assembles a case: what the problem costs, what the proposed solution does, what it costs, what alternatives exist, and why the organization cannot solve it with something it already owns.

That last question is the one that kills the most requests, and it is rarely asked out loud to the vendor. Many health systems already own capability they are not using, particularly inside their existing electronic health record.

Stage 3: Value analysis

The Value Analysis Committee reviews the request against clinical benefit, cost, disruption, and standardization.

The committee is usually reading a written submission, not watching a presentation. The vendor is frequently not present. This is the single most misunderstood stage in healthcare selling: the quality of the document beats the quality of the pitch, because the document is what is in the room.

Stage 4: Parallel technical reviews

Security and privacy review, integration assessment, and where relevant clinical governance run alongside each other. Each can block independently.

These are mostly queues. Integration analyst capacity in particular is scheduled months ahead at most systems, and a health system will sometimes decline an otherwise preferred product purely because it cannot staff the build this fiscal year. That is a scheduling constraint, not a product judgment, and it is worth surfacing rather than misreading.

Stage 5: Sourcing and contracting

Now the commercial mechanism gets chosen. An existing contract, a GPO agreement, a competitive RFP, or a sole source justification.

By the time an RFP is published, its requirements were usually shaped months earlier by conversations with one or two vendors. Responding cold to an RFP you had no hand in shaping is a low-probability exercise. That is not cynicism about the process, it is an argument for being visible earlier.

Stage 6: Implementation and conversion

For anything that started as a trial, the real purchase decision is the pilot-to-enterprise conversion, and it is judged on measured results at full price rather than on promise at pilot price.

The pattern underneath

Read the six stages together and something becomes obvious. Only stages one and six involve the vendor substantially. Stages two through five are internal, document-driven, and largely invisible from outside.

That is not an obstacle to work around. It is a description of where the influence actually sits: in the quality of the material available to the people doing the internal work, at the moment they are doing it. Which is a research problem, not a sales problem.

Where this goes next

Topics: procurement, buying process, value analysis, rfp

More in Buyer Intelligence