<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="review-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v23i7e26236</article-id>
      <article-id pub-id-type="pmid">34287210</article-id>
      <article-id pub-id-type="doi">10.2196/26236</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>Functionalities and Issues in the Implementation of Personal Health Records: Systematic Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kukafka</surname>
            <given-names>Rita</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Davis</surname>
            <given-names>Selena</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mehdizadeh</surname>
            <given-names>Hamed</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Ndabu</surname>
            <given-names>Theophile</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Pang</surname>
            <given-names>Patrick Cheong-Iao</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Harahap</surname>
            <given-names>Nabila Clydea</given-names>
          </name>
          <degrees>SKom, MKom</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Faculty of Computer Science</institution>
            <institution>University of Indonesia</institution>
            <addr-line>Kampus UI Depok, Pondok Cina, Beji</addr-line>
            <addr-line>Depok, 16424</addr-line>
            <country>Indonesia</country>
            <phone>62 85716526799</phone>
            <email>nabila.clydea@ui.ac.id</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7420-0396</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Handayani</surname>
            <given-names>Putu Wuri</given-names>
          </name>
          <degrees>SKom, MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5341-3800</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Hidayanto</surname>
            <given-names>Achmad Nizar</given-names>
          </name>
          <degrees>SKom, MKom, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5793-9460</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Faculty of Computer Science</institution>
        <institution>University of Indonesia</institution>
        <addr-line>Depok</addr-line>
        <country>Indonesia</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Nabila Clydea Harahap <email>nabila.clydea@ui.ac.id</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>7</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>21</day>
        <month>7</month>
        <year>2021</year>
      </pub-date>
      <volume>23</volume>
      <issue>7</issue>
      <elocation-id>e26236</elocation-id>
      <history>
        <date date-type="received">
          <day>9</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>16</day>
          <month>1</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>7</day>
          <month>3</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>24</day>
          <month>5</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Nabila Clydea Harahap, Putu Wuri Handayani, Achmad Nizar Hidayanto. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 21.07.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2021/7/e26236" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Functionalities of personal health record (PHR) are evolving, and continued discussions about PHR functionalities need to be performed to keep it up-to-date. Technological issues such as nonfunctional requirements should also be discussed in the implementation of PHR.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study systematically reviewed the main functionalities and issues in implementing the PHR.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>This systematic review was conducted using Preferred Reporting Items for Systematic Reviews and Meta-analyses (PRISMA) guidelines. The search is performed using the online databases Scopus, ScienceDirect, IEEE, MEDLINE, CINAHL, and PubMed for English journal articles and conference proceedings published between 2015 and 2020.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 105 articles were selected in the review. Seven function categories were identified in this review, which is grouped into basic and advanced functions. Health records and administrative records were grouped into basic functions. Medication management, communication, appointment management, education, and self-health monitoring were grouped into advanced functions. The issues found in this study include interoperability, security and privacy, usability, data quality, and personalization.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>In addition to PHR basic and advanced functions, other supporting functionalities may also need to be developed based on the issues identified in this study. This paper provides an integrated PHR architectural model that describes the functional requirements and data sources of PHRs.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>personal health record</kwd>
        <kwd>systematic review</kwd>
        <kwd>functionalities</kwd>
        <kwd>issues</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>In health emergencies such as epidemics, natural disasters, or artificial disasters, access to reliable health information becomes crucial for the community [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. As of 2020, the COVID-19 pandemic throughout the world has led to an increasing need for electronic health records (EHRs) to provide reliable health information [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. According to the World Health Organization, the EHR that collects data from various health service providers will provide better patient care during a pandemic, such as preventing and detecting an outbreak [<xref ref-type="bibr" rid="ref5">5</xref>]. The EHR’s function will be more optimal if patients can share their health data with health care providers [<xref ref-type="bibr" rid="ref6">6</xref>]. Personal health records (PHRs) can help patients share their data with health care providers and provide useful information during health emergencies [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      <p>The EHR aims to collect health data managed by health care providers, while the PHR aims to collect health data entered by individuals [<xref ref-type="bibr" rid="ref1">1</xref>]. The PHR was developed with a patient-centered approach in the capture and storage of information [<xref ref-type="bibr" rid="ref7">7</xref>]. In its simplest form, a PHR is a stand-alone application that is not connected to other systems. Users can access their PHR using commercially available applications to record and analyze daily activities and habits to maintain a healthy lifestyle. In a more complex form, the PHR’s health information is connected to the EHR of the health care provider (tethered PHR) or to various health service data sources (integrated or interconnected PHR). A PHR integrated with an EHR, either through tethering or interconnectivity, provides far more significant benefits than a stand-alone PHR [<xref ref-type="bibr" rid="ref1">1</xref>].</p>
      <p>One of the important PHR research areas is PHR functionality [<xref ref-type="bibr" rid="ref8">8</xref>]. Previous studies have provided data types and functionalities of PHRs [<xref ref-type="bibr" rid="ref9">9</xref>] and a guide to evaluate PHR functionalities [<xref ref-type="bibr" rid="ref10">10</xref>]. Some studies reviewed PHRs used for chronic diseases, which include discussions about their functionalities [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. However, these studies focused only on PHRs in the United States and developed countries [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Moreover, previous studies have also discussed technological issues in implementing or using PHRs, such as data quality [<xref ref-type="bibr" rid="ref13">13</xref>], personalization [<xref ref-type="bibr" rid="ref14">14</xref>], privacy [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref15">15</xref>], and usability [<xref ref-type="bibr" rid="ref14">14</xref>]. These studies still have no clear explanations about how these issues can be included as requirements in implementing PHRs.</p>
      <p>Functions or features of PHRs are evolving [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], so continued discussions about PHR functionalities need to be held to keep the research up-to-date. In addition, technological issues as nonfunctional requirements [<xref ref-type="bibr" rid="ref16">16</xref>] in the design and development of a system must be discussed. Technological issues can be defined as constraints and qualities related to the technology used to perform the function [<xref ref-type="bibr" rid="ref17">17</xref>]. Thus, this paper aims to review the PHR studies focusing on the functionalities and technological issues in building the PHR system. This paper addresses the following research question: What are the main functionalities and issues in the implementation of PHRs? This study can provide PHR design or implementation recommendations to health care management, application developers, policymakers, or other related stakeholders.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>This systematic review was conducted using the Preferred Reporting Items for Systematic Reviews and Meta-analyses (PRISMA) guidelines [<xref ref-type="bibr" rid="ref18">18</xref>]. PRISMA is suitable for studies related to health care interventions, and it focuses on ways in which authors can ensure the transparent and complete reporting of systematic reviews [<xref ref-type="bibr" rid="ref19">19</xref>]. The PRISMA checklist for this study is provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
      <sec>
        <title>Search Strategy</title>
        <p>The search is conducted using the online databases Scopus, ScienceDirect, IEEE Xplore, MEDLINE, CINAHL, and PubMed. Terms or keywords used to search the articles: (“phr” OR “personal health record” OR “personal medical record” OR “personal health information” OR “personally controlled electronic health record” OR “pcehr” OR “patient portal”) AND (“functionality” OR “features” OR “issues” OR “implementation”). The search was conducted for journal articles and conference proceedings published between January 2015 and December 2020 to ensure that the data were current because the functions of PHRs are evolving.</p>
      </sec>
      <sec>
        <title>Eligibility Criteria</title>
        <p>The authors defined inclusion criteria as the review guidelines for study selection. The articles included for this study must have full text available and written in English, be original research articles, focus on discussing the electronic PHR platform, and discuss functionalities and/or issues in the implementation of PHRs.</p>
        <p>In this study, the PHRs discussed are all PHR types (stand-alone, tethered, and integrated) that provide access to health information or records to patients electronically. Therefore, papers with related terms such as patient health records or patient portals are also included in this review. The authors also reviewed PHRs at the design stage to include conceptual papers in this review.</p>
      </sec>
      <sec>
        <title>Study Selection</title>
        <p>The study selection consists of the following phases:</p>
        <list list-type="order">
          <list-item>
            <p>Keyword or search string was searched in each online database previously mentioned. Duplicated records were checked and removed.</p>
          </list-item>
          <list-item>
            <p>The title and abstract of identified articles were selected based on the eligibility criteria. Articles that did not meet inclusion criteria were eliminated.</p>
          </list-item>
          <list-item>
            <p>Articles that were not eliminated in the previous stage were read in full text to determine whether they should be included in the review based on the eligibility criteria. Reference lists of the included studies were also checked to identify additional relevant articles.</p>
          </list-item>
        </list>
        <p>The first author screened the titles and abstracts based on the eligibility criteria. The same author reviewed full-text versions of the articles that were not excluded from the previous screening. The first author extracted data from selected studies and the second author reviewed the extracted data. Disagreements between the two authors were resolved through discussion. If an agreement could not be made, the third author would determine the decision. We were unable to consistently evaluate the risk of bias due to the variety of methodologies within the studies.</p>
      </sec>
      <sec>
        <title>Data Items and Synthesis</title>
        <p>Data collection was performed manually using a data extraction form. Information extracted from each article consists of characteristics of selected articles, such as study location, PHR purpose, and methodology, and functionalities of PHRs and issues in PHR implementation</p>
        <p>Authors categorized functionalities of PHRs based on their purpose as defined in Bouayad et al [<xref ref-type="bibr" rid="ref9">9</xref>], Price et al [<xref ref-type="bibr" rid="ref12">12</xref>], and Genitsaridi et al [<xref ref-type="bibr" rid="ref10">10</xref>]. For each function category, the authors explained subfunctions or data elements that were implemented or recommended from the selected articles. Moreover, each function category was grouped based on basic and advanced functions defined by Detmer et al [<xref ref-type="bibr" rid="ref20">20</xref>]. Basic functionalities help people collect, organize, and store health information, while advanced functionalities enable patients to play a more active role in their health [<xref ref-type="bibr" rid="ref20">20</xref>]. The authors explained PHR implementation issues that are mentioned explicitly or implicitly from the selected articles.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Study Selection</title>
        <p>The database search results identified 2248 studies from 2015 to 2020. Next, duplicate records were removed, resulting in a total of 1511 studies; 124 studies were excluded after the title and abstract screening (articles that mentioned literature review and articles not related to PHRs, patient portals, or access to health records to patients were excluded at this stage). A total of 387 articles were assessed in full text, of which 297 were excluded because they did not meet the selection criteria. However, 15 additional studies were identified from reference lists checking, for a total of 105 studies included in this review (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Flow diagram for search results. IEEE: Institute of Electrical and Electronics Engineers; MEDLINE: Medical Literature Analysis and Retrieval System Online; CINAHL: Cumulative Index to Nursing and Allied Health Literature; PHR: personal health record.</p>
          </caption>
          <graphic xlink:href="jmir_v23i7e26236_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Study Characteristics</title>
        <p>The chosen articles showed that PHR research has mainly been done in developed countries such as the United States, Canada, and European countries compared to developing countries. This country classification was based on the United Nations World Economic Situation and Prospects 2020 [<xref ref-type="bibr" rid="ref21">21</xref>]. Countries involved in selected studies consist of developed countries such as the United States (42 studies), Canada (10 studies), Germany (8 studies), Australia (5 studies), Italy (4 studies), Netherlands (4 studies), United Kingdom (4 studies), South Korea (3 studies), European Union (2 studies), New Zealand (2 studies), Austria (1 study), Belgium (1 study), Norway (1 study), Portugal (1 study), and Taiwan (1 study) and developing countries such as Argentina (3 studies), China (3 studies), Iran (2 studies), Sri Lanka (2 studies), Brazil (1 study), Colombia (1 study), India (1 study), Malaysia (1 study), Romania (1 study), and Thailand (1 study; <xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <p>The purposes of PHRs (<xref ref-type="table" rid="table1">Table 1</xref>) in selected articles include general, not specific to the disease, health status, or population (48 studies); chronic diseases such as cancer, cardiovascular disease, and diabetes (31 studies); hospital patients such as inpatients and outpatients (10 studies), older adults (5 studies), women and child health (4 studies), mental health (4 studies), and other specific populations such as employees and foster youth (3 studies).</p>
        <p>The study methods (<xref ref-type="table" rid="table2">Table 2</xref>) used in selected studies include qualitative (41 studies), quantitative (33 studies), conceptual paper (16 studies), and mixed method (15 studies). A summary table of the characteristics of the included studies is provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Countries involved in personal health record study.</p>
          </caption>
          <graphic xlink:href="jmir_v23i7e26236_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Purposes of PHRs<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="600"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td>Category</td>
                <td>Description</td>
                <td>Number of studies</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>General</td>
                <td>PHR designated not specific to any diseases, health status, or population.</td>
                <td>48</td>
              </tr>
              <tr valign="top">
                <td>Chronic disease</td>
                <td>PHR for chronic diseases such as cancer, diabetes, or cardiovascular disease.</td>
                <td>31</td>
              </tr>
              <tr valign="top">
                <td>Hospital patients</td>
                <td>PHR for patients who have visited the hospital, such as inpatients and outpatients.</td>
                <td>10</td>
              </tr>
              <tr valign="top">
                <td>Older adults</td>
                <td>PHR for patients with the age of more than 50 years.</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>Women and child health</td>
                <td>PHR for women, pregnancy, and pediatric health.</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Mental health</td>
                <td>PHR for mental health diseases, such as bipolar disorder.</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Other populations</td>
                <td>PHR for other specific populations, such as employees and foster youth.</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Total</td>
                <td>—<sup>b</sup></td>
                <td>105</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>PHRs:patient health records.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Methods used in the studies.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="600"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td>Method</td>
                <td>Type of study</td>
                <td>Number of studies</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Qualitative</td>
                <td>Interview and focus group discussion</td>
                <td>41</td>
              </tr>
              <tr valign="top">
                <td>Quantitative</td>
                <td>Questionnaire, cohort study, and randomized clinical trial</td>
                <td>33</td>
              </tr>
              <tr valign="top">
                <td>Conceptual paper</td>
                <td>—<sup>a</sup></td>
                <td>16</td>
              </tr>
              <tr valign="top">
                <td>Mixed method</td>
                <td>—</td>
                <td>15</td>
              </tr>
              <tr valign="top">
                <td>Total</td>
                <td>—</td>
                <td>105</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Main Functionalities of PHR</title>
        <p>Basic functions identified in this study consist of the health record and administrative record. Advanced functions consist of medication management, communication, appointment management, education, and self-health monitoring (<xref ref-type="table" rid="table3">Table 3</xref>). A summary table of the data elements and subfunctions is provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Identified Functionalities in PHR<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="170"/>
            <col width="400"/>
            <col width="400"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Function</td>
                <td>Description</td>
                <td>References</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Basic function</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Health record</td>
                <td>Allows patients to view or access clinical documents from health providers’ EHR<sup>b</sup>.</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref71">71</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Administrative record</td>
                <td>Allows patients to manage personal information and view information related to health providers and insurance.</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref44">44</xref>-<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref72">72</xref>-<xref ref-type="bibr" rid="ref78">78</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Advanced function</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Medications management</td>
                <td>Allows patients to manage information related to medications and prescriptions.</td>
                <td>[<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref59">59</xref>-<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref68">68</xref>-<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref73">73</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref79">79</xref>-<xref ref-type="bibr" rid="ref85">85</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Communication</td>
                <td>Allows patients to interact and communicate with health care providers and others, such as support groups and families.</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref57">57</xref>, <xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref82">82</xref>-<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref86">86</xref>-<xref ref-type="bibr" rid="ref94">94</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Appointment management</td>
                <td>Allows patients to manage appointments with health care providers.</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref57">57</xref>, <xref ref-type="bibr" rid="ref59">59</xref>-<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref73">73</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref85">85</xref>-<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref94">94</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Education</td>
                <td>Allows patients to access health-related education resources.</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref95">95</xref>-<xref ref-type="bibr" rid="ref99">99</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Self-health monitoring</td>
                <td>Allows patients to manage their self-health data through clinical measures.</td>
                <td>[<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref93">93</xref>,<xref ref-type="bibr" rid="ref95">95</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref100">100</xref>-<xref ref-type="bibr" rid="ref105">105</xref>]</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>PHR: patient health record.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>EHR: electronic health record.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Basic Functions</title>
        <sec>
          <title>Health Record</title>
          <p>The health record function provides patients options to view clinical documents that can be retrieved from health providers’ EHR [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. This information can include problem lists [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref67">67</xref>-<xref ref-type="bibr" rid="ref71">71</xref>], allergies [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref39">39</xref>, <xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref67">67</xref>-<xref ref-type="bibr" rid="ref70">70</xref>], immunization [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref35">35</xref>, <xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref68">68</xref>-<xref ref-type="bibr" rid="ref71">71</xref>], laboratory and test results [<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="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>, <xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref42">42</xref>-<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref67">67</xref>-<xref ref-type="bibr" rid="ref71">71</xref>], diagnostic information [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref62">62</xref>], discharge information [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref63">63</xref>], and clinical notes [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. <xref rid="figure3" ref-type="fig">Figure 3</xref> shows an example of test results in PittPHR [<xref ref-type="bibr" rid="ref33">33</xref>].</p>
          <p>This function can also include information about medical history [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref68">68</xref>], family history [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref66">66</xref>], genetic history [<xref ref-type="bibr" rid="ref45">45</xref>], surgical history [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref68">68</xref>], social history [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref68">68</xref>]. Some studies suggested that this function also supports patients’ ability to print the record [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref36">36</xref>] and add comments or notes in health records [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref61">61</xref>].</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Test results menu in the health records module of PittPHR [<xref ref-type="bibr" rid="ref33">33</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Administrative Record</title>
          <p>This function enables the patient to manage information about demographics or personal information [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>] such as name [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref73">73</xref>], gender [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref72">72</xref>], birthdate [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref73">73</xref>], blood type [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref44">44</xref>], contact information [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>], and parents’ names [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. Patients can also change their information, such as change password, address, and email address [<xref ref-type="bibr" rid="ref22">22</xref>]. Patients can enter this information [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>] or retrieve it from a central patient registry, such as in Lifelong PHR [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
          <p>Patients can also view health professionals’ information, such as name of health worker [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref74">74</xref>], role [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>], educational background [<xref ref-type="bibr" rid="ref75">75</xref>], contact information [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>], specialty [<xref ref-type="bibr" rid="ref76">76</xref>], location [<xref ref-type="bibr" rid="ref76">76</xref>], and pictures [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref78">78</xref>]. Patients can also view hospital information, such as location, contact info, address, navigation [<xref ref-type="bibr" rid="ref70">70</xref>]. Patients can also view and pay bill [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref77">77</xref>] and get insurance-related information [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref66">66</xref>]. This data can be retrieved from the regional health care information system [<xref ref-type="bibr" rid="ref34">34</xref>]. <xref rid="figure4" ref-type="fig">Figure 4</xref> shows an example of the health care team information in the PHR app [<xref ref-type="bibr" rid="ref74">74</xref>].</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Health care team information menu [<xref ref-type="bibr" rid="ref74">74</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Advanced Functions</title>
        <sec>
          <title>Medication Management</title>
          <p>Health care providers publish prescriptions to the patient’s PHR, while pharmacists dispense the prescribed medication [<xref ref-type="bibr" rid="ref34">34</xref>]. This function provides information about the list of medications that patients are currently taking [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>, <xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>], medication name and dosage [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref80">80</xref>], and list of past medications [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref73">73</xref>,<xref ref-type="bibr" rid="ref81">81</xref>]. PHRs should also add information about the purpose or class of medications to give patients an understanding of the medication type [<xref ref-type="bibr" rid="ref74">74</xref>] and allow pharmacists to explore the data according to their common questions [<xref ref-type="bibr" rid="ref80">80</xref>].</p>
          <p>This function also allows patients to view list of prescribed medications [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref82">82</xref>,<xref ref-type="bibr" rid="ref83">83</xref>], prescribing physician [<xref ref-type="bibr" rid="ref79">79</xref>], refill prescription [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref55">55</xref>, <xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref84">84</xref>], order medications [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref71">71</xref>], deliver purchased medication [<xref ref-type="bibr" rid="ref79">79</xref>], as well as track the delivery of medication [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Some PHRs also provide medication schedulers and reminders of when to take medicines [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref85">85</xref>], drug or medicine reconciliation [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref83">83</xref>], and warning alerts of potential adverse interactions based on the medication and allergy list [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref73">73</xref>]. <xref rid="figure5" ref-type="fig">Figure 5</xref> shows an example of medication management in medication management in My Chart in My Hand [<xref ref-type="bibr" rid="ref85">85</xref>].</p>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Medication management in My Chart in My Hand [<xref ref-type="bibr" rid="ref85">85</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Communication</title>
          <p>The patient can send messages to the health care provider to inform them of health condition [<xref ref-type="bibr" rid="ref23">23</xref>], share doubts and worries [<xref ref-type="bibr" rid="ref86">86</xref>], receive medical advice [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref86">86</xref>], or send nonurgent messages [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]. The communication can be in the form of messaging [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref57">57</xref>, <xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref82">82</xref>-<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref86">86</xref>-<xref ref-type="bibr" rid="ref92">92</xref>] or text where patients can write questions (<xref rid="figure6" ref-type="fig">Figure 6</xref>) [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref80">80</xref>]. Some PHRs also enable patients to contact others in a similar situation [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref88">88</xref>], support groups [<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref87">87</xref>], family [<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref89">89</xref>], or customer support and billing departments [<xref ref-type="bibr" rid="ref22">22</xref>]. Some studies also suggested this function have the ability to maintain a record of past conversations [<xref ref-type="bibr" rid="ref36">36</xref>] and provide email or text notification when a health care provider leaves a message on the PHR [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref93">93</xref>,<xref ref-type="bibr" rid="ref94">94</xref>]. Moreover, some studies suggested tracking the status of a question [<xref ref-type="bibr" rid="ref80">80</xref>], message multiple providers at the same time [<xref ref-type="bibr" rid="ref24">24</xref>], and import selected emails and interactions on the social network to PHRs [<xref ref-type="bibr" rid="ref86">86</xref>].</p>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>Comments or questions page in myNYP.org [<xref ref-type="bibr" rid="ref80">80</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Appointment Management</title>
          <p>Some PHRs may allow a patient to request or schedule appointments (<xref rid="figure7" ref-type="fig">Figure 7</xref>) [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref40">40</xref>, <xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref48">48</xref>-<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref92">92</xref>], while others only allow patients to view their past and upcoming appointments [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref73">73</xref>,<xref ref-type="bibr" rid="ref77">77</xref>]. The types of appointments can include patient-doctor visit consultation services and other health services such as specialist encounters, sample takings, hospital admissions, result withdrawal [<xref ref-type="bibr" rid="ref86">86</xref>], therapies, and online consultation [<xref ref-type="bibr" rid="ref23">23</xref>]. Moreover, some studies suggested that PHRs include reminders or notifications for upcoming appointments [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref94">94</xref>]. This reminder can be in the form of email notifications about the date and time of the appointment [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref81">81</xref>]. PHRs can also add a calendar to keep track of future appointments [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref78">78</xref>].</p>
          <fig id="figure7" position="float">
            <label>Figure 7</label>
            <caption>
              <p>Appointment scheduling in mPHR [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Education</title>
          <p>The education function can include resources from trusted websites [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref90">90</xref>], health information libraries [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref30">30</xref>], video resources [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref95">95</xref>], or government supported information [<xref ref-type="bibr" rid="ref95">95</xref>]. The information can consist of lifestyle management [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref71">71</xref>], first-aid information [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref70">70</xref>], discharge instructions [<xref ref-type="bibr" rid="ref31">31</xref>], surgical procedure [<xref ref-type="bibr" rid="ref77">77</xref>], physical activities guidance [<xref ref-type="bibr" rid="ref96">96</xref>], or health-specific education such as pregnancy [<xref ref-type="bibr" rid="ref97">97</xref>,<xref ref-type="bibr" rid="ref98">98</xref>], mental health [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref61">61</xref>], or chronic diseases–related education [<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]. <xref rid="figure8" ref-type="fig">Figure 8</xref> shows an example of the education page in the Maternity Information Access Point [<xref ref-type="bibr" rid="ref97">97</xref>]. Health providers are responsible for providing clinical topics and resources for credible information [<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref99">99</xref>]. Moreover, PHRs should also have the ability to search for information using an intelligent search engine [<xref ref-type="bibr" rid="ref99">99</xref>].</p>
          <fig id="figure8" position="float">
            <label>Figure 8</label>
            <caption>
              <p>Education resources in Maternity Information Access Point [<xref ref-type="bibr" rid="ref97">97</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Self-Health Monitoring</title>
          <p>Patients can manage their own health related to nutrition and diet information such as weight [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref100">100</xref>-<xref ref-type="bibr" rid="ref102">102</xref>], height [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref66">66</xref>], physical activity or exercise [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref101">101</xref>], and food and meals [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref98">98</xref>]. Patients can also manage their vital sign data such as temperature [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref44">44</xref>], blood pressure [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref101">101</xref>,<xref ref-type="bibr" rid="ref103">103</xref>], blood glucose [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref103">103</xref>], and heart rate [<xref ref-type="bibr" rid="ref90">90</xref>]. Patients can also monitor other self-health data such as sleep [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref95">95</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref101">101</xref>], period [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref100">100</xref>], moods [<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref101">101</xref>], and stress [<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref100">100</xref>].</p>
          <p>These clinical measures enable calculation such as BMI [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref100">100</xref>], body fat percentage [<xref ref-type="bibr" rid="ref70">70</xref>], waist-to-height ratio [<xref ref-type="bibr" rid="ref70">70</xref>], calorie [<xref ref-type="bibr" rid="ref70">70</xref>], cholesterol level [<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref86">86</xref>], and glycemia [<xref ref-type="bibr" rid="ref86">86</xref>]. This information can also calculate disease risks such as cardiovascular disease risk and metabolic syndrome risk [<xref ref-type="bibr" rid="ref85">85</xref>]. The data in this function can be retrieved from home monitoring devices [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref104">104</xref>,<xref ref-type="bibr" rid="ref105">105</xref>] such as Bluetooth-enabled health monitors [<xref ref-type="bibr" rid="ref104">104</xref>], accelerometers [<xref ref-type="bibr" rid="ref105">105</xref>], blood pressure monitors [<xref ref-type="bibr" rid="ref58">58</xref>], blood glucose meters [<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref93">93</xref>], and pedometer [<xref ref-type="bibr" rid="ref72">72</xref>] and fitness tracker apps [<xref ref-type="bibr" rid="ref39">39</xref>].</p>
          <p>The monitoring of health data can be shown as a dashboard that visualizes data in graphs, charts, or diagrams [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref101">101</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref105">105</xref>]. Key performance indicators can be different for each patient, depending on their conditions. For example, in the MyHealthKeeper app, the clinician provided individual diet and physical activity targets for each patient during an outpatient visit (<xref rid="figure9" ref-type="fig">Figure 9</xref>) [<xref ref-type="bibr" rid="ref101">101</xref>]. This function can be integrated into a clinician’s EHR, and clinicians could review these data and provide feedback about the health-related lifestyle management of their patients [<xref ref-type="bibr" rid="ref101">101</xref>].</p>
          <fig id="figure9" position="float">
            <label>Figure 9</label>
            <caption>
              <p>MyHealthKeeper interface for patient’s lifestyle data [<xref ref-type="bibr" rid="ref101">101</xref>].</p>
            </caption>
            <graphic xlink:href="jmir_v23i7e26236_fig9.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Issues in Implementation of the PHR</title>
        <p>Some issues must be considered in implementing PHRs because these issues can define additional functionalities that can support the main functionalities in PHRs. The issues identified included interoperability, security and privacy, usability, data quality, and personalization (<xref ref-type="table" rid="table4">Table 4</xref>).</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Issues in implementation of the PHR<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="400"/>
            <col width="400"/>
            <thead>
              <tr valign="top">
                <td>Issues</td>
                <td>Description</td>
                <td>References</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Interoperability</td>
                <td>Ability of PHR to share or exchange data with other systems</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref61">61</xref>-<xref ref-type="bibr" rid="ref63">63</xref>, <xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref88">88</xref>-<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref104">104</xref>,<xref ref-type="bibr" rid="ref106">106</xref>-<xref ref-type="bibr" rid="ref112">112</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Security and privacy</td>
                <td>Safeguarding of data and personal information in PHR</td>
                <td>[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref60">60</xref>-<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref72">72</xref>-<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref83">83</xref>, <xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref97">97</xref>,<xref ref-type="bibr" rid="ref103">103</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref110">110</xref>,<xref ref-type="bibr" rid="ref112">112</xref>-<xref ref-type="bibr" rid="ref122">122</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Usability</td>
                <td>Whether users can use PHR effectively and efficiently</td>
                <td>[<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref74">74</xref>, <xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref92">92</xref>-<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref105">105</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref110">110</xref>,<xref ref-type="bibr" rid="ref117">117</xref>-<xref ref-type="bibr" rid="ref126">126</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Data quality</td>
                <td>Ensures consistency, completeness, accuracy, and timeliness of the PHR information</td>
                <td>[<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref91">91</xref>,<xref ref-type="bibr" rid="ref107">107</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref110">110</xref>-<xref ref-type="bibr" rid="ref113">113</xref>,<xref ref-type="bibr" rid="ref115">115</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Personalization</td>
                <td>Ability of PHR to be tailored and adapted to patient needs and preferences</td>
                <td>[<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref95">95</xref>,<xref ref-type="bibr" rid="ref99">99</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref117">117</xref>,<xref ref-type="bibr" rid="ref118">118</xref>,<xref ref-type="bibr" rid="ref123">123</xref>,<xref ref-type="bibr" rid="ref125">125</xref>]</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>PHR: personal health record.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <sec>
          <title>Interoperability</title>
          <p>An important issue raised in several studies is PHR compatibility with other systems [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref106">106</xref>]. Health service providers such as clinicians should input data from other systems into the PHR or vice versa, which was considered too time-consuming and unfeasible for daily practice [<xref ref-type="bibr" rid="ref100">100</xref>]. This problem can also be caused by health organizations adapting their formats to use health records and not allowing health information sharing in their PHR to other applications or organizations [<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref107">107</xref>]. As a result, a patient may have health records scattered in several applications [<xref ref-type="bibr" rid="ref107">107</xref>]. To provide more benefits and ensure its successful implementation, PHRs should realize interoperability among various data and systems [<xref ref-type="bibr" rid="ref106">106</xref>,<xref ref-type="bibr" rid="ref108">108</xref>]. PHRs should have the ability to share information with others [<xref ref-type="bibr" rid="ref88">88</xref>], such as health professionals [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref89">89</xref>].</p>
          <p>In the tethered or integrated PHR, patients may connect their PHR to the health care provider system [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref104">104</xref>]. With this integration, health information is automatically transferred to the PHR [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref109">109</xref>,<xref ref-type="bibr" rid="ref110">110</xref>]. This can reduce data entry load [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref96">96</xref>], improve data accuracy [<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref96">96</xref>], prevent medical errors [<xref ref-type="bibr" rid="ref38">38</xref>], reduce the health information recall [<xref ref-type="bibr" rid="ref35">35</xref>], and contribute to users’ better perceptions about the system’s usefulness [<xref ref-type="bibr" rid="ref111">111</xref>]. It is also suggested that PHRs be integrated into various health providers and not limited to one health provider [<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref102">102</xref>]. Patients may also have the ability to share information with trusted institutions and insurance bodies to speed up reimbursement procedures [<xref ref-type="bibr" rid="ref86">86</xref>] and access other family members’ records [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref102">102</xref>].</p>
          <p>It is necessary to create legislation to realize PHR interoperability [<xref ref-type="bibr" rid="ref106">106</xref>]. Health providers need to provide standard definitions for data exchange and cooperate with other providers [<xref ref-type="bibr" rid="ref63">63</xref>]. There are international standards or frameworks for interoperability, such as OpenEHR, Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR), and Integrating the Healthcare Enterprise and Continua Health Alliance specifications [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref107">107</xref>,<xref ref-type="bibr" rid="ref112">112</xref>]. OpenEHR describes the management and exchange of data in EHRs for developing PHRs using specific language [<xref ref-type="bibr" rid="ref68">68</xref>]. OpenEHR integrated with other standards in particular health data types, such as laboratory results [<xref ref-type="bibr" rid="ref107">107</xref>]. Similarly, HL7 FHIR enables the management of a single data entity, group of entities, or a record using well-known standard languages [<xref ref-type="bibr" rid="ref68">68</xref>]. FHIR application program interface allows any arbitrary system connected with another medical system already equipped with the FHIR application program interface [<xref ref-type="bibr" rid="ref72">72</xref>]. FHIR allows the patient portal to be interconnected but independent [<xref ref-type="bibr" rid="ref29">29</xref>]. Moreover, Integrating the Healthcare Enterprise specifies architectural approaches using international standards for the health data exchange and can fit the mobile platform’s resources. At the same time, Continua enables communication from personal health devices to EHRs and PHRs [<xref ref-type="bibr" rid="ref112">112</xref>].</p>
        </sec>
        <sec>
          <title>Security and Privacy</title>
          <p>PHRs contain personal and sensitive data [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref112">112</xref>-<xref ref-type="bibr" rid="ref114">114</xref>]. Some people have concerns about storing these data online [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref103">103</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref113">113</xref>,<xref ref-type="bibr" rid="ref115">115</xref>] and consent to use the system [<xref ref-type="bibr" rid="ref116">116</xref>]. They may have concerns about identity theft and unauthorized access in PHRs [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. Confidentiality and privacy of information in PHRs should be ensured through secured access to PHRs [<xref ref-type="bibr" rid="ref110">110</xref>].</p>
          <p>To ensure the security of information, PHRs should use a single sign-on mechanism [<xref ref-type="bibr" rid="ref70">70</xref>], user authentication [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref73">73</xref>,<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref117">117</xref>], authorization [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref112">112</xref>], identity verification [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref63">63</xref>], encryption [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref118">118</xref>] or pseudonymization [<xref ref-type="bibr" rid="ref114">114</xref>], backup mechanism [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref72">72</xref>], and firewalls [<xref ref-type="bibr" rid="ref72">72</xref>]. PHRs can also implement an access log so that users can see who viewed and downloaded information [<xref ref-type="bibr" rid="ref76">76</xref>]. The use of complicated or complex passwords can improve the security of s [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref119">119</xref>]. However, some studies show that users have difficulty remembering their passwords [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref97">97</xref>,<xref ref-type="bibr" rid="ref103">103</xref>,<xref ref-type="bibr" rid="ref120">120</xref>]. Thus, PHRs should also add other methods such as fingerprint authentication [<xref ref-type="bibr" rid="ref97">97</xref>], biometric identification [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref94">94</xref>], citizen digital certificate [<xref ref-type="bibr" rid="ref121">121</xref>], and allow users to change their passwords [<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref72">72</xref>].</p>
          <p>To address privacy concerns related to data sharing, PHRs should have the ability for patients to choose what information to share and who can see that information [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref121">121</xref>,<xref ref-type="bibr" rid="ref122">122</xref>] and provide a privacy policy in the system [<xref ref-type="bibr" rid="ref32">32</xref>]. The consent model should also be considered in implementing PHRs [<xref ref-type="bibr" rid="ref116">116</xref>]. Moreover, PHR systems need to follow specific legal requirements related to security and privacy defined on regional, national, or international levels [<xref ref-type="bibr" rid="ref112">112</xref>]. For example, the Health Insurance Portability and Accountability Act ensures secure data exchange with entire clinics [<xref ref-type="bibr" rid="ref76">76</xref>].</p>
        </sec>
        <sec>
          <title>Usability</title>
          <p>Some usability problems identified in selected studies include font or text size that are difficult to use [<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref94">94</xref>], confusing format [<xref ref-type="bibr" rid="ref81">81</xref>], unclear visualization of data [<xref ref-type="bibr" rid="ref90">90</xref>], problem with navigation [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref59">59</xref>], and complicated data entry [<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref118">118</xref>]. Complicated data entry may cause users to not enter data correctly into their PHR [<xref ref-type="bibr" rid="ref118">118</xref>]. The reduction and simplification of PHR system data entry should be considered in PHR design [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref93">93</xref>,<xref ref-type="bibr" rid="ref118">118</xref>]. Users prefer easy to use, simple, and user-friendly interface [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref110">110</xref>,<xref ref-type="bibr" rid="ref118">118</xref>,<xref ref-type="bibr" rid="ref120">120</xref>-<xref ref-type="bibr" rid="ref124">124</xref>]. Users are also interested in attractive and interactive systems [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref110">110</xref>,<xref ref-type="bibr" rid="ref120">120</xref>,<xref ref-type="bibr" rid="ref124">124</xref>] such as the use of contrasting colors for scroll bars and menu items [<xref ref-type="bibr" rid="ref59">59</xref>]. Moreover, it is also important to maintain consistency and standardization of interfaces [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref117">117</xref>,<xref ref-type="bibr" rid="ref118">118</xref>]. A mobile app version of the PHR was also suggested because it was perceived as more user-friendly and easy to use [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref93">93</xref>,<xref ref-type="bibr" rid="ref100">100</xref>].</p>
          <p>A PHR may add a section to guide patients about the features in the PHR [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref118">118</xref>] and quick access to the essential functionalities [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref108">108</xref>]. The use of user-interface elements like buttons and a dropdown menu can enhance the user-friendliness and simplicity of the PHR interface [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref100">100</xref>]. However, icons should be avoided when designing for older adults since they may not recognize them [<xref ref-type="bibr" rid="ref96">96</xref>]. PHRs should be easy to understand and navigate for all user groups [<xref ref-type="bibr" rid="ref110">110</xref>], including those with basic computer knowledge and those who are not computer literate [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref118">118</xref>]. PHR usability should be determined using health literacy assessments and there should be different PHR versions for specific groups of users [<xref ref-type="bibr" rid="ref36">36</xref>].</p>
          <p>Developers should involve users in designing, updating, or improving PHR systems [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref119">119</xref>]. Using a user-centered design approach can facilitate users’ involvement in PHR design [<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref87">87</xref>]. The user-centered design process increased the development process’s complexity, but the product quality was higher, especially satisfaction and user acceptance [<xref ref-type="bibr" rid="ref105">105</xref>]. However, user-centered design may not apply to all PHR types, especially PHRs targeting the general population, which necessitates identifying specific user groups and specific use contexts [<xref ref-type="bibr" rid="ref125">125</xref>]. Adopting a usability design framework that includes usability and user testing may help address PHR usability issues [<xref ref-type="bibr" rid="ref126">126</xref>]. Standardization used for PHR design is International Standards Organization (ISO 9241-210), which focuses on the requirements and user needs [<xref ref-type="bibr" rid="ref105">105</xref>], and ISO 9241-11 for software systems components that define usability [<xref ref-type="bibr" rid="ref96">96</xref>].</p>
        </sec>
        <sec>
          <title>Data Quality</title>
          <p>Health care providers may doubt patient-entered data in a PHR [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref113">113</xref>]. Not all patients have enough knowledge to generate health data in a PHR [<xref ref-type="bibr" rid="ref107">107</xref>,<xref ref-type="bibr" rid="ref112">112</xref>]. Data uploaded by the patient may be inconsistent [<xref ref-type="bibr" rid="ref91">91</xref>], incomplete [<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref110">110</xref>], inaccurate [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref110">110</xref>,<xref ref-type="bibr" rid="ref115">115</xref>], or not up to date [<xref ref-type="bibr" rid="ref90">90</xref>]. PHRs require patient commitment to keep the system up-to-date and relevant over time [<xref ref-type="bibr" rid="ref111">111</xref>]. This issue needs particular attention, especially when PHR data are transferred to EHRs and used in professional medical decision-making and treatment processes [<xref ref-type="bibr" rid="ref112">112</xref>].</p>
          <p>To ensure data quality of patient-generated data in PHRs, health care professionals need to take time to supervise the quality of information generated by patients in PHRs [<xref ref-type="bibr" rid="ref110">110</xref>,<xref ref-type="bibr" rid="ref112">112</xref>]. PHRs should differentiate patient-generated data from the health care provider’s data [<xref ref-type="bibr" rid="ref68">68</xref>]. Moreover, PHR design needs to define what information is required because an incomplete record is preferable to an inaccurate one from a provider’s perspective [<xref ref-type="bibr" rid="ref35">35</xref>]. Standardization of patient-entered information is essential to ensure data quality [<xref ref-type="bibr" rid="ref33">33</xref>]. Input control should be comfortable and descriptive words should appear to help patients enter PHR data [<xref ref-type="bibr" rid="ref108">108</xref>].</p>
          <p>In tethered PHRs, which are tied to EHRs in health organizations, health information on the PHRs are created automatically from the original patient clinical reports to make this information more reliable [<xref ref-type="bibr" rid="ref34">34</xref>]. However, this can be a problem if the EHR’s information is incomplete [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref64">64</xref>] or if the information is not generated automatically. This can also be caused by health care providers not updating the PHR information consistently [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        </sec>
        <sec>
          <title>Personalization</title>
          <p>Some users may have more health issues than others, such as older patients having more health issues, appointments, and information to manage [<xref ref-type="bibr" rid="ref22">22</xref>]. People want the PHR to be tailored to their needs and capable of changing based on their health and well-being needs [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref123">123</xref>]. This person-specific health and well-being information can make the PHR system more appealing [<xref ref-type="bibr" rid="ref118">118</xref>]. The PHR system needs to be adaptable and extensible to ensure successful operation [<xref ref-type="bibr" rid="ref112">112</xref>]. It is also suggested that PHRs support customizability based on computer literacy [<xref ref-type="bibr" rid="ref87">87</xref>].</p>
          <p>PHR systems should provide medical information that can be dynamically adapted to patient preferences for simpler or more complex information [<xref ref-type="bibr" rid="ref99">99</xref>] [<xref ref-type="bibr" rid="ref117">117</xref>]. For example, in PittPHR, users can customize the trackers according to their own needs by hiding or unhiding available trackers in a given list and add or delete links in the resources module according to their own needs [<xref ref-type="bibr" rid="ref33">33</xref>]. PHRs could also provide tailored health education materials based on patient health problems [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref95">95</xref>,<xref ref-type="bibr" rid="ref117">117</xref>]. Despite the need for personalization, designers or developers need to define the extent to which PHRs can be personalized but still maintain standardization, uniformity, and simplicity [<xref ref-type="bibr" rid="ref125">125</xref>].</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Seven function categories of PHRs are identified as the main functionalities of PHRs, which are grouped into basic and advanced functions. Basic functions (health records and administrative records) provide essential information for patients in their health care. Health records could provide a complete summary of patient health status and condition. Information on this function could reduce health workers’ time gathering patient history and reduce redundant transactions and tests [<xref ref-type="bibr" rid="ref20">20</xref>]. Information on administrative records such as personal information serves as a patient identifier on a PHR.</p>
        <p>Advanced functions (medication management, communication, appointment management, education, and self-health monitoring) could support patient involvement in their health care. Involving patients in controlling their health information improves the chance that health providers would have a comprehensive view of patient health conditions [<xref ref-type="bibr" rid="ref20">20</xref>]. Medication management functions such as medication scheduler and reminders could help patients take medicine on time. Moreover, the medication reconciliation option could avoid medication errors [<xref ref-type="bibr" rid="ref127">127</xref>]. Communication functions such as messaging could free physicians from the limitations of phone and face-to-face communication [<xref ref-type="bibr" rid="ref1">1</xref>]. Appointment management reduces the chance of a patient missing an appointment. Education could support health knowledge promotion [<xref ref-type="bibr" rid="ref20">20</xref>], which may improve the patient’s health literacy. The information recorded from the self-health monitoring function may help health providers with disease diagnosis and treatment [<xref ref-type="bibr" rid="ref10">10</xref>]. This function could help patients track their progress to reach specific health goals [<xref ref-type="bibr" rid="ref9">9</xref>] and monitor the impact of their behavioral changes [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>In addition to these functionalities, other supporting functionalities may also need to be developed based on the issues identified in this study. To improve security and privacy, PHRs should implement access control, which includes authentication and authorization. PHRs can also provide a backup option to avoid data loss and audit logs to review who accessed the record and what data have been accessed. To improve usability, PHRs can provide quick access to the important information or functions that users frequently use and add a menu for help or a user guide about using features in the PHR. Customization options to show or hide specific health data according to patient health needs are also recommended to increase personalization.</p>
        <p>Interoperability represents a key component of PHR architecture [<xref ref-type="bibr" rid="ref8">8</xref>]. When PHRs are integrated with health providers, they provide more significant benefits and valuable content for users [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. Interoperability can also reduce data entry load because health information is automatically transferred to the PHR. This can increase the usability and the quality of data on the PHR. PHRs need to provide standard definitions for data exchange and implement sharing functions to connect PHRs with other stakeholders, such as health providers, insurance, government agency, pharmacy, community or support groups, and other systems such as home monitoring devices. <xref rid="figure10" ref-type="fig">Figure 10</xref> describes the integrated PHR architecture based on the result of this review.</p>
        <fig id="figure10" position="float">
          <label>Figure 10</label>
          <caption>
            <p>Integrated personal health record architecture.</p>
          </caption>
          <graphic xlink:href="jmir_v23i7e26236_fig10.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The main functionalities described in this review, such as health records, administrative records, medication management, communication, appointment management, education, and self-health monitoring, have also been described in previous reviews [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. Most of these reviews [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>] focus more on discussing the functionality of PHRs related to improving health service delivery. Only Genitsaridi et al [<xref ref-type="bibr" rid="ref10">10</xref>] discussed supporting functionalities such as access control to be included in requirements on the PHR. Previous studies also have discussed technological issues [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Our research augments that of previous studies by translating these issues as supporting functionalities in PHR systems.</p>
        <p>The functionalities in PHRs can help health care providers and patients obtain useful health information during public health emergencies such as natural disasters and pandemics. For example, in the COVID-19 pandemic, hospital services experienced a crisis [<xref ref-type="bibr" rid="ref128">128</xref>]. Observations of health outside of standard hospital settings can be difficult [<xref ref-type="bibr" rid="ref129">129</xref>]. Functions such as communication can help patients and health care providers consult without making eye contact. Furthermore, in the education function, PHR providers can provide information about updated COVID-19 and health care information. The health record function helps patients obtain and store test results. The self-health monitoring function increases the patient’s ability to control and manage health conditions. Functions such as measuring body temperature can be used to detect early signs of infection [<xref ref-type="bibr" rid="ref129">129</xref>]. Integrating PHRs into a broader telehealth infrastructure could improve emergency health care delivery by reducing patient spikes in health care facilities [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      </sec>
      <sec>
        <title>Comparison With Prior Work</title>
        <p>The Health Level 7 Personal Health Record System Functional Model (HL7 PHR-S FM) defines a standardized model of the functions present in PHR systems [<xref ref-type="bibr" rid="ref130">130</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]. The model consists of 3 sections: personal health (PH), supportive (S), and information infrastructure (IN). Personal health functions enable an individual to manage information about their health care. Supportive roles assist with the administrative and financial requirements within health care delivery. Information infrastructure functions support personal health and supportive functions.</p>
        <p>Health records, medication management, communication, education, and self-health monitoring can be categorized into personal health sections. Administrative records such as managing patient profiles can be categorized into a personal health section, while information about health professionals, hospitals, and insurance can be categorized as a supportive section. Supporting functions defined based on PHR implementation issues, namely sharing, access control, audit logs, backup options, and customization, can be categorized in the information infrastructure section. This section ensures the privacy and security of PHRs, promotes interoperability between PHRs and other systems, and enables PHR function to be accessible and easy to use [<xref ref-type="bibr" rid="ref130">130</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]. <xref ref-type="table" rid="table5">Table 5</xref> summarized comparisons between functions identified in this review study and functions defined in the HL7 PHR-S FM.</p>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Comparisons between functions.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="30"/>
            <col width="180"/>
            <col width="0"/>
            <col width="280"/>
            <col width="0"/>
            <col width="480"/>
            <thead>
              <tr valign="top">
                <td colspan="4">Functions identified and ID</td>
                <td colspan="3">Functions defined in the HL7 PHR-S FM<sup>a</sup></td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <break/>
                </td>
                <td colspan="2">Function name</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="7">
                  <bold>Basic functions</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Health record</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.2.5</td>
                <td colspan="2">Manage historical and current state data</td>
                <td colspan="2">Provide a summary of the patient’s current medical state and history</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Administrative record</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.1.2</td>
                <td colspan="2">Manage PHR<sup>b</sup> account holder demographics</td>
                <td colspan="2">Capture the patient’s demographic information</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>S.1.3</td>
                <td colspan="2">Manage health care provider information</td>
                <td colspan="2">Import or retrieval of data necessary to identify a health care provider</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>S.1.5</td>
                <td colspan="2">Manage health care facility information</td>
                <td colspan="2">Import or retrieve of data necessary to identify a health care facility</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>S.2.1</td>
                <td colspan="2">Capture and read health insurance account and benefit information</td>
                <td colspan="2">Request and/or receive and read the information on health insurance benefits</td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Advanced functions</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Medications management</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.3.4</td>
                <td colspan="2">Manage medications</td>
                <td colspan="2">Help patients manage his or her medications</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Communication (patient-provider communication)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.6.3</td>
                <td colspan="2">Communications between provider and/or the PHR account holder’s representative</td>
                <td colspan="2">Capture information in preparation for a consultation and maintain continuous communications with the health provider</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>IN.3.10</td>
                <td colspan="2">Secure messaging</td>
                <td colspan="2">Enable secure electronic communication with health providers</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Appointment management</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.6.3</td>
                <td colspan="2">Communications between provider and/or the PHR account holder’s representative</td>
                <td colspan="2">Capture information in preparation for a consultation and maintain continuous communications with the health provider</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Education</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.4</td>
                <td colspan="2">Manage health education</td>
                <td colspan="2">Provide proper medical education and patient-specific knowledge based on information in the PHR</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Self-health monitoring</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.3.1</td>
                <td colspan="2">Manage personal clinical measurements and observations</td>
                <td colspan="2">Provide the patient capability to enter personally sourced data and make it available to authorized health providers or other users or applications</td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Supporting functions</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Sharing</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>IN.2</td>
                <td colspan="2">Standards-based interoperability</td>
                <td colspan="2">Interoperability standards enable the sharing of information between PHRs and other systems</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Access control</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>IN.3.3</td>
                <td colspan="2">Entity access control</td>
                <td colspan="2">PHR must perform authentication and authorization of users or applications</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Audit logs and</bold>
                  <bold>backup option</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>IN.4</td>
                <td colspan="2">Auditable records</td>
                <td colspan="2">Provide system access and use audit capabilities to indicate who accessed the record, how, and when the action was taken</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>Customization option</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>IN.1.3</td>
                <td colspan="2">Present ad hoc views of the health record</td>
                <td colspan="2">Provide ad hoc views of the PHR information</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="6">
                  <bold>User guide</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>PH.1.1</td>
                <td colspan="2">Identify and maintain a PHR account holder record</td>
                <td colspan="2">Offer user guide for the installation, initialization, registration, or operation of their PHR</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>HL7 PHR-S FM: Health Level 7 Personal Health Record System Functional Model.</p>
            </fn>
            <fn id="table5fn2">
              <p><sup>b</sup>PHR: personal health record.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>The functionality identified in this review covers the main section (PH, S, IN) in the HL7 PHR-S FM. However, functionalities and data elements found in this review are on the individual level that focuses on improving health care. Functions that are not included in this review are functions related to the secondary use of health data. Secondary health data use applies to personal health information for uses outside direct health care delivery [<xref ref-type="bibr" rid="ref132">132</xref>]. In the HL7 PHR-S FM, a population health and wellness (PH 3.6) function helps control public health risks to the population and patients. For example, it enables patients to export anonymized data for biosurveillance and public health reporting, and patients can get alerts or warnings regarding population health threats. A manage other resources (S.4) function supports patient enrollment in clinical trials or research [<xref ref-type="bibr" rid="ref131">131</xref>]. From this review, only a few studies [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref91">91</xref>] mentioned that PHRs could be used for secondary health data use, but they did not explain specific data needed for this function. A discussion about secondary health data use in PHRs can be an opportunity for future research.</p>
        <p>Not all functions in the HL7 PHR-S FM were found in this review study because the HL7 PHR-S FM is universal and generic by design. There may be additional constraints in certain realms or regions. PHR developers or designers can create a functional profile to define a selected set of applicable functions for a particular purpose, group of users, degree of interoperability, or custodian [<xref ref-type="bibr" rid="ref130">130</xref>]. This study defines PHR functionalities based on the current state of research and provides more examples of data elements and subfunctions for each functionality. This study also found that the HL7 PHR-S FM only includes patient-provider communication. Other communications, such as communication with others in a similar situation and support groups, are not discussed in the HL7 PHR-S FM.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study is limited to reviewing the implementation of PHRs in research articles and does not address the implementation of commercial PHRs available on the internet. Thus, the functionalities and issues of the PHRs defined in this study may not reflect the state of the practice. This paper does not discuss which functions are more common or whether certain functions are used more frequently than others and does not discuss each function’s benefits and impact on health outcomes. We cannot determine which functionality should be prioritized in the implementation of PHR. We only discuss the functions that are generally mentioned in the selected paper. Each function’s data element may not be comprehensive and might not be generalizable to all patient populations. This is because each disease or condition has different specific data.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This systematic literature review paper discussed functionalities and issues in the implementation of PHRs. Seven function categories are identified in this review, which are grouped into basic and advanced functions. In addition to these functionalities, other supporting functionalities may also need to be developed based on the issues identified in this study. Based on the results, this paper provides an integrated PHR architectural model that describes the functional requirements and data sources of PHRs. This study can offer recommendations or guidance in implementing PHRs by health care facilities management, application developers, policymakers, or other related stakeholders. Functionalities (including data elements and subfunctions) listed in this study and architectural model (<xref rid="figure10" ref-type="fig">Figure 10</xref>) can be used when considering what features to implement in a PHR. The model (<xref rid="figure10" ref-type="fig">Figure 10</xref>) can also serve as the target data sources to be integrated into the PHR system. Moreover, technological issues explained in this study can be used to develop policies in the implementation of PHRs. For example, since security and privacy are identified as technological issues in this study, implementers of PHRs should develop policies that govern access control in PHRs. The findings of this study may be translated as functional and nonfunctional requirements of the PHR system. This study’s findings can also serve as a basis and comparison for other researchers who will examine PHR functionality and use in the future. PHR integrated architecture (<xref rid="figure10" ref-type="fig">Figure 10</xref>) can be used as a model that other researchers can use to compare, map, or evaluate the PHR functionalities that will be examined. Furthermore, personal factors such as age, culture, and health and technology literacy levels can influence security, privacy, and usability issues. Future studies can be conducted to analyze the effect of personal factors on technological issues.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>PRISMA checklist.</p>
        <media xlink:href="jmir_v23i7e26236_app1.doc" xlink:title="DOC File , 66 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Characteristics of the included studies.</p>
        <media xlink:href="jmir_v23i7e26236_app2.docx" xlink:title="DOCX File , 50 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Data elements and subfunctions.</p>
        <media xlink:href="jmir_v23i7e26236_app3.docx" xlink:title="DOCX File , 358 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">FHIR</term>
          <def>
            <p>Fast Healthcare Interoperability Resources</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">HL7</term>
          <def>
            <p>Health Level 7</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HL7 PHR-S FM</term>
          <def>
            <p>Health Level 7 Personal Health Record System Functional Model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">IN</term>
          <def>
            <p>information infrastructure</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">PH</term>
          <def>
            <p>personal health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">PHR</term>
          <def>
            <p>personal health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic reviews and Meta-analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">S</term>
          <def>
            <p>supportive</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This work is supported by grant NKB-3027/UN2.RST/HKP.05.00/2020 from the Pendidikan Magister Menuju Doktor untuk Sarjana Unggul and Ministry of Research, Technology, and Higher Education Republic of Indonesia.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Overhage</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Sands</surname>
              <given-names>DZ</given-names>
            </name>
          </person-group>
          <article-title>Personal health records: definitions, benefits, and strategies for overcoming barriers to adoption</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2006</year>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>121</fpage>
          <lpage>126</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/lookup/pmidlookup?view=long&#38;pmid=16357345"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M2025</pub-id>
          <pub-id pub-id-type="medline">16357345</pub-id>
          <pub-id pub-id-type="pii">M2025</pub-id>
          <pub-id pub-id-type="pmcid">PMC1447551</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>Bouri</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ravi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Going mobile: how mobile personal health records can improve health care during emergencies</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2014</year>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e8</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2014/1/e8/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.3017</pub-id>
          <pub-id pub-id-type="medline">25098942</pub-id>
          <pub-id pub-id-type="pii">v2i1e8</pub-id>
          <pub-id pub-id-type="pmcid">PMC4114425</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Perakslis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Covid-19: a huge stress test for electronic health record systems</article-title>
          <source>Stat</source>
          <year>2020</year>
          <month>03</month>
          <day>12</day>
          <access-date>2020-04-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.statnews.com/2020/03/12/covid-19-huge-stress-test-electronic-health-record-systems/">https://www.statnews.com/2020/03/12/covid-19-huge-stress-test-electronic-health-record-systems/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Finnegan</surname>
              <given-names>Matthew</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 puts new demands on e-health record systems</article-title>
          <source>Computerworld</source>
          <year>2020</year>
          <month>03</month>
          <day>31</day>
          <access-date>2020-04-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.computerworld.com/article/3535083/covid-19-puts-new-demands-on-e-health-record-systems.html">https://www.computerworld.com/article/3535083/covid-19-puts-new-demands-on-e-health-record-systems.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <collab>World Health Organization</collab>
          </person-group>
          <article-title>Management of patient information: Trends and challenges in Member States</article-title>
          <source>WHO Global Observatory for eHealth</source>
          <year>2012</year>
          <publisher-loc>Geneva</publisher-loc>
          <publisher-name>World Health Organization</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Galas</surname>
              <given-names>Jeff</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 pandemic: why patients need to control their own data</article-title>
          <source>HIT Consultant Media</source>
          <year>2020</year>
          <month>03</month>
          <day>24</day>
          <access-date>2020-04-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hitconsultant.net/2020/03/24/covid-19-pandemic-patients-need-control-their-own-data/#.YObQqugzbIU">https://hitconsultant.net/2020/03/24/covid-19-pandemic-patients-need-control-their-own-data/#.YObQqugzbIU</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>Alsahafi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gay</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>An overview of electronic personal health records</article-title>
          <source>Heal Policy Technol</source>
          <year>2018</year>
          <month>12</month>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>427</fpage>
          <lpage>432</lpage>
          <pub-id pub-id-type="doi">10.1016/j.hlpt.2018.10.004</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>Kaelber</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Johnston</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Middleton</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>A research agenda for personal health records (PHRs)</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2008</year>
          <volume>15</volume>
          <issue>6</issue>
          <fpage>729</fpage>
          <lpage>736</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/cgi/pmidlookup?view=long&#38;pmid=18756002"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M2547</pub-id>
          <pub-id pub-id-type="medline">18756002</pub-id>
          <pub-id pub-id-type="pii">M2547</pub-id>
          <pub-id pub-id-type="pmcid">PMC2585530</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>Bouayad</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ialynytchev</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Padmanabhan</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Patient health record systems scope and functionalities: literature review and future directions</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>11</month>
          <day>15</day>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>e388</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2017/11/e388/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8073</pub-id>
          <pub-id pub-id-type="medline">29141839</pub-id>
          <pub-id pub-id-type="pii">v19i11e388</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>Genitsaridi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kondylakis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Koumakis</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Marias</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tsiknakis</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of personal health record systems through the lenses of EC research projects</article-title>
          <source>Comput Biol Med</source>
          <year>2015</year>
          <month>04</month>
          <volume>59</volume>
          <fpage>175</fpage>
          <lpage>185</lpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2013.11.004</pub-id>
          <pub-id pub-id-type="medline">24315661</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(13)00322-3</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>Alturkistani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Qavi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Anyanwu</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Greenfield</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Greaves</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Costelloe</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Patient portal functionalities and patient outcomes among patients with diabetes: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>09</month>
          <day>22</day>
          <volume>22</volume>
          <issue>9</issue>
          <fpage>e18976</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/9/e18976/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18976</pub-id>
          <pub-id pub-id-type="medline">32960182</pub-id>
          <pub-id pub-id-type="pii">v22i9e18976</pub-id>
          <pub-id pub-id-type="pmcid">PMC7539164</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>Price</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bellwood</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kitson</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Davies</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Conditions potentially sensitive to a personal health record (PHR) intervention: a systematic review</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2015</year>
          <volume>15</volume>
          <fpage>32</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.biomedcentral.com/1472-6947/15/32"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-015-0159-1</pub-id>
          <pub-id pub-id-type="medline">25927384</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-015-0159-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC4411701</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>Hawthorne</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Richards</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Personal health records: a new type of electronic medical record</article-title>
          <source>RMJ</source>
          <year>2017</year>
          <month>11</month>
          <day>20</day>
          <volume>27</volume>
          <issue>3</issue>
          <fpage>286</fpage>
          <lpage>301</lpage>
          <pub-id pub-id-type="doi">10.1108/RMJ-08-2016-0020</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>Irizarry</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>DeVito</surname>
              <given-names>DA</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>
          <volume>17</volume>
          <issue>6</issue>
          <fpage>e148</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://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="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carrión</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Fernández-Alemán</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Toval</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Are personal health records safe? A review of free web-accessible personal health record privacy policies</article-title>
          <source>J Med Internet Res</source>
          <year>2012</year>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>e114</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2012/4/e114/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.1904</pub-id>
          <pub-id pub-id-type="medline">22917868</pub-id>
          <pub-id pub-id-type="pii">v14i4e114</pub-id>
          <pub-id pub-id-type="pmcid">PMC3510685</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bajpai</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Gorthi</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>On non-functional requirements: a survey</article-title>
          <year>2012</year>
          <conf-name>Conf Electr Electron Comput Sci</conf-name>
          <conf-date>2012</conf-date>
          <conf-loc>Bhopal</conf-loc>
          <fpage>1</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="doi">10.1109/SCEECS.2012.6184810</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wazlawick</surname>
              <given-names>Raul Sidnei</given-names>
            </name>
          </person-group>
          <article-title>High-Level Requirements</article-title>
          <source>Object-Oriented Analysis and Design for Information Systems</source>
          <year>2014</year>
          <publisher-loc>Amsterdam</publisher-loc>
          <publisher-name>Elsevier</publisher-name>
          <fpage>29</fpage>
          <lpage>57</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <source>Welcome to the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) website!</source>
          <year>2015</year>
          <access-date>2020-05-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.prisma-statement.org/">http://www.prisma-statement.org/</ext-link>
          </comment>
        </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>Liberati</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mulrow</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gøtzsche</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Ioannidis</surname>
              <given-names>JPA</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Devereaux</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kleijnen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The PRISMA statement for reporting systematic reviews and meta-analyses of studies that evaluate health care interventions: explanation and elaboration</article-title>
          <source>J Clin Epidemiol</source>
          <year>2009</year>
          <month>10</month>
          <volume>62</volume>
          <issue>10</issue>
          <fpage>e1</fpage>
          <lpage>e34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://linkinghub.elsevier.com/retrieve/pii/S0895-4356(09)00180-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jclinepi.2009.06.006</pub-id>
          <pub-id pub-id-type="medline">19631507</pub-id>
          <pub-id pub-id-type="pii">S0895-4356(09)00180-2</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>Detmer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bloomrosen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Raymond</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Integrated personal health records: transformative tools for consumer-centric care</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2008</year>
          <volume>8</volume>
          <fpage>45</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-8-45"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-8-45</pub-id>
          <pub-id pub-id-type="medline">18837999</pub-id>
          <pub-id pub-id-type="pii">1472-6947-8-45</pub-id>
          <pub-id pub-id-type="pmcid">PMC2596104</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <source>World economic situation and prospects</source>
          <year>2020</year>
          <access-date>2020-06-15</access-date>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>United Nations</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.un.org/development/desa/dpad/wp-content/uploads/sites/45/WESP2020_Annex.pdf">https://www.un.org/development/desa/dpad/wp-content/uploads/sites/45/WESP2020_Annex.pdf</ext-link>
          </comment>
        </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>Tulu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Trapp</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Strong</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hoque</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Trudel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Garber</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>An analysis of patient portal utilization: what can we learn about online patient behavior by examining portal click data?</article-title>
          <source>Heal Syst</source>
          <year>2017</year>
          <month>12</month>
          <day>19</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>66</fpage>
          <lpage>79</lpage>
          <pub-id pub-id-type="doi">10.1057/hs.2015.5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iacona</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Militello</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Serbanati</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mastratisi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ricci</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gilardi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Personal health system: a tool to support the patient empowerment</article-title>
          <year>2015</year>
          <conf-name>E-Health Bioeng Conf IEEE</conf-name>
          <conf-date>2015</conf-date>
          <conf-loc>Iasi</conf-loc>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/EHB.2015.7391370</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>Mishra</surname>
              <given-names>VK</given-names>
            </name>
            <name name-style="western">
              <surname>Hoyt</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Wolver</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Yoshihashi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Banas</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Qualitative and quantitative analysis of patients' perceptions of the patient portal experience with OpenNotes</article-title>
          <source>Appl Clin Inform</source>
          <year>2019</year>
          <month>01</month>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>10</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30602196"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0038-1676588</pub-id>
          <pub-id pub-id-type="medline">30602196</pub-id>
          <pub-id pub-id-type="pmcid">PMC6327733</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>Abdulnabi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Haiqi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kiah</surname>
              <given-names>MLM</given-names>
            </name>
            <name name-style="western">
              <surname>Zaidan</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Zaidan</surname>
              <given-names>BB</given-names>
            </name>
            <name name-style="western">
              <surname>Hussain</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A distributed framework for health information exchange using smartphone technologies</article-title>
          <source>J Biomed Inform</source>
          <year>2017</year>
          <month>05</month>
          <volume>69</volume>
          <fpage>230</fpage>
          <lpage>250</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(17)30083-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2017.04.013</pub-id>
          <pub-id pub-id-type="medline">28433825</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(17)30083-7</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>Katehakis</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kondylakis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Koumakis</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kouroubali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marias</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Integrated care solutions for the citizen: personal health record functional models to support interoperability</article-title>
          <source>Eur J Biomed Informatics</source>
          <year>2017</year>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>56</fpage>
        </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>Elston Lafata</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Shires</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Dyer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ratliff</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Schreiber</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Patients' adoption of and feature access within electronic patient portals</article-title>
          <source>Am J Manag Care</source>
          <year>2018</year>
          <month>11</month>
          <day>01</day>
          <volume>24</volume>
          <issue>11</issue>
          <fpage>e352</fpage>
          <lpage>e357</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ajmc.com/pubMed.php?pii=87785"/>
          </comment>
          <pub-id pub-id-type="medline">30452203</pub-id>
          <pub-id pub-id-type="pii">87785</pub-id>
          <pub-id pub-id-type="pmcid">PMC6613379</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>Van den Bulck</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Hermens</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Slegers</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Vandenberghe</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Goderis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Vankrunkelsven</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Designing a patient portal for patient-centered care: cross-sectional survey</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>10</month>
          <day>01</day>
          <volume>20</volume>
          <issue>10</issue>
          <fpage>e269</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/10/e269/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9497</pub-id>
          <pub-id pub-id-type="medline">30287416</pub-id>
          <pub-id pub-id-type="pii">v20i10e269</pub-id>
          <pub-id pub-id-type="pmcid">PMC6231862</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Voigt</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Benedict</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Susky</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Scheplitz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Frankowitz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kern</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Schlieter</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ziemssen</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>A digital patient portal for patients with multiple sclerosis</article-title>
          <source>Front Neurol</source>
          <year>2020</year>
          <volume>11</volume>
          <fpage>400</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fneur.2020.00400"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fneur.2020.00400</pub-id>
          <pub-id pub-id-type="medline">32670174</pub-id>
          <pub-id pub-id-type="pmcid">PMC7326091</pub-id>
        </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>Hill</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Weaver</surname>
              <given-names>FM</given-names>
            </name>
            <name name-style="western">
              <surname>Nazi</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>FP</given-names>
            </name>
            <name name-style="western">
              <surname>Goldstein</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hogan</surname>
              <given-names>TP</given-names>
            </name>
          </person-group>
          <article-title>Potential of personal health record portals in the care of individuals with spinal cord injuries and disorders: provider perspectives</article-title>
          <source>J Spinal Cord Med</source>
          <year>2018</year>
          <month>05</month>
          <volume>41</volume>
          <issue>3</issue>
          <fpage>298</fpage>
          <lpage>308</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28325112"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/10790268.2017.1293760</pub-id>
          <pub-id pub-id-type="medline">28325112</pub-id>
          <pub-id pub-id-type="pmcid">PMC6055947</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>Kipping</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stuckey</surname>
              <given-names>MI</given-names>
            </name>
            <name name-style="western">
              <surname>Hernandez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Riahi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A web-based patient portal for mental health care: benefits evaluation</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>11</month>
          <day>16</day>
          <volume>18</volume>
          <issue>11</issue>
          <fpage>e294</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2016/11/e294/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.6483</pub-id>
          <pub-id pub-id-type="medline">27852556</pub-id>
          <pub-id pub-id-type="pii">v18i11e294</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>Rezaee</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>AlizadehNaini</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Halim</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Designing and implementation of web-based personal health record for patients with inflammatory bowel disease</article-title>
          <source>Govaresh</source>
          <year>2018</year>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>108</fpage>
        </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>Zhou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>DeAlmeida</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Parmanto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Applying a user-centered approach to building a mobile personal health record app: development and usability study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>07</month>
          <day>05</day>
          <volume>7</volume>
          <issue>7</issue>
          <fpage>e13194</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/7/e13194/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13194</pub-id>
          <pub-id pub-id-type="medline">31278732</pub-id>
          <pub-id pub-id-type="pii">v7i7e13194</pub-id>
          <pub-id pub-id-type="pmcid">PMC6640070</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>Barbarito</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Pinciroli</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Barone</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pizzo</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ranza</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mason</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mazzola</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bonacina</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marceglia</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Implementing the lifelong personal health record in a regionalised health information system: the case of Lombardy, Italy</article-title>
          <source>Comput Biol Med</source>
          <year>2015</year>
          <month>04</month>
          <volume>59</volume>
          <fpage>164</fpage>
          <lpage>174</lpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2013.10.021</pub-id>
          <pub-id pub-id-type="medline">24238969</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(13)00308-9</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>Clarke</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schuetzler</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Windle</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pachunka</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fruhling</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Usability and cognitive load in the design of a personal health record</article-title>
          <source>Heal Policy Technol</source>
          <year>2020</year>
          <month>06</month>
          <volume>9</volume>
          <issue>2</issue>
          <fpage>218</fpage>
          <lpage>224</lpage>
          <pub-id pub-id-type="doi">10.1016/j.hlpt.2019.10.002</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>Javier</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Troszak</surname>
              <given-names>LK</given-names>
            </name>
            <name name-style="western">
              <surname>Shimada</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>McInnes</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Ohl</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Avoundjian</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Erhardt</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Midboe</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Racial and ethnic disparities in use of a personal health record by veterans living with HIV</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>696</fpage>
          <lpage>702</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30924875"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz024</pub-id>
          <pub-id pub-id-type="medline">30924875</pub-id>
          <pub-id pub-id-type="pii">5423053</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647203</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>Baudendistel</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Winkler</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kamradt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Längst</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Eckrich</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Heinze</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Bergh</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Szecsenyi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ose</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Personal electronic health records: understanding user requirements and needs in chronic cancer care</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <volume>17</volume>
          <issue>5</issue>
          <fpage>e121</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2015/5/e121/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.3884</pub-id>
          <pub-id pub-id-type="medline">25998006</pub-id>
          <pub-id pub-id-type="pii">v17i5e121</pub-id>
          <pub-id pub-id-type="pmcid">PMC4468571</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>Song</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Pak</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kalabins</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fouché</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Standard-based patient-centered personal health record system</article-title>
          <source>Proc 11th Int Conf Ubiquitous Inf Manag Commun</source>
          <year>2017</year>
          <fpage>1</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1145/3022227.3022289</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cernian</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tiganoaia</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sacala</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Pavel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Iftemi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>PatientDataChain: a blockchain-based approach to integrate personal health records</article-title>
          <source>Sensors (Basel)</source>
          <year>2020</year>
          <month>11</month>
          <day>16</day>
          <volume>20</volume>
          <issue>22</issue>
          <fpage>6538</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s20226538"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s20226538</pub-id>
          <pub-id pub-id-type="medline">33207620</pub-id>
          <pub-id pub-id-type="pii">s20226538</pub-id>
          <pub-id pub-id-type="pmcid">PMC7697358</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Flanagan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kunjan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Doebbeling</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Toscos</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Missing links: Challenges in engaging the underserved with health information and communication technology</article-title>
          <source>Proc 10th EAI Int Conf Pervasive Comput Technol Healthc</source>
          <year>2016</year>
          <fpage>122</fpage>
          <lpage>129</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://hdl.handle.net/1805/18170"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Minoletti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rapisarda</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Giraldo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Grande</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sommer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Plazzotta</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Luna</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>User-centered design of a pediatric vaccination module for patients</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <month>08</month>
          <day>21</day>
          <volume>264</volume>
          <fpage>1096</fpage>
          <lpage>1100</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI190395</pub-id>
          <pub-id pub-id-type="medline">31438094</pub-id>
          <pub-id pub-id-type="pii">SHTI190395</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>Klein</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Hogan</surname>
              <given-names>TP</given-names>
            </name>
          </person-group>
          <article-title>A decade of veteran voices: examining patient portal enhancements through the lens of user-centered design</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>07</month>
          <day>10</day>
          <volume>20</volume>
          <issue>7</issue>
          <fpage>e10413</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/7/e10413/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10413</pub-id>
          <pub-id pub-id-type="medline">29991468</pub-id>
          <pub-id pub-id-type="pii">v20i7e10413</pub-id>
          <pub-id pub-id-type="pmcid">PMC6058093</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rief</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hamm</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Zickmund</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Nikolajski</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lesky</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hess</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Weimer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zieth</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <article-title>Using health information technology to foster engagement: patients' experiences with an active patient health record</article-title>
          <source>Health Commun</source>
          <year>2017</year>
          <month>03</month>
          <volume>32</volume>
          <issue>3</issue>
          <fpage>310</fpage>
          <lpage>319</lpage>
          <pub-id pub-id-type="doi">10.1080/10410236.2016.1138378</pub-id>
          <pub-id pub-id-type="medline">27223684</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Miao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Design and implementation of personal health record systems based on knowledge graph</article-title>
          <year>2018</year>
          <conf-name>9th Int Conf Inf Technol Med Educ. IEEE</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Hangzhou</conf-loc>
          <fpage>133</fpage>
          <lpage>136</lpage>
          <pub-id pub-id-type="doi">10.1109/ITME.2018.00039</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dexheimer</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Greiner</surname>
              <given-names>MV</given-names>
            </name>
            <name name-style="western">
              <surname>Beal</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kachelmeyer</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vaughn</surname>
              <given-names>LM</given-names>
            </name>
          </person-group>
          <article-title>Sharing personal health record data elements in protective custody: youth and stakeholder perspectives</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>714</fpage>
          <lpage>721</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31365097"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz067</pub-id>
          <pub-id pub-id-type="medline">31365097</pub-id>
          <pub-id pub-id-type="pii">5542031</pub-id>
          <pub-id pub-id-type="pmcid">PMC6696503</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>JMG</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Menser</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>McAlearney</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Usability evaluation of a commercial inpatient portal</article-title>
          <source>Int J Med Inform</source>
          <year>2018</year>
          <month>12</month>
          <volume>110</volume>
          <fpage>10</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2017.11.007</pub-id>
          <pub-id pub-id-type="medline">29331248</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(17)30419-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tieu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sarkar</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Schillinger</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ralston</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Ratanawongsa</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Pasick</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lyles</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Barriers and facilitators to online portal use among patients and caregivers in a safety net health care system: a qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <volume>17</volume>
          <issue>12</issue>
          <fpage>e275</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2015/12/e275/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4847</pub-id>
          <pub-id pub-id-type="medline">26681155</pub-id>
          <pub-id pub-id-type="pii">v17i12e275</pub-id>
          <pub-id pub-id-type="pmcid">PMC4704882</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>MI</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Simon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bruchanski</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Frangella</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sommer</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Giussi</surname>
              <given-names>MV</given-names>
            </name>
            <name name-style="western">
              <surname>Luna</surname>
              <given-names>DR</given-names>
            </name>
          </person-group>
          <article-title>Lessons learned after redesigning a personal health record</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2017</year>
          <volume>245</volume>
          <fpage>216</fpage>
          <lpage>220</lpage>
          <pub-id pub-id-type="medline">29295085</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Avdagovska</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ballermann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Olson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Graham</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Menon</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Stafinski</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Patient portal implementation and uptake: qualitative comparative case study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>07</month>
          <day>27</day>
          <volume>22</volume>
          <issue>7</issue>
          <fpage>e18973</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/7/e18973/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18973</pub-id>
          <pub-id pub-id-type="medline">32716308</pub-id>
          <pub-id pub-id-type="pii">v22i7e18973</pub-id>
          <pub-id pub-id-type="pmcid">PMC7427986</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carryer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kooienga</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Patients' experience and understanding of E-portals in rural general practice: an ethnographic exploration</article-title>
          <source>J Prim Health Care</source>
          <year>2017</year>
          <month>12</month>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>262</fpage>
          <lpage>268</lpage>
          <pub-id pub-id-type="doi">10.1071/HC17016</pub-id>
          <pub-id pub-id-type="medline">29530137</pub-id>
          <pub-id pub-id-type="pii">HC17016</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gee</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Paterniti</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Ward</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Soederberg</surname>
              <given-names>MLM</given-names>
            </name>
          </person-group>
          <article-title>e-Patients perceptions of using personal health records for self-management support of chronic illness</article-title>
          <source>Comput Inform Nurs</source>
          <year>2015</year>
          <month>06</month>
          <volume>33</volume>
          <issue>6</issue>
          <fpage>229</fpage>
          <lpage>237</lpage>
          <pub-id pub-id-type="doi">10.1097/CIN.0000000000000151</pub-id>
          <pub-id pub-id-type="medline">25899440</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Cronin</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>GP</given-names>
            </name>
          </person-group>
          <article-title>Use of a patient portal during hospital admissions to surgical services</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2016</year>
          <volume>2016</volume>
          <fpage>1967</fpage>
          <lpage>1976</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28269956"/>
          </comment>
          <pub-id pub-id-type="medline">28269956</pub-id>
          <pub-id pub-id-type="pmcid">PMC5333326</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Redelmeier</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Kraus</surname>
              <given-names>NC</given-names>
            </name>
          </person-group>
          <article-title>Patterns in patient access and utilization of online medical records: analysis of MyChart</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>02</month>
          <day>06</day>
          <volume>20</volume>
          <issue>2</issue>
          <fpage>e43</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/2/e43/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8372</pub-id>
          <pub-id pub-id-type="medline">29410386</pub-id>
          <pub-id pub-id-type="pii">v20i2e43</pub-id>
          <pub-id pub-id-type="pmcid">PMC5820458</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metting</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Schrage</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kocks</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>van der Molen</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Assessing the needs and perspectives of patients with asthma and chronic obstructive pulmonary disease on patient web portals: focus group study</article-title>
          <source>JMIR Form Res</source>
          <year>2018</year>
          <month>11</month>
          <day>22</day>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>e22</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2018/2/e22/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/formative.8822</pub-id>
          <pub-id pub-id-type="medline">30684436</pub-id>
          <pub-id pub-id-type="pii">v2i2e22</pub-id>
          <pub-id pub-id-type="pmcid">PMC6334706</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McAlearney</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Sieck</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gaughan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fareed</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Volney</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Huerta</surname>
              <given-names>TR</given-names>
            </name>
          </person-group>
          <article-title>Patients' perceptions of portal use across care settings: qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>06</month>
          <day>06</day>
          <volume>21</volume>
          <issue>6</issue>
          <fpage>e13126</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/6/e13126/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13126</pub-id>
          <pub-id pub-id-type="medline">31172960</pub-id>
          <pub-id pub-id-type="pii">v21i6e13126</pub-id>
          <pub-id pub-id-type="pmcid">PMC6592494</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</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="http://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="ref57">
        <label>57</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>Gatto</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>HT</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Quandt</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Bertoni</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Arcury</surname>
              <given-names>TA</given-names>
            </name>
          </person-group>
          <article-title>Design considerations for patient portal adoption by low-income, older adults</article-title>
          <source>Proc SIGCHI Conf Hum Factor Comput Syst</source>
          <year>2015</year>
          <month>04</month>
          <volume>2015</volume>
          <fpage>3859</fpage>
          <lpage>3868</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27077140"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/2702123.2702392</pub-id>
          <pub-id pub-id-type="medline">27077140</pub-id>
          <pub-id pub-id-type="pmcid">PMC4827765</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Baek</surname>
              <given-names>HY</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Support for sustainable use of personal health records: understanding the needs of users as a first step towards patient-driven mobile health</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2017</year>
          <month>02</month>
          <day>23</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e19</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2017/2/e19/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.6021</pub-id>
          <pub-id pub-id-type="medline">28232300</pub-id>
          <pub-id pub-id-type="pii">v5i2e19</pub-id>
          <pub-id pub-id-type="pmcid">PMC5344982</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Menser</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McAlearney</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Optimizing the user experience: identifying opportunities to improve use of an inpatient portal</article-title>
          <source>Appl Clin Inform</source>
          <year>2018</year>
          <month>12</month>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>105</fpage>
          <lpage>113</lpage>
          <pub-id pub-id-type="doi">10.1055/s-0037-1621732</pub-id>
          <pub-id pub-id-type="medline">29444536</pub-id>
          <pub-id pub-id-type="pmcid">PMC5843764</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Geerts</surname>
              <given-names>PAF</given-names>
            </name>
            <name name-style="western">
              <surname>van der Weijden</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loeffen</surname>
              <given-names>PGM</given-names>
            </name>
            <name name-style="western">
              <surname>Janssen</surname>
              <given-names>LEF</given-names>
            </name>
            <name name-style="western">
              <surname>Almekinders</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wienhold</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Bos</surname>
              <given-names>GMJ</given-names>
            </name>
          </person-group>
          <article-title>Developing a patient portal for haematology patients requires involvement of all stakeholders and a customised design, tailored to the individual needs</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <month>07</month>
          <day>11</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>129</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1186/s12911-019-0868-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-019-0868-y</pub-id>
          <pub-id pub-id-type="medline">31296210</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-019-0868-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC6625061</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strudwick</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>McLean</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rossetti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McCann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Strauss</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Identifying indicators of meaningful patient portal use by psychiatric populations</article-title>
          <source>Inform Health Soc Care</source>
          <year>2020</year>
          <month>10</month>
          <day>01</day>
          <volume>45</volume>
          <issue>4</issue>
          <fpage>396</fpage>
          <lpage>409</lpage>
          <pub-id pub-id-type="doi">10.1080/17538157.2020.1776291</pub-id>
          <pub-id pub-id-type="medline">32603617</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tarver</surname>
              <given-names>WL</given-names>
            </name>
            <name name-style="western">
              <surname>Robb</surname>
              <given-names>BW</given-names>
            </name>
            <name name-style="western">
              <surname>Haggstrom</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <article-title>Usefulness and usability of a personal health record and survivorship care plan for colorectal cancer survivors: survey study</article-title>
          <source>JMIR Cancer</source>
          <year>2019</year>
          <month>08</month>
          <day>20</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e10692</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cancer.jmir.org/2019/2/e10692/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10692</pub-id>
          <pub-id pub-id-type="medline">31432780</pub-id>
          <pub-id pub-id-type="pii">v5i2e10692</pub-id>
          <pub-id pub-id-type="pmcid">PMC6719487</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Subbe</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Øvretveit</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Quinn</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Digital technology: opportunities and barriers for usage of personal health records in hospital</article-title>
          <source>Future Healthc J</source>
          <year>2019</year>
          <month>02</month>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>52</fpage>
          <lpage>56</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31098587"/>
          </comment>
          <pub-id pub-id-type="doi">10.7861/futurehosp.6-1-52</pub-id>
          <pub-id pub-id-type="medline">31098587</pub-id>
          <pub-id pub-id-type="pii">futurehealth</pub-id>
          <pub-id pub-id-type="pmcid">PMC6520086</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wildenbos</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Maasri</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Peute</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Older adults using a patient portal: registration and experiences, one year after implementation</article-title>
          <source>Digit Health</source>
          <year>2018</year>
          <volume>4</volume>
          <fpage>2055207618797883</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30186619"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/2055207618797883</pub-id>
          <pub-id pub-id-type="medline">30186619</pub-id>
          <pub-id pub-id-type="pii">10.1177_2055207618797883</pub-id>
          <pub-id pub-id-type="pmcid">PMC6120166</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hanna</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gill</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Newstead</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hawkins</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Osborne</surname>
              <given-names>RH</given-names>
            </name>
          </person-group>
          <article-title>Patient perspectives on a personally controlled electronic health record used in regional Australia</article-title>
          <source>Health Inf Manag</source>
          <year>2017</year>
          <month>01</month>
          <volume>46</volume>
          <issue>1</issue>
          <fpage>42</fpage>
          <lpage>48</lpage>
          <pub-id pub-id-type="doi">10.1177/1833358316661063</pub-id>
          <pub-id pub-id-type="medline">27486184</pub-id>
          <pub-id pub-id-type="pii">1833358316661063</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Proctor</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Mansell</surname>
              <given-names>PW</given-names>
            </name>
          </person-group>
          <article-title>Immunotherapy for cancer: an overview</article-title>
          <source>Can J Surg</source>
          <year>1976</year>
          <month>01</month>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1145/3290688.3290727</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Weiner</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>WF</given-names>
            </name>
          </person-group>
          <article-title>The wired patient: patterns of electronic patient portal use among patients with cardiac disease or diabetes</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>02</month>
          <day>20</day>
          <volume>17</volume>
          <issue>2</issue>
          <fpage>e42</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2015/2/e42/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.3157</pub-id>
          <pub-id pub-id-type="medline">25707036</pub-id>
          <pub-id pub-id-type="pii">v17i2e42</pub-id>
          <pub-id pub-id-type="pmcid">PMC4376207</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saripalle</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Runyan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Using HL7 FHIR to achieve interoperability in patient health record</article-title>
          <source>J Biomed Inform</source>
          <year>2019</year>
          <month>06</month>
          <volume>94</volume>
          <fpage>103188</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(19)30106-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2019.103188</pub-id>
          <pub-id pub-id-type="medline">31063828</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(19)30106-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wells</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mahony</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Perspectives of New Zealand patients and GPs at the beginning of patient portal implementation</article-title>
          <source>J Prim Health Care</source>
          <year>2019</year>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>315</fpage>
          <pub-id pub-id-type="doi">10.1071/HC19016</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kaur</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>mSwasthya: A mobile-enabled personal health record management system</article-title>
          <year>2015</year>
          <conf-name>Int Conf Comput Commun Autom</conf-name>
          <conf-date>2015</conf-date>
          <conf-loc>Greater Noida</conf-loc>
          <fpage>374</fpage>
          <lpage>379</lpage>
          <pub-id pub-id-type="doi">10.1109/CCAA.2015.7148404</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Portz</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Bayliss</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Bull</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Boxer</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Bekelman</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Gleason</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Czaja</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Using the technology acceptance model to explore user experience, intent to use, and use behavior of a patient portal among older adults with multiple chronic conditions: descriptive qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>04</month>
          <day>08</day>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>e11604</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/4/e11604/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11604</pub-id>
          <pub-id pub-id-type="medline">30958272</pub-id>
          <pub-id pub-id-type="pii">v21i4e11604</pub-id>
          <pub-id pub-id-type="pmcid">PMC6475817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aliakbarpoor</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Comai</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pozzi</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Designing a HL7 compatible personal health record for mobile devices</article-title>
          <year>2017</year>
          <conf-name>IEEE 3rd Int Forum Res Technol Soc Ind</conf-name>
          <conf-date>2017</conf-date>
          <conf-loc>Modena</conf-loc>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/RTSI.2017.8065881</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brandner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schreiweis</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Aguduri</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Bronsch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kunz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pensold</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Stein</surname>
              <given-names>KE</given-names>
            </name>
            <name name-style="western">
              <surname>Weiss</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Yüksekogul</surname>
              <given-names>Nilay</given-names>
            </name>
            <name name-style="western">
              <surname>Bergh</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Heinze</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>The patient portal of the personal cross-enterprise electronic health record (PEHR) in the Rhine-Neckar-Region</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2016</year>
          <volume>228</volume>
          <fpage>157</fpage>
          <lpage>161</lpage>
          <pub-id pub-id-type="medline">27577362</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>O'Leary</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Killarney</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>O'Hara</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Lohman</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Culver</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Liebovitz</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Cameron</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>Patients' and healthcare providers' perceptions of a mobile portal application for hospitalized patients</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2016</year>
          <month>09</month>
          <day>21</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>123</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-016-0363-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-016-0363-7</pub-id>
          <pub-id pub-id-type="medline">27653854</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-016-0363-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC5031299</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Roche</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Dente</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mueller</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>O'Reilly</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Sands</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Talmor</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Preferences of current and potential patients and family members regarding implementation of electronic communication portals in intensive care units</article-title>
          <source>Ann Am Thorac Soc</source>
          <year>2016</year>
          <month>03</month>
          <volume>13</volume>
          <issue>3</issue>
          <fpage>391</fpage>
          <lpage>400</lpage>
          <pub-id pub-id-type="doi">10.1513/AnnalsATS.201509-638OC</pub-id>
          <pub-id pub-id-type="medline">26700656</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marchak</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Cherven</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Williamson Lewis</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Meacham</surname>
              <given-names>LR</given-names>
            </name>
            <name name-style="western">
              <surname>Palgon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Escoffery</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mertens</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>User-centered design and enhancement of an electronic personal health record to support survivors of pediatric cancers</article-title>
          <source>Support Care Cancer</source>
          <year>2020</year>
          <month>08</month>
          <volume>28</volume>
          <issue>8</issue>
          <fpage>3905</fpage>
          <lpage>3914</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31853699"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s00520-019-05199-w</pub-id>
          <pub-id pub-id-type="medline">31853699</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00520-019-05199-w</pub-id>
          <pub-id pub-id-type="pmcid">PMC7880615</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woollen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prey</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sackeim</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Restaino</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Raza</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Bakken</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Feiner</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Patient experiences using an inpatient personal health record</article-title>
          <source>Appl Clin Inform</source>
          <year>2016</year>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>446</fpage>
          <lpage>460</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27437053"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2015-10-RA-0130</pub-id>
          <pub-id pub-id-type="medline">27437053</pub-id>
          <pub-id pub-id-type="pmcid">PMC4941852</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Eschler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Meas</surname>
              <given-names>PL</given-names>
            </name>
            <name name-style="western">
              <surname>Lozano</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McClure</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Ralston</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Pratt</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Integrating the patient portal into the health management work ecosystem: user acceptance of a novel prototype</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2016</year>
          <volume>2016</volume>
          <fpage>541</fpage>
          <lpage>550</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28269850"/>
          </comment>
          <pub-id pub-id-type="medline">28269850</pub-id>
          <pub-id pub-id-type="pmcid">PMC5333335</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fosser</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Sommer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Simón</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giraldo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Plazzotta</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Luna</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>User-centered design of a patient medication reconciliation module in an integrated personal health record</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <month>08</month>
          <day>21</day>
          <volume>264</volume>
          <fpage>1278</fpage>
          <lpage>1282</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI190432</pub-id>
          <pub-id pub-id-type="medline">31438131</pub-id>
          <pub-id pub-id-type="pii">SHTI190432</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Woollen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prey</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Restaino</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bakken</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Feiner</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sackeim</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>Interactive tools for inpatient medication tracking: a multi-phase study with cardiothoracic surgery patients</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>01</month>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>144</fpage>
          <lpage>158</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26744489"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv160</pub-id>
          <pub-id pub-id-type="medline">26744489</pub-id>
          <pub-id pub-id-type="pii">ocv160</pub-id>
          <pub-id pub-id-type="pmcid">PMC5009934</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Conway</surname>
              <given-names>NT</given-names>
            </name>
            <name name-style="western">
              <surname>Allardice</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Wake</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cunningham</surname>
              <given-names>SG</given-names>
            </name>
          </person-group>
          <article-title>User experiences of an electronic personal health record for diabetes</article-title>
          <source>J Diabetes Sci Technol</source>
          <year>2019</year>
          <month>07</month>
          <volume>13</volume>
          <issue>4</issue>
          <fpage>744</fpage>
          <lpage>750</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30585085"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1932296818818837</pub-id>
          <pub-id pub-id-type="medline">30585085</pub-id>
          <pub-id pub-id-type="pmcid">PMC6610613</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schladen</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Ljungberg</surname>
              <given-names>IH</given-names>
            </name>
            <name name-style="western">
              <surname>Underwood</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Groah</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>Exploration of the personal health record as a tool for spinal cord injury health self-management and coordination of care</article-title>
          <source>Top Spinal Cord Inj Rehabil</source>
          <year>2017</year>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>218</fpage>
          <lpage>225</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29339897"/>
          </comment>
          <pub-id pub-id-type="doi">10.1310/sci2303-218</pub-id>
          <pub-id pub-id-type="medline">29339897</pub-id>
          <pub-id pub-id-type="pmcid">PMC5562029</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bernhard</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Mahler</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Seidling</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Stützle</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ose</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baudendistel</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Wensing</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Szecsenyi</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Developing a shared patient-centered, web-based medication platform for type 2 diabetes patients and their health care providers: qualitative study on user requirements</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>03</month>
          <day>27</day>
          <volume>20</volume>
          <issue>3</issue>
          <fpage>e105</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/3/e105/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8666</pub-id>
          <pub-id pub-id-type="medline">29588269</pub-id>
          <pub-id pub-id-type="pii">v20i3e105</pub-id>
          <pub-id pub-id-type="pmcid">PMC5893891</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arcury</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Quandt</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Sandberg</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Latulipe</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Leng</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Talton</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Melius</surname>
              <given-names>KP</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bertoni</surname>
              <given-names>AG</given-names>
            </name>
          </person-group>
          <article-title>Patient portal utilization among ethnically diverse low income older adults: observational study</article-title>
          <source>JMIR Med Inform</source>
          <year>2017</year>
          <month>11</month>
          <day>14</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e47</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://medinform.jmir.org/2017/4/e47/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.8026</pub-id>
          <pub-id pub-id-type="medline">29138129</pub-id>
          <pub-id pub-id-type="pii">v5i4e47</pub-id>
          <pub-id pub-id-type="pmcid">PMC5705857</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>WS</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Managing patient-generated health data through mobile personal health records: analysis of usage data</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2018</year>
          <month>04</month>
          <day>09</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e89</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/4/e89/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.9620</pub-id>
          <pub-id pub-id-type="medline">29631989</pub-id>
          <pub-id pub-id-type="pii">v6i4e89</pub-id>
          <pub-id pub-id-type="pmcid">PMC5913571</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cabitza</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Simone</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>De Michelis</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>User-driven prioritization of features for a prospective InterPersonal Health Record: perceptions from the Italian context</article-title>
          <source>Comput Biol Med</source>
          <year>2015</year>
          <month>04</month>
          <volume>59</volume>
          <fpage>202</fpage>
          <lpage>210</lpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2014.03.009</pub-id>
          <pub-id pub-id-type="medline">24768267</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(14)00072-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>MacKay</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Moving beyond the rhetoric of shared decision-making: designing personal health record technology with young adults with type 1 diabetes</article-title>
          <source>Can J Diabetes</source>
          <year>2020</year>
          <month>07</month>
          <volume>44</volume>
          <issue>5</issue>
          <fpage>434</fpage>
          <lpage>441</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jcjd.2020.03.009</pub-id>
          <pub-id pub-id-type="medline">32616277</pub-id>
          <pub-id pub-id-type="pii">S1499-2671(20)30082-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fylan</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Caveney</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cartwright</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fylan</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Making it work for me: beliefs about making a personal health record relevant and useable</article-title>
          <source>BMC Health Serv Res</source>
          <year>2018</year>
          <month>06</month>
          <day>14</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>445</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-018-3254-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-018-3254-z</pub-id>
          <pub-id pub-id-type="medline">29898730</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-018-3254-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC6001055</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lalitaphanit</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Theeraroungchaisri</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Factors affecting community pharmacy customers? Decision to use personal health records via smartphone</article-title>
          <source>Thai J Pharm Sci (Supplement Issue)</source>
          <year>2016</year>
          <volume>40</volume>
          <fpage>167</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/3fx93uy2"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sieverink</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>S</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>J</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the implementation of a personal health record for chronic primary and secondary care: a mixed methods approach</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <month>11</month>
          <day>27</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>241</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-019-0969-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-019-0969-7</pub-id>
          <pub-id pub-id-type="medline">31775734</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-019-0969-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6882368</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Samet</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ishraque</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving personal health record (P3HR)</article-title>
          <source>Proc 7th Int Conf Softw Inf Eng</source>
          <year>2018</year>
          <fpage>22</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.1145/3220267.3220271</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Osterhage</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hartzler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Joe</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kanagat</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Demiris</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Use of patient portals for personal health information management: the older adult perspective</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2015</year>
          <volume>2015</volume>
          <fpage>1234</fpage>
          <lpage>1241</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26958263"/>
          </comment>
          <pub-id pub-id-type="medline">26958263</pub-id>
          <pub-id pub-id-type="pmcid">PMC4765678</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khaneghah</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Miguel-Cruz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bentley</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Stroulia</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ferguson-Pell</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Users' attitudes towards personal health records: a cross-sectional pilot study</article-title>
          <source>Appl Clin Inform</source>
          <year>2016</year>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>573</fpage>
          <lpage>586</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27437062"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2015-12-RA-0180</pub-id>
          <pub-id pub-id-type="medline">27437062</pub-id>
          <pub-id pub-id-type="pmcid">PMC4941861</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Forchuk</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Reiss</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>O'Regan</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ethridge</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Donelle</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rudnick</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Client perceptions of the mental health engagement network: a qualitative analysis of an electronic personal health record</article-title>
          <source>BMC Psychiatry</source>
          <year>2015</year>
          <month>10</month>
          <day>14</day>
          <volume>15</volume>
          <fpage>250</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpsychiatry.biomedcentral.com/articles/10.1186/s12888-015-0614-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12888-015-0614-7</pub-id>
          <pub-id pub-id-type="medline">26467210</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12888-015-0614-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC4606496</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marthick</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Janssen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cheema</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Alison</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Dhillon</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Feasibility of an interactive patient portal for monitoring physical activity, remote symptom reporting, and patient education in oncology: qualitative study</article-title>
          <source>JMIR Cancer</source>
          <year>2019</year>
          <month>11</month>
          <day>28</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e15539</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cancer.jmir.org/2019/2/e15539/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15539</pub-id>
          <pub-id pub-id-type="medline">31778123</pub-id>
          <pub-id pub-id-type="pii">v5i2e15539</pub-id>
          <pub-id pub-id-type="pmcid">PMC6908976</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sheehan</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Lucero</surname>
              <given-names>RJ</given-names>
            </name>
          </person-group>
          <article-title>Initial usability and feasibility evaluation of a personal health record-based self-management system for older adults</article-title>
          <source>EGEMS (Wash DC)</source>
          <year>2015</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>1152</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26290889"/>
          </comment>
          <pub-id pub-id-type="doi">10.13063/2327-9214.1152</pub-id>
          <pub-id pub-id-type="medline">26290889</pub-id>
          <pub-id pub-id-type="pii">egems1152</pub-id>
          <pub-id pub-id-type="pmcid">PMC4537150</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arcia</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Time to push: use of gestational age in the electronic health record to support delivery of relevant prenatal education content</article-title>
          <source>EGEMS (Wash DC)</source>
          <year>2017</year>
          <month>04</month>
          <day>20</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>5</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29881749"/>
          </comment>
          <pub-id pub-id-type="doi">10.13063/2327-9214.1281</pub-id>
          <pub-id pub-id-type="medline">29881749</pub-id>
          <pub-id pub-id-type="pmcid">PMC5983063</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fonseca</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Peixoto</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Braga</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Machado</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Abelha</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Smart mobile computing in pregnancy care</article-title>
          <source>Proc 34th Int Conf Comput Their Appl</source>
          <year>2019</year>
          <fpage>209</fpage>
          <lpage>212</lpage>
          <pub-id pub-id-type="doi">10.29007/sr6q</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref99">
        <label>99</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iatraki</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kondylakis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Koumakis</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chatzimina</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kazantzaki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Marias</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tsiknakis</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Personal Health Information Recommender: implementing a tool for the empowerment of cancer patients</article-title>
          <source>Ecancermedicalscience</source>
          <year>2018</year>
          <volume>12</volume>
          <fpage>851</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30079113"/>
          </comment>
          <pub-id pub-id-type="doi">10.3332/ecancer.2018.851</pub-id>
          <pub-id pub-id-type="medline">30079113</pub-id>
          <pub-id pub-id-type="pii">can-12-851</pub-id>
          <pub-id pub-id-type="pmcid">PMC6057655</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van den Heuvel</surname>
              <given-names>SCGH</given-names>
            </name>
            <name name-style="western">
              <surname>Meije</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Regeer</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sinnema</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Riemersma</surname>
              <given-names>RF</given-names>
            </name>
            <name name-style="western">
              <surname>Kupka</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>The user experiences and clinical outcomes of an online personal health record to support self-management of bipolar disorder: A pretest-posttest pilot study</article-title>
          <source>J Affect Disord</source>
          <year>2018</year>
          <month>10</month>
          <day>01</day>
          <volume>238</volume>
          <fpage>261</fpage>
          <lpage>268</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jad.2018.05.069</pub-id>
          <pub-id pub-id-type="medline">29894931</pub-id>
          <pub-id pub-id-type="pii">S0165-0327(18)30030-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ryu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Heo</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>SY</given-names>
            </name>
          </person-group>
          <article-title>Impact of an electronic health record-integrated personal health record on patient participation in health care: development and randomized controlled trial of myhealthkeeper</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>12</month>
          <day>07</day>
          <volume>19</volume>
          <issue>12</issue>
          <fpage>e401</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2017/12/e401/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8867</pub-id>
          <pub-id pub-id-type="medline">29217503</pub-id>
          <pub-id pub-id-type="pii">v19i12e401</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cronin</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Conway</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Condon</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jerome</surname>
              <given-names>RN</given-names>
            </name>
            <name name-style="western">
              <surname>Byrne</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Patient and healthcare provider views on a patient-reported outcomes portal</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>11</month>
          <day>01</day>
          <volume>25</volume>
          <issue>11</issue>
          <fpage>1470</fpage>
          <lpage>1480</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy111</pub-id>
          <pub-id pub-id-type="medline">30239733</pub-id>
          <pub-id pub-id-type="pii">5101446</pub-id>
          <pub-id pub-id-type="pmcid">PMC6213079</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fuji</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Abbott</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Galt</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>A qualitative study of how patients with type 2 diabetes use an electronic stand-alone personal health record</article-title>
          <source>Telemed J E Health</source>
          <year>2015</year>
          <month>04</month>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>296</fpage>
          <lpage>300</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2014.0084</pub-id>
          <pub-id pub-id-type="medline">25614996</pub-id>
          <pub-id pub-id-type="pmcid">PMC4378613</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ploner</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Neurath</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Schoenthaler</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zielke</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Prokosch</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Concept to gain trust for a German personal health record system using public cloud and FHIR</article-title>
          <source>J Biomed Inform</source>
          <year>2019</year>
          <month>07</month>
          <volume>95</volume>
          <fpage>103212</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(19)30131-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2019.103212</pub-id>
          <pub-id pub-id-type="medline">31112761</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(19)30131-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Farinango</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Benavides</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Cerón</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>López</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Álvarez</surname>
              <given-names>RE</given-names>
            </name>
          </person-group>
          <article-title>Human-centered design of a personal health record system for metabolic syndrome management based on the ISO 9241-210:2010 standard</article-title>
          <source>J Multidiscip Healthc</source>
          <year>2018</year>
          <volume>11</volume>
          <fpage>21</fpage>
          <lpage>37</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.doi.org/10.2147/JMDH.S150976"/>
          </comment>
          <pub-id pub-id-type="doi">10.2147/JMDH.S150976</pub-id>
          <pub-id pub-id-type="medline">29386903</pub-id>
          <pub-id pub-id-type="pii">jmdh-11-021</pub-id>
          <pub-id pub-id-type="pmcid">PMC5767088</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pohlmann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kunz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ose</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Winkler</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Brandner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Poss-Doering</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Szecsenyi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wensing</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Digitalizing health services by implementing a personal electronic health record in Germany: qualitative analysis of fundamental prerequisites from the perspective of selected experts</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>01</month>
          <day>29</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>e15102</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/1/e15102/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15102</pub-id>
          <pub-id pub-id-type="medline">32012060</pub-id>
          <pub-id pub-id-type="pii">v22i1e15102</pub-id>
          <pub-id pub-id-type="pmcid">PMC7016629</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Roehrs</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>da Costa</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>da Rosa</surname>
              <given-names>RR</given-names>
            </name>
          </person-group>
          <article-title>OmniPHR: a distributed architecture model to integrate personal health records</article-title>
          <source>J Biomed Inform</source>
          <year>2017</year>
          <month>12</month>
          <volume>71</volume>
          <fpage>70</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(17)30108-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2017.05.012</pub-id>
          <pub-id pub-id-type="medline">28545835</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(17)30108-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jing</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>An empirical study on the features influencing users? Adoption towards personal health records system</article-title>
          <source>13th Int Conf Serv Syst Serv Manag</source>
          <year>2016</year>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/icsssm.2016.7538554</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Poss-Doering</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kunz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pohlmann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hofmann</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kiel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Winkler</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Ose</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Szecsenyi</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Utilizing a prototype patient-controlled electronic health record in Germany: qualitative analysis of user-reported perceptions and perspectives</article-title>
          <source>JMIR Form Res</source>
          <year>2018</year>
          <month>08</month>
          <day>03</day>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>e10411</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2018/2/e10411/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10411</pub-id>
          <pub-id pub-id-type="medline">30684411</pub-id>
          <pub-id pub-id-type="pii">v2i2e10411</pub-id>
          <pub-id pub-id-type="pmcid">PMC6334712</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gagnon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Payne-Gagnon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Breton</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fortin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Khoury</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dolovich</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Price</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wiljer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bartlett</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Archer</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Adoption of electronic personal health records in Canada: perceptions of stakeholders</article-title>
          <source>Int J Health Policy Manag</source>
          <year>2016</year>
          <month>07</month>
          <day>01</day>
          <volume>5</volume>
          <issue>7</issue>
          <fpage>425</fpage>
          <lpage>433</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27694670"/>
          </comment>
          <pub-id pub-id-type="doi">10.15171/ijhpm.2016.36</pub-id>
          <pub-id pub-id-type="medline">27694670</pub-id>
          <pub-id pub-id-type="pmcid">PMC4930348</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ruhi</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Majedi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Int Conf e-Health 2015</source>
          <year>2015</year>
          <fpage>43</fpage>
          <lpage>54</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.iadisportal.org/digital-library/mdownload/consumer-adoption-of-personal-health-records-an-empirical-investigation-of-personal-technology-factors"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref112">
        <label>112</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Urbauer</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sauermann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Frohner</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Forjan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pohn</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mense</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Applicability of IHE/Continua components for PHR systems: learning from experiences</article-title>
          <source>Comput Biol Med</source>
          <year>2015</year>
          <month>04</month>
          <volume>59</volume>
          <fpage>186</fpage>
          <lpage>193</lpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2013.12.003</pub-id>
          <pub-id pub-id-type="medline">24374230</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(13)00354-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref113">
        <label>113</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baudendistel</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Winkler</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Kamradt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Brophy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Längst</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Eckrich</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Heinze</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Bergh</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Szecsenyi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ose</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Cross-sectoral cancer care: views from patients and health care professionals regarding a personal electronic health record</article-title>
          <source>Eur J Cancer Care (Engl)</source>
          <year>2016</year>
          <month>02</month>
          <day>03</day>
          <volume>26</volume>
          <issue>2</issue>
          <fpage>e12429</fpage>
          <pub-id pub-id-type="doi">10.1111/ecc.12429</pub-id>
          <pub-id pub-id-type="medline">26840784</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref114">
        <label>114</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vimalachandran</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ji</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Improving accessibility of the Australian My Health Records while preserving privacy and security of the system</article-title>
          <source>Health Inf Sci Syst</source>
          <year>2020</year>
          <month>12</month>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <pub-id pub-id-type="doi">10.1007/s13755-020-00126-4</pub-id>
          <pub-id pub-id-type="medline">33088487</pub-id>
          <pub-id pub-id-type="pii">126</pub-id>
          <pub-id pub-id-type="pmcid">PMC7544771</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref115">
        <label>115</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Dolezel</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Usability of web-based personal health records: an analysis of consumers' perspectives</article-title>
          <source>Perspect Health Inf Manag</source>
          <year>2016</year>
          <volume>13</volume>
          <fpage>1f</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27134611"/>
          </comment>
          <pub-id pub-id-type="medline">27134611</pub-id>
          <pub-id pub-id-type="pmcid">PMC4832130</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref116">
        <label>116</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pang</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McKay</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Privacy concerns of the Australian My Health Record: implications for other large-scale opt-out personal health records</article-title>
          <source>Inform Process Manag</source>
          <year>2020</year>
          <month>11</month>
          <volume>57</volume>
          <issue>6</issue>
          <fpage>102364</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ipm.2020.102364</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Rozenblum</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>WY</given-names>
            </name>
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Stade</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>McNally</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bourie</surname>
              <given-names>PQ</given-names>
            </name>
            <name name-style="western">
              <surname>Massaro</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bokser</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dwyer</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Greysen</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Thornton</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Dalal</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>Acute care patient portals: a qualitative study of stakeholder perspectives on current practices</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>04</month>
          <day>01</day>
          <volume>24</volume>
          <issue>e1</issue>
          <fpage>e9</fpage>
          <lpage>e17</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw081</pub-id>
          <pub-id pub-id-type="medline">27357830</pub-id>
          <pub-id pub-id-type="pii">ocw081</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fernando</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fidge</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sahama</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Design guidelines for effective occupation-based personal health records</article-title>
          <source>Proc Australas Comput Sci Week Multiconf</source>
          <year>2020</year>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1145/3373017.3373042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abd-Alrazaq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bewick</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Farragher</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gardner</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Factors affecting patients' use of electronic personal health records in england: cross-sectional study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>07</month>
          <day>31</day>
          <volume>21</volume>
          <issue>7</issue>
          <fpage>e12373</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/7/e12373/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12373</pub-id>
          <pub-id pub-id-type="medline">31368442</pub-id>
          <pub-id pub-id-type="pii">v21i7e12373</pub-id>
          <pub-id pub-id-type="pmcid">PMC6693305</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref120">
        <label>120</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alpert</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Krist</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Aycock</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Kreps</surname>
              <given-names>GL</given-names>
            </name>
          </person-group>
          <article-title>Applying multiple methods to comprehensively evaluate a patient portal's effectiveness to convey information to patients</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>05</month>
          <day>17</day>
          <volume>18</volume>
          <issue>5</issue>
          <fpage>e112</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2016/5/e112/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.5451</pub-id>
          <pub-id pub-id-type="medline">27188953</pub-id>
          <pub-id pub-id-type="pii">v18i5e112</pub-id>
          <pub-id pub-id-type="pmcid">PMC4887660</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rau</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kao</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chiu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Fuad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chiu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Importance-performance analysis of personal health records in Taiwan: a web-based survey</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>04</month>
          <day>27</day>
          <volume>19</volume>
          <issue>4</issue>
          <fpage>e131</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/4/e131/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7065</pub-id>
          <pub-id pub-id-type="medline">28450273</pub-id>
          <pub-id pub-id-type="pii">v19i4e131</pub-id>
          <pub-id pub-id-type="pmcid">PMC5427249</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdekhoda</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dehnad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khezri</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>The effect of confidentiality and privacy concerns on adoption of personal health record from patient’s perspective</article-title>
          <source>Health Technol</source>
          <year>2019</year>
          <month>1</month>
          <day>6</day>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>463</fpage>
          <lpage>469</lpage>
          <pub-id pub-id-type="doi">10.1007/s12553-018-00287-z</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>BL</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Terry</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cejic</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Thind</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Implementing and using a patient portal: a qualitative exploration of patient and provider perspectives on engaging patients</article-title>
          <source>J Innov Health Inform</source>
          <year>2016</year>
          <month>07</month>
          <day>04</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>848</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.doi.org/10.14236/jhi.v23i2.848"/>
          </comment>
          <pub-id pub-id-type="medline">27869582</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref124">
        <label>124</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tao</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shao</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Qu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Factors affecting consumer acceptance of an online health information portal among young internet users</article-title>
          <source>Comput Inform Nurs</source>
          <year>2018</year>
          <month>11</month>
          <volume>36</volume>
          <issue>11</issue>
          <fpage>530</fpage>
          <lpage>539</lpage>
          <pub-id pub-id-type="doi">10.1097/CIN.0000000000000467</pub-id>
          <pub-id pub-id-type="medline">30074918</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vassilakopoulou</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Grisot</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aanestad</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Between personal and common: the design of hybrid information spaces</article-title>
          <source>Comput Supported Coop Work</source>
          <year>2018</year>
          <month>1</month>
          <day>8</day>
          <volume>27</volume>
          <issue>3-6</issue>
          <fpage>1085</fpage>
          <lpage>1112</lpage>
          <pub-id pub-id-type="doi">10.1007/s10606-017-9304-y</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Walsh</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hemsley</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Allan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Balandin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Georgiou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Higgins</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>McCarthy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hill</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The e-Health literacy demands of Australia's My Health Record: a heuristic evaluation of usability</article-title>
          <source>Perspect Health Inf Manag</source>
          <year>2017</year>
          <volume>14</volume>
          <issue>Fall</issue>
          <fpage>1f</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29118683"/>
          </comment>
          <pub-id pub-id-type="medline">29118683</pub-id>
          <pub-id pub-id-type="pmcid">PMC5653954</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barnsteiner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>RG</given-names>
            </name>
          </person-group>
          <article-title>Medication reconciliation</article-title>
          <source>Patient Safety and Quality: An Evidence-Based Handbook for Nurses</source>
          <year>2008</year>
          <publisher-loc>Rockville</publisher-loc>
          <publisher-name>Agency for Healthcare Research and Quality</publisher-name>
          <fpage>459</fpage>
          <lpage>472</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref128">
        <label>128</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Triggle</surname>
              <given-names>Nick</given-names>
            </name>
          </person-group>
          <article-title>Covid-19: Surge leaves key hospital services "in crisis"</article-title>
          <source>BBC</source>
          <year>2021</year>
          <month>01</month>
          <day>14</day>
          <access-date>2021-02-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bbc.com/news/health-55575112">https://www.bbc.com/news/health-55575112</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref129">
        <label>129</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yamamoto</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Takahashi</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Urasaki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nagayasu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Shimamoto</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tateyama</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Matsuzaki</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kobayashi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kubo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mito</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Abe</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Matsuura</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Iwami</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Health observation app for COVID-19 symptom tracking integrated with personal health records: proof of concept and practical use study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2020</year>
          <month>07</month>
          <day>06</day>
          <volume>8</volume>
          <issue>7</issue>
          <fpage>e19902</fpage>
          <pub-id pub-id-type="doi">10.2196/19902</pub-id>
          <pub-id pub-id-type="medline">32568728</pub-id>
          <pub-id pub-id-type="pii">v8i7e19902</pub-id>
          <pub-id pub-id-type="pmcid">PMC7340163</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref130">
        <label>130</label>
        <nlm-citation citation-type="web">
          <article-title>HL7 Personal Health Record System Functional Model, Release 1</article-title>
          <source>Health Level Seven International</source>
          <year>2014</year>
          <access-date>2021-04-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=88">http://www.hl7.org/implement/standards/product_brief.cfm?product_id=88</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref131">
        <label>131</label>
        <nlm-citation citation-type="web">
          <article-title>Personal Health Record System Functional Model (PHR-S FM), R1</article-title>
          <source>Health Level Seven International</source>
          <year>2014</year>
          <access-date>2021-04-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=88">http://www.hl7.org/implement/standards/product_brief.cfm?product_id=88</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref132">
        <label>132</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Safran</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bloomrosen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hammond</surname>
              <given-names>WE</given-names>
            </name>
            <name name-style="western">
              <surname>Labkoff</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Markel-Fox</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Detmer</surname>
              <given-names>DE</given-names>
            </name>
            <name name-style="western">
              <surname>Expert</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Toward a national framework for the secondary use of health data: an American Medical Informatics Association White Paper</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2007</year>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/17077452"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M2273</pub-id>
          <pub-id pub-id-type="medline">17077452</pub-id>
          <pub-id pub-id-type="pii">M2273</pub-id>
          <pub-id pub-id-type="pmcid">PMC2329823</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
