The Context
Inpatient falls are one of the most common safety events tracked on medical and surgical units. They are also one of the most frequently used teaching examples in healthcare quality improvement, because the data is usually already being collected through incident reports and nursing documentation, and because the causes tend to cluster into a small number of recurring categories. Two published sources illustrate this well: a StatPearls quality improvement reference that walks through a Pareto chart built from inpatient fall data, and a peer reviewed figure showing a Pareto analysis of patient falls stratified by cause after the causes were first logged on a check sheet.
Neither source describes a full hospital-wide Six Sigma program. Both describe exactly the kind of small, local, tool driven analysis a Yellow Belt is trained to run: define the problem on one unit, collect simple counts, chart them, and act on the biggest bars first.
The Problem
A specific medical unit has a fall rate the charge nurse or unit manager is not happy with. Falls are already being reported through the incident system, but nobody has organized the reports by cause. Without that step, staff tend to guess: some blame bed alarms, some blame staffing, some blame patient confusion. Guessing leads to scattered fixes that do not move the number.
How a Yellow Belt Would Scope It
This is a Yellow Belt sized problem because it does not require a hospital-wide DMAIC charter, a control chart, or hypothesis testing. It requires:
- A clear, narrow problem statement: falls on this unit, over a defined recent period, not falls hospital-wide.
- A simple counting tool, not a new IT system.
- A basic chart that any nurse manager can read in a huddle.
- Countermeasures the unit can implement itself, without capital investment.
A Green Belt or Black Belt might extend this into a full DMAIC project with statistical process control on fall rates over time. A Yellow Belt project stops at organizing the data well enough to see where to act first.
Tools Applied, Phase by Phase
Define
The team states the problem in one sentence: falls on this unit are higher than the unit wants them to be, and the causes have not been sorted by frequency. No process map of the entire hospital is needed, just agreement on which unit and which time window to look at.
Measure: the check sheet
The causes for each fall are documented using a check sheet, which is then subjected to further analysis using a Pareto chart to find the vital few factors contributing to falls. In practice this means every fall report gets tagged with a cause category as it comes in, rather than being filed as a narrative note that has to be re-read later. This is the same discipline used on a factory floor check sheet: predefine the categories, then make a tally mark every time one occurs.
Analyze: the Pareto chart
Once enough fall records are tagged, the tallies are turned into a Pareto chart. The StatPearls quality improvement reference walks through exactly this construction using a fall dataset from a medical unit. The Pareto chart for inpatient falls shows five causes, with the left-side Y-axis displaying the number of falls attributed to each cause and the right-side Y-axis showing the cumulative percentage contribution of these causes. The point where the cumulative percentage line intersects the 80 percent reference line indicates the most vital causes for the project, with a dotted line marking the transition from vital few to trivial many.
In the published figure from the peer reviewed study, that same check sheet-to-Pareto sequence found that the most important factors for falls were patient general condition, loss of balance and dizziness. Those three categories, out of a longer list nurses might have brainstormed, are what actually deserve the unit’s limited time and attention.
Improve: standard work on the vital few
With the vital few identified, the countermeasures stay simple and unit-level: standard work for mobility assessment on admission, a visual cue at the bedside for patients flagged as unsteady, and a consistent hourly rounding script that checks for dizziness or disorientation. None of this requires capital spending or a hospital-wide policy change, which is exactly the kind of fix a single unit can pilot on its own.
Control: keep the chart visible
The Pareto chart is not a one-time artifact. It gets posted where the unit already huddles, and it gets refreshed as new falls are tagged, so staff can see whether the same three causes are still dominating or whether the mix has shifted after the countermeasures went in.
Quick reference: causes identified in the published Pareto analysis
| Rank | Cause category | Source |
|---|---|---|
| 1 | Patient general condition | Pareto chart of patient falls stratified by different causes |
| 2 | Loss of balance | Pareto chart of patient falls stratified by different causes |
| 3 | Dizziness | Pareto chart of patient falls stratified by different causes |
What the Result Was
The documented value of this approach is not a single dramatic before-and-after number, it is the shift from an undifferentiated list of possible causes to a ranked, evidence based short list. The fishbone diagram, Pareto chart, and process mapping tools enable healthcare teams to identify and prioritize the root causes of a problem and decide which aspects need to be acted on first. That prioritization is the actual deliverable of a Yellow Belt project: not a finished, permanent fix, but a data backed answer to “what should we work on first.”
A related case discussion of hospital fall data makes the same point about scope discipline: broad, multi-year datasets can be sliced by Pareto chart to see which age groups and which units account for most falls, which helps a team avoid spreading effort thin across every possible variable.
What a Trainee Should Take From It
- A check sheet only works if the categories are defined before data collection starts. Retrofitting categories onto old narrative notes is slower and less reliable.
- A Pareto chart’s value is the cumulative percentage line, not just the bars. That line is what tells you where the “vital few” cutoff actually falls, rather than guessing from the bar heights alone.
- The vital few cutoff is a judgment call informed by the data, not a fixed rule. The StatPearls example notes the vital few could reasonably be the first two or three causes depending on the resources available for the project.
- Yellow Belt scope means picking a fix the unit can run itself: standard work, visual cues, rounding scripts, not new software or capital equipment.
- The chart should stay alive after the analysis. Posting it and updating it is what turns a one-time study into a standing habit of looking at data before acting.
