Written and maintained by CASRAI Editorial Board
Last updated
A hospital’s incident-review process runs into a vocabulary problem fast: “never event” gets used loosely for almost anything shocking, while the National Quality Forum’s actual technical term for the concept is Serious Reportable Event (SRE). For patient-safety officers, quality directors, risk managers, and infection preventionists who own reporting decisions, that distinction is not academic — the term someone uses in a debrief is not necessarily the term a state statute, an accreditor’s policy, or a payer’s rule actually references. This guide covers the NQF SRE list’s real structure, how “never event” relates to it as a looser, non-official label, and what the practical reporting consequences are once an event on the list occurs.
What the NQF Actually Publishes: “Serious Reportable Events,” Not “Never Events”
The National Quality Forum (NQF) — the standards-setting body behind a large share of the measures used in U.S. hospital quality reporting — maintains a list titled the Serious Reportable Events list. NQF’s own criteria for an event to appear on it are that the event is unambiguous (clearly identifiable and measurable), serious (resulting in death or significant disability), and usually preventable through system-level safeguards. NQF’s list was most recently updated in 2012.
“Never event” is an older, informal label — the phrase entered patient-safety usage around 2001, before NQF’s formal list existed in its current form, as shorthand for errors so serious they should, in principle, never happen. Once NQF published its consensus list, “never event” became the popular name people attached to it, but the two things are not perfectly synonymous:
- Serious Reportable Event is NQF’s defined technical term, tied to a specific enumerated list that gets formally revised through a consensus process.
- Never event is colloquial. It is not an NQF term of art, has no single canonical definition, and gets applied inconsistently — sometimes to mean exactly the NQF list, sometimes more loosely to any severe, obviously-preventable error a speaker considers unacceptable.
For day-to-day conversation the difference rarely matters. It matters a great deal the moment a specific reporting obligation is on the table, because “our state requires reporting of never events” is not a precise enough statement to act on — the actual statute or regulation will define its own trigger, and it may or may not be the NQF list verbatim.
The NQF Serious Reportable Events List: 7 Categories, 29 Events
NQF organizes its Serious Reportable Events list into seven categories, comprising 29 specific enumerated events. The category structure itself is what makes the list usable operationally — it gives a patient-safety program a checklist to sort an incoming event against, rather than a flat list of 29 unrelated items:
| Category | What it covers | Representative events |
|---|---|---|
| 1. Surgical or Invasive Procedure Events | Wrong-site, wrong-patient, or wrong-procedure errors, and severe intraoperative harm | Wrong-site surgery; unintended retention of a foreign object after a procedure; death of a normal, healthy patient during or immediately after elective surgery |
| 2. Product or Device Events | Harm caused by contaminated or malfunctioning products/devices the facility supplied | Patient death or serious injury from a contaminated drug, device, or biologic supplied by the facility; death or serious injury from a device malfunction used other than as intended; death or serious injury from intravascular air embolism |
| 3. Patient Protection Events | Failures in supervising or safeguarding a vulnerable patient | Discharge or release of a patient of any age unable to make decisions to someone other than an authorized person; patient disappearance (elopement) resulting in death or serious injury; patient suicide, self-harm, or attempted suicide resulting in serious injury while under care in a facility |
| 4. Care Management Events | Breakdowns in the medication, blood-product, maternal, and general-care processes | Death or serious injury from a medication error; death or serious injury from administration of incompatible blood or blood products; maternal death or serious injury associated with labor/delivery in a low-risk pregnancy; a stage 3, 4, or unstageable pressure injury acquired after admission; failure to communicate a critical test result in time to prevent harm |
| 5. Environmental Events | Harm from the physical care environment itself, not the clinical intervention | Death or serious injury from an electric shock during care; death or serious injury from a burn from any source; death or serious injury associated with physical restraints or bedrails |
| 6. Radiologic Events | Harm from imaging-related hazards, most specifically MRI | Death or serious injury from the introduction of a metallic object into the MRI area |
| 7. Potential Criminal Events | Acts that are also potential crimes, not just clinical failures | Care ordered by, or care/treatment provided by, someone impersonating a licensed healthcare provider; abduction of a patient of any age; sexual abuse/assault of a patient within or on the grounds of the facility; physical assault occurring within or on the grounds of the facility |
Two things are worth noting about how this list actually functions in practice. First, it was designed as a public accountability and reporting framework, not a clinical taxonomy for internal harm scoring — a program that also uses AHRQ’s Patient Safety Indicators or a homegrown severity scale needs to keep those systems conceptually separate from the SRE list, even where an event happens to trigger more than one at once. Second, because the list is built around identifiable, unambiguous occurrences rather than outcome severity thresholds, an event can be on the SRE list without meeting a broader harm-severity definition used elsewhere in a hospital’s safety program, and vice versa.
How SREs Relate to — and Differ From — TJC Sentinel Events and CMS HACs
Three frameworks get invoked around the same incident, from three different bodies, for three different purposes. Confusing them is one of the more common and consequential errors in an incident-review workflow, because each one carries its own review requirement, timeline, and consequence.
NQF Serious Reportable Event vs. Joint Commission Sentinel Event
A sentinel event is The Joint Commission’s accreditation-driven term: a patient-safety event that reaches a patient and results in death, permanent harm, or severe temporary harm, triggering a mandated review under TJC’s Sentinel Event Policy regardless of self-reporting choice. The two lists overlap heavily but are not the same instrument — the NQF list is a fixed enumeration of specific occurrences, while TJC’s sentinel-event definition is an outcome-severity threshold that can be met by events that never appear on the NQF list at all. CASRAI’s Sentinel Event guide covers TJC’s definition, the RCA/action-plan timeline, and this exact vocabulary distinction in full — this guide doesn’t repeat that ground, but the short version: most NQF SREs will also qualify as TJC sentinel events, but “on the SRE list” and “meets the sentinel-event severity threshold” are two different tests, and a program should run both, not assume one implies the other.
NQF Serious Reportable Event vs. CMS Hospital-Acquired Condition (HAC)
CMS runs two separate mechanisms that get shorthanded as “HACs,” and neither one is the NQF SRE list, though there’s real overlap in subject matter:
- The original HAC payment provision (Deficit Reduction Act of 2005, §5001(c)) strips a diagnosis on CMS’s own designated HAC list of its ability to raise a claim to a higher-paying DRG when it’s coded “not present on admission.” This runs entirely off the Present on Admission (POA) indicator on the claim — see CASRAI’s POA Indicator guide for the Y/N/U/W coding mechanics. It is a claim-level payment rule, not a reporting obligation.
- The separate, ACA-created Hospital-Acquired Condition Reduction Program (HACRP) combines AHRQ’s PSI 90 composite with NHSN infection ratios into a Total HAC Score and applies a 1% total Medicare payment cut to the worst-performing quartile of hospitals annually — see CASRAI’s AHRQ Patient Safety Indicators guide for how PSI 90 is built and how it feeds this program.
Some NQF SREs (a retained surgical item, for instance) sit on CMS’s HAC list and can also surface through a PSI flag; many do not, because CMS’s HAC list and NQF’s SRE list were built for different purposes (payment integrity vs. public-accountability reporting) by different processes, and were never designed to match line for line. Treat “is this a never event,” “is this a CMS HAC,” and “does this trigger our state’s reporting statute” as three separate questions with three separate answers, not one question asked three ways.
State Mandatory Reporting: What Actually Varies
This is the piece with the most direct operational consequence, and the piece most often assumed rather than checked. There is no single federal reporting mandate that attaches to the NQF SRE list itself — NQF publishes the list as a voluntary consensus framework. Mandatory reporting comes from state law, and state programs vary substantially in scope and mechanism. As of a widely cited 2019 count, roughly a quarter of U.S. states had reporting laws specifically framed around “never events,” and a further set of states required reporting of the broader category of serious adverse events (which encompasses never events without being limited to the NQF list) — putting some form of mandatory event reporting in place in roughly half of U.S. states, with meaningful variation in the rest.
What varies from state to state, concretely:
- The triggering list itself — some states adopt the NQF SRE list directly by reference; others maintain their own state-specific reportable-event list that overlaps with, but doesn’t exactly match, NQF’s 29 events.
- What happens after a report is filed — reporting-only in some states; in others, the state also requires a formal root cause analysis and submission of its findings. Minnesota is a commonly cited example of a state that mandates both the report and the RCA.
- Public disclosure — some state programs publish aggregate or facility-level reportable-event data; others keep reports confidential to the state health department.
- Enforcement mechanism — ranging from licensure-linked consequences to no independent penalty beyond the reporting duty itself.
The practical implication for a patient-safety program: the NQF list is the right reference for understanding what kind of event the field is generally talking about, but it is not a substitute for reading your own state’s actual reportable-event statute or regulation. A program that reports “because it’s a never event” without checking whether the state’s list, timeline, and RCA requirement actually match what happened is operating on an assumption, not a verified obligation — confirm the current requirement with your state health department or state hospital association before finalizing a reporting policy, since state lists are revised independently of NQF’s own update cycle.
Operational Checklist: Sorting an Event Against All Four Frameworks
Because a single incident can trigger obligations under more than one framework simultaneously, a practical workflow keeps them as separate checkboxes rather than one combined judgment call:
- Does it match an NQF SRE category? Use the seven-category table above as the first sort — it’s the fastest way to recognize the general shape of the event even before every detail is confirmed.
- Does it meet TJC’s sentinel-event severity threshold? Independently of the SRE check — an event can meet this threshold without being on the NQF list, and vice versa. See the Sentinel Event guide linked above for the full definition and RCA timeline.
- Does it touch CMS’s HAC list or a PSI-flagged condition? This determines whether there’s a payment-integrity thread (POA coding, PSI validation) running alongside the safety-review thread, not instead of it.
- Does your state’s reportable-event statute apply, and on what timeline? Check the current state list and RCA/disclosure requirements directly — don’t infer them from the NQF list or from what a neighboring state requires.
Documenting the answer to all four, even when three come back “no,” is what makes an event file defensible later — a reviewer (internal or external) should be able to see that each framework was actually checked, not assumed.
Frequently Asked Questions
Is “never event” an official NQF term?
No. NQF’s official term is “Serious Reportable Event.” “Never event” is an older, informal label that predates NQF’s current list and is commonly (if loosely) applied to it — useful in conversation, not precise enough to cite in a policy document or reporting justification.
Is every never event also a Joint Commission sentinel event?
Not automatically. Most NQF SREs will meet TJC’s sentinel-event severity threshold, but the two are defined by different tests — a fixed enumerated list versus an outcome-severity threshold — so a program should check both rather than assuming one implies the other.
Does every state require reporting of NQF’s Serious Reportable Events specifically?
No. Roughly half of states have some form of mandatory event-reporting law, and among those, some reference the NQF list directly while others use their own state-defined list of reportable events. Check your specific state’s statute rather than assuming NQF’s list is what applies.
Is a retained surgical item automatically a CMS Hospital-Acquired Condition?
Retained surgical items sit on CMS’s HAC list, so a coded, present-on-admission-negative case can trigger the DRA 2005 payment provision, but “on the NQF SRE list” and “on CMS’s HAC list” are governed by separate processes maintained by separate bodies — confirm HAC-list membership against CMS’s current published list rather than assuming SRE-list membership carries over automatically.
Related CASRAI Resources
For the accreditation-side review process once an event clears TJC’s severity threshold, see Sentinel Event: What It Means, and What Happens Next. For the payment mechanics NQF SREs frequently intersect with, see Present on Admission (POA) Indicator and AHRQ Patient Safety Indicators Explained. For the wider cluster, visit the Patient Safety & Infection Prevention pillar.
