Page - 2 - in Applied Interdisciplinary Theory in Health Informatics - Knowledge Base for Practitioners

First, she distinguished carefully between a theory (a set of analytical principles designed to structure our observations, understanding and explanation of a phenomenon in the world; a theory must be explanatory and predictive as well as descriptive), a framework (a structure, overview or plan consisting of various elements, concepts, or variables and their relationships, intended to describe a phenomenon) and a model (a deliberate simplification of a phenomenon or part of a phenomenon, typically descriptive). Unlike theories, frameworks and models do not specify the mechanisms of change. Second, she identified five important categories of theory, model or framework, based largely on their origin and intended use [1]: 1. Process models: these typically specify the steps to be followed to achieve some goal. A historic example relevant to health informatics could be the waterfall model for software engineering (Figure 1) 2. Determinant frameworks: a list of key determinants (e.g. barriers and enablers of change) and their relationships that may influence project outcome. An example relevant to health informatics is Schneiderman‘s checklist of eight user interface features associated with high usability (see Box 1) [2] 3. Classic theories: these are predictive theories that arise from external disciplines (e.g. psychology, sociology or management science) that can assist understanding and / or explanation. An example relevant to health informatics is Michie’s COM-B theory: Behaviour change requires Capability, Opportunity and Motivation [3] 4. Implementation theories: theories that arise from within the implementation science discipline that can assist understanding and / or explanation. Note that this category was named by Nilsen from the perspective of implementation science. In our case, an “implementation theory” might become a Classic theory, and I would like to substitute “health informatics theories” for this 4 th category, i.e. theories arising from within the health informatics discipline. An example of an health informatics theory is van der Lei’s suggestion that data collected for one clinical purpose can rarely be used for another purpose without careful reassessment [4] Figure 1. The Waterfall model for software engineering (By Peter Kemp / Paul Smith - Adapted from Paul Smith's work at wikipedia, CC BY 3.0, https://commons.wikimedia.org/w/index.php?curid=10633070Carver & Scheier 1982). J.C.Wyatt /TheNeed forTheory to InformClinical InformationSystems2