top of page

Delivering Timely Guidelines: Single PICO Flow

Updated: Jun 19, 2023

First published: September 2022

Last updated: June 2023


As a cornerstone to the continuous improvement of evidence-based medicine, guidelines are most valuable when they are delivered in a timely manner. Put simply, outdated guidelines reduce the efficacy of the health care system, and in the worst cases present risks to all those within it. The imperative of producing timely guidelines burst into global awareness with the COVID-19 pandemic. However, as we know, the systems and structures built for traditional guideline production were poorly suited to deal with the demands.


Vision and Design Rule Timeliness

The vision and design of traditional guidelines is often that of large, sometimes encyclopedic, academic publications in printed medical journals. The vision and design for living guidelines has long been for smaller publications, but still in printed medical journals.


Recently, the GRADE Working Group published a framework for living guideline development that made two key contributions to the vision and design of guidelines. First, it codified that, as a digital product, guideline developing organizations should use their websites as a primary dissemination tool. It also reminds us that when producing living guidelines, the individual recommendation is the unit of work.


For many guideline developing organizations, this marks a significant departure from how traditional guideline projects are managed. Therefore, to operationalize living guidelines we need to rethink how we define a “project”, so that we can begin to manage them appropriately.


Designing For Timeliness

When we think about how to manage the work of a guideline project, essentially how to take a PICO question and produce a recommendation, it typically falls into these four categories of work.



The systematic literature review, developing the recommendation, writing the manuscript, and the review and release process. Let’s say we have a hypothetical guideline with 3 PICO questions.



We might manage the work like this, with each step for each PICO happening in sequence.



Hopefully we can get all this work done before our literature search gets too old and needs updating! Operationally, that means we’re waiting for all the work to finish…before releasing the recommendations.


But for living guidelines, the PICO is the unit of work, which means we can manage our work like this:



This new way of managing “projects” immediately cuts down the necessary wait time before we can begin disseminating completed recommendations.


Operationalizing this new way of managing guideline projects allows for the continuous delivery of timely recommendations. For many organizations, this will likely require redesigning the structures and systems of guideline development. Organizations can then use the levers of productive capacity to drive more timely production of guidelines.


Combined with visualizing the work, such as with a Kanban board, this will also facilitate the creation of “flow” in the guideline development process.

 

References:


  1. El Mikati et al. A Framework for the Development of Living Practice Guidelines in Health Care. Ann Intern Med. doi:10.7326/M22-0514


71 views4 comments

Recent Posts

See All

4 Comments


simonvanco
Oct 05, 2022

Hello, very interesting! My name is Simon Van Cauwenbergh and I am part of a guideline development organization in Belgium. How would you incorporate GDG meetings and review processes done by stakeholders in living guidelines frame... for every PICO different meetings? Is there a possibility of significantly increasing the amount of meetings and time spend on this? Thank you very much for you reply, hope my question is clear... Best regards!

Like
Jon Heald
Jon Heald
Oct 06, 2022
Replying to

Hi Simon. Welcome to Agile Guidelines! My team is still working to determine the best strategy for meetings and review processes, but I can share principles we're trying to follow.


For meetings, we're using these principles: 1) only holding meetings to make decisions, not to provide status updates; and 2) be thoughtful intentional about which decisions needs to be made throughout the development process, and make those decisions at the optimal point in the development process.


Two of the biggest challenges we see with meetings is a) productive discussions, and b) making good decisions. The hope is that by using the above principles, we can determine when to hold meetings and how many meetings are needed. Whether this results in…


Like

cliff.berg
cliff.berg
Sep 29, 2022

"rethink how we define a project"


A "product" view might be useful - viewing a set of related guidelines as an integrated "product" that is continuously refined and evolves over time as new information comes in.


One of the challenges with a pipeline workflow pertains to agility. A pipeline view is a "flow" it optimizes for throughput in a situation in which the time to complete each step is highly variable. In contrast, and "agile" view considers that new information might arrive at any time that invalidates steps already completed.


Agility is about reacting quickly and thoughtfully to unexpected change. If new research or clinical data arrives that has implications for guidelines that have already been through a CPG, Write,…


Like
Jon Heald
Jon Heald
Oct 03, 2022
Replying to

Agree, Cliff!


In addition to rethinking "project", I find the product view, especially as it's used in software development, to be very helpful. This is a subject I personally want to dig into more on the blog.


Thanks for connecting the ideas of pipelines and workflow, and contrasting that with how agile behaviors are a necessary component of developing and reestablishing flow due to unexpected change.

Like
bottom of page