CPPS cheat sheet

Culture of safety definition: the product of individual and group values, attitudes, competencies, and patterns of behavior that determine commitment to, and proficiency in, health and safety management.

Three reinforcing components of a safety culture: (1) a just culture that does not punish human error but holds people accountable for reckless behavior; (2) a reporting culture that encourages reporting of errors and near misses; (3) a learning culture that analyzes and acts on reported information.

Just culture algorithm: console human error, coach at-risk behavior, punish only reckless behavior. At-risk behavior is a behavioral choice that increases risk where risk is not recognized or is mistakenly believed justified.

Psychological safety (Edmondson): a shared belief that the team is safe for interpersonal risk-taking; it is a team-level climate, distinct from individual personality and from trust in the organization.

Speak-up culture indicators: rate of employee-reported concerns, proportion of staff who feel comfortable reporting, and percentage of reports that receive visible follow-up.

Hierarchy and authority gradient: steep gradients suppress upward communication; flattening via structured tools (CUS, two-challenge rule, SBAR) increases escalation of concerns.

Culture surveys measure perceptions, not outcomes; pair survey results with behavioral/process measures (e.g., hand hygiene audits, reporting rates) to avoid perception-only conclusions.

Blame culture markers: underreporting, punitive responses to error reports, and defensive documentation; these suppress the data needed for improvement.

Senior leadership accountability: governing body sets safety goals, allocates resources, and reviews safety performance at defined intervals; leadership commitment is a precondition for sustained improvement.

Board-level safety oversight requires regular reporting of harm events, near misses, and progress on improvement plans, not just financial metrics.

Leadership walkrounds: structured, scheduled visits where leaders ask frontline staff about safety concerns and follow up on identified issues; effectiveness depends on closed-loop feedback.

Safety huddles and briefings: short, recurring team meetings used to surface risks, share learning, and assign actions; frequency and standardization predict reliability.

Just culture requires leaders to model transparency: disclosing their own errors and supporting staff after adverse events reduces defensiveness and improves reporting.

Resource decisions (staffing, equipment, training time) are leadership levers; under-resourcing is a latent condition that enables active failures.

Leadership must ensure the improvement infrastructure exists: designated patient safety officers, committees with authority, and protected time for improvement work.

Succession and sustainability: embed safety responsibilities in job descriptions and performance reviews so improvement survives leadership turnover.

Swiss cheese model (Reason): accidents occur when latent conditions (system weaknesses) and active failures (unsafe acts) align across defensive layers; barriers reduce, not eliminate, risk.

Error types: slips (attention failure on routine task), lapses (memory failure), mistakes (rule-based or knowledge-based planning failure), and violations (deliberate deviation from procedure).

High-alert medications (e.g., anticoagulants, insulin, opioids, concentrated electrolytes) require independent double-checks, standardized concentrations, and separated storage.

Medication reconciliation at transitions of care reduces adverse drug events; it requires an accurate list, comparison against current orders, and communication to the next provider.

Handoff failures are a leading contributor to harm; structured handoff tools (SBAR, I-PASS) standardize content and reduce omission of critical information.

Wrong-site surgery prevention: pre-procedure verification, site marking by the operating clinician, and a time-out with the full team present before incision.

Health care–associated infection control: hand hygiene per WHO 5 Moments, aseptic technique for invasive procedures, and device necessity review (e.g., daily catheter check).

Falls prevention bundles: risk screening on admission, multifactorial intervention (mobility aids, medication review, environment modification), and post-fall huddles.

Structure–process–outcome (Donabedian) framework: structure = resources and organization; process = what is done; outcome = results for patients. Use all three to avoid misleading conclusions.

Measure selection criteria: valid, reliable, feasible to collect, actionable, and attributable to the team being measured.

Global trigger tool: retrospective chart review using triggers (e.g., naloxone administration, unplanned return to surgery) to estimate adverse event rates that voluntary reporting misses.

Incident reporting systems capture near misses and low-harm events but are subject to underreporting; they are best used for learning, not as a true incidence measure.

Rate calculation: rate = (number of events ÷ number of patients at risk) × 100 (or per 1,000 patient-days); always state the denominator and time period.

Statistical process control: use run charts and control charts to distinguish common-cause variation from special-cause variation; a run of 6+ points on one side of the median signals a shift.

