Skills on AI

Active theme: Light

Medical Clinical Incident Report

Use when asked to file, structure, or review a clinical incident report — the factual account filed when a patient-safety incident or near-harm event occurs — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.

⚠️ Ask your doctor or health care professional. This information is AI generated for education and NOT medical advice.

A clinical incident report is the initial, factual record filed when a patient-safety incident, near-harm event, or unexpected occurrence happens during care. It captures what happened while details are still fresh, and it's the trigger point that determines whether an event gets escalated for deeper investigation.

Key components

  • Factual, timely account — a clear description of what happened: who was involved, what occurred, when and where, and what actions were taken immediately afterward. Filed as close to the event as possible, ideally before the end of the same shift.
  • Facts kept separate from speculation — what actually happened is recorded distinctly from any theory about why it happened. Cause analysis is the job of a later review, not the initial report.
  • Consistent severity classification — the event is graded against a defined severity scale (for example, near-miss, no harm, low harm, moderate harm, severe harm, death) so that genuinely serious events are reliably flagged for escalation rather than left to individual judgment.
  • Immediate actions taken — what was done at the time to protect the patient and stabilize the situation, distinct from any longer-term corrective action that a subsequent review might recommend.

Why prompt filing matters

Memory of a fast-moving clinical event degrades quickly. The precise sequence, timing, and who-said-what details that make a report useful for later analysis blur within hours and are often unreliable within a day or two. A report filed the same shift, while the sequence is still fresh, is measurably more reliable than one filed days later from recollection — and a delayed report also delays whatever escalation the severity of the event actually warrants.

How it differs from a postmortem and a review

  • vs. Postmortem — a postmortem is the technology-systems practice of analyzing an IT incident after the fact. A clinical incident report is its patient-safety equivalent, but it is filed immediately as a factual capture, not as the deeper after-action analysis a postmortem represents.
  • vs. Medical Adverse Event Review — the incident report is the initial factual capture: what happened, filed promptly. The adverse event review is the deeper investigation that may follow, focused on identifying contributing systemic factors and corrective actions.

Common pitfalls

  • Filing delayed until well after the event — waiting days (or until "there's time") degrades the accuracy of the sequence and details captured, and undermines the whole point of a timely record.
  • Speculation or blame mixed into the factual account — writing "the nurse failed to check the chart" instead of "the chart was not checked before administration" turns a factual report into an accusation before any investigation has happened.
  • Severity under-classified — grading a genuinely serious event as low-harm or a near-miss, whether from haste or reluctance to escalate, means it doesn't get the review and attention it actually needs.
  • Report treated as the end of the process — filing the report and never following up on whether it triggered the appropriate review wastes the information it captured.
  • Only actual-harm events reported — near-misses and no-harm events are still worth a report; see Medical Medication Error Reporting for why near-miss data is often the richest source of prevention insight.

Learn more

View medical-clinical-incident-report/SKILL.md on GitHub