| Literature DB >> 24479687 |
Kelly E Caudle, Teri E Klein, James M Hoffman, Daniel J Muller, Michelle Whirl-Carrillo, Li Gong, Ellen M McDonagh, Katrin Sangkuhl, Caroline F Thorn, Matthias Schwab, Jose A G Agundez, Robert R Freimuth, Vojtech Huser, Ming Ta Michael Lee, Otito F Iwuchukwu, Kristine R Crews, Stuart A Scott, Mia Wadelius, Jesse J Swen, Rachel F Tyndale, C Michael Stein, Dan Roden, Mary V Relling, Marc S Williams, Samuel G Johnson1.
Abstract
The Clinical Pharmacogenetics Implementation Consortium (CPIC) publishes genotype-based drug guidelines to help clinicians understand how available genetic test results could be used to optimize drug therapy. CPIC has focused initially on well-known examples of pharmacogenomic associations that have been implemented in selected clinical settings, publishing nine to date. Each CPIC guideline adheres to a standardized format and includes a standard system for grading levels of evidence linking genotypes to phenotypes and assigning a level of strength to each prescribing recommendation. CPIC guidelines contain the necessary information to help clinicians translate patient-specific diplotypes for each gene into clinical phenotypes or drug dosing groups. This paper reviews the development process of the CPIC guidelines and compares this process to the Institute of Medicine's Standards for Developing Trustworthy Clinical Practice Guidelines.Entities:
Mesh:
Substances:
Year: 2014 PMID: 24479687 PMCID: PMC3977533 DOI: 10.2174/1389200215666140130124910
Source DB: PubMed Journal: Curr Drug Metab ISSN: 1389-2002 Impact factor: 3.731
Standard format of CPIC guidelines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See [2] for examples.
Comparison of CPIC guidelines to the IOM’s Standards for Developing Trustworthy Clinical Practice Guidelines.
| IOM Standard | CPIC Guidelines |
|---|---|
|
| |
| 1.1 The process for developing a clinical practice guideline (CPG) –including funding – should be explicitly described and publicly accessible. |
|
|
| |
| 2.1 Prior to selection of the Guideline Development Group (GDG), individuals being considered for membership should declare all interests and activities potentially resulting in COI with development group activity, by written disclosure to those convening the GDG. |
|
| 2.2 All COI of each GDG member should be reported and discussed by the prospective development group prior to the onset of their work. | |
| Each panel member should explain how their COI could influence the CPG development process or specific recommendations. | |
| 2.3 Members of the GDG should divest themselves of financial investments they or their family members have in, and not participate in marketing activities or advisory boards of, entities whose interests could be affected by CPG recommendations. |
|
| 2.4 Whenever possible GDG members should not have COI. In some circumstances, a GDG may not be able to perform its work without members who have COIs, such as relevant clinical specialists who receive a substantial portion of their incomes from services pertinent to the CPG. Members with COIs should represent not more than a minority of the GDG. |
|
| The chair or co-chairs should not be a person(s) with COI. Funders should have no role in CPG development. | |
|
| |
| 3.1 The GDG should be multidisciplinary and balanced, comprising a variety of methodological experts and clinicians, and populations expected to be affected by the CPG. |
|
| 3.2 Patient and public involvement should be facilitated by including (at least at the time of clinical question formulation and draft CPG review) a current or former patient and a patient advocate or patient/consumer organization representative in the GDG. |
|
| 3.3 Strategies to increase effective participation of patient and consumer representatives, including training in appraisal of evidence, should be adopted by GDGs. |
|
|
| |
| 4.1 CPG developers should use systematic reviews that meet standards set by the Institute of Medicine’s Committee on Standards for Systematic Reviews of Comparative Effectiveness Research. |
|
| 4.2 When systematic reviews are conducted specifically to inform particular guidelines, the GDG and systematic review team should interact regarding the scope, approach, and output of both processes. | |
|
| |
| For each recommendation, the following should be provided: |
|
| An explanation of the reasoning underlying the recommendation,
including:
A clear description of potential benefits and harms. A summary of relevant available evidence (and evidentiary gaps), description of the quality (including applicability), quantity (including completeness), and consistency of the aggregate available evidence. An explanation of the part played by values, opinion, theory, and clinical experience in deriving the recommendation. A rating of the level of confidence in (certainty regarding) the evidence underpinning the recommendation. A rating of the strength of the recommendation in light of the preceding bullets. A description and explanation of any differences of opinion regarding the recommendation. | |
|
| |
| 6.1 Recommendations should be articulated in a standardized form detailing precisely what the recommended action is and under what circumstances it should be performed. |
|
| 6.2 Strong recommendations should be worded so that compliance with the recommendation(s) can be evaluated. |
|
|
| |
| 7.1 External reviewers should comprise a full spectrum of relevant stakeholders, including scientific and clinical experts, organizations (e.g., health care, specialty societies), agencies (e.g., federal government), patients, and representatives of the public. |
|
| 7.2 The authorship of external reviews submitted by individuals and/or organizations should be kept confidential unless that protection has been waived by the reviewer(s). | |
| 7.3 The GDG should consider all external reviewer comments and keep a written record of the rationale for modifying or not modifying a CPG in response to reviewers’ comments. | |
| 7.4 A draft of the CPG at the external review stage or immediately following it (i.e., prior to the final draft) should be made available to the general public for comment. Reasonable notice of impending publication should be provided to interested public stakeholders. | |
|
| |
| 8.1 The CPG publication date, date of pertinent systematic evidence review, and proposed date for future CPG review should be documented in the CPG. |
|
| 8.2 Literature should be monitored regularly following CPG publication to identify the emergence of new, potentially relevant evidence and to evaluate the continued validity of the CPG. | |
| 8.3 CPGs should be updated when new evidence suggests the need for modification of clinically important recommendations. For example, a CPG should be updated if new evidence shows that a recommended intervention causes previously unknown substantial harm, that a new intervention is significantly superior to a previously recommended intervention from an efficacy or harms perspective, or that a recommendation can be applied to new populations. | |