Definition

Fee-for-service (FFS) is a payment model in which providers are paid separately for each service they deliver, such as a visit, test or procedure. Because it rewards volume rather than outcomes, payers and CMS are moving more payment toward value-based models, though fee-for-service still underpins much of physician and hospital billing.

Under fee-for-service, physicians and facilities bill each test, treatment or visit separately. Because each service brings payment, the model rewards doing more. Models such as alternative payment models, patient-centered medical homes and accountable care organizations pay for results instead.

Why does fee-for-service still matter in healthcare?

FFS remains the base of how most US providers are paid, and many value-based models are built on top of FFS payments with bonuses or penalties added. Its focus on volume can lead to unnecessary services and higher costs, which is why CMS and commercial payers keep moving more payment toward value-based care that rewards outcomes and quality.

How is price transparency changing fee-for-service?

Federal price transparency rules require hospitals to publish their standard charges and negotiated rates, and require many health plans to publish their rates too. Patients can compare prices for common services before they get care, and employers and payers use the data in negotiations.

What fee-for-service means for teams selling into healthcare

Whether a provider is paid mostly by FFS or by value-based contracts changes what they buy. FFS-heavy organizations invest in coding, charge capture and throughput, while organizations with more risk invest in care management and analytics. Ask about the payer mix early, because it tells you which problem the buyer is trying to solve.

FFS

See where FFS 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)