Direct answer: A strong health care quality-improvement plan defines one measurable performance problem, establishes a baseline, sets a specific aim, selects process, outcome, and balancing measures, analyzes likely causes, proposes evidence-based changes, tests those changes through a structured method such as Plan-Do-Study-Act, assigns responsibilities, and explains how improvement will be sustained. A list of desirable actions is not a quality-improvement plan unless it shows how the organization will learn whether the change works.
The central reasoning chain is problem → baseline → aim → measures → causes → change ideas → tests → implementation → sustainability. Every intervention and measure should connect to the stated problem.
Capella’s current health care administration curriculum includes quality management, operations assessment and improvement, research methodology, and the application of continuous improvement processes to organizational and patient outcomes.[1] This guide is independent educational support. Use the current assessment instructions and fictionalize or de-identify examples when real organizational information is restricted.
General summary: A health care quality improvement plan defines a measurable performance gap, identifies contributing process factors, selects an evidence-based improvement strategy, assigns responsibilities and resources, and explains how implementation and outcomes will be monitored. The plan should connect every proposed action to the same clearly defined quality or safety problem.
Educational and professional boundary: This independent guide supports academic research, analysis, planning, writing, and revision. It provides no patient-specific medical or legal advice and does not replace current course instructions or professional judgment.
What a health care quality-improvement plan must accomplish
A complete plan should answer:
- What process or outcome is not performing as expected?
- Who is affected, in which setting, and over what period?
- What baseline evidence shows that improvement is needed?
- What measurable aim will define success?
- Which changes are expected to improve the system?
- How will the team test and measure those changes?
- What risks, unintended effects, and equity concerns require monitoring?
- How will the improved process be maintained?
Distinguish quality improvement from general problem solving
Quality improvement is a systematic, data-informed effort to change processes and produce better, more reliable results. CMS describes quality improvement as a framework for systematically improving care by standardizing processes and structures, reducing variation, and improving outcomes.[2]
A general recommendation such as “train staff” may be part of a plan, but QI asks additional questions: Which behavior should change? What process barrier caused the problem? How will the team test the training? Which measure will show whether the change improved performance rather than simply increasing attendance?
Define one specific improvement problem
A weak statement says, “Medication safety needs improvement.” A stronger statement identifies the setting, population, current performance, gap, and consequence:
Problem statement pattern: In [setting], [population or process] currently experiences [measured performance] compared with [desired benchmark or standard], creating [quality, safety, cost, access, or experience consequence].
Example: “In a fictional ambulatory clinic, only 61% of high-risk medication reconciliations are completed within 24 hours of a care transition, creating preventable discrepancies and follow-up work.”
Do not include invented national benchmarks. Use an assigned benchmark, an authoritative measure, or clearly label a local target as a proposed goal.
Establish a credible baseline
The baseline is the starting level of performance. Define the numerator, denominator, data source, period, inclusion and exclusion rules, and missing-data approach. A baseline based on ten convenient records may not represent normal performance.
Quality measurement can establish initial performance and then track results after an intervention begins.[3] Explain whether the data come from electronic health records, incident reports, audits, patient surveys, staffing systems, or another source. Also discuss the reliability and timeliness of the data.
Write a measurable aim statement
The Institute for Healthcare Improvement’s Model for Improvement begins with the question, “What are we trying to accomplish?” A useful aim specifies what will improve, by how much, by when, for whom, and where.[4]
Example: “Increase completion of high-risk medication reconciliation within 24 hours of a care transition from 61% to 90% in the fictional ambulatory clinic by December 31, while maintaining an average documentation time below 12 minutes.”
The last clause introduces a balancing concern. A fast process that creates excessive burden or new errors is not a complete improvement.
Select outcome, process, and balancing measures
AHRQ describes structure, process, and outcome measures as major categories used to assess health care quality.[5] A practical QI plan should also consider balancing measures.
| Measure type | Fictional measure | Definition | Why it matters | Frequency |
|---|---|---|---|---|
| Outcome | Medication discrepancies discovered after transition | Number of confirmed discrepancies per 100 eligible transitions | Reflects the patient-safety result the team wants to reduce | Monthly |
| Process | Timely reconciliation completion | Eligible transitions completed within 24 hours ÷ all eligible transitions | Shows whether the new workflow is being followed | Weekly |
| Process | Pharmacy escalation completed | High-risk cases reviewed according to the escalation rule | Tests a key change component | Weekly |
| Balancing | Average documentation time | Mean minutes required per completed reconciliation | Detects excessive workload or delay | Weekly |
| Balancing | Patient follow-up complaints | Number related to duplicate or confusing medication contacts | Detects unintended experience problems | Monthly |
Define each measure precisely. Otherwise, apparent improvement may reflect a changed definition rather than a changed process.
Analyze the process and likely causes
Do not jump from the problem directly to a solution. Map the current workflow and identify where delays, rework, ambiguity, missing information, or handoff failures occur. Useful tools include:
- process map;
- cause-and-effect diagram;
- five-whys analysis;
- Pareto chart;
- failure-mode review;
- stakeholder interviews;
- direct observation;
- audit of a small set of cases.
The cause analysis should focus on the system rather than blaming individuals. For example, late reconciliation may reflect unclear ownership, inconsistent referral data, poorly timed alerts, role duplication, or an inaccessible medication history.
Choose evidence-based change ideas
Each proposed change should address a documented cause. Possible fictional changes include:
- a standardized transition checklist;
- clear assignment of responsibility at the time of scheduling;
- an electronic work queue for high-risk patients;
- pharmacist escalation criteria;
- patient-friendly medication verification before the visit;
- daily exception review;
- feedback to teams using run-chart data.
“Educate all staff” is rarely sufficient by itself. Education may be needed, but the plan should also address workflow, technology, accountability, and environmental conditions.
Use the Model for Improvement and PDSA cycles
The IHI Model for Improvement combines three questions—what the team is trying to accomplish, how it will know a change is an improvement, and what change can be made—with iterative tests of change.[6]
A Plan-Do-Study-Act cycle should be small enough to learn quickly:
- Plan: predict what will happen, define the test, participants, measures, and timing.
- Do: run the test and document unexpected events.
- Study: compare results with the prediction and examine the data.
- Act: adopt, adapt, or abandon the change and plan the next cycle.
Example: Test the high-risk reconciliation work queue with one clinician and one medical assistant for five transitions over three days before implementing it across the clinic.
Plan stakeholders, roles, and governance
Identify the sponsor, improvement lead, data analyst, process owner, frontline staff, patient or family representative, technology support, and compliance or safety roles. A RACI matrix can clarify who is responsible, accountable, consulted, and informed.
Stakeholder engagement should affect the design, not merely appear as a list. Frontline employees may identify workflow barriers, patients may identify confusing communication, and leaders may address resource or policy constraints.
Address equity and unintended consequences
Quality improvement should examine whether the problem or proposed change affects groups differently. Consider language access, disability, digital access, transportation, health literacy, insurance, work schedules, and other relevant conditions. Stratified data may reveal that an overall average hides a persistent gap.
Also monitor unintended effects. A reminder system may improve completion but create alert fatigue. Centralizing a process may improve consistency but delay urgent exceptions. Balancing measures make these trade-offs visible.
Build an implementation and communication plan
Describe:
- the sequence of tests and scale-up;
- resources, technology, and training;
- policy or procedure changes;
- communication channels;
- data-review schedule;
- decision rules for adapting the plan;
- risk management and escalation;
- timeline and responsibility.
A simple phased plan—pilot, refine, expand, standardize—usually provides more learning than a single organization-wide launch.
Plan for sustainability
Sustainability requires the improved process to become part of normal work. Consider:
- standard operating procedures;
- orientation and refresher training;
- ownership after the project ends;
- automated or routine measurement;
- auditing and feedback;
- resource and staffing requirements;
- policy alignment;
- review when performance declines.
A plan that reaches the target for one month but cannot be maintained has not fully solved the problem.
Recommended structure for the written plan
- Executive summary.State the problem, aim, main changes, and expected benefit.
- Background and baseline.Define the setting, gap, evidence, and significance.
- Aim and measures.Present operational definitions and data sources.
- Cause analysis.Explain the process barriers and evidence.
- Change strategy.Connect each intervention to a cause.
- Testing and implementation.Describe PDSA cycles, roles, timeline, and resources.
- Equity, risk, and balancing measures.Monitor unintended effects.
- Sustainability and evaluation.Explain how gains will be maintained and reviewed.
Use the Health Care Administration hub for related guidance and the editing and revision resources when checking alignment among the aim, measures, causes, and changes.
Common quality-improvement plan mistakes
- Choosing a broad issue without a measurable performance gap.
- Using no baseline or an undefined denominator.
- Writing an aim that is not time-bound or measurable.
- Using only an outcome measure and no process measure.
- Proposing education without addressing workflow causes.
- Implementing at full scale before testing.
- Ignoring balancing measures and equity.
- Blaming staff rather than analyzing the system.
- Omitting ownership, resources, or sustainability.
- Presenting invented organizational data as factual.
Final quality checklist
- The problem and population are specific.
- The baseline definition is reproducible.
- The aim states how much improvement is expected and by when.
- Outcome, process, and balancing measures are defined.
- Causes are analyzed before changes are selected.
- Each change addresses a documented cause.
- PDSA tests are small and measurable.
- Roles, resources, and timeline are clear.
- Equity and unintended effects are monitored.
- Sustainability and ongoing ownership are explained.
How should policy and stakeholders influence a quality improvement plan?
Use the health care policy analysis guide to determine how laws, regulations, reimbursement rules, and organizational policies affect the proposed improvement. Apply the stakeholder analysis guide to identify influence, resistance, communication needs, and implementation responsibilities. Use the balanced scorecard guide when the plan requires linked performance objectives and measures. Return to the Health Care Administration hub for connected assignment formats.
Frequently asked questions
Is quality improvement the same as research?
They may use related methods, but their primary purposes, oversight, generalizability, and context can differ. Follow the assignment and organizational guidance rather than assuming that one label automatically applies.
How many measures should I include?
Use enough to determine whether the outcome improves, whether the process changes, and whether unintended harm occurs. A small, clearly defined set is usually more useful than many poorly specified indicators.
Can I use PDSA for the entire plan?
PDSA is a testing method within a wider improvement plan. The plan still needs a problem definition, aim, measures, cause analysis, governance, implementation, and sustainability.
What if no baseline data are provided?
Explain what data should be collected, how the measure would be defined, and which assumptions are fictional. Do not invent precise organizational results.
Should the target always be 100%?
Not necessarily. The target should be meaningful, evidence informed, feasible, and sensitive to exclusions or clinical exceptions.
Sources and further reading
- Capella University: Health Care Administration Leadership courses.
- Centers for Medicare & Medicaid Services: Quality Measurement and Quality Improvement.
- AHRQ: Uses of Quality Measurement.
- Institute for Healthcare Improvement: Setting Aims.
- AHRQ: Types of Health Care Quality Measures.
- Institute for Healthcare Improvement: Model for Improvement.