<?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 article-type="review-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JA</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Aging</journal-id>
      <journal-title>JMIR Aging</journal-title>
      <issn pub-type="epub">2561-7605</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">v6i1e31812</article-id>
      <article-id pub-id-type="pmid">36735321</article-id>
      <article-id pub-id-type="doi">10.2196/31812</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Contextual Factors That Impact the Implementation of Patient Portals With a Focus on Older People in Acute Care Hospitals: Scoping Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Leung</surname>
            <given-names>Tiffany</given-names>
          </name>
        </contrib>
        <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>Petrovskaya</surname>
            <given-names>Olga</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chu</surname>
            <given-names>Yuanchia</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Anonymous</surname>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Khadjesari</surname>
            <given-names>Zarnie</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Behavioural and Implementation Science research group</institution>
            <institution>School of Health Sciences</institution>
            <institution>University of East Anglia</institution>
            <addr-line>Norwich Research Park</addr-line>
            <addr-line>Norwich, NR4 7TJ</addr-line>
            <country>United Kingdom</country>
            <phone>44 01603 597001</phone>
            <email>Z.Khadjesari@uea.ac.uk</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2958-9555</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Houghton</surname>
            <given-names>Julie</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5006-9239</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>Tracey J</given-names>
          </name>
          <degrees>MSci</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4381-5974</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Jopling</surname>
            <given-names>Helena</given-names>
          </name>
          <degrees>MBBS</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6339-2599</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Stevenson</surname>
            <given-names>Fiona</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2139-2309</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Lynch</surname>
            <given-names>Jennifer</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2601-7498</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Behavioural and Implementation Science research group</institution>
        <institution>School of Health Sciences</institution>
        <institution>University of East Anglia</institution>
        <addr-line>Norwich</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Norwich Medical School</institution>
        <institution>University of East Anglia</institution>
        <addr-line>Norwich</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Department of Public Health</institution>
        <institution>West Suffolk NHS Foundation Trust</institution>
        <addr-line>Bury St Edmunds</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Primary Care and Population Health</institution>
        <institution>University College London</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>School of Health and Social Work</institution>
        <institution>University of Hertfordshire</institution>
        <addr-line>Hatfield</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Zarnie Khadjesari <email>Z.Khadjesari@uea.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>3</day>
        <month>2</month>
        <year>2023</year>
      </pub-date>
      <volume>6</volume>
      <elocation-id>e31812</elocation-id>
      <history>
        <date date-type="received">
          <day>6</day>
          <month>7</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>22</day>
          <month>10</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>13</day>
          <month>12</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>4</day>
          <month>12</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Zarnie Khadjesari, Julie Houghton, Tracey J Brown, Helena Jopling, Fiona Stevenson, Jennifer Lynch. Originally published in JMIR Aging (https://aging.jmir.org), 03.02.2023.</copyright-statement>
      <copyright-year>2023</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 JMIR Aging, is properly cited. The complete bibliographic information, a link to the original publication on https://aging.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://aging.jmir.org/2023/1/e31812" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Older people are the highest users of health services but are less likely to use a patient portal than younger people.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This scoping review aimed to identify and synthesize the literature on contextual factors that impact the implementation of patient portals in acute care hospitals and among older people.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A scoping review was conducted according to the PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses Extension for Scoping Reviews) guidelines. The following databases were searched from 2010 to June 2020: MEDLINE and Embase via the Ovid platform, CINAHL and PsycINFO via the EBSCO platform, and the Cochrane Library. Eligible reviews were published in English; focused on the implementation of tethered patient portals; included patients, health care professionals, managers, and budget holders; and aimed at identifying the contextual factors (ie, barriers and facilitators) that impact the implementation of patient portals. Review titles and abstracts and full-text publications were screened in duplicate. The study characteristics were charted by one author and checked for accuracy by a second author. The NASSS (Non-adoption, Abandonment, Scale-up, Spread, and Sustainability) framework was used to synthesize the findings.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>In total, 10 systematic reviews published between 2015 and 2020 were included in the study. Of these, 3 (30%) reviews addressed patient portals in acute care hospitals, and 2 (20%) reviews addressed the implementation of patient portals among older people in multiple settings (including acute care hospitals). To maximize the inclusion of the literature on patient portal implementation, we also included 5 reviews of systematic reviews that examined patient portals in multiple care settings (including acute care hospitals). Contextual factors influencing patient portal implementation tended to cluster in specific NASSS domains, namely the condition, technology, and value proposition. Certain aspects within these domains received more coverage than others, such as sociocultural factors and comorbidities, the usability and functionality aspects of the technology, and the demand-side value. There are gaps in the literature pertinent to the consideration of the provision of patient portals for older people in acute care hospitals, including the lack of consideration of the diversity of older adults and their needs, the question of interoperability between systems (likely to be important where care involves multiple services), the involvement of lay caregivers, and looking beyond short-term implementation to ways in which portal use can be sustained.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>We identified important contextual factors that impact patient portal implementation and key gaps in the literature. Future research should focus on evaluating strategies that address disparities in use and promote engagement with patient portals among older people in acute care settings.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>patient portal</kwd>
        <kwd>tethered personal health records</kwd>
        <kwd>acute care hospitals</kwd>
        <kwd>implementation</kwd>
        <kwd>scoping review</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Patient portals (also known as tethered personal health records) consist of an internet-based application that accesses the electronic health record of a health care organization and provides timely access to medical records, laboratory results, appointment bookings, repeat prescriptions, and secure messaging with health care professionals, among other content and functionality [<xref ref-type="bibr" rid="ref1">1</xref>]. Patient portals aim to engage patients and carers in managing their care, which has been found to improve health outcomes, the quality of care, and patient safety [<xref ref-type="bibr" rid="ref2">2</xref>]. Patient portals are well established in UK family practice, with electronic health records being commonplace in 96% of general practices for almost 3 decades [<xref ref-type="bibr" rid="ref3">3</xref>]. In UK acute care hospitals, the use of handwritten inpatient records remains widespread [<xref ref-type="bibr" rid="ref3">3</xref>], and as such, patient portals are less common. Global Digital Exemplar (GDE) trusts are internationally recognized providers of exceptional and efficient National Health Service (NHS) care via world-class digital technology and information and are committed to sharing best practices and supporting the widespread adoption of patient portals [<xref ref-type="bibr" rid="ref4">4</xref>]. The future vision of the NHS is to create a single access point to acute care hospitals with integrated systems that share and exchange data securely with other health and care providers [<xref ref-type="bibr" rid="ref5">5</xref>]. However, the integration of portals with the existing systems is currently a barrier to their adoption, in addition to clinical engagement, information governance, low patient awareness, and resources [<xref ref-type="bibr" rid="ref6">6</xref>]. Furthermore, among the patients who currently access portals, engagement or meaningful use is often limited.</p>
        <p>The greatest benefit to patients and the health service can be achieved by optimizing portal use among older people [<xref ref-type="bibr" rid="ref7">7</xref>]. Older people (aged ≥65 years) are less likely to use a patient portal than younger people (86% of adopters are aged &lt;65 years) [<xref ref-type="bibr" rid="ref8">8</xref>], yet they are the highest users of the health service, with more than half (54%) of them experiencing multimorbidity [<xref ref-type="bibr" rid="ref9">9</xref>]. Older people are more at risk of serious complications and hospital-acquired infections, and they may experience frailty and other mobility problems that hinder their access to health centers. Moreover, older age is the greatest risk factor for mortality from COVID-19 [<xref ref-type="bibr" rid="ref10">10</xref>]. Barriers are exacerbated when older patients lack access to and experience of using technology, have lower levels of education, and have low health literacy [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref13">13</xref>]. However, older people have been found to express interest in using a patient portal independently or with a carer, irrespective of their health literacy level, previous portal use, or experience seeking health information over the internet [<xref ref-type="bibr" rid="ref11">11</xref>]. The COVID-19 pandemic has accelerated the rate of adoption of digital technologies in health care settings by necessitating remote visits, communication, and monitoring, which are especially important for people managing long-term health conditions [<xref ref-type="bibr" rid="ref14">14</xref>]. The need and demand for more flexible access to health services are unlikely to diminish.</p>
        <p>There are numerous reviews of patient portal features, functionality, adoption, and implementation, with the vast majority focusing on family practice settings. A review examining portal use in multiple health care settings was published by Antonio et al [<xref ref-type="bibr" rid="ref14">14</xref>]. This umbrella review explored the current state of evidence for patient portals, with a specific focus on portal technology. It identified several factors that influence portal adoption, including patient circumstances, interest, and satisfaction; portal usability; provider attitudes; and service use [<xref ref-type="bibr" rid="ref14">14</xref>]. Another review across multiple health care settings reported a range of patient characteristics that impact portal use, such as age, ethnicity, education, health literacy, health status, and carer role [<xref ref-type="bibr" rid="ref7">7</xref>], and factors that impact patient portal engagement, such as provider endorsement and portal usability. The authors argue that future research should aim to boost portal engagement among specific populations most likely to benefit from its use [<xref ref-type="bibr" rid="ref7">7</xref>]. This review set out to scope the literature on older people and acute care settings to inform the broader aim of our research program—to develop an evidence-based implementation strategy for portal use and engagement among older people in acute care settings. Despite efforts toward the widespread uptake of and engagement with patient portals across acute NHS trusts, there is limited research into evidence-based strategies for successful engagement [<xref ref-type="bibr" rid="ref15">15</xref>]. Engagement strategies, such as advertisement campaigns or training for patients, carers, and staff, must be tailored to the targeted population groups and the local context to be effective [<xref ref-type="bibr" rid="ref16">16</xref>]. Tailoring can improve equity within the patient group. Identifying contextual factors that impact the routine implementation of patient portals in acute care hospitals is the first step toward developing an evidence-based implementation strategy for older people.</p>
      </sec>
      <sec>
        <title>Aim</title>
        <p>The aim of this scoping review was to identify and synthesize the literature on contextual factors that impact the implementation of patient portals in acute care hospitals and among older people.</p>
        <p>Our primary interest was to improve the engagement with patient portals among older people in acute care hospitals. However, we needed a broad scope of the literature to capture learning from studies in multiple settings (family practice and acute care hospitals) and patient groups (general population and older people), given the potential generalizability of the findings across settings.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Reporting Guidance and Theoretical Framework</title>
        <p>This scoping review followed the methodological framework described by Arksey and O’Malley [<xref ref-type="bibr" rid="ref17">17</xref>] and the PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses Extension for Scoping Reviews) reporting guidelines [<xref ref-type="bibr" rid="ref18">18</xref>]. The framework was selected to achieve our broad aim of summarizing what is known about our primary area of interest, to synthesize findings, and to highlight key gaps in the literature.</p>
      </sec>
      <sec>
        <title>Non-adoption, Abandonment, Scale-up, Spread, and Sustainability Framework</title>
        <p>To build on the existing literature, we used a theoretical framework to provide a semantic structure to the synthesis of our findings. The NASSS (Non-adoption, Abandonment, Scale-up, Spread, and Sustainability) framework [<xref ref-type="bibr" rid="ref19">19</xref>] provided the basis for summarizing the results. This framework was developed to analyze the varied outcomes of technological innovations in health and social care and to help inform the implementation of such technologies. The NASSS framework comprises 7 domains: (1) the condition or illness, (2) the technology, (3) the value proposition, (4) the adopter system (intended users), (5) the organization, (6) the wider system (especially regulatory, legal, and policy issues), and (7) a final cross-cutting domain that considers adaptation and embedding over time. Each of the 7 domains can be “simple” (ie, few components and predictable), “complicated” (ie, many components but still largely predictable), or “complex” (ie, many components interacting in a dynamic and unpredictable way). Crucially, NASSS surfaces factors that are often unacknowledged in technology implementation programs, helping to move beyond the identification of individual barriers and enablers in recognition of the dynamic interactions between the domains, for example, the relationship between the individual adopter and the organizational or wider system context.</p>
      </sec>
      <sec>
        <title>Search Strategy</title>
        <p>A search strategy was developed in collaboration with an academic librarian. As a preliminary examination of the literature indicated that only a few reviews focused solely on acute care hospitals or older adults and because the specific health care setting was not always immediately clear, we decided not to include filters for population or health care setting in order not to exclude potentially relevant publications.</p>
        <p>The full search strategy is shown in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>. Search terms related to patient portals and systematic reviews were used. The search strategy used a combination of medical subject headings and free-text words. Searches were restricted to 2010 to account for the pace of development in portal technology. Searches were conducted on June 16, 2020, and included the following databases: MEDLINE and Embase via the Ovid platform, CINAHL and PsycINFO via the EBSCO platform, and the Cochrane Library. Reference lists of the included reviews were screened for additional literature.</p>
        <p>To generate sufficient breadth of coverage for the scoping review, inclusion criteria were defined to capture maximum learning with respect to the implementation of tethered patient portals among older people and in acute care hospitals. Specifically, 3 categories of reviews were eligible for consideration:</p>
        <list list-type="order">
          <list-item>
            <p>Systematic reviews of patient portals in acute care hospitals</p>
          </list-item>
          <list-item>
            <p>Systematic reviews of reviews (with both primary studies and reviews) of patient portals in multiple settings, including acute care hospitals</p>
          </list-item>
          <list-item>
            <p>Systematic reviews of patient portals for older adults in multiple settings, including acute care hospitals</p>
          </list-item>
        </list>
        <p>The inclusion criteria were as follows: reviews published since 2010 in English; reviews focused on the implementation of tethered patient portals (as defined in the <italic>Introduction</italic> section); reviews focused on patient portals for older adults (in settings that include acute care hospitals); reviews focused on patient portals for patients, health care professionals, managers, and budget holders in acute care hospitals; reviews of reviews of patient portals in settings that include acute care hospitals; reviews focused on contextual factors (ie, barriers and facilitators) that impact the implementation of patient portals; systematic reviews; scoping reviews; narrative reviews; qualitative meta-syntheses; meta-ethnographies; and reviews of reviews.</p>
        <p>The exclusion criteria were as follows: reviews published before 2010; reviews not in English; reviews not focused on the implementation of tethered patient portals; reviews focused on the technical aspects of patient portals; reviews in family practice settings only; nonsystematic reviews; secondary analyses of the existing data sets; discussions of literature for theory building or critique; summaries of literature for information or commentary; editors’ discussions; letters; conference abstracts; and theses; and reviews whose full text was not available.</p>
        <boxed-text id="box1" position="float">
          <title>Search strategy by database.</title>
          <p>
            <bold>Search terms for MEDLINE and Embase (via OVID)</bold>
          </p>
          <list list-type="order">
            <list-item>
              <p>Exp Patient Portals/</p>
            </list-item>
            <list-item>
              <p>Health Records, Personal</p>
            </list-item>
            <list-item>
              <p>Patient ADJ2 Portal*.mp</p>
            </list-item>
            <list-item>
              <p>Electronic ADJ2 Portal.mp</p>
            </list-item>
            <list-item>
              <p>(personal adj2 (health or medical) adj2 (record* or info*)).mp</p>
            </list-item>
            <list-item>
              <p>Patient accessible record*.mp</p>
            </list-item>
            <list-item>
              <p>PHR.mp</p>
            </list-item>
            <list-item>
              <p>ePHR.mp</p>
            </list-item>
            <list-item>
              <p>or/1-8 (MEDLINE) or/3-8 (EMBASE)</p>
            </list-item>
            <list-item>
              <p>Meta analysis/</p>
            </list-item>
            <list-item>
              <p>Meta-analysis.ti,ab,pt.</p>
            </list-item>
            <list-item>
              <p>Meta-ethno*.ti,ab,pt.</p>
            </list-item>
            <list-item>
              <p>Review.ti,ab.pt.</p>
            </list-item>
            <list-item>
              <p>or/10-13</p>
            </list-item>
            <list-item>
              <p>and/9,14</p>
            </list-item>
            <list-item>
              <p>Limits – English Language, 2010-current, humans</p>
            </list-item>
          </list>
          <p>
            <bold>Search terms for CINAHL and PsycINFO (via EBSCO)</bold>
          </p>
          <list list-type="order">
            <list-item>
              <p>MH “Patient Portals”</p>
            </list-item>
            <list-item>
              <p>MH “Medical Records, Personal”</p>
            </list-item>
            <list-item>
              <p>Patient n2 Portal*</p>
            </list-item>
            <list-item>
              <p>Electronic n2 Portal</p>
            </list-item>
            <list-item>
              <p>Personal n2 (health or medical) n2 (record* or info*)</p>
            </list-item>
            <list-item>
              <p>Patient accessible record*</p>
            </list-item>
            <list-item>
              <p>PHR</p>
            </list-item>
            <list-item>
              <p>ePHR</p>
            </list-item>
            <list-item>
              <p>or/1-8 (CINAHL) or/3-8 (PsycInfo)</p>
            </list-item>
            <list-item>
              <p>MH Meta analysis</p>
            </list-item>
            <list-item>
              <p>Meta-analysis</p>
            </list-item>
            <list-item>
              <p>Meta-ethno*</p>
            </list-item>
            <list-item>
              <p>Review.ti,ab.pt.</p>
            </list-item>
            <list-item>
              <p>or/10-13</p>
            </list-item>
            <list-item>
              <p>and/9,14</p>
            </list-item>
            <list-item>
              <p>Limits – English Language, 2010-current</p>
            </list-item>
          </list>
          <p>
            <bold>Search terms for Cochrane Library</bold>
          </p>
          <list list-type="order">
            <list-item>
              <p>Exp Patient Portals</p>
            </list-item>
            <list-item>
              <p>Health Records, Personal</p>
            </list-item>
            <list-item>
              <p>Health Records, Electronic</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Study Selection</title>
        <p>Search results were imported into EndNote reference management software (Clarivate Analytics), and duplicates were removed automatically and double checked manually. Two reviewers (JH and ZK) independently screened titles and abstracts. Any discrepancies in the articles identified for full-text screening were discussed, and consensus was reached. Full-text articles of potentially eligible reviews were assessed independently by 2 reviewers (JH and ZK) against the prespecified inclusion and exclusion criteria. Discrepancies were resolved through discussion. The reasons for exclusion were recorded and included in the PRISMA diagram (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) diagram.</p>
          </caption>
          <graphic xlink:href="aging_v6i1e31812_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Data Charting</title>
        <p>In accordance with the Arksey and O’Malley framework for scoping reviews [<xref ref-type="bibr" rid="ref17">17</xref>], a data charting form was compiled in Microsoft Excel (Microsoft Corp), which contained a row for each included study and columns to record general study information, namely authors, publication date, country of origin, review aim, health care setting, participants, definition of patient portal, theoretical framework, database searches, inclusion and exclusion criteria, data extraction method, quality assessment method, method of analysis or synthesis, and the number of included studies. The included studies were examined to determine the extent of study overlap between the included reviews. The data charting form was also used to extract data on the contextual factors (barriers and facilitators) that impacted the implementation of patient portals in accordance with the 7 domains of the NASSS framework (refer to the <italic>NASSS Framework</italic> section), together with the authors’ recommendations for future research. The form was piloted on 4 studies. A single reviewer (JH) read each study and extracted the study characteristics and data on contextual factors from the results and discussion sections. The discussion sections were included in the charting process, as they often provide additional material to enhance the interpretation of review findings. The data extraction for each of the 4 articles was cross-checked by another team member (TJB, ZK, JL, and FS) to verify whether data charting was performed in accordance with the 7 NASSS framework domains. Data charting was then completed by a single reviewer (JH) and independently verified by another member of the team (ZK).</p>
      </sec>
      <sec>
        <title>Summarizing the Results</title>
        <p>A narrative approach was used to summarize the results of the scoping review. In line with the usual practice for scoping reviews [<xref ref-type="bibr" rid="ref17">17</xref>], no attempt was made to assess the quality of the included reviews or the weight of the evidence with respect to the implementation of patient portals.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Search Results</title>
        <p>A total of 2065 references were identified (<xref rid="figure1" ref-type="fig">Figure 1</xref>). After the removal of duplicates (n=606, 29.35%), another 1340 (64.9%) records were excluded based on the title and abstract, leaving 119 (5.76%) full-text articles to be assessed for eligibility. Of the 119 full papers assessed, 10 (8.4%) met the criteria for inclusion in this scoping review. Scrutiny of the reference lists of the included reviews did not generate additional literature for inclusion. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> provides details on the characteristics of the included reviews [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref28">28</xref>].</p>
      </sec>
      <sec>
        <title>Description of the Included Reviews</title>
        <p>The reviews were published between 2015 and 2020. Of the 10 included reviews, 4 (40%) originated from the United States [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref22">22</xref>], 2 (20%) each from the United Kingdom [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>] and the Netherlands [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>], and 1 (10%) each from Australia [<xref ref-type="bibr" rid="ref27">27</xref>] and Iran [<xref ref-type="bibr" rid="ref28">28</xref>]. Overall, 3 (30%) systematic reviews addressed patient portals in acute care hospitals [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>], 5 (50%) systematic reviews of reviews examined patient portals in both acute care hospitals and other care settings [<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref28">28</xref>], and 2 (20%) systematic reviews addressed the implementation of patient portals among older adults (in multiple settings, including acute care hospitals) [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p>
        <p>Of the included reviews, 7 (70%) did not specify a particular framework for the analysis of the results [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], 1 (10%) used the System Engineering Initiative for Patient Safety model to categorize interventions [<xref ref-type="bibr" rid="ref15">15</xref>], 1 (10%) used the Clinical Adoption Framework [<xref ref-type="bibr" rid="ref25">25</xref>], and 1 (10%) applied the Problem Solving Cycle [<xref ref-type="bibr" rid="ref26">26</xref>]. Reviews in which no framework was specified considered portal design, use, and usability [<xref ref-type="bibr" rid="ref20">20</xref>]; input, process, and output factors [<xref ref-type="bibr" rid="ref27">27</xref>]; content and capabilities [<xref ref-type="bibr" rid="ref28">28</xref>]; impact on outcome measures [<xref ref-type="bibr" rid="ref24">24</xref>]; barriers to and facilitators of adoption and user experience [<xref ref-type="bibr" rid="ref21">21</xref>]; characteristics of older users, evaluation of outcome measures and results, and barriers to and facilitators of use [<xref ref-type="bibr" rid="ref22">22</xref>]; and impact on trust and communication and consideration of ethical issues [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      </sec>
      <sec>
        <title>Study Overlap</title>
        <p>To establish the breadth of coverage of this scoping review, an indication of the extent of overlap of studies in the included reviews was determined. The included reviews contained 206 studies (156 primary studies, 75.8%, and 50 reviews, 24.3%), excluding the 109 references of Otte-Trojel et al [<xref ref-type="bibr" rid="ref26">26</xref>], which, unfortunately, we were not able to obtain for scrutiny. <xref ref-type="table" rid="table1">Table 1</xref> provides a summary of the extent of study overlap. Only 19 studies appeared in &gt;1 included review, suggesting limited duplication in the scoping review.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Overlap of studies<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="120"/>
            <col width="90"/>
            <col width="90"/>
            <col width="80"/>
            <col width="100"/>
            <col width="80"/>
            <col width="80"/>
            <col width="90"/>
            <col width="80"/>
            <col width="0"/>
            <col width="100"/>
            <col width="90"/>
            <thead>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">Acute care hospitals, n</td>
                <td colspan="6">Multiple settings (review of reviews), n</td>
                <td colspan="2">Older adults (aged &gt;60 years), n</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>D’Costa et al [<xref ref-type="bibr" rid="ref23">23</xref>], 2020</td>
                <td>Grossman et al [<xref ref-type="bibr" rid="ref15">15</xref>], 2019</td>
                <td>Kelly et al [<xref ref-type="bibr" rid="ref20">20</xref>], 2018</td>
                <td>Dendere et al [<xref ref-type="bibr" rid="ref27">27</xref>], 2019</td>
                <td>Aslani et al [<xref ref-type="bibr" rid="ref28">28</xref>], 2020</td>
                <td>van Mens et al [<xref ref-type="bibr" rid="ref25">25</xref>], 2019</td>
                <td>Otte-Trojel et al [<xref ref-type="bibr" rid="ref26">26</xref>], 2016<sup>b</sup></td>
                <td>Jilka et al [<xref ref-type="bibr" rid="ref24">24</xref>], 2015</td>
                <td colspan="2">Sakaguchi-Tang et al [<xref ref-type="bibr" rid="ref21">21</xref>], 2017</td>
                <td>Kneale and Demiris [<xref ref-type="bibr" rid="ref22">22</xref>], 2017</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>D’Costa et al [<xref ref-type="bibr" rid="ref23">23</xref>], 2020</td>
                <td>N/A<sup>b</sup></td>
                <td>0</td>
                <td>3</td>
                <td>3</td>
                <td>0</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">0</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Grossman et al [<xref ref-type="bibr" rid="ref15">15</xref>], 2019</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td>1</td>
                <td>0</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">0</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Kelly et al [<xref ref-type="bibr" rid="ref20">20</xref>], 2018</td>
                <td>3</td>
                <td>0</td>
                <td>N/A</td>
                <td>6</td>
                <td>0</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">0</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Dendere et al [<xref ref-type="bibr" rid="ref27">27</xref>], 2019</td>
                <td>3</td>
                <td>1</td>
                <td>5</td>
                <td>N/A</td>
                <td>1</td>
                <td>6</td>
                <td>N/A</td>
                <td>2</td>
                <td colspan="2">0</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>Aslani et al [<xref ref-type="bibr" rid="ref28">28</xref>], 2020</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>1</td>
                <td>N/A</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">0</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>van Mens et al [<xref ref-type="bibr" rid="ref25">25</xref>], 2019</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>6</td>
                <td>0</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">0</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Otte-Trojel et al [<xref ref-type="bibr" rid="ref26">26</xref>], 2016<sup>c</sup></td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td colspan="2">N/A</td>
                <td>N/A</td>
              </tr>
              <tr valign="top">
                <td>Jilka et al [<xref ref-type="bibr" rid="ref24">24</xref>], 2015</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>2</td>
                <td>0</td>
                <td>0</td>
                <td>N/A</td>
                <td>N/A</td>
                <td colspan="2">0</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Sakaguchi-Tang et al [<xref ref-type="bibr" rid="ref21">21</xref>], 2017</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">N/A</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Kneale and Demiris [<xref ref-type="bibr" rid="ref22">22</xref>], 2017</td>
                <td>0</td>
                <td>0</td>
                <td>0</td>
                <td>2</td>
                <td>1</td>
                <td>0</td>
                <td>N/A</td>
                <td>0</td>
                <td colspan="2">1</td>
                <td>N/A</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Overlap tracked in 156 primary studies and 50 reviews.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>N/A: not applicable.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>Not able to obtain reference list.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Narrative of Results by NASSS Framework Domains</title>
        <sec>
          <title>Overview</title>
          <p>The results and discussion sections of the included studies were successfully mapped to the NASSS framework domains and subdomains. The findings for each domain are presented and a summary is provided in <xref ref-type="table" rid="table2">Table 2</xref>. The headings for the domains and subdomains are taken directly from the NASSS framework. Although each domain is commented on in turn, there are interrelationships between the findings that are highlighted in the text and addressed at the end of this section.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Non-adoption, Abandonment, Scale-up, Spread, and Sustainability (NASSS) framework: contextual factors that influence the implementation of patient portals.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="30"/>
              <col width="30"/>
              <col width="590"/>
              <col width="0"/>
              <col width="90"/>
              <col width="0"/>
              <col width="100"/>
              <col width="0"/>
              <col width="130"/>
              <thead>
                <tr valign="top">
                  <td colspan="5">NASSS domain and subdomain and contextual factors (namely, facilitators and barriers)</td>
                  <td colspan="2">Acute care hospitals</td>
                  <td colspan="2">Mixed health care setting</td>
                  <td>Older adults (aged &gt;60 years)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="10">
                    <bold>1. Condition</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>What is the nature of the condition or illness?</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Greater disease severity</td>
                  <td colspan="2">—<sup>a</sup></td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Chronic disease (and associated well-established case management programs)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Severity and circumstances of illness (eg, reduced involvement in decision-making and fewer questions)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Relevant sociocultural factors and comorbidities</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Higher socioeconomic status, female sex, younger age, White ethnicity, and younger senior citizens</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Disease-specific portal</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Lower socioeconomic status, male gender, older age, and non-White ethnicity (impacts enrollment and engagement)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Diversity of older adults (not well understood)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Low health literacy and numeracy (and understanding of health literacy)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Lack of digital access</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Insurance status</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Comorbidities such as vision and hearing loss, decreased dexterity and mobility, and declining cognitive function</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td colspan="10">
                    <bold>2. Technology</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Key features</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Information and identity authentication and protection</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Usability (eg, set-up, interface design, simple displays, text visibility, buttons, patient-friendly content, ease of navigation, personalized interface, and reminders to view)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Functionality (eg, communication with providers; access to reliable, timely and comprehensive personal medical information; content in minority languages; and inbuilt system alerts)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Accessibility (eg, adding mobile access and providing on-site kiosks)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Participatory and iterative design approaches</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Iterative user evaluation (eg, patients and providers)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Definition of minimum data set to plan care and continuously evaluate treatment</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients’ security and privacy concerns (eg, control over access)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Providers’ concerns about sharing patient information</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Usability (eg, interface design, technical glitches, log-on, navigation, accessibility of information for patients, and printing and using information)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Establishing a trade-off among security measures, user friendliness, and flexibility</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Functionality (eg, differing information needs of patients and providers; differing patient preferences over data content and input; diversity of health data types and formats and portal ability to handle the diversity of health data types and formats; data transparency—what data are released and to whom and how they are released; language used; and level of features [eg, reminders, dictionary, lifestyle advice, print capability, and user voice command])</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Accessibility (eg, computer and internet access and secure and stable infrastructures)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Type of knowledge in play</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Data set is comprehensive, reliable, complete, understandable, and valid</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Audit trail for revisions to data</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Concerns about patients’ ability to interpret test results and deal with sensitive information without professional support or interpretation</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Real-time (release of) information without real-time support</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Providers’ concerns about the reliability of patient-generated data (as basis for clinical decisions)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Knowledge to use</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patient training and technical support (eg, videos, handbooks, hotline, and workshops)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Training for providers</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Quality of patient training</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients’ level of technology literacy (eg, perceived and actual skill and computer anxiety)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Technology supply model</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Portals that integrate into preexisting systems</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Interoperability (eg, information exchange and sharing)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Interoperability (eg, achieving appropriate data exchange among systems)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td colspan="10">
                    <bold>3. Value proposition</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Supply-side value</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Facilitates the processing of payments by insurance companies</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Trial period before purchase (ie, to test usability and estimate financial and organizational impact)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Positive return on investment and impact on charges and costs</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Trade-off among the type of architecture, responsiveness to local needs, and implementation time and cost (ie, decentralized and more expensive but more responsive and shorter implementation time)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Establishing sound business case (eg, no standardized evaluation frameworks, no reimbursement structures for electronic services, lack of evidence of cost savings, and lack of financial sustainability)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Demand-side value</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Satisfies patients’ need for information; facilitates knowledge retention, understanding, and engagement in care by patient; sense of empowerment and control; feeling of being better prepared; and perceived usefulness (eg, aids self-management, utility features, and information in one place)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Provide communication route with professionals between clinic rounds (eg, patient driven communication)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Assists (verbal) interactions or appointments with professionals and patient-provider communication</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Access to information facilitates the development of trust in diagnosis, investigations, treatment, and professionals (eg, relationships)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Helps inaccuracies in EHR<sup>b</sup> to be identified (eg, detection of errors and patient safety)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Contributes to enhanced discussions with patients and aids communication</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Prevents misunderstandings and builds trust (ie, careful and clear recording of information)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Usefulness and time efficiency (ie, clear recording prevents the need to repeat information and aids interprofessional communication)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Helps improve care (eg, planning and continuous evaluation of treatment, adherence, patient satisfaction and engagement, reduced patient anxiety, timely decision-making)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients perceive extra responsibility for finding errors or poor outcomes</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients’ concern about threat to face-to-face communication with professionals</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients’ do not see value or usefulness (eg, lack awareness of features)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patient views about “user fee for use”</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals’ concern that messaging may adversely impact verbal communication</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals do not perceive usefulness</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td colspan="10">
                    <bold>4. Adopter system</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Changes in staff roles, practices, and identities</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Accepting of collaborative versus expert-led care</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals’ positive level of engagement, knowledge, and confidence in portal systems</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Less accepting of collaborative versus expert-led care and do not wish to cede autonomy to patients</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals need to support patients to interpret and emotionally deal with the information in portals</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>How is responsibility for the release of test results managed? (eg, who takes responsibility and editing before release)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals’ level of engagement, knowledge, skills, and confidence in portals</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>What is expected of patients?</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals support and encourage patients’ use of portals (eg, endorsement, reminders, and materials)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients’ willingness to enter basic information into portals or manage records</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patient preferences regarding the entry of data into portals, increased knowledge, and managing records</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals or providers do not encourage patients’ use of portals</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>What is assumed about the network of lay care givers?</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>None identified</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Patients lack help or support to access portals</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                </tr>
                <tr valign="top">
                  <td colspan="10">
                    <bold>5. Organization</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Organization’s capacity to innovate</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Leadership involvement in portal design and development of policies for user training and the integration of patient portals into workflows</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Communication around technical, interpersonal, and workflow aspects of portals</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Organizational interpretation of government legislation related to portals</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Constrained financial context (eg, small or rural hospitals)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Organizational interpretation of government legislation</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Lack of leadership support (fear and hesitancy in implementation)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Is the organization ready for technology-supported change?</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Policies in place to support portals (eg, universal access policy, security protocols, adherence audits, data availability, and timing)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Lack of support for new forms of communication between patients and professionals</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Lack of policies on access rights and authorization process (including proxy access and access for minors)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Ease of funding and adoption decision</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Internal and external exchange of information to improve the quality, safety, and effectiveness of care</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Providers’ concerns about diverting resources to the less disadvantaged (ie, those who can read and ask questions)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Integrating patient portal use across care transitions (ie, with other organizations) to improve care</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Deciding on the balance between IT structure and implementation time and cost</td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Changes needed in team interactions and routines</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Integrating data release with workflow (ie, to facilitate professionals’ follow-up with patients)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Workload and work routines not adversely impacted or positively impacted (eg, time efficiencies)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>How to organize the release of results to patients without professionals’ help with interpretation and support (eg, real-time release or delayed released)</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Professionals’ concerns about the impact of increased level of patient questions, patient overuse of messaging, increase in documentation time, and portals on workflow</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Work involved in implementation and who will do it</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Involvement of professionals in workflow engineering and the evaluation of the impact of portal use on workload and processes</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>None identified</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td colspan="10">
                    <bold>6. Wider context</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>What is the political, economic, regulatory, professional, and sociocultural context of program rollout?</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Aspects of culture (doctors from English-speaking countries), including the coverage of portals, PHRs<sup>c</sup>, and EHRs in medical and nursing school curricula</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Health professionals’ liability concerns</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Health systems with a transactional component</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Resource for policy makers, health care specialists, and stakeholders to improve care and the quality of treatment</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">National and international information exchange (interoperability) and other standards (eg, Health Insurance Portability and Accountability Act, International Health Level 7, regional health information exchanges, and key public infrastructures)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Appropriate reimbursement mechanisms</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Reimbursement structures for electronic services</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Providers’ liability concerns (eg, breached privacy or patients’ harmful behaviors)</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Nonstandardized rules for developing and managing health information infrastructures</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Relationship between macrolevel and mesolevel (eg, organization) factors was not well explored</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref22">22</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Regulations (eg, Health Insurance Portability) do not cover portal developers and hosting organizations</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td colspan="10">
                    <bold>7. Embedding and adaptation</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Scope for adapting and coevolving technology and service</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>None identified</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">
                    <bold>Barriers</bold>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Concern that medical record maintains integrity as a working document that facilitates the transfer of knowledge between health professionals</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>How portals can be extended beyond a single organization (ie, particularly in fragmented care delivery contexts)?</td>
                  <td colspan="2">—</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="9">
                    <bold>Organization resilience to critical events</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Facilitators</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>None identified</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="8">
                    <bold>Barriers</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>None identified</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                  <td colspan="2">—</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>Not available.</p>
              </fn>
              <fn id="table2fn2">
                <p><sup>b</sup>EHR: electronic health record.</p>
              </fn>
              <fn id="table2fn3">
                <p><sup>c</sup>PHR: personal health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Domain 1: The Condition</title>
          <sec>
            <title>What Is the Nature of the Condition or Illness?</title>
            <p>The included reviews documented patient portals that are open to individuals with a variety of health conditions, including acute and chronic diseases and high-risk conditions. Reviews focusing on patient portals in acute care hospitals included adult patients with acute medical conditions [<xref ref-type="bibr" rid="ref23">23</xref>], inpatients and outpatients classified as vulnerable (including those with cardiovascular diseases, those with HIV, those with ophthalmic conditions and those with chronic or unspecified conditions) [<xref ref-type="bibr" rid="ref15">15</xref>], patients who have had cardiac surgery, patients who were in an intensive care unit, patients with cancer, parents of patients who were in a neonatal intensive care unit, and caregivers or patients who underwent bone marrow transplant. Reviews focusing on multiple care settings included patients with multiple sclerosis [<xref ref-type="bibr" rid="ref28">28</xref>], patients in any medical domain [<xref ref-type="bibr" rid="ref25">25</xref>], adult patients with chronic diseases, patients in family practice settings [<xref ref-type="bibr" rid="ref24">24</xref>], and patients with unspecified conditions [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. The reviews focused on older patients aged ≥60 years did not specify an illness or medical domain.</p>
            <p>There was limited consideration of how clinical characteristics played a role in patient portal use. An examination of inpatient portals [<xref ref-type="bibr" rid="ref27">27</xref>] highlighted patients’ desire to be able to view their daily schedule, view information on medications and test results, and learn about care and preparations for discharge. This review acknowledged how the nature of an individual’s condition (eg, severe illness or intense pain) could affect their ability or desire to interact with the functionality of a patient portal, as well as their capacity to be involved in decision-making about their care and to formulate and ask questions to health professionals [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
            <p>A total of 3 (30%) reviews suggested that patients with greater disease severity [<xref ref-type="bibr" rid="ref27">27</xref>] or with chronic disease [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>] may engage more with a portal. Patients with chronic diseases (such as diabetes, hypertension, or depression) have the benefit of well-established case management programs [<xref ref-type="bibr" rid="ref24">24</xref>]. Although this may facilitate the adoption of a portal, the authors noted that concomitant case management programs will also be a factor impacting disease outcomes (separate from any impact on patient outcomes from the portal), making the findings of disease-specific studies of patient portal implementation difficult to extrapolate across non–disease-specific populations [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          </sec>
          <sec>
            <title>What Are the Relevant Sociocultural Factors and Comorbidities?</title>
            <p>The NASSS framework considers how complexity occurs when a condition or an illness is associated with sociocultural factors (eg, poverty or social exclusion) and comorbidities (eg, loss of function and multimorbidity of older age). The impact of these factors on patient portal adoption received more extensive coverage in the included reviews, along with concerns about the potential for the exacerbation of health inequalities owing to disparities in engagement, as outlined subsequently.</p>
            <p>The included reviews suggested that portal adoption is associated with having a higher socioeconomic status, being female, being of White ethnicity, being younger, and being a younger senior citizen [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
            <p>Low health literacy and numeracy in patient groups [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>] as well as a lack of digital access [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref26">26</xref>] were identified as barriers to portal use. Vulnerable groups [<xref ref-type="bibr" rid="ref15">15</xref>], those with lower socioeconomic status [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], and those with less favorable health insurance status [<xref ref-type="bibr" rid="ref15">15</xref>] are less likely to be enrolled in or engage with patient portals. In addition, increasing age, male sex, and non-White ethnicity were identified as factors associated with low adoption [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
            <p>Certain comorbidities, such as vision and hearing loss, decreased dexterity and mobility, and declining cognitive function, were identified as barriers to portal use [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. These factors may be associated with the aging process; however, 1 (10%) review highlighted that the diversity of older adults and their needs relative to patient portals are not well understood [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
          </sec>
        </sec>
        <sec>
          <title>Domain 2: The Technology</title>
          <sec>
            <title>Material and Technical Features</title>
            <p>The included reviews did not outline the technology in detail but identified several material and technical features that promote patient portal adoption and user satisfaction, including a well-designed interface [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], ease of setup and access [<xref ref-type="bibr" rid="ref21">21</xref>], straightforward navigation [<xref ref-type="bibr" rid="ref20">20</xref>] and information transfer [<xref ref-type="bibr" rid="ref21">21</xref>], simple formats [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>] and buttons [<xref ref-type="bibr" rid="ref23">23</xref>], text visibility [<xref ref-type="bibr" rid="ref28">28</xref>], user-friendly content [<xref ref-type="bibr" rid="ref20">20</xref>], error messages [<xref ref-type="bibr" rid="ref28">28</xref>], real-time [<xref ref-type="bibr" rid="ref20">20</xref>] or disease-specific information [<xref ref-type="bibr" rid="ref27">27</xref>], email reminders to view content [<xref ref-type="bibr" rid="ref15">15</xref>], and a personalized interface [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
            <p>Conversely, poor usability features, such as poor interface design [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], technical glitches [<xref ref-type="bibr" rid="ref27">27</xref>], log-on [<xref ref-type="bibr" rid="ref21">21</xref>] or navigation difficulties [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>], and difficulties with printing and using information [<xref ref-type="bibr" rid="ref22">22</xref>] were reported to have a negative impact on users’ experience, and satisfaction, with patient portals [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Moreover, 1 (10%) review suggested that if patients perceive the access to their personal health records as useful, they are more willing to overcome the technical barriers of engaging with the patient portal [<xref ref-type="bibr" rid="ref22">22</xref>]. This is linked to domain 3 (the value proposition) in terms of the desirability or value of the portal technology for patients.</p>
            <p>The reviews suggested that participatory and iterative design [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>] and iterative user evaluation [<xref ref-type="bibr" rid="ref15">15</xref>], including both patient and health professional users, at the planning and development stage of a patient portal are ways to overcome usability issues. Such inclusive and consultative design approaches also allow the functionality of patient portals to be addressed [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. Reviews reported that patient engagement with portals can be facilitated by offering desired features, including communication with health professionals [<xref ref-type="bibr" rid="ref20">20</xref>]; access to reliable, timely, and comprehensive personal medical information [<xref ref-type="bibr" rid="ref27">27</xref>]; and content in minority languages [<xref ref-type="bibr" rid="ref26">26</xref>]. The reviews also pointed to the benefits for health professionals from their involvement at the design stage, including the specification of a minimum data set for care planning and for the continuous evaluation of treatment [<xref ref-type="bibr" rid="ref28">28</xref>], and from inbuilt system alerts (eg, if a patient does not open an email or to signal a medical emergency) [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
            <p>Several reviews highlighted potential difficulties in defining the functionality of a patient portal system, including the differing information needs of patients and health professionals [<xref ref-type="bibr" rid="ref20">20</xref>], differing patient preferences regarding data content and data input [<xref ref-type="bibr" rid="ref27">27</xref>], the diversity of health data formats [<xref ref-type="bibr" rid="ref28">28</xref>], the language to be used (ie, designing content for lay and professional audiences) [<xref ref-type="bibr" rid="ref26">26</xref>], the level of features (eg, reminders, dictionary of medical terms, lifestyle advice, and print and user voice command capability) [<xref ref-type="bibr" rid="ref21">21</xref>], and data transparency (ie, deciding what data to release to patients and when and how to make them available) [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
            <p>The information privacy and security aspects of patient portals were reported to be an area of concern. This could be patients’ concerns regarding their personal health information [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref27">27</xref>] or health professionals’ concerns about sharing patient information [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. Measures such as robust identity authentication and information protection [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] were suggested as mechanisms to address such concerns, with the observation that there can be a trade-off between security measures and user friendliness [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
            <p>Accessibility of the technology for patients [<xref ref-type="bibr" rid="ref24">24</xref>], including computer [<xref ref-type="bibr" rid="ref21">21</xref>] and internet [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref25">25</xref>] access, was highlighted as another barrier to the implementation of patient portals. This may be because of cost issues [<xref ref-type="bibr" rid="ref21">21</xref>]. Suggested mechanisms to promote accessibility were making mobile as well as computer access available [<xref ref-type="bibr" rid="ref15">15</xref>] and providing on-site kiosks [<xref ref-type="bibr" rid="ref26">26</xref>]. Establishing secure and stable technical infrastructures on which portals can operate was reported to be a challenge for providers [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
          </sec>
          <sec>
            <title>Type of Data Generated or Knowledge in Play</title>
            <p>In terms of the data held in the patient portal, 1 (10%) review suggested that the data set needed to be comprehensive, reliable, complete, understandable, and valid [<xref ref-type="bibr" rid="ref28">28</xref>], with another (10%) recommending the inclusion of an audit trail so that the revisions made to the data are visible [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
            <p>Several reviews raised the issue of health professionals’ concerns about patients’ access to health information via portals, particularly sensitive information, with questions about how patients can deal with the information without professionals’ help with interpretation and support [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. This concern particularly revolved around the issue of the real-time release of data or test results without real-time support [<xref ref-type="bibr" rid="ref23">23</xref>] and is linked to domain 5 (the organization), whereby health professionals need to adapt to patient portal technology and incorporate it into their practice. Patient portals providing opportunities for patients to enter data about their condition raised additional questions about knowledge in play; 2 (20%) reviews reported that health professionals can have reservations about the reliability of patient-generated data in a portal and whether these data should form the basis of clinical decisions [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>].</p>
          </sec>
          <sec>
            <title>Knowledge Needed to Use</title>
            <p>The reviews suggested that training and support can help portal use [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref26">26</xref>] and the use of specific features [<xref ref-type="bibr" rid="ref15">15</xref>], helping to overcome the barrier of patients’ technology literacy [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref26">26</xref>], including perceived and actual computer and internet skills [<xref ref-type="bibr" rid="ref21">21</xref>]. However, 1 (10%) review reported that it is possible for training to have unintended consequences (ie, decreased intention to use) [<xref ref-type="bibr" rid="ref15">15</xref>]. The training of health professionals must also be addressed [<xref ref-type="bibr" rid="ref26">26</xref>]. It was posited that various tools and aids can facilitate the understanding of portal concepts and navigation, health information, and health management tasks (eg, videos, user handbooks, hotlines, and workshops) [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
          </sec>
          <sec>
            <title>Technology Supply Model</title>
            <p>Although the included reviews did not address how the patient portal technology was procured, the lack of interoperability for achieving appropriate data exchange between systems was identified as a barrier to adoption [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Portals that can be integrated into preexisting systems or offer data sharing and exchange are identified as facilitators [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
          </sec>
        </sec>
        <sec>
          <title>Domain 3: The Value Proposition</title>
          <sec>
            <title>What Is the Developer’s Business Case for the Technology (Supply-Side Value)?</title>
            <p>The reviews did not address the issue of the business case for patient portals from the developer’s perspective but did examine it from the health care system’s point of view, primarily with respect to the difficulties in establishing such a case [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>].</p>
            <p>Uncertainty around cost savings and financial sustainability, as well as reimbursement models for electronic services [<xref ref-type="bibr" rid="ref26">26</xref>], contributes to complexity in this situation. The absence of standardized evaluation frameworks means that evidence of benefits (such as administrative efficiency or better-managed patients) is lacking. In addition, 1 (10%) review highlighted the challenge of deciding on a balance between technology architecture (ie, centralized or decentralized), its responsiveness to local needs, ease of implementation, and cost when compiling a business case; decentralized architectures are reportedly more compatible with local needs and can be implemented more quickly but have higher costs [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
            <p>A recommendation for ensuring a sustainable business case was to have a trial period before committing to the purchase of a portal [<xref ref-type="bibr" rid="ref26">26</xref>]. This allows the testing of usability and provides an opportunity to estimate the likely financial and organizational effects [<xref ref-type="bibr" rid="ref26">26</xref>], such as the facilitation of the processing of payments [<xref ref-type="bibr" rid="ref28">28</xref>]. It was suggested that determining a positive return on investment and the potential for lower hospital costs will support implementation [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          </sec>
          <sec>
            <title>What Is the Desirability, Efficacy, Safety, and Cost-effectiveness (Demand-Side Value)?</title>
            <p>The reviews suggested that patient portals do satisfy patients’ need for information (eg, about hospital schedule, medication, test results, and discharge planning) [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], helping with knowledge retention [<xref ref-type="bibr" rid="ref23">23</xref>] and interactions with professionals [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] and providing a communication channel between clinic rounds [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. These features support patients’ understanding of their condition [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>] and engagement in care or self-management [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], leading to a greater sense of empowerment and control [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref27">27</xref>] and feeling of being better prepared (ie, for appointments, emergencies, and discharge) [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. In addition, the reviews indicated that access to information via the portal also facilitated the development of trust in health professionals [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>], with patients feeling reassured by shared information [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
            <p>Professionals valued patient portals as a mechanism for enhancing patient care [<xref ref-type="bibr" rid="ref27">27</xref>] through timely decision-making [<xref ref-type="bibr" rid="ref28">28</xref>], planning and continuous evaluation of treatment [<xref ref-type="bibr" rid="ref28">28</xref>], and building trust [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>] and as a mechanism that leads to improved patient engagement, adherence to treatment, and satisfaction with care [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. Portals are also regarded as an aid to communication with patients [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] and as a tool to enhance interprofessional communication [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. The clear recording of data in a portal was found to help efficiency by reducing the need to repeat information [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] and to contribute to patient safety by allowing inaccuracies and errors to be identified [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
            <p>As indicated under domain 2 (the technology), where patients perceive portals as useful, they are prepared to overcome the technical barriers to portal use [<xref ref-type="bibr" rid="ref22">22</xref>]. However, some reviews identified a lack of perceived usefulness from the patient perspective as a barrier to engagement with a portal [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], together with patient views about “fee for use” [<xref ref-type="bibr" rid="ref22">22</xref>]. Some patients regarded portals as a threat to valued face-to-face communication with health professionals [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>] or felt an additional (and unwelcome) burden of responsibility with respect to their care (eg, for finding errors or for poor outcomes) [<xref ref-type="bibr" rid="ref23">23</xref>]. Some health professionals also did not see the usefulness or value of patient portals [<xref ref-type="bibr" rid="ref24">24</xref>] or felt that they would adversely impact face-to-face communication with patients [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
          </sec>
        </sec>
        <sec>
          <title>Domain 4: The Adopter System</title>
          <sec>
            <title>What Changes in Staff Roles, Practices, and Identities Are Implied?</title>
            <p>The reviews highlighted that the adoption of patient portals can raise questions regarding health professionals’ scope of practice and professional identity. There are implications in terms of health professionals’ confidence and ability to interact with the technology [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]; their need to incorporate the technology into their work practices [<xref ref-type="bibr" rid="ref23">23</xref>]; and the potential for patient portals to alter the balance of the professional-patient relationship, shifting to more collaborative, rather than expert-led, working [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. These elements are linked to considerations in domain 2 (the technology) regarding the involvement of health professionals at the portal design stage, as well as the provision of training and ongoing support for portal use, and to domain 5 (the organization) regarding the potential impact of patient portals on the workflow and workload of professionals and models of care and service delivery.</p>
            <p>Moreover, 1 (10%) review suggested that when health professionals advocated collaborative working with patients and had confidence in using patient portals, this acted as a facilitator of implementation [<xref ref-type="bibr" rid="ref23">23</xref>]. Conversely, where professionals were reluctant to cede professional autonomy and work more collaboratively with patients [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>] or had concerns about their capacity and skills to engage with portal technology [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], this acted as a barrier to the implementation of patient portals. Examples of implications for practice included being able to support patients to interpret and emotionally deal with the information contained in the portal and deciding who takes responsibility for the release of information into the portal and whether the information needs to be edited before release [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
          </sec>
          <sec>
            <title>What Is Expected of the Patient (or Immediate Caregiver) and Is This Achievable by, and Acceptable to, Them?</title>
            <p>Professionals’ support and encouragement of patients’ use of portals were identified as mechanisms to facilitate the adoption of portals among patients [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>]. Both (20%) the reviews that focused on older adults suggested that patients may be willing to enter basic data into the portal [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Patient engagement with portals is impacted by different preferences: some patients may not wish to have the responsibility of increased knowledge afforded by the portal [<xref ref-type="bibr" rid="ref23">23</xref>] and do not wish to enter data [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>] or be responsible for managing records [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
          </sec>
          <sec>
            <title>What Is Assumed About the Extended Network of Lay Caregivers?</title>
            <p>The included reviews did not directly address expectations of the involvement of the wider care network or lay caregivers in the adoption of patient portals, although it is acknowledged that older patients may lack help or support to access a portal [<xref ref-type="bibr" rid="ref21">21</xref>]. This subject is linked to the information security and privacy concerns raised in domain 2 (the technology) and to the questions about policies on access (including proxy access) and security in domain 5 (the organization).</p>
          </sec>
        </sec>
        <sec>
          <title>Domain 5: The Organization</title>
          <sec>
            <title>What Is the Organization’s Capacity to Innovate?</title>
            <p>The included reviews highlighted the importance of organizational leadership support in promoting portal adoption [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] through actions such as working with developers on portal design [<xref ref-type="bibr" rid="ref27">27</xref>] and developing policies for user training (both patients and health professionals) and integrating portals into clinical workflows, as well as organizing communication around the technical, interpersonal, and workflow aspects of patient portals [<xref ref-type="bibr" rid="ref28">28</xref>]. A lack of executive leadership support can lead to hesitancy with portal implementation [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
            <p>One (10%) review pointed to the potential for variability in portal implementation (eg, content made available to patients) in situations where providers have the discretion to interpret government legislation [<xref ref-type="bibr" rid="ref27">27</xref>]. This is connected with the issue of internal and external information exchange; domain 6 (the wider context); and the extent to which there are standardized, nationally mandated regulations for developing and maintaining health information technologies. This may also influence the value proposition for patients (domain 3).</p>
            <p>A constrained financial context will impact the implementation of portal technology [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. One of the included reviews highlighted resource constraints at small or rural hospitals [<xref ref-type="bibr" rid="ref27">27</xref>] as a situation likely to make the adoption of patient portals more difficult.</p>
          </sec>
          <sec>
            <title>How Ready Is the Organization for Technology-Supported Change?</title>
            <p>The included reviews highlighted the range of preparatory work that organizations need to do to support portal implementation. Organizational policies such as universal access [<xref ref-type="bibr" rid="ref15">15</xref>]; security protocols, including those related to proxy access and access for minors [<xref ref-type="bibr" rid="ref26">26</xref>]; adherence audits [<xref ref-type="bibr" rid="ref26">26</xref>]; and data availability and timing will facilitate portal development and implementation. One (10%) review pointed to the necessity for sufficient organizational support for new forms of communication between patients and health professionals afforded by patient portals [<xref ref-type="bibr" rid="ref27">27</xref>].</p>
          </sec>
          <sec>
            <title>How Easy Will the Adoption and Funding Decision Be?</title>
            <p>The challenges of making decisions on adoption and funding were highlighted by the included reviews. Organizations need to decide on the balance between costs, implementation time, and the flexibility of the portal architecture [<xref ref-type="bibr" rid="ref28">28</xref>], including the ability to integrate portal use across care transitions (ie, interoperability with other organizations) [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. There may be concerns that portals divert scarce resources to those who are <italic>less</italic> disadvantaged (ie, those who can read and have the confidence to ask questions) [<xref ref-type="bibr" rid="ref23">23</xref>]. However, enhanced communication through internal and external exchange of information may offer positive advantages for the quality, safety, and effectiveness of patient care [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
          </sec>
          <sec>
            <title>What Changes Will Be Needed in Team Interactions and Routines?</title>
            <p>Concerns among health professionals regarding the potential impact of patient portals on workload and workflow were identified in the reviews [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], including the possibility of an increased level of patient questions [<xref ref-type="bibr" rid="ref20">20</xref>], the potential for patient overuse of portal messaging functions [<xref ref-type="bibr" rid="ref20">20</xref>], the question of how to respond to patient inquiries in a timely manner [<xref ref-type="bibr" rid="ref26">26</xref>], and an increase in documentation time [<xref ref-type="bibr" rid="ref24">24</xref>]. A related concern was how to manage and organize the release of results to patients without the presence of a health professional to offer help with interpretation and support [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
            <p>Some solutions addressing workflow concerns were presented, including integrating data release to patients with workflow patterns to facilitate health professional follow-up with patients when the results are made available [<xref ref-type="bibr" rid="ref26">26</xref>] and providing evidence for a positive impact on workflow and workload (eg, time efficiencies) [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
            <p>These issues are linked to the involvement of health professionals at the technology design stage (domain 2), where concerns about the potential impact on workflows can be raised, and to the points raised earlier about the development of policies around integration by organizational leadership and proactive communication around the integration of portals into workflows.</p>
          </sec>
        </sec>
        <sec>
          <title>Domain 6: The Wider Context</title>
          <sec>
            <title>What Is the Political, Economic, Regulatory, Professional, and Sociocultural Context for Program Rollout?</title>
            <p>The included reviews suggest the development of national and international information exchange (ie, interoperability) and other standards (eg, security) as a facilitator of portal implementation [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>].</p>
            <p>One (10%) review identified health professionals’ liability concerns as a factor that will promote patient access to records (eg, in countries such as Norway and the United States) [<xref ref-type="bibr" rid="ref23">23</xref>]. For countries with health systems that have a transactional component (eg, the United States), it is posited that portals can act as a mechanism for helping patients understand their health care costs and that this will encourage the provision of the technology [<xref ref-type="bibr" rid="ref23">23</xref>]. Other cultural components identified as important for adoption included the coverage of portals in medical and nursing school curricula [<xref ref-type="bibr" rid="ref26">26</xref>] and the perceived benefit of portal data sets as a resource for policy makers, health care specialists, and stakeholders to evaluate and improve care [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
            <p>Barriers to portal implementation identified in the reviews included nonstandardized rules for developing and managing health information infrastructures (ie, for interoperability) and regulations for data protection and management (eg, Health Insurance Portability and Accountability Act in the United States) that do not cover portal developers or hosting organizations, creating uncertainty about appropriate data governance [<xref ref-type="bibr" rid="ref26">26</xref>]. In addition, it was pointed out that providers may have liability concerns about privacy breaches or patients’ harmful behaviors [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
            <p>One (10%) review pointed to inadequate or contradictory reimbursement structures for electronic services as a wider contextual barrier to the implementation of patient portals [<xref ref-type="bibr" rid="ref26">26</xref>], inhibiting the development of a sound business model (link to domain 3). This review cited the Meaningful Use program in the United States as an example of a national initiative for patient portal adoption that was hampered by modest incentives and high thresholds, which impeded the development of an adequate business case [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
          </sec>
        </sec>
        <sec>
          <title>Domain 7: Embedding and Sustaining</title>
          <sec>
            <title>How Much Scope Is There for Adapting and Coevolving the Technology and Services Over Time?</title>
            <p>In the included reviews, there was little consideration of the long-term adaptability and sustainability of the patient portals. The focus of attention was on development and short-term implementation issues.</p>
            <p>Two long-term considerations were mentioned in the literature. The first was a general concern that the medical record maintains its integrity as a working document that facilitates the transfer of knowledge among many health professionals [<xref ref-type="bibr" rid="ref23">23</xref>]. The second was related to the fact that most portals are implemented within a single organization or organized care delivery system, which limits their relevance to other organizational contexts [<xref ref-type="bibr" rid="ref26">26</xref>]. Portal implementation will be more challenging across organizational contexts or in fragmented care delivery contexts, which are situations that are likely to feature in older people’s care.</p>
          </sec>
          <sec>
            <title>How Resilient Is the Organization to Handling Critical Events and Adapting to Unforeseen Eventualities?</title>
            <p>There was no coverage of organizational resilience to critical or unforeseen events and ability to adapt to them.</p>
          </sec>
        </sec>
      </sec>
      <sec>
        <title>Coverage and Interactions Between NASSS Domains</title>
        <p><xref ref-type="table" rid="table2">Table 2</xref> shows that the contextual factors influencing implementation identified in the included reviews tended to cluster in specific domains: (1) the condition, (2) the technology, and (3) the value proposition. Certain aspects within these domains received more coverage than others, such as sociocultural factors and comorbidities, the usability and functionality aspects of the technology, and the demand-side value. The included reviews that used a theoretical framework [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] pointed to a focus on a narrow range of components of patient portal adoption, usually people and use factors.</p>
        <p>There are links among the different domains. For example, the severity of an individual’s illness can affect their ability to interact with portal technology, raising questions about expectations of the involvement of lay caregivers (domain 4: the adopter system), organizational policies on proxy access (domain 5: the organization), privacy and security features (domain 2: the technology), and information governance (domain 6: the wider context). Similarly, organizational leadership and support (domain 5: the organization) for the development and implementation of portals can ensure inclusive and iterative portal design (domain 1: the technology), addressing not only usability and functionality issues but also the perceived value (domain 3: the value proposition) of the technology, as well as concerns about the impact of portals on health professional roles and identities (domain 4: the adopter system) and workload and workflow (domain 5: the organization).</p>
        <p>There are gaps in the literature pertinent to the consideration of the provision of patient portals among older people in acute care hospitals, including the lack of consideration of the diversity of older adults and their needs, the question of interoperability between systems (likely to be important where care involves multiple services), the involvement of lay caregivers and looking beyond short-term implementation to ways in which portal use can be sustained.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of Key Findings</title>
        <p>This scoping review provides an overview of the contextual factors that impact the implementation of patient portals through an exploration of the emerging literature on patient portal use and engagement in acute care hospitals and among older people. Patients with chronic disease or greater disease severity were found to engage more with portals; however, comorbidities associated with the aging process were identified as barriers to portal use (domain 1: the condition). Perceived benefits from the supply side supported the adoption of portals, such as the potential for lower hospital costs, as did benefits from the demand side, such as engagement in care or self-management (domain 3: value proposition). Training for patients and staff should address technology literacy, the use of portal features, capacity-related concerns (integration of portals into workflows), and perceived value among health care professionals (domain 2: the technology). Older patients may lack help or support to access a portal; however, expectations of the involvement of lay caregivers in the adoption of patient portals were not reported (domain 4: the adopter system). Organizational leadership facilitates portal adoption, such as working with developers on portal design, developing policies for user training, and integrating portals into clinical workflows (domain 5: the organization). The development of national and international information exchange (ie, interoperability) and other standards (eg, security) was as a facilitator of portal implementation within the wider context (domain 6: the wider context). The reviews did not report on the long-term adaptability or sustainability of patient portals or organizational resilience. There were concerns that most portals are implemented within a single organization and that implementation across organizational contexts or in fragmented care delivery contexts would be challenging. This is important for the care of older people (domain 7: embedding and sustaining).</p>
      </sec>
      <sec>
        <title>Older People and Inequalities</title>
        <p>The diversity of older adults and their patient portal needs are not well understood. Older patients are more likely to experience chronic disease or greater severity of disease, and patients with chronic illness and greater severity of disease were found to engage more with portals owing to the perceived benefits of self-management, empowerment, and enhanced patient care. However, comorbidities related to age, such as vision and hearing loss, decreased dexterity and mobility, and declining cognitive function impede portal use. Variability in portal use and engagement among older people will, in part, be linked to the reasons for variability in internet use. Low income is the largest impediment to internet use among older people, followed by being aged &gt;75 years, living alone, mobility, and memory or concentration problems [<xref ref-type="bibr" rid="ref29">29</xref>]. This scoping review found that lower socioeconomic status, increasing age, male sex, and non-White ethnicity were factors associated with low adoption. People of lower socioeconomic status, older people, and people with mobility and memory or concentration problems are regular users of acute care services, making it an ideal setting to address these inequalities in patient portal access and engagement. Training programs and other engagement activities must directly target these inequalities to prevent any unintended exacerbation of the gray digital divide caused by the introduction or widespread use of a patient portal.</p>
      </sec>
      <sec>
        <title>Adopter System</title>
        <p>An important gap in the literature identified by this review was the lack of consideration of the involvement of the wider care network or lay caregivers in the adoption of patient portals. Many impediments to internet use among older people are linked to the increased likelihood of receiving care, for example, older age, mobility, and memory or concentration problems [<xref ref-type="bibr" rid="ref29">29</xref>]. Older people are found to value proxy access to patient portals [<xref ref-type="bibr" rid="ref30">30</xref>], with motivators including help to manage care, in the event of an emergency and lack of technology experience [<xref ref-type="bibr" rid="ref31">31</xref>]. However, older patients express concerns when portals contain access to stigmatized conditions and financial commitments [<xref ref-type="bibr" rid="ref32">32</xref>]. A review of 20 US health systems found that half of them had proxy access functionality, although only a few allowed the patient to specify role-based privileges [<xref ref-type="bibr" rid="ref33">33</xref>]. The provision of separate proxy access should be accompanied by the provision of more control for patients over the information they wish to share [<xref ref-type="bibr" rid="ref34">34</xref>]. This review found that organizational policies such as universal access; security protocols, including proxy access; adherence audits; and data availability and timing will facilitate portal development and implementation. To further aid the organizational readiness for technology-supported change, wider contextual factors must be considered at the planning stage in the form of policy shifts and patient developer specifications regarding the facility for internal and external information exchange. There is a need to engage with new ways of managing and talking about people’s data, which may require a different skill set, that is, different stakeholders round the table.</p>
      </sec>
      <sec>
        <title>Technology Supply Model</title>
        <p>None of the included studies addressed the procurement process for patient portals. In the United Kingdom, there are a handful of providers that offer patient portals to acute care hospitals, such as Epic and Cerner. Patient portals differ in the extent to which they provide an off-the-shelf product or a tailored product with features that can be switched on or off depending on organizational readiness and capacity to facilitate them, such as patient-clinician communication. This review found that decentralized architectures were more compatible with local needs and implemented more quickly but were associated with higher costs [<xref ref-type="bibr" rid="ref28">28</xref>]. Furthermore, there is no information on the level of support provided by the technology suppliers for the use of their products. This is anticipated to be a major organizational level barrier to implementation, which needs to be promptly addressed to facilitate the scale-up of portal use in acute care hospitals across the United Kingdom. Portals that can integrate into preexisting systems or offer data sharing and exchange were identified as facilitators [<xref ref-type="bibr" rid="ref20">20</xref>]. Interoperability of health and care systems and other community services, such as the police and social services, is placed high on the NHS agenda [<xref ref-type="bibr" rid="ref5">5</xref>], but although organizations may desire data sharing among themselves, the loss of control over shared data may serve as a barrier to portal adoption and highlights the complexity of this approach.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>This scoping review used a comprehensive set of search terms to identify literature from electronic databases and followed robust procedures for citation and full-text screening in duplicate. Study overlap is a recognized limitation of reviews of reviews, where the primary studies may be reported in &gt;1 systematic review and hence findings are overemphasized. This review included 156 primary studies and 50 reviews. We found that 19 (9.2%) of these 206 studies appeared in &gt;1 review, indicating that study overlap was minimal, although we did not track overlap in the reference lists of all the included reviews. The NASSS framework provides a semantic structure by which to explore multilevel contextual factors impacting the implementation of digital health interventions. NASSS has largely been used to predict and evaluate implementation programs, but more recently, the framework has been used to synthesize review findings [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>].</p>
        <p>The number of reviews that focused exclusively on acute care hospitals (3/10, 30%) and older people (2/10, 20%) was low, which led to a broader scope of the extensive literature, primarily conducted in family practice and other patient groups, to capture learning and potential generalizability of the findings across settings and patients. In broadening the scope of the review, there were similarities with the umbrella review conducted by Antonio et al [<xref ref-type="bibr" rid="ref14">14</xref>], who used a similar search strategy and a knowledge translation tool to present their findings. Our review was designed and our searches were conducted before the publication of the review conducted by Antonio et al [<xref ref-type="bibr" rid="ref14">14</xref>]. We believe these similarities reinforce our robust approach to reviewing and synthesizing the literature, particularly as our design aimed to scope and map the literature rather than to systematically review it. The key differences between the reviews include our focus on older people and acute care hospitals; our review design aimed to scope rather than systematically review and appraise the literature; and our application of the NASSS framework. The NASSS has been referenced in &gt;70 JMIR published studies since its publication in 2017, enabling easy comparison with the wider literature.</p>
        <p>Papers were selected in accordance with our definition of a patient portal, and we were guided by the authors’ description of a patient portal. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> shows the definition of patient portals in each of the included studies. The use of the NASSS framework is concerned with the complexity of the use of portals; therefore, all data were considered according to the framework to produce a “big picture” aggregation of what is known about the implementation of patient portals. The included reviews were limited to those published in English; however, we did not exclude reviews that included non-English studies.</p>
      </sec>
      <sec>
        <title>Recommendations for Research</title>
        <p>There is substantial literature on the contextual factors impacting patient portal use, with approximately 200 studies identified by the included reviews. However, there are few studies that evaluated interventions to address disparities in the use of patient portals [<xref ref-type="bibr" rid="ref15">15</xref>]. As highlighted in a systematic review on the implementation of complex interventions in family practice [<xref ref-type="bibr" rid="ref37">37</xref>], implementation studies exploring contextual factors tend to focus on surveys and qualitative studies, which are valuable in providing individual stakeholder perspectives but need triangulation with other methods. Observation and document analysis should accompany interviews to capture a more complete picture of the contextual factors at play, in particular, the wider context. As with any study exploring or evaluating the determinants of implementing a complex intervention, the features and functionality of the portal should be described in detail using established guidance [<xref ref-type="bibr" rid="ref38">38</xref>] to enable reflection on the transferability of the findings to other settings. Finally, where interviews are used to explore the determinants of implementation among patients and staff, portal use data could be used to prompt further examination of use and sustained use.</p>
      </sec>
      <sec>
        <title>Recommendations for Practice</title>
        <p>This review provides implications for portal adoption and implementation that can inform current practice. This review found that cost, interoperability, trialability, and adaptability were all facilitators of portal adoption. Among hospitals in England deciding which portal product to adopt, GDE trusts play an important role in sharing detailed journeys through a digital technology via GDE blueprints, which are intended to promote scale-up, spread, and sustainability. To maximize the impact of GDE blueprints, they must be reported in an honest and transparent manner, with details on the challenges as well as the benefits of portals’ adoption, engagement, and sustained use. Descriptions of portal implementation must clearly delineate implementation strategies, such as detailed information on training for staff and patients (ie, content, frequency, and format) and communication strategies for the technical, interpersonal, and workflow aspects of patient portals. NHS Digital has created a Personal Health Records adoption toolkit, which offers generic support to organizations looking to implement a patient portal [<xref ref-type="bibr" rid="ref39">39</xref>]. Furthermore, GDE trusts act as buddy sites to support other trusts, known as “Fast Followers,” for example, by sharing software, IT teams, standard processes, and could possibly assist with the selection and implementation of a patient portal; this approach is a powerful knowledge mobilization strategy enabling successful models to be scaled-up across the NHS [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This scoping review found that contextual factors influencing patient portal implementation tended to cluster in specific domains: (1) the condition, (2) the technology, and (3) the value proposition. Certain aspects within these domains received more coverage than others, such as sociocultural factors and comorbidities, the usability and functionality aspects of the technology, and the demand-side value. There are gaps in the literature pertinent to the consideration of the provision of patient portals for older people in acute care hospitals, including the lack of consideration of the diversity of older adults and their needs, the question of interoperability between systems (likely to be important where care involves multiple services), the involvement of lay caregivers, and looking beyond short-term implementation to ways in which portal use can be sustained. There is substantial literature on the contextual factors impacting patient portal use. Future research should focus on evaluating strategies that address disparities in use and promote engagement with patient portals among older people in acute care settings.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Characteristics of included reviews.</p>
        <media xlink:href="aging_v6i1e31812_app1.docx" xlink:title="DOCX File , 32 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">GDE</term>
          <def>
            <p>Global Digital Exemplar</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">NASSS</term>
          <def>
            <p>Non-adoption, Abandonment, Scale-up, Spread, and Sustainability</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">PRISMA-ScR</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses Extension for Scoping Reviews</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The research was funded by UEA Health and Social Care Partners (UEAHSCP). This is a summary of the research supported by the National Institute for Health Research (NIHR) Applied Research Collaboration East of England. JL (NIHR Knowledge Mobilisation Research Fellow KMRF-2017-06-ST2-006) was funded by the NIHR for this research project. The views expressed in this publication are those of the authors and not necessarily those of the NIHR, the National Health Service, or the UK Department of Health and Social Care. FS is the deputy lead for the Innovation and Implementation Science theme at the Applied Research Collaboration North Thames.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>HJ is a member of the digital management team at a Global Digital Exemplar National Health Service trust and has management responsibility for the implementation of a patient portal (Oracle Cerner HealtheLife). She has presented at Cerner conferences and received travel and hospitality reimbursement from Cerner.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Griffin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Skinner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Thornhill</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Weinberger</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Patient Portals: who uses them? What features do they use? And do they reduce hospital readmissions?</article-title>
          <source>Appl Clin Inform</source>
          <year>2016</year>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>489</fpage>
          <lpage>501</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27437056"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2016-01-RA-0003</pub-id>
          <pub-id pub-id-type="medline">27437056</pub-id>
          <pub-id pub-id-type="pmcid">PMC4941855</pub-id>
        </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>Ricciardi</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mostashari</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Daniel</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Siminerio</surname>
              <given-names>EP</given-names>
            </name>
          </person-group>
          <article-title>A national action plan to support consumer engagement via e-health</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2013</year>
          <month>02</month>
          <volume>32</volume>
          <issue>2</issue>
          <fpage>376</fpage>
          <lpage>84</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2012.1216</pub-id>
          <pub-id pub-id-type="medline">23381531</pub-id>
          <pub-id pub-id-type="pii">32/2/376</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bradley</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Lawrence</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Carder</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Using primary care data for health research in England - an overview</article-title>
          <source>Future Healthc J</source>
          <year>2018</year>
          <month>10</month>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>207</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31098568"/>
          </comment>
          <pub-id pub-id-type="doi">10.7861/futurehosp.5-3-207</pub-id>
          <pub-id pub-id-type="medline">31098568</pub-id>
          <pub-id pub-id-type="pii">futurehealth</pub-id>
          <pub-id pub-id-type="pmcid">PMC6502602</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>Global digital exemplars</article-title>
          <source>NHS England</source>
          <access-date>2021-06-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.england.nhs.uk/digitaltechnology/connecteddigitalsystems/exemplars/">https://www.england.nhs.uk/digitaltechnology/connecteddigitalsystems/exemplars/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>The future of healthcare: our vision for digital, data and technology in health and care</article-title>
          <source>Department of Health and Social Care</source>
          <year>2018</year>
          <month>10</month>
          <day>17</day>
          <access-date>2021-04-21</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/government/publications/the-future-of-healthcare-our-vision-for-digital-data-and-technology-in-health-and-care/the-future-of-healthcare-our-vision-for-digital-data-and-technology-in-health-and-care">https://www.gov.uk/government/publications/the-future-of-healthcare-our-vision-for-digital-data-and-technology-in-health-and-care/the-future-of-healthcare-our-vision-for-digital-data-and-technology-in-health-and-care</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>Personal health record (PHR) - landscape review</article-title>
          <source>Royal College of Physicians</source>
          <year>2016</year>
          <access-date>2020-10-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rcplondon.ac.uk/projects/outputs/personal-health-record-phr-landscape-review">https://www.rcplondon.ac.uk/projects/outputs/personal-health-record-phr-landscape-review</ext-link>
          </comment>
        </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>Irizarry</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>DeVito Dabbs</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Curran</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Patient portals and patient engagement: a state of the science review</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>06</month>
          <day>23</day>
          <volume>17</volume>
          <issue>6</issue>
          <fpage>e148</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2015/6/e148/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4255</pub-id>
          <pub-id pub-id-type="medline">26104044</pub-id>
          <pub-id pub-id-type="pii">v17i6e148</pub-id>
          <pub-id pub-id-type="pmcid">PMC4526960</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Emani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Karson</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Lipsitz</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>LaRocca</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Suric</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Wald</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Wheeler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>DH</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Who adopts a patient portal?: an application of the diffusion of innovation model</article-title>
          <source>J Innov Health Inform</source>
          <year>2018</year>
          <month>10</month>
          <day>25</day>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>149</fpage>
          <lpage>57</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://informatics.bmj.com/lookup/pmidlookup?view=long&amp;pmid=30398458"/>
          </comment>
          <pub-id pub-id-type="doi">10.14236/jhi.v25i3.991</pub-id>
          <pub-id pub-id-type="medline">30398458</pub-id>
        </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>Kingston</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Knapp</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jagger</surname>
              <given-names>C</given-names>
            </name>
            <collab>MODEM project</collab>
          </person-group>
          <article-title>Projections of multi-morbidity in the older population in England to 2035: estimates from the Population Ageing and Care Simulation (PACSim) model</article-title>
          <source>Age Ageing</source>
          <year>2018</year>
          <month>05</month>
          <day>01</day>
          <volume>47</volume>
          <issue>3</issue>
          <fpage>374</fpage>
          <lpage>80</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29370339"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/ageing/afx201</pub-id>
          <pub-id pub-id-type="medline">29370339</pub-id>
          <pub-id pub-id-type="pii">4815738</pub-id>
          <pub-id pub-id-type="pmcid">PMC5920286</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>Chinnadurai</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ogedengbe</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Money-Coomes</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Abdurrahman</surname>
              <given-names>AZ</given-names>
            </name>
            <name name-style="western">
              <surname>Mohammed</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kalra</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Rothwell</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Pradhan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Older age and frailty are the chief predictors of mortality in COVID-19 patients admitted to an acute medical unit in a secondary care setting- a cohort study</article-title>
          <source>BMC Geriatr</source>
          <year>2020</year>
          <month>10</month>
          <day>16</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>409</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcgeriatr.biomedcentral.com/articles/10.1186/s12877-020-01803-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12877-020-01803-5</pub-id>
          <pub-id pub-id-type="medline">33066750</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12877-020-01803-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7563906</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>Irizarry</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shoemake</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nilsen</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Czaja</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Beach</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>DeVito Dabbs</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Patient portals as a tool for health care engagement: a mixed-method study of older adults with varying levels of health literacy and prior patient portal use</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>03</month>
          <day>30</day>
          <volume>19</volume>
          <issue>3</issue>
          <fpage>e99</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/3/e99/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7099</pub-id>
          <pub-id pub-id-type="medline">28360022</pub-id>
          <pub-id pub-id-type="pii">v19i3e99</pub-id>
          <pub-id pub-id-type="pmcid">PMC5391436</pub-id>
        </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>Gordon</surname>
              <given-names>NP</given-names>
            </name>
            <name name-style="western">
              <surname>Hornbrook</surname>
              <given-names>MC</given-names>
            </name>
          </person-group>
          <article-title>Differences in access to and preferences for using patient portals and other ehealth technologies based on race, ethnicity, and age: a database and survey study of seniors in a large health plan</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>03</month>
          <day>04</day>
          <volume>18</volume>
          <issue>3</issue>
          <fpage>e50</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2016/3/e50/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.5105</pub-id>
          <pub-id pub-id-type="medline">26944212</pub-id>
          <pub-id pub-id-type="pii">v18i3e50</pub-id>
          <pub-id pub-id-type="pmcid">PMC4799429</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nahm</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sagherian</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Use of patient portals in older adults: a comparison of three samples</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2016</year>
          <volume>225</volume>
          <fpage>354</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">27332221</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Antonio</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Petrovskaya</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>The state of evidence in patient portals: umbrella review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>11</month>
          <day>11</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>e23851</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/11/e23851/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23851</pub-id>
          <pub-id pub-id-type="medline">33174851</pub-id>
          <pub-id pub-id-type="pii">v22i11e23851</pub-id>
          <pub-id pub-id-type="pmcid">PMC7688386</pub-id>
        </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>Grossman</surname>
              <given-names>LV</given-names>
            </name>
            <name name-style="western">
              <surname>Masterson Creber</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Benda</surname>
              <given-names>NC</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Ancker</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>Interventions to increase patient portal use in vulnerable populations: a systematic review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <month>08</month>
          <day>01</day>
          <volume>26</volume>
          <issue>8-9</issue>
          <fpage>855</fpage>
          <lpage>70</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30958532"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz023</pub-id>
          <pub-id pub-id-type="medline">30958532</pub-id>
          <pub-id pub-id-type="pii">5432090</pub-id>
          <pub-id pub-id-type="pmcid">PMC6696508</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>Powell</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Beidas</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Aarons</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>McMillen</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Proctor</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Mandell</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Methods to improve the selection and tailoring of implementation strategies</article-title>
          <source>J Behav Health Serv Res</source>
          <year>2017</year>
          <month>04</month>
          <volume>44</volume>
          <issue>2</issue>
          <fpage>177</fpage>
          <lpage>94</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26289563"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11414-015-9475-6</pub-id>
          <pub-id pub-id-type="medline">26289563</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11414-015-9475-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC4761530</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>Arksey</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>O'Malley</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Scoping studies: towards a methodological framework</article-title>
          <source>Int J Social Res Methodol</source>
          <year>2005</year>
          <month>02</month>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>19</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1080/1364557032000119616</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Lillie</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Zarin</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Colquhoun</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Levac</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Horsley</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Weeks</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hempel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McGowan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hartling</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Aldcroft</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Garritty</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lewin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Macdonald</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Langlois</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Soares-Weiser</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Moriarty</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Clifford</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tunçalp</surname>
              <given-names>Ö</given-names>
            </name>
            <name name-style="western">
              <surname>Straus</surname>
              <given-names>SE</given-names>
            </name>
          </person-group>
          <article-title>PRISMA extension for scoping reviews (PRISMA-ScR): checklist and explanation</article-title>
          <source>Ann Intern Med</source>
          <year>2018</year>
          <month>10</month>
          <day>02</day>
          <volume>169</volume>
          <issue>7</issue>
          <fpage>467</fpage>
          <lpage>73</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/abs/10.7326/M18-0850?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M18-0850</pub-id>
          <pub-id pub-id-type="medline">30178033</pub-id>
          <pub-id pub-id-type="pii">2700389</pub-id>
        </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>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="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Coller</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hoonakker</surname>
              <given-names>PL</given-names>
            </name>
          </person-group>
          <article-title>Inpatient portals for hospitalized patients and caregivers: a systematic review</article-title>
          <source>J Hosp Med</source>
          <year>2018</year>
          <month>06</month>
          <day>01</day>
          <volume>13</volume>
          <issue>6</issue>
          <fpage>405</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29261819"/>
          </comment>
          <pub-id pub-id-type="doi">10.12788/jhm.2894</pub-id>
          <pub-id pub-id-type="medline">29261819</pub-id>
          <pub-id pub-id-type="pmcid">PMC6136247</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>Sakaguchi-Tang</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Bosold</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>YK</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Patient portal use and experience among older adults: systematic review</article-title>
          <source>JMIR Med Inform</source>
          <year>2017</year>
          <month>10</month>
          <day>16</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e38</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2017/4/e38/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.8092</pub-id>
          <pub-id pub-id-type="medline">29038093</pub-id>
          <pub-id pub-id-type="pii">v5i4e38</pub-id>
          <pub-id pub-id-type="pmcid">PMC5662789</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>Kneale</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Demiris</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Lack of diversity in personal health record evaluations with older adult participants: a systematic review of literature</article-title>
          <source>J Innov Health Inform</source>
          <year>2017</year>
          <month>01</month>
          <day>15</day>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>881</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://informatics.bmj.com/lookup/pmidlookup?view=long&amp;pmid=28346131"/>
          </comment>
          <pub-id pub-id-type="doi">10.14236/jhi.v23i4.881</pub-id>
          <pub-id pub-id-type="medline">28346131</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>D'Costa</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>IL</given-names>
            </name>
            <name name-style="western">
              <surname>Fritz</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of patient access to medical records in the acute setting: practicalities, perspectives and ethical consequences</article-title>
          <source>BMC Med Ethics</source>
          <year>2020</year>
          <month>03</month>
          <day>02</day>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>18</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedethics.biomedcentral.com/articles/10.1186/s12910-020-0459-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12910-020-0459-6</pub-id>
          <pub-id pub-id-type="medline">32122332</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12910-020-0459-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7053049</pub-id>
        </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>Jilka</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Callahan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sevdalis</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mayer</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>"Nothing about me without me": an interpretative review of patient accessible electronic health records</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>06</month>
          <day>29</day>
          <volume>17</volume>
          <issue>6</issue>
          <fpage>e161</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2015/6/e161/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4446</pub-id>
          <pub-id pub-id-type="medline">26123476</pub-id>
          <pub-id pub-id-type="pii">v17i6e161</pub-id>
          <pub-id pub-id-type="pmcid">PMC4526966</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Mens</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Duijm</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Nienhuis</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>de Keizer</surname>
              <given-names>NF</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Determinants and outcomes of patient access to medical records: systematic review of systematic reviews</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>09</month>
          <volume>129</volume>
          <fpage>226</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.05.014</pub-id>
          <pub-id pub-id-type="medline">31445260</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(19)30265-5</pub-id>
        </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>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>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://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="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dendere</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Slade</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Burton-Jones</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Staib</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Janda</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Patient portals facilitating engagement with inpatient electronic medical records: a systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>04</month>
          <day>11</day>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>e12779</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/4/e12779/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12779</pub-id>
          <pub-id pub-id-type="medline">30973347</pub-id>
          <pub-id pub-id-type="pii">v21i4e12779</pub-id>
          <pub-id pub-id-type="pmcid">PMC6482406</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aslani</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Samadbeik</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of the attributes of electronic personal health records for patients with multiple sclerosis</article-title>
          <source>Health Technol</source>
          <year>2019</year>
          <month>12</month>
          <day>09</day>
          <volume>10</volume>
          <issue>3</issue>
          <fpage>587</fpage>
          <lpage>99</lpage>
          <pub-id pub-id-type="doi">10.1007/s12553-019-00387-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davidson</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Digital inclusion evidence review 2018</article-title>
          <source>Age UK</source>
          <year>2018</year>
          <month>11</month>
          <access-date>2021-04-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ageuk.org.uk/globalassets/age-uk/documents/reports-and-publications/age_uk_digital_inclusion_evidence_review_2018.pdf">https://www.ageuk.org.uk/globalassets/age-uk/documents/reports-and-publications/age_uk_digital_inclusion_evidence_review_2018.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zulman</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Nazi</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Turvey</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>TH</given-names>
            </name>
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>An</surname>
              <given-names>LC</given-names>
            </name>
          </person-group>
          <article-title>Patient interest in sharing personal health record information: a web-based survey</article-title>
          <source>Ann Intern Med</source>
          <year>2011</year>
          <month>12</month>
          <day>20</day>
          <volume>155</volume>
          <issue>12</issue>
          <fpage>805</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/abs/10.7326/0003-4819-155-12-201112200-00002?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/0003-4819-155-12-201112200-00002</pub-id>
          <pub-id pub-id-type="medline">22184687</pub-id>
          <pub-id pub-id-type="pii">155/12/805</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wolff</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Berger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Stametz</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Yule</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Darer</surname>
              <given-names>JD</given-names>
            </name>
          </person-group>
          <article-title>Patients, care partners, and shared access to the patient portal: online practices at an integrated health system</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>11</month>
          <volume>23</volume>
          <issue>6</issue>
          <fpage>1150</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw025</pub-id>
          <pub-id pub-id-type="medline">27026614</pub-id>
          <pub-id pub-id-type="pii">ocw025</pub-id>
        </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>Latulipe</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Quandt</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Melius</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Bertoni</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Arcury</surname>
              <given-names>TA</given-names>
            </name>
          </person-group>
          <article-title>Insights into older adult patient concerns around the caregiver proxy portal use: qualitative interview study</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>11</month>
          <day>02</day>
          <volume>20</volume>
          <issue>11</issue>
          <fpage>e10524</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/11/e10524/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10524</pub-id>
          <pub-id pub-id-type="medline">30389654</pub-id>
          <pub-id pub-id-type="pii">v20i11e10524</pub-id>
          <pub-id pub-id-type="pmcid">PMC6240158</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wolff</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>VS</given-names>
            </name>
            <name name-style="western">
              <surname>Mintz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stametz</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Griffin</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>An environmental scan of shared access to patient portals</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>04</month>
          <day>01</day>
          <volume>25</volume>
          <issue>4</issue>
          <fpage>408</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29025034"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocx088</pub-id>
          <pub-id pub-id-type="medline">29025034</pub-id>
          <pub-id pub-id-type="pii">4093936</pub-id>
          <pub-id pub-id-type="pmcid">PMC6658842</pub-id>
        </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>Sarkar</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Care partners and online patient portals</article-title>
          <source>JAMA</source>
          <year>2014</year>
          <volume>311</volume>
          <issue>4</issue>
          <fpage>357</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2013.285825</pub-id>
          <pub-id pub-id-type="medline">24394945</pub-id>
          <pub-id pub-id-type="pii">1810285</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>James</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>SE</given-names>
            </name>
          </person-group>
          <article-title>Spread, scale-up, and sustainability of video consulting in health care: systematic review and synthesis guided by the NASSS framework</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>01</month>
          <day>26</day>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>e23775</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/1/e23775/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23775</pub-id>
          <pub-id pub-id-type="medline">33434141</pub-id>
          <pub-id pub-id-type="pii">v23i1e23775</pub-id>
          <pub-id pub-id-type="pmcid">PMC7837451</pub-id>
        </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>Bastoni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wrede</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gaggioli</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Braakman-Jansen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Factors influencing implementation of eHealth technologies to support informal dementia care: umbrella review</article-title>
          <source>JMIR Aging</source>
          <year>2021</year>
          <month>10</month>
          <day>08</day>
          <volume>4</volume>
          <issue>4</issue>
          <fpage>e30841</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aging.jmir.org/2021/4/e30841/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/30841</pub-id>
          <pub-id pub-id-type="medline">34623314</pub-id>
          <pub-id pub-id-type="pii">v4i4e30841</pub-id>
          <pub-id pub-id-type="pmcid">PMC8538023</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Stevenson</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>BN</given-names>
            </name>
            <name name-style="western">
              <surname>Dziedzic</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Treweek</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Eldridge</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Everitt</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kennedy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Qureshi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Peacock</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Murray</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Achieving change in primary care--causes of the evidence to practice gap: systematic reviews of reviews</article-title>
          <source>Implement Sci</source>
          <year>2016</year>
          <month>03</month>
          <day>22</day>
          <volume>11</volume>
          <fpage>40</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/s13012-016-0396-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13012-016-0396-4</pub-id>
          <pub-id pub-id-type="medline">27001107</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13012-016-0396-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC4802575</pub-id>
        </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>Hoffmann</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>PP</given-names>
            </name>
            <name name-style="western">
              <surname>Boutron</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Milne</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Perera</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Barbour</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Macdonald</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Johnston</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lamb</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Dixon-Woods</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>McCulloch</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Michie</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Better reporting of interventions: template for intervention description and replication (TIDieR) checklist and guide</article-title>
          <source>BMJ</source>
          <year>2014</year>
          <month>03</month>
          <day>07</day>
          <volume>348</volume>
          <fpage>g1687</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://core.ac.uk/reader/19913708?utm_source=linkout"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.g1687</pub-id>
          <pub-id pub-id-type="medline">24609605</pub-id>
          <pub-id pub-id-type="pii">bmj.g1687</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>Personal Health Records adoption toolkit</article-title>
          <source>NHS Digital</source>
          <access-date>2021-03-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital.nhs.uk/services/personal-health-records-adoption-service/personal-health-records-adoption-toolkit">https://digital.nhs.uk/services/personal-health-records-adoption-service/personal-health-records-adoption-toolkit</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