Leading indicators (e.g., hand hygiene compliance, checklist completion) predict future harm; lagging indicators (e.g., harm events) confirm outcomes already occurred.

Benchmarking requires comparable definitions, denominators, and case mix; comparing unadjusted rates across dissimilar settings can mislead.

Root cause analysis (RCA): structured retrospective method for serious adverse events; goal is to identify system vulnerabilities and fix them, not to assign individual blame.

RCA output should include causal statements, contributing factors (human, equipment, environment, organizational), and a prioritized action plan with owners and deadlines.

Fishbone (Ishikawa) diagram organizes potential causes into categories (people, process, equipment, environment, materials, management) for team brainstorming.

Five whys: iterative questioning to move from a proximate cause to underlying system causes; stop when reaching a cause the organization can act on.

Plan-Do-Study-Act (PDSA): small-scale iterative testing cycles; 'Study' compares predictions with observed results before scaling.

Failure mode and effects analysis (FMEA): prospective method that scores each failure mode by severity × occurrence × detectability (risk priority number) to prioritize prevention.

Model for Improvement: three questions (aim, measures, changes) plus PDSA cycles; aims should be specific, measurable, and time-bound.

Sustainability and spread: standardize the change, build it into workflows and training, and monitor measures after the project ends to detect regression.

Teamwork and communication competencies (TeamSTEPPS framework): leadership, situation monitoring, mutual support, and communication; each has observable behaviors.

Structured communication tools: SBAR (Situation, Background, Assessment, Recommendation) for handoffs and escalation; CUS (Concerned, Uncomfortable, Safety issue) for assertive escalation.

Closed-loop communication: sender gives message, receiver repeats back, sender confirms; reduces errors in high-tempo settings.

Patient and family engagement: shared decision-making, open disclosure after harm, and inclusion of patients on safety committees improve safety and trust.

Open disclosure elements: acknowledge the event, express regret, explain what is known, commit to investigation, and provide follow-up contact.

Interprofessional education and simulation build team competencies; debriefing after simulation or real events converts experience into learning.

Speaking up requires both individual skill (assertiveness) and system support (leaders who respond non-punitively); training alone without leadership response fails.

Second victim phenomenon: clinicians involved in adverse events experience emotional harm; peer support programs improve recovery and future reporting.

Just culture distinguishes three behaviors: human error (console), at-risk behavior (coach), and reckless behavior (remediate or discipline).

Human error is an unintended act or omission; the appropriate response is support and system redesign, not punishment.

At-risk behavior is a conscious choice where risk is underestimated or believed justified; response is coaching and removing incentives for the risky shortcut.

Reckless behavior is a conscious disregard of substantial unjustified risk; it warrants disciplinary action per policy.

Substitution test: would a similarly trained colleague in the same circumstances have acted the same way? If yes, the issue is likely system-driven.

Accountability is not the same as blame: accountability means owning behavior and participating in improvement; blame assigns fault without learning.

Reporting systems should separate learning data from disciplinary data to preserve trust and reporting volume.

Leaders must apply the algorithm consistently; inconsistent responses to similar events destroy credibility and suppress reporting.

Human factors engineering designs tasks, tools, and environments to match human capabilities and limits; it treats error as a system property, not a personal failing.

Cognitive load and working memory limits (about 4–7 chunks) mean checklists, standardization, and forcing functions reduce reliance on memory.

Forcing functions make an error impossible or immediately visible (e.g., incompatible connectors, locked cabinets for high-alert drugs).

Standardization reduces variation and error; examples include standardized concentrations, order sets, and color-coded equipment.

Interruptions and multitasking increase error rates; design workflows to protect critical tasks (e.g., no-interruption zones for medication preparation).

Fatigue and staffing levels are latent conditions; scheduling and workload management are safety interventions, not administrative conveniences.

Usability testing of devices and health IT with real users identifies use errors before deployment; workarounds signal design failure.

Alarm fatigue: excessive alarms desensitize staff; interventions include alarm rationalization, delayed thresholds, and role-based notification.

Accreditation standards require documented safety programs, incident reporting, RCA for sentinel events, and evidence of leadership oversight.

Sentinel event: an unexpected occurrence involving death or serious physical or psychological injury, or the risk thereof; requires immediate investigation and response.

National Patient Safety Goals (e.g., patient identification, communication, medication safety, infection prevention) are specific, measurable requirements updated periodically.

