SEC 3 — Quality, Patient Safety & Audit System (QPS) | دليل السياسات والإجراءات في غرفة العمليات

Department Operating Theatre (OT)
General Hospital

Version & Dates Version: 1.0
Effective: ___/___/20__
Review: ___/___/20__

Owner OT Director + OT Nurse Manager + QPS Liaison

Applies to All OT staff, surgical teams inside OT, contracted services.

1.0 Executive Summary (the “why” in plain human language)

1.1 What we are trying to protect

In the operating theatre, many things can go wrong without anyone being careless. Harm often happens when systems are weak: an unread label, a count not closed properly, a checklist treated like paperwork, a door opening too often, a rushed decision, an unreported “good catch” that disappears with the shift handover.

This policy makes sure patient safety in OT is not dependent on who is on duty, but on how OT works every day:

A visible patient safety program with clear roles and safety rounds
A reliable reporting system for incidents, near-misses, and hazards (with feedback)
A structured response to sentinel events with RCA and strong action plans
A disciplined audit program focused on what truly harms patients (counts, checklist compliance, IPC behaviors, medication labeling)
A KPI dashboard that tells the truth (not just “numbers for reports”)
Tracer readiness and mock survey practice (because surveyors follow patient journeys) (jointcommission.org)
A respectful mechanism for patient feedback and complaints
Continuous improvement using PDSA and reliability tools (ihi.org)

1.2 Accreditation alignment (what surveyors look for)

CBAHI requires structured quality and patient safety systems and emphasizes mandatory reporting requirements (e.g., sentinel event reporting through its portal within defined time). (cbahi.gov.sa)
OT safety is closely linked to perioperative hazards such as wrong site surgery, retained foreign bodies, mislabeled specimens, equipment unavailability, and miscommunication. (istitlaa.ncc.gov.sa)
JCI / IPSG concepts strongly focus on correct patient identification, correct procedure/site, effective communication, infection prevention, and safe medication practices in high-risk areas like OT. (jointcommission.org)

2.0 Purpose

2.1 Purpose statement

To establish an OT Quality & Patient Safety system that:

2.1.1 Prevents avoidable harm through standardized high-reliability processes
2.1.2 Detects risk early using incident reports, near-miss reports, hazard reports, and safety rounds
2.1.3 Responds to serious events with structured analysis (RCA/RCA2) and strong actions (ihi.org)
2.1.4 Measures what matters using OT KPIs (safety, quality, efficiency, patient experience)
2.1.5 Demonstrates readiness for tracers and mock surveys through continuous self-assessment (jointcommission.org)
2.1.6 Converts learning into improvement using PDSA cycles and reliability tools (ihi.org)

3.0 Scope

3.1 Included

3.1.1 OT patient safety governance and roles
3.1.2 Safety rounds and risk identification
3.1.3 Incident / near-miss / hazard reporting and OT responsibilities (psnet.ahrq.gov)
3.1.4 Sentinel event response and RCA participation (OT interface and ownership) (jointcommission.org)
3.1.5 OT audit program: counts, checklist compliance, IPC behaviors, medication labeling (who.int)
3.1.6 OT KPI dashboard and performance review
3.1.7 Tracer readiness, mock survey planning (jointcommission.org)
3.1.8 Patient feedback/complaints handling in OT
3.1.9 Continuous improvement (PDSA, reliability tools) (ihi.org)

3.2 Exclusions (clear boundary)

3.2.1 Anesthesia clinical governance standards (moderate sedation, anesthesia monitoring protocols, anesthesia machine checks) are governed by the Anesthesia Department manual.
3.2.2 This policy covers OT systems and interfaces only.

4.0 Definitions (shared language)

4.1 Patient Safety Event types

4.1.1 Adverse Event: An injury caused by medical management rather than the patient’s illness (general safety definition).
4.1.2 Near Miss: An unsafe situation indistinguishable from an adverse event except for the outcome—harm did not occur due to luck or early detection. (psnet.ahrq.gov)
4.1.3 Unsafe Condition / Hazard: A circumstance that increases the probability of an adverse event (e.g., unlabeled syringes on sterile field, missing instrument set, wet pack). (psnet.ahrq.gov)

4.2 Sentinel Event

4.2.1 A sentinel event is a patient safety event that reaches a patient and results in death, permanent harm, or severe harm (definitions used in major accreditation/oversight). (jointcommission.org)

