Skip to content
All lessons
Cross-cutting · Patient Safety

Hospital-Acquired Conditions & Never Events

A boards-focused lesson separating CMS Hospital-Acquired Conditions (the payment/present-on-admission rule) from NQF Never Events and Joint Commission sentinel events, with the tested next steps — honest disclosure, incident reporting, and root cause analysis — plus CLABSI/CAUTI prevention and the error taxonomy.

12 min readHigh yield

The Framework: Payment vs. Reporting

Hospital-Acquired Conditions (HACs) and Never Events are overlapping frameworks for preventable in-hospital harm — and both are tested as systems problems, not individual blame.

HACs are a CMS reimbursement concept: a defined list of reasonably preventable conditions for which Medicare withholds the higher DRG payment when the condition was not present on admission (POA). Never Events (the NQF Serious Reportable Events) are egregious, largely preventable errors — wrong-site surgery, retained foreign body, ABO-incompatible transfusion — that should never occur. There is real overlap between the two lists.

On Step 2 CK / Step 3 the vignette rarely asks for a drug; it asks you to (1) recognize the event, (2) choose the correct next step — honest disclosure to the patient, an incident report, and a root cause analysis — and (3) pick the system fix rather than punishing the individual.

CMS Hospital-Acquired Conditions
  • HAC = a CMS payment rule: reasonably preventable AND not present on admission (POA) → hospital absorbs the cost (no higher DRG). In effect since 2008 (Deficit Reduction Act of 2005).
  • Classic CMS HACs: retained foreign object after surgery; air embolism; ABO-incompatible blood; stage III/IV pressure ulcers; falls/trauma (fractures, dislocations); CAUTI; CLABSI (vascular catheter infection); SSI after CABG (mediastinitis), bariatric, or orthopedic surgery; DVT/PE after hip or knee replacement; iatrogenic pneumothorax from a central line; poor glycemic control (DKA, hypoglycemic coma).
  • POA is everything: a stage IV ulcer documented as present on admission is still reimbursed — the penalty targets what the hospital caused.
  • HAC Reduction Program (ACA): the worst-performing quartile (bottom 25%) of hospitals loses 1% of all Medicare payments (metrics include CLABSI, CAUTI, SSI, MRSA, C. difficile, and the PSI-90 composite).
Never Events & the Error Taxonomy
  • Never Event = NQF Serious Reportable Event: 29 events in 7 categoriessurgical (wrong site/patient/procedure, retained object), device, patient protection (elopement, infant to wrong person, inpatient suicide), care management (medication error, wrong blood, severe hypoglycemia, maternal death in low-risk delivery), environmental (burns, restraints, electric shock), radiologic (metal object into the MRI suite), criminal (abduction, assault).
  • Sentinel event (Joint Commission): reaches a patient causing death, permanent, or severe temporary harm → mandatory root cause analysis within 45 days.
  • Adverse event: harm from care (not always an error). Near miss: error caught before reaching the patient — still report it.
  • Active error (sharp end — e.g., wrong drug given) vs latent error (blunt end — system/design flaw, look-alike packaging).
  • Swiss cheese model (Reason): harm occurs when the holes in successive layers of defense line up.

Getting the Terminology Right

TermDefinitionReached patient?Key point
Near missError caught before it reaches the patientNoStill report — a free lesson
Adverse eventHarm caused by medical careYesNot always an error
Never eventEgregious, preventable error (NQF SRE)UsuallyWrong-site, retained object, wrong blood
Sentinel eventDeath / permanent / severe harmYesTriggers RCA within 45 days
Diagram of stacked Swiss cheese slices whose aligned holes represent failures in successive layers of defense, allowing a hazard to pass through and reach a patient.
Reason's Swiss cheese model: harm results when weaknesses (holes) in successive safety layers align — the rationale for a systems, not blame, response. · Wikimedia Commons — Davidmack — CC BY-SA 3.0, via Wikimedia Commons
Vignette: The Retained Sponge

Vignette: A 62-year-old woman has persistent fever and abdominal pain on POD#5 after exploratory laparotomy. The operative record notes an incorrect sponge count at closing. CT shows a rolled radiopaque marker (gossypiboma).

  • Recognition: a retained surgical foreign body is both a Never Event and a CMS HAC.
  • Next best step if the count is incorrect intraoperatively: obtain an intraoperative radiograph before the patient leaves the OR.
  • Recognized later: surgical removal + disclose the error to the patient (honest disclosure is ethically and legally correct, even absent lasting harm) + file an incident report + institutional root cause analysis (systems-focused, non-punitive).
  • Prevention = Universal Protocol: pre-procedure verification, site marking, and a "time-out" immediately before incision; standardized instrument/sponge counts.
  • Wrong-site / wrong-patient surgery is prevented by the same time-out — a skipped time-out is the classic root cause.
Vignette: The Central Line

Vignette: An ICU patient with a femoral central line for 6 days develops new fever and hypotension. Cultures drawn from the line and a peripheral vein grow the same organism with no other source → CLABSI.

  • Next best step: remove the catheter, culture the tip and blood, and start empiric antibiotics — vancomycin (MRSA) plus gram-negative coverage (e.g., cefepime) in this septic patient.
  • CLABSI prevention bundle: hand hygiene, maximal sterile barrier at insertion, chlorhexidine skin prep, subclavian site preferred (avoid the femoral site — highest infection risk), and daily review with prompt removal of unnecessary lines.
  • CAUTI: place a Foley only when truly indicated, use aseptic technique, and remove as early as possible; a catheter left in "for convenience" is the classic misstep.
  • Both are CMS HACs — if hospital-acquired and not POA, Medicare will not pay the added cost.
The 5 Rights of Medication Administration

The "5 Rights" — the bedside defense against medication-error Never Events:

  • Right Patient (verify two identifiers)
  • Right Drug
  • Right Dose
  • Right Route
  • Right Time

(Commonly extended by Right Documentation and Right Reason.)

Look-alike / sound-alike drug names, unlabeled syringes, and verbal or telephone orders (always use read-back) are the classic latent setups. The boards want the system fix — barcode scanning, standardized labeling, computerized order entry — not merely blaming the nurse.

RCA vs. FMEA: React vs. Anticipate

FeatureRoot Cause Analysis (RCA)FMEA (Failure Mode & Effects Analysis)
TimingRetrospective — after an eventProspective — before an event
TriggerA sentinel event occurredA new or high-risk process
Core question"Why did this happen?" (5 Whys)"What could go wrong?"
AimFix the system, non-punitiveAnticipate and prevent failure modes

Practice Patient Safety now

Board-style questions, spaced-repetition flashcards, and a Socratic AI tutor — free to start.