Glossary

Group Purchasing Organization (GPO)

Definition

A group purchasing organization (GPO) is an organization that negotiates contracts with manufacturers, distributors and other vendors on behalf of many hospitals, health systems and other providers, using their combined buying power to get better prices and terms. For suppliers, being on a GPO contract often decides whether a product can be sold to its members.

A GPO does not buy products itself. It negotiates contracts with prices and terms, and its members, such as hospitals, health systems, surgery centers, nursing homes and physician practices, buy from vendors under those contracts. Vendors usually pay the GPO an administrative fee on what members buy.

How do group purchasing organizations work?

  • Providers join a GPO, often through their health system, and get access to its contract portfolio.
  • The GPO runs sourcing events, often with input from member clinicians and supply chain leaders, and awards contracts to one or more vendors in each category.
  • Members choose which contracts to use and buy directly from the vendor or distributor.
  • Vendors pay the GPO a fee based on member purchases, and many GPOs share part of it back with members.

What do GPOs contract for?

GPOs started with medical and surgical supplies and now cover much more: pharmacy, capital equipment, food service, purchased services, staffing and software. Many also offer analytics, benchmarking and consulting to help members manage spending.

Which GPOs do hospitals use?

National GPOs include Vizient, Premier and HealthTrust, and many health systems also run regional purchasing groups or belong to more than one GPO. The market keeps consolidating: Vizient completed its acquisition of Intalere on April 1, 2021 (Vizient news release). Check a hospital's current GPO before you plan a deal, because older lists go out of date.

What GPOs mean for teams selling into healthcare

For MedTech and supply vendors, a GPO contract can open the door to many members at once, but it does not guarantee volume: each hospital still decides what to buy, and clinicians often drive product choice through value analysis. Health IT and services companies meet GPOs too, because many GPOs now contract for software and purchased services. Before you pitch a hospital, find out which GPO it uses and whether its health system buys centrally, then reach both the supply chain leaders and the clinical owners of your category.

Dmand AI guides that use GPO

GPO

See where GPO shows up on the accounts you sell to

Search 7.4M+ HCPs and 11M+ executives at 997K+ sites of care, each placed under its health system and IDN.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)