How to Write a Quality Improvement Project Abstract for the NHS

Why this topic matters

Abstracts are the gateway to your quality improvement project. They serve multiple vital functions within the NHS and broader healthcare landscape:

• Dissemination of Learning: A good abstract allows others to quickly grasp your project's aims, methods, findings, and implications, facilitating the spread of good practice across departments, trusts, and even nationally.
• Professional Development: For junior doctors and trainees, presenting QI work, often starting with an abstract submission, is a key component of professional development and portfolio building. It demonstrates engagement with improving patient care and systems.
• Engagement and Recognition: A compelling abstract can attract interest, leading to opportunities for presentation, publication, and collaboration, which are vital for fostering a culture of continuous improvement.
• Resource Allocation: For QI leads and managers, abstracts can be a tool for showcasing the impact of QI initiatives, potentially influencing future resource allocation and strategic planning.
• Informing Practice: By clearly summarising outcomes, abstracts contribute to the collective knowledge base, helping clinicians make informed decisions about adopting new approaches or replicating successful interventions.

Practical explanation: What makes a good QI abstract?

A quality improvement abstract differs from a research abstract. While both aim for brevity and clarity, a QI abstract typically focuses on the specific context, the intervention implemented, the process of change, and the outcomes related to improvement, rather than hypothesis testing or generalisability across populations. The IHI (Institute for Healthcare Improvement) recommends a clear structure, which many NHS organisations and conferences have adopted.

Key characteristics of an effective QI abstract include:

• Clarity and Conciseness: Every word counts. Avoid jargon where possible, or explain it briefly. Aim for maximum information in minimal space (typically 250-350 words).
• Structured Format: Most platforms require specific headings. Adhering to these makes your abstract easy to read and ensures all critical information is included.
• Focus on Improvement: Clearly articulate the problem, the intervention, and the measured improvement. It's about 'what changed' and 'how much'.
• Actionable Learning: What can others learn from your project? What are the key takeaways or recommendations?
• Credibility: Present data clearly and honestly. Even if improvement wasn't as expected, reporting accurately is crucial.

Common pitfalls to avoid

When writing a QI abstract, several common mistakes can detract from its effectiveness:

• Too much background/introduction: While context is important, the abstract is not the place for an extensive literature review. Get straight to your project.
• Lack of clear aims: Fuzzy or multiple aims can confuse the reader. State your primary aim clearly, often using SMART (Specific, Measurable, Achievable, Relevant, Time-bound) principles.
• Vague methodology: Don't just say 'we implemented a change'. Briefly explain what change, how it was implemented, and how you measured its impact (e.g., PDSA cycles, run charts, specific data points).
• Absence of results/data: The core of a QI project is measured improvement. Even interim data or process measures are valuable. Avoid statements like 'data will be presented'.
• Over-claiming or generalising: QI projects are often context-specific. Be cautious about suggesting your findings are universally applicable without local validation.
• Poor grammar or spelling: These errors can undermine the credibility of your work.
• Exceeding word limits: Adhere strictly to word counts. Editors often reject abstracts that go over, or truncate them, potentially losing key information.

Step-by-step approach to writing your QI abstract

Most QI abstracts follow a standard format, often aligning with the SQUIRE (Standards for Quality Improvement Reporting Excellence) guidelines or a simplified version for conference submissions. A common structure includes:

1. Title

• Purpose: Grab attention and clearly state the project's focus. It should be informative and concise.
• Content: Include the intervention, target population/setting, and the desired outcome. Avoid acronyms unless universally understood.
• Example: "Reducing Waiting Times for Paediatric Phlebotomy Services in Outpatients: A QI Initiative Using Process Mapping."

2. Introduction/Background

• Purpose: Briefly outline the problem or gap in care that the project addresses, and why it is important.
• Content: Provide essential context. What was the unmet need or issue? Why was improvement necessary? Keep it to 1-2 sentences.
• Example: "Prolonged waiting times for paediatric phlebotomy appointments led to parental dissatisfaction and clinic inefficiency. Our aim was to reduce the average waiting time."

3. Aim(s)

• Purpose: Clearly state what your project intended to achieve.
• Content: A single, clear, measurable aim is often best. Use SMART criteria if possible.
• Example: "To reduce the average waiting time for paediatric phlebotomy from 45 minutes to 20 minutes within six months, by December 2024."

