<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>Making sense of implementation theories, models and frameworks</title>
        <author>Per Nilsen</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>Making sense of implementation theories, models and frameworks</title>
          <date>2015</date>
          <publisher>Implementation Science</publisher>
          <idno type="DOI">10.1186/s13012-015-0242-0</idno>
          
          <idno type="record">nilsen2015-implementation-theories-models-frameworks</idno>
          <note type="staged-file">nilsen2015-implementation-theories-models-frameworks.txt, the project's staged copy</note>
          <note type="text-sha1">56931be6094538fafeed2a0b7e8a0e86a8a318ea</note>
          <note type="rights">cc-by</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>implementation-science</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">100 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a9" to="#a10" type="object_of_study" ana="#object_of_study" resp="#paper">theories, models, and frameworks used to describe, explain, guide, and evaluate implementation in implementation science</span>
      <span xml:id="t1" from="#a9" to="#a10" type="research_question" ana="#research_question" resp="#paper">how implementation theories, models, and frameworks differ in aims, assumptions, origins, and practical uses, and how they can be classified for appropriate selection</span>
      <span xml:id="t2" from="#a30" to="#a31" type="contribution" ana="#contribution" resp="#paper">a five-category taxonomy connecting three overarching aims of theoretical approaches in implementation science</span>
      <span xml:id="t3" from="#a1" to="#a2" type="claim_type" ana="#claim_type" resp="#paper">existence</span>
      <span xml:id="t4" from="#a32" to="#a33" type="phenomenon" ana="#phenomenon" resp="#paper">the proliferation, overlap, inconsistent naming, selection difficulty, and differing purposes of theoretical approaches in implementation science</span>
      <span xml:id="t5" from="#a15" to="#a18" type="method" ana="#method" resp="#paper">review<term>review</term></span>
      <span xml:id="t6" from="#a3" to="#a4" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="0.99">mechanisms<term>TAXONOMIC DIFFERENTIATION maps three overarching aims to five categories so researchers can select approaches by purpose</term></span>
      <span xml:id="t7" from="#a34" to="#a35" type="mechanisms" ana="#mechanisms[1]" resp="#tagger" cert="0.99">mechanisms<term>PROCESS MODELS organize research-to-practice translation into phases or stages from knowledge production to use</term></span>
      <span xml:id="t8" from="#a36" to="#a38" type="mechanisms" ana="#mechanisms[2]" resp="#tagger" cert="0.99">mechanisms<term>ACTION MODELS prescribe practical planning and execution stages for translating research into practice</term></span>
      <span xml:id="t9" from="#a39" to="#a40" type="mechanisms" ana="#mechanisms[3]" resp="#tagger" cert="0.99">mechanisms<term>DETERMINANT FRAMEWORKS map multilevel barriers and enablers onto implementation outcomes</term></span>
      <span xml:id="t10" from="#a43" to="#a44" type="mechanisms" ana="#mechanisms[4]" resp="#tagger" cert="0.99">mechanisms<term>SYSTEMS THINKING integrates components with within-level and cross-level relationships rather than treating determinants in isolation</term></span>
      <span xml:id="t11" from="#a59" to="#a60" type="mechanisms" ana="#mechanisms[5]" resp="#tagger" cert="0.99">mechanisms<term>COM-B RECIPROCITY links capability, opportunity, and motivation to behaviour and feeds behaviour back into the three components</term></span>
      <span xml:id="t12" from="#a62" to="#a63" type="mechanisms" ana="#mechanisms[6]" resp="#tagger" cert="0.99">mechanisms<term>NORMALIZATION combines sense making, engagement, collective action, and reflexive monitoring to explain embedding complex interventions</term></span>
      <span xml:id="t13" from="#a95" to="#a96" type="mechanisms" ana="#mechanisms[7]" resp="#tagger" cert="0.99">mechanisms<term>FORMALIZATION makes assumptions explicit and revisable so incorrect deductions can lead to adaptation, extension, or abandonment</term></span>
      <span xml:id="t14" from="#a68" to="#a69" type="limitations" ana="#limitations[0]" resp="#tagger" cert="0.99">The narrative review is selective and is not intended as a complete catalogue of implementation approaches.</span>
      <span xml:id="t15" from="#a70" to="#a71" type="limitations" ana="#limitations[1]" resp="#tagger" cert="0.99">The five categories overlap and can serve secondary functions outside their primary taxonomic category.</span>
      <span xml:id="t16" from="#a73" to="#a74" type="limitations" ana="#limitations[2]" resp="#tagger" cert="0.99">Determinant frameworks usually provide limited how-to guidance because determinants are too generic.</span>
      <span xml:id="t17" from="#a75" to="#a76" type="limitations" ana="#limitations[3]" resp="#tagger" cert="0.99">Process models often mention barriers and enablers without systematically structuring determinants of implementation success.</span>
      <span xml:id="t18" from="#a50" to="#a51" type="limitations" ana="#limitations[4]" resp="#tagger" cert="0.99">Implementation science lacks consensus on the definition, manifestation, and measurement of context.</span>
      <span xml:id="t19" from="#a45" to="#a46" type="limitations" ana="#limitations[5]" resp="#tagger" cert="0.99">Individual determinant assessment can assume linearity and miss interactions or unmeasured barriers and enablers.</span>
      <span xml:id="t20" from="#a83" to="#a86" type="limitations" ana="#limitations[6]" resp="#tagger" cert="0.99">A single theory offers partial understanding, while combinations may conceal incompatible assumptions.</span>
      <span xml:id="t21" from="#a91" to="#a92" type="limitations" ana="#limitations[7]" resp="#tagger" cert="0.99">Evidence is still needed on whether formal theoretical approaches improve implementation and under what conditions.</span>
      <span xml:id="t22" from="#a98" to="#a99" type="limitations" ana="#limitations[8]" resp="#tagger" cert="0.99">Theory can become a blinder that hides problems outside existing models or blocks new views of known problems.</span>
      <span xml:id="t23" from="#a11" to="#a12" type="concepts" ana="#concepts[0]" resp="#paper" cert="0.99">implementation science<term>implementation science</term></span>
      <span xml:id="t24" from="#a13" to="#a14" type="concepts" ana="#concepts[1]" resp="#paper" cert="0.99">implementation<term>implementation</term></span>
      <span xml:id="t25" from="#a13" to="#a14" type="concepts" ana="#concepts[2]" resp="#paper" cert="0.99">diffusion<term>diffusion</term></span>
      <span xml:id="t26" from="#a13" to="#a14" type="concepts" ana="#concepts[3]" resp="#paper" cert="0.99">dissemination<term>dissemination</term></span>
      <span xml:id="t27" from="#a13" to="#a14" type="concepts" ana="#concepts[4]" resp="#paper" cert="0.99">diffusion-dissemination-implementation continuum<term>diffusion-dissemination-implementation continuum</term></span>
      <span xml:id="t28" from="#a15" to="#a17" type="concepts" ana="#concepts[5]" resp="#paper" cert="0.99">narrative review<term>narrative review</term></span>
      <span xml:id="t29" from="#a19" to="#a21" type="concepts" ana="#concepts[6]" resp="#paper" cert="0.99">theory<term>theory</term></span>
      <span xml:id="t30" from="#a19" to="#a21" type="concepts" ana="#concepts[7]" resp="#paper" cert="0.99">good theory<term>good theory</term></span>
      <span xml:id="t31" from="#a22" to="#a23" type="concepts" ana="#concepts[8]" resp="#paper" cert="0.98">abstraction continuum<term>abstraction continuum</term></span>
      <span xml:id="t32" from="#a24" to="#a26" type="concepts" ana="#concepts[9]" resp="#paper" cert="0.99">model<term>model</term></span>
      <span xml:id="t33" from="#a27" to="#a29" type="concepts" ana="#concepts[10]" resp="#paper" cert="0.99">framework<term>framework</term></span>
      <span xml:id="t34" from="#a27" to="#a28" type="concepts" ana="#concepts[11]" resp="#paper" cert="0.98">descriptive categories<term>descriptive categories</term></span>
      <span xml:id="t35" from="#a34" to="#a35" type="concepts" ana="#concepts[12]" resp="#paper" cert="0.99">process models<term>process models</term></span>
      <span xml:id="t36" from="#a36" to="#a38" type="concepts" ana="#concepts[13]" resp="#paper" cert="0.99">action models<term>action models</term></span>
      <span xml:id="t37" from="#a39" to="#a40" type="concepts" ana="#concepts[14]" resp="#paper" cert="0.99">determinant frameworks<term>determinant frameworks</term></span>
      <span xml:id="t38" from="#a39" to="#a40" type="concepts" ana="#concepts[15]" resp="#paper" cert="0.99">barriers<term>barriers</term></span>
      <span xml:id="t39" from="#a39" to="#a40" type="concepts" ana="#concepts[16]" resp="#paper" cert="0.99">enablers<term>enablers</term></span>
      <span xml:id="t40" from="#a39" to="#a40" type="concepts" ana="#concepts[17]" resp="#paper" cert="0.99">implementation outcomes<term>implementation outcomes</term></span>
      <span xml:id="t41" from="#a43" to="#a44" type="concepts" ana="#concepts[18]" resp="#paper" cert="0.99">systems approach<term>systems approach</term></span>
      <span xml:id="t42" from="#a47" to="#a49" type="concepts" ana="#concepts[19]" resp="#paper" cert="0.99">context<term>context</term></span>
      <span xml:id="t43" from="#a52" to="#a53" type="concepts" ana="#concepts[20]" resp="#paper" cert="0.99">classic theories<term>classic theories</term></span>
      <span xml:id="t44" from="#a54" to="#a55" type="concepts" ana="#concepts[21]" resp="#paper" cert="0.99">Theory of Diffusion<term>Theory of Diffusion</term></span>
      <span xml:id="t45" from="#a54" to="#a55" type="concepts" ana="#concepts[22]" resp="#paper" cert="0.99">innovation attributes<term>innovation attributes</term></span>
      <span xml:id="t46" from="#a56" to="#a57" type="concepts" ana="#concepts[23]" resp="#paper" cert="0.99">implementation theories<term>implementation theories</term></span>
      <span xml:id="t47" from="#a58" to="#a60" type="concepts" ana="#concepts[24]" resp="#paper" cert="0.99">COM-B<term>COM-B</term></span>
      <span xml:id="t48" from="#a59" to="#a60" type="concepts" ana="#concepts[25]" resp="#paper" cert="0.99">capability, opportunity and motivation<term>capability, opportunity and motivation</term></span>
      <span xml:id="t49" from="#a59" to="#a60" type="concepts" ana="#concepts[26]" resp="#paper" cert="0.99">behaviour<term>behaviour</term></span>
      <span xml:id="t50" from="#a61" to="#a63" type="concepts" ana="#concepts[27]" resp="#paper" cert="0.99">Normalization Process Theory<term>Normalization Process Theory</term></span>
      <span xml:id="t51" from="#a62" to="#a63" type="concepts" ana="#concepts[28]" resp="#paper" cert="0.98">coherence<term>coherence</term></span>
      <span xml:id="t52" from="#a62" to="#a63" type="concepts" ana="#concepts[29]" resp="#paper" cert="0.98">cognitive participation<term>cognitive participation</term></span>
      <span xml:id="t53" from="#a62" to="#a63" type="concepts" ana="#concepts[30]" resp="#paper" cert="0.98">collective action<term>collective action</term></span>
      <span xml:id="t54" from="#a62" to="#a63" type="concepts" ana="#concepts[31]" resp="#paper" cert="0.98">reflexive monitoring<term>reflexive monitoring</term></span>
      <span xml:id="t55" from="#a64" to="#a65" type="concepts" ana="#concepts[32]" resp="#paper" cert="0.99">evaluation frameworks<term>evaluation frameworks</term></span>
      <span xml:id="t56" from="#a64" to="#a65" type="concepts" ana="#concepts[33]" resp="#paper" cert="0.99">RE-AIM<term>RE-AIM</term></span>
      <span xml:id="t57" from="#a64" to="#a65" type="concepts" ana="#concepts[34]" resp="#paper" cert="0.99">PRECEDE-PROCEED<term>PRECEDE-PROCEED</term></span>
      <span xml:id="t58" from="#a66" to="#a67" type="concepts" ana="#concepts[35]" resp="#paper" cert="0.98">acceptability<term>acceptability</term></span>
      <span xml:id="t59" from="#a66" to="#a67" type="concepts" ana="#concepts[36]" resp="#paper" cert="0.98">fidelity<term>fidelity</term></span>
      <span xml:id="t60" from="#a66" to="#a67" type="concepts" ana="#concepts[37]" resp="#paper" cert="0.98">sustainability<term>sustainability</term></span>
      <span xml:id="t61" from="#a79" to="#a80" type="concepts" ana="#concepts[38]" resp="#paper" cert="0.99">theory ladder climbing<term>theory ladder climbing</term></span>
      <span xml:id="t62" from="#a81" to="#a82" type="concepts" ana="#concepts[39]" resp="#paper" cert="0.99">grand implementation theory<term>grand implementation theory</term></span>
      <span xml:id="t63" from="#a89" to="#a90" type="concepts" ana="#concepts[40]" resp="#paper" cert="0.99">common sense<term>common sense</term></span>
      <span xml:id="t64" from="#a94" to="#a96" type="concepts" ana="#concepts[41]" resp="#paper" cert="0.99">formal theory<term>formal theory</term></span>
      <span xml:id="t65" from="#a87" to="#a88" type="concepts" ana="#concepts[42]" resp="#paper" cert="0.98">research-practice gap<term>research-practice gap</term></span>
      <span xml:id="t66" from="#a36" to="#a37" type="unhoused_relations" ana="#unhoused_relations[0]" resp="#tagger" cert="0.99">action models → process models<note>Action models are presented as process models that provide practical implementation guidance.</note></span>
      <span xml:id="t67" from="#a52" to="#a53" type="unhoused_relations" ana="#unhoused_relations[1]" resp="#tagger" cert="0.98">classic theories → action models<note>Classic theories may be considered passive relative to action models because they explain change without seeking to produce it.</note></span>
      <span xml:id="t68" from="#a5" to="#a6" type="unhoused_relations" ana="#unhoused_relations[2]" resp="#tagger" cert="0.99">poor theoretical underpinning → understanding implementation success or failure<note>Poor theoretical underpinning makes implementation success or failure harder to understand and explain.</note></span>
      <span xml:id="t69" from="#a7" to="#a8" type="unhoused_relations" ana="#unhoused_relations[3]" resp="#tagger" cert="0.99">many theoretical approaches → selection difficulty<note>The abundance of theoretical approaches makes choosing an appropriate one difficult.</note></span>
      <span xml:id="t70" from="#a16" to="#a17" type="unhoused_relations" ana="#unhoused_relations[4]" resp="#tagger" cert="0.99">narrative review → diversities and pluralities of understanding<note>Narrative reviews capture diverse and plural understandings through qualitative synthesis.</note></span>
      <span xml:id="t71" from="#a41" to="#a42" type="unhoused_relations" ana="#unhoused_relations[5]" resp="#tagger" cert="0.99">determinant frameworks → change mechanisms<note>Determinant frameworks do not address how change occurs or specify causal mechanisms.</note></span>
      <span xml:id="t72" from="#a45" to="#a46" type="unhoused_relations" ana="#unhoused_relations[6]" resp="#tagger" cert="0.99">individual assessment of determinants → determinant interactions<note>Assessing determinants individually ignores potentially important interactions among barriers and enablers.</note></span>
      <span xml:id="t73" from="#a83" to="#a84" type="unhoused_relations" ana="#unhoused_relations[7]" resp="#tagger" cert="0.99">single theory → complete implementation understanding<note>A single theory focused on one implementation aspect yields only partial understanding.</note></span>
      <span xml:id="t74" from="#a85" to="#a86" type="unhoused_relations" ana="#unhoused_relations[8]" resp="#tagger" cert="0.99">multiple theoretical approaches → contrasting assumptions<note>Combining theoretical approaches may mask contrasting assumptions even while improving coverage.</note></span>
      <span xml:id="t75" from="#a81" to="#a82" type="unhoused_relations" ana="#unhoused_relations[9]" resp="#tagger" cert="0.99">implementation complexity → grand implementation theory<note>Implementation&#x27;s complexity makes a universal grand implementation theory unlikely.</note></span>
      <span xml:id="t76" from="#a98" to="#a99" type="unhoused_relations" ana="#unhoused_relations[10]" resp="#tagger" cert="0.99">theory → unfamiliar problems<note>Theory may act as blinders that hide problems outside existing approaches or block new views of known problems.</note></span>
      <span xml:id="t77" from="#a95" to="#a97" type="unhoused_relations" ana="#unhoused_relations[11]" resp="#tagger" cert="0.99">formal theory → correction and cumulative knowledge<note>Formal theory supports examination, correction, and integration of facts into cumulative knowledge.</note></span>
      <span xml:id="t78" from="#a11" to="#a12" type="senses" ana="#senses[0]" resp="#tagger" cert="0.99">`implementation science` means scientific study of methods that promote systematic uptake of research and evidence-based practice into routine practice</span>
      <span xml:id="t79" from="#a13" to="#a14" type="senses" ana="#senses[1]" resp="#tagger" cert="0.99">`diffusion`, `dissemination`, and `implementation` mean passive spread, planned active spread, and integration of practices within a setting, respectively</span>
      <span xml:id="t80" from="#a19" to="#a20" type="senses" ana="#senses[2]" resp="#tagger" cert="0.99">`theory` means analytical principles or statements that structure observation, understanding, and explanation</span>
      <span xml:id="t81" from="#a24" to="#a26" type="senses" ana="#senses[3]" resp="#tagger" cert="0.99">`model` means a deliberate simplification with narrower explanatory scope, while `theory` is explanatory as well as descriptive</span>
      <span xml:id="t82" from="#a27" to="#a29" type="senses" ana="#senses[4]" resp="#tagger" cert="0.99">`framework` means a structure of descriptive categories and their presumed relations, without explanatory mechanisms</span>
      <span xml:id="t83" from="#a48" to="#a49" type="senses" ana="#senses[5]" resp="#tagger" cert="0.99">`context` means the conditions or surroundings in which something occurs, usually at a higher analytical level than the focal phenomenon</span>
      <span xml:id="t84" from="#a66" to="#a67" type="senses" ana="#senses[6]" resp="#tagger" cert="0.99">`sustainability` also means maintenance or institutionalization as an implementation outcome</span>
      <span xml:id="t85" from="#a89" to="#a90" type="senses" ana="#senses[7]" resp="#tagger" cert="0.99">`common sense` means shared tacit knowledge that can be treated as informal, non-codified theory</span>
      <span xml:id="t86" from="#a3" to="#a4" type="claim_relations" ana="#claim_relations[0]" resp="#tagger" cert="0.99">supports → a taxonomy of five theoretical-approach categories serving three implementation-science aims<note>note: This is the article&#x27;s central taxonomic contribution.</note></span>
      <span xml:id="t87" from="#a19" to="#a21" type="claim_relations" ana="#claim_relations[1]" resp="#tagger" cert="0.99">builds-on → general-literature distinctions among theory, model, and framework<note>note: The taxonomy begins from general conceptual distinctions before applying them to implementation science.</note></span>
      <span xml:id="t88" from="#a72" to="#a78" type="claim_relations" ana="#claim_relations[2]" resp="#tagger" cert="0.99">distinguishes-from → process models from determinant frameworks by temporal process perspective and determinant structure<note>note: The review states the contrast directly and explains its practical consequence.</note></span>
      <span xml:id="t89" from="#a70" to="#a71" type="claim_relations" ana="#claim_relations[3]" resp="#tagger" cert="0.99">qualifies → the separateness of the five taxonomy categories<note>note: The taxonomy is useful without claiming mutually exclusive categories.</note></span>
      <span xml:id="t90" from="#a73" to="#a74" type="claim_relations" ana="#claim_relations[4]" resp="#tagger" cert="0.99">critiques → determinant frameworks as practical how-to guides<note>note: The limitation is stated directly.</note></span>
      <span xml:id="t91" from="#a83" to="#a86" type="claim_relations" ana="#claim_relations[5]" resp="#tagger" cert="0.99">critiques → single-theory accounts of multifaceted implementation<note>note: The article balances partial single-theory accounts against risks of combining approaches.</note></span>
      <span xml:id="t92" from="#a91" to="#a93" type="claim_relations" ana="#claim_relations[6]" resp="#tagger" cert="0.99">recommends → empirical study of whether, how, and under which conditions theoretical approaches improve implementation<note>note: The review explicitly calls for empirical and developmental work.</note></span>
      <span xml:id="t93" from="#a13" to="#a14" type="concept_edges" ana="#concept_edges[0]" resp="#tagger" cert="0.99">implementation —part-of→ diffusion-dissemination-implementation continuum<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Direct categorical part-of statement. · the relation stated: Implementation is part of a diffusion-dissemination-implementation continuum.</note><term>implementation</term><term>diffusion-dissemination-implementation continuum</term></span>
      <span xml:id="t94" from="#a27" to="#a28" type="concept_edges" ana="#concept_edges[1]" resp="#tagger" cert="0.99">descriptive categories —part-of→ framework<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Explicit categorical composition via &#x27;consisting of&#x27;. · the relation stated: Descriptive categories are components of a framework.</note><term>descriptive categories</term><term>framework</term></span>
      <span xml:id="t95" from="#a25" to="#a26" type="concept_edges" ana="#concept_edges[2]" resp="#tagger" cert="0.99">model —contrasted-with→ theory<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: Explicit flat contrast marked by &#x27;whereas&#x27;. · the relation stated: A model is descriptive, whereas a theory is explanatory as well as descriptive.</note><term>model</term><term>theory</term></span>
      <span xml:id="t96" from="#a77" to="#a78" type="concept_edges" ana="#concept_edges[3]" resp="#tagger" cert="0.99">process models —contrasted-with→ determinant frameworks<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: Explicit categorical contrast; neither direction is causal. · the relation stated: Process models recognize a temporal sequence, whereas determinant frameworks do not explicitly take a process perspective.</note><term>process models</term><term>determinant frameworks</term></span>
      <span xml:id="t97" from="#a59" to="#a60" type="concept_edges" ana="#concept_edges[4]" resp="#tagger" cert="0.99">capability, opportunity and motivation —causes→ behaviour<note>the relation itself is separately evidenced · strength of the relation: 0.9 · note: Positive causal sign checked; flat theoretical assertion (&#x27;posits ... generate&#x27;) but not a necessary/sufficient empirical result. · the relation stated: Capability, opportunity, and motivation generate behaviour in COM-B.</note><term>capability, opportunity and motivation</term><term>behaviour</term></span>
      <span xml:id="t98" from="#a59" to="#a60" type="concept_edges" ana="#concept_edges[5]" resp="#tagger" cert="0.99">behaviour —causes→ capability, opportunity and motivation<note>the relation itself is separately evidenced · strength of the relation: 0.9 · note: Positive reciprocal causal direction checked; flat theoretical assertion. · the relation stated: Behaviour in turn influences the three COM-B components.</note><term>behaviour</term><term>capability, opportunity and motivation</term></span>
      <span xml:id="t99" from="#a94" to="#a97" type="concept_edges" ana="#concept_edges[6]" resp="#tagger" cert="0.99">formal theory —contrasted-with→ common sense<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: Flat comparative distinction; the relation is conceptual, not causal. · the relation stated: Formal theories are explicit and examinable, whereas common sense usually consists of implicit assumptions.</note><term>formal theory</term><term>common sense</term></span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> Making sense of implementation theories, models and frameworks</p>
        <p>Abstract</p>
        <p>Implementation science has progressed towards increased use of theoretical approaches to provide better understanding and explanation of how and why implementation succeeds or fails. <anchor xml:id="a1"/>The aim of this article is to propose a taxonomy that distinguishes between different categories of theories, models and frameworks in implementation science, to facilitate appropriate selection and application of relevant approaches in implementation research and practice and to foster cross-disciplinary dialogue among implementation researchers.<anchor xml:id="a2"/></p>
        <p><anchor xml:id="a3"/>Theoretical approaches used in implementation science have three overarching aims: describing and/or guiding the process of translating research into practice (process models); understanding and/or explaining what influences implementation outcomes (determinant frameworks, classic theories, implementation theories); and evaluating implementation (evaluation frameworks).<anchor xml:id="a4"/></p>
        <p>This article proposes five categories of theoretical approaches to achieve three overarching aims. These categories are not always recognized as separate types of approaches in the literature. While there is overlap between some of the theories, models and frameworks, awareness of the differences is important to facilitate the selection of relevant approaches. Most determinant frameworks provide limited “how-to” support for carrying out implementation endeavours since the determinants usually are too generic to provide sufficient detail for guiding an implementation process. And while the relevance of addressing barriers and enablers to translating research into practice is mentioned in many process models, these models do not identify or systematically structure specific determinants associated with implementation success. Furthermore, process models recognize a temporal sequence of implementation endeavours, whereas determinant frameworks do not explicitly take a process perspective of implementation.</p>
        <p>Keywords: Theory, Model, Framework, Evaluation, Context</p>
        <p>Background</p>
        <p>Implementation science was borne out of a desire to address challenges associated with the use of research to achieve more evidence-based practice (EBP) in health care and other areas of professional practice. Early implementation research was empirically driven and did not always pay attention to the theoretical underpinnings of implementation. Eccles et al. ([ 1 ]:108) remarked that this research seemed like “an expensive version of trial-and-error”. A review of guideline implementation strategies by Davies et al. [ 2 ] noted that only 10% of the studies identified provided an explicit rationale for their strategies. Mixed results of implementing EBP in various settings were often attributed to a limited theoretical basis [ 1 , 3 - 5 ]. <anchor xml:id="a5"/>Poor theoretical underpinning makes it difficult to understand and explain how and why implementation succeeds or fails, thus restraining opportunities to identify factors that predict the likelihood of implementation success and develop better strategies to achieve more successful implementation.<anchor xml:id="a6"/></p>
        <p>However, the last decade of implementation science has seen wider recognition of the need to establish the theoretical bases of implementation and strategies to facilitate implementation. There is mounting interest in the use of theories, models and frameworks to gain insights into the mechanisms by which implementation is more likely to succeed. Implementation studies now apply theories borrowed from disciplines such as psychology, sociology and organizational theory as well as theories, models and frameworks that have emerged from within implementation science. <anchor xml:id="a7"/>There are now so many theoretical approaches that some researchers have complained about the difficulties of choosing the most appropriate [ 6 - 11 ].<anchor xml:id="a8"/></p>
        <p><anchor xml:id="a9"/>This article seeks to further implementation science by providing a narrative review of the theories, models and frameworks applied in this research field. The aim is to describe and analyse how theories, models and frameworks have been applied in implementation science and propose a taxonomy that distinguishes between different approaches to advance clarity and achieve a common terminology. The ambition is to facilitate appropriate selection and application of relevant approaches in implementation studies and foster cross-disciplinary dialogue among implementation researchers.<anchor xml:id="a10"/> The importance of a clarifying taxonomy has evolved during the many discussions on theoretical approaches used within implementation science that the author has had over the past few years with fellow implementation researchers, as well as reflection on the utility of different approaches in various situations.</p>
        <p><anchor xml:id="a11"/>Implementation science is defined as the scientific study of methods to promote the systematic uptake of research findings and other EBPs into routine practice to improve the quality and effectiveness of health services and care [ 12 ].<anchor xml:id="a12"/> The terms knowledge translation, knowledge exchange, knowledge transfer, knowledge integration and research utilization are used to describe overlapping and interrelated research on putting various forms of knowledge, including research, to use [ 8 , 13 - 16 ]. <anchor xml:id="a13"/>Implementation is part of a diffusion-dissemination-implementation continuum: diffusion is the passive, untargeted and unplanned spread of new practices; dissemination is the active spread of new practices to the target audience using planned strategies; and implementation is the process of putting to use or integrating new practices within a setting [ 16 , 17 ].<anchor xml:id="a14"/></p>
        <p><anchor xml:id="a15"/>A narrative review of selective literature was undertaken to identify key theories, models and frameworks used in implementation science. <anchor xml:id="a16"/>The narrative review approach gathers information about a particular subject from many sources and is considered appropriate for summarizing and synthesizing the literature to draw conclusions about “what we know” about the subject. Narrative reviews yield qualitative results, with strengths in capturing diversities and pluralities of understanding [ 18 , 19 ].<anchor xml:id="a17"/> Six textbooks that provide comprehensive overviews of research regarding implementation science and implementation of EBP were consulted: Rycroft-Malone and Bucknall [ 20 ], Nutley et al. [ 21 ], Greenhalgh et al. [ 17 ], Grol et al. [ 22 ], Straus et al. [ 23 ] and Brownson et al. [ 24 ]. A few papers presenting overviews of theories, models and frameworks used in implementation science were also used: Estabrooks et al. [ 14 ], Sales et al. [ 4 ], Graham and Tetroe [ 25 ], Mitchell et al. [ 8 ], Flottorp et al. [ 26 ], Meyers et al. [ 27 ] and Tabak et al. [ 28 ]. In addition, Implementation Science (first published in 2006) was searched using the terms “theory”, “model” and “framework” to identify relevant articles. The titles and abstracts of the identified articles were scanned, and those that were relevant to the study aim were read in full.<anchor xml:id="a18"/></p>
        <p>Discussion</p>
        <p>Theories, models and frameworks in the general literature</p>
        <p><anchor xml:id="a19"/>Generally, a theory may be defined as a set of analytical principles or statements designed to structure our observation, understanding and explanation of the world [ 29 - 31 ].<anchor xml:id="a20"/> Authors usually point to a theory as being made up of definitions of variables, a domain where the theory applies, a set of relationships between the variables and specific predictions [ 32 - 35 ]. A “good theory” provides a clear explanation of how and why specific relationships lead to specific events.<anchor xml:id="a21"/> <anchor xml:id="a22"/>Theories can be described on an abstraction continuum. High abstraction level theories (general or grand theories) have an almost unlimited scope, middle abstraction level theories explain limited sets of phenomena and lower level abstraction theories are empirical generalizations of limited scope and application [ 30 , 36 ].<anchor xml:id="a23"/></p>
        <p><anchor xml:id="a24"/>A model typically involves a deliberate simplification of a phenomenon or a specific aspect of a phenomenon. Models need not be completely accurate representations of reality to have value [ 31 , 37 ]. Models are closely related to theory and the difference between a theory and a model is not always clear. <anchor xml:id="a25"/>Models can be described as theories with a more narrowly defined scope of explanation; a model is descriptive, whereas a theory is explanatory as well as descriptive [ 29 ].<anchor xml:id="a26"/></p>
        <p><anchor xml:id="a27"/>A framework usually denotes a structure, overview, outline, system or plan consisting of various descriptive categories, e.g. concepts, constructs or variables, and the relations between them that are presumed to account for a phenomenon [ 38 ].<anchor xml:id="a28"/> Frameworks do not provide explanations; they only describe empirical phenomena by fitting them into a set of categories [ 29 ].<anchor xml:id="a29"/></p>
        <p>Theories, models and frameworks in implementation science</p>
        <p><anchor xml:id="a30"/>It was possible to identify three overarching aims of the use of theories, models and frameworks in implementation science: (1) describing and/or guiding the process of translating research into practice, (2) understanding and/or explaining what influences implementation outcomes and (3) evaluating implementation. Theoretical approaches which aim at understanding and/or explaining influences on implementation outcomes (i.e. the second aim) can be further broken down into determinant frameworks, classic theories and implementation theories based on descriptions of their origins, how they were developed, what knowledge sources they drew on, stated aims and applications in implementation science. Thus, five categories of theoretical approaches used in implementation science can be delineated (Table 1 ; Figure 1 ):<anchor xml:id="a31"/></p>
        <p>Process models</p>
        <p>Determinant frameworks</p>
        <p>Classic theories</p>
        <p>Implementation theories</p>
        <p>Evaluation frameworks</p>
        <p>Five categories of theories, models and frameworks used in implementation science</p>
        <p>Three aims of the use of theoretical approaches in implementation science and the five categories of theories, models and frameworks.</p>
        <p><anchor xml:id="a32"/>Although theories, models and frameworks are distinct concepts, the terms are sometimes used interchangeably in implementation science [ 9 , 14 , 39 ]. A theory in this field usually implies some predictive capacity (e.g. to what extent do health care practitioners’ attitudes and beliefs concerning a clinical guideline predict their adherence to this guideline in clinical practice?) and attempts to explain the causal mechanisms of implementation. Models in implementation science are commonly used to describe and/or guide the process of translating research into practice (i.e. “implementation practice”) rather than to predict or analyse what factors influence implementation outcomes (i.e. “implementation research”). Frameworks in implementation science often have a descriptive purpose by pointing to factors believed or found to influence implementation outcomes (e.g. health care practitioners’ adoption of an evidence-based patient intervention). Neither models nor frameworks specify the mechanisms of change; they are typically more like checklists of factors relevant to various aspects of implementation.<anchor xml:id="a33"/></p>
        <p>Describing and/or guiding the process of translating research into practice</p>
        <p>Process models</p>
        <p><anchor xml:id="a34"/>Process models are used to describe and/or guide the process of translating research into practice. Models by Huberman [ 40 ], Landry et al. [ 41 ], the CIHR (Canadian Institutes of Health Research) Knowledge Model of Knowledge Translation [ 42 ], Davis et al. [ 43 ], Majdzadeh et al. [ 44 ] and the K2A (Knowledge-to-Action) Framework [ 15 ] outline phases or stages of the research-to-practice process, from discovery and production of research-based knowledge to implementation and use of research in various settings.<anchor xml:id="a35"/></p>
        <p>Early research-to-practice (or knowledge-to-action) models tended to depict rational, linear processes in which research was simply transferred from producers to users. However, subsequent models have highlighted the importance of facilitation to support the process and placed more emphasis on the contexts in which research is implemented and used. Thus, the attention has shifted from a focus on production, diffusion and dissemination of research to various implementation aspects [ 21 ].</p>
        <p><anchor xml:id="a36"/>So-called action (or planned action) models are process models that facilitate implementation by offering practical guidance in the planning and execution of implementation endeavours and/or implementation strategies.<anchor xml:id="a37"/> Action models elucidate important aspects that need to be considered in implementation practice and usually prescribe a number of stages or steps that should be followed in the process of translating research into practice.<anchor xml:id="a38"/> Action models have been described as active by Graham et al. ([ 45 ]:185) because they are used “to guide or cause change”. It should be noted that the terminology is not fully consistent, as some of these models are referred to as frameworks, for instance the Knowledge-to-Action Framework [ 46 ].</p>
        <p>Many of the action models originate from the nursing-led field of research use/utilization; well-known examples include the Stetler Model [ 47 ], the ACE (Academic Center for Evidence-Based Practice) Star Model of Knowledge Transformation [ 48 ], the Knowledge-to-Action Framework [ 13 ], the Iowa Model [ 49 , 50 ] and the Ottawa Model [ 51 , 52 ]. There are also numerous examples of similar “how-to-implement” models that have emerged from other fields, including models developed by Grol and Wensing [ 53 ], Pronovost et al. [ 54 ] and the Quality Implementation Framework [ 27 ], all of which are intended to provide support for planning and managing implementation endeavours.</p>
        <p>The how-to-implement models typically emphasize the importance of careful, deliberate planning, especially in the early stages of implementation endeavours. In many ways, they present an ideal view of implementation practice as a process that proceeds step-wise, in an orderly, linear fashion. Still, authors behind most models emphasize that the actual process is not necessarily sequential. Many of the action models mentioned here have been subjected to testing or evaluation, and some have been widely applied in empirical research, underscoring their usefulness [ 9 , 55 ].</p>
        <p>The process models vary with regard to how they were developed. Models such as the Stetler Model [ 47 , 56 ] and the Iowa Model [ 49 , 50 ] were based on the originators’ own experiences of implementing new practices in various settings (although they were also informed by research and expert opinion). In contrast, models such as the Knowledge-to-Action Framework [ 45 ] and the Quality Implementation Framework [ 27 ] have relied on literature reviews of theories, models, frameworks and individual studies to identify key features of successful implementation endeavours.</p>
        <p>Understanding and explaining what influences implementation outcomes</p>
        <p>Determinant frameworks</p>
        <p><anchor xml:id="a39"/>Determinant frameworks describe general types (also referred to as classes or domains) of determinants that are hypothesized or have been found to influence implementation outcomes, e.g. health care professionals’ behaviour change or adherence to a clinical guideline. Each type of determinant typically comprises a number of individual barriers (hinders, impediments) and/or enablers (facilitators), which are seen as independent variables that have an impact on implementation outcomes, i.e. the dependent variable.<anchor xml:id="a40"/> Some frameworks also hypothesize relationships between these determinants (e.g. [ 17 , 57 , 58 ]), whereas others recognize such relationships without clarifying them (e.g. [ 59 , 60 ]). Information about what influences implementation outcomes is potentially useful for designing and executing implementation strategies that aim to change relevant determinants.</p>
        <p><anchor xml:id="a41"/>The determinant frameworks do not address how change takes place or any causal mechanisms, underscoring that they should not be considered theories.<anchor xml:id="a42"/> Many frameworks are multilevel, identifying determinants at different levels, from the individual user or adopter (e.g. health care practitioners) to the organization and beyond. Hence, these integrative frameworks recognize that implementation is a multidimensional phenomenon, with multiple interacting influences.</p>
        <p>The determinant frameworks were developed in different ways. Many frameworks (e.g. [ 17 , 21 , 22 , 57 , 59 , 61 ]) were developed by synthesizing results from empirical studies of barriers and enablers for implementation success. Other frameworks have relied on existing determinant frameworks and relevant theories in various disciplines, e.g. the frameworks by Gurses et al. [ 58 ] and CFIR (Consolidated Framework for Implementation Research) [ 60 ].</p>
        <p>Several frameworks have drawn extensively on the originator’s own experiences of implementing new practices. For instance, the Understanding-User-Context Framework [ 62 ] and Active Implementation Frameworks [ 63 ] were both based on a combination of literature reviews and the originators’ implementation experiences. Meanwhile, PARIHS (Promoting Action on Research Implementation in Health Services) [ 5 , 64 ] emerged from the observation that successful implementation in health care might be premised on three key determinants (characteristics of the evidence, context and facilitation), a proposition which was then analysed in four empirical case studies; PARIHS has subsequently undergone substantial research and development work [ 64 ] and has been widely applied [ 65 ].</p>
        <p>Theoretical Domains Framework represents another approach to developing determinant frameworks. It was constructed on the basis of a synthesis of 128 constructs related to behaviour change found in 33 behaviour change theories, including many social cognitive theories [ 10 ]. The constructs are sorted into 14 theoretical domains (originally 12 domains), e.g. knowledge, skills, intentions, goals, social influences and beliefs about capabilities [ 66 ]. Theoretical Domains Framework does not specify the causal mechanisms found in the original theories, thus sharing many characteristics with determinant frameworks.</p>
        <p>The determinant frameworks account for five types of determinants, as shown in Table 2 , which provides details of eight of the most commonly cited frameworks in implementation science. The frameworks are superficially quite disparate, with a broad range of terms, concepts and constructs as well as different outcomes, yet they are quite similar with regard to the general types of determinants they account for. Hence, implementation researchers agree to a large extent on what the main influences on implementation outcomes are, albeit to a lesser extent on which terms that are best used to describe these determinants.</p>
        <p>Implementation determinants and outcomes in eight determinant frameworks</p>
        <p>The frameworks describe “implementation objects” in terms of research, guidelines, interventions, innovations and evidence (i.e. research-based knowledge in a broad sense). Outcomes differ correspondingly, from adherence to guidelines and research use, to successful implementation of interventions, innovations, evidence, etc. (i.e. the application of research-based knowledge in practice). The relevance of the end users (e.g. patients, consumers or community populations) of the implemented object (e.g. an EBP) is not explicitly addressed in some frameworks (e.g. [ 17 , 21 , 67 ]), suggesting that this is an area where further research is needed for better analysis of how various end users may influence implementation effectiveness.</p>
        <p><anchor xml:id="a43"/>Determinant frameworks imply a systems approach to implementation because they point to multiple levels of influence and acknowledge that there are relationships within and across the levels and different types of determinants. A system can be understood only as an integrated whole because it is composed not only of the sum of its components but also by the relationships among those components [ 68 ].<anchor xml:id="a44"/> <anchor xml:id="a45"/>However, determinants are often assessed individually in implementation studies (e.g. [ 69 - 72 ]), (implicitly) assuming a linear relationship between the determinants and the outcomes and ignoring that individual barriers and enablers may interact in various ways that can be difficult to predict. For instance, there could be synergistic effects such that two seemingly minor barriers constitute an important obstacle to successful outcomes if they interact.<anchor xml:id="a46"/> Another issue is whether all relevant barriers and enablers are examined in these studies, which are often based on survey questionnaires, and are thus biased by the researcher’s selection of determinants. Surveying the perceived importance of a finite set of predetermined barriers can yield insights into the relative importance of these particular barriers but may overlook factors that independently affect implementation outcomes. Furthermore, there is the issue of whether the barriers and enablers are the actual determinants (i.e. whether they have actually been experienced or encountered) and the extent to which they are perceived to exist (i.e. they are more hypothetical barriers and enablers). The perceived importance of particular factors may not always correspond with the actual importance.</p>
        <p><anchor xml:id="a47"/>The context is an integral part of all the determinant frameworks. Described as “an important but poorly understood mediator of change and innovation in health care organizations” ([ 73 ]:79), the context lacks a unifying definition in implementation science (and related fields such as organizational behaviour and quality improvement). <anchor xml:id="a48"/>Still, context is generally understood as the conditions or surroundings in which something exists or occurs, typically referring to an analytical unit that is higher than the phenomena directly under investigation.<anchor xml:id="a49"/> The role afforded the context varies, from studies (e.g. [ 74 - 77 ]) that essentially view the context in terms of a physical “environment or setting in which the proposed change is to be implemented” ([ 5 ]:150) to studies (e.g. [ 21 , 74 , 78 ]) that assume that the context is something more active and dynamic that greatly affects the implementation process and outcomes. <anchor xml:id="a50"/>Hence, although implementation science researchers agree that the context is a critically important concept for understanding and explaining implementation, there is a lack of consensus regarding how this concept should be interpreted, in what ways the context is manifested and the means by which contextual influences might be captured in research.<anchor xml:id="a51"/></p>
        <p>The different types of determinants specified in determinant frameworks can be linked to classic theories. Thus, psychological theories that delineate factors influencing individual behaviour change are relevant for analysing how user/adopter characteristics affect implementation outcomes, whereas organizational theories concerning organizational climate, culture and leadership are more applicable for addressing the influence of the context on implementation outcomes.</p>
        <p>Classic theories</p>
        <p><anchor xml:id="a52"/>Implementation researchers are also wont to apply theories from other fields such as psychology, sociology and organizational theory. These theories have been referred to as classic (or classic change) theories to distinguish them from research-to-practice models [ 45 ]. They might be considered passive in relation to action models because they describe change mechanisms and explain how change occurs without ambitions to actually bring about change.<anchor xml:id="a53"/></p>
        <p>Psychological behaviour change theories such as the Theory of Reasoned Action [ 79 ], the Social Cognitive Theory [ 80 , 81 ], the Theory of Interpersonal Behaviour [ 82 ] and the Theory of Planned Behaviour [ 83 ] have all been widely used in implementation science to study determinants of “clinical behaviour” change [ 84 ]. Theories such as the Cognitive Continuum Theory [ 85 ], the Novice-Expert Theory [ 86 ], the Cognitive-Experiential Self-Theory [ 87 ] and habit theories (e.g. [ 88 , 89 ]) may also be applicable for analysing cognitive processes involved in clinical decision-making and implementing EBP, but they are not as extensively used as the behaviour change theories.</p>
        <p>Theories regarding the collective (such as health care teams) or other aggregate levels are relevant in implementation science, e.g. theories concerning professions and communities of practice, as well as theories concerning the relationships between individuals, e.g. social networks and social capital [ 14 , 53 , 90 - 93 ]. However, their use is not as prevalent as the individual-level theories.</p>
        <p>There is increasing interest among implementation researchers in using theories concerning the organizational level because the context of implementation is becoming more widely acknowledged as an important influence on implementation outcomes. Theories concerning organizational culture, organizational climate, leadership and organizational learning are relevant for understanding and explaining organizational influences on implementation processes [ 21 , 53 , 57 , 94 - 101 ]. Several organization-level theories might have relevance for implementation science. For instance, Estabrooks et al. [ 14 ] have proposed the use of the Situated Change Theory [ 102 ] and the Institutional Theory [ 103 , 104 ], whereas Plsek and Greenhalgh [ 105 ] have suggested the use of complexity science [ 106 ] for better understanding of organizations. Meanwhile, Grol et al. [ 22 ] have highlighted the relevance of economic theories and theories of innovative organizations. However, despite increased interest in organizational theories, their actual use in empirical implementation studies thus far is relatively limited.</p>
        <p><anchor xml:id="a54"/>The Theory of Diffusion, as popularized through Rogers’ work on the spread of innovations, has also influenced implementation science. The theory’s notion of innovation attributes, i.e. relative advantage, compatibility, complexity, trialability and observability [ 107 ], has been widely applied in implementation science, both in individual studies (e.g. [ 108 - 110 ]) and in determinant frameworks (e.g. [ 17 , 58 , 60 ]) to assess the extent to which the characteristics of the implementation object (e.g. a clinical guideline) affect implementation outcomes.<anchor xml:id="a55"/> Furthermore, the Theory of Diffusion highlights the importance of intermediary actors (opinion leaders, change agents and gate-keepers) for successful adoption and implementation [ 107 ], which is reflected in roles described in numerous implementation determinant frameworks (e.g. [ 63 , 64 ]) and implementation strategy taxonomies (e.g. [ 111 - 114 ]). The Theory of Diffusion is considered the single most influential theory in the broader field of knowledge utilization of which implementation science is a part [ 115 ].</p>
        <p>Implementation theories</p>
        <p><anchor xml:id="a56"/>There are also numerous theories that have been developed or adapted by researchers for potential use in implementation science to achieve enhanced understanding and explanation of certain aspects of implementation. Some of these have been developed by modifying certain features of existing theories or concepts, e.g. concerning organizational climate and culture. Examples include theories such as Implementation Climate [ 116 ], Absorptive Capacity [ 117 ] and Organizational Readiness [ 118 ].<anchor xml:id="a57"/> The adaptation allows researchers to prioritize aspects considered to be most critical to analyse issues related to the how and why of implementation, thus improving the relevance and appropriateness to the particular circumstances at hand.</p>
        <p><anchor xml:id="a58"/>COM-B (Capability, Opportunity, Motivation and Behaviour) represents another approach to developing theories that might be applicable in implementation science. This theory began by identifying motivation as a process that energizes and directs behaviour. Capability and opportunity were added as necessary conditions for a volitional behaviour to occur, given sufficient motivation, on the basis of a US consensus meeting of behavioural theorists and a principle of US criminal law (which considers prerequisites for performance of specified volitional behaviours) [ 119 ]. <anchor xml:id="a59"/>COM-B posits that capability, opportunity and motivation generate behaviour, which in turn influences the three components. Opportunity and capability can influence motivation, while enacting a behaviour can alter capability, motivation and opportunity [ 66 ].<anchor xml:id="a60"/></p>
        <p><anchor xml:id="a61"/>Another theory used in implementation science, the Normalization Process Theory [ 120 ], began life as a model, constructed on the basis of empirical studies of the implementation of new technologies [ 121 ]. The model was subsequently expanded upon and developed into a theory as change mechanisms and interrelations between various constructs were delineated [ 122 ]. <anchor xml:id="a62"/>The theory identifies four determinants of embedding (i.e. normalizing) complex interventions in practice (coherence or sense making, cognitive participation or engagement, collective action and reflexive monitoring) and the relationships between these determinants [ 123 ].<anchor xml:id="a63"/></p>
        <p>Evaluating implementation</p>
        <p>Evaluation frameworks</p>
        <p><anchor xml:id="a64"/>There is a category of frameworks that provide a structure for evaluating implementation endeavours. Two common frameworks that originated in public health are RE-AIM (Reach, Effectiveness, Adoption, Implementation, Maintenance) [ 124 ] and PRECEDE-PROCEED (Predisposing, Reinforcing and Enabling Constructs in Educational Diagnosis and Evaluation-Policy, Regulatory, and Organizational Constructs in Educational and Environmental Development) [ 125 ]. Both frameworks specify implementation aspects that should be evaluated as part of intervention studies.<anchor xml:id="a65"/></p>
        <p><anchor xml:id="a66"/>Proctor et al. [ 126 ] have developed a framework of implementation outcomes that can be applied to evaluate implementation endeavours. On the basis of a narrative literature review, they propose eight conceptually distinct outcomes for potential evaluation: acceptability, adoption (also referred to as uptake), appropriateness, costs, feasibility, fidelity, penetration (integration of a practice within a specific setting) and sustainability (also referred to as maintenance or institutionalization).<anchor xml:id="a67"/></p>
        <p>Although evaluation frameworks may be considered in a category of their own, theories, models and frameworks from the other four categories can also be applied for evaluation purposes because they specify concepts and constructs that may be operationalized and measured. For instance, Theoretical Domains Framework (e.g. [ 127 , 128 ]), and Normalization Process Theory [ 129 ] and COM-B (e.g. [ 130 , 131 ]) have all been widely used as evaluation frameworks. Furthermore, many theories, models and frameworks have spawned instruments that serve evaluation purposes, e.g. tools linked to PARIHS [ 132 , 133 ], CFIR [ 134 ] and Theoretical Domains Framework [ 135 ]. Other examples include the EBP Implementation Scale to measure the extent to which EBP is implemented [ 136 ] and the BARRIERS Scale to identify barriers to research use [ 137 ], as well as instruments to operationalize theories such as Implementation Climate [ 138 ] and Organizational Readiness [ 139 ].</p>
        <p>Summary</p>
        <p>Implementation science has progressed towards increased use of theoretical approaches to address various implementation challenges. <anchor xml:id="a68"/>While this article is not intended as a complete catalogue of all individual approaches available in implementation science, it is obvious that the menu of potentially useable theories, models and frameworks is extensive.<anchor xml:id="a69"/> Researchers in the field have pragmatically looked into other fields and disciplines to find relevant approaches, thus emphasizing the interdisciplinary and multiprofessional nature of the field.</p>
        <p>This article proposes a taxonomy of five categories of theories, models and frameworks used in implementation science. These categories are not always recognized as separate types of approaches in the literature. For instance, systematic reviews and overviews by Graham and Tetroe [ 25 ], Mitchell et al. [ 8 ], Flottorp et al. [ 26 ], Meyers et al. [ 27 ] and Tabak et al. [ 28 ] have not distinguished between process models, determinant frameworks or classic theories because they all deal with factors believed or found to have an impact on implementation processes and outcomes. However, what matters most is not how an individual approach is labelled; it is important to recognize that these theories, models and frameworks differ in terms of their assumptions, aims and other characteristics, which have implications for their use.</p>
        <p><anchor xml:id="a70"/>There is considerable overlap between some of the categories. Thus, determinant frameworks, classic theories and implementation theories can also help to guide implementation practice (i.e. functioning as action models), because they identify potential barriers and enablers that might be important to address when undertaking an implementation endeavour. They can also be used for evaluation because they describe aspects that might be important to evaluate.<anchor xml:id="a71"/> A framework such as the Active Implementation Frameworks [ 68 ] appears to have a dual aim of providing hands-on support to implement something and identifying determinants of this implementation that should be analysed. Somewhat similarly, PARIHS [ 5 ] can be used by “anyone either attempting to get evidence into practice, or anyone who is researching or trying to better understand implementation processes and influences” ([ 64 ]:120), suggesting that it has ambitions that go beyond its primary function as a determinant framework.</p>
        <p><anchor xml:id="a72"/>Despite the overlap between different theories, models and frameworks used in implementation science, knowledge about the three overarching aims and five categories of theoretical approaches is important to identify and select relevant approaches in various situations. <anchor xml:id="a73"/>Most determinant frameworks provide limited “how-to” support for carrying out implementation endeavours since the determinants may be too generic to provide sufficient detail for guiding users through an implementation process.<anchor xml:id="a74"/> <anchor xml:id="a75"/>While the relevance of addressing barriers and enablers to translating research into practice is mentioned in many process models, these models do not identify or systematically structure specific determinants associated with implementation success.<anchor xml:id="a76"/> <anchor xml:id="a77"/>Another key difference is that process models recognize a temporal sequence of implementation endeavours, whereas determinant frameworks do not explicitly take a process perspective of implementation since the determinants typically relate to implementation as a whole.<anchor xml:id="a78"/></p>
        <p><anchor xml:id="a79"/>Theories applied in implementation science can be characterized as middle level. Higher level theories can be built from theories at lower abstraction levels, so-called theory ladder climbing [ 140 ].<anchor xml:id="a80"/> May [ 141 ] has discussed how a “general theory of implementation” might be constructed by linking the four constructs of Normalization Process Theory with constructs from relevant sociology and psychology theories to provide a more comprehensive explanation of the constituents of implementation processes. <anchor xml:id="a81"/>Still, it seems unlikely that there will ever be a grand implementation theory since implementation is too multifaceted and complex a phenomenon to allow for universal explanations.<anchor xml:id="a82"/> There has been debate in the policy implementation research field for many years whether researchers should strive to produce a theory applicable to public policy as a whole [ 38 ]. However, policy implementation researchers have increasingly argued that it would be a futile undertaking because “the world is too complex and there are too many causes of outcomes to allow for parsimonious explanation” ([ 37 ]:31). Determinant frameworks in implementation science clearly suggest that many different theories are relevant for understanding and explaining the many influences on implementation.</p>
        <p><anchor xml:id="a83"/>The use of a single theory that focuses only on a particular aspect of implementation will not tell the whole story. Choosing one approach often means placing weight on some aspects (e.g. certain causal factors) at the expense of others, thus offering only partial understanding.<anchor xml:id="a84"/> <anchor xml:id="a85"/>Combining the merits of multiple theoretical approaches may offer more complete understanding and explanation, yet such combinations may mask contrasting assumptions regarding key issues.<anchor xml:id="a86"/> For instance, are people driven primarily by their individual beliefs and motivation or does a pervasive organizational culture impose norms and values that regulate how people behave and make individual characteristics relatively unimportant? Is a particular behaviour primarily influenced by reflective thought processes or is it an automatically enacted habit? Furthermore, different approaches may require different methods, based on different epistemological and ontological assumptions.</p>
        <p><anchor xml:id="a87"/>There is a current wave of optimism in implementation science that using theoretical approaches will contribute to reducing the research-practice gap [ 4 , 10 , 11 , 63 , 142 ].<anchor xml:id="a88"/> Although the use of theories, models and frameworks has many advocates in implementation science, there have also been critics [ 143 , 144 ], who have argued that theory is not necessarily better than common sense for guiding implementation. <anchor xml:id="a89"/>Common sense has been defined as a group’s shared tacit knowledge concerning a phenomenon [ 145 ]. One could argue that common sense about how or why something works (or does not) also constitutes a theory, albeit an informal and non-codified one.<anchor xml:id="a90"/> <anchor xml:id="a91"/>In either case, empirical research is needed to study how and the extent to which the use of implementation theories, models and frameworks contributes to more effective implementation and under what contextual conditions or circumstances they apply (and do not apply).<anchor xml:id="a92"/> It is also important to explore how the current theoretical approaches can be further developed to better address implementation challenges. Hence, both inductive construction of theory and deductive application of theory are needed.<anchor xml:id="a93"/></p>
        <p><anchor xml:id="a94"/>While the use of theory does not necessarily yield more effective implementation than using common sense, there are certain advantages to applying formal theory over common sense (i.e. informal theory). <anchor xml:id="a95"/>Theories are explicit and open to question and examination; common sense usually consists of implicit assumptions, beliefs and ways of thinking and is therefore more difficult to challenge. If deductions from a theory are incorrect, the theory can be adapted, extended or abandoned.<anchor xml:id="a96"/> Theories are more consistent with existing facts than common sense, which typically means that a hypothesis based on an established theory is a more educated guess than one based on common sense. Furthermore, theories give individual facts a meaningful context and contribute towards building an integrated body of knowledge, whereas common sense is more likely to produce isolated facts [ 145 , 146 ].<anchor xml:id="a97"/> <anchor xml:id="a98"/>On the other hand, theory may serve as blinders, as suggested by Kuhn [ 147 ] and Greenwald et al. [ 148 ], causing us to ignore problems that do not fit into existing theories, models and frameworks or hindering us from seeing known problems in new ways.<anchor xml:id="a99"/> Theorizing about implementation should therefore not be an abstract academic exercise unconnected with the real world of implementation practice. In the words of Immanuel Kant, “Experience without theory is blind, but theory without experience is mere intellectual play”.</p>
        <p>Acknowledgements</p>
        <p>I am grateful to Bianca Albers, Susanne Bernhardsson (special thanks), Dean L. Fixsen, Karen Grimmer, Ursula Reichenpfader and Kerstin Roback for constructive comments on drafts of this article. Also, thanks are due to Margit Neher, Justin Presseau and Jeanette Wassar Kirk for their input.</p>
        <p>Footnotes</p>
        <p>References<anchor xml:id="a100"/></p>
    </body>
  </text>
</TEI>
