⚡ Promptolis Original · Healthcare & Medical

🚨 Patient Safety Incident Investigation — Root Cause Analysis + System Fix

The structured patient safety investigation covering the RCA (Root Cause Analysis) methodology, the just-culture framework distinguishing system failures from individual errors, 5-Whys technique, and the prevention-focused approach that drives learning vs. blame.

⏱️ Ongoing after incidents 🤖 ~2 min in Claude 🗓️ Updated 2026-04-20

Why this is epic

Patient safety incidents reveal system failures + require structured investigation. This Original produces RCA + just culture framework + system fixes preventing recurrence.

Names 5 investigation failures (blame-focused, incomplete, single-cause assumption, no systems thinking, no follow-through).

Produces complete framework. Just-culture principles.

The prompt

Promptolis Original · Copy-ready
<role> You are a patient safety + quality improvement specialist with 12 years of experience. You've led 100+ incident investigations. You draw on Joint Commission, IHI, AHRQ patient safety frameworks, just culture principles. </role> <principles> 1. System failures > individual errors. 2. 5-Whys to root causes. 3. Timeline reconstruction objective. 4. Just culture framework. 5. Multiple causes expected. 6. Follow-through critical. 7. Share learnings. 8. Measure prevention. </principles> <input> <incident-type>{medication error, fall, wrong-site, etc}</incident-type> <severity>{near miss, harm, sentinel}</severity> <timeline>{what happened when}</timeline> <people-involved>{roles, not names}</people-involved> <immediate-actions>{what was done}</immediate-actions> <current-investigation}>{what's been done so far}</current-investigation> <institutional-context>{culture, resources}</institutional-context> <goal>{formal RCA, informal review}</goal> </input> <output-format> # Incident Investigation: [Type + severity] ## Immediate Response ## Timeline Reconstruction ## Root Cause Analysis (5-Whys + Fishbone) ## Just Culture Assessment ## Contributing Factors ## System Fixes ## Follow-Through Plan ## Learning Dissemination ## Key Takeaways 5 bullets. </output-format> <auto-intake> If input incomplete: ask for incident type, severity, timeline, people, actions, investigation status, context, goal. </auto-intake> Now, investigate:

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
<incident-type>Medication error — patient received wrong dose of insulin (40 units instead of 4 units), resulted in severe hypoglycemia requiring D50 + glucose monitoring.</incident-type>
<severity>Harm (patient recovered but required intervention + extended stay).</severity>
<timeline>Admitted 48 hrs prior for DKA. Order written correctly for 4 units Humulin R IV. Nurse administered 40 units. Error discovered 30 min later when glucose dropped to 35. Rescued with D50. Patient stabilized over next 4 hrs.</timeline>
<people-involved>MD ordering (intern), pharmacy (verified order), RN administering, charge RN.</people-involved>
<immediate-actions>Patient treated + stabilized. Incident report filed. Staff pulled from patient care pending review.</immediate-actions>
<current-investigation>Incident report filed. Nursing leadership has reviewed. Formal RCA not yet initiated.</current-investigation>
<institutional-context>Academic medical center. Formal RCA process exists. Just culture stated as value but practice inconsistent.</institutional-context>
<goal>Formal RCA to identify system failures + prevent recurrence.</goal>
🤖 Output

Incident Investigation: 10x Insulin Dose Error, Harm Resulting, Formal RCA

A patient safety incident investigation produces systematic root cause analysis + prevention framework. Your situation — medication error with patient harm — warrants formal RCA. This framework: timeline + 5-Whys + just culture + system fixes.

Immediate Response (Completed + Next Steps)

Already Done:
  • Patient treatment + stabilization
  • Incident report filed
  • Staff pulled from patient care
Next Steps Within 24 Hours:
  • Patient + family disclosure (transparent, compassionate)
  • Risk management notified
  • Leadership informed
  • Resources arranged for involved staff (EAP, peer support)
Within 48 Hours:
  • Preliminary interview with involved staff (supportive, not accusatory)
  • Document secure preservation
  • Medications + equipment secured as evidence

Timeline Reconstruction (Objective)

Factual timeline (from records + interviews):

TimeEvent
Admission -48hPatient admitted for DKA
H-2:00Intern MD orders 'Humulin R 4 units IV'
H-1:30Pharmacy verifies order
H-1:15Order transmitted to medication administration system
H-0:30RN accesses Pyxis, retrieves insulin vial
H-0:15RN draws up medication
H-0:10RN administers to patient
HCheck glucose at 30 min post-administration
H+0:30Glucose 35 mg/dL noted — severe hypoglycemia
H+0:35D50 administered + rapid response called
H+0:45Patient stabilizing
H+4:00Patient fully recovered + continued hospital course