Patient identification: use at least two identifiers (name and date of birth or medical record number); never use room number or bed as an identifier.

Regulatory reporting requirements vary by jurisdiction; organizations must know which events are mandatory-reportable and within what timeframe.

Governing body fiduciary duty includes safety performance; boards should receive regular dashboards of harm and improvement progress.

Policy and procedure management: version control, staff attestation, and periodic review keep practices aligned with current evidence.

Confidentiality protections for safety work (e.g., peer review protections) vary by jurisdiction and affect how incident data can be used and shared.

Model for Improvement: (1) What are we trying to accomplish? (2) How will we know that a change is an improvement? (3) What changes can we make that will result in improvement?

PDSA cycle steps: Plan (predict and plan the test), Do (run the test and document), Study (compare results to prediction), Act (adopt, adapt, or abandon).

Aim statements should specify the population, the measure, the baseline, the target, and the timeframe.

Run charts: plot a measure over time with a median line; look for shifts (6+ consecutive points on one side), trends (5+ increasing/decreasing), and too few or too many runs.

Control charts add statistical limits (e.g., ±3 sigma) to distinguish common-cause from special-cause variation; special cause warrants investigation of the process change.

Pareto principle: a small number of causes account for most of the effect; rank causes to focus improvement effort.

Process mapping (flowchart) reveals steps, handoffs, and delays; value stream mapping identifies non-value-added steps.

Small tests of change reduce risk: test on one unit or one day before scaling; document what was learned at each cycle.

Proactive risk assessment methods (FMEA, hazard analysis) identify failure modes before harm occurs; reactive methods (RCA) follow events.

FMEA risk priority number = severity × occurrence × detectability; higher scores indicate priority for redesign.

Hazard identification sources: incident reports, near misses, claims data, staff concerns, direct observation, and trigger tools.

Failure mode: the manner in which a process or device fails to perform as intended; effects analysis asks what happens when it fails.

Barrier analysis: identify defenses between a hazard and harm; assess whether each barrier is reliable, independent, and monitored.

High-reliability organizing principles: preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, deference to expertise.

Risk registers track identified risks with likelihood, impact, owner, and mitigation status; review them on a defined cycle.

Simulation and drills (e.g., mock codes, emergency preparedness exercises) test system readiness and reveal latent gaps.

Open disclosure is a structured conversation with the patient/family after harm: what happened, consequences, expression of regret, investigation plan, and follow-up.

Disclosure should occur promptly, be led by trained staff, and be documented; delay and defensiveness increase patient and family distress.

Apology laws in many jurisdictions protect expressions of sympathy from being used as evidence; scope varies, so know local rules.

Second victim: the clinician(s) involved in an adverse event who experience guilt, shame, and distress; peer support and structured debriefing help recovery.

Just culture supports disclosure: staff who fear punishment hide information, which prevents learning and harms patients.

Patient and family advisors on safety committees bring the lived experience of care and improve the relevance of improvement work.

Complaints and grievances are safety signals; analyze themes and feed them into improvement, not just service recovery.

Support programs should be separate from disciplinary processes to preserve trust and encourage use.

Incident reporting system design: easy to use, non-punitive, with feedback loops; report volume alone is not a quality indicator because underreporting varies.

Trigger tools: automated or manual flags (e.g., antidote administration, abnormal lab values, unplanned readmission) that prompt chart review for harm.

Harm classification: use standardized severity scales (e.g., no harm, temporary harm, permanent harm, death) and apply them consistently.

Data quality checks: completeness, accuracy, timeliness, and consistency of definitions; validate before drawing conclusions.

Small numbers produce unstable rates; use confidence intervals or aggregate over longer periods before declaring improvement.

Learning from near misses is cheaper than learning from harm; near-miss analysis reveals system weaknesses before injury occurs.

Dashboards should present a balanced set of measures (outcome, process, balancing) to prevent unintended consequences.

Feedback of data to frontline teams (audit and feedback) improves performance when it is timely, credible, and paired with a clear action.

Patient engagement levels: consultation, involvement, partnership, and shared leadership; higher levels require resources and role clarity.

Teach-back: ask patients to explain information in their own words to confirm understanding; it improves comprehension and reduces errors.

Health literacy: use plain language, limit information to key points, and use written materials at appropriate reading levels.

