Clinical Practice Guidelines
3.0.0-ballot - STU 3 Ballot International flag

Clinical Practice Guidelines, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cqf-recommendations/ and changes regularly. See the Directory of published versions

L1 Checklist

Page standards status: Informative

Use this checklist to review narrative guidance and its evidence before you select a recommendation to translate. Select · Jump to checklist items

GIN McMaster Guideline Development Checklist Extension for Computable Guidelines

Guidelines Knowledge Level 1 (L1) Checklist

This checklist is an extension of the widely used GIN-McMaster Guideline Development Checklist and Tool for the Adoption and Implementation of Computable Guidelines. This checklist extension is intended to be used as a tool to help guideline developers develop narrative clinical guidelines with knowledge Level 1 (L1) in clearer, consistent, and more structured approach so that their key information like metadata, evidence, and recommendations may be successfully implemented by informaticists in computable formats used in clinical decision support systems that would improve patient outcomes through evidence-based medical practice in a learning health system based on FAIR (Findable, Accessible, Interoperable, and Reusable) principles. This may cover clinical practice guidelines and their related systematic reviews, evidence reports, and supplementary data and materials.1

Checklist items

Applicable to Guideline Developer Applicable to Informaticist/ Implementer Item Label Description Useful Resources/ Examples Further details
X* -* 1. Policy Provide a clear policy and link with a persistent identifier to public documentation of procedures used by the organization for guideline recommendations development, including how it establishes transparency, composes its guideline development group, manages conflicts of interest, reviews and rates evidence using rigorous methods, conducts peer review, updates the guidelines versions, manages data, and distributes/publishes guidelines recommendations. * IOM Guidance
* WHO handbook for guideline development, 2nd Edition
New item linked to GDC topic 1 “Organization, Budget, Planning and Training”
X - 2. Scope Clearly define the scope of the guideline development project, including who the guidelines are for (e.g., subject matter experts (SMEs), providers, patients, etc.), what clinical domains they would cover, and what settings and contexts they may be practiced at. * Adapting Clinical Guidelines for the Digital Age
* An Integrated Process for Co-Developing and Implementing Written and Computable Clinical Practice Guidelines
* Integrated Process tables: https://stacks.cdc.gov/view/cdc/131006
* An Evaluation Framework for a Novel Process to Codevelop Written and Computable Guidelines
* Evaluation framework tool: https://stacks.cdc.gov/view/cdc/131007
Extended item linked to GDC topic 5 “Identifying Target Audience and Topic Selection” and topic 8 “Patient/population, Intervention, Comparison, and Outcomes (PICO) Question Generation”
X - 3. Goal(s) Clearly articulate why a guideline development project is needed.   Extended item linked to GDC topic 2 “Priority Setting”
X X 4. Contributor(s) Ensure the involvement of informaticists and/or implementers in your guideline development panel at the start of the process to help identify areas in the guideline that require clarification and translation into CG recommendations using appropriate tools, data elements and value sets.   Extended item linked to GDC topic 3 “Guideline Group Membership”
- X 5. Knowledge Levels Requirements Provide a clear, strong, and tangible definition of the requirements of each guideline’s knowledge representation levels starting with the structured knowledge level 2 (L2), semi-structured knowledge level 3 (L3),† and executable knowledge level 4 (L4) for guideline developers to be able to understand what is needed to write an L1 recommendation for translation by the informaticists. These levels represent a progression from traditional narrative text to fully computable formats in clinical practice guidelines development. * FHIR Clinical Guidelines (v1.0.0) (STU 1) (hl7.org) New item to GDC topics
X - 6. Guideline Question formulation Formulate measurable and/or observable clinical questions using the Patient/population, Intervention, Comparison, and Outcomes (PICO) or Patient/population, Exposure, Comparison, and Outcomes (PECO) approaches. * Patient/population, Intervention, Comparison, and Outcomes (PICO) Process Extended item linked to GDC topic 8 “Patient/population, Intervention, Comparison, and Outcomes (PICO) Question Generation”
X X 7. Guideline Structure Use a valid grading system and approach to grade CG recommendations, such as the Grading of Recommendations Assessment, Development and Evaluation (GRADE) methodology. CG recommendations need to be written and styled in an identifiable, consistent format (i.e., contained in a labelled recommendation section with each recommendation labelled so it may be provided unique identifiers) so that they may be encoded and extracted from narrative contexts for translation across interchangeable formats (i.e., conditional statements using If, then) including the strength of the recommendation (i.e., strong, or conditional). * JATS4R
* IOM Guidance
* EBMonFHIR - Clinical Decision Support - Confluence (hl7.org)
* Agency for Healthcare Research and Quality (AHRQ) Systematic Review Data Repository (SRDR+)
New item linked to GDC topic 12 “Judging Quality, Strength or Certainty of a Body of Evidence”.

Use the evidence-based structure and requirements for guidelines related systematic reviews, evidence reports, and supplementary data and materials.
X X 8. Documentation requirements per recommendation Utilize existing applications, consistent templates, or authoring and conversion tools that facilitate the extraction of individual recommendation statements to be translated for execution. Such translations may be specified algorithms or decision trees or other computable representations that permit guidelines to be successfully integrated and implemented at point-of-care, allowing for systematic and consistent decision-making based on specific conditions or criteria. These resources can streamline the guideline development process and ensure a standardized approach to their documentation. Articulate all possible care options explicitly, incorporating known variables and contextual factors necessary for optimal decision-making.