4.3 RCA / RCA2

4.3.1 RCA is a structured method to analyze serious events and identify underlying systems issues, avoiding blame on individuals. (psnet.ahrq.gov)
4.3.2 RCA2 emphasizes not only analysis but high-leverage actions that prevent recurrence. (ihi.org)

5.0 Policy Statement

5.1 OT shall operate a structured Quality & Patient Safety system that continuously identifies risk, reports and investigates events, conducts targeted audits, tracks KPIs, prepares for tracers, listens to patients, and implements measurable improvement.
5.2 OT leadership shall ensure safety culture: reporting without fear, learning without shame, and improvement without delay.
5.3 Sentinel events shall be managed according to hospital policy and national requirements; CBAHI reporting obligations shall be fulfilled through the official portal and within required timeframes. (cbahi.gov.sa)

6.0 Procedures and System Design (SEC 3.1–3.8)

6.1 Patient Safety Program in OT (roles, safety rounds)

6.1.1 The OT Patient Safety Program — what it looks like in real life

6.1.1.1 The OT Patient Safety Program is not “a file on a shelf.” It is a routine, visible rhythm:

a) daily safety huddles
b) weekly or monthly safety rounds
c) incident review and learning feedback
d) audits and corrective actions
e) KPI review in OT leadership and OTMC meetings

6.1.1.2 The goal is simple: make safe practice the easiest practice and make risky practice hard to hide.

6.1.2 Roles and responsibilities (minimum)

6.1.2.1 OT Director / OT Chair

a) champions safety culture and “stop-the-line” authority
b) ensures the OT safety program is discussed in OTMC
c) supports corrective actions even when they are uncomfortable

6.1.2.2 OT Nurse Manager (Operations)

a) owns daily implementation of safety processes
b) ensures safety rounds occur and actions are closed
c) ensures audit results translate into training and fixes
d) escalates system risks to hospital QPS

6.1.2.3 OT Quality & Patient Safety Lead / Champion

a) maintains OT audit plan and KPI dashboard
b) coordinates tracer readiness activities
c) trends incidents/near misses and produces learning summaries
d) supports improvement project charters (PDSA)

6.1.2.4 Charge Nurse (each shift)

a) conducts safety huddle, identifies immediate constraints
b) ensures safe staffing and escalation when unsafe
c) supports reporting of near misses (“good catches”)
d) ensures immediate containment actions are taken

6.1.2.5 All OT staff

a) practice safe behaviors (counts, labeling, sterile discipline)
b) report hazards, near misses, and events early (psnet.ahrq.gov)
c) participate in audits and improvement activities

6.1.3 OT Safety Rounds (structure and frequency)

6.1.3.1 Frequency: Minimum monthly; higher frequency during risk periods (staff shortage, outbreaks, major changes).

6.1.3.2 Participants: OT leadership + QPS rep + IPC rep + CSSD rep + Biomedical/Engineering (as needed).

6.1.3.3 Method: short walk-through using a checklist that focuses on high-risk failure points:

a) identification and time-out discipline support
b) count reliability behaviors
c) sterile field and traffic discipline
d) medication labeling on sterile field (ECRI and ISMP)
e) specimen labeling and handling
f) equipment readiness and failures
g) privacy behaviors (access control, unnecessary exposure)
h) staff fatigue signals (overtime, missed breaks)

6.1.3.4 Output: Each round ends with:

a) 3 immediate fixes (same day)
b) 3 improvement actions (within 30 days)
c) 1 systemic risk for OTMC/hospital QPS (if needed)

6.1.4 Daily OT Safety Huddle (short, protective habit)

6.1.4.1 Time: Start of day + mid-day if high volume.

6.1.4.2 Agenda (7 minutes):

a) staffing risks and skill mix
b) instrument/implant readiness
c) isolation cases and IPC needs
d) known equipment problems
e) bed status constraints (ICU/ward interface)
f) reminders: “counts, labeling, checklist discipline”

6.1.4.3 The huddle is not a meeting to complain; it is a tool to prevent surprises.

6.2 Incident / Near-Miss / Hazard Reporting (OT responsibilities)

6.2.1 Why reporting matters (human explanation)

6.2.1.1 A near miss is a gift—an accident that tried to happen but didn’t. (psnet.ahrq.gov)

6.2.1.2 If we don’t capture it, the system stays broken and the next time the patient may pay the price.

6.2.2 What must be reported

