Quality improvement in healthcare is a systematic, ongoing effort to make patient care safer, more effective, and more consistent. Rather than waiting for something to go wrong, it uses data to find weak spots in how care is delivered, tests small changes, and scales what works. The Agency for Healthcare Research and Quality describes it as reducing variation in processes and improving outcomes for both patients and the organizations that serve them.
The concept rests on a simple idea: healthcare delivery is made up of processes, and processes can be measured, analyzed, and redesigned. A hospital’s method for preventing infections, a clinic’s system for scheduling follow-up visits, a pharmacy’s workflow for catching drug interactions: all of these are processes with measurable results. Quality improvement treats those results not as fixed realities but as starting points for doing better.
The Six Aims of Quality Healthcare
In 2001, the Institute of Medicine outlined six aims that define what “better” actually means in healthcare. These have become the standard framework the industry uses to set goals and measure progress. Care should be:
- Safe: avoiding harm to patients from the care that’s meant to help them
- Timely: reducing waits and delays that can hurt outcomes
- Effective: providing treatments based on scientific evidence, not habit or guesswork
- Efficient: avoiding waste of equipment, supplies, energy, and time
- Equitable: delivering the same quality of care regardless of a patient’s gender, ethnicity, geography, or income
- Patient-centered: respecting individual preferences, needs, and values in clinical decisions
These six aims give quality improvement efforts a shared vocabulary. A hospital might launch one initiative focused on safety (reducing falls) and another focused on timeliness (shortening emergency department wait times), but both fall under the same quality improvement umbrella.
How It Differs From Quality Assurance
Quality assurance and quality improvement sound similar but work in opposite directions. Quality assurance is reactive: it asks, “Are we doing this procedure the way it’s supposed to be done?” It checks whether existing standards are being met, like auditing hand-hygiene compliance or reviewing whether surgical checklists were completed. Quality improvement is proactive: it asks, “How can we do this better?” It assumes current performance can always be raised, even when standards are technically being met. Quality assurance catches problems. Quality improvement prevents them and raises the ceiling on what’s possible.
The Plan-Do-Study-Act Cycle
The most widely used method for running a quality improvement project is the Plan-Do-Study-Act cycle, often called PDSA. It’s designed to test changes on a small scale before rolling them out broadly, which limits risk and builds evidence for what actually works.
In the Plan phase, a team identifies a specific problem, states a clear objective, predicts what they think will happen, and designs a small test. The Institute for Healthcare Improvement recommends scoping early cycles as small as possible. A real-world example: a clinic wanting to improve blood sugar management in diabetic patients might start by having one doctor ask one patient if they’d like more support, then scheduling a follow-up visit within a week.
In the Do phase, the team carries out the test exactly as planned, documenting any problems or surprises along the way and beginning to collect data. The Study phase is where they analyze those results and compare them to their predictions. Did the change produce the expected outcome? What was different from what they assumed? In the Act phase, they refine the change based on what they learned and prepare for the next cycle. In the diabetes example, the next cycle might expand to five patients and involve the scheduling team to manage the diabetes educator’s workload.
Each cycle builds on the last. A project might run through dozens of PDSA cycles before a change is ready for full implementation. This iterative approach is what makes quality improvement continuous rather than one-and-done.
Lean Six Sigma in Healthcare
Some organizations use a more data-intensive methodology called Lean Six Sigma, which combines two distinct philosophies. Lean, originally developed for Toyota’s manufacturing system in the 1950s, focuses on eliminating waste: unnecessary steps, redundant paperwork, idle time between handoffs. Six Sigma focuses on reducing variation, so patients receive consistently reliable care rather than care that depends on which nurse is on shift or which unit they’re admitted to.
Lean Six Sigma projects typically follow five phases: Define, Measure, Analyze, Improve, and Control. The team starts by defining the project’s objective and scope, then collects baseline data to understand current performance. In the Analyze phase, they use tools like cause-and-effect diagrams to trace problems back to their root causes. They then design and implement changes in the Improve phase, and finally put monitoring systems in place during the Control phase to make sure gains don’t slip away over time.
This approach tends to be used for larger, more complex problems, like redesigning how an entire emergency department manages patient flow, while PDSA cycles work well for smaller, faster tests of change.
Tools Teams Use to Find Root Causes
Quality improvement teams rely on a handful of visual tools to understand problems before jumping to solutions. Three of the most common are fishbone diagrams, Pareto charts, and process maps.
A fishbone diagram (also called an Ishikawa diagram) is a structured way to brainstorm all the possible causes of a problem. The “head” of the fish is the problem itself, and the “bones” branch out into categories like staffing, equipment, communication, and workflow. It forces a team to think broadly instead of fixating on the first explanation that comes to mind.
A Pareto chart applies the 80/20 rule: the idea that roughly 80% of problems come from 20% of causes. It displays causes as bars ordered from most to least frequent, with a line showing their cumulative effect. This helps teams focus their energy on the “vital few” factors that will yield the biggest improvement rather than spreading effort thin across every possible contributor.
A process map diagrams every step in a workflow as it actually happens, not as it’s written in a policy manual. Mapping reality often reveals duplicated steps, unnecessary delays, and decision points where things break down. These gaps between how a process is supposed to work and how it actually works are where many quality improvement projects find their biggest opportunities.
Measurable Results
Quality improvement isn’t theoretical. A large-scale initiative across 88 U.S. hospitals, published in The Joint Commission Journal on Quality and Patient Safety, tracked outcomes from 2021 to 2023 and found striking results. Overall mortality dropped by 23.4%, translating to 4,186 fewer deaths. Central line-associated bloodstream infections fell by 24.8%. Catheter-associated urinary tract infections dropped by 30.6%. MRSA bloodstream infections declined by 29%, and a common hospital-acquired intestinal infection fell by 35.1%. Acute kidney injury episodes during hospitalization dropped by 6.2%, representing 1,725 fewer events.
These numbers came from coordinated, sustained quality improvement work, not from new drugs or technology. They came from teams measuring their processes, identifying failures, testing changes, and holding gains.
Who Does This Work
Quality improvement is not a job for a single department. Effective initiatives include clinical leads who understand the care process, frontline staff (nurses, pharmacists, technicians) who carry out daily workflows and spot problems first, and people with data skills who can track whether changes are actually working. Leadership support matters because improvement projects often require shifting resources, changing schedules, or redesigning roles. Without organizational buy-in from the top, even well-designed projects stall.
The emphasis on frontline involvement is deliberate. The people closest to a process usually understand its failures best. Empowering nurses, medical assistants, and other team members to contribute ideas, not just implement decisions made by physicians or administrators, consistently produces stronger results.
How Quality Is Tracked and Reported
Healthcare quality isn’t just an internal exercise. It’s tied to how organizations get paid. The Centers for Medicare and Medicaid Services runs the Quality Payment Program, which directly links reimbursement to quality performance. Quality accounts for 30% of a provider’s final score under this program. Providers must report on at least six quality measures, including at least one outcome measure, covering a full 12-month performance period. They need to submit performance data for at least 75% of eligible patients for each measure. Measures that don’t meet this data completeness threshold score zero points.
On a broader scale, standardized measurement sets like HEDIS (Healthcare Effectiveness Data and Information Set), maintained by the National Committee for Quality Assurance, allow health plans to benchmark their performance against each other. HEDIS measures cover major public health concerns: cancer screening rates, blood pressure control, antidepressant medication management, follow-up after mental health hospitalization, and hospital readmission rates, among others. These metrics give both organizations and patients a way to compare quality across providers and identify where gaps exist.
Structure, Process, and Outcome
One framework that helps make sense of all these measurements was proposed by physician Avedis Donabedian over 50 years ago and remains foundational. He argued that healthcare quality can be evaluated across three dimensions: structure, process, and outcome. Structure refers to the setting where care happens: staffing levels, equipment, electronic health records, physical facilities. Process is what clinicians and staff actually do: whether they follow evidence-based protocols, how quickly they respond to test results, how well they communicate with patients. Outcome is what happens to the patient: whether they recover, develop complications, or end up back in the hospital.
Measuring all three dimensions matters because good outcomes alone don’t prove good quality (a patient might recover despite poor care), and good processes alone don’t guarantee good outcomes (some conditions are simply hard to treat). The interplay between structure, process, and outcome gives organizations a complete picture of where their quality stands and where improvement efforts should focus next.