Patient Safety and Risk Management
Patient Safety and Risk Management
This domain tests whether you can recognize, report, and reduce preventable harm across the care episode: falls, pressure injuries, medication events, device-related complications, and diagnostic delays. The exam favors system thinking over blame and asks you to distinguish a near miss, an adverse event, and a sentinel event.
Core rules
- Safety is a system property: staffing, workflow, equipment, and communication shape error rates; individual blame suppresses reporting.
- Report every event and near miss through the approved channel; reporting is not the same as disclosure to the patient.
- Use validated risk tools (for example Morse Fall Scale, Braden Scale) to trigger interventions, then reassess when condition changes.
- Root cause analysis (RCA) examines a sentinel event after it happens; failure mode and effects analysis (FMEA) predicts risk before a process goes live.
- Just culture separates human error (console), at-risk behavior (coach), and reckless behavior (sanction).
- Disclose harmful events promptly, factually, and with empathy under organizational policy.
Worked example
A postoperative patient on opioids and a diuretic is admitted at 22:00. The nurse documents a Morse score of 55 but does not apply bed brakes or hourly rounding. At 03:00 the patient falls while walking to the bathroom. The correct response is: assess for injury (head, hip, neuro status), vital signs and glucose, notify the provider, complete an incident report, and escalate for a post-fall huddle. The system fix is not retrain the nurse alone; it is verifying that risk scores automatically trigger bed alarms, non-skid footwear, and toileting rounds.
Traps
- Treating incident reports as punitive evidence rather than safety data.
- Completing a fall risk score once on admission and never updating it.
- Saying no harm, no report-near misses are reportable.
- Confusing RCA with FMEA or using both interchangeably.