6.2.2.1 Report immediately (same shift):

a) wrong patient/site/procedure catch
b) count discrepancy (even if resolved)
c) unlabeled medication/solution on sterile field (ECRI and ISMP)
d) specimen labeling discrepancy
e) sterility breach (wet pack, torn wrapper, contamination)
f) device malfunction affecting care
g) patient harm event (fall, burn, wrong medication exposure)

6.2.2.2 Report as hazard (even without patient contact):

a) repeated missing instruments
b) recurring cleaning failures
c) persistent door opening / traffic breaches
d) repeated temperature/humidity out-of-range (if monitored)
e) staff fatigue patterns creating risk

6.2.3 Definitions used for consistency

6.2.3.1 Near miss and error definitions align with established patient safety terminology. (psnet.ahrq.gov)

6.2.4 OT reporting responsibilities (step-by-step)

6.2.4.1 Step 1 — Protect the patient (immediate containment)

a) stop the unsafe process (“stop-the-line”)
b) correct the immediate risk (label, re-count, replace tray, repeat verification)
c) inform surgeon/charge nurse as appropriate

6.2.4.2 Step 2 — Inform OT leadership (rapid escalation)

a) charge nurse must be informed for all significant safety events
b) OT manager notified for moderate/high severity or repetitive patterns

6.2.4.3 Step 3 — Enter the report in the hospital reporting system

6.2.4.3.1 Reports should include:

a) what happened, where, when
b) who was involved (as required by system)
c) immediate actions taken
d) what might have prevented it
e) any equipment/lot numbers (implants, meds, sterile packs)

6.2.4.4 Step 4 — Investigation level (triage)

6.2.4.4.1 QPS/OT leadership determines investigation type:

a) Level A (Quick review): low risk, one-time issue
b) Level B (Mini-RCA): moderate risk, trend, or significant near miss
c) Level C (Formal RCA/RCA2): sentinel/serious harm or high-risk event (psnet.ahrq.gov)

6.2.4.5 Step 5 — Feedback and learning loop

6.2.4.5.1 Event reporting is known to be more valuable when organizations provide feedback and use multiple detection methods. (psnet.ahrq.gov)

6.2.4.5.2 OT shall provide:

a) “lessons learned” summaries (de-identified)
b) visible fixes (policy update, label packs, count standardization)
c) recognition of “good catches” (positive safety culture)

6.2.5 Reporting culture protections

6.2.5.1 RCA principles emphasize focusing on systems and avoiding the trap of blaming individuals. (psnet.ahrq.gov)

6.2.5.2 OT leadership must protect staff from retaliation when reporting in good faith.

6.3 Sentinel Event Response (RCA participation, action plans)

6.3.1 First hour mindset: stabilize, respect, preserve truth

6.3.1.1 When a sentinel event occurs, the OT must shift into three priorities:

a) Care for the patient and family
b) Secure the environment and preserve evidence
c) Activate the reporting and investigation pathway

6.3.2 Sentinel event definition and examples

6.3.2.1 Sentinel events involve death, permanent harm, or severe harm. (jointcommission.org)

6.3.2.2 Perioperative examples include wrong site surgery, retained foreign body, lost/mislabeled specimens, and major miscommunication—recognized perioperative hazards. (istitlaa.ncc.gov.sa)

6.3.3 Immediate response checklist (same shift)

6.3.3.1 Clinical actions: stabilize patient and provide emergency response per clinical policy.

6.3.3.2 Operational actions:

a) stop related activity if needed (pause room use)
b) quarantine involved equipment/consumables if relevant
c) preserve documentation (records, count sheets, labels, device logs)
d) notify OT leadership and QPS immediately

6.3.4 Notification and reporting requirements (CBAHI)

6.3.4.1 Reporting of sentinel events through the CBAHI portal is mandated and must occur within the specified timeframe (commonly stated as within 5 working days). (cbahi.gov.sa)

6.3.4.2 OT leadership will coordinate with hospital QPS to complete reporting and provide required RCA/action plan documentation within required timelines. (istitlaa.ncc.gov.sa)

6.3.5 RCA / RCA2 process (how we investigate without blame)

6.3.5.1 RCA is a structured method to identify underlying system vulnerabilities. (psnet.ahrq.gov)

6.3.5.2 RCA2 emphasizes strong actions, not weak promises. (ihi.org)

6.3.5.3 RCA team composition (minimum):

