<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v22i5e16921</article-id>
      <article-id pub-id-type="pmid">32427110</article-id>
      <article-id pub-id-type="doi">10.2196/16921</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Adopting Patient Portals in Hospitals: Qualitative Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Wiig</surname>
            <given-names>Siri</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Choi</surname>
            <given-names>Sung</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Goniewicz</surname>
            <given-names>Krzysztof</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Jambaulikar</surname>
            <given-names>Guru</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>van Lettow</surname>
            <given-names>Britt</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Hulter</surname>
            <given-names>Pauline</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Erasmus School of Health Policy &#38; Management</institution>
            <institution>Erasmus University Rotterdam</institution>
            <addr-line>Burgemeester Oudlaan 50</addr-line>
            <addr-line>Rotterdam, 3062 PA</addr-line>
            <country>Netherlands</country>
            <phone>31 618406943</phone>
            <email>hulter@eshpm.eur.nl</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5545-178X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Pluut</surname>
            <given-names>Bettine</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7984-8279</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Leenen-Brinkhuis</surname>
            <given-names>Christine</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3560-3229</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>de Mul</surname>
            <given-names>Marleen</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3447-5920</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Ahaus</surname>
            <given-names>Kees</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9973-3746</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Weggelaar-Jansen</surname>
            <given-names>Anne Marie</given-names>
          </name>
          <degrees>MCM, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7786-6326</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Erasmus School of Health Policy &#38; Management</institution>
        <institution>Erasmus University Rotterdam</institution>
        <addr-line>Rotterdam</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Dutch Hospital Association</institution>
        <addr-line>Utrecht</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Eindhoven University of Technology</institution>
        <addr-line>Eindhoven</addr-line>
        <country>Netherlands</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Pauline Hulter <email>hulter@eshpm.eur.nl</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>5</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>19</day>
        <month>5</month>
        <year>2020</year>
      </pub-date>
      <volume>22</volume>
      <issue>5</issue>
      <elocation-id>e16921</elocation-id>
      <history>
        <date date-type="received">
          <day>5</day>
          <month>11</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>6</day>
          <month>1</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>2</day>
          <month>3</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>5</day>
          <month>3</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Pauline Hulter, Bettine Pluut, Christine Leenen-Brinkhuis, Marleen de Mul, Kees Ahaus, Anne Marie Weggelaar-Jansen. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 19.05.2020.</copyright-statement>
      <copyright-year>2020</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://www.jmir.org/2020/5/e16921/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Theoretical models help to explain or predict the adoption of electronic health (eHealth) technology and illustrate the complexity of the adoption process. These models provide insights into general factors that influence the use of eHealth technology. However, they do not give hospitals much actionable knowledge on how to facilitate the adoption process.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>Our study aims to provide insights into patient portal adoption processes among patients and hospital staff, including health care professionals (HCPs), managers, and administrative clerks. Studying the experiences and views of stakeholders answers the following question: How can hospitals encourage patients and HCPs to adopt a patient portal?</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted 22 semistructured individual and group interviews (n=69) in 12 hospitals and four focus groups with members of national and seminational organizations and patient portal suppliers (n=53).</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The effort hospitals put into adopting patient portals can be split into three themes. First, inform patients and HCPs about the portal. This communication strategy has four objectives: users should (1) know about the portal, (2) know how the portal works, (3) know that action on the portal is required, and (4) know where to find help with the portal. Second, embed the patient portal in the daily routine of HCPs and management. This involves three forms of support: (1) hospital policy, (2) management by monitoring the numbers, and (3) a structured implementation strategy that includes all staff of one department. Third, try to adjust the portal to meet patients’ needs to optimize user-friendliness in two ways: (1) use patients’ feedback and (2) focus on optimizing for patients with special needs (eg, low literacy and low digital skills).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Asking stakeholders what they have learned from their efforts to stimulate patient portal use in hospitals elicited rich insights into the adoption process. These insights are missing in the theoretical models. Therefore, our findings help to translate the relatively abstract factors one finds in theoretical models to the everyday pragmatics of eHealth projects in hospitals.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>patient portal</kwd>
        <kwd>adoption</kwd>
        <kwd>adoption processes</kwd>
        <kwd>eHealth</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Electronic health (eHealth) technology is generally considered promising for improving both the well-being and health of patients and the efficiency and effectiveness of the health care organization [<xref ref-type="bibr" rid="ref1">1</xref>]. However, several studies show that its promise is not always fulfilled [<xref ref-type="bibr" rid="ref1">1</xref>] and the results on the benefits gained are diverse [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. This also applies to patient portals [<xref ref-type="bibr" rid="ref2">2</xref>], which have sparked the interest of researchers, government policy makers, and health care organizations.</p>
      <p>Previous studies define a patient portal in various ways [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. Some consider them the same as a personal health record (PHR) [<xref ref-type="bibr" rid="ref3">3</xref>]. Others regard them as a class of PHR [<xref ref-type="bibr" rid="ref4">4</xref>]: whereas health care organizations own and control patient portals, PHRs are owned and controlled by patients themselves [<xref ref-type="bibr" rid="ref5">5</xref>]. Grünloh et al [<xref ref-type="bibr" rid="ref6">6</xref>] define patient portals as “provider-tethered applications that allow patients to access, but not to control, certain health care information (eg, their EHR [electronic health record]) and provide communication and administrative functions (eg, secure messaging, appointment booking, and prescription refill requests).” Wildenbos [<xref ref-type="bibr" rid="ref7">7</xref>] adds the possibility of authorizing informal caregivers to share access to patient portals.</p>
      <p>Despite its technological focus and aim, the success or failure of a patient portal relies on how it is used by patients and staff, such as health care professionals (HCPs), managers, and administrative clerks [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. A systematic review shows often-limited use by patients and HCPs for seven nontechnical reasons [<xref ref-type="bibr" rid="ref2">2</xref>]: (1) patients worry about the confidentiality of their personal health data, (2) patients are unaware of the portal, have no digital access, or think it will not be useful, (3) patients have low health literacy or find using the portal too complicated, (4) HCPs worry about increased workload and disruptions to their usual tasks, (5) HCPs lack the digital skills to interact with patients, (6) HCPs worry that they cannot respond fast enough to patients’ questions, and (7) HCPs are concerned that they can be held liable [<xref ref-type="bibr" rid="ref2">2</xref>]. All seven reasons hinder the adoption of patient portals [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      <p>Researchers have developed theoretical models to explain or predict the adoption of eHealth technologies, including patient portals. Two systematic reviews on information technology adoption both mention three frequently used acceptance and adoption models [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Strikingly, these three general models are applied in all societal domains, not just health care [<xref ref-type="bibr" rid="ref9">9</xref>]. <xref ref-type="table" rid="table1">Table 1</xref> details these most-used models to facilitate an understanding of their ideas on the adoption process [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref20">20</xref>]. The table also includes the recently developed NASSS (nonadoption, abandonment, scale-up, spread, and sustainability) framework [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Theoretical acceptance and adoption models.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="90"/>
          <col width="90"/>
          <col width="50"/>
          <col width="90"/>
          <col width="300"/>
          <col width="190"/>
          <col width="190"/>
          <thead>
            <tr valign="top">
              <td>Model</td>
              <td>Developer</td>
              <td>Year</td>
              <td>Theoretical basis</td>
              <td>Central constructs</td>
              <td>Points of critique</td>
              <td>Extended models</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>TAM<sup>a</sup></td>
              <td>Davis [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]</td>
              <td>1985</td>
              <td>Cognitive psychology [<xref ref-type="bibr" rid="ref13">13</xref>]</td>
              <td>Describes elements to predict the degree to which a person plans to perform specific future behavior. It suggests that perceived usefulness, perceived ease of use, and attitude (ie, intention to use) can explain user motivation [<xref ref-type="bibr" rid="ref12">12</xref>]. It is a way to predict the intended use of a technology.</td>
              <td>Mainly conceptualized for the acceptance of individuals and is not useful for explaining acceptance of electronic health (eHealth) technologies by organizations [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref14">14</xref>].</td>
              <td>TAM2 (by Venkatesh and Davis) and TAM3 (by Venkatesh and Bala) [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]</td>
            </tr>
            <tr valign="top">
              <td>DOI<sup>b</sup></td>
              <td>Rogers [<xref ref-type="bibr" rid="ref9">9</xref>]</td>
              <td>1995</td>
              <td>Diffusion research [<xref ref-type="bibr" rid="ref18">18</xref>]</td>
              <td>Explains the characteristics of innovation. Observability, trialability, complexity, relative advantage, and compatibility are the primary determinants of innovation diffusion, which help explain the different rates of adoption [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Diffusion starts with recognizing the user’s need. It spreads by knowledge acquisition, persuasion, decision (ie, adopt or reject), implementation (ie, routine use, reinvention, and conformation), promotion, and evaluation [<xref ref-type="bibr" rid="ref15">15</xref>].</td>
              <td>There is little focus on the organizational context [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>].</td>
              <td>The unifying theoretical model of Greenhalgh et al [<xref ref-type="bibr" rid="ref16">16</xref>] and the Consolidated Framework for Implementation Research (CFIR) of Damschroder et al [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]</td>
            </tr>
            <tr valign="top">
              <td>UTAUT<sup>c</sup></td>
              <td>Venkatesh et al [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]</td>
              <td>2003</td>
              <td>Cognitive psychology [<xref ref-type="bibr" rid="ref13">13</xref>]</td>
              <td>Builds on TAM and focuses on perceptions and assumptions of people, resulting in the intention to use technology. States that constructs like performance expectancy, effort expectancy, social influence, and facilitating conditions influence intention and ultimately behavior [<xref ref-type="bibr" rid="ref19">19</xref>]. These four constructs are moderated by gender, age, experience, and voluntariness of use [<xref ref-type="bibr" rid="ref19">19</xref>].</td>
              <td>Does not deal with hindrances to actual use [<xref ref-type="bibr" rid="ref13">13</xref>]. Excludes users’ cognitive, affective, and physical ability to use technology [<xref ref-type="bibr" rid="ref20">20</xref>] and ignores technological factors that might influence the decision to use an application [<xref ref-type="bibr" rid="ref20">20</xref>].</td>
              <td>UTAUT2 by Venkatesh et al developed in 2012 [<xref ref-type="bibr" rid="ref9">9</xref>]</td>
            </tr>
            <tr valign="top">
              <td>NASSS<sup>d</sup> framework</td>
              <td>Greenhalgh et al [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]</td>
              <td>2017</td>
              <td>Complexity theory [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]</td>
              <td>Points to aspects explaining the complexity of technological innovations in health care, which according to all the described models influence the adoption. Includes the value proposition (ie, supply-side and demand-side values) as an important factor, in contrast to many implementation theories that do not [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</td>
              <td>Not found yet</td>
              <td>Not found yet</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>TAM: Technology Acceptance Model.</p>
          </fn>
          <fn id="table1fn2">
            <p><sup>b</sup>DOI: diffusion of innovations.</p>
          </fn>
          <fn id="table1fn3">
            <p><sup>c</sup>UTAUT: Unified Theory of Acceptance and Use of Technology.</p>
          </fn>
          <fn id="table1fn4">
            <p><sup>d</sup>NASSS: nonadoption, abandonment, scale-up, spread, and sustainability.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>All four theoretical models include two key concepts—acceptance and adoption—which are either ill-defined or used interchangeably. The concept of acceptance focuses on if, how, and when intended users would use a technology [<xref ref-type="bibr" rid="ref23">23</xref>], and adoption is the actual use of an eHealth technology. Different stages in an adoption process can result in the actual use of an eHealth technology [<xref ref-type="bibr" rid="ref16">16</xref>]. During an adoption process, users of eHealth technology develop feelings about the technology, gain experience, find meaning or do not find meaning in its use, and evaluate the functions of the technology [<xref ref-type="bibr" rid="ref16">16</xref>]. Thus, there is a difference between intended use (ie, acceptance) and actual use (ie, adoption) [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
      <p>The complexity of the adoption process of eHealth technologies is underexposed in all four theoretical models. The literature reports that adoption is a highly complex process and that results cannot be <italic>made</italic> or even predicted [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Greenhalgh et al highlight specific prerequisites for each of the three adoption process stages for innovations [<xref ref-type="bibr" rid="ref16">16</xref>]: (1) in the preadoption stage, intended adopters should know about the innovation: in this case, the patient portal, (2) in the early use stage, intended adopters should be supported in using the innovation and learn how to fit or blend it into their daily routines, (3) in the adoption stage, established users arise if they gain an understanding of the consequences of using of the innovation and if they have the opportunity to refine and improve it: in this case, a patient portal [<xref ref-type="bibr" rid="ref16">16</xref>]. The theoretical models provide no clarity on the pragmatics of efforts in the adoption process. For instance, they do not show how hospitals can encourage patients and HCPs to adopt a patient portal. Therefore, we studied the introduction of patient portals in 12 Dutch hospitals, using a multi-actor perspective to gain a broad understanding of the experiences and views on adoption. Our empirical study focuses on the pragmatics of stimulating the adoption of a patient portal. This paper answers the following research question: How can hospitals encourage patients and HCPs to adopt a patient portal?</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Design and Setting</title>
        <p>In this qualitative study, we asked participants from various backgrounds how they encouraged users to adopt a patient portal and what they had learned from their efforts, in order to understand what stimulated or hindered the adoption process. We conducted 22 multi-actor, semistructured group interviews and held four structured focus groups to check, enlarge, and enrich our findings [<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. <xref ref-type="table" rid="table2">Table 2</xref> lists the different forms of data collection.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Data collection.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="420"/>
            <col width="280"/>
            <col width="270"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Type of data collection and participants</td>
                <td>Number of participants (N=122), n (%)</td>
                <td>Data collection moments (N=26), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Individual and group interview</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Patients</td>
                <td>22 (18.0)</td>
                <td>22 (85)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Health care professionals</td>
                <td>16 (13.1)</td>
                <td>22 (85)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Organizational staff</td>
                <td>31 (25.4)</td>
                <td>22 (85)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Focus group</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Project leaders and staff 1</td>
                <td>14 (11.5)</td>
                <td>2 (8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Project leaders and staff 2</td>
                <td>28 (23.0)</td>
                <td>2 (8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Patient portal suppliers</td>
                <td>5 (4.1)</td>
                <td>1 (4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Macro stakeholders</td>
                <td>6 (4.9)</td>
                <td>1 (4)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>All interviews, both group and individual, and focus group sessions took place in a hospital or online. All the hospitals included in this study are participating in a national program—VIPP (Versnellingsprogramma Informatie- Uitwisseling Patiënt en Professional) [<xref ref-type="bibr" rid="ref27">27</xref>]—initiated by the Dutch Hospital Association and the Dutch government. VIPP is the Dutch government’s financial incentive program to support information exchange between patients and professionals through patient portals. The aim of the VIPP program is to give patients online access to their medical data, either through a patient portal or a PHR [<xref ref-type="bibr" rid="ref27">27</xref>]. Information technology (IT) suppliers with a commercial interest deliver patient portals and PHRs. Given that Dutch hospitals are free to choose any supplier for their patient portals or PHRs, the hospitals in this study use different patient portals. The portals might differ in their available functionalities, but they all offer patients online access to their personal health information [<xref ref-type="bibr" rid="ref6">6</xref>]. Additionally, hospitals had different aims for their patient portals; only the VIPP program aims were similar for all Dutch hospitals. Hospitals receive financial support based on their achievement of specific national VIPP aims; for example, “In the past 30 days, 25% of all patients (based on DRG [diagnosis-related group] contacts) logged in to the patient portal or the link to a PHR” [<xref ref-type="bibr" rid="ref28">28</xref>]. How hospitals achieve these aims is left up to the hospital.</p>
      </sec>
      <sec>
        <title>Recruitment and Participants</title>
        <p>There are three categories of Dutch hospital: academic, teaching, and general. Academic hospitals were excluded from our study because at the time they were not participating in the VIPP program. We first determined inclusion criteria for general and teaching hospitals, aiming for a diverse study group. Based on user statistics of patient portals (low and high), geographical differences (rural areas and cities), variation in patient portal suppliers, and usage of the patient portal (more or less than one year), the researchers (PH, AMWJ, and BP) made a selection of targeted hospitals.</p>
        <p>In total, 15 of 64 Dutch hospitals (23%) were approached, of which 12 (80%: 10 teaching and 2 general) agreed to participate. Reasons for not participating included “already participating in another study” (n=1) and “too busy with implementation and fear of not meeting VIPP deadlines,” which would mean losing financial support (n=2).</p>
        <p>At each hospital or via the Zoom online platform [<xref ref-type="bibr" rid="ref29">29</xref>], the researchers arranged individual and group interviews in close collaboration with the person running the implementation of the patient portal at that particular hospital. Most often, this person was the project leader who selected participants according to a predefined list of three roles:</p>
        <list list-type="order">
          <list-item>
            <p>Patients: patients and client council members (n=22).</p>
          </list-item>
          <list-item>
            <p>HCPs: physicians, Chief Medical Information Officers (CMIOs), nurses, Chief Nursing Information Officers (CNIOs), pharmacists, and outpatient clinic staff (n=16).</p>
          </list-item>
          <list-item>
            <p>Organizational staff: project leaders, project staff, communication advisors, legal policy makers, and managers (n=31).</p>
          </list-item>
        </list>
        <p>In total, 69 participants were included (see <xref ref-type="table" rid="table2">Table 2</xref>) if they were older than 18 years and had experience with developing and/or using a patient portal. The researchers emailed invitations to participants of the individual and group interviews; groups ranged from 2 to 6 participants. In 10 of the participating hospitals, we organized one or two group interviews; in the remaining two hospitals we conducted one individual interview for logistical reasons.</p>
        <p>The aim of the focus groups was to check, enlarge, and enrich our results. Two of the four focus groups were held with project leaders and project staff of hospitals. They joined one of two self-selected focus groups organized during an educational meeting of the VIPP program (n=14 and n=28, respectively). For the other two, we used targeted sampling, selecting experts from patient portal suppliers (n=5) for the third group. The fourth group included macro stakeholders: Ministry of Health, NICTIZ (Nationaal ICT Instituut in de Zorg), the center of expertise for eHealth, health insurance companies, and scientific experts (n=6). All focus group members were invited to take part by email.</p>
      </sec>
      <sec>
        <title>Data Collection and Analysis</title>
        <p>Qualitative data were collected on-site in the hospital (n=59) or online via the Zoom platform [<xref ref-type="bibr" rid="ref29">29</xref>] (n=10) in the fall of 2018. The Zoom platform enabled the inclusion of hard-to-reach, geographically dispersed participants [<xref ref-type="bibr" rid="ref30">30</xref>]. Group interviews lasted an average of 72 minutes (range 53-88) and the individual interviews lasted an average of 53 minutes (range 44-65). One researcher (PH) conducted all the interviews, following a predefined topic list (see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) [<xref ref-type="bibr" rid="ref31">31</xref>] that was based on a search of the literature and discussed among the research team.</p>
        <p>The four focus groups lasted an average of 82 minutes (range 71-88) and were steered by a Microsoft PowerPoint presentation explaining the findings of our study. No revisions were made in the presentation between focus group sessions, ensuring that varying opinions were heard before conclusions were drawn [<xref ref-type="bibr" rid="ref32">32</xref>]. Each focus group was run by two researchers (PH and BP or PH and AMWJ) complementing each other: one moderating and the other taking notes.</p>
        <p>During both group interviews and focus group sessions we encouraged the exchange of heterogeneous views that provided insights into similarities and differences in the opinions and experiences of the various stakeholders [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. We also invited the participants to challenge each other’s views [<xref ref-type="bibr" rid="ref33">33</xref>], to explore the implications of their thinking, and to articulate their sometimes-implicit assumptions about the adoption process. This method generated new insights through group interactions.</p>
        <p>We audio-recorded the on-site interviews and focus groups and video-recorded the online sessions. All interviews were transcribed verbatim. Analysis, comprising six phases [<xref ref-type="bibr" rid="ref34">34</xref>], was not linear but a recursive process. First, each individual researcher gave the transcripts a close reading. Second, one researcher (PH) developed codes for the interesting parts of the data. Next, three researchers (PH, AMWJ, and BP) independently developed themes, reaching consensus on a list of relevant themes (eg, communication channel, ambassadors, and patient participation [<xref ref-type="bibr" rid="ref35">35</xref>]) through discussion. Fourth, one researcher (PH) read the transcripts again. Fifth, using the list of themes, one researcher (PH) performed thematic coding, which two other researchers (AMWJ and BP) checked. In the final phase we (PH, AMWJ, and BP) started writing the results [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
      </sec>
      <sec>
        <title>Ethical Approval</title>
        <p>The Medical Ethics Review Committee of Erasmus Medical Center (Erasmus MC) approved our research proposal (MET-2018-1531) and checked if we were General Data Protection Regulation (GDPR) compliant. All participants were asked to sign an informed consent form.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>Our study aims to provide insights into the adoption process of a patient portal by patients and HCPs. The efforts of hospitals to stimulate the use of patient portals can be categorized under three themes: (1) informing patients and professionals about the patient portal, (2) embedding the patient portal in the daily routine of HCPs, and (3) adjusting the portal to patients’ needs in the initial and continuous development process. Below we present our empirical findings for each of these themes.</p>
      </sec>
      <sec>
        <title>Informing Patients and Health Care Professionals About the Patient Portal</title>
        <sec>
          <title>Overview</title>
          <p>Participants agreed that communication about the patient portal is very important for the adoption of patient portals. The hospitals require the involvement of communication experts to inform patients and HCPs. We identified four objectives to support patient portal adoption using the informing of patients and HCPs as the basis. Here we explain them one by one. Participants mentioned using 23 communication channels to reach their audiences (see <xref ref-type="table" rid="table3">Table 3</xref>).</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Channels (N=23) used to achieve four communication objectives to inform patients and health care professionals.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="400"/>
              <col width="130"/>
              <col width="130"/>
              <col width="170"/>
              <col width="170"/>
              <thead>
                <tr valign="top">
                  <td>Channel</td>
                  <td>Knowing about the portal</td>
                  <td>Knowing how the portal works</td>
                  <td>Knowing that action is required on the portal</td>
                  <td>Knowing where to find help with the portal</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Pocket tickets</td>
                  <td>x<sup>a</sup></td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Promotion leaflets</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Press releases</td>
                  <td>x</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Posters</td>
                  <td>x</td>
                  <td>
                    <break/>
                  </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Banners</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Screen in waiting room</td>
                  <td>x</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Social media</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Video on website</td>
                  <td>x</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Explanatory leaflets</td>
                  <td>x</td>
                  <td>x</td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Students or volunteers in central hall for a week</td>
                  <td>x</td>
                  <td>x</td>
                  <td> </td>
                  <td>x</td>
                </tr>
                <tr valign="top">
                  <td>Physical point with employees and volunteers</td>
                  <td>x</td>
                  <td>x</td>
                  <td> </td>
                  <td>x</td>
                </tr>
                <tr valign="top">
                  <td>Health care professionals</td>
                  <td>x</td>
                  <td>x</td>
                  <td>x</td>
                  <td>x</td>
                </tr>
                <tr valign="top">
                  <td>Letter with request (before or after appointment)</td>
                  <td> </td>
                  <td> </td>
                  <td>x</td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Text message with request</td>
                  <td> </td>
                  <td> </td>
                  <td>x</td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Mail with request</td>
                  <td> </td>
                  <td> </td>
                  <td>x</td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Staffed desk</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                  <td>xxx</td>
                </tr>
                <tr valign="top">
                  <td>Informative meetings</td>
                  <td>xx</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Interactive meetings</td>
                  <td>xxx</td>
                  <td>xxx</td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Internal website</td>
                  <td>xx</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Peer to peer</td>
                  <td>xx</td>
                  <td>xx</td>
                  <td>xx</td>
                  <td>xx</td>
                </tr>
                <tr valign="top">
                  <td>Training</td>
                  <td>xx</td>
                  <td>xx</td>
                  <td>xx</td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Newsletter</td>
                  <td>xx</td>
                  <td> </td>
                  <td> </td>
                  <td> </td>
                </tr>
                <tr valign="top">
                  <td>Goodie bag with explanation</td>
                  <td>xx</td>
                  <td>xx</td>
                  <td> </td>
                  <td> </td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>Key: x = patients; xx = professionals; and xxx = patients and professionals.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Objective 1: Knowing About the Portal</title>
          <p>First, participants argued that it is obviously necessary to make sure that patients and HCPs know about the patient portal; otherwise, they cannot use it. Meeting this objective means that patients and HCPs will have a general idea of what the portal is and what it looks like. The hospitals used various mass-focused channels most frequently to communicate the existence of the portal to patients and HCPs. These channels include leaflets and posters, banners hung in the corridors, messages on social media, and placing volunteers in the central hall of the hospital to point patients to the portal. Using multiple channels to reach patients is considered important because patients have different preferences, but it is probably a bit inefficient, as these quotes illustrate:</p>
          <disp-quote>
            <p>I am not inclined to take leaflets from the hospital. If it’s really important, I think I will be reminded.</p>
            <attrib>Participant #0.4, client council member</attrib>
          </disp-quote>
          <disp-quote>
            <p>All those freebies [goodie bags], I don’t like them. They won’t get me to look at the portal.</p>
            <attrib>Participant #14.2, patient, informal caregiver, and former client council member</attrib>
          </disp-quote>
          <disp-quote>
            <p>Still, it works for others.</p>
            <attrib>Participant #11.4, client council member</attrib>
          </disp-quote>
          <p>Looking at the channels used to reach HCPs, we see hospitals organizing informative presentations for medical and nursing staff and department meetings. Participants felt that informing only the team leaders and managers is not enough; it is important to directly inform the HCPs. According to participants, effective channels that reach broad groups of professionals include department meetings, the hospital intranet, and the staff newsletter. Reaching out by email is considered inefficient because HCPs receive a lot of email and particular messages can be easily missed or skipped.</p>
        </sec>
        <sec>
          <title>Objective 2: Knowing How the Portal Works</title>
          <p>Second, participants argued that patients and professionals need to know how the patient portal works. Hospitals can meet this objective by (1) using video screens in waiting rooms, (2) putting explanatory videos on the hospital website, and (3) placing volunteers in the central hall of the hospital to teach patients how the portal works.</p>
          <p>Hospitals asked professionals who are already successful portal users to explain how the portal works to their peers (ie, peer-to-peer information). One hospital gave their professionals a goodie bag with explanatory flyers during portal training, but only a few hospitals organized training sessions on new functionalities for HCPs. However, the participants said that HCPs need to know how the portal actually works as patients sometimes turn to them for help with portal questions:</p>
          <disp-quote>
            <p>So often I hear that people can’t log in to the patient portal. I think that as staff we should be looking into the portal far more. How does it actually work for the patient in practice?</p>
            <attrib>Participant #1.2, staff member</attrib>
          </disp-quote>
          <p>If the HCP has to tell the patient that they do not know how to help, this can be a disappointment. One participant reflected the following:</p>
          <disp-quote>
            <p>Lots of patients say, “I'm logged in but then I don't know [what to do].” Many colleagues say, “I don't know either.” If you can’t help the patient, they’ll drop out immediately.</p>
            <attrib>Participant #5.5, senior doctor’s assistant</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Objective 3: Knowing That Action Is Required on the Portal</title>
          <p>A third objective is to entice patients and HCPs to visit the portal. Hospitals did this by sending specific calls to action, including personal letters, text messages, or emails asking the recipient to read through an online brochure on their treatment before their hospital appointment or to fill in a questionnaire:</p>
          <disp-quote>
            <p>Your appointment letter also asks you to complete the pre-operative screening questionnaire at home.</p>
            <attrib>Participant #9.1, communication advisor</attrib>
          </disp-quote>
          <p>Hospitals encouraged HCPs to use the patient portal by asking them to respond to e-consults (ie, messages sent by the patient) and by showing them functions that will save their time or make their work more efficient. Time-saving functions like preoperative screening questionnaires on the patient portal are easy to embed in the daily routine of professionals. One participant explained the following:</p>
          <disp-quote>
            <p>We built the pre-operative screening questionnaire in such a way that [the information the patient provides] gets entered directly into the anesthesiologist's outpatient file. [This means] that the moment the anesthesiologist starts the consultation with the patient, the data are already in the system. The outpatient clinic started using the questionnaire right from the go-live.</p>
            <attrib>Participant #12.1, project leader</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Objective 4: Knowing Where to Find Help With the Portal</title>
          <p>The fourth communication objective is to ensure that patients and HCPs know where to look for help when they have a problem using the portal. Hospitals organized a help desk, publishing its phone number and email address in leaflets, letters, on the hospital website, and on the portal itself. Some hospitals organized a service point clearly visible in the central hall of the hospital, where patients receive face-to-face service. Outpatient clinic staff can tell patients about this service point. HCPs can ask their colleagues for help (ie, peers).</p>
          <p>Reviewing these hospital communication strategies, three findings are worth a mention:</p>
          <list list-type="order">
            <list-item>
              <p>The texts used to inform patients and HCPs have a promotional tone. Hospitals choose to stress the benefits and hardly mention the potential disadvantages or risks of portal use.</p>
            </list-item>
            <list-item>
              <p>Mass communication is preferred because it is less labor intensive. However, it is also less personal and less in line with the needs of an individual. Personal communications, such as letters, text messages, and emails, have the advantage in that they probably make patients and health care professionals feel personally addressed.</p>
            </list-item>
            <list-item>
              <p>Hospitals struggle with the timing of starting their communication efforts, for example, having a silent “go-live” or starting a campaign directly after launching the portal.</p>
            </list-item>
          </list>
          <p>Our participants explained that most hospitals do not inform patients about the go-live, because this gives them the opportunity to solve start-up problems and technical issues signaled by the first users. After some two to three months they will use a cross-media approach to communicate on the portal. Our participants expressed concern that if a hospital initiated a communication campaign straight after launching the portal, the hospital could be making promises that they cannot keep.</p>
        </sec>
      </sec>
      <sec>
        <title>Embedding the Patient Portal in Daily Routines</title>
        <sec>
          <title>Overview</title>
          <p>In the previous section we showed how communication strategies support patient portal adoption processes. HCPs worry that using the portal is time-consuming and will disturb their daily routine. They regard explaining how the portal works and communicating with patients on the portal as extra tasks and expect that helping non-computer-literate patients (eg, the elderly and people with low literacy) will be especially time-consuming. One participant explained the following:</p>
          <disp-quote>
            <p>If a patient says, “I don’t use the computer,” I won’t ask if they have a son or daughter who’d like to share their access. I don’t start with that, it costs too much time, really.</p>
            <attrib>Participant #5.5, senior doctor’s assistant</attrib>
          </disp-quote>
          <p>Our data show three ways to support embedding the patient portal in the daily routine of HCPs and management: (1) hospital policy, (2) management by monitoring the numbers, and (3) a structured implementation strategy that includes all employees in the department, termed a specialism-focused approach. According to our participants, all three ways require changing work processes and routines.</p>
        </sec>
        <sec>
          <title>1: Hospital Policy</title>
          <p>The first way to embed patient portals is by developing hospital policy on digitalization. Our participants revealed that some hospitals lack hospital-wide agreements, resulting in a lack of coherence for the patient. One such hospital-wide agreement could set the maximum time that HCPs have to respond to an e-consult. According to our participants, the CMIO and the CNIO can play an important role in setting hospital-wide agreements and explaining new work routines to their colleagues (ie, peer influence). Our participants also said that some hospitals set no obligation or targets to use the portal:</p>
          <disp-quote>
            <p>How can we make sure the patient portal lands properly in the outpatient clinic? Good question... Well, it may have landed, but there is still no obligation [to use it] and that’s the real problem.</p>
            <attrib>Participant #1.1, communication advisor</attrib>
          </disp-quote>
          <p>For example, it is not clear within which time frame HCPs need to respond to patients’ e-consults or how many patients per specialism should be using the portal. Responses to patients should be prompt, and the professionals need time to incorporate their responses into their daily work processes on the portal. One participant explained the following:</p>
          <disp-quote>
            <p>If you have to explain something to the patient on the portal or send them an email within four hours, then we need to think about how to get that complex planning process in the system. The professionals need time to think about it too. So that's development; and you need even more time to implement.</p>
            <attrib>Participant #13.2, CNIO</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>2: Management by Monitoring the Numbers</title>
          <p>The second way to embed patient portals is by ensuring that management monitors information on portal use or response time. Most hospitals lack management control of portal use. Some hospitals, however, monitor the numbers of new patient accounts and users on a dashboard or monitoring system. In one hospital, outpatient clinic employees must ask all patients presenting themselves at the desk if they are interested in opening a patient portal account. Hospital management uses this monitoring information to talk with staff who do not seem to be encouraging enough patients to sign up for the portal. One participant revealed the following:</p>
          <disp-quote>
            <p>Staff must register whether or not they have asked if a patient is interested in having a portal account. Now we can run reports on the employee level... We do that sometimes and then we can see that, say, Marie scores 100% on “not interested.” Of course, ... then you’d have to start the conversation.</p>
            <attrib>Participant #5.4, care and operations manager</attrib>
          </disp-quote>
          <p>Our participants said that fear is possibly a reason why HCPs do not motivate patients to sign up for the portal. Professionals need to overcome their own unfamiliarity and prejudices by experiencing the benefits of the patient portal. One participant declared the following:</p>
          <disp-quote>
            <p>Of course, we do it for the patient, but let's see where it helps the physician. Then you’ll get them to at least use the patient portal.</p>
            <attrib>Participant #8.7, internist</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>3: Specialism-Focused Approach</title>
          <p>A third way to embed portals in daily routines is to apply a specialism-focused approach—a structured implementation strategy—that includes all the staff in the department. This involves a multidisciplinary project team (eg, communication advisor and project leader), management, and HCPs temporarily collaborating on changing work processes to benefit the incorporation of the patient portal into daily routines. Not trying to convince just one physician, but the whole department (eg, the outpatient clinic team), makes it easier to embed the patient portal. Working closely with project staff gives the HCPs support that is based on their needs or wishes. This approach requires giving HCPs the time to discuss their problems, share their experiences, and experiment. One participant explained the following:</p>
          <disp-quote>
            <p>Using this approach, we’ve really looked in depth at the points where the portal can be embedded better in their work process. For example, we’ve supported the specialism of rheumatology. They have very clear ideas about using the portal. Now we’ll work actively with the health care professionals in the coming period to increase the use of the patient portal within their specialism.</p>
            <attrib>Participant #11.2, communication advisor</attrib>
          </disp-quote>
          <p>According to our participants, using this approach supports giving professionals an understanding of how the portal works and how they can use it in their daily routines. However, they said that it is labor intensive for everyone involved, which slows down the adoption process hospital-wide.</p>
          <p>Another implementation strategy is for hospitals to start off the portal adoption processes with keen, intrinsically motivated HCPs. Hospitals put effort into these professionals. They are seen as ambassadors, as <italic>game changers</italic>, who will convince other HCPs by setting a good example. One participant said the following:</p>
          <disp-quote>
            <p>I believe that starting out with the enthusiastic specialists is the most successful strategy and that’s why we’re starting with people who want it. We’re not setting out with the difficult ones who don’t want it.</p>
            <attrib>Participant #11.3, CMIO</attrib>
          </disp-quote>
        </sec>
      </sec>
      <sec>
        <title>Adjusting the Portal to Meet Patients’ Needs</title>
        <sec>
          <title>Overview</title>
          <p>Our participants said that in the continuous development process, adjusting the portal to meet the patients’ needs is important. For example, enhancing user-friendliness ensures repeated use of a portal. As well, asking patients for feedback on the portal can reveal points of improvement that the project staff might not spot, as our participants explained:</p>
          <disp-quote>
            <p>An example: a patient tests the portal, first on a dummy and later on their own file. Someone remarks: “It’s in chronological order, but the most recent is at the bottom. Why don’t you put the most recent at the top of the page?”</p>
            <attrib>Participant #4.2, project leader</attrib>
          </disp-quote>
          <disp-quote>
            <p>It’s as simple as that. You don’t notice that when you are so involved.</p>
            <attrib>Participant #4.1, advisor of functional management</attrib>
          </disp-quote>
          <p>According to our participants, another reason they find it important to adjust to patients’ needs is because the perspectives of the patient and the communication advisor may differ:</p>
          <disp-quote>
            <p>I’m against all those abbreviations... Why not explain what they are? I guarantee you that half the patients won’t know what the abbreviation means. Add an abbreviation list.</p>
            <attrib>Participant #10.6, patient and client council member</attrib>
          </disp-quote>
          <disp-quote>
            <p>It’s my choice. I can write the term in full, I can explain it the abbreviation. But when I write it out completely, it becomes a very long sentence.</p>
            <attrib>Participant #10.2, communication advisor</attrib>
          </disp-quote>
          <p>Our participants mentioned two methods hospitals use in the effort to optimize portal user-friendliness: (1) patient feedback and (2) focus on optimizations for patients with special needs (eg, low literacy, visually impaired, and low digital skills).</p>
        </sec>
        <sec>
          <title>1: Patient Feedback</title>
          <p>The first way to adjust to patients’ needs in the continuous development of patient portals is to set up a panel of patients to act as a sounding board or to survey patients on their experiences and wishes. One participant reported the following:</p>
          <disp-quote>
            <p>We have a panel of 150 people. We sent these people a questionnaire on the patient portal and how they would like to use it.</p>
            <attrib>Participant #3.2, client council member</attrib>
          </disp-quote>
          <p>Another way is to organize sessions with patients to test portal functionalities (eg, access to data, an e-consult, and filling in questionnaires). To illustrate, one hospital organized a test session for feedback and observations:</p>
          <disp-quote>
            <p>We invited a few patients from our patient panel. We gave them a test version of the portal and asked them to do a few assignments and fill in a questionnaire. For example: look at the patient portal and see if you get it. Give as much feedback as possible about the things that could be improved... There was one-on-one guidance. We had a large number of employees involved, so that we could sit next to the patients and get as much feedback as possible. So, we could also see how things went.</p>
            <attrib>Participant #7.1, project employee</attrib>
          </disp-quote>
          <p>Hospitals also asked for feedback and reused questions, comments, and complaints patients express to the helpdesk. One participant said the following:</p>
          <disp-quote>
            <p>We now actively request feedback from patients. The helpdesk also receives feedback and phone calls and we can use the input obtained.</p>
            <attrib>Participant #1.1, communication advisor</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>2: Focus on Optimizations for Patients With Special Needs</title>
          <p>A second way to adjust to patients’ needs is by optimizing the portal for people with special needs. For example, language experts check the language used on the portal and written information on how to use it, removing jargon and abbreviations and simplifying texts for patients with low literacy. They make more use of visuals (eg, icons, pictograms, and infographics):</p>
          <disp-quote>
            <p>You can summarize in pictograms, which makes it much easier for patients with low literacy. Visuals work better and faster.</p>
            <attrib>Participant #9.2, patient</attrib>
          </disp-quote>
          <p>Another example of optimizing portal use for people with special needs is when hospitals collaborate with organizations offering general computer courses, such as the municipality, community centers, and libraries, for patients with few digital skills. Hospitals ask those organizations to blend the patient portal into their course and teach patients to work with it. Also, hospitals may refer patients to this course if they do not have computer skills and need to learn how to work with the Dutch national identity authentication method (DigiD). Participants report that the DigiD is not easy to use and its log-in process requires many steps:</p>
          <disp-quote>
            <p>I find the accessibility of the patient portal a real problem. Logging in with your DigiD is difficult.</p>
            <attrib>Participant #3.3, functional manager</attrib>
          </disp-quote>
          <disp-quote>
            <p>We look for courses on using the DigiD subsidized by the municipality. They organize courses in the community centers for people having trouble with DigiD and then these people can practice logging in on the patient portals.</p>
            <attrib>Participant #11.2, communication advisor</attrib>
          </disp-quote>
          <p>Despite the importance of adjusting to patients’ needs in continuous development, hospitals sometimes hesitate to include patients, because they may not be able to act on the patients’ feedback. For example, if patients miss functionalities, it can require time and money to add them to the portal and, therefore, this cannot be easily fixed. Participants mentioned the importance of explaining to patients what the hospital does with their feedback and why some feedback points cannot be solved in the near future (eg, technologically impossible or too expensive). Otherwise, patients will feel that the hospital is not taking their feedback seriously. The following quote shows how hospitals struggle to let patients participate in the continuous portal development, even though they find patient input invaluable:</p>
          <disp-quote>
            <p>If we invite the panel group for testing, then we have to show that we have improved the portal based on their feedback... Otherwise they will think “nothing happens with our input.” If we organize patient participation, you can only say “we’re too busy” once.</p>
            <attrib>Participant #4.1, advisor of functional management, and participant #4.2, project leader</attrib>
          </disp-quote>
          <p>One of the challenges of acting on patient feedback stems from the collaboration with the suppliers of patient portals. Suppliers will undertake to improve or develop new functionalities when multiple hospitals make the same request. Surprisingly, however, suppliers (n=5) said that they include no patients in their development process. The suppliers see it as the responsibility of their customers—the hospitals—to give voice to patients’ wishes.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This qualitative study focuses on patient portal adoption processes by patients and HCPs in a Dutch hospital context. Overall, our results show that the adoption of patient portals is more dynamic than presented in theoretical models and the literature. Greenhalgh et al’s linear adoption stages (ie, preadoption, early use, and established users) [<xref ref-type="bibr" rid="ref16">16</xref>] seem useful in studying adoption by individuals, but hospital patients and HCPs are in different adoption stages. Consequently, an organization cannot simply move through sequential stages; it needs ongoing effort to be put into informing, embedding, and adjusting to patients’ needs. Their focus on individuals rather than the organizational context is also a criticism levied at the theoretical models (see <xref ref-type="table" rid="table1">Table 1</xref>) [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>].</p>
        <p>All participating hospitals seem to be experimenting with stimulating adoption of the patient portal. They are trying to create effective communication strategies, looking for the best way to embed the portal in daily routines and adjust to its patients’ needs. As yet, they have not found the best way of encouraging portal use by patients and HCPs. Here we explain the implications of our results.</p>
        <p>Our study shows that hospitals are experimenting with many communication channels (N=23), mostly ones that are already in use. Despite efforts by communication departments, it seems that portal adoption is still quite a challenge. It seems that hospitals do not know which channels are most effective for which target audiences and what the right timing is for their communication campaigns. Looking at their communication strategies, we found that hospitals choose to emphasize the benefits of portal use and hardly mention the potential disadvantages or risks. According to Greenhalgh et al [<xref ref-type="bibr" rid="ref16">16</xref>], intended adopters must know the consequences of adopting a patient portal to become established users. If intended adopters are not informed of the potential disadvantages, then they cannot oversee all the consequences of using the portal, for example, the risks. However, the financial incentives of the VIPP program may explain the positive promotion strategy. If hospitals do not attain a certain adoption percentage (ie, 10% or 25%) they will have to repay their VIPP grant.</p>
        <p>Our results show that hospitals invest in HCP adoption through peer-to-peer influence. However, focusing on the enthusiastic HCPs can mean that the less-motivated HCPs will lag behind. That a patient portal often does not reduce the burden of HCPs (ie, it only means extra work) and that it is not embedded properly in work routines can hinder adoption. The specialism-focused approach offers a way of encouraging patient portal adoption by HCPs. This experiment with portal embedding would be interesting to study in other contexts to see where and how it could lead to better embedding of the patient portal. A possible disadvantage of this approach could be that patients will not understand why specialisms are in different adoption stages (ie, patients can make an online appointment with one specialism but not for another).</p>
        <p>Another principal finding is that hospitals are struggling to adjust the portal to meet patients’ needs in their continuous development process, although all seem to find this important. According to Greenhalgh et al [<xref ref-type="bibr" rid="ref16">16</xref>], it is vital that intended users get the opportunity to refine the portal so that they will not drop out in the early adoption stage. Hospitals are using various ways to adjust to the patients’ needs in ongoing portal development, without knowing which one is most effective in which phase and for what purpose. It would be interesting to do more research on how patients can participate in portal development, including efforts to stimulate adoption.</p>
        <p>Nonusers of patient portals could be studied further. Previous studies show that nonusers have various reasons for not adopting the portal [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>], including a preference to speak directly to their HCP, the level of their communication skills [<xref ref-type="bibr" rid="ref36">36</xref>], and their concern for privacy and information security [<xref ref-type="bibr" rid="ref36">36</xref>]. Such studies would show that hospitals are taking nonusers’ concerns seriously and, at the same time, could produce insights valuable to exploring whether and how the patient portal could be made useful to them.</p>
        <p>A remarkable finding is that portal suppliers do not include patients in their development process. The suppliers see it as their clients’ responsibility to give voice to patients’ wishes, but the focus group discussion did make them rethink this. This means that hospitals must explain to the supplier how they should make the portal more user-friendly for patients. Because of the variation in hospital context and portal suppliers, this could explain the disappointing adoption by patients.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>Our study has four limitations. The first is that the adoption processes in the hospitals we studied might be somewhat unusual due to the financial incentives of the national VIPP program. Conducting similar research in other countries would, therefore, be interesting and could also teach us more about the contextual, including cultural, factors that influence hospitals’ efforts to stimulate adoption.</p>
        <p>The second limitation is the way we recruited hospital participants. Using our own research networks may have biased our sample. However, our recruiting process resulted in a good variation in the mix of included hospitals.</p>
        <p>The third limitation is that we only included teaching and general hospitals, given that academic hospitals follow another implementation program. Also, during the study period they were not participating in the VIPP program and, therefore, could not be compared. However, the inclusion criteria context of the studied hospitals varied greatly to include different kinds of hospitals and patients.</p>
        <p>Last, this descriptive study shows the efforts that some Dutch hospitals have made to stimulate adoption of a patient portal. We did not study whether the undertaken efforts led to an actual increase of the adoption of patient portals. A further study on the effectiveness of these efforts is recommended.</p>
      </sec>
      <sec>
        <title>Comparison With Prior Work</title>
        <p>In recent years, many theoretical models on the adoption of information technology have been developed [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. These models show which variables are important for the adoption of a technology; for example, <italic>perceived ease of use</italic>, defined in the Technology Acceptance Model (TAM) as “the degree to which the person believes that using the particular system would be free of effort” [<xref ref-type="bibr" rid="ref12">12</xref>]. However, these models are not explanatory and do not provide the know-how to stimulate patient portal adoption [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Consequently, we suggest future research should not focus on models, including new ones, but should deal with actionable knowledge for practice [<xref ref-type="bibr" rid="ref38">38</xref>]. Action research can be used to study the adoption process and the embedding of patient portals in daily practice [<xref ref-type="bibr" rid="ref39">39</xref>].</p>
        <p>Communication experts support the hospitals’ choice to use a cross-media promotion to inform patients and HCPs about the patient portal [<xref ref-type="bibr" rid="ref40">40</xref>]. Explaining the benefits of using a patient portal is especially important for promotional messages [<xref ref-type="bibr" rid="ref41">41</xref>]. However, open dialogue among HCPs and project leaders and staff is also vital because it illuminates the professionals’ perspectives on portal development [<xref ref-type="bibr" rid="ref41">41</xref>]. Earlier research shows that ignoring doubts while trying to convince others to use a technology may produce negative energy and a reluctance to use the portal [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Further research is required to find the most effective hospital communication strategies for encouraging patient portal adoption for patients and HCPs.</p>
        <p>Our study showed that embedding a patient portal in the daily routine of HCPs requires changing their work processes. Earlier studies suggest that hospitals need to make extra time available to HCPs so that they can change and learn new work processes [<xref ref-type="bibr" rid="ref41">41</xref>]. Research shows that portal use by patients may increase when HCPs are active on the patient portal and it is embedded in their work processes [<xref ref-type="bibr" rid="ref43">43</xref>]. Research suggests training can benefit the adoption process [<xref ref-type="bibr" rid="ref41">41</xref>], yet only some hospitals organize courses that explain how the portal works. As a result, some HCPs lack familiarity with portal functionalities [<xref ref-type="bibr" rid="ref42">42</xref>].</p>
        <p>The literature reports several ways of using feedback to adjust the portal to patients’ needs in the continuous development of patient portals. These studies could help hospitals struggling with this. It is important to include patients at the beginning of ongoing development of patient portals [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. Examples include co-design, where patients help identify the project based on personal experiences in collaborating with the clinician [<xref ref-type="bibr" rid="ref45">45</xref>], and participatory stakeholder co-design, where patients and clinicians are equal stakeholders in the whole project [<xref ref-type="bibr" rid="ref45">45</xref>]. Vulnerable patient groups, such as disadvantaged older adults, should be given special attention in the process of cocreation and user testing [<xref ref-type="bibr" rid="ref7">7</xref>]. This is an important issue for future research.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Patient portal adoption processes are not just about implementing the technology. They require human interaction in a multitude of ways. Our study reveals three key findings for the adoption process: (1) informing patients and HCPs about the portal, (2) embedding it in the daily routine of HCPs, and (3) adjusting it to patients’ needs in the continuous development of the portal. Our paper provides rich insights into the complexity of the adoption process and gives examples of efforts to stimulate the adoption of patient portals. Our findings help to translate the relatively abstract factors mentioned in the theoretical models to the everyday pragmatics of eHealth projects in hospitals.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Topic list for interviews.</p>
        <media xlink:href="jmir_v22i5e16921_app1.docx" xlink:title="DOCX File , 22 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CMIO</term>
          <def>
            <p>Chief Medical Information Officer</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CNIO</term>
          <def>
            <p>Chief Nursing Information Officer</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DigiD</term>
          <def>
            <p>Dutch national identity authentication method</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">DRG</term>
          <def>
            <p>diagnosis-related group</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">eHealth</term>
          <def>
            <p>electronic health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">Erasmus MC</term>
          <def>
            <p>Erasmus Medical Center</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">HCP</term>
          <def>
            <p>health care professional</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">NASSS</term>
          <def>
            <p>nonadoption, abandonment, scale-up, spread, and sustainability</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">NICTIZ</term>
          <def>
            <p>Nationaal ICT Instituut in de Zorg</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">PHR</term>
          <def>
            <p>personal health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">TAM</term>
          <def>
            <p>Technology Acceptance Model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">VIPP</term>
          <def>
            <p>Versnellingsprogramma Informatie-Uitwisseling Patiënt en Professional</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The study was commissioned by the Dutch Hospital Association. We would like to thank our participants and the members of our scientific group. We are grateful for the helpful comments and insightful suggestions by our colleagues, especially Marcello Aspria and Louis Ter Meer.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <source>eHealth Research, Theory and Development: A Multi-Disciplinary Approach</source>
          <year>2018</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Routledge</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Otte-Trojel</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>de Bont</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rundall</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>van de Klundert</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>What do we know about developing patient portals? A systematic literature review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>04</month>
          <volume>23</volume>
          <issue>e1</issue>
          <fpage>e162</fpage>
          <lpage>e168</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26335985"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv114</pub-id>
          <pub-id pub-id-type="medline">26335985</pub-id>
          <pub-id pub-id-type="pii">ocv114</pub-id>
          <pub-id pub-id-type="pmcid">PMC4954617</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Al-Ramani</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Noteboom</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A systematic analysis of patient portals adoption, acceptance and usage: The trajectory for triple aim?</article-title>
          <source>Proceedings of the 51st Hawaii International Conference on System Sciences</source>
          <year>2018</year>
          <month>01</month>
          <day>03</day>
          <conf-name>51st Hawaii International Conference on System Sciences</conf-name>
          <conf-date>January 2-6, 2018</conf-date>
          <conf-loc>Big Island, HI</conf-loc>
          <fpage>852</fpage>
          <lpage>861</lpage>
          <pub-id pub-id-type="doi">10.24251/hicss.2018.107</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sieck</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hefner</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>McAlearney</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Improving the patient experience through patient portals: Insights from experienced portal users</article-title>
          <source>Patient Exp J</source>
          <year>2018</year>
          <month>11</month>
          <day>06</day>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>47</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.35680/2372-0247.1269</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kruse</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Bolton</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Freriks</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>The effect of patient portals on quality outcomes and its implications to meaningful use: A systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>02</month>
          <day>10</day>
          <volume>17</volume>
          <issue>2</issue>
          <fpage>e44</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2015/2/e44/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.3171</pub-id>
          <pub-id pub-id-type="medline">25669240</pub-id>
          <pub-id pub-id-type="pii">v17i2e44</pub-id>
          <pub-id pub-id-type="pmcid">PMC4342639</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grünloh</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Myreteg</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Cajander</surname>
              <given-names>Å</given-names>
            </name>
            <name name-style="western">
              <surname>Rexhepi</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>"Why do they need to check me?" Patient participation through eHealth and the doctor-patient relationship: Qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>01</month>
          <day>15</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>e11</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/1/e11/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8444</pub-id>
          <pub-id pub-id-type="medline">29335237</pub-id>
          <pub-id pub-id-type="pii">v20i1e11</pub-id>
          <pub-id pub-id-type="pmcid">PMC5789160</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wildenbos</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Peute</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The equity paradox: Older patients' participation in patient portal development</article-title>
          <source>Int J Qual Health Care</source>
          <year>2019</year>
          <month>12</month>
          <day>31</day>
          <volume>31</volume>
          <issue>10</issue>
          <fpage>793</fpage>
          <lpage>797</lpage>
          <pub-id pub-id-type="doi">10.1093/intqhc/mzy245</pub-id>
          <pub-id pub-id-type="medline">30576454</pub-id>
          <pub-id pub-id-type="pii">5253759</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maguire</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Honeyman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Omojomolo</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>Digital Change in Health and Social Care</source>
          <year>2018</year>
          <month>06</month>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>The King’s Fund</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Salahshour Rad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nilashi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mohamed Dahlan</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Information technology adoption: A review of the literature and classification</article-title>
          <source>Univers Access Inf Soc</source>
          <year>2017</year>
          <month>3</month>
          <day>30</day>
          <volume>17</volume>
          <issue>2</issue>
          <fpage>361</fpage>
          <lpage>390</lpage>
          <pub-id pub-id-type="doi">10.1007/s10209-017-0534-z</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Taherdoost</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A review of technology acceptance and adoption models and theories</article-title>
          <source>Procedia Manuf</source>
          <year>2018</year>
          <volume>22</volume>
          <fpage>960</fpage>
          <lpage>967</lpage>
          <pub-id pub-id-type="doi">10.1016/j.promfg.2018.03.137</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ajibade</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Technology Acceptance Model limitations and criticisms: Exploring the practical applications and use in technology-related studies, mixed-method, and qualitative researches</article-title>
          <source>Libr Philos Pract</source>
          <year>2018</year>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://digitalcommons.unl.edu/libphilprac/1941"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marangunić</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Granić</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Technology Acceptance Model: A literature review from 1986 to 2013</article-title>
          <source>Univers Access Inf Soc</source>
          <year>2014</year>
          <month>2</month>
          <day>16</day>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>81</fpage>
          <lpage>95</lpage>
          <pub-id pub-id-type="doi">10.1007/s10209-014-0348-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Beerlage-de Jong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Oinas-Kukkonen</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Persuasive health technology</article-title>
          <source>eHealth Research, Theory and Development: A Multi-Disciplinary Approach</source>
          <year>2018</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Routledge</publisher-name>
          <fpage>228</fpage>
          <lpage>246</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pieterse</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Cruz-Martínez</surname>
              <given-names>RR</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The complexitiy of eHealth implementation: A theoretical and practical perspective</article-title>
          <source>eHealth Research, Theory and Development: A Multi-Disciplinary Approach</source>
          <year>2018</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Routledge</publisher-name>
          <fpage>247</fpage>
          <lpage>270</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Benson</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Digital innovation evaluation: User perceptions of innovation readiness, digital confidence, innovation adoption, user experience and behaviour change</article-title>
          <source>BMJ Health Care Inform</source>
          <year>2019</year>
          <month>04</month>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://informatics.bmj.com/cgi/pmidlookup?view=long&#38;pmid=31039121"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjhci-2019-000018</pub-id>
          <pub-id pub-id-type="medline">31039121</pub-id>
          <pub-id pub-id-type="pii">bmjhci-2019-000018</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Macfarlane</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bate</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kyriakidou</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Diffusion of innovations in service organizations: Systematic review and recommendations</article-title>
          <source>Milbank Q</source>
          <year>2004</year>
          <volume>82</volume>
          <issue>4</issue>
          <fpage>581</fpage>
          <lpage>629</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/15595944"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/j.0887-378X.2004.00325.x</pub-id>
          <pub-id pub-id-type="medline">15595944</pub-id>
          <pub-id pub-id-type="pii">MILQ325</pub-id>
          <pub-id pub-id-type="pmcid">PMC2690184</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Damschroder</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Aron</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Keith</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Kirsh</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Alexander</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Lowery</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Fostering implementation of health services research findings into practice: A consolidated framework for advancing implementation science</article-title>
          <source>Implement Sci</source>
          <year>2009</year>
          <month>08</month>
          <day>07</day>
          <volume>4</volume>
          <fpage>50</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/1748-5908-4-50"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1748-5908-4-50</pub-id>
          <pub-id pub-id-type="medline">19664226</pub-id>
          <pub-id pub-id-type="pii">1748-5908-4-50</pub-id>
          <pub-id pub-id-type="pmcid">PMC2736161</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <source>Diffusion Of Innovations. 4th edition</source>
          <year>2010</year>
          <month>07</month>
          <day>06</day>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>The Free Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Rana</surname>
              <given-names>NP</given-names>
            </name>
            <name name-style="western">
              <surname>Dwivedi</surname>
              <given-names>YK</given-names>
            </name>
          </person-group>
          <article-title>The unified theory of acceptance and use of technology (UTAUT): A literature review</article-title>
          <source>J Enterp Inf Manag</source>
          <year>2015</year>
          <month>04</month>
          <day>13</day>
          <volume>28</volume>
          <issue>3</issue>
          <fpage>443</fpage>
          <lpage>488</lpage>
          <pub-id pub-id-type="doi">10.1108/JEIM-09-2014-0088</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Logue</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Effken</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Modeling factors that influence personal health records adoption</article-title>
          <source>Comput Inform Nurs</source>
          <year>2012</year>
          <month>07</month>
          <volume>30</volume>
          <issue>7</issue>
          <fpage>354</fpage>
          <lpage>362</lpage>
          <pub-id pub-id-type="doi">10.1097/NXN.0b013e3182510717</pub-id>
          <pub-id pub-id-type="medline">22525046</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>A'Court</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hinder</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fahy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Beyond adoption: A new framework for theorizing and evaluating nonadoption, abandonment, and challenges to the scale-up, spread, and sustainability of health and care technologies</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>e367</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/11/e367/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8775</pub-id>
          <pub-id pub-id-type="medline">29092808</pub-id>
          <pub-id pub-id-type="pii">v19i11e367</pub-id>
          <pub-id pub-id-type="pmcid">PMC5688245</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>A'Court</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hinder</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Analysing the role of complexity in explaining the fortunes of technology programmes: Empirical application of the NASSS framework</article-title>
          <source>BMC Med</source>
          <year>2018</year>
          <month>05</month>
          <day>14</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>66</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-018-1050-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12916-018-1050-6</pub-id>
          <pub-id pub-id-type="medline">29754584</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12916-018-1050-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC5950199</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Triberti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gaggioli</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>User engagement</article-title>
          <source>eHealth Research, Theory and Development: A Multi-Disciplinary Approach</source>
          <year>2018</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Routledge</publisher-name>
          <fpage>271</fpage>
          <lpage>289</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Focus group methodology: A review</article-title>
          <source>Int J Soc Res Methodol</source>
          <year>2014</year>
          <month>06</month>
          <day>10</day>
          <volume>1</volume>
          <issue>3</issue>
          <fpage>181</fpage>
          <lpage>203</lpage>
          <pub-id pub-id-type="doi">10.1080/13645579.1998.10846874</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smithson</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Alasuurtari</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Bickman</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Brannen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Focus groups</article-title>
          <source>The Sage Handbook of Social Research Methods</source>
          <year>2008</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
          <fpage>357</fpage>
          <lpage>370</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Frey</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Fontana</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The group interview in social research</article-title>
          <source>Soc Sci J</source>
          <year>2019</year>
          <month>12</month>
          <day>09</day>
          <volume>28</volume>
          <issue>2</issue>
          <fpage>175</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.1016/0362-3319(91)90003-m</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <source>VIPP</source>
          <year>2020</year>
          <access-date>2020-02-11</access-date>
          <comment>Wat is VIPP (What is VIPP) [article in Dutch]<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.vipp-programma.nl/over-vipp/wat-is-vipp">https://www.vipp-programma.nl/over-vipp/wat-is-vipp</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>VIPP</collab>
          </person-group>
          <source>Handboek VIPP Eindtoets (VIPP Handbook Final Test) [document in Dutch]</source>
          <year>2016</year>
          <month>12</month>
          <day>27</day>
          <access-date>2020-04-19</access-date>
          <publisher-loc>The Hague, the Netherlands</publisher-loc>
          <publisher-name>Ministerie van Volksgezondheid Welzijn en Sport (Ministry of Health, Well-Being and Sport)</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rijksoverheid.nl/binaries/rijksoverheid/documenten/rapporten/2016/12/27/handboek-vipp-eindtoets/Handboek+VIPP+eindtoets+ter+publicatie2.pdf">https://www.rijksoverheid.nl/binaries/rijksoverheid/documenten/rapporten/2016/12/27/handboek-vipp-eindtoets/Handboek+VIPP+eindtoets+ter+publicatie2.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <source>Zoom</source>
          <year>2020</year>
          <access-date>2020-02-11</access-date>
          <publisher-name>Zoom Video Communications</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://zoom.us/">https://zoom.us/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>DL</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Gubrium</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Holstein</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Focus group interviewing</article-title>
          <source>Handbook of Interview Research: Context and Method</source>
          <year>2001</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
          <fpage>141</fpage>
          <lpage>159</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gibbs</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Arthur</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Waring</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Coe</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hedges</surname>
              <given-names>LV</given-names>
            </name>
          </person-group>
          <article-title>Focus groups and group interviews</article-title>
          <source>Research Methods and Methodologies in Education</source>
          <year>2012</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
          <fpage>186</fpage>
          <lpage>192</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McLafferty</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Focus group interviews as a data collecting strategy</article-title>
          <source>J Adv Nurs</source>
          <year>2004</year>
          <month>10</month>
          <volume>48</volume>
          <issue>2</issue>
          <fpage>187</fpage>
          <lpage>194</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1365-2648.2004.03186.x</pub-id>
          <pub-id pub-id-type="medline">15369499</pub-id>
          <pub-id pub-id-type="pii">JAN3186</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gaskell</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bauer</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Gaskell</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Individual and group interviewing</article-title>
          <source>Qualitative Researching with Text, Image and Sound: A Practical Handbook</source>
          <year>2000</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
          <fpage>38</fpage>
          <lpage>56</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Using thematic analysis in psychology</article-title>
          <source>Qual Res Psychol</source>
          <year>2006</year>
          <month>01</month>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>101</lpage>
          <pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mortelmans</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>Handboek Kwalitatieve Onderzoeksmethoden (Handbook of Qualitative Research Methods). 4th edition  [book in Dutch]</source>
          <year>2013</year>
          <publisher-loc>Leuven, Belgium</publisher-loc>
          <publisher-name>Acco</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Anthony</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Campos-Castillo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>PS</given-names>
            </name>
          </person-group>
          <article-title>Who isn't using patient portals and why? Evidence and implications from a national sample of US adults</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2018</year>
          <month>12</month>
          <volume>37</volume>
          <issue>12</issue>
          <fpage>1948</fpage>
          <lpage>1954</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2018.05117</pub-id>
          <pub-id pub-id-type="medline">30633673</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Oudshoorn</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Pinch</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Non-users also matter: The construction of users and non-users of the Internet</article-title>
          <source>How Users Matter: The Co-construction of Users and Technology</source>
          <year>2003</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>The MIT Press</publisher-name>
          <fpage>67</fpage>
          <lpage>79</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Argyris</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Actionable knowledge: Design causality in the service of consequential theory</article-title>
          <source>J Appl Behav Sci</source>
          <year>2016</year>
          <month>07</month>
          <day>26</day>
          <volume>32</volume>
          <issue>4</issue>
          <fpage>390</fpage>
          <lpage>406</lpage>
          <pub-id pub-id-type="doi">10.1177/0021886396324004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coghlan</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>Doing Action Research in Your Own Organization. 5th edition</source>
          <year>2019</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leppäniemi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Karjaluoto</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Mobile marketing: From marketing strategy to mobile marketing campaign implementation</article-title>
          <source>Int J Mob Mark</source>
          <year>2008</year>
          <month>06</month>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>50</fpage>
          <lpage>61</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/profile/Heikki_Karjaluoto/publication/252113084_Mobile_Marketing_From_Marketing_Strategy_to_Mobile_Marketing_Campaign_Implementation/links/567148a008ae2b1f87aee230/Mobile-Marketing-From-Marketing-Strategy-to-Mobile-Marketing-Campaign-Implementation.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kujala</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hörhammer</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kaipio</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Heponiemi</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Health professionals' expectations of a national patient portal for self-management</article-title>
          <source>Int J Med Inform</source>
          <year>2018</year>
          <month>09</month>
          <volume>117</volume>
          <fpage>82</fpage>
          <lpage>87</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(18)30348-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2018.06.005</pub-id>
          <pub-id pub-id-type="medline">30032968</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30348-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Myers</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Electronic patient portals: Patient and provider perceptions</article-title>
          <source>Online J Nurs Inform</source>
          <year>2018</year>
          <month>02</month>
          <day>27</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/electronic-patient-portals-patient-and-provider-perceptions"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hoogenbosch</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Postma</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>de Man-van Ginkel</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Tiemessen</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>van Delden</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>van Os-Medendorp</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Use and the users of a patient portal: Cross-sectional study</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>09</month>
          <day>17</day>
          <volume>20</volume>
          <issue>9</issue>
          <fpage>e262</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/9/e262/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9418</pub-id>
          <pub-id pub-id-type="medline">30224334</pub-id>
          <pub-id pub-id-type="pii">v20i9e262</pub-id>
          <pub-id pub-id-type="pmcid">PMC6231740</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>BL</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Terry</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cejic</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Thind</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Implementing and using a patient portal: A qualitative exploration of patient and provider perspectives on engaging patients</article-title>
          <source>J Innov Health Inform</source>
          <year>2016</year>
          <month>07</month>
          <day>04</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>848</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.doi.org/10.14236/jhi.v23i2.848"/>
          </comment>
          <pub-id pub-id-type="doi">10.14236/jhi.v23i2.848</pub-id>
          <pub-id pub-id-type="medline">27869582</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kildea</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Battista</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cabral</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hendren</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Herrera</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hijal</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Joseph</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Design and development of a person-centered patient portal using participatory stakeholder co-design</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>11</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e11371</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/2/e11371/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11371</pub-id>
          <pub-id pub-id-type="medline">30741643</pub-id>
          <pub-id pub-id-type="pii">v21i2e11371</pub-id>
          <pub-id pub-id-type="pmcid">PMC6388099</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