4. Methodology/Intervention

• Purpose: Describe the approach taken and the changes implemented.
• Content: Briefly explain your QI method (e.g., PDSA cycles). What specific interventions were tested or implemented? What data did you collect and how (e.g., run charts, surveys)?
• Example: "We used iterative Plan-Do-Study-Act (PDSA) cycles, engaging staff and parents, to trial interventions including a new booking system, dedicated phlebotomy slots, and pre-assessment calls. Waiting times were tracked weekly using a run chart, and staff/parent feedback was collected."

5. Results/Findings

• Purpose: Present the key outcomes and measured improvements.
• Content: State the quantifiable results clearly. Refer to baseline data and the achieved change. Use numbers, percentages, or statistical process control (SPC) chart findings if applicable. Report both process and outcome measures.
• Example: "Baseline average waiting time was 45 minutes (range 30-70 mins). After 4 PDSA cycles, the average waiting time reduced to 18 minutes (range 10-30 mins) by month 5, meeting our aim. Parent satisfaction scores increased from 60% to 90%."

6. Discussion/Conclusion

• Purpose: Interpret the results and discuss their implications.
• Content: What did you learn? How do these findings contribute to better patient care or efficiency? Acknowledge limitations briefly. What are the next steps or recommendations?
• Example: "The project successfully demonstrated that targeted interventions, coupled with iterative testing, can significantly improve paediatric phlebotomy waiting times and patient satisfaction. Sustaining these improvements and exploring spread to other clinics are the next steps."

Example in clinical practice

Here’s an example abstract for a hypothetical QI project:

Title: Improving Timely Administration of 'Stat' Antibiotics in Medical Assessment Units: A Quality Improvement Project

Introduction: Delayed administration of 'stat' (immediate) antibiotics can lead to poorer patient outcomes in acute care settings. Our medical assessment unit (MAU) identified inconsistencies in the time taken from prescription to administration of 'stat' intravenous antibiotics.

Aim: To reduce the median 'door-to-needle' time for 'stat' intravenous antibiotic administration in MAU from 90 minutes to 60 minutes within a three-month period (June-August 2024).

Methodology: A multidisciplinary team utilised a Plan-Do-Study-Act (PDSA) cycle approach. Interventions included: dedicated 'stat' antibiotic trays in treatment rooms, nurse education sessions on preparation protocols, and daily huddles to identify barriers. Time stamps from electronic prescribing and administration records were collected daily and monitored using a run chart.

Results: Baseline median 'door-to-needle' time was 90 minutes (IQR 65-110). Following three PDSA cycles, the median time reduced to 55 minutes (IQR 40-75) by the end of August 2024, consistently below the 60-minute target. A shift in the run chart indicated a significant improvement in process reliability. Ward-based feedback indicated improved staff confidence in timely administration.

Conclusion: This QI project demonstrated that focused, multidisciplinary interventions can significantly improve the timely administration of 'stat' antibiotics in MAU. Sustaining these gains through regular audits and exploring opportunities to spread this practice to other acute areas are priorities.

How Lazomis can help

Lazomis provides structured tools and templates that can streamline your QI project from inception to reporting. Our platform offers dedicated sections for documenting your project aims, methodology, and results, making it easier to extract information for abstract writing. Our project management features ensure you capture the necessary data points throughout your project lifecycle, simplifying the process of generating your 'results' section. Furthermore, Lazomis Dashboards can help you visualise your run charts and other key metrics, providing clear evidence of improvement that can be directly referenced in your abstract. By using Lazomis for your QI work, you'll have a consistent, organised record, making abstract generation a less daunting task.

Key takeaways

• Structure is key: Follow a standard format (e.g., Title, Intro, Aim, Methods, Results, Conclusion) for clarity.
• Be concise and clear: Every word counts; remove jargon and unnecessary detail.
• Focus on the 'improvement story': Clearly articulate the problem, intervention, measured change, and learning.
• Quantify your results: Include specific data, even if preliminary, to demonstrate impact.
• Adhere to word limits: Respect the specified word count, as exceeding it can lead to rejection.
• Proofread meticulously: Errors undermine credibility.

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