Using the SQUIRE Guidelines for Reporting Healthcare Improvement Projects

Why This Topic Matters

Effective reporting of healthcare improvement projects offers multiple benefits. It allows others to understand what was done, why it was done, the impact achieved, and the underlying mechanisms of change. Without clear and detailed reporting, valuable lessons can be lost, and successful interventions may not be adopted elsewhere. For those undertaking quality improvement (QI) work, especially junior doctors and trainees, presenting improvement projects formally can be a powerful way to demonstrate leadership, analytical skills, and commitment to patient care, supporting career progression and portfolio development.

Furthermore, for an NHS committed to continuous learning and evidence-based practice, robustly reported QI provides a rich source of practical knowledge. It bridges the gap between research and practice, showing how improvements are implemented in complex healthcare settings.

Practical Explanation: What are the SQUIRE Guidelines?

The SQUIRE Guidelines were developed to improve the quality and completeness of reporting for healthcare improvement studies. They acknowledge that QI projects often unfold iterativel, in complex adaptive systems, which differentiates them from explanatory randomised controlled trials. SQUIRE provides a 17-item checklist and explanatory material to guide authors through the essential components of their reports.

The guidelines aim to ensure that reports contain enough detail for readers to:

• Understand the context in which the improvement project took place.
• Grasp the problem being addressed and the rationale for the intervention.
• Appreciate the methods used to implement and study the change.
• Evaluate the results and their implications.
• Consider the project's transferability to alternative settings.

SQUIRE 2.0 is the current version, refining the original guidelines to be more user-friendly and to better reflect the evolving landscape of improvement science. It embraces the idea that improvement is often a journey of discovery rather than a linear experiment.

Common Pitfalls in Improvement Reporting

When reporting improvement work, several common issues can hinder clarity and utility:

• Lack of Context: Failing to describe the setting, organisational culture, or specific challenges that influenced the project makes it difficult for others to understand the problem or replicate the solution.
• Vague Aims: Stating aims too broadly (e.g., 'to improve patient care') without measurable, specific goals (e.g., 'to reduce catheter-associated urinary tract infections by 25% in Ward X within 6 months') makes it impossible to assess success.
• Insufficient Detail on Interventions: Describing 'what' was done without explaining 'how' it was done, 'who' was involved, or 'why' particular changes were chosen. This is particularly important for others to learn from or adapt the approach.
• Poor Data Presentation: Presenting data without appropriate run charts, statistical process control (SPC) charts, or clear explanations of measures and results. A common mistake is reporting only endpoint comparisons without showing the trend over time.
• Limited Discussion: Not adequately discussing the limitations of the project, the challenges encountered, the generalisability of findings, or the implications for future practice and research.
• Confusing QI with Research: Not distinguishing between ethical review processes for QI (usually local governance approval) versus formal research ethics committee (REC) approval for research. This can lead to delays or misinterpretation of ethical oversight.

Step-by-Step Approach: Applying SQUIRE to Your Report

The SQUIRE 2.0 checklist is organised into several sections, mirroring the structure of a typical scientific paper. Here's how to approach each key section:

Title and Abstract

• Title: Make it informative, concise, and include keywords like 'quality improvement' or 'patient safety'.
• Abstract: Summarise the project's background, local problem, methods, results, and conclusions. This is often the first, and sometimes only, part people read. Ensure it accurately reflects the full report.

Introduction

• Problem Description: Clearly articulate the specific healthcare problem, its local impact, and why it is a priority for improvement. Use national or local data to support its significance (e.g., audit findings, NHS England data, NICE guidance).
• Available Knowledge: Briefly summarise what is known about the problem and relevant interventions from the literature or similar improvement projects. What gap does your project address?
• Rationale: Explain why your chosen intervention approach was considered appropriate for your context.
• Specific Aims: State your aims clearly, often using SMART (Specific, Measurable, Achievable, Relevant, Time-bound) principles. Include process and outcome measures where appropriate.

Methods

