Framework outputs and case demonstration
The development process produced a four-stage cycle and six operational steps. The method requires the team to retain a traceable link between evidence, candidate factors, causal chains, SEIPS dimensions, actions, and measures. The following cases show how that record can be constructed; they do not test comparative effectiveness.
Domestic insulin use example
The Fishbone scan identified candidate factors relating to patient knowledge, education tasks, insulin-pen materials, demonstration tools, the discharge environment, and organizational ownership. A priority chain began with incorrect pen use: why was the device used incorrectly, why was the misunderstanding not identified, why was teaching provided without standardized demonstration and teach-back, and why were resources and accountability for medication education insufficient? This chain shifted the analytical endpoint from patient error to modifiable education design and governance conditions. SEIPS mapping located the conditions across person (health literacy and prior experience), tasks (preparation and administration steps), tools and technology (limited visual or video aids), environment (time-limited discharge teaching), and organization (non-standard education and unclear ownership). Corresponding actions included standardized illustrated and video instructions, teach-back, and access to pharmacy consultation. The available case description reported improvement after six months but did not provide a denominator, sample size, comparator, or statistical analysis; no effect estimate is therefore claimed.
Published Italian heparin case
Fishbone analysis identified similar packaging, adjacent storage of concentrations, ineffective checks, and vulnerabilities spanning procurement to administration23. Five Whys linked selection and detection failures to absent separation standards, weak forcing functions, and fragmented governance. SEIPS mapping placed the conditions in tools and technology, tasks, physical environment, and organization rather than attributing the event to a single operator. The mapped conditions support layered actions such as physical separation and standardization of high-alert medicines, barcode medication administration, unit-dose dispensing, and formal pharmacy-nursing governance. These actions demonstrate cause-to-intervention alignment, but the published event investigation does not isolate the independent effect of each intervention.
Cross-case methodological findings
In both demonstrations, Fishbone analysis expanded the search space, Five Whys developed selected causal chains, and SEIPS exposed interactions and guided system-level action. The examples also identified a reporting requirement for the framework: when denominators, sample sizes, comparator data, or implementation measures are unavailable, the limitation must be recorded rather than replaced with an unsupported quantitative claim.
Pharmacy Functions Within the Framework
Four pharmacy functions were mapped to the framework: technical analysis, multidisciplinary coordination, system-improvement delivery, and safety learning. These functions are methodological role assignments intended to clarify responsibility at each stage. They are not presented as roles derived from a systematic synthesis or as empirically proven determinants of outcome24,25.
Pharmacist as technical expert and analysis leader
This foundational RCA role requires pharmacists to move beyond traditional information consultation to become architects of the analytical process and arbiters of technical drug-related issues. Specifically, they must clarify all medication details—standard and maximum doses, pharmacological properties, compatibility, and administration routes26. These judgments form the cornerstone for correct analysis, preventing unfounded discussions. Regarding methodology, pharmacists should be skilled in guiding teams through the creation of Fishbone Diagrams, applying the Five Whys, and explaining SEIPS system concepts. Crucially, they must use specialized knowledge in pharmacokinetics and pharmacodynamics to assess event likelihood and causality, providing a scientific basis for the analysis.
Communication coordinator and team builder
The pharmacy department’s unique position naturally bridges multiple stakeholders. Through daily collaboration with clinical, nursing, and management teams, pharmacists often serve as team facilitators. This role requires strong communication skills—translating clinical issues for clinicians, while framing improvement proposals in terms of risk control and cost-effectiveness for management27. When interdepartmental disagreements arise, pharmacists can leverage their relatively neutral standing to steer discussions toward objective data and standard procedures, fostering consensus28. Moreover, they should model a non‑punitive safety culture by avoiding blame‑oriented language and promoting an open, system‑focused team environment through professional demeanor29.
System improvement designer and driver
This role marks the pharmacist's transition from analyst to implementer30. Pharmacists must move beyond problem identification to become solution architects and project managers for the improvement process. They are required to translate RCA findings into actionable changes—for instance, advancing P&T Committee decisions on packaging, revising SOPs for process flaws, or developing alert systems and training for knowledge gaps. Crucially, pharmacists must proactively coordinate resources across departments to optimize IT systems, workflows, and policies. This involves collaborating with IT on prescription rules, co-designing high-alert medication processes with nursing, and proposing medication safety metrics for performance reviews. Throughout, pharmacists must track implementation, overcome resistance, and ensure measures are effectively executed and deliver intended results31.
Safety culture advocate and educator
In this role, pharmacists transform individual incident knowledge into institutional wisdom. They are tasked with converting RCA insights into educational content—such as integrating case studies into training programs, sharing lessons via pharmacy bulletins and internal platforms, and establishing medication safety alerts. Through new-employee orientation, continuing education, and inter-departmental exchanges, these efforts help prevent similar errors elsewhere and nurture an open, learning-oriented safety culture across the hospital. By consistently educating and advocating, pharmacists turn one-time RCA outcomes into a sustained driver of organizational improvement, ultimately reshaping the institution’s safety ecosystem.
In summary, the four pharmacist roles in RCA form a progressive path from technical core to strategic leader. This model demands that modern pharmacists possess not only expert knowledge but also systems thinking, change management, communication, and leadership skills. By fulfilling this evolution, the pharmacy department can solidify its indispensable value within healthcare quality and safety systems, thereby offering stronger protection for patient safety32.
DATA AVAILABILITY:
All data generated or analyzed during this study are available at the URL: https://zenodo.org/records/23027239.

Figure 1: Four-stage closed-loop management framework for pharmacy-led root cause analysis of medication safety events. The process begins at the Initial stage and proceeds through the preparation and launch phase, cause analysis phase, plan development and implementation phase, and effect evaluation and feedback phase. If the expected effect has been achieved (Yes), the results of the improvement are documented, and the process ends. If the expected effect has not been achieved (No), opportunities for improvement are identified, and the process returns to the Preparation and Launch Phase, forming a continuous improvement cycle. Please click here to view a larger version of this figure.

Figure 2: Fishbone diagram for organizing candidate contributing factors to medication safety events. Factors are grouped into six categories: Personnel (understaffing, lack of training, fatigue due to overwork, and ineffective communication), Method (flaws in the dispensing process, inconsistent standards, and ineffective verification mechanisms), Material (similar drug appearances, unclear labeling, and improper storage conditions), Machine (malfunction of automated packaging machines and information system defects), Environment (disruptive pharmacy layout, insufficient lighting, and noisy work environment), and Management (weak safety culture, biased performance evaluation orientation, and lack of quality monitoring indicators). The central arrow represents the medication-use process, and the other arrows indicate the potential influence of these factors on medication safety events. Please click here to view a larger version of this figure.