Addressing implementation challenges during guideline development - A case study of Swedish national guidelines for methods of preventing disease.

BackgroundMany of the world¿s life threatening diseases (e.g. cancer, heart disease, stroke) could be prevented by eliminating life-style habits such as tobacco use, unhealthy diet, physical inactivity and excessive alcohol use. Incorporating evidence-based research on methods to change unhealthy lifestyle habits in clinical practice would be equally valuable. However gaps between guideline development and implementation are well documented, with implications for health care quality, safety and effectiveness. The development phase of guidelines has been shown to be important both for the quality in guideline content and for the success of implementation. There are, however, indications that guidelines related to general disease prevention methods encounter specific barriers compared to guidelines that are diagnosis-specific. In 2011 the Swedish National board for Health and Welfare launched guidelines with a preventive scope. The aim of this study was to investigate how implementation challenges were addressed during the development process of these disease preventive guidelines.MethodsSeven semi-structured interviews were conducted with members of the guideline development management group. Archival data detailing the guideline development process were also collected and used in the analysis. Qualitative data were analysed using content analysis as the analytical framework.ResultsThe study identified several strategies and approaches that were used to address implementation challenges during guideline development. Four themes emerged from the analysis: broad agreements and consensus about scope and purpose; a formalized and structured development procedure; systematic and active involvement of stakeholders; and openness and transparency in the specific guideline development procedure. Additional factors concerning the scope of prevention and the work environment of guideline developers were perceived to influence the possibilities to address implementation issues.C