Never Events in 2027: How the Joint Commission and NQF Lists Are Merging

On 26 January 2026, the Joint Commission and the National Quality Forum announced they're finally merging two safety-event lists that healthcare organisations have had to track separately for over a decade. From 1 January 2027, Joint Commission Sentinel Events and NQF Serious Reportable Events (SREs) — commonly known as "never events" — become a single, unified list. For any hospital or care organisation still running two parallel coding systems, the countdown to a genuinely simpler, and more demanding, reporting framework has started.

What a "never event" actually is

CMS defines never events as preventable medical errors that result in serious consequences for the patient — errors that are clearly identifiable, preventable, and serious enough that, in CMS's own words, they simply should never happen. Since an Inpatient Prospective Payment System rule effective 1 October 2008, Medicare has refused to pay the additional hospitalisation costs created by certain hospital-acquired conditions that weren't present on admission, covering surgical never events like wrong-body-part surgery, wrong-patient surgery, and incorrect procedures. A 2009 expansion added several more non-payment categories, including surgical site infections after select elective orthopedic and bariatric procedures, serious blood-sugar-control complications, and DVT or pulmonary embolism following knee or hip replacement.

The 2027 change: one list instead of two

Until now, an organisation tracking safety events has effectively had to run two coding systems in parallel: the Joint Commission's Sentinel Event framework and NQF's Serious Reportable Events list. The new unified taxonomy consolidates both into a single list of 28 SREs across four categories:

• Procedural Events — 7 SREs
• Product or Device Events — 4 SREs
• Patient Protection Events — 5 SREs
• Care Provision Events — 12 SREs

Fifteen of these become new, explicitly named categories that organisations must track individually for the first time — previously, these incidents may have met the broader sentinel-event definition without being called out as their own reportable category. The point of the merger isn't just administrative tidiness: running two overlapping taxonomies has made reliable cross-organisation benchmarking nearly impossible, and a unified framework is meant to enable standardised signal detection and safety-data comparisons that actually mean the same thing from one hospital to the next.

What hospitals need to do before January 2027

The transition isn't a single cutover date — it's a phased process that, if organisations follow the pattern being recommended across the sector, looks roughly like this:

• First half of 2026: designate an internal alignment owner, obtain the official Joint Commission materials, and brief leadership on what's changing.
• Mid-to-late 2026: map existing policies and incident-report forms to the new 28-SRE taxonomy, coordinate with incident-reporting system vendors, and plan staff education.
• Final quarter of 2026: validate the new coding by running it in parallel with the current system against 50–100 recent cases, while preserving historical trend data for comparison.
• January 2027: go live on the unified list, with close monitoring through the first quarter to catch mapping errors early.

Grievance workflows need the same attention as clinical incident reporting — policy language and categorisation frameworks that reference the old sentinel-event or SRE terminology will need updating in step with the new list, not as an afterthought once the clinical side is done.

Where this connects to documentation and survey readiness

A never event doesn't stay contained to an internal incident report. Depending on severity and scope, it can trigger the same CMS survey and Plan of Correction process covered elsewhere on this site — and the quality of the underlying documentation is exactly what determines whether a corrective response holds up. The same discipline covered in Learnsignal's incident investigation and documentation standards piece applies directly here: a never event miscoded under the old taxonomy, or documented inconsistently against whichever list happens to be live at the time, is a weaker record at exactly the moment scrutiny is highest.

Building never-event prevention into ongoing practice

• Don't wait for January 2027 to start mapping. The recommended timeline front-loads the mapping and validation work into 2026 specifically so the go-live isn't the first time staff see the new categories.
• Treat the 15 newly explicit categories as a prompt to review current practice, not just a coding update — if an event type is being named individually for the first time, it's worth asking whether current prevention protocols already address it adequately.
• Keep historical data comparable. Preserving trend data across the transition is what lets an organisation tell whether a change in reported never events reflects an actual safety shift or just the new taxonomy counting things differently.
• Treat this as a cross-functional project, not a quality-department-only task — risk management, compliance, IT/vendor coordination, and frontline staff education all have a role in a clean 2027 transition.

Frequently asked questions

Is the unified 28-SRE list already in effect?
No. The alignment was announced 26 January 2026, with the Joint Commission adopting the updated list from 1 January 2027 — organisations have a defined runway to prepare, not an immediate requirement.

Does this change what Medicare will and won't pay for?
The unified list changes how events are categorised and tracked, but the underlying CMS non-payment policy for hospital-acquired conditions not present on admission, dating to 2008 and 2009 rules, is a separate, already-established framework.

How many of the 28 SREs are genuinely new categories?
Fifteen become new explicit categories under the unified list; the rest consolidate events that were already tracked under one framework or the other.

Getting ahead of the 2027 transition is a documentation and process question as much as a clinical one. Learnsignal's CPD training library covers patient safety reporting, incident documentation, and survey readiness for healthcare organisations navigating CMS and Joint Commission requirements.