Patients and families can detect errors that staff miss (e.g., medication discrepancies, wrong-site concerns); encourage them to speak up.

Shared decision-making uses evidence, patient values, and clinician expertise; decision aids support, but do not replace, conversation.

Discharge planning with patients and caregivers reduces readmissions and medication errors; confirm understanding before leaving.

Complaints and patient experience data are safety inputs; link them to incident review and improvement priorities.

Cultural humility and language access (interpreters, translated materials) are required for equitable safety.

Competency assessment should be based on observable behaviors and verified at defined intervals, not just completion of e-learning.

Simulation-based training with debriefing improves teamwork and technical skills; effectiveness depends on fidelity, feedback, and repetition.

Just-in-time training (e.g., at the point of a new device or protocol) improves retention compared with one-time sessions.

Crew resource management (CRM) training targets communication, leadership, and decision-making in high-stress teams.

Competency for high-risk tasks (e.g., sedation, central line insertion) should include supervised practice and sign-off.

Training alone rarely changes outcomes; pair education with system changes (checklists, forcing functions) to sustain behavior.

Interprofessional training improves collaboration and reduces hierarchy-related communication failures.

Track training completion and link it to safety measures to evaluate whether education is producing change.

WHO 5 Moments for hand hygiene: before touching a patient, before clean/aseptic procedure, after body fluid exposure risk, after touching a patient, after touching patient surroundings.

Standard precautions apply to all patients: hand hygiene, PPE, safe injection practices, and safe handling of sharps.

Transmission-based precautions (contact, droplet, airborne) add precautions based on the pathogen's route; apply promptly on suspicion.

Central line–associated bloodstream infection prevention bundle: hand hygiene, maximal sterile barrier, chlorhexidine skin antisepsis, optimal site selection, and daily review of line necessity.

Catheter-associated urinary tract infection prevention: avoid unnecessary catheters, use aseptic insertion, maintain closed drainage, and remove early.

Surgical site infection prevention: appropriate antibiotic prophylaxis timing, normothermia, glucose control, and sterile technique.

Multidrug-resistant organism control: surveillance, contact precautions, antimicrobial stewardship, and environmental cleaning.

Hand hygiene compliance measurement: direct observation is the reference but is subject to the Hawthorne effect; pair with product-use data.

Medication error stages: prescribing, transcribing, dispensing, administering, and monitoring; errors can occur at any stage.

High-alert medications require independent double-check by two qualified staff, standardized concentrations, and clear labeling.

Look-alike/sound-alike drug names are a known error source; use tall-man lettering, separate storage, and read-back of verbal orders.

Verbal and telephone orders require read-back to confirm accuracy; limit verbal orders to urgent situations.

Pediatric dosing is weight-based; require double-check of weight and dose calculations before administration.

Adverse drug event detection: trigger tools (e.g., naloxone, vitamin K, diphenhydramine administration) flag possible events for review.

Anticoagulant safety: standardized protocols, monitoring, patient education, and reversal agent availability.

Medication reconciliation at admission, transfer, and discharge reduces discrepancies and preventable harm.

Universal protocol: pre-procedure verification, site marking, and a time-out immediately before the procedure with the full team present.

Site marking should be done by the clinician performing the procedure, with the patient involved when possible, using an unambiguous mark.

Time-out content: patient identity, procedure, site, consent, allergies, positioning, equipment, and anticipated critical events.

Briefings before procedures and debriefings after improve team communication and reveal near misses.

Retained surgical items prevention: standardized counts, radiopaque sponges, and a final count before closure with resolution of discrepancies.

Anesthesia safety: pre-anesthesia evaluation, continuous monitoring (pulse oximetry, capnography), and standardized equipment checks.

Post-procedure handoff to recovery or ward should include procedure details, complications, and monitoring plan.

Procedural sedation requires trained staff, monitoring, and rescue equipment immediately available.

High-reliability organizations (HROs) maintain mindful operations: preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, and deference to expertise.

Emergency preparedness cycle: mitigation, preparedness, response, and recovery; exercises should test communication and surge capacity.

Mock codes test response times, equipment readiness, and team communication; debrief and act on findings.

Rapid response systems: early warning scores trigger review by a rapid response team to prevent deterioration and cardiac arrest.

Failure to rescue: mortality after a complication; early recognition and escalation reduce it.

