Where public healthcare RFPs are actually posted (and why SAM.gov misses most of them)

The short answer: SAM.gov lists federal opportunities. A county health department, a public hospital district or a state university buys under its own state and local rules, and posts its RFPs where those rules say — usually its own website, sometimes a state portal or a shared bid platform. If SAM.gov is the only place you look, you see the federal slice and miss most of the public healthcare market.

Who the public healthcare buyers are

When people say “public healthcare”, they usually mean federal agencies. But most public buyers of healthcare services, software and consulting are state and local. In the directory of public health buyers that VeloCapture reads (1,825 buyers across 56 states and territories, as of 15 October 2026), they break down like this:

• Counties — 839. County health departments, county-run hospitals and clinics, and the county purchasing office that buys for them.
• Universities — 325, many with medical schools or academic medical centres.
• State agencies — 164: Medicaid agencies, departments of health, corrections health, veterans’ homes.
• Tribal governments and tribal health organisations — 126.
• Public health districts — 94, and cities — 90.
• Hospital districts and public health systems — 67 between them.

Where they post their RFPs

Of the 2,128 procurement links in that directory, 1,934 point to a page on the buyer’s own website: a “Bids”, “Purchasing” or “RFPs” page that lists open solicitations and their documents. The rest sit on shared bid platforms — Public Purchase, BidNet Direct, Bonfire, DemandStar, OpenGov, IonWave, Jaggaer and others — where many buyers post side by side. A few states run one portal for every agency; most don’t.

Two things make this harder than it sounds. First, the documents often live somewhere other than the listing: Delaware, for example, lists a bid on one site and serves its files from a separate document server. Second, many shared platforms want a free vendor account before you can download the documents or submit, and some only show their full listings to signed-in vendors.

Why you can’t just search for them

• There is no national index. Each of those 1,825 buyers decides where it posts, and changes it when it changes website.
• Pages move. When the directory was last checked by hand, in October 2026, 80 of its links needed a corrected address and 30 more bid lists turned up for the same buyers.
• Some pages turn automated readers away. Firewalls and robots.txt rules keep a share of buyers’ pages out of reach of anything but a person in a browser — and they should be respected, not worked around.
• Listings are short-lived. Local RFPs are often open for only a few weeks, so checking once a month misses many of them.

A routine a small team can keep up

• List your buyers, not your keywords. Start from the 50–200 public bodies that buy what you sell in the states you serve, and write down each one’s bid page and the platform it uses.
• Register where it matters. On each shared platform your buyers use, create a free vendor account, choose the commodity codes for what you sell, and switch on email alerts.
• Forward the alerts somewhere you’ll triage them. Alert emails pile up in individual inboxes; route them to one place where someone decides bid or no bid each week.
• Check the rest weekly. For buyers that only post on their own site, a weekly look at each bid page catches most two-week windows.
• Read the documents early. Download the solicitation, its appendices and every addendum on the day you decide to look — addenda change scope and deadlines.

Most public healthcare RFPs are not hidden. They’re scattered: 1,825 buyers, each on its own page or portal. Finding them is a routine, not a search.

How VeloCapture helps

VeloCapture reads those buyers’ public bid pages every night, along with SAM.gov, Grants.gov and state and local feeds, and shows you the opportunities that match what you sell — each with a link to the buyer’s own page. Where a page can’t be read automatically, it says why and shows you the link instead. If your team gets alert emails from portals it subscribes to, you can forward them to a private VeloCapture address and they land in the same list. And when you decide to bid, the Velo Capture browser extension fetches the solicitation and its addenda into the RFP’s workspace from the portal you’re signed in to — including portals that keep their files on a separate site.