01Principles and purposeThe professional or clinical skill and the decisions it supports.
Clinical audit is one QI method. HQIP defines it as a quality-improvement cycle involving measurement of healthcare effectiveness against agreed and proven standards, action to bring practice in line and further measurement. An audit criterion states what should happen to whom and under what circumstances. A standard is the target level of compliance. Standards need an authoritative evidence source and justified exceptions; setting every target at 100% can be inappropriate when contraindication, decline or clinical judgement are legitimate.
Choose the project type from the question and activity. Research seeks new generalisable knowledge. Clinical audit compares care with an explicit standard. Service evaluation judges how an existing service performs without determining a new standard of care. QI tests changes in a local system. These categories can overlap in methods, and publication does not itself turn QI into research. Use the organisation’s governance, information and ethics routes before data collection.
Map the current process with people who do the work and receive the service. A simple flow map may reveal that a result reaches the inbox but no one owns recall, or that patients receive separate appointments they cannot attend. Cause-and-effect diagrams and five-whys questioning can generate hypotheses, but they do not prove a root cause. Prioritise modifiable causes supported by data and avoid blaming individuals for a system that makes the safe action difficult.
Write a SMART aim with scope and time: “Increase the proportion of eligible patients with completed, reviewed and communicated monitoring from 54% to 85% within twelve weeks, without increasing urgent appointment waits.” The aim should be ambitious enough to matter and realistic enough to test. Avoid embedding the proposed solution in the aim, because a reminder template may fail while another change succeeds.
The Model for Improvement uses three questions: What are we trying to accomplish? How will we know a change is an improvement? What change can we make that will result in improvement? A driver diagram links the aim to primary system drivers, secondary drivers and candidate changes. It is a theory of change, not proof. Update it when PDSA learning contradicts the original assumptions.
Build a measure family. Outcome measures represent the result that matters, such as harm, control or patient experience. Process measures show whether the intended work occurred. Balancing measures detect displacement or harm, such as increased workload, waiting time or overtreatment. Structure measures describe capacity. Use operational definitions specifying numerator, denominator, inclusion, exclusion, data source, frequency and owner so measurement is reproducible.
PDSA is experimental learning at local scale. Plan the change, prediction, who, where, when and data. Do the smallest useful test and record what departed from plan. Study results against the prediction, including qualitative feedback. Act by adapting, adopting or abandoning and plan the next cycle. A cycle written retrospectively after full rollout misses the method’s protection: learning before exposure of the whole system.
Clinical audit follows a related cycle. Select a priority; define evidence-based criteria and standards; determine population, sample and exclusions; collect reliable data; compare results; agree specific actions with owners and deadlines; implement; and re-audit. Re-audit should use comparable definitions and enough time for change to operate. If performance improves but misses target, investigate mechanism and iterate rather than declaring failure or changing the denominator.
Sampling must answer the project question. A census may be practical for a small register. A consecutive sample reduces cherry-picking. Random sampling can improve representativeness. Convenience samples may be useful for early PDSA learning but cannot support broad claims. Report dates, setting, denominator, exclusions, missingness and data quality. A percentage without counts can exaggerate change in small samples: 50% to 100% could mean one of two to two of two.
Patient involvement changes both aim and design. Patients may identify that the problem is not missed blood tests but repeated travel, unclear messages or no explanation of results. Co-production means sharing influence, not asking for approval after the intervention is fixed. Use accessible engagement and compensate contributions where policy allows. Include experience or burden among measures and communicate findings back to participants.
Sustainability requires incorporation into ordinary work: named ownership, training, induction, electronic configuration, supplies, policy and ongoing measurement. Test under different staff, days and demand before spread. A successful pilot may depend on one enthusiastic clinician. Create a control plan stating what will be monitored, how often, by whom and what threshold triggers action. Share methods and limits honestly so another site can adapt rather than copy blindly.
Key points
- Quality improvement is systematic work to improve patient outcomes, experience and service performance; clinical audit is a QI cycle that measures care against agreed evidence-based standards and remeasures after action.
- Start with a specific patient or system problem, involve affected patients and staff, understand the current process and define a time-bound aim rather than beginning with a favoured solution.
- The Model for Improvement asks what the team is trying to accomplish, how it will know a change is an improvement and what change may produce improvement.
- Use outcome measures for patient or system effect, process measures for whether the change occurs, and balancing measures for unintended consequences.
- PDSA tests a change on a small scale: predict and plan, do while recording deviations, study data against the prediction, then act by adopting, adapting or abandoning.
- Clinical audit needs explicit criteria, target standards, an eligible denominator, reliable data, action on gaps and re-audit; data collection alone does not close the loop.
- Research asks what should work and often seeks generalisable knowledge; audit asks whether care meets a standard; service evaluation describes current service; governance review determines the route, not the project label alone.
- Protect confidentiality, minimise data, record decisions, report safety concerns promptly and publish negative or neutral learning within the team rather than selecting only successful cycles.
02Situations and prioritiesThe context, relevant information and actions that matter most.
Baseline measurement and recommendations without implemented change and repeat measurement do not demonstrate completed clinical audit.
Choosing education, a template or an alert before defining the problem and mechanism risks activity without improvement.
Changing exclusions, denominator or documentation can improve the reported percentage without improving patient care.
Ordinary fluctuation around a stable process should not trigger a new reaction to every data point; examine the pattern over time.
A faster pathway may increase staff interruption, overtreatment, cost or delay elsewhere unless balancing measures are tracked.
A change dependent on one person, protected time or manual rescue may disappear when spread into routine conditions.
03Assessment and interpretationHow to gather information, assess the situation and recognise uncertainty.
Consider the information, its meaning and its limitations before deciding what follows.
- 01
Baseline process map - Why
- Locate delays, duplication, handoffs and failure points before choosing change.
- Interpretation and limitations
- Map actual work with staff and patients; policy diagrams may not represent what happens under real demand.
- 02
Audit criteria and standard - Why
- Define evidence-based expected care and target compliance.
- Interpretation and limitations
- Specify eligible population, exceptions and authoritative source; justify targets below or at 100% rather than choosing convenience.
- 03
Operational measure set - Why
- Make outcome, process and balancing data reproducible.
- Interpretation and limitations
- Name numerator, denominator, exclusions, source, frequency and owner and keep definitions stable across cycles.
- 04
Run chart or time series - Why
- Distinguish sustained change from isolated before-and-after variation.
- Interpretation and limitations
- Plot in sequence, annotate interventions and examine denominator or external changes before attributing cause.
- 05
Governance classification - Why
- Select the appropriate audit, QI, evaluation, research and information route.
- Interpretation and limitations
- Base classification on aims, intervention, allocation and data use, and seek organisational advice when boundaries are uncertain.
04Worked approachesCases with ordered reasoning, an action and a check of the outcome.
01Worked example: monitoring-result loopComplete a measurable PDSA and re-auditBaseline review finds 27 of 50 eligible high-risk medicine monitoring episodes were completed, reviewed and communicated within the locally specified interval.+
- 1Define the operational measure as completed plus clinician-reviewed plus patient-communicated episodes divided by all eligible episodes; validate the 54% baseline and map failure at test booking, result routing and recall.
- 2Set a twelve-week aim of 85%, co-design candidate changes and predict that a daily named inbox owner plus one combined reminder will reduce unowned results without increasing urgent wait time.
- 3Run the first PDSA with one clinician and ten due patients for one week, record deviations and measure completion, patient contacts and staff minutes; adapt reminder wording and backup ownership from the findings.
- 4The final action is staged adoption only after successive cycles show benefit; re-audit a comparable 50-episode cohort and verify sustainability with a run chart, patient feedback, urgent-wait balancing measure and a named monthly control-plan owner.
02Clinical auditMeasure, change and remeasure against a standardAn authoritative recommendation defines care expected for a local patient group.+
- 1Translate the recommendation into explicit criteria, justified target standards, denominator and exceptions.
- 2Collect a defensible sample, compare performance and investigate process causes with patients and staff.
- 3Implement owned actions with deadlines and re-audit using comparable definitions after the change has had time to work.
03PDSA cycleLearn safely before full implementationA candidate system change has a plausible mechanism but uncertain local effects.+
- 1Plan a small test with prediction, responsibilities, setting, duration and measures.
- 2Do the test and record actual execution, deviations, data and feedback.
- 3Study against prediction, then adopt, adapt or abandon and specify the next cycle.
04Sustain and spreadTest reliability under ordinary conditionsSeveral small cycles show a useful change in the pilot setting.+
- 1Test with different staff, days, demand levels and patient groups while monitoring outcome and balancing measures.
- 2Build ownership, training, electronic support, supplies and escalation into routine systems.
- 3Use a control plan and share context, failures and resource requirements before another team adapts the change.
05Feedback, follow-up and evidenceReview outcomes, seek feedback and identify what to improve.
- Plot the primary outcome and key process measure in time order at a frequency that supports action, with intervention annotations.
- Review balancing measures for workload, waiting, overtreatment, cost, continuity and unequal access at every scale-up decision.
- Repeat clinical audit with comparable definitions, population and sampling after enough time for the intervention to operate.
- Check data completeness, denominator stability and unintended documentation effects before claiming improvement.
- Use a control plan naming measure owner, review interval, expected range and the threshold that triggers investigation.
- Share results, neutral findings, failures and patient feedback with the team and affected people, then record the next action.
06Special situationsVariants, exceptions and circumstances that change the usual approach.
Measurement is for learning
Early PDSA data can be small and frequent when their purpose is to refine a change, provided claims remain proportionate.
A target needs exceptions
An evidence-based standard should state legitimate contraindication, refusal or clinical-judgement exclusions to avoid harmful gaming.
Documentation can be a proxy
Better coding may reveal care that already occurred, so pair record measures with patient-important process or outcome where possible.
Failure is useful evidence
A disconfirmed prediction clarifies mechanism and protects patients when the test is small, honestly studied and used to adapt.
Spread changes the system
A change that works with one clinician may fail across roles and demand, requiring new ownership, training and balancing measures.
Re-audit tests action
The second measurement should assess whether implemented changes altered care, not simply produce another report with new definitions.
07Common pitfallsFrequent interpretation and management errors.
- 01
Do not start with a preferred solution before verifying the problem and current process.
- 02
Do not call data collection a completed audit without change and remeasurement.
- 03
Do not set 100% as every target without considering evidence-based exceptions.
- 04
Do not report percentages without counts, denominator, dates and exclusions.
- 05
Do not use a before-and-after snapshot when repeated time-ordered data are feasible.
- 06
Do not omit balancing measures when a change can shift burden or harm elsewhere.
- 07
Do not write PDSA cycles retrospectively after full implementation and call them prospective tests.
- 08
Do not delay escalation of an immediate patient-safety concern until the project is complete.