Key moment of error: between order + administration. Something caused 4 units → 40 units.

Root Cause Analysis (5-Whys + Fishbone)

5-Whys Analysis

Problem: patient received 40 units insulin instead of 4 units.

Why 1: Why did RN administer 40 units?

Answer 1: RN calculated dose as '40 units' when reading '4 units' from syringe labeling.

Why 2: Why did RN calculate 40 units?

Answer 2: Confusing vial labeling + time pressure led to misreading.

Why 3: Why was vial labeling confusing?

Answer 3: Insulin concentration labeling inconsistent — some 100 units/mL, some 500 units/mL. Institution has both.

Why 4: Why do we have two concentrations?

Answer 4: Legacy workflow — high-dose insulin cases used concentrated insulin. But safety protocols not updated.

Why 5: Why weren't safety protocols updated?

Answer 5: No systematic review of medication safety controls when products introduced.

Multiple 5-whys paths often needed. Other branches:

Why didn't pharmacy catch it?
  • Pharmacy verified order, not dose math
  • Automation limitations
  • No independent check on dose math
Why didn't independent nurse check catch it?
  • Second nurse check required for insulin
  • Happened, but not for dose calculation verification
  • Second nurse confirmed vial identity only
Why did intern MD write ambiguous order?
  • Order was correct as written ('4 units')
  • Error occurred downstream
Fishbone Diagram Categories

Methods/Procedures:

  • Inconsistent insulin concentration inventory
  • Second nurse check protocol inadequate
  • Independent dose verification missing

People:

  • RN training on concentrated insulin may be inadequate
  • Communication breakdown in verification

Equipment/Systems:

  • Pyxis dispensing same-looking vials
  • EHR not flagging concentration differences

Environment:

  • Time pressure
  • Shift change potentially
  • Distractions

Materials:

  • Similar-looking insulin vials (100 vs. 500 units/mL)
  • Labeling not distinct

Just Culture Assessment

Three behavior categories:

Human Error (systemic issues)

Definition: inadvertent slip in attention, mental model mismatch

Assessment of RN:

  • Misread vial during dose preparation
  • System-enabled error (confusing labels, inadequate safeguards)
  • Not reckless
  • Would likely happen to another competent RN in same situation

Classification: Human error enabled by system failures.

At-Risk Behavior

Definition: choice taking shortcuts despite known risk

Not clearly present here. No evidence RN knowingly bypassed safety checks.

Reckless Behavior

Definition: conscious disregard of substantial risk

Not present. No evidence of disregard.

Just Culture Response

For human error (this case):

  • Console + support
  • Focus on system fix
  • No punitive action for RN
  • Learning opportunity

For at-risk behavior:

  • Coach + educate
  • Understand motivations
  • Address gaps

For reckless behavior:

  • Discipline appropriate
  • But not this case

Staff wellbeing:

  • RN likely traumatized
  • EAP + peer support
  • Protected time off if needed
  • Return-to-work support

Contributing Factors

Primary (System-Level):

1. Dual insulin concentrations in inventory — enabled mix-up

2. Insufficient labeling differentiation — similar vials

3. Second-check protocol gaps — verified vial identity but not dose math

4. EHR not flagging concentration — missed safety opportunity

5. Pyxis dispensing confusion — similar storage

Secondary (Process-Level):

6. Time pressure during shift — busy unit

7. Training on concentrated insulin — may have been inadequate

8. High-risk medication protocols — insulin should have extra safeguards

Tertiary (Patient-Level):

9. Complex patient — DKA management + insulin titration

10. Multiple care providers — handoff points

System Fixes

Priority 1: Single Insulin Concentration

Action: standardize to 100 units/mL only (or 500 with separate storage).

Rationale: eliminates confusion.

Implementation:

  • Phase out 500 units/mL from routine inventory
  • Dedicated storage for 500 units/mL (if kept)
  • Update pharmacy formulary
  • Staff communication

Timeline: 60-90 days.

Priority 2: Enhanced Labeling + Dispensing

Action: distinct labeling + Pyxis dispensing safeguards.

Implementation:

  • High-visibility warning labels on concentrated insulin
  • Pyxis requires special authorization for concentrated
  • EHR alerts for concentration differences

Timeline: 30-60 days.

Priority 3: Strengthened Second Check

Action: insulin administration requires full dose verification (not just vial check).

Implementation:

  • Two RN verification: dose math + vial + patient
  • Clinical decision support for dose ranges
  • Insulin administration checklist

Timeline: 30 days.

Priority 4: EHR Decision Support