a) facilitator trained in RCA methods
b) OT representative(s) who know the normal process
c) QPS representative
d) IPC/CSSD/Biomed/Supply chain as needed
e) a member not directly involved in the event (to reduce bias)

6.3.5.4 RCA steps:

a) map the real process (what should happen vs what happened)
b) identify contributing factors (human factors, environment, equipment, communication, policy gaps)
c) identify root/system causes
d) develop actions using an action hierarchy (prefer strong system actions) (ihi.org)
e) define effectiveness measures (how we know it worked)

6.3.5.5 Examples of “strong” vs “weak” actions

a) Strong: standardization, forcing functions, physical redesign, automation, independent double checks
b) Weak: reminders only, “be careful” memos, re-education without system changes

(Aligned with RCA2 guidance emphasizing action strength.) (ihi.org)

6.3.6 Action plan closure and verification

6.3.6.1 Every action must have: owner, due date, evidence of completion, and a re-audit plan.

6.3.6.2 OTMC reviews sentinel event actions until closure.

6.4 OT Audit Program (counts, checklist compliance, IPC, meds labeling)

6.4.1 Why OT audits must be narrow and serious

6.4.1.1 OT audit is not “busy work.” It is a method to verify that the most dangerous processes are performed reliably.

6.4.2 Audit governance

6.4.2.1 OT shall maintain an Annual OT Audit Plan approved by OT leadership and reviewed in OTMC.

6.4.2.2 Audit methods include:

a) direct observation (best for behavior/reliability)
b) document review (count sheets, checklist forms)
c) targeted sampling triggered by incidents/trends
d) tracer-style audits following a patient journey (jointcommission.org)

6.4.3 Audit #1 — Safe Surgery Checklist Compliance

6.4.3.1 The WHO Surgical Safety Checklist includes confirmation of counts, specimen labeling, and team communication at defined moments. (who.int)

6.4.3.2 Audit elements (minimum):

a) Sign-In completed before induction phase (OT verifies process compliance)
b) Time-Out performed with full team attention
c) Sign-Out includes: correct procedure name, counts completed, specimen labeling read aloud, equipment issues noted (who.int)

6.4.3.3 Scoring (example):

a) 0 = not done / falsified / unsafe
b) 1 = partially done / poor engagement
c) 2 = fully done with team engagement

6.4.3.4 Target compliance: ≥ 90% full compliance with meaningful engagement (adjust per hospital target).

6.4.4 Audit #2 — Surgical Counts Reliability (RSI prevention)

6.4.4.1 Retained surgical items are recognized hazards; prevention relies on reliable counting systems and team actions. (psnet.ahrq.gov)

6.4.4.2 Audit elements (minimum):

a) initial count performed and documented
b) additional counts performed at required moments (closure, staff handoff, cavity closure as applicable)
c) discrepancy triggers full reconciliation before patient leaves OT
d) communication: count results verbally confirmed as required (aligned with checklist sign-out behavior) (who.int)

6.4.4.3 Near miss capture: any discrepancy resolved must still be reported as near miss (learning value).

6.4.5 Audit #3 — Infection Prevention Behaviors in OT

6.4.5.1 OT shall audit high-impact IPC behaviors:

a) hand hygiene compliance in OT workflow
b) attire and zoning discipline
c) traffic/door opening discipline
d) environmental cleaning compliance
e) sterile supplies integrity checks (wet packs, torn wrappers)

6.4.5.2 SSI prevention link: SSI prevention depends on evidence-based strategies across pre/intra/post periods (OT contributes through sterile discipline and bundles). (iris.who.int)

6.4.6 Audit #4 — Medication Labeling in the OT Sterile Field

6.4.6.1 ISMP perioperative guidelines emphasize that drug containers remain labeled up to administration and include detailed sterile field labeling expectations. (ECRI and ISMP)

6.4.6.2 Audit elements:

a) all syringes/bowls/cups on sterile field labeled immediately after filling
b) labels contain at minimum medication name + strength/concentration and preparer identification (as applicable) (ECRI and ISMP)
c) labeling performed even if only one solution is present (ECRI and ISMP)
d) no pre-labeling of empty containers (ECRI and ISMP)
e) verbal + visual confirmation between scrub and circulating staff where applicable (ECRI and ISMP)

6.4.7 Audit action pathway (what happens when results are poor)

6.4.7.1 If compliance below threshold:

