Glossary

Hospital-Acquired Conditions (HACs)

Definition

Hospital-acquired conditions (HACs) are harms a patient develops during a hospital stay that were not present on admission, such as infections, pressure injuries, falls and blood clots after surgery. Medicare reduces payments to hospitals with the highest HAC rates, so reducing them is both a quality and a financial priority for hospital leaders.

HACs were not present when the patient was admitted, so they often point to gaps in the quality of care. They make patients sicker, lengthen stays and raise costs, which is why CMS ties hospital payments to them.

What are common examples of hospital-acquired conditions?

  • Infections picked up in the hospital, such as Clostridioides difficile (C. diff) and MRSA
  • Surgical site infections after procedures
  • Stage III and IV pressure injuries
  • Infections linked to central lines and urinary catheters
  • Falls and injuries during the stay
  • Blood clots after certain surgeries

How does Medicare penalize hospital-acquired conditions?

Under the Hospital-Acquired Condition Reduction Program, hospitals that rank in the worst-performing quartile on HAC measures, with a Total HAC Score above the 75th percentile, receive a 1% reduction in Medicare payments for all fee-for-service discharges that year (CMS, HAC Reduction Program, as of September 2026).

How can technology help reduce HACs?

Early-warning tools in the EHR flag patients at risk of sepsis, falls or pressure injuries before harm happens. Infection surveillance software tracks cases across units, and analytics show which practices and units need attention. Devices such as safer catheters and pressure-relief surfaces target specific conditions.

What HACs mean for teams selling into healthcare

Because HACs carry a direct payment penalty, patient safety and infection prevention leaders have a clear reason to buy. Sell to the chief quality officer, the CNO, infection prevention and the patient safety team, and show how your product moves the measures CMS scores.

HAC

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