Action: dose-range checking + concentration warnings.

Implementation:

  • Alerts for doses outside expected range
  • Concentration confirmation at order entry
  • Dose verification at medication administration

Timeline: 90 days (IT development).

Priority 5: Training + Competency

Action: insulin-specific training + competency validation.

Implementation:

  • Annual insulin administration competency
  • Scenario-based training
  • Regular audits

Timeline: ongoing.

Priority 6: Near-Miss Tracking

Action: track + review insulin-related near misses systematically.

Implementation:

  • Improve reporting culture
  • Review monthly
  • Trend analysis

Timeline: immediate start.

Follow-Through Plan

30-Day Actions
  • Investigation report completed
  • Leadership review + approval
  • Patient + family follow-up
  • Staff debrief + support
  • Immediate safety actions implemented
60-Day Actions
  • System fixes implemented (high-priority)
  • Pharmacy inventory changes
  • Training materials updated
  • Staff competency assessments
90-Day Actions
  • EHR changes deployed
  • Full policy revisions
  • Quality monitoring baseline
6-Month Actions
  • Effectiveness evaluation
  • Trending insulin-related events
  • Policy compliance audit
  • Sustainability check
12-Month Actions
  • Formal review of fix effectiveness
  • Continued monitoring
  • Share learnings organization-wide

Learning Dissemination

Internal

Immediate (within 2 weeks):

  • Leadership briefing
  • Affected units briefed (de-identified)
  • Quality committee review

Monthly:

  • Safety bulletin to clinical staff
  • QI dashboard updates
  • Team huddles reference incident (de-identified)

Quarterly:

  • Organization-wide patient safety report
  • Systemic learnings shared
  • Prevention strategies highlighted
External

Regulatory:

  • Report to state if required
  • Joint Commission if sentinel event
  • FDA MedWatch if drug-related

Professional:

  • Conference presentation (de-identified)
  • Publication in patient safety journal
  • Share with peer institutions

Transparency:

  • Institutional patient safety reports
  • Quality dashboards
  • Patient + family engagement

Key Takeaways

  • Root causes: system failures (dual insulin concentrations, inadequate labeling, gaps in second-check process, EHR not flagging). Not individual RN error. Just culture response.
  • 6 system fixes prioritized: (1) single insulin concentration, (2) enhanced labeling, (3) strengthened second check, (4) EHR decision support, (5) training, (6) near-miss tracking. Implementation timeline 30-90 days.
  • Just culture assessment: human error enabled by system failures. Not at-risk or reckless. Staff support + system fixes focus. No punitive action against RN.
  • Follow-through essential. 30/60/90 day milestones + 6-month + 12-month effectiveness evaluation. Recommendations without implementation = waste.
  • Learning dissemination internal + external. De-identified sharing prevents recurrence at peer institutions. Regulatory reporting per requirements. Transparency builds trust.

Common use cases

  • After patient safety events
  • Quality improvement teams
  • Hospital incident command
  • Risk management
  • Medical error investigations

Best AI model for this

Claude Opus 4 or Sonnet 4.5. Incident investigation requires systems + quality + ethics. Top-tier reasoning matters.

Pro tips

  • System failures > individual errors (80/20 rule).
  • 5-Whys technique drills to root causes.
  • Timeline reconstruction objective + detailed.
  • Just culture: distinguish human error, at-risk behavior, reckless behavior.
  • Multiple causes typical — not single root cause.
  • Follow-through on recommendations critical.
  • Share learnings (de-identified) across organization.
  • Measure prevention effectiveness.

Customization tips

  • Engage involved staff as partners in investigation, not targets. Better data + appropriate resolution.
  • Follow-through on recommendations is the challenge. Quality dashboard for accountability.
  • Share de-identified learnings widely. Peer institutions benefit + trust builds.
  • Near-miss investigation equally valuable. Don't wait for harm to learn.
  • Annual RCA skills training. Patient safety muscle atrophies without practice.

Variants

Sentinel Event RCA

Serious events requiring formal RCA.

Near Miss Review

Near misses as learning opportunities.

Process Failure

System breakdowns.

Medication Error

Specific medication incidents.

Frequently asked questions

How do I use the Patient Safety Incident Investigation — Root Cause Analysis + System Fix prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Patient Safety Incident Investigation — Root Cause Analysis + System Fix?

Claude Opus 4 or Sonnet 4.5. Incident investigation requires systems + quality + ethics. Top-tier reasoning matters.

Can I customize the Patient Safety Incident Investigation — Root Cause Analysis + System Fix prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: System failures > individual errors (80/20 rule).; 5-Whys technique drills to root causes.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals