The Institute of Medicine defines quality of care as the degree to which health services for individuals and populations increase the likelihood of desired health outcomes and are consistent with current professional knowledge. Quality improvement (QI) is the continuous, data-driven work of making care safer, more effective, and more reliable by changing systems and processes, not by blaming individuals.

Landmark reports that shaped US quality work

• To Err Is Human (Institute of Medicine, 1999) — estimated that tens of thousands of hospital deaths each year were caused by preventable errors and argued that most errors come from faulty systems
• Crossing the Quality Chasm (IOM, 2001) — six aims for care, remembered as STEEEP: Safe, Timely, Effective, Efficient, Equitable, Patient-centered

Related terms

The management control process (the "controlling" function) is the same logic applied by a nurse manager:

1. Establish standards (measurable, realistic, understood and accepted by staff)
2. Measure actual performance
3. Compare performance with the standard and analyze the cause of any gap
4. Take corrective action, then re-measure; if the result meets the standard, maintain and monitor (and consider raising the target)

Control can be feedforward (preventive, before the work — e.g., orientation, protocols), concurrent (real-time — e.g., an electronic early-warning alert), or feedback (after the fact — e.g., monthly error rates compared with the budget or target). Effective control is timely, cost-effective (the cost of control should not exceed its benefit), and acceptable to staff. Cultural (normative) control relies on shared values and trust rather than formal rules.

Donabedian's structure–process–outcome model

A process improvement only matters if it improves outcomes: when medication errors fall 20%, also check whether harm, length of stay, or satisfaction changed and whether other measures (balancing measures) got worse.

Model for Improvement and PDSA (Institute for Healthcare Improvement; based on Shewhart and Deming). Three questions come first: What are we trying to accomplish (aim)? How will we know a change is an improvement (measures)? What change can we make that will result in improvement? Then test changes with rapid PDSA cycles:

PDCA (Plan-Do-Check-Act) is the older name for the same cycle.

Lean (from the Toyota Production System) removes waste — anything that does not add value for the client (waiting, unnecessary motion, overprocessing, excess inventory, defects, transport). Tools: value stream mapping, 5S workplace organization, standard work, visual management.

Six Sigma reduces variation and defects using the DMAIC steps: Define, Measure, Analyze, Improve, Control. The goal level is about 3.4 defects per million opportunities. "Lean Six Sigma" combines both.

Root cause analysis (RCA) is retrospective: after an event, a multidisciplinary team asks "what happened, why, and how do we prevent it?" to find system causes. Failure mode and effects analysis (FMEA) is prospective: before a process is used (or when it is redesigned), the team maps each step, lists what could fail, and scores each failure mode for severity, occurrence, and detectability; multiplying the three gives a risk priority number (RPN) that ranks what to fix first. Each factor is usually scored 1–10, so the RPN ranges from 1 to 1,000. Example: severity 8 × occurrence 5 × detectability 6 = 240. Fix the highest RPNs first, and also any failure mode with very high severity even if its RPN is lower.

Common QI tools

Typical unit QI project sequence

1. Identify the problem from data (incident reports, indicators, satisfaction surveys, audits)
2. Analyze the data first — which shifts, which clients, which step — before choosing a solution
3. Form a team that includes frontline staff who do the work
4. Set an aim that is specific and measurable, with a time frame
5. Test changes with PDSA cycles; measure process, outcome, and balancing measures
6. Standardize what works (protocols, checklists, order sets), spread, and keep monitoring

Nursing-sensitive indicators commonly tracked on units include falls and falls with injury, hospital-acquired pressure injuries, CLABSI, catheter-associated urinary tract infection (CAUTI), restraint use, nursing hours per patient day, skill mix, and RN satisfaction.

Staff nurse

• Follow evidence-based protocols and bundles (the "process" that produces outcomes)
• Report errors, near misses, and unsafe conditions — the data for improvement
• Take part in audits, huddles, unit councils, and PDSA tests of change; suggest improvements from the bedside
• Understand the unit's dashboard and what the numbers mean

