<?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">v21i2e12439</article-id>
      <article-id pub-id-type="pmid">30747714</article-id>
      <article-id pub-id-type="doi">10.2196/12439</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Implementing Blockchains for Efficient Health Care: Systematic Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
        <contrib contrib-type="editor">
          <name>
            <surname>Clauson</surname>
            <given-names>Kevin</given-names>
          </name>
        </contrib>
        <contrib contrib-type="editor">
          <name>
            <surname>Zhang</surname>
            <given-names>Peng</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Schreiweis</surname>
            <given-names>Björn</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Zheng</surname>
            <given-names>Shuai</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="author" id="contrib1">
          <name name-style="western">
            <surname>Vazirani</surname>
            <given-names>Anuraag A</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-3642-3390</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib2">
          <name name-style="western">
            <surname>O'Donoghue</surname>
            <given-names>Odhran</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-6507-8990</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib3">
          <name name-style="western">
            <surname>Brindley</surname>
            <given-names>David</given-names>
          </name>
          <degrees>MEng, MSc, DPhil, FRSA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-5166-8583</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib4" corresp="yes">
          <name name-style="western">
            <surname>Meinert</surname>
            <given-names>Edward</given-names>
          </name>
          <degrees>MA, MSc, MBA, MPA, CEng FBCS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Healthcare Translation Research Group</institution>
            <institution>Department of Paediatrics</institution>
            <institution>University of Oxford</institution>
            <addr-line>John Radcliffe Hospital</addr-line>
            <addr-line>Oxford,</addr-line>
            <country>United Kingdom</country>
            <phone>44 7824446808</phone>
            <email>edward.meinert@paediatrics.ox.ac.uk</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-2484-3347</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
      <label>1</label>
      <institution>Healthcare Translation Research Group</institution>
      <institution>Department of Paediatrics</institution>  
      <institution>University of Oxford</institution>  
      <addr-line>Oxford</addr-line>
      <country>United Kingdom</country></aff>
      <aff id="aff2">
      <label>2</label>
      <institution>Global Digital Health Unit</institution>
      <institution>Department of Primary Care and Public Health</institution>  
      <institution>Imperial College London</institution>  
      <addr-line>London</addr-line>
      <country>United Kingdom</country></aff>
      <author-notes>
        <corresp>Corresponding Author: Edward Meinert 
        <email>edward.meinert@paediatrics.ox.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection"><month>02</month><year>2019</year></pub-date>
      <pub-date pub-type="epub">
        <day>12</day>
        <month>02</month>
        <year>2019</year>
      </pub-date>
      <volume>21</volume>
      <issue>2</issue>
      <elocation-id>e12439</elocation-id>
      <!--history from ojs - api-xml-->
      <history>
        <date date-type="received">
          <day>7</day>
          <month>10</month>
          <year>2018</year>
        </date>
        <date date-type="rev-request">
          <day>25</day>
          <month>10</month>
          <year>2018</year>
        </date>
        <date date-type="rev-recd">
          <day>27</day>
          <month>11</month>
          <year>2018</year>
        </date>
        <date date-type="accepted">
          <day>29</day>
          <month>12</month>
          <year>2018</year>
        </date>
      </history>
      <copyright-statement>©Anuraag A Vazirani, Odhran O'Donoghue, David Brindley, Edward Meinert. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 12.02.2019.</copyright-statement>
      <copyright-year>2019</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://www.jmir.org/2019/2/e12439/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The decentralized nature of sensitive health information can bring about situations where timely information is unavailable, worsening health outcomes. Furthermore, as patient involvement in health care increases, there is a growing need for patients to access and control their data. Blockchain is a secure, decentralized online ledger that could be used to manage electronic health records (EHRs) efficiently, therefore with the potential to improve health outcomes by creating a conduit for interoperability.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to perform a systematic review to assess the feasibility of blockchain as a method of managing health care records efficiently.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Reviewers identified studies via systematic searches of databases including PubMed, MEDLINE, Scopus, EMBASE, ProQuest, and Cochrane Library. Suitability for inclusion of each was assessed independently.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Of the 71 included studies, the majority discuss potential benefits and limitations without evaluation of their effectiveness, although some systems were tested on live data.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Blockchain could create a mechanism to manage access to EHRs stored on the cloud. Using a blockchain can increase interoperability while maintaining privacy and security of data. It contains inherent integrity and conforms to strict legal regulations. Increased interoperability would be beneficial for health outcomes. Although this technology is currently unfamiliar to most, investments into creating a sufficiently user-friendly interface and educating users on how best to take advantage of it would lead to improved health outcomes.</p>
        </sec>
        <sec sec-type="registered-report">
          <title>International Registered Report Identifier (IRRID)</title>
          <p>RR2-10.2196/10994</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>blockchain</kwd>
        <kwd>electronic health records</kwd>
        <kwd>efficiency</kwd>
        <kwd>interoperability</kwd>
        <kwd>health</kwd>
        <kwd>information science</kwd>
        <kwd>computers</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Medical records in Britain comprise of legacy paper records and numerous disconnected electronic systems. Despite the advancement of other health care fields such as oncology and neurology in their use of technology [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>], there remains a lack of interoperability in health care systems, arising from the nonuniform record storage methods, that restricts doctors in their capacity to provide appropriate care [<xref ref-type="bibr" rid="ref3">3</xref>]. Furthermore, the lack of (correct) information has been considered the primary cause of problems in health care, leading to medical errors and adverse events [<xref ref-type="bibr" rid="ref4">4</xref>]. Not only does this include clinical errors, but administrative ones, such as the recent failure by the National Health Service (NHS) to invite almost 50,000 women for their cervical screening tests [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. Patients must recount their history multiple times, which may be done incompletely. They too appreciate that interoperability would be beneficial in alleviating these adverse events [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. The NHS planned to mend the situation by computerizing all records by 2018, however this target was delayed first to 2020 and again to 2023 [<xref ref-type="bibr" rid="ref9">9</xref>]. In the United States, almost 90% of physicians already use a computerized system [<xref ref-type="bibr" rid="ref10">10</xref>], although these are not all interoperable. Efficient health information technology (IT) systems are especially important at a time when the NHS faces shortages of more than 100,000 doctors and nurses [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], a total that is expected to increase with increasing demands on the service. Blockchain could solve the problem of interoperability by allowing doctors to gather information about a patient from multiple independent systems.</p>
      <p>A blockchain is a decentralized online ledger (database), first implemented to store an ever-increasing record of all transactions using the cryptocurrency, Bitcoin [<xref ref-type="bibr" rid="ref13">13</xref>]. It works by replacing trusted third-party signatories of a transaction (in a financial context, typically a “middle-man” payment provider such as Visa) with computational (cryptographic) proof to validate transactions. This validation is carried out by a network of users (“full nodes”) who collectively adhere to previously agreed rules, which are implemented by the software. This method saves both the cost of mediation, as a blockchain involves no mediator, and the cost associated with reversing transactions when disputes arise, as blockchain transactions are essentially irreversible. The transaction records are grouped into blocks, each of which is locked to the next with a cryptographic hash. Once recorded, data in any given block cannot be modified without altering all subsequent blocks (as each block’s hash depends on the last), nor without the agreement of a majority of the members of the network. As well as in financial services, distributed ledger technology has also been applied in the manufacturing industry to track goods within a supply chain [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>], in governments for voting and public records [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>], and in retail for unmediated goods trading and to allow more sophisticated loyalty packages [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>].</p>
      <p>The system is also flexible enough to allow the addition of arbitrary logic to process, validate, and access the data. This is implemented via components of business logic known as smart contracts, which reside on the blockchain and are synchronized across all nodes. A smart contract is a string of computer code that executes whenever certain conditions are met, ensuring security and authorized access [<xref ref-type="bibr" rid="ref20">20</xref>]. The ability to create smart contracts makes blockchain suitable for health care, where strict regulations govern how sensitive data can be used [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Information exchange using smart contracts is transparent and conflict-free and eliminates the need for a middleman, as the blockchain executes the data sharing based on the preagreed conditions of the contract [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]<bold>.</bold></p>
      <p>Ownership and privacy of data are important issues that blockchain could solve. It is currently debated whether the health care provider or the patient owns health care data relating to a patient (although patients have a definite right to access the data [<xref ref-type="bibr" rid="ref25">25</xref>]). In addition to ownership issues, with the introduction of the General Data Protection Regulation (GDPR) in the European Union, it is important for patients to know how their personal information is being handled [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Smart contracts implemented by a blockchain would simplify the consent process for data access by doctors. The current consent process is not standardized or personalized, which makes it difficult for a patient to express clearly via an access control policy, which may, for example, involve allowing selected access to particular specialists.</p>
      <p>Another concern with medical records is the cost currently associated with transferring records between locations [<xref ref-type="bibr" rid="ref27">27</xref>]. Repeated imaging studies carried out because of unavailability of prior results can be dangerous in terms of delayed treatment as well as financially costly. Sending data via email is considered a security risk [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>], and there is clear inefficiency inherent in transcribing a digital asset onto optical media which is commonly read only once at the receiving site [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. A system integrating patient consent as well as access to authorized individuals would save on these costs.</p>
      <p>Medical information is no longer limited to written reports, imaging studies, and blood tests. Genomic data and that collected by wearable devices, such as bracelets and watches embedded with sensors, are increasingly accumulated. If exploited effectively, the availability of these new forms of data may lead to improved treatment options and outcomes and may also be examined by health insurance companies offering discounts for “healthy” behavior. Further benefits arise in the realm of artificial intelligence. When given the appropriate data, this can infer trends from the data that are then used to generate population-level insight, and so achieve population health as a whole. These new data formats, however, will require careful integration to allow appropriate analysis while maintaining patient privacy and security against hackers.</p>
      <p>Although digitization of health records has been in place in the general practitioner (GP) sector for over 30 years (albeit lacking essential data sharing and exchanging capabilities), secondary care has not yet successfully achieved this de facto standard. Distributed ledger technology, initiated and exemplified by the bitcoin blockchain, is having a growing impact on IT environments in which conformation to legislative regulations and maintenance of public trust are increasingly paramount [<xref ref-type="bibr" rid="ref31">31</xref>], and it may be used in realizing NHS Digital’s target. The aim of this review was to summarize the evidence relating to the implementation of blockchains to manage electronic health records (EHRs), and to discuss whether this would improve efficiency of record management.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>The review protocol [<xref ref-type="bibr" rid="ref32">32</xref>] was used with the following modifications: (1) The research question was narrowed to focus on efficiency, as the issues of privacy and scalability would broaden the review excessively, (2) A total of 5 additional search databases were included to account for the potential lack of published research on the topic, and (3) The population was extended to anyone whose health data are stored in a blockchain.</p>
      <sec>
        <title>Research Question and Definitions</title>
        <disp-formula>RQ: What strategies have been proposed or trialed to implement a blockchain or blockchains for the management of electronic medical records, and how do they improve efficiency compared to currently employed medical record management methods?</disp-formula>
        <list list-type="order">
          <list-item>
            <p><italic>Medical record</italic>: [any] record consisting of information about the physical or mental health or condition of an identifiable individual made by or on behalf of a health professional in connection with the care of that individual [<xref ref-type="bibr" rid="ref33">33</xref>].</p>
          </list-item>
          <list-item>
            <p><italic>Efficiency</italic>: Either improved interoperability or cost-effectiveness, or improved health outcomes as a result of these.</p>
          </list-item>
          <list-item>
            <p><italic>Current methods</italic>: These may consist of traditional paper-based methods or more advanced technology adopted to provide more coordinated health care.</p>
          </list-item>
          <list-item>
            <p><italic>Interoperability</italic>: Automatic and seamless exchange of health information across health information systems [<xref ref-type="bibr" rid="ref34">34</xref>]. (This corresponds to syntactic interoperability.)</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Ethics and Dissemination</title>
        <p>As data collection was executed via published literature, ethical approval was not be required for this review.</p>
      </sec>
      <sec>
        <title>Search Strategy and Study Selection</title>
        <p>We searched PubMed, Scopus, EMBASE, MEDLINE, ProQuest, CINAHL, AMED, Global Health, Books@Ovid, and Cochrane Library for all relevant literature. We also searched for other systematic reviews on the topic on the PROSPERO [<xref ref-type="bibr" rid="ref35">35</xref>] database. We used the MeSH database [<xref ref-type="bibr" rid="ref34">34</xref>] to derive keywords and search term combinations (<xref ref-type="app" rid="app1">Multimedia Appendix 1</xref>). As blockchains applied to the health care sector remain a novel approach, we did not place restrictions on the study type, dates of publication, or geographic locations. However, only studies in English were included.</p>
        <p>Results of the search strings (<xref ref-type="app" rid="app2">Multimedia Appendix 2</xref>) were imported into EndNote X8.0.1 (Clarivate Analytics), which was used to remove duplicate articles. Remaining duplicates were deleted manually. We used an iterative approach of title, abstract, and full text searches (<xref ref-type="app" rid="app3">Multimedia Appendix 3</xref>) and exported the results into Microsoft Excel. Titles and abstracts were then independently screened by 2 reviewers, based on the following inclusion criteria:</p>
        <list list-type="order">
          <list-item>
            <p>Articles must discuss the use of blockchain to manage medical records in some manner, and</p>
          </list-item>
          <list-item>
            <p>Articles must describe the benefits and/or disadvantages of using this technology (and compare this to currently used methods of managing medical data).</p>
          </list-item>
        </list>
        <p>Where the second point may not be determined from the abstract alone, the study should be taken to full text screening. Studies may not identify a comparator, and these may be included provided the remaining inclusion criteria are met.</p>
        <p>A total of 2 reviewers (AV and OO) resolved discrepancies through discussion (<xref ref-type="app" rid="app4">Multimedia Appendix 4</xref>), and no adjudication from a third reviewer was required. The full texts of the remaining articles were subsequently assessed for their eligibility, based on the same eligibility criteria. This selection process is demonstrated using the Preferred Reporting Items for Systematic Reviews and Meta-Analyses flow diagram (<xref ref-type="fig" rid="figure1">Figure 1</xref>).</p>
      </sec>
      <sec>
        <title>Data Extraction</title>
        <p>A template was designed to collect information required to address the research question. Basic metadata were collected automatically by EndNote, and the remaining data items (<xref ref-type="app" rid="app5">Multimedia Appendix 5</xref>) were gathered after reading the papers in full.</p>
      </sec>
      <sec>
        <title>Outcomes</title>
        <p>The primary outcome measures were interoperability and cost-effectiveness (our definition of efficiency). The secondary outcome measure was improved health outcomes, although it was noted that it might be difficult to determine a quantitative measure of this with respect to blockchains.</p>
      </sec>
      <sec>
        <title>Strength of Evidence and Data Synthesis</title>
        <p>Studies of interventions involving randomized and nonrandomized methods were assessed for risk of bias using the Cochrane Collaboration Risk of Bias Tool and the Risk of Bias in Nonrandomized Studies - of Interventions tools, respectively.</p>
        <p>The extracted data were subsequently summarized qualitatively. No meta-analysis was performed, because application of blockchains in health care remains a novel method and articles with sufficient numerical data were not found. In addition, the heterogeneity of studies prevented a meta-analysis.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses flow diagram.</p>
          </caption>
          <graphic xlink:href="jmir_v21i2e12439_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Description and Characteristics of Included Studies</title>
        <p>After the initial literature search, removal of duplicates, eligibility (<xref ref-type="app" rid="app6">Multimedia Appendix 6</xref>), and full-text screening, 61 articles were included in the study. An additional 10 articles were added via snowballing (review of the references from the included articles) of the full texts screened (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <p>Few studies described the implementation of a blockchain system to real-world medical data, highlighting the novelty of this technique. Of these, 1 [<xref ref-type="bibr" rid="ref36">36</xref>] used smart contracts to manage access to medical data that were stored on the cloud, whereas the others stored medical data directly on the blockchain. Of the largest group of articles which proposed a framework (without testing it on live data), the majority advocated cloud-based data storage with blockchain-based access control. In addition to the primary outcome of interoperability, issues considered in these articles included those of privacy and data security, scalability, and administrative affairs. There are also a number of companies currently implementing blockchains in health care, which were referred to throughout the literature, and many of which have not published any academic literature. These are collated in <xref ref-type="app" rid="app7">Multimedia Appendix 7</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Summary themes of included articles.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="700"/>
            <col width="300"/>
            <thead>
              <tr valign="top">
                <td>Article type</td>
                <td>Number of articles</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Implementation of EHR<sup>a</sup> blockchain system (tested on real data)</td>
                <td>4 [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref39">39</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Proposal of EHR blockchain framework (not tested on real data)</td>
                <td>18 [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref52">52</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Discussion of benefits and drawbacks of the use of blockchain for EHRs</td>
                <td>10 [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref53">53</xref>-<xref ref-type="bibr" rid="ref59">59</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Description of company in the field</td>
                <td>20 (<xref ref-type="app" rid="app7">Multimedia Appendix 7</xref>)</td>
              </tr>
              <tr valign="top">
                <td>Newspaper, magazine, and columns (opinion articles)</td>
                <td>19 in searched databases</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>EHR: electronic health record.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>The majority of the information comparing blockchain’s potential versus current methods of managing records was found in opinion articles, which were set more broadly in the context of developments in health care technology; many described the disarray of current health record management. Some used the successes of blockchain in other fields than health care and finance to demonstrate its versatility.</p>
      </sec>
      <sec>
        <title>Outcome Measures</title>
        <p>Interoperability, one of our primary outcome measures, was seen as feasible using a blockchain approach to store an index of records and to manage access to cloud-based records [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. This approach saves the administrative costs involved in transporting records, as well as the medical costs associated with waiting for their arrival. Logistical difficulties and costs may arise in collating legacy data, although we expect that these would be accounted for in savings from improved health outcomes in the long term.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of Evidence</title>
        <p>A blockchain can allow improved interoperability as data across multiple systems can be exchanged and accessed simultaneously and immediately. The interfacing of different systems would also save costs, as no expensive data mediators or escrow services are required to broker trust [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. Costs are also saved in the process of data transfer, which becomes immediate [<xref ref-type="bibr" rid="ref27">27</xref>]. This is especially useful in the management of patients suffering from chronic diseases, facilitating the delivery of care by connecting both patients and providers with medical data. These factors, therefore, reduce administrative delays, as does the use of smart contracts to execute patients’ consent preferences immediately [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. An off blockchain data repository (“data lake”) is scalable and can store a variety of data types, as well as being a tool for research. This is in contrast to current health care data systems, which are not synchronized to allow intersystem communication or equipped to manage emerging data formats [<xref ref-type="bibr" rid="ref9">9</xref>]. Blockchain is interactive and supports high throughput data analysis and machine learning, while being encrypted and digitally signed to ensure data privacy and authenticity [<xref ref-type="bibr" rid="ref51">51</xref>]. These are particularly important factors in a field that is both dominated by evidence-based research but bound by strict data regulations [<xref ref-type="bibr" rid="ref21">21</xref>]. The disjointed systems currently in use do not lend themselves toward such modern research techniques, nor are they stored in a secure or immutable manner. The collaboration between patients, doctors, and researchers arising from a blockchain-based system allows for a greater degree of exchange and comparison, leading to specific and personalized care pathways [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. The Office of the National Coordinator for Health Information Technology (ONC) has recently described several features critical to the development of an interoperable health system, which are addressed by blockchain [<xref ref-type="bibr" rid="ref60">60</xref>], such as establishing a directory of resource locations that can be easily referenced to locate information and creating an economic environment in which interoperability is a sound business decision[<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>Interoperability</title>
        <p>Health data are dynamic and expansive, and seamless exchange of health data across health information systems would be advantageous. As it would not be practical in terms of speed, storage capacity, or sustainability to replicate all health records on every computer in the blockchain network [<xref ref-type="bibr" rid="ref54">54</xref>], we instead advocate blockchain as a method to manage access control (and for smart contract management) by systematically storing a catalogue of all users’ health records and related metadata. Each time data are added to the EHR by a doctor or patient (from a mobile app or wearable sensor), a metadata-containing pointer to this is added to the blockchain, while the data are stored securely on the cloud [<xref ref-type="bibr" rid="ref51">51</xref>]. A full index of a particular patient’s records is stored in a single location along with related metadata, regardless of the whereabouts of the medical data. The blockchain, with this secured index of records, then directs authorized individuals to the cloud-based data, thus allowing the immediate exchange of information between approved professionals, while also keeping an immutable ledger of those readers. The fact that blockchain is based on open-source software also has potential benefits, as health trusts can use the open application programming interface to integrate data as they wish, giving them timely access to accurate information in a format useable by them. Striving for interoperability is also a key feature of the Health Information Technology for Economic and Clinical Health Act, which has meant that since 2011; American health care providers have been given financial incentives to demonstrate meaningful use of EHRs [<xref ref-type="bibr" rid="ref61">61</xref>].</p>
      </sec>
      <sec>
        <title>Health</title>
        <p>Fast access to a comprehensive set of patient data would allow doctors to treat patients without the need to wait for the arrival of previous results. The availability not only of prompt but more frequent data would allow physicians to create specialized treatment plans on the basis of outcomes and treatment efficacy. Daily health data would also engage a patient more in their own health care, and improve patient compliance [<xref ref-type="bibr" rid="ref51">51</xref>], a historic challenge in the field [<xref ref-type="bibr" rid="ref62">62</xref>]. The capability of personalized medicine would, therefore, be improved with this interoperability, as a single access point for all real-time health data is created for each patient. Data gathered from wearable sensors and mobile apps would contribute information on the risks and benefits of treatments, and on patient-reported outcome measures.</p>
      </sec>
      <sec>
        <title>Integrity</title>
        <p>The immutability of a blockchain that stems from linking the hashes of subsequent blocks, carries with it inherent integrity as blocks cannot be rewritten without collaboration of a majority of nodes. This is key to maintaining a true record of patient-provider interactions as well as data originating from devices, both of which could influence not only medical decisions but also those involving insurance. This property was exemplified by RadBit at the 2017 Yale Healthcare Hackathon [<xref ref-type="bibr" rid="ref46">46</xref>], a system which allows patients to keep possession of their medical images, along with an immutable chain of custody. Temporary keys (“tokens”) can be created by users of the blockchain and passed onto those such as health care providers and insurance companies, providing them temporary access. The token is independent of the data, containing only authorization commands, and is verified and validated (by recording them on the chain) before the required reports are dispatched. Integrity may also be maintained by the use of external auditors, who may verify the accuracy of the system in real time and retrospectively [<xref ref-type="bibr" rid="ref21">21</xref>]. Potential ways to improve the integrity are to use blind signatures, which reinforce protection from tampering as well as confirming the sender’s and viewer’s identities [<xref ref-type="bibr" rid="ref53">53</xref>], or to use signatures from multiple authorities [<xref ref-type="bibr" rid="ref42">42</xref>].</p>
      </sec>
      <sec>
        <title>The Office of the National Coordinator for Health Information Technology Blockchain Challenge</title>
        <p>In 2016, the ONC organized the “Use of Blockchain in Health IT and Health-Related Research” challenge, seeking ideas to address the difficulties of managing health records [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]. Winning papers described innovative ways to securely empower patients through interoperability [<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]. MedRec, one of the winning entries, is now being implemented in Boston. This proposal from Massachusetts Institute of Technology’s media lab involves associating a medical record with viewing permissions and data retrieval instructions for execution on external databases, thus using the blockchain to record patient-provider interactions via smart contracts. Once a doctor creates a record, it is verified, and its viewing permissions are authorized by the patient. The party receiving new information receives an automated notification [<xref ref-type="bibr" rid="ref3">3</xref>] and a hashed pointer to the new medical record, and its permissions are stored on the chain. This system allows patients to be empowered through access and control of their data, options which have until recently not been available outside a trial setting [<xref ref-type="bibr" rid="ref57">57</xref>], and which we hope will soon become a standard of care. So far, their system has been successful with medications, blood tests, vaccination histories, and other therapeutic interventions [<xref ref-type="bibr" rid="ref66">66</xref>].</p>
      </sec>
      <sec>
        <title>Large-Scale Implementation</title>
        <p>Blockchain has recently been adopted on a large scale by the Estonian government, in collaboration with Guardtime, where it now secures millions of records. Other companies involved in introducing blockchain to everyday health care include Medicalchain, which allows users to sign up and use the interface to interact with their GP, and Patientory that connects doctors, health providers, and consumers, and others listed in <xref ref-type="app" rid="app7">Multimedia Appendix 7</xref>.</p>
      </sec>
      <sec>
        <title>Challenges and Limitations</title>
        <sec>
          <title>Data Ownership and Privacy</title>
          <p>Achieving interoperability depends on patients taking control of their data and deciding on how it is to be used, features integral to blockchain. Although shifting data ownership from the government and companies to patients would require extensive reengineering of legacy systems to introduce a blockchain, it would incentivize patients to become active agents in their own care by contributing data to get the best possible treatment [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref68">68</xref>]. The blockchain would also give patients the sole power to authorize data access to various providers at their discretion [<xref ref-type="bibr" rid="ref41">41</xref>], eliminating delays associated with the current bureaucracy [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref69">69</xref>], and ensuring patient privacy [<xref ref-type="bibr" rid="ref21">21</xref>]. These benefits bestowed by blockchain stand to empower patients with control over their data, a new expectation in a time when mutualistic and consumerist patient-doctor relationships are becoming the norm. Patients could also selectively share data with researchers using blockchain, either for the greater scientific good or to enable studies on their unique condition [<xref ref-type="bibr" rid="ref70">70</xref>]. The system would guarantee their consent, a factor key to establishing autonomy and patient-centered care. A recent example of patient autonomy over health data is 23andMe, 80% of whose users chose to make their genomic data available to researchers. This demonstrates that patients will be happy to share data for research should they stand to benefit. Enabling direct patient involvement in controlling the use of their records in this open and secure manner enabled by blockchain will enhance the uptake of such platforms and potentially lead to improved health outcomes [<xref ref-type="bibr" rid="ref31">31</xref>]. Sharing data may be accomplished with a trusted system, but as an additional incentive, there is the idea of “rewarding” patients for healthy behavior, such as with lower insurance premiums [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]. This and other similar ideas will need to be piloted to determine how effectively they will overcome this challenge.</p>
        </sec>
        <sec>
          <title>Legal</title>
          <p>Under GDPR (Article 17), the Organization of Economic Cooperation and Development privacy guideline, the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule, and others [<xref ref-type="bibr" rid="ref58">58</xref>], individuals may request for their data to be erased. This is possible when the records themselves are not stored on the blockchain. However, a record of the data’s previous existence may still be maintained within the chain, even if the data were to be deleted. The legal question arising from this relates to whether metadata of personal data classifies as personal data [<xref ref-type="bibr" rid="ref54">54</xref>]. Regardless, the fact that data in the system would in any case be controlled by the patient is a definite sign of progress. A potential limitation here arises with respect to the use of a private or consortium-led blockchain, as these data privacy concerns would need to be addressed to make the services compliant and vendor neutral. This may be achieved by having a governing authority enforce open standards. Although these sorts of regulatory constraints are necessary to ensure such appropriate use of information, they may slow development in the field. HIPAA, for example, requires that an institutional review board approve the use of data [<xref ref-type="bibr" rid="ref21">21</xref>]. That any such delay would be substantial is however unlikely, and so compliance with these regulations is paramount to the success of blockchain.</p>
        </sec>
        <sec>
          <title>Security</title>
          <p>Sensitive data must be kept safe from eavesdroppers and intruders [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]. Breaches have a negative impact on the public perception of the health care field and threaten to hinder future research through more stringent regulatory restrictions [<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref73">73</xref>]. The WannaCry attack of May 2017 infected many thousands of computers worldwide, including those of the NHS [<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>]. One earlier attack in Los Angeles targeted EHRs in particular, demanding thousands of dollars in ransom [<xref ref-type="bibr" rid="ref76">76</xref>]. A blockchain is more secure than legacy methods, which would issue patients with credentials [<xref ref-type="bibr" rid="ref23">23</xref>]. It achieves this property by the use of public-key cryptography (as opposed to symmetric-key cryptography, the method typically used for encryption). This involves generating a public and private key for each user using a one-way encryption function, known as a hash. There is no way for anyone but the recipient to see information sent over the blockchain, as it is secured by their private key. The only security flaw that may arise with a blockchain is unrelated to encryption and comes about if a public blockchain is used: hackers could collude in a “51% attack,” resulting in the rewriting of the chain structure [<xref ref-type="bibr" rid="ref77">77</xref>]. Thus, to realize the advantages of a decentralized system, patients must have some trust that at least 50% of mining nodes would not want to violate the immutability of the blockchain. The public blockchain also leads to the possibility of patient identification, which would need to be avoided by pseudonymizing data to protect patients’ identities [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]. If a private or consortium blockchain was to be used, however, mining nodes would be limited to hospitals and other trusted health providers, eliminating these security flaws.</p>
        </sec>
        <sec>
          <title>Other Concerns</title>
          <p>Although the major concerns with blockchain are those of security, privacy, and legal restrictions, for which various workarounds have been developed, there remain some further challenges to consider. First, consolidating data from legacy systems will involve removing data that are duplicated in different parts of the system [<xref ref-type="bibr" rid="ref8">8</xref>] and converting outdated file formats. This introduces an implementation cost, in excess of the basic cost to introduce a blank system [<xref ref-type="bibr" rid="ref78">78</xref>], which a government may not be willing to spend [<xref ref-type="bibr" rid="ref79">79</xref>]. Second, as with any system, it is necessary for users to input good quality information: the trustworthiness arising from blockchain’s immutability and decentralization concedes to the input of low-quality (incorrect) information [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Finally, the issue of currency, used in blockchain to incentivize users to mine blocks in the new network. An initial coin offering [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref80">80</xref>] could initiate this process by valuing the new token as funds are raised. However, extremes of price could deter miners, and so mining may need to be restricted to health care providers to avoid this. Another view is to remove all currency, as data are owned by the patient and are not inherently an exchangeable currency [<xref ref-type="bibr" rid="ref23">23</xref>]. On the basis of this, we may assume that providers already have an incentive to secure patients’ medical information, and so there would be no need to incentivize mining beyond the simple use of the system. Finally, the reliance of a blockchain on essentially arbitrary computation could be seen to introduce administrative inefficiency [<xref ref-type="bibr" rid="ref31">31</xref>]. Transactions are therefore energy-intensive, as each must be computationally verified and validated by the whole network [<xref ref-type="bibr" rid="ref45">45</xref>]. However, such a mechanism is still beneficial, as rather than providing economic value it demonstrates proof-of-participation, which would be required for ongoing use of the system.</p>
        </sec>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The storage and sharing of medical data (developing interoperability) are vital for improved health outcomes. Respecting privacy of sensitive information while doing this remains a big challenge in health care. The literature shows that with the appropriate regulatory guidelines and use standards, blockchain can act as a vehicle to manage consented access to EHRs. This will increase interoperability without compromising security, while also protecting patient privacy. These issues would most effectively be tackled by the use of a private or consortium-led blockchain; however, this would need to be regulated to ensure appropriate use of data. The improved interoperability and reduced long-term administrative costs would lead to improved health outcomes.</p>
        <p>Blockchain represents a new form of technology in which the current literature is lacking in this application context, and no usage feedback or statistical comparisons with traditional systems exist. There are costs associated with transferring to a new system, and in educating health professionals and patients on how best to take advantage of it for improved health. Blockchain involves concepts unfamiliar to the vast majority of the population, such as cryptographic signature and key management. Investments into new systems would, however, be outweighed through returns. In the primary stages of implementation, the practical usefulness of the proposed system will likely depend on the end-user experience—the complexities underlying the blockchain will need to be hidden behind a sufficiently user-friendly interface such as an online or mobile app to be adopted successfully. Short-term trials will outline the most effective ways to implement such a user-friendly experience, which may be expanded thereafter.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <app id="app1">
        <title>Multimedia Appendix 1</title>
        <p>Search terms and keywords.</p>
        <media xlink:href="jmir_v21i2e12439_app1.docx" xlink:title="DOCX File, 12KB"/>
      </app>
      <app id="app2">
        <title>Multimedia Appendix 2</title>
        <p>Search strings.</p>
        <media xlink:href="jmir_v21i2e12439_app2.docx" xlink:title="DOCX File, 13KB"/>
      </app>
      <app id="app3">
        <title>Multimedia Appendix 3</title>
        <p>Electronic screening.</p>
        <media xlink:href="jmir_v21i2e12439_app3.docx" xlink:title="DOCX File, 13KB"/>
      </app>
      <app id="app4">
        <title>Multimedia Appendix 4</title>
        <p>Title and abstract screening.</p>
        <media xlink:href="jmir_v21i2e12439_app4.docx" xlink:title="DOCX File, 12KB"/>
      </app>
      <app id="app5">
        <title>Multimedia Appendix 5</title>
        <p>Data extraction items.</p>
        <media xlink:href="jmir_v21i2e12439_app5.docx" xlink:title="DOCX File, 12KB"/>
      </app>
      <app id="app6">
        <title>Multimedia Appendix 6</title>
        <p>Eligibility stage search exclusions.</p>
        <media xlink:href="jmir_v21i2e12439_app6.docx" xlink:title="DOCX File, 12KB"/>
      </app>
      <app id="app7">
        <title>Multimedia Appendix 7</title>
        <p>Blockchain and company system names.</p>
        <media xlink:href="jmir_v21i2e12439_app7.docx" xlink:title="DOCX File, 12KB"/>
      </app>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">GP</term>
          <def>
            <p>general practitioner</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HIPAA</term>
          <def>
            <p>Health Insurance Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">IT</term>
          <def>
            <p>information technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">ONC</term>
          <def>
            <p>Office of the National Coordinator for Health Information Technology</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This work was supported by the Sir David Cooksey Fellowship in Healthcare Translation (EM), the SENS Research Foundation (EM), the Oxford Academic Health Sciences Centre (EM), and the Final Honor School of Medical Sciences, Cell &amp; Systems, Biology and Neuroscience at the University of Oxford (AV).</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>EM conceived the study topic and oversaw the project. AV investigated and executed bench research and completed manuscript drafting on his own. OD completed peer review of papers for analysis and gave helpful discussion on content. EM gave feedback on the completed manuscript to AV who incorporated all feedback. DB also provided feedback on iterations. AV responded to peer review facilitated by EM. The final manuscript was approved by all authors. EM is the guarantor.</p>
      </fn>
      <fn fn-type="conflict">
        <p>DB is a stockholder in Translation Ventures Ltd (Charlbury, UK), IP Asset Ventures Ltd, and Biolacuna Ltd (Oxford, UK), companies that, among other services, provide biomanufacturing, regulatory, and financial advice to pharmaceutical clients. DB is also subject to the CFA Institute's codes, standards, and guidelines, so he must stress that this piece is provided for academic interest only and must not be construed in any way as an investment recommendation. Additionally, at time of publication, DB and the organizations with which he is affiliated may or may not have agreed to and/or pending funding commitments from the organizations named herein.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Sample</surname>
            <given-names>I</given-names>
          </name>
        </person-group>
        <source>The Guardian</source>  
        <access-date>2018-11-14</access-date>
        <comment>'It's going to create a revolution': how AI is transforming the NHS 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.theguardian.com/technology/2018/jul/04/its-going-create-revolution-how-ai-transforming-nhs">https://www.theguardian.com/technology/2018/jul/04/its-going-create-revolution-how-ai-transforming-nhs</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="749i1L3v9"/></comment> </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>Ding</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Sohn</surname>
            <given-names>JH</given-names>
          </name>
          <name name-style="western">
            <surname>Kawczynski</surname>
            <given-names>MG</given-names>
          </name>
          <name name-style="western">
            <surname>Trivedi</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Harnish</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Jenkins</surname>
            <given-names>NW</given-names>
          </name>
          <name name-style="western">
            <surname>Lituiev</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Copeland</surname>
            <given-names>TP</given-names>
          </name>
          <name name-style="western">
            <surname>Aboian</surname>
            <given-names>MS</given-names>
          </name>
          <name name-style="western">
            <surname>Aparici</surname>
            <given-names>CM</given-names>
          </name>
          <name name-style="western">
            <surname>Behr</surname>
            <given-names>SC</given-names>
          </name>
          <name name-style="western">
            <surname>Flavell</surname>
            <given-names>RR</given-names>
          </name>
          <name name-style="western">
            <surname>Huang</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Zalocusky</surname>
            <given-names>KA</given-names>
          </name>
          <name name-style="western">
            <surname>Nardo</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Seo</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Hawkins</surname>
            <given-names>RA</given-names>
          </name>
          <name name-style="western">
            <surname>Pampaloni</surname>
            <given-names>MH</given-names>
          </name>
          <name name-style="western">
            <surname>Hadley</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Franc</surname>
            <given-names>BL</given-names>
          </name>
        </person-group>
        <article-title>A deep learning model to predict a diagnosis of alzheimer disease by using F-FDG PET of the brain</article-title>
        <source>Radiology</source>  
        <year>2018</year>  
        <month>11</month>  
        <day>6</day>  
        <fpage>180958</fpage>  
        <pub-id pub-id-type="doi">10.1148/radiol.2018180958</pub-id>
        <pub-id pub-id-type="medline">30398430</pub-id></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Brock</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Healthcare Innovation</source>  
        <year>2017</year>  
        <month>05</month>  
        <day>25</day>  
        <access-date>2019-02-02</access-date>
        <comment>Healing revenue cycle management 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hcinnovationgroup.com/finance-revenue-cycle/article/13008199/healing-revenue-cycle-management">https://www.hcinnovationgroup.com/finance-revenue-cycle/article/13008199/healing-revenue-cycle-management</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tD2Hagj"/></comment> </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
        <source>CRICO</source>  
        <year>2015</year>  
        <comment>Malpractice Risks in Communication Failures 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rmf.harvard.edu/Malpractice-Data/Annual-Benchmark-Reports/Risks-in-Communication-Failures">https://www.rmf.harvard.edu/Malpractice-Data/Annual-Benchmark-Reports/Risks-in-Communication-Failures</ext-link></comment> </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
        <source>Capita</source>  
        <access-date>2019-02-02</access-date>
        <comment>Capita statement on cervical screening correspondence delay 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.capita.com/news/news/2018/capita-statement-on-cervical-screening-correspondence-delay/">https://www.capita.com/news/news/2018/capita-statement-on-cervical-screening-correspondence-delay/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tDEQHcT"/></comment> </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Iacobucci</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Cervical screening: GP leaders slam Capita over failure to send up to 48 500 letters</article-title>
        <source>Br Med J</source>  
        <year>2018</year>  
        <month>11</month>  
        <day>14</day>  
        <fpage>k4832</fpage>  
        <pub-id pub-id-type="doi">10.1136/bmj.k4832</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
        <source>PwC UK</source>  
        <access-date>2019-02-02</access-date>
        <comment>Majority of public have never accessed their own health records 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pwc.co.uk/press-room/press-releases/majority-of-public-have-never-accessed-their-own-health-records.html">https://www.pwc.co.uk/press-room/press-releases/majority-of-public-have-never-accessed-their-own-health-records.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tDJNqKK"/></comment> </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>Engelhardt</surname>
            <given-names>MA</given-names>
          </name>
        </person-group>
        <article-title>Hitching healthcare to the chain: an introduction to blockchain technology in the healthcare sector</article-title>
        <source>TIM Rev</source>  
        <year>2017</year>  
        <month>10</month>  
        <day>27</day>  
        <volume>7</volume>  
        <issue>10</issue>  
        <fpage>22</fpage>  
        <lpage>34</lpage>  
        <pub-id pub-id-type="doi">10.22215/timreview/1111</pub-id></nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
        <source>Department of Health &amp; Social Care</source>  
        <access-date>2018-07-13</access-date>
        <comment>Making IT work: harnessing the power of health information technology to improve care in England 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/government/publications/using-information-technology-to-improve-the-nhs/making-it-work-harnessing-the-power-of-health-information-technology-to-improve-care-in-england">https://www.gov.uk/government/publications/using-information-technology-to-improve-the-nhs/making-it-work-harnessing-the-power-of-health-information-technology-to-improve-care-in-england</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gDg6PI5"/></comment> </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Jamoom</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Yang</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <source>Centers for Disease Control and Prevention</source>  
        <year>2016</year>  
        <access-date>2018-09-11</access-date>
        <comment>National Electronic Health Records Survey: 2015 State and National Electronic Health Record Adoption Summary Tables 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/nchs/data/ahcd/nehrs/2015_nehrs_web_table.pdf">https://www.cdc.gov/nchs/data/ahcd/nehrs/2015_nehrs_web_table.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gDyiV4m"/></comment> </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
        <source>The Nuffield Trust</source>  
        <access-date>2019-02-02</access-date>
        <comment>The health care workforce in England 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nuffieldtrust.org.uk/files/2018-11/health-foundation-king-s-fund-and-nuffield-trust-the-health-care-workforce-in-england.pdf">https://www.nuffieldtrust.org.uk/files/2018-11/health-foundation-king-s-fund-and-nuffield-trust-the-health-care-workforce-in-england.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tDcPHRK"/></comment> </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Iacobucci</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>NHS staff shortages could reach 250 000 by 2030 without urgent action, experts warn</article-title>
        <source>Br Med J</source>  
        <year>2018</year>  
        <month>11</month>  
        <day>14</day>  
        <volume>363</volume>  
        <fpage>k4831</fpage>  
        <pub-id pub-id-type="doi">10.1136/bmj.k4831</pub-id>
        <pub-id pub-id-type="medline">30442691</pub-id></nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nakamoto</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <source>Bitcoin</source>  
        <year>2008</year>  
        <access-date>2018-11-04</access-date>
        <comment>Bitcoin: A Peer-to-Peer Electronic Cash System 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bitcoin.org/bitcoin.pdf">https://bitcoin.org/bitcoin.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gEKsOBp"/></comment> </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
        <source>Skuchain</source>  
        <access-date>2018-11-14</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.skuchain.com/">http://www.skuchain.com/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="73vJXmYwP"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
        <source>Wayback Machine</source>  
        <access-date>2018-11-14</access-date>
        <comment>Blockchain: the solution for transparency in product supply chains 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://web.archive.org/web/20180920095159/https://www.provenance.org/whitepaper">http://web.archive.org/web/20180920095159/https://www.provenance.org/whitepaper</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73vJRTl2X"/></comment> </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Aki</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Bitcoin Magazine</source>  
        <access-date>2018-11-14</access-date>
        <comment>Thailand Uses Blockchain-Supported Electronic Voting System in Primaries 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bitcoinmagazine.com/articles/thailand-uses-blockchain-supported-electronic-voting-system-primaries/">https://bitcoinmagazine.com/articles/thailand-uses-blockchain-supported-electronic-voting-system-primaries/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73vK241Jm"/></comment> </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ruubel</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <source>Guardtime</source>  
        <access-date>2018-11-14</access-date>
        <comment>Blockchain-Enabled Cloud: Estonian Government selects Ericsson, Apcera and Guardtime 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://guardtime.com/blog/blockchain-enabled-cloud-estonian-government-selects-ericsson-apcera-and-guardtime">https://guardtime.com/blog/blockchain-enabled-cloud-estonian-government-selects-ericsson-apcera-and-guardtime</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73vJmtlDt"/></comment> </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
        <source>OpenBazaar</source>  
        <access-date>2018-11-14</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://openbazaar.org/">https://openbazaar.org/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="73vK9DRMy"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
        <source>Loyyal</source>  
        <access-date>2018-11-14</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.loyyal.com/">https://www.loyyal.com/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="73vKSBkb3"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wright</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Wright</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Landman</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <source>NEJM Catalyst</source>  
        <year>2017</year>  
        <month>02</month>  
        <day>9</day>  
        <access-date>2018-11-04</access-date>
        <comment>Blockchain in Health Care: Decoding the Hype 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://catalyst.nejm.org/decoding-blockchain-technology-health/">https://catalyst.nejm.org/decoding-blockchain-technology-health/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gERTHFx"/></comment> </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>Mamoshina</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Ojomoko</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Yanovich</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Ostrovski</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Botezatu</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Prikhodko</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Izumchenko</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Aliper</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Romantsov</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Zhebrak</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Ogu</surname>
            <given-names>IO</given-names>
          </name>
          <name name-style="western">
            <surname>Zhavoronkov</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Converging blockchain and next-generation artificial intelligence technologies to decentralize and accelerate biomedical research and healthcare</article-title>
        <source>Oncotarget</source>  
        <year>2018</year>  
        <month>01</month>  
        <day>19</day>  
        <volume>9</volume>  
        <issue>5</issue>  
        <fpage>5665</fpage>  
        <lpage>90</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.impactjournals.com/oncotarget/misc/linkedout.php?pii=22345"/>
        </comment>  
        <pub-id pub-id-type="doi">10.18632/oncotarget.22345</pub-id>
        <pub-id pub-id-type="medline">29464026</pub-id>
        <pub-id pub-id-type="pii">22345</pub-id>
        <pub-id pub-id-type="pmcid">PMC5814166</pub-id></nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Patel</surname>
            <given-names>V</given-names>
          </name>
        </person-group>
        <article-title>A framework for secure and decentralized sharing of medical imaging data via blockchain consensus</article-title>
        <source>Health Informatics J</source>  
        <year>2018</year>  
        <month>04</month>  
        <day>1</day>  
        <fpage>1460458218769699</fpage>  
        <pub-id pub-id-type="doi">10.1177/1460458218769699</pub-id>
        <pub-id pub-id-type="medline">29692204</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>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>Sustain Cities Soc</source>  
        <year>2018</year>  
        <month>05</month>  
        <volume>39</volume>  
        <fpage>283</fpage>  
        <lpage>97</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.scs.2018.02.014</pub-id></nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Alhadhrami</surname>
            <given-names>Z</given-names>
          </name>
          <name name-style="western">
            <surname>Alghfeli</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Alghfeli</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Abedlla</surname>
            <given-names>JA</given-names>
          </name>
          <name name-style="western">
            <surname>Shuaib</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Introducing Blockchains for Healthcare</article-title>
        <year>2017</year>  
        <month>11</month>  
        <day>23</day>  
        <conf-name>2017 International Conference on Electrical and Computing Technologies and Applications (ICECTA)</conf-name>
        <conf-date>November 21-23, 2017</conf-date>
        <conf-loc>Ras Al Khaimah, United Arab Emirates</conf-loc>
        <pub-id pub-id-type="doi">10.1109/ICECTA.2017.8252043</pub-id></nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
        <source>Nottinghamshire Local Medical Committee Ltd</source>  
        <year>2018</year>  
        <month>06</month>  
        <access-date>2019-02-02</access-date>
        <comment>Access to health records: Updated to reflect the General Data Protection Regulation 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bma.org.uk/-/media/files/pdfs/employment%20advice/ethics/access%20to%20health%20records%2027%20june%202018.pdf">https://www.bma.org.uk/-/media/files/pdfs/employment%20advice/ethics/access%20to%20health%20records%2027%20june%202018.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tDxfUIG"/></comment> </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
        <source>Health Information Privacy</source>  
        <access-date>2018-11-04</access-date>
        <comment>Your Rights Under HIPAA 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-individuals/guidance-materials-for-consumers/index.html">https://www.hhs.gov/hipaa/for-individuals/guidance-materials-for-consumers/index.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gElGR1a"/></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>Patel</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Barker</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>Siminerio</surname>
            <given-names>E</given-names>
          </name>
        </person-group>
        <source>Office of the National Coordinator for Health Information Technology</source>  
        <access-date>2018-07-13</access-date>
        <comment>Trends in Consumer Access and Use of Electronic Health Information 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/briefs/oncdatabrief30_accesstrends_.pdf">https://www.healthit.gov/sites/default/files/briefs/oncdatabrief30_accesstrends_.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gFcnBMo"/></comment> </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>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>
        <source>AMIA Annu Symp Proc</source>  
        <year>2017</year>  
        <volume>2017</volume>  
        <fpage>650</fpage>  
        <lpage>9</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29854130"/>
        </comment>  
        <pub-id pub-id-type="medline">29854130</pub-id>
        <pub-id pub-id-type="pmcid">PMC5977675</pub-id></nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
        <source>Health Information Privacy</source>  
        <access-date>2018-11-04</access-date>
        <comment>HIPAA Privacy Rule 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-professionals/privacy/index.html">https://www.hhs.gov/hipaa/for-professionals/privacy/index.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gFk9wju"/></comment> </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Erickson</surname>
            <given-names>BJ</given-names>
          </name>
        </person-group>
        <article-title>Experience with importation of electronic images into the medical record from physical media</article-title>
        <source>J Digit Imaging</source>  
        <year>2011</year>  
        <month>08</month>  
        <volume>24</volume>  
        <issue>4</issue>  
        <fpage>694</fpage>  
        <lpage>9</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21286776"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s10278-011-9364-3</pub-id>
        <pub-id pub-id-type="medline">21286776</pub-id>
        <pub-id pub-id-type="pmcid">PMC3138924</pub-id></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Cunningham</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Ainsworth</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Enabling patient control of personal electronic health records through distributed ledger technology</article-title>
        <source>Stud Health Technol Inform</source>  
        <year>2017</year>  
        <volume>245</volume>  
        <fpage>45</fpage>  
        <lpage>8</lpage>  
        <pub-id pub-id-type="doi">10.3233/978-1-61499-830-3-45</pub-id>
        <pub-id pub-id-type="medline">29295049</pub-id></nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
       <nlm-citation citation-type="journal"> <person-group person-group-type="author"> <name name-style="western"> <surname>Meinert</surname> <given-names>E</given-names> </name> <name name-style="western"> <surname>Alturkistani</surname> <given-names>A</given-names> </name> <name name-style="western"> <surname>Foley</surname> <given-names>Kimberley A</given-names> </name> <name name-style="western"> <surname>Osama</surname> <given-names>Tasnime</given-names> </name> <name name-style="western"> <surname>Car</surname> <given-names>J</given-names> </name> <name name-style="western"> <surname>Majeed</surname> <given-names>A</given-names> </name> <name name-style="western"> <surname>Van Velthoven</surname> <given-names>Michelle</given-names> </name> <name name-style="western"> <surname>Wells</surname> <given-names>G</given-names> </name> <name name-style="western"> <surname>Brindley</surname> <given-names>David</given-names> </name> </person-group> <article-title>Blockchain Implementation in Health Care: Protocol for a Systematic Review</article-title> <source>JMIR Res Protoc</source> <year>2019</year> <month>02</month> <day>08</day> <volume>8</volume> <issue>2</issue> <fpage>e10994</fpage> <comment><ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.researchprotocols.org/2019/2/e10994/"/></comment> <pub-id pub-id-type="doi">10.2196/10994</pub-id> <pub-id pub-id-type="medline">30735146</pub-id> <pub-id pub-id-type="pii">v8i2e10994</pub-id> </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
        <source>National Health Service</source>  
        <access-date>2018-11-04</access-date>
        <comment>Guidance for Access to Health Records Requests 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.igt.hscic.gov.uk/WhatsNewDocuments/Access%20to%20Health%20Records%20Feb%202010.pdf">https://www.igt.hscic.gov.uk/WhatsNewDocuments/Access%20to%20Health%20Records%20Feb%202010.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gGTGgOc"/></comment> </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
        <source>MeSH Browser</source>  
        <access-date>2019-02-02</access-date>
        <comment>Medical Subject Headings 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://meshb.nlm.nih.gov/search">https://meshb.nlm.nih.gov/search</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tEgmIg4"/></comment> </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
        <source>PROSPERO</source>  
        <access-date>2019-02-02</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.crd.york.ac.uk/prospero/">https://www.crd.york.ac.uk/prospero/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="75tEiPdRt"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</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>  
        <month>08</month>  
        <conf-name>2nd International Conference on Open and Big Data (OBD)</conf-name>
        <conf-date>August 22-24, 2016</conf-date>
        <conf-loc>Vienna, Austria</conf-loc>
        <pub-id pub-id-type="doi">10.1109/OBD.2016.11</pub-id></nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ichikawa</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Kashiyama</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Ueno</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Tamper-resistant mobile health using blockchain technology</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2017</year>  
        <month>07</month>  
        <day>26</day>  
        <volume>5</volume>  
        <issue>7</issue>  
        <fpage>e111</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2017/7/e111/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.7938</pub-id>
        <pub-id pub-id-type="medline">28747296</pub-id>
        <pub-id pub-id-type="pii">v5i7e111</pub-id>
        <pub-id pub-id-type="pmcid">PMC5550736</pub-id></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>SH</given-names>
          </name>
          <name name-style="western">
            <surname>Yang</surname>
            <given-names>CS</given-names>
          </name>
        </person-group>
        <article-title>Fingernail analysis management system using microscopy sensor and blockchain technology</article-title>
        <source>Int J Distrib Sens Netw</source>  
        <year>2018</year>  
        <month>03</month>  
        <day>28</day>  
        <volume>14</volume>  
        <issue>3</issue>  
        <fpage>155014771876704</fpage>  
        <pub-id pub-id-type="doi">10.1177/1550147718767044</pub-id></nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
        <source>e-Estonia</source>  
        <access-date>2018-11-04</access-date>
        <comment>eHealth authority partners with Guardtime to accelerate transparency and auditability in health care 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://e-estonia.com/ehealth-authority-partners-with-guardtime-to-accelerate-transparency-and-auditability-in-health-care/">https://e-estonia.com/ehealth-authority-partners-with-guardtime-to-accelerate-transparency-and-auditability-in-health-care/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gGdQOAX"/></comment> </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</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>How Blockchain Could Empower eHealth: An Application for Radiation Oncology</article-title>
        <year>2017</year>  
        <conf-name>Data Management and Analytics for Medicine and Healthcare - Third International Workshop, DMAH 2017</conf-name>
        <conf-date>September 1, 2017</conf-date>
        <conf-loc>Munich, Germany</conf-loc>
        <fpage>0494</fpage>  
        <pub-id pub-id-type="doi">10.1007/978-3-319-67186-4_1</pub-id></nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Omar</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rahman</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Basu</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Kiyomoto</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>MediBchain: A Blockchain Based Privacy Preserving Platform for Healthcare Data</article-title>
        <year>2017</year>  
        <month>12</month>  
        <day>9</day>  
        <conf-name>10th International Conference on Security, Privacy and Anonymity in Computation, Communication and Storage (SpaCCS 2017)</conf-name>
        <conf-date>December 12-15, 2017</conf-date>
        <conf-loc>Guangzhou, China</conf-loc>
        <fpage>534</fpage>  
        <lpage>43</lpage>  
        <pub-id pub-id-type="doi">10.1007/978-3-319-72395-2_49</pub-id></nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Guo</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Shi</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Zhao</surname>
            <given-names>Q</given-names>
          </name>
          <name name-style="western">
            <surname>Zheng</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Secure attribute-based signature scheme with multiple authorities for blockchain in electronic health records systems</article-title>
        <source>IEEE Access</source>  
        <year>2018</year>  
        <volume>6</volume>  
        <fpage>11676</fpage>  
        <lpage>86</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8279429"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1109/ACCESS.2018.2801266</pub-id></nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Liang</surname>
            <given-names>X</given-names>
          </name>
          <name name-style="western">
            <surname>Shetty</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Zhao</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Bowden</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <source>ResearchGate</source>  
        <comment>Towards Decentralized AccountabilitySelf-sovereignty in Healthcare Systems 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/321137917_Towards_Decentralized_Accountability_and_Self-Sovereignty_in_Healthcare_Systems">https://www.researchgate.net/publication/321137917_Towards_Decentralized_Accountability_and_Self-Sovereignty_in_Healthcare_Systems</ext-link></comment> </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>Liang</surname>
            <given-names>X</given-names>
          </name>
          <name name-style="western">
            <surname>Zhao</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Shetty</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Integrating Blockchain for Data Sharing and Collaboration in Mobile Healthcare Applications</article-title>
        <year>2017</year>  
        <month>10</month>  
        <day>8</day>  
        <conf-name>2017 IEEE 28th Annual International Symposium on Personal, Indoor, and Mobile Radio Communications (PIMRC)</conf-name>
        <conf-date>October 8-13, 2017</conf-date>
        <conf-loc>Bologna, Italy</conf-loc>
        <fpage>1</fpage>  
        <lpage>5</lpage>  
        <pub-id pub-id-type="doi">10.1109/PIMRC.2017.8292361</pub-id></nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Mannaro</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Baralla</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Pinna</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Ibba</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>A blockchain approach applied to a teledermatology platform in the Sardinian region (Italy)</article-title>
        <source>Information</source>  
        <year>2018</year>  
        <month>02</month>  
        <day>23</day>  
        <volume>9</volume>  
        <issue>2</issue>  
        <fpage>44</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/323374145_A_Blockchain_Approach_Applied_to_a_Teledermatology_Platform_in_the_Sardinian_Region_Italy"/>
        </comment>  
        <pub-id pub-id-type="doi">10.3390/info9020044</pub-id></nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nichol</surname>
            <given-names>PB</given-names>
          </name>
        </person-group>
        <source>CIO</source>  
        <year>2017</year>  
        <access-date>2018-07-13</access-date>
        <comment>Top 3 practical innovations from Yale healthcare hackathon 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cio.com/article/3161886/innovation/top-3-practical-innovations-from-yale-healthcare-hackathon.html">https://www.cio.com/article/3161886/innovation/top-3-practical-innovations-from-yale-healthcare-hackathon.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73gGohT1l"/></comment> </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Raju</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Rajesh</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Deogun</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>The Case for a Data Bank: an Institution to Govern Healthcare and Education</article-title>
        <source>Proceedings of the 10th International Conference on Theory and Practice of Electronic Governance</source>  
        <year>2017</year>  
        <month>03</month>  
        <day>7</day>  
        <conf-name>ICEGOV'17</conf-name>
        <conf-date>March 7-9, 2017</conf-date>
        <conf-loc>New Delhi, India</conf-loc>
        <fpage>538</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1145/3047273.3047275</pub-id></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>Siddiqi</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>All</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Sivaraman</surname>
            <given-names>V</given-names>
          </name>
        </person-group>
        <article-title>Secure Lightweight Context-driven Data Logging for Bodyworn Sensing Devices</article-title>
        <year>2017</year>  
        <month>04</month>  
        <day>26</day>  
        <conf-name>5th International Symposium on Digital Forensic and Security (ISDFS 2017)</conf-name>
        <conf-date>April 26-28, 2017</conf-date>
        <conf-loc>Tirgu Mures, Romania</conf-loc>
        <pub-id pub-id-type="doi">10.1109/ISDFS.2017.7916500</pub-id></nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Xue</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Huang</surname>
            <given-names>X</given-names>
          </name>
        </person-group>
        <article-title>A secure system for pervasive social network-based healthcare</article-title>
        <source>IEEE Access</source>  
        <year>2016</year>  
        <volume>4</volume>  
        <fpage>9239</fpage>  
        <lpage>50</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/311972951_A_Secure_System_For_Pervasive_Social_Network-based_Healthcare"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1109/ACCESS.2016.2645904</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>Zhao</surname>
            <given-names>Z</given-names>
          </name>
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Peng</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Xu</surname>
            <given-names>Ruzhi</given-names>
          </name>
        </person-group>
        <article-title>Lightweight backup and efficient recovery scheme for health blockchain keys</article-title>
        <year>2017</year>  
        <month>03</month>  
        <day>22</day>  
        <conf-name>IEEE 13th International Symposium on Autonomous Decentralized Systems</conf-name>
        <conf-date>March 22-24, 2017</conf-date>
        <conf-loc>Bangkok, Thailand</conf-loc>
        <pub-id pub-id-type="doi">10.1109/ISADS.2017.22</pub-id></nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Linn</surname>
            <given-names>LA</given-names>
          </name>
          <name name-style="western">
            <surname>Koo</surname>
            <given-names>MB</given-names>
          </name>
        </person-group>
        <source>Office of the National Coordinator for Health Information Technology</source>  
        <access-date>2018-11-05</access-date>
        <comment>Blockchain For Health Data and Its Potential Use in Health IT and Health Care Related Research 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/11-74-ablockchainforhealthcare.pdf">https://www.healthit.gov/sites/default/files/11-74-ablockchainforhealthcare.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hP7Ddos"/></comment> </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Yue</surname>
            <given-names>X</given-names>
          </name>
          <name name-style="western">
            <surname>Wang</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Jin</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Jiang</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <article-title>Healthcare data gateways: found healthcare intelligence on blockchain with novel privacy risk control</article-title>
        <source>J Med Syst</source>  
        <year>2016</year>  
        <month>10</month>  
        <volume>40</volume>  
        <issue>10</issue>  
        <fpage>218</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://paperpile.com/b/RUDrOC/D5Tsi"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s10916-016-0574-6</pub-id>
        <pub-id pub-id-type="medline">27565509</pub-id>
        <pub-id pub-id-type="pii">10.1007/s10916-016-0574-6</pub-id></nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>Medical record system using blockchain, big data tokenization</article-title>
        <year>2016</year>  
        <month>11</month>  
        <day>25</day>  
        <conf-name>International Conference on Information and Communications Security (ICICS 2016)</conf-name>
        <conf-date>November 29–December 2, 2016</conf-date>
        <conf-loc>Singapore</conf-loc>
        <fpage>254</fpage>  
        <lpage>61</lpage>  
        <pub-id pub-id-type="doi">10.1007/978-3-319-50011-9_20</pub-id></nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Esposito</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>de Santis</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Tortora</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Chang</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Choo</surname>
            <given-names>KR</given-names>
          </name>
        </person-group>
        <article-title>Blockchain: a panacea for healthcare cloud-based data security and privacy?</article-title>
        <source>IEEE Cloud Comput</source>  
        <year>2018</year>  
        <month>01</month>  
        <volume>5</volume>  
        <issue>1</issue>  
        <fpage>31</fpage>  
        <lpage>7</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://pdfs.semanticscholar.org/7f8f/4ff1377ebf0a084c44dbf6926af03dd2cdd8.pdf"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1109/MCC.2018.011791712</pub-id></nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Mertz</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>(Block) chain reaction: a blockchain revolution sweeps into health care, offering the possibility for a much-needed data solution</article-title>
        <source>IEEE Pulse</source>  
        <year>2018</year>  
        <volume>9</volume>  
        <issue>3</issue>  
        <fpage>4</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1109/MPUL.2018.2814879</pub-id>
        <pub-id pub-id-type="medline">29757744</pub-id></nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Mertz</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Hospital CIO explains blockchain potential: an interview with Beth Israel Deaconess Medical Center's John Halamka</article-title>
        <source>IEEE Pulse</source>  
        <year>2018</year>  
        <month>5</month>  
        <volume>9</volume>  
        <issue>3</issue>  
        <fpage>8</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1109/MPUL.2018.2814878</pub-id>
        <pub-id pub-id-type="medline">29757745</pub-id></nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Pauwels</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Grevatt</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <source>Wilson Center</source>  
        <year>2017</year>  
        <access-date>2018-11-05</access-date>
        <comment>The Social Benefits of Blockchain for Health Data: Securing Patient Privacy &amp; Control 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.wilsoncenter.org/sites/default/files/blockchain_for_health_data_securing_patient_privacy_control.pdf">https://www.wilsoncenter.org/sites/default/files/blockchain_for_health_data_securing_patient_privacy_control.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hPNSZel"/></comment> </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Weiss</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Botha</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Herselman</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Loots</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Blockchain as an enabler for public mHealth solutions in South Africa</article-title>
        <year>2017</year>  
        <month>05</month>  
        <day>30</day>  
        <conf-name>IST-Africa Week Conference (IST-Africa)</conf-name>
        <conf-date>2017</conf-date>
        <conf-loc>Windhoek, Namibia</conf-loc>
        <publisher-name>30 May-2 June, 2017</publisher-name>
        <pub-id pub-id-type="doi">10.23919/ISTAFRICA.2017.8102404</pub-id></nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wong</surname>
            <given-names>MC</given-names>
          </name>
          <name name-style="western">
            <surname>Yee</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Nøhr</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Socio-technical considerations for the use of blockchain technology in healthcare</article-title>
        <source>Stud Health Technol Inform</source>  
        <year>2018</year>  
        <volume>247</volume>  
        <fpage>636</fpage>  
        <lpage>40</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://eprints.utas.edu.au/27633/2/126306.pdf"/>
        </comment>  
        <pub-id pub-id-type="medline">29678038</pub-id></nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="web">
        <source>Office of the National Coordinator for Health Information Technology</source>  
        <access-date>2018-11-05</access-date>
        <comment>Connecting Health and Care for the Nation: A Shared Nationwide Interoperability Roadmap 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/hie-interoperability/nationwide-interoperability-roadmap-final-version-1.0.pdf">https://www.healthit.gov/sites/default/files/hie-interoperability/nationwide-interoperability-roadmap-final-version-1.0.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hPb3aIE"/></comment> </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="web">
        <source>Office of the National Coordinator for Health Information Technology</source>  
        <access-date>2018-09-18</access-date>
        <comment>Index for Excerpts from the American Recovery and Reinvestment Act of 2009 (ARRA) 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/hitech_act_excerpt_from_arra_with_index.pdf">https://www.healthit.gov/sites/default/files/hitech_act_excerpt_from_arra_with_index.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hPkxfxS"/></comment> </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Scambler</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <source>Sociology as Applied to Medicine Sixth Edition</source>  
        <year>2008</year>  
        <publisher-loc>London, UK</publisher-loc>
        <publisher-name>Saunders Ltd</publisher-name></nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="web">
        <source>Office of the National Coordinator for Health Information Technology</source>  
        <access-date>2018-11-05</access-date>
        <comment>Announcing the Blockchain Challenge 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/topic/grants-contracts/announcing-blockchain-challenge">https://www.healthit.gov/topic/grants-contracts/announcing-blockchain-challenge</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hPshgqZ"/></comment> </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>Slabodkin</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Blockchain remains a work in progress for use in healthcare</article-title>
        <source>Health Data Manage</source>  
        <year>2017</year>  
        <volume>25</volume>  
        <issue>3</issue>  
        <fpage>37</fpage>  
        <lpage>9</lpage>  
        <comment>https://www.healthdatamanagement.com/news/blockchain-remains-a-work-in-progress-for-use-in-healthcare</comment> </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="web">
        <source>ID2020 Alliance</source>  
        <access-date>2018-11-05</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://id2020.org/">https://id2020.org/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="73hPwddbe"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="web">
        <source>Journal of Ahima</source>  
        <access-date>2019-02-02</access-date>
        <comment>New Administration Gets to Know 'Blockchain' 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.ahimajournal-digital.com/ahimajournal/april_2017?pg=11#pg11">http://www.ahimajournal-digital.com/ahimajournal/april_2017?pg=11#pg11</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tGNXr5x"/></comment> </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kitson</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Marshall</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Bassett</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Zeitz</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>What are the core elements of patient-centred care? A narrative review and synthesis of the literature from health policy, medicine and nursing</article-title>
        <source>J Adv Nurs</source>  
        <year>2013</year>  
        <month>01</month>  
        <volume>69</volume>  
        <issue>1</issue>  
        <fpage>4</fpage>  
        <lpage>15</lpage>  
        <pub-id pub-id-type="doi">10.1111/j.1365-2648.2012.06064.x</pub-id>
        <pub-id pub-id-type="medline">22709336</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>Stewart</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Towards a global definition of patient centred care</article-title>
        <source>Br Med J</source>  
        <year>2001</year>  
        <month>02</month>  
        <day>24</day>  
        <volume>322</volume>  
        <issue>7284</issue>  
        <fpage>444</fpage>  
        <lpage>5</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/11222407"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1136/bmj.322.7284.444</pub-id>
        <pub-id pub-id-type="medline">11222407</pub-id>
        <pub-id pub-id-type="pmcid">PMC1119673</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>Potts</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>The big cure</article-title>
        <source>IPA Review</source>  
        <year>2016</year>  
        <volume>68</volume>  
        <issue>4</issue>  
        <fpage>-</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://search.informit.com.au/browsePublication;py=2016;vol=68;res=IELHSS;issn=1329-8100;iss=4"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Prajna</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <source>CommsMEA</source>  
        <year>2017</year>  
        <access-date>2018-11-05</access-date>
        <comment>Unleashing the power of the ledger 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.commsmea.com/16927-unleashing-the-power-of-the-ledger">https://www.commsmea.com/16927-unleashing-the-power-of-the-ledger</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hQDGaxT"/></comment> </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="web">
        <source>Health Information Privacy</source>  
        <access-date>2018-11-05</access-date>
        <comment>HIPAA Security Rule 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html">https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hQPLMHD"/></comment> </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Patil</surname>
            <given-names>HK</given-names>
          </name>
          <name name-style="western">
            <surname>Seshadri</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Big Data Security and Privacy Issues in Healthcare</article-title>
        <year>2014</year>  
        <month>10</month>  
        <day>27</day>  
        <conf-name>IEEE International Congress on Big Data</conf-name>
        <conf-date>June 27-July 2, 2014</conf-date>
        <conf-loc>Washington, DC</conf-loc>
        <pub-id pub-id-type="doi">10.1109/BigData.Congress.2014.112</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>Padmanabhan</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <source>CIO</source>  
        <access-date>2018-07-13</access-date>
        <comment>How AI and blockchain are driving precision medicine in 2017 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cio.com/article/3157477/healthcare/how-ai-and-blockchain-are-driving-precision-medicine-in-2017.html">https://www.cio.com/article/3157477/healthcare/how-ai-and-blockchain-are-driving-precision-medicine-in-2017.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hQZnu0o"/></comment> </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="web">
        <source>Fox News</source>  
        <access-date>2018-11-05</access-date>
        <comment>'Ransomware' cyberattack cripples hospitals across England 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.foxnews.com/health/ransomware-cyberattack-cripples-hospitals-across-england">https://www.foxnews.com/health/ransomware-cyberattack-cripples-hospitals-across-england</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hQg0X4g"/></comment> </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="web">
        <source>Recode</source>  
        <access-date>2018-09-18</access-date>
        <comment>US hospitals have been hit by the global ransomware attack 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.recode.net/2017/6/27/15881666/global-eu-cyber-attack-ushackers-nsa-hospitals">https://www.recode.net/2017/6/27/15881666/global-eu-cyber-attack-ushackers-nsa-hospitals</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hQjc8JH"/></comment> </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Conn</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Modern Healthcare</source>  
        <access-date>2018-11-05</access-date>
        <comment>Could blockchain help cure health IT's security woes? 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.modernhealthcare.com/article/20161105/MAGAZINE/311059966">https://www.modernhealthcare.com/article/20161105/MAGAZINE/311059966</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hQu0K6H"/></comment> </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wood</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <source>Gavin Wood</source>  
        <access-date>2019-02-02</access-date>
        <comment>Ethereum: A secure decentralized transaction ledger 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://gavwood.com/paper.pdf">http://gavwood.com/paper.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="75tGmqUkv"/></comment> </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Moss</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Davies</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Healthcare Dive</source>  
        <year>2017</year>  
        <month>09</month>  
        <day>1</day>  
        <comment>Blockchain shows promise in healthcare 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthcaredive.com/news/blockchain-shows-promise-in-improving-interoperability-idc-report-says/528105/">https://www.healthcaredive.com/news/blockchain-shows-promise-in-improving-interoperability-idc-report-says/528105/</ext-link></comment> </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Padmanabhan</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <source>CIO</source>  
        <year>2017</year>  
        <access-date>2018-11-05</access-date>
        <comment>Technology-led innovation in digital health: the law of inverse relationships 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cio.com/article/3211596/innovation/technology-led-innovation-in-digital-health-the-law-of-inverse-relationships.html">https://www.cio.com/article/3211596/innovation/technology-led-innovation-in-digital-health-the-law-of-inverse-relationships.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hRC9v8Y"/></comment> </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Damiani</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Forbes</source>  
        <year>2017</year>  
        <access-date>2018-07-13</access-date>
        <comment>SimplyVital Health Is Using Blockchain To Revolutionize Healthcare 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.forbes.com/sites/jessedamiani/2017/11/06/simplyvital-health-blockchain-revolutionize-healthcare">https://www.forbes.com/sites/jessedamiani/2017/11/06/simplyvital-health-blockchain-revolutionize-healthcare</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="73hPChtda"/></comment> </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
