<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v23i4e25094</article-id>
      <article-id pub-id-type="pmid">33847591</article-id>
      <article-id pub-id-type="doi">10.2196/25094</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>Blockchain 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>da Costa</surname>
            <given-names>Cristiano Andrew</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kuo</surname>
            <given-names>Tsung-Ting</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lee</surname>
            <given-names>Jae-Ho</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Fang</surname>
            <given-names>Hao Sen Andrew</given-names>
          </name>
          <degrees>MBBS, MMed, MTech</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>SingHealth Polyclinics</institution>
            <addr-line>167, Jalan Bukit Merah</addr-line>
            <addr-line>Connection One, Tower 5, #15-10</addr-line>
            <addr-line>Singapore, 150167</addr-line>
            <country>Singapore</country>
            <phone>65 93690001</phone>
            <email>andrew.fang.h.s@singhealth.com.sg</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4761-9356</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>Teng Hwee</given-names>
          </name>
          <degrees>MBBS, FRANZCR</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0649-9714</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>Yan Fang Cheryl</given-names>
          </name>
          <degrees>MBBS, MMed, FCFP</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2538-1263</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>Chun Jin Marcus</given-names>
          </name>
          <degrees>MBBS, MMed, FRCOphth, MTech</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4849-6194</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>SingHealth Polyclinics</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>National University Health System</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>SingHealth Community Hospitals</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Hao Sen Andrew Fang <email>andrew.fang.h.s@singhealth.com.sg</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>4</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>13</day>
        <month>4</month>
        <year>2021</year>
      </pub-date>
      <volume>23</volume>
      <issue>4</issue>
      <elocation-id>e25094</elocation-id>
      <history>
        <date date-type="received">
          <day>17</day>
          <month>10</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>21</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>25</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>16</day>
          <month>3</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Hao Sen Andrew Fang, Teng Hwee Tan, Yan Fang Cheryl Tan, Chun Jin Marcus Tan. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 13.04.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 http://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/4/e25094" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Blockchain technology has the potential to enable more secure, transparent, and equitable data management. In the health care domain, it has been applied most frequently to electronic health records. In addition to securely managing data, blockchain has significant advantages in distributing data access, control, and ownership to end users. Due to this attribute, among others, the use of blockchain to power personal health records (PHRs) is especially appealing.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This review aims to examine the current landscape, design choices, limitations, and future directions of blockchain-based PHRs.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Adopting the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-analyses) guidelines, a cross-disciplinary systematic review was performed in July 2020 on all eligible articles, including gray literature, from the following 8 databases: ACM, IEEE Xplore, MEDLINE, ScienceDirect, Scopus, SpringerLink, Web of Science, and Google Scholar. Three reviewers independently performed a full-text review and data abstraction using a standardized data collection form.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 58 articles met the inclusion criteria. In the review, we found that the blockchain PHR space has matured over the past 5 years, from purely conceptual ideas initially to an increasing trend of publications describing prototypes and even implementations. Although the eventual application of blockchain in PHRs is intended for the health care industry, the majority of the articles were found in engineering or computer science publications. Among the blockchain PHRs described, permissioned blockchains and off-chain storage were the most common design choices. Although 18 articles described a tethered blockchain PHR, all of them were at the conceptual stage.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This review revealed that although research interest in blockchain PHRs is increasing and that the space is maturing, this technology is still largely in the conceptual stage. Being the first systematic review on blockchain PHRs, this review should serve as a basis for future reviews to track the development of the space.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>blockchain</kwd>
        <kwd>personal health records</kwd>
        <kwd>electronic health records</kwd>
        <kwd>distributed ledger</kwd>
        <kwd>systematic review</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Personal health records (PHRs) are a form of electronic health records (EHRs). PHRs are unique in that patients themselves can access, manage, and share their health information [<xref ref-type="bibr" rid="ref1">1</xref>]. The benefits of PHRs include patient empowerment, which leads to improved outcomes and reduced health care costs [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. Although interest in PHRs has been increasing, their adoption remains low [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. One of the oft-cited reasons is related to privacy and security concerns owing to an increasing trend of health information breaches [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. Another reason is the lack of perceived usefulness to patients [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
        <p>Blockchain technology was introduced through Bitcoin in 2008 [<xref ref-type="bibr" rid="ref8">8</xref>]. It is considered a general-purpose technology and has since been successfully applied across several different industries [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. In the health care industry, EHRs were found to be the most commonly used case for blockchain applications [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Compared with conventional data management methods that rely on on-premise data servers or third-party cloud services, blockchain’s distributed ledger technology offers a novel alternative. This could potentially address the privacy and security concerns surrounding EHRs [<xref ref-type="bibr" rid="ref15">15</xref>]. Specifically for application to PHRs, blockchain also has the ability to decentralize control and incorporate incentive mechanisms through smart contracts, which can further entice its general use and increase adoption [<xref ref-type="bibr" rid="ref16">16</xref>]. These advantages, among others, have motivated efforts to test the feasibility and implement blockchain PHRs [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>The research space in which EHRs and blockchain intersect is still in its infancy, with the first blockchain EHR introduced in 2016 [<xref ref-type="bibr" rid="ref20">20</xref>]. Systematic reviews covering this space so far have considered EHRs as a collective entity. Mayer et al [<xref ref-type="bibr" rid="ref21">21</xref>] provided an overview of the ecosystem of blockchain EHRs while also proposing a taxonomy for the space. Shuaib et al [<xref ref-type="bibr" rid="ref22">22</xref>] looked at the main areas of focus when implementing a blockchain EHR and the remaining issues to be addressed, whereas Vazirani et al [<xref ref-type="bibr" rid="ref23">23</xref>] assessed the feasibility of blockchain as a method of managing health care records efficiently.</p>
        <p>Given that one of the inherent properties of blockchain is its decentralized nature, in which data ownership is placed in the hands of individual users, some have proposed that blockchain may be more suitably applied to PHRs specifically rather than EHRs in general [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. In this paper, we aim to systematically review the following: (1) the current landscape and trends of blockchain-based PHRs (blockchain PHRs), (2) the attributes of various blockchain PHRs that have been described, and (3) the current limitations and future directions for blockchain PHRs. To the best of our knowledge, this is the first systematic review examining blockchain with PHRs. We hope that this review will serve as a useful reference, especially for those intending to develop a blockchain PHR and for future reviews in this area.</p>
        <p>To provide more context for subsequent sections of this paper, we will first explain pertinent blockchain concepts and take the opportunity to introduce some terminology specific to blockchain. This is by no means an exhaustive explanation of blockchain.</p>
      </sec>
      <sec>
        <title>What Is a Blockchain?</title>
        <p>A blockchain can be thought of as a shared (or distributed) database that is spread across multiple sites and participants. For new data to be added to a blockchain, they are first compiled into a <italic>block</italic>, which is simply a collection of records to be added to the database. The block is then combined with some data (a <italic>hash key</italic>) from the previous block through a cryptographic technique called <italic>hashing</italic> before it is added. As it combines the previous block’s hash key, each new block is tied to all its predecessors in the form of a chain—hence the term <italic>blockchain</italic> (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Illustration of how blocks of data are linked together in a blockchain through hashing. To add a new record (eg, Record #7) to the blockchain, this is first grouped with other records (Records #6, #8, and #9). The group of records is then combined with a hash key from the previous block (hash key 2) and then put through a hashing algorithm to produce a new hash key (hash key 3). The new records, along with hash keys 2 and 3, are now part of a new block (Block N+3) that has been added to the blockchain. This process continues as new records are added.</p>
          </caption>
          <graphic xlink:href="jmir_v23i4e25094_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Types of Blockchains and Their Properties</title>
        <p>Before data can be added to a blockchain, its users need to agree or reach <italic>consensus</italic>. This is achieved through a <italic>consensus algorithm</italic>. A well-known consensus algorithm is the proof of work (PoW) algorithm. PoW is used in the Bitcoin and Ethereum blockchain network protocols [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. In the PoW algorithm, users (also known as <italic>miners</italic>) compete in computational tasks to reach consensus. The winning miner of each block’s task is usually given a reward [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <p>Blockchains can be classified into the following three types, depending on which participants are allowed in the consensus algorithm [<xref ref-type="bibr" rid="ref28">28</xref>]:</p>
        <list list-type="order">
          <list-item>
            <p>Public: anyone can participate in the consensus algorithm. Examples include Bitcoin and Ethereum [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
          </list-item>
          <list-item>
            <p>Consortium: a select (or permissioned) group of entities can participate in the consensus algorithm. Examples include Hyperledger Fabric (HF), Quorum, and Corda [<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>].</p>
          </list-item>
          <list-item>
            <p>Private: only a single entity operates the consensus algorithm and controls the addition of new data.</p>
          </list-item>
        </list>
        <p>Public blockchains are sometimes referred to as permissionless blockchains, whereas consortium and private blockchains are collectively termed permissioned blockchains.</p>
        <p>The three types of blockchains differ in the following properties:</p>
        <list list-type="order">
          <list-item>
            <p>Decentralization: unlike traditional databases that are owned by a specific entity, a decentralized blockchain can allow every user to own the data collectively. Using the illustration in <xref rid="figure1" ref-type="fig">Figure 1</xref> as an example, a decentralized blockchain would contain all the records, but only one user owns records #1, #3, #4, #6, and #8, and another user separately owns records #2, #5, #7, and #9.</p>
          </list-item>
          <list-item>
            <p>Immutability: because of the underlying chain structure, once data have been added to the blockchain, they cannot be tampered with. Changing a record would alter the hash key and effectively cause a break in the chain.</p>
          </list-item>
          <list-item>
            <p>Transparency (with privacy): the entire blockchain can be made publicly viewable while preserving privacy by masking each individual record using cryptography. To unmask one’s own records, a private key is required.</p>
          </list-item>
        </list>
        <p><xref ref-type="table" rid="table1">Table 1</xref> provides a summary of the different types of blockchains and their properties, with an example of each type in the health care setting.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Comparison of public, consortium, and private blockchains.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="190"/>
            <col width="270"/>
            <col width="270"/>
            <col width="270"/>
            <thead>
              <tr valign="top">
                <td>Variables</td>
                <td colspan="3">Type of blockchain</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Public</td>
                <td>Consortium</td>
                <td>Private</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Participation in consensus protocol</td>
                <td>Anyone</td>
                <td>Select (or permissioned) group of entities</td>
                <td>A single entity</td>
              </tr>
              <tr valign="top">
                <td>Decentralization</td>
                <td>Yes</td>
                <td>Partial</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Immutability</td>
                <td>Tamperproof</td>
                <td>Could be tampered with</td>
                <td>Could be tampered with</td>
              </tr>
              <tr valign="top">
                <td>Transparency</td>
                <td>Public</td>
                <td>Can be public or restricted</td>
                <td>Can be public or restricted</td>
              </tr>
              <tr valign="top">
                <td>Example in health care setting</td>
                <td>A transnational, open EMR<sup>a</sup> system in which anyone (eg, health care institutions, patients) may choose to contribute their own resources to maintain health records of all patients who use the EMR system</td>
                <td>A national EMR system in which selected health care institutions collectively maintain the health care records of their patients</td>
                <td>An institution-based EMR system in which only a single institution maintains the health records of its own patients</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>EMR: electronic medical record.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Scalability and Smart Contracts</title>
        <p>Finally, we will briefly explain the two concepts of <italic>scalability</italic> and <italic>smart contracts</italic>, which will be relevant to subsequent parts of this paper.</p>
        <p>Scalability refers to the capacity of a blockchain to store and process transactions. It generally relates to the size and frequency of transactions a blockchain can handle. For example, Bitcoin’s block size is limited to 1 megabyte, and each block is added every 10 minutes. This translates to a rate of approximately 7 transactions per second. Various solutions have been proposed to improve scalability. One such solution is to store data <italic>off-chain</italic> (instead of on-chain), and another solution is to use <italic>side-chains</italic> (linked to the main chain) to enable larger transaction volumes to be processed in parallel. Given that health care data are estimated to reach as much as 2314 exabytes generated yearly by 2020, it is crucial for almost all blockchain-based health care applications to achieve a certain level of scalability [<xref ref-type="bibr" rid="ref32">32</xref>].</p>
        <p>Smart contracts are programmable computer rules. Blockchain is a digital database that allows for the implementation of smart contracts, which can be automatically triggered to execute when predefined conditions are satisfied. For example, a smart contract can be programmed to issue tokens on the blockchain each time a user records his or her blood pressure. These tokens can then be used to pay for health care services. Such smart contracts can thus potentially be used to enable incentive structures to encourage certain positive user behaviors.</p>
        <p>In this systematic review, particularly focused on the blockchain component of blockchain PHRs, we will pay particular attention to the (1) type of blockchain, (2) scalability solutions, and (3) smart contract–based incentive structures.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>While conducting and reporting this systematic literature review, the guidelines described in the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-analyses) statement were adopted [<xref ref-type="bibr" rid="ref33">33</xref>]. This type of literature review was selected because the goal was to identify articles on blockchain PHRs and to summarize the current landscape, design choices, limitations, and future directions. Unlike a meta-analysis, this review did not require any data synthesis. Quality assessment was not performed because the intention was to achieve a collective understanding of the efforts and ideas rather than judging the quality of various blockchain PHRs.</p>
        <p>The presented systematic review was carried out by defining the following activities:</p>
        <list list-type="order">
          <list-item>
            <p>Research questions</p>
          </list-item>
          <list-item>
            <p>Search strategy</p>
          </list-item>
          <list-item>
            <p>Article selection</p>
          </list-item>
          <list-item>
            <p>Data abstraction</p>
          </list-item>
        </list>
        <sec>
          <title>Research Questions</title>
          <p>For this review, there were 3 research questions we aimed to address:</p>
          <list list-type="order">
            <list-item>
              <p>What are the current landscape and trends of blockchain PHRs in terms of interest groups, geography, and maturity level?</p>
            </list-item>
            <list-item>
              <p>What were the key design decisions made for the blockchain PHRs described?</p>
            </list-item>
            <list-item>
              <p>What are the current limitations faced by blockchain PHRs and future directions?</p>
            </list-item>
          </list>
        </sec>
        <sec>
          <title>Search Strategy</title>
          <p>The following search string was used: “blockchain” AND (“health record*” OR “medical record*” OR “*EHR*” OR “*EMR*” OR “*PHR*”). Articles in the following databases were searched: (1) ACM, (2) IEEE Xplore, (3) MEDLINE, (4) ScienceDirect, (5) Scopus, (6) SpringerLink, (7) Web of Science, and (8) Google Scholar. For databases whose search engines did not enable the use of wildcards, the search was widened to include abstracts and keywords, and Microsoft Excel was subsequently used to filter the returned list by applying the search string to the titles.</p>
          <p>As the space is still in its infancy stage, Google Scholar was included as a search database to incorporate relevant gray literature in this review. This decision was supported by systematic reviews by Holbl et al [<xref ref-type="bibr" rid="ref34">34</xref>] and Kuo et al [<xref ref-type="bibr" rid="ref35">35</xref>] on blockchain in the health care domain, which had found valuable information residing in gray literature.</p>
        </sec>
        <sec>
          <title>Article Selection</title>
          <p>Once the articles were obtained, we applied the following inclusion and exclusion criteria to select articles for the final review. The inclusion criteria were as follows: a health record system that had (1) a patient-facing component and (2) used blockchain in its health record system. The exclusion criteria were as follows: (1) duplicate articles, (2) review articles, (3) articles that did not have full text available, and (4) articles whose full text was not in English.</p>
          <p>The selection was performed in a stepwise manner. First, duplicate articles returned from multiple databases were excluded. Second, the titles of the articles were reviewed and those that were not relevant to the topic were discarded. Third, the abstracts of the articles were reviewed and those whose main focus was not on blockchains and EHR or PHR and those that were review articles were also discarded. Those that looked at EHRs at this stage were retained because some EHRs would have a patient-facing component but might not have been explicitly mentioned in the title or abstract. Finally, the full text was reviewed and those that did not have a PHR element in the EHR were discarded. At this stage, those that did not have full text available or whose full text was not in English were also excluded.</p>
        </sec>
        <sec>
          <title>Data Abstraction</title>
          <p>For data abstraction, a standardized data collection form was developed using Microsoft Excel. A full-text review of each selected study was performed independently by 3 reviewers who are knowledgeable about blockchain and health records. For discrepancies in the abstracted data, the reviewers performed a repeat review of the articles together to reach a consensus.</p>
          <p>For the interest groups, author affiliations, publishers, and publications were used as a proxy. As this space is situated at the intersection of computer science (CS), engineering, and medicine, we classified the publications into either (1) CS or engineering, (2) medical, or (3) general. For maturity level, the classification used by Chukwu et al [<xref ref-type="bibr" rid="ref12">12</xref>] was modified, and the projects were classified as <italic>concept/model/framework</italic>, <italic>prototypes</italic>, and <italic>pilots or implementations</italic>. A prototype was considered to have both a working front-end and back-end system, and a pilot or implementation had to be a product that was released for use in the real world. If an article described systems at multiple levels of maturity (eg, a framework and a prototype), only the more mature level described was abstracted.</p>
          <p>Many design choices must be made when developing a blockchain PHR. To keep this review manageable, the review focused on high-level design decisions [<xref ref-type="bibr" rid="ref36">36</xref>]. To ensure a comprehensive list of possible design parameters, the <italic>PHR taxonomy</italic> proposed by Roehrs et al [<xref ref-type="bibr" rid="ref37">37</xref>] and <italic>EHR in a Blockchain taxonomy</italic> proposed by Mayer et al [<xref ref-type="bibr" rid="ref21">21</xref>] were used as starting points. Next, through a consensus-driven process of elimination, 10 design parameters were selected for abstraction. These were (1) blockchain type, (2) data storage, (3) scaling solution, (4) incentive smart contract, (5) PHR type, (6) data owner, (7) read and write ability, (8) semantic standards, (9) privacy standards, and (10) user interface (UI).</p>
          <p>For limitations and future directions, the issues and areas for improvement brought up across the articles reviewed were identified, consolidated, and presented as a list of unique issues. We did not delve into a more in-depth analysis such as ranking the unique issues because the frequency of mention was not necessarily associated with importance or criticality. Moreover, the articles may not have fully listed all their limitations, as it was not their primary aim.</p>
          <p>In total, 23 data elements were extracted from each article. <xref ref-type="table" rid="table2">Table 2</xref> provides a complete list of the extracted data elements and a description of each element.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>List of data elements extracted from the selected articles.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="270"/>
              <col width="0"/>
              <col width="700"/>
              <thead>
                <tr valign="top">
                  <td colspan="3">Types of data elements</td>
                  <td>Description</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="4">
                    <bold>General</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Author</td>
                  <td colspan="2">First author’s last name</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Title</td>
                  <td colspan="2">Title of the article</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Year</td>
                  <td colspan="2">Publication year of the article</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Country</td>
                  <td colspan="2">First author’s affiliated country</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Type</td>
                  <td colspan="2">Type of article (eg, journal article, conference paper, book chapter, and whitepaper)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Publisher</td>
                  <td colspan="2">Name of publisher of the article</td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Blockchain</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Name of blockchain PHR<sup>a</sup></td>
                  <td colspan="2">Name of the blockchain PHR (if any)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Maturity</td>
                  <td colspan="2">Maturity level of the blockchain PHR described (ie, concept/framework, prototype, and pilot/implementation)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Blockchain type</td>
                  <td colspan="2">Type of blockchain (ie, public, consortium, private, or a combination)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Blockchain name</td>
                  <td colspan="2">Name of the blockchain used (if any)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Data storage</td>
                  <td colspan="2">Type of data storage mechanism (ie, on-chain, off-chain, or hybrid)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Scaling solution</td>
                  <td colspan="2">Type of scaling solution used in the blockchain PHR (if any)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Incentive smart contract</td>
                  <td colspan="2">Was a smart contract used to incentivize use of the blockchain PHR? (yes or no)</td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>PHR</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PHR type</td>
                  <td colspan="2">Type of PHR (ie, standalone or tethered to an existing EMR<sup>b</sup> system)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Data owner</td>
                  <td colspan="2">Party that owned the data from the blockchain PHR (ie, patient, provider, or both)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Read-write access (for patients)</td>
                  <td colspan="2">Was the patient given read and/or write access in the blockchain PHR? (yes or no)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Read-write access (for providers)</td>
                  <td colspan="2">Was the provider given read and/or write access in the blockchain PHR? (yes or no)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Read-write access (for other parties)</td>
                  <td colspan="2">Were other parties given read and/or write access in the blockchain PHR? (yes or no)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Semantic standard</td>
                  <td colspan="2">Type of semantic standard adopted (eg, HL-7<sup>c</sup> and FHIR<sup>d</sup>)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Privacy standard</td>
                  <td colspan="2">Type of privacy standard adopted (eg, HIPAA<sup>e</sup> and GDPR<sup>f</sup>)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>User interface</td>
                  <td colspan="2">Modality of accessing the blockchain PHR (ie, web, mobile, or desktop application)</td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Additional</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Limitations</td>
                  <td colspan="2">Current limitations of the blockchain PHR</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Future directions</td>
                  <td colspan="2">Future directions and opportunities described</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>PHR: personal health record.</p>
              </fn>
              <fn id="table2fn2">
                <p><sup>b</sup>EMR: electronic medical record.</p>
              </fn>
              <fn id="table2fn3">
                <p><sup>c</sup>HL-7: health level 7.</p>
              </fn>
              <fn id="table2fn4">
                <p><sup>d</sup>FHIR: Fast Healthcare Interoperability Resource.</p>
              </fn>
              <fn id="table2fn5">
                <p><sup>e</sup>HIPAA: Health Insurance Portability and Accountability Act.</p>
              </fn>
              <fn id="table2fn6">
                <p><sup>f</sup>GDPR: General Data Protection Regulation.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview of Articles</title>
        <p>The search performed on July 6, 2020, yielded 325 articles, of which 158 were unique articles. From the article selection process, 51 articles were selected for review. An additional 7 articles were added via snowballing (review of the references from the included articles) of the full texts screened (<xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-analyses) flow diagram of the article selection process. The title and author screen involved removing duplicate articles that had the same title and authors. The abstract screen involved reviewing article abstracts to remove review articles and those not related to blockchain and electronic health records. The full text screen involved reviewing the full articles to exclude those that did not meet the inclusion and exclusion criteria, and those whose full text was not available or in English. ACM: Association of Computing Machinery; EHR: electronic health record; IEEE: Institute of Electrical and Electronics Engineers; PHR: personal health record.</p>
          </caption>
          <graphic xlink:href="jmir_v23i4e25094_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>A total of 58 studies were included in the final review [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref92">92</xref>]. The complete list of articles, with identifiers used in this study, are presented in <xref ref-type="table" rid="table3">Table 3</xref>. The completed data collection form for these articles can be found in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. An overview of the articles with the publication year, publisher, article type, country, and interest group is presented in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref92">92</xref>].</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>List of articles included in the final review.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="150"/>
            <col width="200"/>
            <col width="650"/>
            <thead>
              <tr valign="top">
                <td>Article identifier</td>
                <td>Authors</td>
                <td>Article title</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>A01</td>
                <td>Burniske [<xref ref-type="bibr" rid="ref37">37</xref>]</td>
                <td>How blockchain technology can enhance EHR<sup>a</sup> interoperability</td>
              </tr>
              <tr valign="top">
                <td>A02</td>
                <td>McFarlane et al [<xref ref-type="bibr" rid="ref38">38</xref>]</td>
                <td>Patientory: A Healthcare Peer-to-Peer EMR<sup>b</sup> Storage Network</td>
              </tr>
              <tr valign="top">
                <td>A03</td>
                <td>Roehrs et al [<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                <td>OmniPHR: A distributed architecture model to integrate personal health records</td>
              </tr>
              <tr valign="top">
                <td>A04</td>
                <td>Badr et al [<xref ref-type="bibr" rid="ref40">40</xref>]</td>
                <td>Multi-tier blockchain framework for IoT<sup>c</sup>-EHRs systems</td>
              </tr>
              <tr valign="top">
                <td>A05</td>
                <td>Boiani [<xref ref-type="bibr" rid="ref41">41</xref>]</td>
                <td>Blockchain based electronic health record management for mass crisis scenarios: A feasibility study</td>
              </tr>
              <tr valign="top">
                <td>A06</td>
                <td>Chen et al [<xref ref-type="bibr" rid="ref42">42</xref>]</td>
                <td>Blockchain-Based Medical Records Secure Storage and Medical Service Framework</td>
              </tr>
              <tr valign="top">
                <td>A07</td>
                <td>Dagher et al [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                <td>Ancile: Privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology</td>
              </tr>
              <tr valign="top">
                <td>A08</td>
                <td>Dubovitskaya et al [<xref ref-type="bibr" rid="ref44">44</xref>]</td>
                <td>Secure and Trustable Electronic Medical Records Sharing using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A09</td>
                <td>Gebremedhin [<xref ref-type="bibr" rid="ref45">45</xref>]</td>
                <td>Blockchain as a Technology to Facilitate Privacy and Better Health Record Management</td>
              </tr>
              <tr valign="top">
                <td>A10</td>
                <td>Lippman et al [<xref ref-type="bibr" rid="ref46">46</xref>]</td>
                <td>MedRec: Patient Control of Medical Record Distribution</td>
              </tr>
              <tr valign="top">
                <td>A11</td>
                <td>Medicalchain [<xref ref-type="bibr" rid="ref47">47</xref>]</td>
                <td>Medicalchain</td>
              </tr>
              <tr valign="top">
                <td>A12</td>
                <td>Rouhani et al [<xref ref-type="bibr" rid="ref48">48</xref>]</td>
                <td>MEDICHAIN: A Secure Decentralized Medical Data Asset Management System</td>
              </tr>
              <tr valign="top">
                <td>A13</td>
                <td>Thwin and Vasupongayya [<xref ref-type="bibr" rid="ref49">49</xref>]</td>
                <td>Blockchain Based Secret-Data Sharing Model for Personal Health Record System</td>
              </tr>
              <tr valign="top">
                <td>A14</td>
                <td>Vora et al [<xref ref-type="bibr" rid="ref50">50</xref>]</td>
                <td>BHEEM<sup>d</sup>: A Blockchain-Based Framework for Securing Electronic Health Records</td>
              </tr>
              <tr valign="top">
                <td>A15</td>
                <td>Zhang and Poslad [<xref ref-type="bibr" rid="ref51">51</xref>]</td>
                <td>Blockchain Support for Flexible Queries with Granular Access Control to Electronic Medical Records (EMR)</td>
              </tr>
              <tr valign="top">
                <td>A16</td>
                <td>Abouzahra [<xref ref-type="bibr" rid="ref52">52</xref>]</td>
                <td>Using blockchain technology to enhance the use of personal health records</td>
              </tr>
              <tr valign="top">
                <td>A17</td>
                <td>Alkhushayni et al, [<xref ref-type="bibr" rid="ref53">53</xref>]</td>
                <td>Blockchain technology applied to electronic health records</td>
              </tr>
              <tr valign="top">
                <td>A18</td>
                <td>Ray Chawdhuri [<xref ref-type="bibr" rid="ref54">54</xref>]</td>
                <td>Patient Privacy and Ownership of Electronic Health Records on a Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A19</td>
                <td>Ciampi [<xref ref-type="bibr" rid="ref55">55</xref>]</td>
                <td>A Blockchain Architecture for the Italian EHR System</td>
              </tr>
              <tr valign="top">
                <td>A20</td>
                <td>Daraghmi et al [<xref ref-type="bibr" rid="ref56">56</xref>]</td>
                <td>MedChain: A Design of Blockchain-Based System for Medical Records Access and Permissions Management</td>
              </tr>
              <tr valign="top">
                <td>A21</td>
                <td>Donawa et al [<xref ref-type="bibr" rid="ref57">57</xref>]</td>
                <td>Scaling Blockchains to Support Electronic Health Records for Hospital Systems</td>
              </tr>
              <tr valign="top">
                <td>A22</td>
                <td>Hang et al [<xref ref-type="bibr" rid="ref58">58</xref>]</td>
                <td>A novel EMR integrity management based on a medical blockchain platform in hospital</td>
              </tr>
              <tr valign="top">
                <td>A23</td>
                <td>Harika et al [<xref ref-type="bibr" rid="ref59">59</xref>]</td>
                <td>Blockchain technology for managing an architectural model of decentralized medical record</td>
              </tr>
              <tr valign="top">
                <td>A24</td>
                <td>Huang et al [<xref ref-type="bibr" rid="ref60">60</xref>]</td>
                <td>MedBloc: A Blockchain-Based Secure EHR System for Sharing and Accessing Medical Data</td>
              </tr>
              <tr valign="top">
                <td>A25</td>
                <td>Hylock and Zeng [<xref ref-type="bibr" rid="ref61">61</xref>]</td>
                <td>A Blockchain Framework for Patient-Centered Health Records and Exchange (HealthChain): Evaluation and Proof-of-Concept Study</td>
              </tr>
              <tr valign="top">
                <td>A26</td>
                <td>Jiang et al [<xref ref-type="bibr" rid="ref62">62</xref>]</td>
                <td>Patients-Controlled Secure and Privacy-Preserving EHRs Sharing Scheme Based on Consortium Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A27</td>
                <td>Koushik et al [<xref ref-type="bibr" rid="ref63">63</xref>]</td>
                <td>Performance Analysis of BlockChain-based Medical Records Management System</td>
              </tr>
              <tr valign="top">
                <td>A28</td>
                <td>Lee [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                <td>PHR<sup>e</sup> system using blockchain technology</td>
              </tr>
              <tr valign="top">
                <td>A29</td>
                <td>MediBloc [<xref ref-type="bibr" rid="ref65">65</xref>]</td>
                <td>MediBloc Technical Whitepaper</td>
              </tr>
              <tr valign="top">
                <td>A30</td>
                <td>MediLOT [<xref ref-type="bibr" rid="ref66">66</xref>]</td>
                <td>MediLOT Whitepaper</td>
              </tr>
              <tr valign="top">
                <td>A31</td>
                <td>Nchinda et al [<xref ref-type="bibr" rid="ref67">67</xref>]</td>
                <td>MedRec: A Network for Personal Information Distribution</td>
              </tr>
              <tr valign="top">
                <td>A32</td>
                <td>Nguyen et al [<xref ref-type="bibr" rid="ref68">68</xref>]</td>
                <td>Blockchain for Secure EHRs Sharing of Mobile Cloud Based E-Health Systems</td>
              </tr>
              <tr valign="top">
                <td>A33</td>
                <td>Park et al [<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                <td>Is Blockchain Technology Suitable for Managing Personal Health Records? Mixed-Methods Study to Test Feasibility</td>
              </tr>
              <tr valign="top">
                <td>A34</td>
                <td>Rajput et al [<xref ref-type="bibr" rid="ref69">69</xref>]</td>
                <td>EACMS: Emergency Access Control Management System for Personal Health Record Based on Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A35</td>
                <td>Reen et al [<xref ref-type="bibr" rid="ref70">70</xref>]</td>
                <td>Decentralized patient centric e-Health record management system using blockchain and IPFS<sup>e</sup></td>
              </tr>
              <tr valign="top">
                <td>A36</td>
                <td>Sangeetha [<xref ref-type="bibr" rid="ref71">71</xref>]</td>
                <td>Electronic Health Record System using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A37</td>
                <td>Shahnaz et al [<xref ref-type="bibr" rid="ref72">72</xref>]</td>
                <td>Using Blockchain for Electronic Health Records</td>
              </tr>
              <tr valign="top">
                <td>A38</td>
                <td>Shekhawat [<xref ref-type="bibr" rid="ref73">73</xref>]</td>
                <td>Cloud-chain: Revamp Health Record System Using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A39</td>
                <td>Thwin and Vasupongayya [<xref ref-type="bibr" rid="ref74">74</xref>]</td>
                <td>Blockchain-Based Access Control Model to Preserve Privacy for Personal Health Record Systems</td>
              </tr>
              <tr valign="top">
                <td>A40</td>
                <td>Tian [<xref ref-type="bibr" rid="ref75">75</xref>]</td>
                <td>Blockchain-based secure medical record sharing system</td>
              </tr>
              <tr valign="top">
                <td>A41</td>
                <td>Toshniwal et al [<xref ref-type="bibr" rid="ref76">76</xref>]</td>
                <td>PACEX: Patient-centric EMR exchange in Healthcare Systems using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A42</td>
                <td>Wang et al [<xref ref-type="bibr" rid="ref77">77</xref>]</td>
                <td>Blockchain-Based Personal Health Records Sharing Scheme With Data Integrity Verifiable</td>
              </tr>
              <tr valign="top">
                <td>A43</td>
                <td>Wang et al [<xref ref-type="bibr" rid="ref78">78</xref>]</td>
                <td>Cloud-Assisted EHR Sharing with Security and Privacy Preservation via Consortium Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A44</td>
                <td>Wu and Du [<xref ref-type="bibr" rid="ref79">79</xref>]</td>
                <td>Electronic medical record security sharing model based on blockchain</td>
              </tr>
              <tr valign="top">
                <td>A45</td>
                <td>Al Goni et al [<xref ref-type="bibr" rid="ref80">80</xref>]</td>
                <td>A P2P Optimistic Fair-Exchange Scheme for Personal Health Records Using Blockchain Technology</td>
              </tr>
              <tr valign="top">
                <td>A46</td>
                <td>Arunkumar and Kousalya [<xref ref-type="bibr" rid="ref81">81</xref>]</td>
                <td>Blockchain-Based Decentralized and Secure Lightweight E-Health System for Electronic Health Records</td>
              </tr>
              <tr valign="top">
                <td>A47</td>
                <td>Aswin et al [<xref ref-type="bibr" rid="ref82">82</xref>]</td>
                <td>Design of AYUSH: A blockchain-based health record management system</td>
              </tr>
              <tr valign="top">
                <td>A48</td>
                <td>Cao et al [<xref ref-type="bibr" rid="ref83">83</xref>]</td>
                <td>Hybrid blockchain–based privacy-preserving electronic medical records sharing scheme across medical information control system</td>
              </tr>
              <tr valign="top">
                <td>A49</td>
                <td>Charanya et al [<xref ref-type="bibr" rid="ref84">84</xref>]</td>
                <td>Sefra: A secure framework to manage eHealth records using blockchain technology</td>
              </tr>
              <tr valign="top">
                <td>A50</td>
                <td>Kavathekar and Patil [<xref ref-type="bibr" rid="ref85">85</xref>]</td>
                <td>Data sharing and privacy-preserving of medical records using blockchain</td>
              </tr>
              <tr valign="top">
                <td>A51</td>
                <td>Kim et al [<xref ref-type="bibr" rid="ref86">86</xref>]</td>
                <td>Design of Secure Protocol for Cloud-Assisted Electronic Health Record System Using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A52</td>
                <td>Kung et al [<xref ref-type="bibr" rid="ref87">87</xref>]</td>
                <td>Personal Health Record in FHIR<sup>f</sup> Format Based on Blockchain Architecture</td>
              </tr>
              <tr valign="top">
                <td>A53</td>
                <td>Lee et al [<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                <td>An Architecture and Management Platform for Blockchain-Based Personal Health Record Exchange: Development and Usability Study</td>
              </tr>
              <tr valign="top">
                <td>A54</td>
                <td>Sharma et al [<xref ref-type="bibr" rid="ref88">88</xref>]</td>
                <td>Secure Cloud Storage Architecture for Digital Medical Record in Cloud Environment using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A55</td>
                <td>Sharma and Balamurugan [<xref ref-type="bibr" rid="ref89">89</xref>]</td>
                <td>Preserving the Privacy of Electronic Health Records using Blockchain</td>
              </tr>
              <tr valign="top">
                <td>A56</td>
                <td>Tith et al [<xref ref-type="bibr" rid="ref90">90</xref>]</td>
                <td>Application of Blockchain to Maintaining Patient Records in Electronic Health Record for Enhanced Privacy, Scalability, and Availability</td>
              </tr>
              <tr valign="top">
                <td>A57</td>
                <td>Verdonck and Poels [<xref ref-type="bibr" rid="ref91">91</xref>]</td>
                <td>Architecture and value analysis of a blockchain-based electronic health record permission management system</td>
              </tr>
              <tr valign="top">
                <td>A58</td>
                <td>Wu et al [<xref ref-type="bibr" rid="ref92">92</xref>]</td>
                <td>Secure Personal Health Records Sharing Based on Blockchain and IPFS<sup>g</sup></td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>EHR: electronic health record.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>EMR: electronic medical record.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>IoT: internet of things.</p>
            </fn>
            <fn id="table3fn4">
              <p><sup>d</sup>BHEEM: Blockchain-based framework for efficient storage and maintenance of electronic health records</p>
            </fn>
            <fn id="table3fn5">
              <p><sup>e</sup>PHR: personal health record.</p>
            </fn>
            <fn id="table3fn6">
              <p><sup>f</sup>FHIR: Fast Healthcare Interoperability Resource.</p>
            </fn>
            <fn id="table3fn7">
              <p><sup>g</sup>IPFS: Interplanetary File System.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Current Landscape and Trends of Blockchain PHRs</title>
        <sec>
          <title>Interest Group</title>
          <p>The level of academic interest in the space has been rising, supported by an increasing trend in the number of published articles since 2016. In terms of interest groups, 45 articles were CS-or engineering-related publications or from CS- or engineering-related authors. Seven were published in medical journals, all of which were related to medical informatics. Of the 6 remaining articles that were classified as <italic>General</italic>, 5 were whitepapers. The articles from the CS or engineering interest group showed a sharp rise from 2017 to 2019 and may have started to plateau, whereas those from medical journals have been following a gradual, steady increase since 2016 (<xref rid="figure3" ref-type="fig">Figure 3</xref>).</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Trend of blockchain personal health record articles by interest group. The trend from 2019 to 2020 (represented by dashed lines) is a projection because only data from the first half of the year 2020 was available at the time of the search. Count refers to the number of articles published in that year.</p>
            </caption>
            <graphic xlink:href="jmir_v23i4e25094_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Geographic Distribution</title>
          <p>The articles originated from 23 different countries. The majority were from India (n=13), United States (n=9), China (n=8), and South Korea (n=5), with Canada, Switzerland, Taiwan, and Thailand having 2 articles each and the remaining countries having 1 article each (<xref rid="figure4" ref-type="fig">Figure 4</xref>). Although the research interest in blockchain PHR is multinational, there clearly are a few countries that are leading the pack. Among these leading countries, there has been an increasing number of publications from India over the years, whereas China, South Korea, and the United States have shown a slowing trend. Apart from these countries, the aggregated output from the rest of the countries is also increasing (<xref rid="figure5" ref-type="fig">Figure 5</xref>).</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Distribution of articles published by geography. The number of articles refers to the total number of articles selected for the final review.</p>
            </caption>
            <graphic xlink:href="jmir_v23i4e25094_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Trend of blockchain personal health record articles by country. Only countries with 5 or more articles in the final review were plotted individually. The other countries were grouped under an Others category. The trend from 2019 to 2020 (represented by dashed lines) is a projection because only data from the first half of the year 2020 was available at the time of the search. Count refers to the number of articles published in that year.</p>
            </caption>
            <graphic xlink:href="jmir_v23i4e25094_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Maturity Level</title>
          <p>The blockchain PHR space is maturing, with the proportion of articles describing prototypes showing an upward trend (<xref rid="figure6" ref-type="fig">Figure 6</xref>). In addition, the first paper to describe an implementation was also published in the first half of 2020 by Lee et al [<xref ref-type="bibr" rid="ref19">19</xref>]. Their blockchain PHR implementation was deployed across Southeast Asia via an information network and became the first PHR management platform for cross-regional medical data exchange.</p>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>Trend of blockchain personal health record maturity. Note that the trend from 2019 to 2020 (represented by dashed lines) is a projection because only data from the first half of the year 2020 was available at the time of search. Count refers to the number of articles published in that year (2018).</p>
            </caption>
            <graphic xlink:href="jmir_v23i4e25094_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Key Design Choices for Blockchain PHRs</title>
        <sec>
          <title>Blockchain Attributes</title>
          <p>Most blockchain PHRs are described using a private (n=24) or consortium (n=22) blockchain, whereas 4 others used a public-permissioned hybrid design. Only 4 cases of using a public blockchain were described. In the remaining 4 cases, the blockchain type was not clearly stated. An Ethereum-based blockchain was the most commonly used (n=26), with HF being the next most common (n=20). Among these, 3 articles used both Ethereum and HF.</p>
          <p>For data storage, the majority used off-chain data storage (n=40), 14 stored EHR data on-chain, and 4 described hybrid data storage. For off-chain storage, 10 articles, all from 2019 onward, used the Interplanetary File System (IPFS). In terms of other scaling solutions, 9 articles considered new consensus algorithms such as Proof-of-Authority, 4 used a tiered-chain architecture, and 1 used both side-chain and algorithmic methods to improve the blockchain scaling capacity.</p>
          <p>Among the articles, 5 described an incentive structure in the blockchain PHR using smart contracts. Four of these were whitepapers, which proposed incentivizing stakeholders through the issuing of tokens (digital currency of value) from smart contracts. In these cases, once an action warranting compensation had taken place, the smart contract automatically triggered the issuance of tokens. <xref ref-type="table" rid="table4">Table 4</xref> provides additional details of the tokens and how they can be earned and used as part of the incentive structure. Unlike the others, Daraghmi et al [<xref ref-type="bibr" rid="ref56">56</xref>] proposed a novel, nonmonetary incentive. Their system kept score using <italic>degrees</italic> based on the effort in maintaining the quality of records and creating new blocks. Those with higher degrees would have a lower probability of performing the computation task of creating new blocks. In this way, it is meant to achieve fairness and sustainability of the system.</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Incentive structure proposed by blockchain personal health record systems.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="130"/>
              <col width="150"/>
              <col width="160"/>
              <col width="280"/>
              <col width="280"/>
              <thead>
                <tr valign="top">
                  <td>Article identifier</td>
                  <td>Token name</td>
                  <td>Party compensated</td>
                  <td>Compensation</td>
                  <td>Token use</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>A02</td>
                  <td>Patientory issued tokens</td>
                  <td>Provider</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>On the basis of how effective provider ensures improvement in care quality and outcomes</p>
                      </list-item>
                    </list>
                  </td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Renting storage space on the platform</p>
                      </list-item>
                      <list-item>
                        <p>Execution of smart contracts</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>A11</td>
                  <td>MedToken</td>
                  <td>Patients</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Sharing of personal health data on health care data marketplace</p>
                      </list-item>
                    </list>
                  </td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Lower insurance premiums</p>
                      </list-item>
                      <list-item>
                        <p>Payment for use of applications (eg, tele-consultations)</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>A29</td>
                  <td>MediBloc coin</td>
                  <td>Provider</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Performing computational task of producing blocks</p>
                      </list-item>
                    </list>
                  </td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Tradable for monetary value</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>A30</td>
                  <td>LOT<sup>a</sup> token</td>
                  <td>Patients</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Contribute data</p>
                      </list-item>
                      <list-item>
                        <p>Compliance to health care recommendations</p>
                      </list-item>
                    </list>
                  </td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Analytics services (eg, personalized health reports)</p>
                      </list-item>
                      <list-item>
                        <p>Payment to retail and pharmaceutical partners</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>LOT: token used in the MediLOT system.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>PHR Attributes</title>
          <p>A total of 18 articles described a tethered blockchain PHR that interfaced with an existing electronic medical record (EMR) system. All of these were of the <italic>Concept/Framework/Model</italic> maturity level. Those that were prototypes, pilots, or implementations were all standalone PHR systems.</p>
          <p>In the majority (n=45) of the articles, the patient was the data owner. Of the remaining articles, providers were data owners in 9 of them, whereas 2 had both patients and providers as owners. It was unclear who the data owner was in the last 2 articles.</p>
          <p>In most articles, both patients and providers had read and write abilities. Most blockchain PHRs granted providers with both read and write abilities (n=40), and only 4 blockchain PHRs did not grant providers any read or write abilities. <xref ref-type="table" rid="table5">Table 5</xref> is a matrix representing the distribution of read and write capabilities for patients and doctors among the various articles and article codes refer to article identifier in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Matrix of various read and write models among the blockchain personal health records reviewed.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="190"/>
              <col width="270"/>
              <col width="270"/>
              <col width="270"/>
              <thead>
                <tr valign="top">
                  <td>Provider</td>
                  <td colspan="3">Patient</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Read only</td>
                  <td>Write only</td>
                  <td>Read and write</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Read only</td>
                  <td>—<sup>a</sup></td>
                  <td>—</td>
                  <td>A04, A15, A32, A42, A48, A50, A52, A58</td>
                </tr>
                <tr valign="top">
                  <td>Write only</td>
                  <td>A07, A14, A18, A31</td>
                  <td>—</td>
                  <td>—</td>
                </tr>
                <tr valign="top">
                  <td>Read and write</td>
                  <td>A01, A05, A08, A10, A12, A17, A19, A20, A23, A24, A27, A28, A30, A33, A40, A41, A43, A47, A49, A56</td>
                  <td>A25, A51</td>
                  <td>A02, A03, A06, A09, A11, A21, A22, A26, A34, A35, A37, A38, A39, A44, A45, A46, A53, A54, A55, A57</td>
                </tr>
                <tr valign="top">
                  <td>Neither</td>
                  <td>—</td>
                  <td>A16</td>
                  <td>A13, A29, A36</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>Not available.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>Most articles did not mention the adoption of any semantic standard. For those that did, the 2 standards mentioned were Fast Healthcare Interoperability Resource (FHIR) and health level 7 (HL-7) in 5 and 2 articles, respectively. Similarly, most did not mention adopting any privacy standards. For those that did, 4 mentioned compliance with the Health Insurance Portability and Accountability Act (HIPAA), 1 with the General Data Protection Regulation (GDPR), and 1 with both the HIPAA and GDPR.</p>
          <p>Among the blockchain PHRs that were either prototypes or implementations, 9 developed a web UI, whereas 2 had both a mobile phone application UI and a desktop UI.</p>
        </sec>
      </sec>
      <sec>
        <title>Current Limitations of and Future Directions for Blockchain PHRs</title>
        <sec>
          <title>Current Limitations</title>
          <p>Most of the current limitations can be grouped into 1 of the following 3 main categories: (1) scalability, (2) privacy, and (3) usability. Scalability issues pertained to the inability of blockchain PHR to store large file sizes such as medical images [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref54">54</xref>] or to the slowness in confirming transactions, especially with the incorporation of streaming data from internet of things devices [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref76">76</xref>].</p>
          <p>The inability of blockchain PHRs to ensure full privacy has been highlighted in a few articles. Although records on the blockchain are encrypted, there are possible means to infer the information, such as through blockchain analysis [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref54">54</xref>]. Another privacy issue raised was the inability to erase one’s records, as blockchains are inherently immutable [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref70">70</xref>]. This limitation would make it difficult for blockchain PHRs to comply with privacy regulations such as the GDPR, which stipulates data subjects’ right to erasure (Article 17 of the GDPR).</p>
          <p>One of the usability limitations was the affordability of the blockchain PHR, as each transaction typically required users to pay a transaction fee [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]. Another practical usability issue described by Charanya et al [<xref ref-type="bibr" rid="ref84">84</xref>] was that, unlike conventional PHRs that had password recovery mechanisms, patients would not be able to access their records if they lost their private keys on blockchain PHRs. Incapacitated or unconscious patients also present a similar problem with blockchain PHRs that do not have built-in access control when emergency health care providers would need permission to access records.</p>
          <p>Apart from these 3 main categories, there were other limitations inherent to certain types of popular blockchains such as Ethereum. For example, Gebremedhin [<xref ref-type="bibr" rid="ref45">45</xref>] highlighted that Solidity (Ethereum’s programming language) was unable to implement nested string data types, whereas Kung et al [<xref ref-type="bibr" rid="ref86">86</xref>] mentioned the need to batch upload data in a certain file format as a limitation of their Ethereum-based PHR.</p>
        </sec>
        <sec>
          <title>Future Directions</title>
          <p>The current limitations provide direction to some future work areas for blockchain PHRs. Scalability solutions have already been studied and experimented on, such as Proof-of-Authority and the novel Byzanthine fault tolerance (BFT) consensus mechanisms [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]. Other methods include enhancing the blockchain architecture through tiered-chain [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref64">64</xref>] or side-chain structures [<xref ref-type="bibr" rid="ref57">57</xref>]. Although privacy solutions were more limited in our review, we came across one by Reen et al [<xref ref-type="bibr" rid="ref70">70</xref>] who proposed storing InterPlantary Naming System records instead of the conventional hash of the medical records directly on the blockchain. In this way, users may retain the ability to revoke access to the record if desired.</p>
          <p>Many suggestions have been made to improve the usability of the system. These suggestions could be grouped into (1) user experience, (2) integration with existing systems, and (3) compliance with regulations and development of governance processes. <xref ref-type="table" rid="table6">Table 6</xref> summarizes the suggestions proposed in the articles reviewed.</p>
          <table-wrap position="float" id="table6">
            <label>Table 6</label>
            <caption>
              <p>Suggestions for improving blockchain personal health record usability from the selected articles.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="770"/>
              <col width="0"/>
              <col width="200"/>
              <thead>
                <tr valign="top">
                  <td colspan="3">Suggestion</td>
                  <td>Article identifiers</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="4">
                    <bold>User experience</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Improving user interface of blockchain PHRs<sup>a</sup></td>
                  <td colspan="2">A10, A31, A55</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Biometric user authentication</td>
                  <td colspan="2">A40</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Allowing next-of-kin or caregiver to access records if patient grants access or is incapable of self-access</td>
                  <td colspan="2">A40</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Incorporating incentives for users</td>
                  <td colspan="2">A56</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Incorporating analytics capabilities for personal health insights and management</td>
                  <td colspan="2">A32, A53</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Adding on payment functions for health care services</td>
                  <td colspan="2">A37, A55</td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Integration with existing systems</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Integrating with existing EMR<sup>b</sup> systems</td>
                  <td colspan="2">A07, A08, A19, A20, A52,</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Adopting health care data standards</td>
                  <td colspan="2">A03, A09, A17, A53</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Integrating with IoT<sup>c</sup> devices</td>
                  <td colspan="2">A32</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Integrating with open, public blockchain systems</td>
                  <td colspan="2">A17, A18, A33</td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Compliance with regulations and development of governance processes</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Complying with regulations on health care data privacy</td>
                  <td colspan="2">A07, A18</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Developing governance processes for the blockchain PHRs</td>
                  <td colspan="2">A38</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table6fn1">
                <p><sup>a</sup>PHR: personal health record.</p>
              </fn>
              <fn id="table6fn2">
                <p><sup>b</sup>EMR: electronic medical record.</p>
              </fn>
              <fn id="table6fn3">
                <p><sup>c</sup>IoT: internet of things.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>Apart from improving usability, another aspect of future work is the validation of blockchain PHRs. Among the areas for validation, several articles suggested data validation when data were transferred to off-chain storage [<xref ref-type="bibr" rid="ref77">77</xref>], security validation [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref79">79</xref>], and real-world validation in terms of cost-effectiveness [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]. Validating these components would be relevant to obtain stakeholder and user confidence in deciding where to implement and adopt blockchain PHRs.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>In this first ever systematic review on blockchain PHRs, we adopted a broad search strategy across medical and CS and engineering databases and included gray literature. We focused on the scope of blockchain PHRs to allow for more targeted data abstraction. Through our study, we found that there was a growing interest in blockchain PHRs and that the space has been steadily maturing over the past few years, albeit still much in the conceptual stage. As the space is still fairly new, a lion’s share of the research and innovation has been happening at the technical level to discover new ways to solve problems. This is evidenced by the overwhelming proportion of articles that have come from the CS and engineering domain.</p>
        <p>One of the major areas regarding blockchain PHRs that is still undergoing much research is scalability. We came across a few ideas such as Proof-of-Authority, novel BFT consensus mechanisms, and other modified blockchain architectures such as tiered-chains and side-chains [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]. Apart from blockchain PHR teams working on this, the space may also benefit from parallel innovations from the larger blockchain ecosystem. As Ethereum is looking forward to a new version release (version 2), it is considering various scaling solutions, of which <italic>rollups</italic> is a strong contender [<xref ref-type="bibr" rid="ref93">93</xref>]. <italic>Rollups</italic> solution essentially involves keeping transaction data on-chain while pushing the computational load off-chain. If adopted into Ethereum 2.0, this could automatically benefit many Ethereum-based PHRs.</p>
        <p>Although some areas are actively evolving, others are beginning to consolidate. As found in other systematic reviews, most blockchain PHR project teams have gravitated toward Ethereum and HF as their blockchains of choice [<xref ref-type="bibr" rid="ref22">22</xref>]. In addition, in terms of data storage, we see more projects opting for IPFS as a complementary off-chain data store for their blockchain PHRs [<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]. Outside of this review, we are also aware that there are efforts happening in other public blockchains. An example is NEO, whose core developers are developing a similarly distributed, decentralized object storage network known as NEO file storage system (NeoFS), which will seamlessly integrate with its native blockchain [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]. We did not come across any NEO-based PHRs in this review. NeoFS could potentially be a game changer, so it would be interesting to track its development in this area.</p>
        <p>In this review, we also identified some current limitations that blockchain PHRs need to address. We broadly classified them into scalability, privacy, and usability limitations. In addition to identifying the current limitations, this review also revealed some possible solutions. For example, to address the privacy issue of inferring information from chain analysis, Ray Chawdhuri [<xref ref-type="bibr" rid="ref54">54</xref>] introduced zero-knowledge provable mixing, whereas Park et al [<xref ref-type="bibr" rid="ref17">17</xref>] proposed the zero-knowledge succinct non-interactive argument of knowledge technique. Another example is the solution of using biometric authentication mentioned by Tian [<xref ref-type="bibr" rid="ref75">75</xref>] to address the issues of verifiable user authentication and patients losing their private keys. Medicalchain has also described an emergency bracelet that can be scanned, giving access to essential health information in unconscious patients who are unable to access their private keys [<xref ref-type="bibr" rid="ref47">47</xref>].</p>
        <p>The first blockchain PHR has already been piloted, and this will undoubtedly augur a move of the space toward deployment [<xref ref-type="bibr" rid="ref19">19</xref>]. With this in mind, blockchain PHRs will need to comply with the privacy standards within the jurisdictions they intend to become operational. In addition, to enable integration with existing health care EMR systems, it is necessary to design blockchain PHRs that follow established semantic standards such as HL-7 and FHIR. Looking further ahead, to realize true decentralization, it may be necessary to consider building a PHR atop public blockchains.</p>
        <p>Finally, in terms of geographic interest, we found that although interest in blockchain PHR was multinational, there were obvious leaders in this space. Looking deeper among the leading countries, we noticed that since 2018 there has been an increase in publications from India, whereas those from China, South Korea, and the United States started to level off or decrease. A possible reason for this could be that in 2017, in the midst of an initial coin offering (ICO) fever that drove unusually high interest in blockchain, the latter 3 countries’ relevant authorities had issued bans or indicated legal restrictions on ICO activities with stiff penalties [<xref ref-type="bibr" rid="ref96">96</xref>-<xref ref-type="bibr" rid="ref98">98</xref>]. This may suggest further research into the different factors, including sociopolitical, economic, and cultural factors, which could significantly impact the development of this space. In terms of interest groups, our findings should also provide a sense of where most of the developments are occurring, and this may guide government and private sector funders in their allocation of resources.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>We acknowledge that this review is not exhaustive and that there are many other areas that were excluded. These areas include other smart contract uses, performance evaluation, and the type of vocabulary standard such as Systematized Nomenclature of Medicine Clinical Terms, 10th revision of the International Classification of Diseases, and Logical Observation Identifiers Names and Codes. We also recognize that greater detail about the read and write models could be studied, such as their validity periods and whether other stakeholders (eg, researchers and insurance companies) were given access. Future reviews should consider delving deeper into these areas.</p>
        <p>Furthermore, despite our best efforts to capture as much material available as possible, we are aware that the exclusion of articles whose full text was not in English would have limited the scope of this review. In addition, there may also be other developments in this space that have not been made publicly available for commercial or other reasons.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This cross-disciplinary systematic review on the blockchain PHR space has revealed that as of now, much of the development is still in the conceptual stage. However, there is a trend of growth and maturation. We believe that this provides consolidated evidence for researchers to continue following this space and, more optimistically, to spur them to contribute ideas and efforts to accelerate its development. Those in the medical informatics community will undoubtedly play an increasingly larger role in the development and implementation of blockchain PHRs, especially when the need to integrate with EMR systems and adopt health care data standards becomes more prominent. In addition, as the first systematic review covering blockchain PHRs, we expect this to be an important basis for subsequent reviews to track how the space has progressed in the future.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>List of articles with data abstracted.</p>
        <media xlink:href="jmir_v23i4e25094_app1.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 29 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Overview of the articles with the article identifier, publication year, publisher, type of article, country and interest group.</p>
        <media xlink:href="jmir_v23i4e25094_app2.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BFT</term>
          <def>
            <p>Byzanthine fault tolerance</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CS</term>
          <def>
            <p>computer science</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">FHIR</term>
          <def>
            <p>Fast Healthcare Interoperability Resource</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">HF</term>
          <def>
            <p>Hyperledger Fabric</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">HIPAA</term>
          <def>
            <p>Health Insurance Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">HL-7</term>
          <def>
            <p>health level 7</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">ICO</term>
          <def>
            <p>initial coin offering</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">IPFS</term>
          <def>
            <p>Interplanetary File System</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">NeoFS</term>
          <def>
            <p>NEO file storage system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">PHR</term>
          <def>
            <p>personal health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">PoW</term>
          <def>
            <p>proof of work</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">UI</term>
          <def>
            <p>user interface</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank their families and work organizations—SingHealth Polyclinics, SingHealth Community Hospitals, and the National University Hospital—for their support.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>AF had the original idea for this study. AF, MT, and CT designed the review. MT obtained the relevant articles. AF, TT, and MT reviewed the articles and abstracted the data. AF wrote the first draft of this paper, and all the authors subsequently assisted in revising the work and have approved the final version.</p>
      </fn>
      <fn fn-type="conflict">
        <p>The authors did not receive any funding for this work and declare no conflicts of interest. However, the authors would like to highlight that MT is the cofounder of MediLOT, which published one of the articles reviewed in this paper.</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>
          <month>03</month>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>121</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://paperpile.com/b/kOVAHn/jlUbm"/>
          </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>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="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Andrikopoulou</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Herrera</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Good</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>What are the important design features of personal health records to improve medication adherence for patients with long-term conditions? A systematic literature review</article-title>
          <source>BMJ Open</source>
          <year>2019</year>
          <month>09</month>
          <day>26</day>
          <volume>9</volume>
          <issue>9</issue>
          <fpage>e028628</fpage>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2018-028628</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dameff</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Clay</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Longhurst</surname>
              <given-names>CA</given-names>
            </name>
          </person-group>
          <article-title>Personal Health Records: More Promising in the Smartphone Era?</article-title>
          <source>JAMA</source>
          <year>2019</year>
          <month>01</month>
          <day>29</day>
          <volume>321</volume>
          <issue>4</issue>
          <fpage>339</fpage>
          <lpage>340</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2018.20434</pub-id>
          <pub-id pub-id-type="medline">30633300</pub-id>
          <pub-id pub-id-type="pii">2721088</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alanazi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Anazi</surname>
              <given-names>YA</given-names>
            </name>
          </person-group>
          <article-title>The Challenges in Personal Health Record Adoption</article-title>
          <source>Journal of Healthcare Management</source>
          <year>2019</year>
          <volume>64</volume>
          <issue>2</issue>
          <fpage>104</fpage>
          <lpage>109</lpage>
          <pub-id pub-id-type="doi">10.1097/jhm-d-17-00191</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hossain</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>YA</given-names>
            </name>
          </person-group>
          <article-title>Trends and characteristics of protected health information breaches in the United States</article-title>
          <year>2019</year>
          <conf-name>AMIA Annu Symp Proc. 2020</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Washington</conf-loc>
          <fpage>1081</fpage>
          <lpage>1090</lpage>
        </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>Abd-alrazaq</surname>
              <given-names>AA</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 that affect the use of electronic personal health records among patients: A systematic review</article-title>
          <source>International Journal of Medical Informatics</source>
          <year>2019</year>
          <month>06</month>
          <volume>126</volume>
          <fpage>164</fpage>
          <lpage>175</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.03.014</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>Nakamoto</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Bitcoin: A Peer-to-Peer Electronic Cash System</article-title>
          <source>SSRN Journal</source>
          <year>2008</year>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.2139/ssrn.3440802</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>Kane</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Is Blockchain a General Purpose Technology?</article-title>
          <source>SSRN Journal</source>
          <year>2017</year>
          <month>03</month>
          <day>11</day>
          <fpage>1</fpage>
          <lpage>27</lpage>
          <pub-id pub-id-type="doi">10.2139/ssrn.2932585</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tapscott</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Tapscott</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Blockchain Revolution: How the Technology Behind Bitcoin and Other Cryptocurrencies Is Changing the World</source>
          <year>2018</year>
          <publisher-loc>Blockchain Revolution</publisher-loc>
          <publisher-name>Penguin Random House</publisher-name>
        </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>Agbo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mahmoud</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Eklund</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Blockchain Technology in Healthcare: A Systematic Review</article-title>
          <source>Healthcare</source>
          <year>2019</year>
          <month>04</month>
          <day>04</day>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>56</fpage>
          <pub-id pub-id-type="doi">10.3390/healthcare7020056</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>Chukwu</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Garg</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A Systematic Review of Blockchain in Healthcare: Frameworks, Prototypes, and Implementations</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <volume>8</volume>
          <fpage>21196</fpage>
          <lpage>21214</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.2969881</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>Drosatos</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kaldoudi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Blockchain Applications in the Biomedical Domain: A Scoping Review</article-title>
          <source>Computational and Structural Biotechnology Journal</source>
          <year>2019</year>
          <volume>17</volume>
          <fpage>229</fpage>
          <lpage>240</lpage>
          <pub-id pub-id-type="doi">10.1016/j.csbj.2019.01.010</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>Hasselgren</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kralevska</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gligoroski</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Faxvaag</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in healthcare and health sciences—A scoping review</article-title>
          <source>International Journal of Medical Informatics</source>
          <year>2020</year>
          <month>02</month>
          <volume>134</volume>
          <fpage>104040</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.104040</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Adelmeyer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Meier</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Teuteberg</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Security and Privacy of Personal Health Records in Cloud Computing Environments - An Experimental Exploration of the Impact of Storage Solutions and Data Breaches</article-title>
          <source>Security and Privacy of Personal Health Records in Cloud Computing Environments - An Experimental Exploration of the Impact of Storage Solutions and Data Breaches</source>
          <year>2019</year>
          <conf-name>Wirtschaftsinformatik 2019</conf-name>
          <conf-date>23-Feb-2019 to 29-Feb-2019</conf-date>
          <conf-loc>Siegen</conf-loc>
          <publisher-name>AIS Electronic Library</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xuan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Man</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Guizani</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>An incentive mechanism for data sharing based on blockchain with smart contracts</article-title>
          <source>Computers &#38; Electrical Engineering</source>
          <year>2020</year>
          <month>05</month>
          <volume>83</volume>
          <fpage>106587</fpage>
          <pub-id pub-id-type="doi">10.1016/j.compeleceng.2020.106587</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Na</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Is Blockchain Technology Suitable for Managing Personal Health Records? Mixed-Methods Study to Test Feasibility</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>08</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12533</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2019/2/e12533/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12533</pub-id>
          <pub-id pub-id-type="medline">30735142</pub-id>
          <pub-id pub-id-type="pii">v21i2e12533</pub-id>
          <pub-id pub-id-type="pmcid">PMC6384539</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>Righi</surname>
              <given-names>RR</given-names>
            </name>
            <name name-style="western">
              <surname>de Oliveira</surname>
              <given-names>KS</given-names>
            </name>
          </person-group>
          <article-title>Personal health records: a systematic literature review</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>01</month>
          <day>06</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>e13</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/1/e13/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.5876</pub-id>
          <pub-id pub-id-type="medline">28062391</pub-id>
          <pub-id pub-id-type="pii">v19i1e13</pub-id>
          <pub-id pub-id-type="pmcid">PMC5251169</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Udayasankaran</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Kijsanayotin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>B Marcelo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>LR</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>An Architecture and Management Platform for Blockchain-Based Personal Health Record Exchange: Development and Usability Study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>06</month>
          <day>09</day>
          <volume>22</volume>
          <issue>6</issue>
          <fpage>e16748</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/6/e16748"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/16748</pub-id>
          <pub-id pub-id-type="medline">32515743</pub-id>
          <pub-id pub-id-type="pii">v22i6e16748</pub-id>
          <pub-id pub-id-type="pmcid">PMC7312212</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Azaria</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ekblaw</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vieira</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lippman</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>MedRec: Using Blockchain for Medical Data Access and Permission Management</article-title>
          <year>2016</year>
          <conf-name>International Conference on Open and Big Data</conf-name>
          <conf-date>22-24 Aug 2016</conf-date>
          <conf-loc>Vienna</conf-loc>
          <publisher-loc>MedRec</publisher-loc>
          <publisher-name>Using Blockchain for Medical Data Access and Permission Management. Innd International Conference on Open and Big Data (OBD)</publisher-name>
          <fpage>2016</fpage>
          <lpage>2</lpage>
          <pub-id pub-id-type="doi">10.1109/obd.2016.11</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>A</surname>
              <given-names>Mayer</given-names>
            </name>
            <name name-style="western">
              <surname>C</surname>
              <given-names>Costa</given-names>
            </name>
            <name name-style="western">
              <surname>R</surname>
              <given-names>Righi</given-names>
            </name>
          </person-group>
          <article-title>Electronic health records in a Blockchain: A systematic review</article-title>
          <source>Electronic health records in a Blockchain: A systematic review</source>
          <year>2020</year>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/full/10.1177/1460458219866350"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1460458219866350</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Shuaib</collab>
            <collab>Saleous</collab>
            <collab>Shuaib</collab>
            <collab>Zaki</collab>
          </person-group>
          <article-title>Blockchains for Secure Digitized Medicine</article-title>
          <source>JPM</source>
          <year>2019</year>
          <month>07</month>
          <day>13</day>
          <volume>9</volume>
          <issue>3</issue>
          <fpage>35</fpage>
          <pub-id pub-id-type="doi">10.3390/jpm9030035</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vazirani</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>O'Donoghue</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Brindley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Meinert</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Implementing Blockchains for Efficient Health Care: Systematic Review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>12</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12439</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2019/2/e12439/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12439</pub-id>
          <pub-id pub-id-type="medline">30747714</pub-id>
          <pub-id pub-id-type="pii">v21i2e12439</pub-id>
          <pub-id pub-id-type="pmcid">PMC6390185</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>Angeles</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-Based Healthcare: Three Successful Proof-of-Concept Pilots Worth Considering</article-title>
          <source>Blockchain-Based Healthcare: Three Successful Proof-of-Concept Pilots Worth Considering</source>
          <year>2018</year>
          <volume>27</volume>
          <issue>3</issue>
          <fpage>38</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rijmenam</surname>
              <given-names>DV</given-names>
            </name>
          </person-group>
          <article-title>How Blockchain Will Give Consumers Ownership of their Data</article-title>
          <source>Medium</source>
          <access-date>2020-07-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medium.com/@markvanrijmenam/how-blockchain-will-give-consumers-ownership-of-their-data-3e90020107e6">https://medium.com/@markvanrijmenam/how-blockchain-will-give-consumers-ownership-of-their-data-3e90020107e6</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dickson</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>How blockchain solves the complicated data-ownership problem</article-title>
          <source>The Next Web</source>
          <access-date>2020-07-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://thenextweb.com/contributors/2017/08/17/blockchain-solves-complicated-data-ownership-problem/">https://thenextweb.com/contributors/2017/08/17/blockchain-solves-complicated-data-ownership-problem/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ethereum</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Ethereum Whitepaper</article-title>
          <source>Ethereum</source>
          <access-date>2020-07-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ethereum.org">https://ethereum.org</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>An Overview of Blockchain Technology: Architecture, Consensus, and Future Trends</article-title>
          <source>IEEE International Congress on Big Data (BigData Congress)</source>
          <year>2017</year>
          <conf-name>IEEE International Congress on Big Data (BigData Congress)</conf-name>
          <conf-date>25-30 Jun 2017</conf-date>
          <conf-loc>Honolulu</conf-loc>
          <publisher-loc>An Overview of Blockchain Technology</publisher-loc>
          <publisher-name>Architecture, Consensus, and Future Trends. InIEEE International Congress on Big Data (BigData Congress)</publisher-name>
          <fpage>A</fpage>
          <pub-id pub-id-type="doi">10.1109/bigdatacongress.2017.85</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Hyperledger</collab>
          </person-group>
          <article-title>Hyperledger Whitepaper</article-title>
          <source>Hyperledger project</source>
          <access-date>2020-07-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hyperledger.org/">https://www.hyperledger.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>Quorum Whitepaper</article-title>
          <source>Quorum project</source>
          <access-date>2020-07-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.goquorum.com/">https://www.goquorum.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Corda</surname>
              <given-names>&#124; Open Source Blockchain Platform for Business</given-names>
            </name>
          </person-group>
          <article-title>Corda Whitepaper</article-title>
          <source>Corda project</source>
          <access-date>2020-07-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.corda.net/">https://www.corda.net/</ext-link>
          </comment>
        </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>Banks</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>Sizing up big data</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>01</month>
          <day>13</day>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-019-0703-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liberati</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>DG</given-names>
            </name>
            <collab>PRISMA Group</collab>
          </person-group>
          <article-title>Preferred reporting items for systematic reviews and meta-analyses: the PRISMA statement</article-title>
          <source>J Clin Epidemiol</source>
          <year>2009</year>
          <month>10</month>
          <volume>62</volume>
          <issue>10</issue>
          <fpage>1006</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jclinepi.2009.06.005</pub-id>
          <pub-id pub-id-type="medline">19631508</pub-id>
          <pub-id pub-id-type="pii">S0895-4356(09)00179-6</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>Hölbl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kompara</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kamišalić</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nemec Zlatolas</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A Systematic Review of the Use of Blockchain in Healthcare</article-title>
          <source>Symmetry</source>
          <year>2018</year>
          <month>10</month>
          <day>10</day>
          <volume>10</volume>
          <issue>10</issue>
          <fpage>470</fpage>
          <pub-id pub-id-type="doi">10.3390/sym10100470</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>Kuo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Zavaleta Rojas</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ohno-Machado</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Comparison of blockchain platforms: a systematic review and healthcare examples</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <month>05</month>
          <day>01</day>
          <volume>26</volume>
          <issue>5</issue>
          <fpage>462</fpage>
          <lpage>478</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy185</pub-id>
          <pub-id pub-id-type="medline">30907419</pub-id>
          <pub-id pub-id-type="pii">5419321</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>Keutzer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Newton</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rabaey</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sangiovanni-Vincentelli</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>System-level design: orthogonalization of concerns and platform-based design</article-title>
          <source>IEEE Trans. Comput.-Aided Des. Integr. Circuits Syst</source>
          <year>2020</year>
          <volume>19</volume>
          <issue>12</issue>
          <fpage>1523</fpage>
          <lpage>1543</lpage>
          <pub-id pub-id-type="doi">10.1109/43.898830</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Burniske</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>How blockchain technology can enhance EHR operability</article-title>
          <source>3iQ</source>
          <year>2016</year>
          <access-date>2021-04-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://3iq.ca/how-blockchain-technology-can-enhance-electronic-health-record-ehr-operability/">https://3iq.ca/how-blockchain-technology-can-enhance-electronic-health-record-ehr-operability/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McFarlane</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Beer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prendergast</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Patientory: A Healthcare Peer-to-Peer EMR Storage Network v1.0</article-title>
          <source>Patientory</source>
          <access-date>2021-04-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href=""/>
          </comment>
        </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>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 Righi</surname>
              <given-names>R</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>07</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="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Badr</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gomaa</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Abd-Elrahman</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Multi-tier Blockchain Framework for IoT-EHRs Systems</article-title>
          <source>Procedia Computer Science</source>
          <year>2018</year>
          <volume>141</volume>
          <fpage>159</fpage>
          <lpage>166</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2018.10.162</pub-id>
        </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>Boiani</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Blockchain Based Electronic Health Record Management For Mass Crisis Scenarios?: A Feasibility Study</article-title>
          <source>undefined. Published 2018. Accessed July 14, 2020. /paper/Blockchain-Based-Electronic-Health-Record-For-Mass-Boiani/1218ed976d8fb5ad33096933defc3ce87cc0</source>
          <year>2018</year>
          <fpage>6488</fpage>
        </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>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-Based Medical Records Secure Storage and Medical Service Framework</article-title>
          <source>J Med Syst</source>
          <year>2018</year>
          <month>11</month>
          <day>22</day>
          <volume>43</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-018-1121-4</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>Dagher</surname>
              <given-names>GG</given-names>
            </name>
            <name name-style="western">
              <surname>Mohler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Milojkovic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Marella</surname>
              <given-names>PB</given-names>
            </name>
          </person-group>
          <article-title>Ancile: Privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology</article-title>
          <source>Sustainable Cities and Society</source>
          <year>2018</year>
          <month>05</month>
          <volume>39</volume>
          <fpage>283</fpage>
          <lpage>297</lpage>
          <pub-id pub-id-type="doi">10.1016/j.scs.2018.02.014</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>Dubovitskaya</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Ryu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schumacher</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Secure and Trustable Electronic Medical Records Sharing using Blockchain</article-title>
          <year>2018</year>
          <conf-name>AMIA Annu Symp Proc. 2018</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>San Francisco</conf-loc>
          <fpage>650</fpage>
          <lpage>659</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gebremedhin</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Blockchain as a Technology to Facilitate Privacy and Better Health Record Management</article-title>
          <source>Published online September 1</source>
          <year>2018</year>
          <access-date>2020-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bora.uib.no/handle/1956/19621">https://bora.uib.no/handle/1956/19621</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <article-title>MedRec: Patient Control of Medical Record Distribution - IEEE Blockchain Initiative</article-title>
          <source>IEEE Blockchain Initiative</source>
          <access-date>2020-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blockchain.ieee.org/technicalbriefs/july-2018/medrec-patient-control-of-medical-record-distribution">https://blockchain.ieee.org/technicalbriefs/july-2018/medrec-patient-control-of-medical-record-distribution</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Medicalchain</surname>
              <given-names>W2</given-names>
            </name>
          </person-group>
          <article-title>Medicalchain Whitepaper</article-title>
          <source>Medicalchain</source>
          <access-date>2020-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medicalchain.com/en/whitepaper/">https://medicalchain.com/en/whitepaper/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rouhani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Butterworth</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Simmons</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Humphery</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Deters</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>MediChainTM: A Secure Decentralized Medical Data Asset Management System</article-title>
          <year>2018</year>
          <conf-name>IEEE Int Conf Internet Things</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Halifax</conf-loc>
          <fpage>A</fpage>
          <pub-id pub-id-type="doi">10.1109/cybermatics_2018.2018.00258</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thwin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vasupongayya</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain Based Secret-Data Sharing Model for Personal Health Record System</article-title>
          <year>2018</year>
          <conf-name>5th International Conference on Advanced Informatics: Concept Theory and Applications (ICAICTA)</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Thailand</conf-loc>
          <publisher-loc>Inth International Conference on Advanced Informatics</publisher-loc>
          <publisher-name>Concept Theory and Applications (ICAICTA)</publisher-name>
          <fpage>2018</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1109/icaicta.2018.8541296</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vora</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nayyar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tanwar</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>BHEEM: A Blockchain-Based Framework for Securing Electronic Health Records</article-title>
          <source>IEEE</source>
          <year>2018</year>
          <conf-name>2018 IEEE Globecom Workshops</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Abu Dhabi</conf-loc>
          <publisher-name>IEEE</publisher-name>
          <fpage>A</fpage>
          <pub-id pub-id-type="doi">10.1109/glocomw.2018.8644088</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Poslad</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain Support for Flexible Queries with Granular Access Control to Electronic Medical Records (EMR)</article-title>
          <year>2018</year>
          <conf-name>IEEE International Conference on Communications (ICC)</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Kansas City</conf-loc>
          <fpage>2018</fpage>
          <pub-id pub-id-type="doi">10.1109/icc.2018.8422883</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abouzahra</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Using Blockchain Technology to Enhance the Use of Personal Health Records</article-title>
          <source>AMCIS Proc</source>
          <year>2019</year>
          <conf-name>AMCIS</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Cancun</conf-loc>
          <fpage>1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aisel.aisnet.org/amcis2019/healthcare_it/healthcare_it/6"/>
          </comment>
        </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>Alkhushayni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Zaleq</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kengne</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Blockchain Technology applied to Electronic Health Records</article-title>
          <source>EasyChair</source>
          <year>2019</year>
          <fpage>34</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.29007/2x3r</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ray</surname>
              <given-names>CD</given-names>
            </name>
          </person-group>
          <article-title>Patient Privacy Ownership of Electronic Health Records on a Blockchain</article-title>
          <source>Lecture Notes in Computer Science</source>
          <year>2019</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>95</fpage>
          <lpage>111</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ciampi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A blockchain architecture for the Italian EHR system</article-title>
          <source>ThinkMind Digital Library</source>
          <year>2019</year>
          <conf-name>The Fourth International Conference on Informatics and Assistive Technologies for Health-Care, Medical Support and Wellbeing (HEALTHINFO 2019)</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Valencia</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/337946548_A_blockchain_architecture_for_the_Italian_EHR_system"/>
          </comment>
        </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>Daraghmi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Daraghmi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>MedChain: A Design of Blockchain-Based System for Medical Records Access and Permissions Management</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>164595</fpage>
          <lpage>164613</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2952942</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Donawa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Orukari</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Scaling Blockchains to Support Electronic Health Records for Hospital Systems</article-title>
          <source>IEEE</source>
          <year>2019</year>
          <conf-name>IEEE 10th Annual Ubiquitous Computing, Electronics Mobile Communication Conference (UEMCON)</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>New York</conf-loc>
          <fpage>2019</fpage>
          <pub-id pub-id-type="doi">10.1109/uemcon47517.2019.8993101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Hang</collab>
            <collab>Choi</collab>
            <collab>Kim</collab>
          </person-group>
          <article-title>A Novel EMR Integrity Management Based on a Medical Blockchain Platform in Hospital</article-title>
          <source>Electronics</source>
          <year>2019</year>
          <month>04</month>
          <day>25</day>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>467</fpage>
          <pub-id pub-id-type="doi">10.3390/electronics8040467</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Harika</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rahmadika</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ramdania</surname>
              <given-names>DR</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology for managing an architectural model of decentralized medical record</article-title>
          <source>J. Phys.: Conf. Ser</source>
          <year>2019</year>
          <month>12</month>
          <day>14</day>
          <conf-name>J Phys Conf Ser</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Medan</conf-loc>
          <fpage>077027</fpage>
          <pub-id pub-id-type="doi">10.1088/1742-6596/1402/7/077027</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Qi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Asghar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Meads</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>MedBloc: A Blockchain-Based Secure EHR System for Sharing and Accessing Medical Data</article-title>
          <source>Tu Y-C</source>
          <year>2019</year>
          <conf-name>18th IEEE International Conference On Trust, Security And Privacy In Computing And Communications</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>New Zealand</conf-loc>
          <publisher-loc>MedBloc</publisher-loc>
          <publisher-name>A Blockchain-Based Secure EHR System for Sharing and Accessing Medical Data. Inth IEEE International Conference On Trust, Security And Privacy In Computing And Communications/13th IEEE International Conference On Big Data Science And Engineering (TrustCom/BigDataSE)</publisher-name>
          <pub-id pub-id-type="doi">10.1109/trustcom/bigdatase.2019.00085</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>Hylock</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>A Blockchain Framework for Patient-Centered Health Records and Exchange (HealthChain): Evaluation and Proof-of-Concept Study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>8</month>
          <day>31</day>
          <volume>21</volume>
          <issue>8</issue>
          <fpage>e13592</fpage>
          <pub-id pub-id-type="doi">10.2196/13592</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Patients-Controlled Secure and Privacy-Preserving EHRs Sharing Scheme Based on Consortium Blockchain</article-title>
          <source>IEEE</source>
          <year>2019</year>
          <conf-name>IEEE Global Communications Conference (GLOBECOM)</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Hawaii</conf-loc>
          <pub-id pub-id-type="doi">10.1109/globecom38437.2019.9013220</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Koushik</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Menon</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lohia</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chaudhari</surname>
              <given-names>SB</given-names>
            </name>
          </person-group>
          <article-title>Performance Analysis of BlockChain-based Medical Records Management System</article-title>
          <year>2019</year>
          <conf-name>4th International Conference on Recent Trends on Electronics, Information, Communication Technology (RTEICT)</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Bengaluru</conf-loc>
          <fpage>2019</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="doi">10.1109/rteict46194.2019.9016812</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>Lee</surname>
              <given-names>SY</given-names>
            </name>
          </person-group>
          <article-title>PHR System using Blockchain Technology</article-title>
          <source>International Journal of Advanced Trends in Computer Science and Engineering</source>
          <year>2019</year>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.warse.org/IJATCSE/static/pdf/file/ijatcse84862019.pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.30534/ijatcse/2019/84862019</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Medibloc</collab>
          </person-group>
          <article-title>Medibloc Technical Whitepaper</article-title>
          <source>MediBloc</source>
          <year>2019</year>
          <access-date>2020-07-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/medibloc/whitepaper">https://github.com/medibloc/whitepaper</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="web">
          <article-title>MediLOT &#124; Transforming Healthcare For All</article-title>
          <source>MediLOT</source>
          <access-date>2020-07-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medilot.com/">https://medilot.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nchinda</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Cameron</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Retzepi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lippman</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>MedRec: A Network for Personal Information Distribution</article-title>
          <year>2019</year>
          <conf-name>International Conference on Computing, Networking and Communications (ICNC)</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Hawaii</conf-loc>
          <publisher-loc>MedRec</publisher-loc>
          <publisher-name>A Network for Personal Information Distribution. InInternational Conference on Computing, Networking and Communications (ICNC)</publisher-name>
          <fpage>A</fpage>
          <pub-id pub-id-type="doi">10.1109/iccnc.2019.8685631</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>Nguyen</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Pathirana</surname>
              <given-names>PN</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Seneviratne</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for Secure EHRs Sharing of Mobile Cloud Based E-Health Systems</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>66792</fpage>
          <lpage>66806</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2917555</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>Rajput</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Taleby Ahvanooey</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Masood</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>EACMS: Emergency Access Control Management System for Personal Health Record Based on Blockchain</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>84304</fpage>
          <lpage>84317</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2917976</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>Reen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Mohandas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Venkatesan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Decentralized Patient Centric e- Health Record Management System using Blockchain and IPFS</article-title>
          <source>IEEE</source>
          <year>2019</year>
          <conf-name>InIEEE Conference on Information and Communication Technology</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Pakistan</conf-loc>
          <fpage>2019</fpage>
          <pub-id pub-id-type="doi">10.1109/cict48419.2019.9066212</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>Sangeetha</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Electronic Health Record System using Blockchain</article-title>
          <source>Int Res J Multidiscip Technovation</source>
          <year>2019</year>
          <month>03</month>
          <day>25</day>
          <volume>1</volume>
          <issue>2</issue>
          <fpage>57</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.34256/irjmt1927</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shahnaz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Qamar</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Khalid</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Using Blockchain for Electronic Health Records</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>147782</fpage>
          <lpage>147795</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2946373</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shekhawat</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Cloud-chain: Revamp Health Record System Using Blockchain</article-title>
          <source>Website</source>
          <year>2019</year>
          <access-date>2020-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href=""/>
          </comment>
        </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>Thwin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vasupongayya</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-Based Access Control Model to Preserve Privacy for Personal Health Record Systems</article-title>
          <source>Security and Communication Networks</source>
          <year>2019</year>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2019/8315614"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2019/8315614</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tian</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based secure medical record sharing system</article-title>
          <source>Website</source>
          <year>2019</year>
          <access-date>2020-07-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://eprints.utar.edu.my/3435/">http://eprints.utar.edu.my/3435/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Toshniwal</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Podili</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kataoka</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>PACEX: PAtient-Centric EMR eXchange in Healthcare Systems using Blockchain</article-title>
          <source>IEEE</source>
          <year>2019</year>
          <conf-name>IEEE 10th Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON)</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Vancouver</conf-loc>
          <publisher-loc>PACEX</publisher-loc>
          <publisher-name>PAtient-Centric EMR eXchange in Healthcare Systems using Blockchain. InIEEE 10th Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON)</publisher-name>
          <fpage>2019</fpage>
          <pub-id pub-id-type="doi">10.1109/iemcon.2019.8936258</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>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-Based Personal Health Records Sharing Scheme With Data Integrity Verifiable</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>102887</fpage>
          <lpage>102901</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2931531</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>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Cloud-Assisted EHR Sharing With Security and Privacy Preservation via Consortium Blockchain</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>136704</fpage>
          <lpage>136719</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2943153</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sihua</surname>
              <given-names>Wu</given-names>
            </name>
            <name name-style="western">
              <surname>Jang</surname>
              <given-names>Du</given-names>
            </name>
          </person-group>
          <article-title>Electronic medical record security sharing model based on blockchain</article-title>
          <source>Proceedings of the 3rd International Conference on Cryptography, Security and Privacy</source>
          <year>2019</year>
          <conf-name>ICCSP '19</conf-name>
          <conf-date>2019</conf-date>
          <conf-loc>Japan</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3309074.3309079</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goni</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ibrahim</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A P2P Optimistic Fair-Exchange (OFE) Scheme for Personal Health Records Using Blockchain Technology</article-title>
          <source>Springer</source>
          <year>2020</year>
          <conf-name>3rd International Conference on Wireless, Intelligent and Distributed Environment for Communication</conf-name>
          <conf-date>2020</conf-date>
          <conf-loc>Toronto</conf-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.1007/978-3-030-44372-6_1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arunkumar</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kousalya</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-Based DecentralizedSecure Lightweight E-Health System for Electronic Health Records</article-title>
          <source>Intelligent Systems, Technologies and Applications</source>
          <year>2020</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>273</fpage>
          <lpage>289</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aswin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Basil</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Viswan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Reji</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kuriakose</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Design of AYUSH: A Blockchain-Based Health Record Management System</article-title>
          <source>Inventive Communication and Computational Technologies</source>
          <year>2020</year>
          <publisher-loc>Singapore</publisher-loc>
          <publisher-name>Springer Singapore</publisher-name>
        </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>Cao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Min</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Hybrid blockchain-based privacy-preserving electronic medical records sharing scheme across medical information control system</article-title>
          <source>Measurement and Control</source>
          <year>2020</year>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/full/10.1177/0020294020926636"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/0020294020926636</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>Charanya</surname>
              <given-names>RR</given-names>
            </name>
          </person-group>
          <article-title>SeFra: A Secure Framework to Manage eHealth Records Using Blockchain Technology</article-title>
          <source>International Journal of E-Health and Medical Communications (IJEHMC)</source>
          <year>2020</year>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.4018/ijehmc.2020010101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kavathekar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patil</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Data Sharing and Privacy Preserving of Medical Records Using Blockchain</article-title>
          <source>Lecture Notes on Data Engineering and Communications Technologies</source>
          <year>2020</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>65</fpage>
          <lpage>72</lpage>
        </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>Kim</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Design of Secure Protocol for Cloud-Assisted Electronic Health Record System Using Blockchain</article-title>
          <source>Sensors</source>
          <year>2020</year>
          <month>05</month>
          <day>21</day>
          <volume>20</volume>
          <issue>10</issue>
          <fpage>2913</fpage>
          <pub-id pub-id-type="doi">10.3390/s20102913</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Personal Health Record in FHIR Format Based on Blockchain Architecture</article-title>
          <source>Lecture Notes in Electrical Engineering</source>
          <year>2020</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>1776</fpage>
          <lpage>1788</lpage>
        </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>Sharma</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>lala</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Singhai</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Secure Cloud Storage Architecture for Digital Medical Record in Cloud Environment Using Blockchain</article-title>
          <source>SSRN Journal</source>
          <year>2020</year>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.2139/ssrn.3565922</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>Sharma</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Balamurugan</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Preserving the privacy of electronic health records using blockchain</article-title>
          <source>Procedia Comput Sci</source>
          <year>2020</year>
          <volume>173</volume>
          <issue>1</issue>
          <fpage>171</fpage>
          <lpage>80</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2020.06.021</pub-id>
        </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>Tith</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Suzuki</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wijesundara</surname>
              <given-names>WM</given-names>
            </name>
            <name name-style="western">
              <surname>Taira</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Obi</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ohyama</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Application of blockchain to maintaining patient records in electronic health record for enhanced privacy, scalability, and availability</article-title>
          <source>Healthc Inform Res</source>
          <year>2020</year>
          <month>01</month>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>3</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.e-hir.org/DOIx.php?id=10.4258/hir.2020.26.1.3"/>
          </comment>
          <pub-id pub-id-type="doi">10.4258/hir.2020.26.1.3</pub-id>
          <pub-id pub-id-type="medline">32082695</pub-id>
          <pub-id pub-id-type="pmcid">PMC7010942</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Verdonck</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Poels</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Architecture and Value Analysis of a Blockchain-Based Electronic Health Record Permission Management System</article-title>
          <source>Proceedings of 14th International Workshop on Value Modelling and Business Ontologies</source>
          <year>2020</year>
          <conf-name>14th International Workshop on Value Modelling and Business Ontologies</conf-name>
          <conf-date>Jan 16, 2020</conf-date>
          <conf-loc>Brussels, Belgium</conf-loc>
          <publisher-name>Ghent University</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://biblio.ugent.be/publication/8654183"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Secure personal health records sharing based on blockchain and IPFS</article-title>
          <source>Trusted Computing and Information Security. Communications in Computer and Information Science</source>
          <year>2020</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="web">
          <article-title>Layer</article-title>
          <source>Ethereum</source>
          <year>2020</year>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ethereum.org">https://ethereum.org</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="web">
          <article-title>Neo Smart Economy</article-title>
          <source>NEO team</source>
          <access-date>2020-07-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://neo.org/">https://neo.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="web">
          <article-title>NeoFS data storage, payment, and auditing demoed at Consensus 2019</article-title>
          <source>Neo News Today</source>
          <year>2020</year>
          <access-date>2020-07-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://neonewstoday.com/development/neofs-data-storage-payment-and-auditing-demoed-at-consensus-2019/">https://neonewstoday.com/development/neofs-data-storage-payment-and-auditing-demoed-at-consensus-2019/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="web">
          <article-title>China Bans Digital Coin Offers as Celebrities Like Paris Hilton Tout Them</article-title>
          <source>Walls Street Journal</source>
          <access-date>2020-12-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.wsj.com/articles/some-digital-coins-are-up-2-800-what-could-go-wrong-1504522801">https://www.wsj.com/articles/some-digital-coins-are-up-2-800-what-could-go-wrong-1504522801</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>South Korea bans raising money through initial coin offerings</article-title>
          <source>Reuters</source>
          <access-date>2020-12-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.reuters.com/article/us-southkorea-bitcoin-idUSKCN1C408N. Published September 29, 2017">https://www.reuters.com/article/us-southkorea-bitcoin-idUSKCN1C408N. Published September 29, 2017</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="web">
          <article-title>SEC Issues Investigative Report Concluding DAO Tokens, a Digital Asset, Were Securities</article-title>
          <source>SEC.hov</source>
          <year>2020</year>
          <access-date>2021-04-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sec.gov/news/press-release/2017-131">https://www.sec.gov/news/press-release/2017-131</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