Nurse manager

• Set measurable standards with staff; monitor indicators; lead or sponsor QI teams
• Use data to decide; protect time and resources for improvement
• Maintain a nonpunitive climate so problems are reported and fixed
• Recognize and share successes

Quality and Safety Education for Nurses (QSEN) lists six competencies expected of every nurse: patient-centered care, teamwork and collaboration, evidence-based practice, quality improvement, safety, and informatics.

• Confidentiality: QI data containing client information must follow HIPAA privacy rules (minimum necessary use, secure storage). Reports shared with teams are de-identified where possible.
• Peer review and QI protections: most states protect the deliberations and records of quality and peer-review committees from discovery in lawsuits so that staff can analyze problems openly. Patient safety work product submitted to a federally listed Patient Safety Organization is privileged and confidential under the Patient Safety and Quality Improvement Act of 2005. Facts documented in the medical record are not protected.
• QI vs. research ethics: a project designed to produce generalizable knowledge for publication may need institutional review board (IRB) review; routine local QI usually does not, but organizations have their own screening process.
• Ethical basis: the ANA Code of Ethics holds nurses responsible for contributing to safe, quality practice environments. Blaming individuals for system failures is both ineffective and unjust.

Case 1 — Choosing the measure. A unit wants to know whether its new CLABSI bundle works. The manager tracks both bundle compliance (process) and the CLABSI rate per 1,000 central-line days (outcome). Why: process compliance alone does not prove clients are better off; the outcome shows real benefit.

Case 2 — Data before solutions. Satisfaction scores for "nurses explained things in a way you could understand" are low. The team's first step is to break down the data by shift, unit, and topic and to listen to clients, not to schedule mandatory lectures. Why: QI decisions are data-driven; the cause must be known before an intervention is chosen.

Case 3 — Prospective vs. retrospective. A hospital will install new smart infusion pumps next quarter. The safety team runs an FMEA on the workflow before go-live. Why: FMEA anticipates failures before harm occurs; RCA is used after an event.

Case 4 — The Do step. A charge nurse suggests bedside shift report to reduce missed information. The manager pilots it for two weeks on one hallway and collects data. Why: PDSA tests changes small and fast before spreading them.

• Confusing process with outcome: hand hygiene compliance, fall-risk screening, and time-outs are processes; infection rates and injuries are outcomes; staffing and equipment are structure
• Thinking CQI looks for the person at fault — it looks for weak processes
• Mixing up RCA (after the event, retrospective) and FMEA (before, prospective)
• Placing "Do" as full implementation — it is a small-scale test
• Skipping the first control step: standards must be set (and be measurable) before performance can be compared
• Believing QA and CQI are the same: QA checks against minimum standards; CQI improves continuously
• Ignoring balancing measures (e.g., fewer falls because of more restraint use is not an improvement)
• Choosing an RCA team of managers only — it must be multidisciplinary (nursing, medicine, pharmacy, other involved departments) and include people who know the process; its job is to find system causes, not to judge individuals

• Donabedian: structure (resources), process (care given), outcome (client result — e.g., CLABSI rate, falls with injury)
• PDSA: Plan → Do (small test) → Study → Act; driven by the Model for Improvement's three questions
• Lean = remove waste; Six Sigma = reduce variation with DMAIC
• RCA = retrospective, system causes, multidisciplinary; FMEA = prospective, risk priority number
• Pareto = vital few causes; fishbone = categories of causes; control chart = common vs. special-cause variation
• CQI is continuous, data-driven, team-based, client-focused, and nonpunitive
• Control process: set standards → measure → compare → correct
• Benchmarking compares with best performers to close the gap
• IOM aims: STEEEP; QSEN includes quality improvement as a core nursing competency
• Always pair a process change with an outcome measure and a balancing measure