• Context: Describe the setting, staff involved, patient population, and relevant organisational details. This helps others understand the local 'ecology' of your project.
• Intervention: Detail the specific changes made, the theories or models used (e.g., Plan-Do-Study-Act (PDSA) cycles, Lean, Six Sigma), and how the intervention was developed and implemented. Explicitly describe successive iterations if using PDSA cycles.
• Study of the Intervention: Clearly state your measurements (what was measured, how, and when), data collection methods, and analytical approaches. Explain how you assessed the impact of your intervention. Include ethical considerations and governance approvals.
• Ethical Considerations: Confirm that the project was conducted in line with local governance, clinical audit, or QI approval processes. Most QI work does not require formal REC approval but local review is essential.

Results

• Process and Outcome Data: Present your data clearly, often using run charts or SPC charts to show trends over time. Describe what happened to your key measures. Explain any contextual factors or major changes that coincided with your results.
• Unexpected Findings: Report any unintended consequences, positive or negative.
• Limitations: Be transparent about the limitations of your project, such as sample size, data quality, duration, or generalisability.

Discussion

• Summary of Findings: Reiterate your main findings in relation to your aims.
• Interpretation: Discuss the meaning of your findings. Why did the intervention work (or not work)? What did you learn about the system or process?
• Comparison with Other Studies: How do your findings compare to previous work or published literature?
• Implications: What are the practical implications for practice, policy, or future improvement work in your own setting or elsewhere? What are the next steps?

Conclusion

• Briefly summarise your main conclusions and key messages.

Additional Sections

• Funding: Acknowledge any funding sources.
• Acknowledgements: Thank individuals or teams who contributed significantly.

Example in Clinical Practice

Imagine a junior doctor team on a busy medical ward aiming to reduce the time from 'prescription' to 'first dose administered' for new intravenous antibiotics. They identify delays in Pharmacy dispensing and nursing administration. Their project using SQUIRE might look like this:

• Title: Reducing Time to First Dose Intravenous Antibiotics on a Medical Ward: A Quality Improvement Project
• Introduction: Describe the problem of delayed IV antibiotics, its link to patient outcomes (e.g., sepsis), and local audit data showing a median delay of 4 hours. Aim: To reduce median time to first dose IV antibiotics to under 60 minutes within 3 months.
• Methods: Context: 30-bed acute medical ward in a DGH. Intervention: Implemented three PDSA cycles including a 'STAT' sticker system for acute IVs, a dedicated nurse for medication rounds, and a daily pharmacy liaison huddle. Study of Intervention: Data collected prospectively on 50 consecutive new IV antibiotic prescriptions weekly using a local audit tool. Run chart used for analysis.
• Results: Run charts showing a gradual reduction in median time from 240 minutes to 55 minutes, with three points below the target median. Specific PDSA cycles correlated with drops in time. Challenges included initial staff resistance and inconsistent use of the 'STAT' sticker.
• Discussion: Interprets the key drivers of improvement (e.g., dedicated nurse time, improved communication), compares findings to national antimicrobial stewardship guidelines, discusses limitations (single ward, short duration), and highlights sustainability efforts.
• Conclusion: The project successfully reduced time to first dose IV antibiotics, demonstrating the effectiveness of targeted process changes.

How Lazomis Can Help

Lazomis provides structured tools that can significantly assist in applying the SQUIRE Guidelines to your improvement projects:

• Project Setup Templates: The Lazomis QI Project Setup tool guides you through defining your project aim, context, and measures, directly aligning with SQUIRE's Introduction and Methods sections.
• Data Collection and Visualisation: Our data collection forms and automated run charts and statistical process control (SPC) charts simplify the 'Study of the Intervention' and 'Results' sections, ensuring you present data accurately and effectively.
• Reporting Frameworks: Lazomis offers report templates and prompts designed with SQUIRE principles in mind, helping you structure your narrative and ensure all essential elements are covered for internal reports or external submissions.
• Collaboration Features: Facilitate team-based reporting, allowing multiple contributors to input sections of the report, ensuring comprehensive detail and shared understanding.

By systematising your QI workflow and structuring your data and narrative, Lazomis helps you produce SQUIRE-compliant reports more efficiently, enabling better dissemination of your valuable improvement work.

This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.