a) immediate reinforcement coaching
b) identify barriers (lack of labels, workflow design, staffing)
c) implement system fixes (label packs, standard work, role clarity)
d) re-audit within 2–4 weeks
e) persistent noncompliance escalated to OT leadership and OTMC

6.5 OT KPI Dashboard (SSI bundle compliance, cancellation, utilization, etc.)

6.5.1 KPI philosophy (make the numbers meaningful)

6.5.1.1 KPIs exist to reveal truth, guide action, and protect patients—not to decorate reports.

6.5.2 KPI categories (minimum)

6.5.2.1 Safety KPIs

a) count discrepancies (rate per 100 cases)
b) medication labeling compliance (audit %) (ECRI and ISMP)
c) wrong-site/near-miss events (count and learning actions)
d) sentinel events (number, RCA completion, action closure)

6.5.2.2 Infection Prevention / SSI KPIs

a) SSI rate by procedure group (if surveillance available)
b) SSI bundle compliance (selected elements based on local policy)

Evidence base: WHO and CDC publish SSI prevention recommendations and guidance. (iris.who.int)

6.5.2.3 Efficiency KPIs

a) cancellation rate (overall and avoidable)
b) utilization (%)
c) first-case on-time start
d) turnover time (median + outliers)

6.5.2.4 Staff / Culture KPIs

a) reporting rate (events + near misses) as a culture indicator (psnet.ahrq.gov)
b) training and competency completion (linked to SEC 2)
c) overtime/fatigue indicators (proxy)

6.5.2.5 Patient Experience KPIs

a) complaints related to privacy/dignity and OT communication
b) patient feedback themes (qualitative + actions)

6.5.3 KPI dictionary (required discipline)

6.5.3.1 Each KPI must have:

a) clear definition
b) numerator/denominator
c) data source
d) frequency of reporting
e) owner
f) action thresholds (green/amber/red)
g) improvement plan when red

6.5.4 KPI review cadence

6.5.4.1 Unit level: monthly
6.5.4.2 OTMC: monthly/quarterly (depending on governance design)
6.5.4.3 Hospital QPS committee: quarterly

6.6 Tracer Readiness & Mock Survey Plan

6.6.1 What tracer methodology means (and why OT must love it)

6.6.1.1 Tracer methodology follows the patient’s experience of care through the organization to identify performance issues and interfaces. (jointcommission.org)

6.6.1.2 OT is always part of tracers because it sits at the intersection of many risks: IPC, medication, documentation, equipment, communication.

6.6.2 OT tracer types (minimum)

6.6.2.1 Patient tracer (a real or recent case pathway):

a) pre-op verification → OT entry → checklist → counts → specimen → implant traceability → PACU handover interface

6.6.2.2 System tracer (process-focused):

a) sterile processing interface
b) medication labeling and storage system
c) infection prevention behaviors
d) environment/facility safety interface

6.6.2.3 Mock tracer method

Joint Commission tracer-style mock review methods are documented in guidance on how to conduct mock tracers. (digitalassets.jointcommission.org)

6.6.3 Mock survey plan (OT practical plan)

6.6.3.1 Frequency: at least quarterly; monthly during pre-accreditation phase.

6.6.3.2 Team: OT lead + QPS + IPC + CSSD + FMS/HCT as needed.

6.6.3.3 Steps:

a) choose tracer case type (implant case, emergency case, isolation case)
b) prepare interview questions (staff know the “why,” not just “what”)
c) observe real work (not staged)
d) score gaps
e) immediate debrief (“what we fix today” vs “what needs a project”)
f) track actions with deadlines and re-verification

6.6.4 Evidence binder (OT readiness file)

6.6.4.1 Keep a controlled readiness set:

a) audit plan + latest results
b) KPI dashboard
c) incident trend summaries
d) RCA action closures
e) training compliance summary
f) policies and forms index (current versions)

6.7 Patient Feedback / Complaints Handling in OT

6.7.1 The patient voice in OT (often silent, always important)

6.7.1.1 Patients often remember OT as a blur—fear, exposure, coldness, voices, waiting.

6.7.1.2 Complaints in OT are often about: dignity, communication, delays, and privacy.

6.7.2 Receiving feedback (channels)

6.7.2.1 Patient relations unit
6.7.2.2 written complaint forms
6.7.2.3 verbal feedback documented by nurse/charge nurse
6.7.2.4 post-op follow-up calls (where hospital uses them)