Ensure that guidance for each extracted and translated recommendations aligns with the essential data elements, value sets, and measures specified in the PICO/PECO questions. Consistently employ common data elements and variables in the curation and FAIR indexing of recommendations to meet real-world requirements, adhere to clinical terminology, and align with health outcomes (21-23). Data elements, such as gender, age, and identifiers, must be clearly defined and utilized throughout the learning health system pertaining to the specific topic, disease, drug, screening, etc. This model aims to balance efficiency and accuracy in decision-making, where possible, guideline developers should provide decision trees, often labelled as care algorithms or pathways, that supports decision-making by breaking it down into key decision points or nodes. Each node represents a critical decision or branch in the care pathway. Subject the decision tree to iterative review and validation by experts in the field to ensure that the decision tree accurately reflects the best available evidence and clinical expertise. Refer to Figures 3, 4, 5, and 6 for examples illustrating the hypothetical scenario relevant to recommendation statements: If condition (x AND y OR z) is true, make a specific recommendation N. Clearly document the x, y, and z conditions statements to enhance transparency and reproducibility.
* https://goodwin.libguides.com/c.php?g=309484\&p=2066254
* United States Core Data for Interoperability (USCDI) | Interoperability Standards Advisory (ISA) (healthit.gov)
* Value Set Authority Center (nih.gov)
* CDS Authoring Tool (ahrq.gov)
* FHIR Clinical Guidelines (v0.2.0) (Current) (hl7.org)
* FFT Decision Tree Example

Additional Resources for International Community:
* International Patient Summary IG (hl7.org)
* International Classification of Health Interventions (ICHI) (who.int)
New item linked to GDC topic 14 “Wording of Recommendations and of Considerations of Implementation, Feasibility and Equity” and topic 16 “Dissemination and Implementation”.

Define the data elements and variables that will be used when performing complex queries on available data sets and published literature.
X X 9. Guideline Update Maintain an open, transparent, and regularly reviewed and updated guidelines recommendations based on the latest set of evidence available. This creates a foundation for a continuous cycle of evidence generation, translation to practice and practice driven data collection and use. Use existing guidance such as the living guidelines model where recommendations will be updated as soon as relevant new evidence becomes available or the CheckUp tool that informs guideline developers about strategies for updating clinical guidelines and their reporting requirements. Follow a consistently systematic approach for assigning and managing versions of all guideline updates using common version algorithms or mechanisms that ensure changes made to a file or a set of files are tracked, documented, and organized in a structured manner. Use a transparent and consistent labelling system for updates to indicate if they represent minor changes that are not critical for clinical decision-making to major updates where recommendations are altered in the narrative and impact decision-making. Annotating a section in the narrative that lists all changes in updated guidelines best facilitates informaticists work when computable formats need updates to be used at point-of-care. The modelling of versions of narrative guidelines with persistent identifiers and their linked evidence documents and supporting data is critical in evaluating reproducibility of guidance for optimal care. The guideline community may consider extending the work of the NISO Standards Committee on Versions of Journal Articles to meet the unique use cases of guideline developers. For FHIR outputs of computable recommendations, one common approach for versioning informaticists may consider is known as Semantic Versioning (SemVer) that provides a structured way to communicate changes in software, which thus allows developers and users to quickly understand the nature of changes, making it easier to manage dependencies and assess the impact of updates. * https://semver.org/
* https://www.hl7.org/fhir/valueset-version-algorithm.html
* Living systematic reviews: 4. Living guideline recommendations
* Reporting Items for Updated Clinical Guidelines: Checklist for the Reporting of Updated Guidelines (CheckUp) (nih.gov)
* https://www.niso.org/publications/z3996-2021-jats
* https://www.niso.org/standards-committees/journal-article-versions
New item linked to GDC topic 18 “Updating”.

Each version shall have a persistent identifier for transparency in the historical record, and that each version can be linked across all other versions of that document through clearly communicated related publications in each document and its indexed metadata.

*X: Applicable, -: Not Applicable

†Editor's note: Item 5 is reproduced as published. The published text describes knowledge level 2 (L2) as structured and knowledge level 3 (L3) as semi-structured, which is the reverse of the levels of knowledge representation used in this implementation guide, where L2 is semi-structured and L3 is structured. This is being raised with the checklist authors.

GDC: GIN-McMaster Guideline Development Checklist. Numbered references (for example, 21-23) and figures (Figures 3, 4, 5, and 6) cited in the item descriptions refer to the published article below.

The material on this page was developed by the GIN-NA working group and presented to the CPG-on-FHIR project team for inclusion in the CPG-on-FHIR implementation guide in support of the shared goals of creating computable clinical guideline content. The checklist is reproduced from Appendix 1 (Supporting Information) of the following article, published under a Creative Commons Attribution 4.0 International (CC BY 4.0) license:

Chehab C, Lathrop S, Harrod CG, Kariuki J, Ritz D, Michaels M. Development of Computable Guidelines: GIN McMaster Guideline Development Checklist Extension for Computable Guidelines. Clinical and Public Health Guidelines. 2025;2(3):e70023. https://doi.org/10.1002/gin2.70023