Standardized emergency carts and equipment checks ensure readiness; document checks and assign ownership.

Surge capacity planning includes staff, supplies, space, and systems (the 4 S's).

Crisis communication requires pre-defined roles, scripts, and channels to avoid information gaps.

Transitions of care (admission, transfer, discharge) are high-risk periods; standardized handoff and reconciliation reduce errors.

Discharge instructions should include medication changes, follow-up appointments, warning signs, and who to contact.

Teach-back at discharge confirms patient understanding and reduces post-discharge adverse events.

Follow-up contact after discharge (phone call or visit) identifies early complications and medication problems.

Referral communication should include reason for referral, relevant history, and expected follow-up; closed-loop referral tracking prevents loss to follow-up.

Ambulatory safety risks include delayed diagnosis, test result follow-up failures, and medication errors; track results and abnormal findings.

Care coordination across settings requires shared information systems or reliable communication channels.

Readmission analysis identifies preventable causes and informs improvement priorities.

Diagnostic error: failure to establish an accurate and timely explanation of the patient's health problem or communicate that explanation.

Diagnostic process spans history, examination, testing, interpretation, and follow-up; errors can occur at any step.

Cognitive biases (anchoring, premature closure, confirmation bias) contribute to diagnostic error; structured reflection and second opinions mitigate.

Test result management: track pending results, notify patients, and document follow-up; failures are a common ambulatory safety gap.

Diagnostic stewardship reduces unnecessary testing and incidental findings that trigger cascades of care.

Closed-loop communication between radiology/pathology and ordering clinicians prevents missed critical results.

Diagnostic error measurement is difficult; use trigger tools, case review, and malpractice claims data as complementary sources.

Second reads and multidisciplinary review improve accuracy for complex cases.

Health IT safety hazards include unsafe defaults, alert fatigue, poor usability, and incorrect data display.

Clinical decision support should be evidence-based, actionable, and targeted; excessive alerts cause override fatigue.

CPOE with dose-range checking reduces medication errors but requires maintenance of the drug knowledge base.

Copy-and-paste and copy-forward in documentation can propagate errors; require review and attestation.

Interoperability gaps at transitions cause information loss; use standardized exchange and reconciliation.

Usability testing with real users before go-live identifies use errors and workarounds.

Downtime procedures must be documented and practiced; paper backups for critical functions.

Health IT incident reporting should capture near misses (e.g., wrong patient selection) to drive redesign.

Workforce safety includes physical hazards (needlesticks, violence, lifting injuries) and psychological hazards (burnout, moral distress).

Needlestick prevention: safety-engineered devices, sharps containers, and post-exposure protocols.

Workplace violence prevention: risk assessment, de-escalation training, reporting systems, and security response.

Burnout is associated with worse safety outcomes; workload, control, and organizational support are modifiable drivers.

Moral distress occurs when clinicians cannot act on their professional judgment; it erodes engagement and safety.

Staff well-being programs should be paired with system fixes (staffing, workflow) rather than individual resilience alone.

Injury and exposure data should be tracked and analyzed like patient harm data.

Psychological safety and workforce safety are linked: staff who fear reporting hide hazards.

Health equity means everyone has a fair opportunity to attain their highest level of health; safety events may disproportionately affect disadvantaged groups.

Stratify safety measures by patient characteristics (language, race/ethnicity, insurance, geography) to detect disparities.

Language access: use qualified interpreters, not family members, for clinical communication.

Implicit bias can affect diagnosis, treatment, and escalation; training alone is insufficient without system checks.

Cultural humility involves self-reflection and openness to patients' values and preferences.

Social determinants (housing, transportation, food) affect adherence and follow-up; screen and refer.

Equity-focused improvement requires data, community input, and targeted interventions.

Measure access and outcomes across groups to identify and close gaps.

Spread requires a clear change package, engaged adopters, and infrastructure (training, data, leadership support).

Sustainability elements: standardize the change, embed in policy and training, assign ownership, and monitor measures over time.

Hardwiring: build changes into workflows, default settings, and checklists so the safe action is the easy action.

Spread strategies: pilot on one unit, document results, share stories, and support adopters with coaching.

Monitor for regression after project end; use run charts to detect drift.

Celebrate and communicate results to maintain engagement and reinforce the change.

Leadership turnover threatens sustainability; embed responsibilities in roles and documents.

Scale requires adaptation to local context, not simple replication.

SBAR: Situation, Background, Assessment, Recommendation; standardizes handoffs and escalation.

CUS: Concerned, Uncomfortable, Safety issue; a graded assertiveness tool for raising concerns.

Two-challenge rule: if a concern is not addressed, state it a second time and escalate if needed.

Closed-loop communication: sender transmits, receiver repeats back, sender confirms.

Briefings, huddles, and debriefings structure team communication before, during, and after work.

Handoff tools (I-PASS: Illness severity, Patient summary, Action list, Situation awareness, Synthesis by receiver) reduce omissions.

Speak-up requires psychological safety and leadership responsiveness; training alone is insufficient.

Interprofessional rounds improve shared understanding and reduce communication gaps.

Incident report content: what happened, when, where, who was involved, immediate action taken, and severity.

Report promptly; preserve equipment and documentation for investigation.

Triage reports by severity and potential for learning; not every report needs a full RCA.

RCA team should include those closest to the work and those with authority to change the system.

Causal statements should describe cause and effect and be system-focused (e.g., 'lack of standardized labeling led to...').

Action plans should prioritize strong interventions (forcing functions, standardization) over weak ones (education, reminders).

Share lessons learned with frontline staff to close the loop and encourage future reporting.

Track action completion and measure whether the change reduced the risk.

Use at least two patient identifiers (name and date of birth or medical record number) before care, medication, blood, or specimens.

Never use room number, bed, or physical location as an identifier.

Barcode scanning at the bedside verifies patient identity and medication match.

Blood transfusion: two-person verification of patient identity and blood product compatibility.

Specimen labeling at the bedside, with patient present, prevents mislabeling.

Newborn identification uses paired bands and matching with the mother.

Patient identification failures are a root cause of wrong-patient errors, including wrong-site and medication errors.

Standardize identification processes across settings and audit compliance.

Clinical governance: the framework through which organizations are accountable for continuously improving quality and safeguarding standards.

Components: leadership, audit, risk management, education, patient involvement, and information.

Quality committees should have clear terms of reference, membership, and reporting lines to the governing body.

Clinical audit cycle: select topic, set standards, collect data, compare, implement change, re-audit.

Morbidity and mortality (M&M) meetings review adverse outcomes and identify system improvements.

Peer review supports professional standards and learning; protect confidentiality where applicable.

Dashboards and reports should reach decision-makers with actionable data.

Accountability requires follow-through on identified actions.

Slips and lapses are skill-based errors from inattention or memory failure; reduce with checklists, standardization, and forcing functions.

Mistakes are rule-based or knowledge-based errors; reduce with decision support, training, and clear protocols.

Violations are deliberate deviations; distinguish routine (accepted practice) from situational (necessitated by circumstances) and exceptional (reckless).

Routine violations often signal that the procedure does not fit the work; investigate the design before punishing.

Blame suppresses reporting; separate learning from discipline.

Just culture responses should be consistent and transparent.

Investigate near misses as seriously as harm events; they reveal the same system weaknesses without injury.

Document the rationale for the response to build trust.

Patient safety competencies include understanding systems, human factors, teamwork, and improvement methods.

Education should be interprofessional and case-based to reflect real care.

Simulation and debriefing build skills safely without patient risk.

Research methods: use validated measures, appropriate denominators, and control for confounders.

Quality improvement projects are not the same as research; IRB review may be required depending on intent and publication.

Publish and share findings to contribute to the broader safety evidence base.

Evaluate education by behavior change and outcomes, not just satisfaction.

Faculty development is needed to teach safety competencies effectively.

WHO Global Patient Safety Action Plan focuses on policies, high-reliability systems, safety of processes, and patient engagement.

Policy levers include regulation, accreditation, payment incentives, and public reporting.

Public reporting of safety measures can drive improvement but may create gaming or avoidance of high-risk patients.

Payment penalties for harm (e.g., never events) exist in some systems; evidence of effectiveness is mixed.

International comparisons require harmonized definitions and denominators.

Patient safety is a global health priority; low-resource settings face additional risks from infrastructure and staffing.

Legislation on disclosure and apology varies by country and affects practice.

Engage policymakers with data and patient stories to drive system change.

Simulation types: task trainers, manikins, standardized patients, and in-situ simulation in the real environment.

In-situ simulation reveals latent system issues (equipment, layout, communication) in the actual workspace.

Debriefing structure: describe what happened, analyze why, and summarize learning.

Psychological safety in simulation is essential; frame it as learning, not testing.

Fidelity should match learning objectives; high fidelity is not always necessary.

Repeat practice improves retention and performance.

Debrief after real events (hot debrief) to capture learning while memory is fresh.

Evaluate simulation by behavior change in real care, not just participant satisfaction.

Hawthorne effect: observed behavior changes when people know they are observed; direct observation hand hygiene audits overestimate compliance.

Selection bias: non-random samples may not represent the population.

Measurement bias: the tool itself may systematically misclassify events.

Regression to the mean: extreme values tend to move toward average on repeat measurement; do not attribute this to intervention.

Small denominators produce wide variation; avoid overinterpreting single data points.

Use control charts to distinguish signal from noise.

Triangulate data sources (reports, audits, outcomes) before concluding.

Document definitions and changes in measurement to preserve comparability over time.

Transformational leadership (idealized influence, inspirational motivation, intellectual stimulation, individualized consideration) is associated with better safety climate.

Safety-specific transformational leadership: leaders articulate safety vision, model safe behavior, and reward safety.

Leader rounding with follow-up builds trust and surfaces concerns.

Leaders should respond to bad news with curiosity, not blame, to encourage reporting.

Visible leadership commitment (resources, time, attention) predicts safety climate scores.

Climate surveys should be paired with action plans and communicated back to staff.

Leaders must address disruptive behavior; incivility harms teamwork and safety.

Succession planning embeds safety leadership in the organization.

TeamSTEPPS core skills: communication, leadership, situation monitoring, and mutual support.

Briefing: short planning session before work; huddle: problem-solving during work; debrief: learning after work.

STEP: Status of patient, Team members, Environment, Progress toward goal; a situation monitoring tool.

I'M SAFE: Illness, Medication, Stress, Alcohol/drugs, Fatigue, Eating/elimination; a self-check for fitness for duty.

Mutual support includes task assistance, feedback, advocacy and assertion, and conflict resolution.

Advocacy and assertion: use CUS or two-challenge rule to raise concerns.

Cross-monitoring: team members monitor each other's actions and catch errors.

Team training should be paired with system changes (checklists, protocols) to sustain behavior.

RCA is triggered by sentinel events or serious harm; it is retrospective and system-focused.

Steps: identify the event, gather information (records, interviews, site visit), map the process, identify contributing factors, develop causal statements, and create an action plan.

Contributing factors categories: patient factors, task factors, individual factors, team factors, work environment, organizational/management, and institutional context.

Causal statement format: cause → effect → event; avoid naming individuals.

Strong actions: forcing functions, standardization, simplification, and automation; weak actions: education, warnings, and reminders.

Action plans require owners, deadlines, and measures of effectiveness.

Share findings and monitor for recurrence.

RCA quality depends on team diversity and psychological safety during interviews.

PDSA cycle: Plan (predict, plan test), Do (run test, document), Study (compare to prediction), Act (adopt, adapt, abandon).

Start small: test with one patient or one day to reduce risk.

Predictions make learning explicit; compare observed results to prediction.

Iterate: multiple cycles build confidence before scaling.

Measures: outcome, process, and balancing measures.

Aim statements should be specific, measurable, and time-bound.

Spread after demonstrated improvement; adapt to local context.

Document cycles to preserve learning and support spread.

Critical result communication requires closed-loop notification and documentation of who received the result and when.

Read-back of critical results confirms accuracy.

Policies should define critical values, timeframes, and escalation if the clinician cannot be reached.

Test result tracking systems reduce missed results.

Patient notification of results is part of the loop; document it.

Failures in result communication are a common source of diagnostic error.

Audit compliance with critical result policies.

Use standardized templates for result communication.

Safety culture surveys measure staff perceptions of teamwork, leadership, reporting, and safety climate.

Survey results should be reported by unit and role to identify local issues.

Pair survey results with behavioral measures (reporting rates, audits) to avoid perception-only conclusions.

Action plans should be developed with staff input and communicated back.

Repeat surveys at intervals to track change.

Response rates affect representativeness; encourage participation.

Benchmarking with comparable organizations requires harmonized items and methods.

Culture change is slow; use trend data rather than single snapshots.