6.7.3 OT complaint workflow (minimum)

6.7.3.1 Step 1: acknowledge receipt (timely, respectful)
6.7.3.2 Step 2: triage severity (privacy breach, harm allegation, communication issue)
6.7.3.3 Step 3: investigation (interviews + document review)
6.7.3.4 Step 4: response and remedy
6.7.3.5 Step 5: trend analysis (monthly themes)
6.7.3.6 Step 6: improvement action if systemic

6.7.4 Confidentiality and dignity

6.7.4.1 OT must protect patient confidentiality during complaint handling; details shared only with those who need to know.

6.8 Continuous Improvement (PDSA, reliability tools)

6.8.1 Improvement is how we honor “good catches”

6.8.1.1 Reporting without improvement is like diagnosing without treating.

6.8.2 Model for Improvement and PDSA

6.8.2.1 The Model for Improvement uses an aim, measures, and change ideas tested through PDSA cycles. (ihi.org)

6.8.2.2 OT improvement projects must be practical and short-cycle: test changes in real work, learn, then scale.

6.8.3 Reliability tools OT should use (high-yield)

6.8.3.1 Standard work (one best way for counts, labeling, checklist leadership)
6.8.3.2 Bundles (SSI bundle compliance tracking with selected elements) (iris.who.int)
6.8.3.3 Visual cues (label packs, count boards, specimen label “read-back” script)
6.8.3.4 Independent double checks (high-risk steps)
6.8.3.5 Action hierarchy mindset (choose stronger actions when fixing risk) (ihi.org)

6.8.4 Improvement project governance

6.8.4.1 Every OT improvement project must have:

a) aim statement (specific, time-bound)
b) measures (process + outcome)
c) team and sponsor
d) PDSA log
e) sustainability plan (audit + training + ownership)

7.0 Documentation and Controlled Records

7.1 OT Safety rounds checklist and action log
7.2 Incident/near-miss/hazard reports and closure evidence
7.3 Sentinel event RCA/RCA2 files, action plans, verification audits (ihi.org)
7.4 Annual audit plan + results + corrective actions
7.5 KPI dashboard + minutes where KPIs reviewed
7.6 Tracer/mock survey tools + action closure evidence (digitalassets.jointcommission.org)
7.7 Complaint log (de-identified themes) + improvement actions

8.0 Training Requirements

8.1 Staff must be oriented to incident reporting definitions and expectations. (psnet.ahrq.gov)
8.2 Staff must be trained on checklist leadership and engagement (not tick-box behavior). (who.int)
8.3 Staff must be trained on medication labeling rules for sterile field. (ECRI and ISMP)
8.4 Leaders must be trained on RCA/RCA2 and action strength. (ihi.org)

9.0 Compliance, Noncompliance, and Escalation

9.1 Critical safety noncompliance (e.g., falsified checklist, unresolved count discrepancy, repeated unlabeled syringes) triggers immediate intervention, coaching, and escalation to OT leadership.
9.2 Persistent patterns become OTMC agenda items with system-level corrective actions.

10.0 References (English)

10.1 CBAHI Portal overview and standards mission. (portal.cbahi.gov.sa)
10.2 CBAHI sentinel event reporting Reporting statement (portal requirement). (cbahi.gov.sa)
10.3 CBAHI/NCC published standards Text showing sentinel event reporting timeline and RCA/risk reduction plan expectations. (istitlaa.ncc.gov.sa)
10.4 Perioperative safety hazards list (wrong site, RSI, mislabeled specimens, missing equipment, miscommunication). (istitlaa.ncc.gov.sa)
10.5 AHRQ PSNet Definitions for near misses/errors; event reporting concepts; RCA primer. (psnet.ahrq.gov)
10.6 IHI Model for Improvement and PDSA; RCA2 tool. (ihi.org)
10.7 Joint Commission tracer methodology And mock tracer guidance (used for tracer readiness design). (jointcommission.org)
10.8 WHO Surgical Safety Checklist And implementation resources. (who.int)
10.9 ISMP Guidelines For Safe Medication Use in Perioperative and Procedural Settings (labeling). (ECRI and ISMP)
10.10 CDC and WHO guidance On SSI prevention (evidence base for SSI bundle/KPIs). (stacks.cdc.gov)

SEC 3 — Quality, Patient Safety, and Audit System (QPS / IPSG)