PEBCHandbook
PEBCHandbook
PEBCHandbook
Project Planning
The impetus to begin a new PEBC guideline project may come from an existing DSG/GDG, CCO Clinical Programs or Executive Team, the Ontario Ministry of Health and Long Term Care or other stakeholders in the Ontario cancer system. Some common criteria used to set priorities include the burden of disease, emergence of new care options, unwanted variation in clinical practice, opportunity to improve quality of care, safety or system performance, and new evidence. Every PEBC project begins with a planning
Page 2 of 15
process, involving the project leaders and a project Working Group, and with a formal project plan document as the outcome.
The process of determining the Working Group membership varies somewhat, depending on whether the project will be conducted within an existing DSG/GDG or not. Within an existing DSG/GDG, the Working Group members are indentified within the group, or are recruited by the group. Sometimes, depending on the topic, clinicians from outside the group will be recruited to provide specific subject matter expertise. These extra members may be recruited from outside Ontario, or even internationally; the goal is to create a group that has intimate and in-depth knowledge of the topic of the guideline project. For topics that will be conducted outside an existing GDG, a project Lead Author/Chair for the Working Group is usually established at the outset. This individual might be an appropriate CCO Clinical Program Head, or someone designated by the Clinical Program Head, or it might be the person who is most associated with bringing the topic forward for guideline development. Then, specific individuals are nominated by the LEAD AUTHOR and by other key partners (DSG Chairs, Clinical Program Heads, etc.), and these individuals are contacted in order to put together a balanced and complete Working Group. These individuals might be recognized as provincial leaders in their discipline or might have previously collaborated on PEBC projects. Ultimately, the core group of two to six clinicians/content experts and a PEBC Research Coordinator will be ready to begin the guideline development work. Conflict of interest (COI) statements are obtained from the members of the Working Group. The COI disclosures focus on financial involvement with industry or manufacturing parties related to the guideline topic, although the PEBC recognizes that many other conflicts might exist. At this time, the PEBC does not have formal policy regarding group participation if there are conflicts declared.
Page 3 of 15
The project plan is developed by the Working Group, and is reviewed by, at a minimum, an Assistant Director of the PEBC prior to project initiation. For projects that might be expected to require resourceintensive development or have potentially complex implications for implementation, the project plan would also be reviewed by additional stakeholders and managers (the PEBC Director, CCO Clinical Program Heads, CCO Executive Team, etc.) Although the project plan is completed prior to the initiation of the project, it is considered to be a living document that is subject to change throughout the execution of the project. However, alterations to the planned scope and/or methodologies are reviewed carefully by the PEBC as they are likely to have a large impact on the resources and time required for completion of the project. All changes made to the project plan document throughout the project are documented, dated, and approved by the group members.
Page 4 of 15
Document Creation
Once a project plan has been completed, the process of creating the document can begin. The document creation process will depend on the choices made during project planning, but the process can be generally divided into four stages: identification and review of existing guidelines, systematic review of the evidence, recommendations formulation, and draft completion.
Page 5 of 15
When these criteria are not met, the PEBC has found that the most efficient way to move forward is to use the evidentiary base of the existing guideline(s) to formulate new recommendations, rather than using the existing recommendations, and to update the evidentiary base as necessary.
Literature Search
A search for all the available and relevant literature is conducted, based on the research question(s) and the study selection criteria set out in the project plan. The search covers, at minimum, peer-reviewed articles indexed in Medline and EMBASE, and a review of both the Central Registry of Clinical Trials and the Database of Systematic Reviews of the Evidence in the Cochrane Library. In addition, the websites of known developers of high-quality systematic reviews, whose work is not always published in the peer reviewed journals, are searched for existing reviews on the same topic. These sites include those of other guideline developer organizations such as the National Institute for Clinical Excellence (NICE) and the Scottish Intercollegiate Guideline Network (SIGN), as well as organizations that create health technology assessments and other systematic reviews for policy purposes, such as the Agency for Research on Healthcare Quality (AHRQ). In order to identify studies that might not have been published in peer-reviewed journals, the search most often covers abstracts and/or presentations of the results of randomized trials, made at appropriate, internationally recognized conferences such as the ASCO annual meeting, the ESMO meetings, etc. Although data presented in meeting abstracts or presentations may not be as reliable and complete as that from papers published in peer-reviewed journals, abstracts can be a source of important evidence from randomized trials and add to the evidence available from fully published studies. Those data often appear first in meeting abstracts and may not be published for several years. This search is usually conducted in two phases, although elements of the phases may be conducted simultaneously in order to save time. First, the existing systematic reviews/meta-analyses relevant to the research question(s) outlined in the project plan are identified. The objective is to make use of existing work to the greatest extent possible to develop the evidence base for the document efficiently. The findings are evaluated by the Working Group to determine if any of them provide a sufficiently comprehensive evidence base to answer one or more of the research questions. The Working Group takes into account the timeliness and quality of the systematic review and whether it summarizes the target populations, interventions, comparisons, and outcomes of interest as outlined in the project plan. After the Working Group has evaluated the existing systematic reviews and determined how to apply them, a literature search is conducted covering the research questions and those areas (time frame, populations, interventions, etc.) that the existing reviews do not address fully or at all. The search employs the standard methods of a literature search that have been described elsewhere (4). In conducting a search for primary study evidence, the intent of the PEBC is not to develop a complete summary of all the available evidence, regardless of its form. The intent is to identify, in a systematic fashion, that evidence which is relevant and useful for the formulation of recommendations. Metaanalyses and randomized trials are the primary evidence sought by the PEBC, but for some questions, other types of comparative studies (cohort studies, case-control studies, diagnostic/screening studies, and
Page 6 of 15
other experimental designs) can be useful in developing recommendations. In contrast, in the PEBCs experience, non-comparative study data (retrospective or prospective case series and phase I and II clinical trials), regardless of the number of studies and subjects, are rarely a sufficient basis for recommendations, while at the same time being more difficult to identify, collect, and summarize than that from comparative studies. Therefore, the assumption when beginning any project is that noncomparative studies will be excluded, even when the a priori belief is that there is limited comparative data available. In cases where the evidence is limited to non-comparative data, the PEBC has found that moving directly to formal consensus methods for the development of recommendations can be a more fruitful and pragmatic way to develop guidelines.
Environmental Scan
In some cases, and especially when the topic under consideration deals with organizational questions, for instance, the methods of care delivery or the training requirements for clinicians, a systematic review will not identify important and relevant sources of information. The need then is to determine whether experiences in a different context or jurisdiction might be useful to consider or avoid in the Ontario context. These sources of information might include policy documents and guidance from other organizations or reports from government institutions or professional organizations that are found outside of the indexed medical literature. These sources are often not evidence-based, but they are useful for establishing a general consensus of worldwide opinion regarding topics that do not allow for evidencebased recommendations. In such cases, an environmental scan may be appropriate. The PEBC environmental scan process includes a targeted search of known or suspected relevant sources (other government, institutional, or professional organization websites, for example), and an untargeted search of the Internet using Google (2009) or another search engine, with relevant search terms, to identify these sources of information. The PEBC uses this information to address gaps in the existing evidence base and to provide a basis for initial recommendation formulation, which often leads to a formal consensus process, as described below.
Page 7 of 15
Recommendations Development
Initial Formulation of Recommendations
The Working Group formulates recommendations for practice or the delivery of care on the basis of the evidence synthesized in the process outlined above. Regardless of the quality and quantity of the evidence available to address all the research questions posed, the Working Group always needs to judge, interpret, and reach consensus on the meaning of this evidence for practice in Ontario. Expert opinion always plays a role in the development of recommendations, and frequently, the interpretation of the available evidence and the recommendations that the evidence can support is ambiguous--reasonable people may differ on the meaning and importance of the evidence. Even in the absence of any relevant evidence from the systematic review, the Working Group may still choose to make recommendations justified on other grounds such as logical argument, related evidence from other sources, and/or clinical experience. However, the justification for each recommendation and the degree to which it is based on the evidence directly versus the opinion and consensus of the Working Group must be explicitly stated in the recommendation itself.
Formal Consensus
Usually the recommendations are the result of informal consensus among the Working Group members. There are situations, however, where a formal process of ensuring consensus is necessary and useful. These situations include: When the available literature is very limited in terms of quantity and/or quality, but recommendations are still necessary. When it is desirable that a broader array of individuals, not just the Working Group, be involved in the recommendations development process, and not just in the review and approval of the recommendations. Formal consensus processes are used by a group of content experts to allow explicit reporting of the consensus opinion. The goal is to produce a set of recommendations based on the consensus of a wide array of appropriate experts in a transparent and systematic fashion, and to describe fully any controversial areas where consensus cannot be reached. As noted by Murphy et al (7): [Consensus development]is a process for making policy decisions, not a scientific method for creating new knowledge. At its best, consensus development merely makes the best use of available information, be that scientific data or the collective wisdom of the participants. Thus, although it may capture collective knowledge, it is inevitably vulnerable to the possibility of capturing collective ignorance. The decision to employ a formal consensus process may occur when: There is no evidence or when the evidence is very poor and it is unlikely that good quality studies will be conducted in the future (as in the case of a rare disease such as thymoma). As part of an Adaptation process: When recommendations are derived by a small working Group from an existing guideline, a formal consensus process with a larger group of clinical/content experts provides a method for refining the recommendations and allows for a transparent reporting of the level of consensus for each recommendation within the practice community.
Page 8 of 15
There are several methods for obtaining a formal consensus, and their use in clinical guideline development is outlined by Murphy et al (7). The Delphi technique is described by Linstone and Turoff (8). The PEBC has used a modified Delphi process with two rounds of feedback, as outlined in Figure 3. First, the Working Group members formulate draft recommendations on the basis of existing evidence and/or their own clinical experience and/or through the adaptation of recommendations from a relevant existing guideline. Then, in each round of feedback, the draft recommendations are submitted to the consensus body of experts, who are asked to rate their level of agreement with each recommendation using a Likert
Figure 3. Steps in a generic formal consensus process (a modified Delphi approach) used to develop recommendations for the PEBC guidelines.
scale, and to provide feedback on each recommendation. The Working Group makes an a priori decision on the interpretation of the responses from the consensus group regarding what constitutes a consensus agreement. For instance, if 75% or more of the consensus group agree or strongly agree with the recommendation then the recommendation is accepted. Defining thresholds for both consensus in support of a recommendation as well as consensus against a recommendation is important. After the first round, the responses are evaluated and summarized, to identify the recommendations with a high level of agreement and those for which there is no agreement or frank disagreement. Controversial recommendations are then rewritten or modified, based on the feedback, in an attempt to improve the level of agreement. In the second feedback round, the recommendations are again presented to the consensus body, along with the results of the previous round, in the form of a table or chart that illustrates or describes the level
Page 9 of 15
of agreement on each recommendation. For controversial recommendations, both the old and the newer, modified versions of the recommendation are presented. The consensus body is again asked to rate their level of agreement with all the recommendations, taking into account their knowledge of how their peers responded in the previous round. After two rounds, a final set of recommendations is drafted. Recommendations that complete the last stage with high levels of agreement are considered consensual. Draft recommendations where controversy still exists are presented in the final document as points for discussion, not as recommendations, with a description of the controversy surrounding them. The first example of PEBC guideline development using formal consensus methods is EBS 7-11 The Management of Thymoma, published online on the CCO website in September 2008.
External Review
Following the approval by the RAP and the GDG and the integration of the internal review process into Section 3, the new draft is prepared for external review. All but the following PEBC documents undergo complete external review: 1. Special advice reports submitted by the PEBC to the Committee to Evaluate Drugs (described below) are requested by and provide advice to that group for funding decisions and are therefore not submitted to external review. 2. If a formal consensus process has been undertaken to develop the recommendations, and the document has already been thoroughly reviewed by appropriate experts during that process, then the recommendations cannot be changed and still be considered the result of consensus. In this
Page 10 of 15
case, external review would be both redundant and in violation of the method used to develop the recommendations. The PEBC submits its documents to two forms of external review: targeted peer review and professional consultation.
Professional Consultation
The PEBCs Professional Consultation process is intended to disseminate the draft guideline as widely as possible to its intended readership, to provide a forum for recipients to explain any disagreement with the conclusions and/or recommendations, and to further ensure the quality and relevance of the document. Initially, the PEBC identifies individuals in the PEBC internal contact database who are likely to be interested in the guideline, organizations whose membership might be interested in the subject matter, and other important relevant stakeholders suggested by the Working Group. These individuals are then contacted by email and mail and are invited to review the document and provide feedback either online, by mail, fax or by email. Each consultee is asked to provide general feedback about the document and answer a very short questionnaire (available upon request). The feedback is taken into consideration by the Working Group and used, as necessary, to correct and revise the document. The intent of the Professional Consultation process is to alert a large number of applicable individuals and groups to the existence of the guideline and to obtain general feedback and criticism from interested individuals. Achieving a specified proportion of responses is not the intent. The Working Group considers the critical review from the external review process, and responses to the review are prepared through discussion and informal consensus. The process of and details arising from the external review are documented in Section 3 of the EBS, as are any changes made to the rest of the document as a result of the feedback.
Document Publication
Once the results of the external review are incorporated, the document undergoes approval by the GDG. It then receives a final copy editing and is considered completed. The guideline can now be published and disseminated not only to its intended users but also to other interested parties.
Page 11 of 15
Web Publication
All PEBC documents are released publicly on the CCO website (www.cancercare.on.ca) to make the document freely available to Ontario health care providers and the general public, and to anyone else who wishes to access them. The PEBC also works with the National Guideline Clearinghouse (6) and the CMA Infobase (7) to ensure that our documents are properly indexed in those two databases so that individuals seeking guidance on topics that our documents address can locate them.
Journal Publication
In addition to web publication, the PEBC typically seeks to have each document, or certain portions, published in the peer-reviewed medical literature. In many cases, this involves producing two separate manuscripts for submission to relevant journals: an evidentiary-base manuscript and a practice guideline manuscript. In the experience of the PEBC, the evidentiary-base of our documents is often more easily published than the guideline recommendations, because it is relevant to a wider audience. The guideline recommendations, on the other hand, are written to be specifically relevant to the Ontario context. The basic structure of our documents, the three-part EBS, as described above, makes this submission process easier, because the document is already divided into a separate guideline (Section 1), evidence base (Section 2), and methods (Section 3).
Further Dissemination
The PEBC has found that the formal consensus and professional consultation processes described above are often sufficient to ensure that the intended Ontario users of our documents are made aware of them. In some cases, however, the PEBC document may be part of a larger initiative of CCO or the Ontario Ministry of Health and Long Term Care to affect practice in Ontario. In such cases, there may be additional dissemination efforts, including public meetings, news releases, implementation projects, and public policy development.
Document Maintenance
Once a document has been completed, it remains available on the PEBC website until it is updated or identified as being irrelevant to practice or incorrect. Ideally, the PEBC would choose to continually update the evidence base and recommendations of all of its documents, but the reality is that there are insufficient resources to do so. The PEBC has instead implemented a process of document maintenance that prioritizes those documents most in need of review and that makes the current status, relevance, and currency of the its documents clear to the users.
Periodic Review
The aim of the PEBC is that all our publicly available documents undergo a review within three years of their initial release, and then at least every two years thereafter. The goal of this review is to determine whether the document is still relevant to current practice or whether there are known or suspected problems with its current recommendations and to determine the priority of the document for update or rewrite. The PEBC has implemented the Document Assessment and Review Tool (DART) as a formal method of conducting these reviews. There are several outcomes for a document as a result of the DART review: Archiving: A document is archived when it is no longer considered relevant to current practice--it has become out-of-date and is unreliable to guide practice. The document is still available on the
Page 12 of 15
CCO website but has text and watermarking added to it to make clear that it should not be used for clinical decision making. Removal: A document is removed from public availability when there are known or suspected problems with its recommendations such that its implementation might cause harm or result in unnecessary care or treatment. The document is available only by contacting the PEBC. Endorsement: A document is endorsed when no update to the recommendations is considered necessary, and the recommendations are still considered valid and relevant for clinical practice. Endorsement can occur in the following three cases. o First, the document may be a definitive statement regarding the questions it addresses. That is, its recommendations are based on a large, consistent, and unambiguous evidence base, and there are no new questions that have arisen. Second, the recommendations may be derived primarily from consensus and expert opinion regarding a topic area where limited evidence is expected to be available such as for very rare diseases or conditions. Third, a new evidence search has been completed, and either no new evidence has been identified, or the evidence wholly supports the existing recommendations. The document is modified to indicate its endorsement and remains available on the website.
Deferral: A document may be deferred when there are insufficient resources to fully review the document, or when there are good reasons to postpone the review (for instance, a known relevant study will be published in the near future). The document remains available on the website, modified so that the reader can see the reasons for deferral. Prioritization for Update: The document remains available on the website, but is prioritized to be updated as soon as possible. In each case, the DART and any accompanying literature search results are incorporated into the document so that the user can see the documents current status and the reasons for that status.
Updating
A document is updated in the following circumstances: The clinical questions in the existing document are still relevant, and no new questions are required. There is believed or known to be a limited number of new sources of evidence regarding those questions. There is a low likelihood that major revisions and additions to the recommendations will be necessary. In an update, the original evidence base of the document (Section 2 of the EBS) is left unchanged, becoming Section 2B or similar. An updated evidence base is created, using the methods described above
Page 13 of 15
and incorporating all evidence that has been released since the completion of the original document. Only the guidance portion of the document (Section 1 of the EBS) is rewritten. Additional information is added to the methods and review section (Section 3 of the EBS) to reflect and describe the changes that were made. The updated document then undergoes a new round of internal and external review, as described above, although in some cases the changes made to the recommendations and the volume of new evidence may be considered small enough to not warrant review.
Rewriting
If any of the criteria for updating mentioned above are not met, the document may require rewriting. In this case, the document will undergo the entire PEBC development cycle again, including the creation of a new project plan. The existing document will be used to whatever extent possible to speed the process of development. However, a rewrite is essentially a new project, as the research questions, the scope of the evidence search, and the scope of the recommendations may all change radically from the earlier version.
Page 14 of 15
References
1. 2. 3. 4. 5. 6. 7. 8. Browman G, Levine M, Mohide E, Hayward R, Prtichard K, Gafni A, et al. The practice guidelines development cycle: a conceptual tool for practice guidelines development and implementation. J Clin Oncol.1995;13:502-12. The AGREE Research Trust. The Appraisal of Guidelines for Research & Evaluation (AGREE) instrument. London: The AGREE Research Trust; 2001 [cited 2009 Jul 29]. Available from: http://www.agreetrust.org/instrument.htm. The ADAPTE Collaboration. The ADAPTE Manual and Resource Toolkit. The ADAPTE Collaboration; 2007 [cited 2009 Jul 29]. Available from: http://www.adapte.org/rubrique/manual-and-tools.php. Scottish Intercollegiate Guidelines Network. SIGN 50: A guideline developer's handbook. Edinburgh: Scottish Intercollegiate Guidelines Network; 2008 [cited 2009 Jul 29]. Available from: http://www.sign.ac.uk/guidelines/fulltext/50/index.html. Moher D, Jadad A, Tugwell P. Assessing the quality of randomized controlled trials. Int J Technol Assess Health Care. 1996;12(2):195-208. Lipsey M, Wilson D. Practical meta-analysis. Bickman L, Rog D, editors. Thousand Oaks (CA): Sage Publications; 2001. Murphy MK, Black NA, Lamping DL, McKee CM, Sanderson CFB, Askham J, et al. Consensus development methods, and their use in clinical guideline development. Health Technol Assess. 1998;2(3). Linstone HA, Turnoff M, editors. The Delphi method: techniques and applications. Don Mills (ON): Addison-Wesley Publishing; 2002. Available from: http://is.njit.edu/pubs/delphibook/delphibook.pdf.
Page 15 of 15