Sentinel Event: What It Means, and What Happens Next

“Sentinel event” is a Joint Commission accreditation term, not a generic phrase for “bad outcome.” If you landed here looking for the FDA’s Sentinel Initiative (the post-market drug-safety surveillance system) or the cybersecurity vendor SentinelOne, this is a different topic. This page covers the accreditation meaning: the category of patient-safety event that triggers a mandated review process under The Joint Commission’s Sentinel Event Policy, and what an accredited organization must actually do once one occurs.

Page checked against The Joint Commission’s published Sentinel Event Policy in August 2026. The policy is revised periodically — treat the definition and timeframe below as current as of that check, and verify against the current Sentinel Event (SE) chapter of your organization’s applicable accreditation manual before relying on it for a live case, since specific inclusion/exclusion criteria are enumerated there in more detail than a summary page can responsibly reproduce.

What Makes an Event “Sentinel”

Under the Joint Commission’s Sentinel Event Policy, a sentinel event is a patient safety event — not primarily related to the natural course of the patient’s illness or underlying condition — that reaches a patient and results in death, permanent harm, or severe temporary harm. The word “sentinel” signals that the event warrants immediate investigation and response regardless of how it was discovered, because it points to a serious weakness in a process or system rather than an isolated, unavoidable complication.

Two things distinguish this from an everyday adverse-event definition. First, “sentinel” is deliberately narrower than “harm” in general — it is reserved for the most serious outcomes, not every complication or every deviation from expected care. Second, the policy separates the definition of a sentinel event from an organization’s reporting choice: accredited organizations are expected to conduct a full review of every event that meets the definition, whether or not they choose to self-report it to The Joint Commission.

Sentinel Event vs. Never Event vs. Adverse Event — Three Different Vocabularies

These three terms come from three different bodies and get used interchangeably in casual conversation, which causes real confusion in incident-reporting and risk-management workflows. They are not synonyms.

• Sentinel event — a Joint Commission accreditation term. Defined by outcome severity (death, permanent harm, severe temporary harm) as described above, and tied to a specific accreditation-driven review requirement.
• Never event — a term originating with the National Quality Forum’s list of Serious Reportable Events: a defined, enumerated list of specific occurrences (for example, surgery on the wrong body part, or a foreign object retained after surgery) that are considered largely preventable and are not expected to occur if available safeguards are followed. CMS uses a version of this concept for non-payment policy. A never event is usually also a sentinel event, but the two lists are not identical — the never-event list is a fixed enumeration of specific occurrences, while the sentinel-event definition is an outcome-severity threshold that can be met by events not on the never-event list.
• Adverse event — the broadest of the three, and not a term of art tied to a single body. It generally means any injury to a patient caused by medical management (as opposed to the underlying condition), regardless of severity or preventability. Every sentinel event is an adverse event; most adverse events are not sentinel events.

For a patient-safety officer, the practical consequence is that these three classifications trigger different downstream obligations — accreditation review, payment/reporting consequences, and general quality tracking, respectively — and a single case can carry more than one label at once.

What Happens After a Sentinel Event: The Required Review

Once an event meets the sentinel-event definition, the accredited organization is expected to conduct what the Joint Commission calls a comprehensive systematic analysis — the formal root-cause-analysis process most patient-safety staff know by the RCA (or RCA²) name — regardless of whether the event is ever reported to The Joint Commission. The analysis is meant to look past the individual clinician involved and identify the underlying system factors — communication breakdowns, staffing and workflow gaps, equipment issues, training deficiencies — that allowed the event to occur.

Self-reporting a sentinel event to The Joint Commission is strongly encouraged but not mandatory. Organizations that do self-report, or whose sentinel event becomes known to The Joint Commission by another route (a complaint, a media report, a state agency referral, or an on-site survey), are expected to submit a thorough comprehensive systematic analysis and corrective action plan within a defined window — reported as 45 business days of the event, or of the organization becoming aware of it, under current policy. Because this figure is exactly the kind of detail that changes between policy revisions, confirm it against the current Sentinel Event Policy chapter before citing it in a submission to The Joint Commission. Failure to complete an acceptable analysis and action plan within the required window can affect the organization’s accreditation status.

A separate and important point: state law frequently layers its own mandatory serious-event or “never event” reporting obligation to a state health department on top of — and independent of — the Joint Commission review. A sentinel event that triggers the accreditation-driven RCA requirement may also trigger a completely separate state reporting deadline with its own timeline and recipient. Track both; meeting one does not satisfy the other.

Building the Corrective Action Plan

A comprehensive systematic analysis that will satisfy accreditation review typically includes: a clear timeline of the event as it actually unfolded; identification of the proximate and underlying (system-level) contributing factors, not just the point of error; causal statements that connect each contributing factor to a specific, actionable improvement rather than a vague finding; and a corrective action plan with a named owner, an implementation date, and — critically — a defined measure of effectiveness so the organization can show the fix actually worked, not just that it was implemented. Analyses that stop at “retrain the staff involved” without addressing the system-level factor are a recurring reason organizations are asked to revise and resubmit.

Where This Intersects With Patient Safety Organization Reporting

A sentinel event review is frequently also relevant material for reporting through a federally listed Patient Safety Organization (PSO), which can extend a separate federal confidentiality and privilege protection to the analysis if it is properly created within the organization’s patient safety evaluation system. That protection is real but bounded, and routing a sentinel-event analysis through a PSO does not change the Joint Commission’s own review and timeline requirements — the two processes serve different purposes and run on separate tracks.

Frequently Asked Questions

Is reporting a sentinel event to The Joint Commission mandatory?

No. Self-reporting is strongly encouraged but voluntary. What is not optional is conducting the comprehensive systematic analysis internally once an event meets the definition — that expectation applies whether or not the event is ever reported to The Joint Commission.

Is a “close call” or near miss a sentinel event?

No. The sentinel-event definition requires that the event actually reach a patient and result in death, permanent harm, or severe temporary harm. A near miss that was caught before reaching the patient is valuable safety data and worth tracking through your internal event-reporting system, but it does not meet the sentinel-event threshold.

Does a sentinel event automatically mean malpractice occurred?

No. Sentinel event status is an accreditation classification based on outcome severity, not a legal or clinical determination of negligence. Many sentinel events result from system failures with no individual negligence involved, which is the entire premise behind the RCA process’s focus on systems rather than blame.

Do accreditors other than The Joint Commission use the same definition?

“Sentinel event” specifically is a Joint Commission term of art. Other CMS-recognized accrediting organizations (such as DNV or HFAP) maintain their own serious-event review requirements, which cover similar ground but are not guaranteed to use identical definitions or timeframes — check the specific accreditor’s standards if your organization is not Joint Commission-accredited.

See the Patient Safety & Infection Prevention hub for related coverage of accreditation-driven patient safety programs, including National Patient Safety Goals and morbidity and mortality conference structure.