<?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">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</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">v9i6e20713</article-id>
      <article-id pub-id-type="pmid">34100768</article-id>
      <article-id pub-id-type="doi">10.2196/20713</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Blockchain Applications in Health Care and Public Health: Increased Transparency</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Raghavendra</surname>
            <given-names>Meda</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hasselgren</surname>
            <given-names>Anton</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Velmovitsky</surname>
            <given-names>Pedro Elkind</given-names>
          </name>
          <degrees>BSc, MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7539-3193</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Bublitz</surname>
            <given-names>Frederico Moreira</given-names>
          </name>
          <degrees>BSc, MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1711-5392</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Fadrique</surname>
            <given-names>Laura Xavier</given-names>
          </name>
          <degrees>MSc, PMP</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8317-6201</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Morita</surname>
            <given-names>Plinio Pelegrini</given-names>
          </name>
          <degrees>PEng, MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>School of Public Health and Health Systems</institution>
            <institution>University of Waterloo</institution>
            <addr-line>200 University Ave W</addr-line>
            <addr-line>Waterloo, ON, N2L 3G1</addr-line>
            <country>Canada</country>
            <phone>1 15198884567 ext 41372</phone>
            <email>plinio.morita@uwaterloo.ca</email>
          </address>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <xref rid="aff5" ref-type="aff">5</xref>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9515-6478</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>School of Public Health and Health Systems</institution>
        <institution>University of Waterloo</institution>
        <addr-line>Waterloo, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Center for Strategic Technologies in Health (NUTES)</institution>
        <institution>State University of Paraiba (UEPB)</institution>
        <addr-line>Campina Grande</addr-line>
        <country>Brazil</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Institute of Health Policy, Management, and Evaluation</institution>
        <institution>University of Toronto</institution>
        <addr-line>Toronto, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Research Institute for Aging</institution>
        <institution>University of Waterloo</institution>
        <addr-line>Waterloo, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Department of Systems Design Engineering</institution>
        <institution>University of Waterloo</institution>
        <addr-line>Waterloo, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>eHealth Innovation</institution>
        <institution>Techna Institute</institution>
        <institution>University Health Network</institution>
        <addr-line>Toronto, ON</addr-line>
        <country>Canada</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Plinio Pelegrini Morita <email>plinio.morita@uwaterloo.ca</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>6</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>8</day>
        <month>6</month>
        <year>2021</year>
      </pub-date>
      <volume>9</volume>
      <issue>6</issue>
      <elocation-id>e20713</elocation-id>
      <history>
        <date date-type="received">
          <day>26</day>
          <month>5</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>6</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>7</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>24</day>
          <month>4</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Pedro Elkind Velmovitsky, Frederico Moreira Bublitz, Laura Xavier Fadrique, Plinio Pelegrini Morita. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 08.06.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2021/6/e20713" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Although big data and smart technologies allow for the development of precision medicine and predictive models in health care, there are still several challenges that need to be addressed before the full potential of these data can be realized (eg, data sharing and interoperability issues, lack of massive genomic data sets, data ownership, and security and privacy of health data). Health companies are exploring the use of blockchain, a tamperproof and distributed digital ledger, to address some of these challenges.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>In this viewpoint, we aim to obtain an overview of blockchain solutions that aim to solve challenges in health care from an industry perspective, focusing on solutions developed by health and technology companies.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted a literature review following the protocol defined by Levac et al to analyze the findings in a systematic manner. In addition to traditional databases such as IEEE and PubMed, we included search and news outlets such as CoinDesk, CoinTelegraph, and Medium.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Health care companies are using blockchain to improve challenges in five key areas. For electronic health records, blockchain can help to mitigate interoperability and data sharing in the industry by creating an overarching mechanism to link disparate personal records and can stimulate data sharing by connecting owners and buyers directly. For the drug (and food) supply chain, blockchain can provide an auditable log of a product’s provenance and transportation (including information on the conditions in which the product was transported), increasing transparency and eliminating counterfeit products in the supply chain. For health insurance, blockchain can facilitate the claims management process and help users to calculate medical and pharmaceutical benefits. For genomics, by connecting data buyers and owners directly, blockchain can offer a secure and auditable way of sharing genomic data, increasing their availability. For consent management, as all participants in a blockchain network view an immutable version of the truth, blockchain can provide an immutable and timestamped log of consent, increasing transparency in the consent management process.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Blockchain technology can improve several challenges faced by the health care industry. However, companies must evaluate how the features of blockchain can affect their systems (eg, the append-only nature of blockchain limits the deletion of data stored in the network, and distributed systems, although more secure, are less efficient). Although these trade-offs need to be considered when viewing blockchain solutions, the technology has the potential to optimize processes, minimize inefficiencies, and increase trust in all contexts covered in this viewpoint.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health care</kwd>
        <kwd>blockchain</kwd>
        <kwd>EHR</kwd>
        <kwd>health insurance</kwd>
        <kwd>drug supply chain</kwd>
        <kwd>genomics</kwd>
        <kwd>consent</kwd>
        <kwd>digital ledger</kwd>
        <kwd>food supply chain</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Global society is moving into an age of ubiquitous and smart technologies that monitor our health, such as smart devices, Internet of Things solutions, and ambient assisted living systems. These technologies allow continuous and effortless health data collection at a previously unseen scale [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>], generating rich and massive data sets, known as big data [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
        <p>The <italic>age of big data</italic> can lead to a change in the way health care is delivered. Generally, health care is reactive, in which individuals interact with health care services when there is something wrong [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>] and usually to treat acute diseases, instead of proactive, in which real-time monitoring of health data from different sources leads to predictions and insights into individual and population health, as opposed to checkups with health services when a problem appears [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. In this manner, a proactive and predictive health care model includes surveillance and monitoring of individuals through remote sensing technologies, such as smart bands and smart thermostats, generating large volumes of diverse and real-time data in a cost-effective manner. The use of such technologies in a community will also enable public health surveillance on a scale never seen before, allowing public health agencies to better understand the socioeconomic determinants of health and prevent disease outbreaks [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>].</p>
        <p>However, to achieve this model of health care, there are challenges that need to be overcome. For example, health records are stored by different providers in systems that lack interoperability [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. This makes data sharing difficult and prevents doctors from having a complete view of a patient’s health [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Interoperability issues and costs also affect the availability of genomic data and minimize their benefits [<xref ref-type="bibr" rid="ref9">9</xref>]. In addition, increasingly advanced methods of data collection and analysis of personal, medical, and genomic data raise concerns regarding ownership, privacy, and regulations of health data [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>].</p>
        <p>One possible tool to overcome or mitigate these challenges is blockchain [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref13">13</xref>]. This technology can be seen as a distributed virtual ledger that records timestamped transactions [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. Cryptography is used to ensure that when a block is added to the blockchain, it cannot be tampered with [<xref ref-type="bibr" rid="ref12">12</xref>]. Hence, blockchain is a tamperproof digital ledger in which all participants view an immutable version of the truth, making it ideal to track an asset and enable trust among parties (eg, health data or user consent for data collection) [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref14">14</xref>].</p>
        <p>In 2016 and 2018, IBM Corporation surveyed more than 400 health care and life sciences executives on the use of blockchain technology. Among their findings, more than half of the executives in both industries had plans to adopt it by 2020 [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Given the perceived potential of blockchain by industry experts from multiple areas [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>] and to help guide the implementation of digital solutions that can solve pressing needs in health care systems, the aim of this study is to review current blockchain solutions being developed by the health care industry. This paper provides a comprehensive view of the blockchain health care industry, providing guidance to innovators about how to leverage this technology in daily operations and how to implement solutions that can help evolve health care delivery. The COVID-19 outbreak has created an increased demand for home-based digital health solutions such as telehealth and telemonitoring [<xref ref-type="bibr" rid="ref15">15</xref>], increasing the importance of using technologies such as blockchain to increase the transparency of digital transactions and data provenance [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>].</p>
      </sec>
      <sec>
        <title>Related Work</title>
        <p>McGhin et al [<xref ref-type="bibr" rid="ref18">18</xref>] provide an overview of the main opportunities and challenges for blockchain in the health care field and describe some initiatives (both in academia and industry) focused on developing blockchain solutions. Vazirani et al [<xref ref-type="bibr" rid="ref19">19</xref>] detailed a systematic review examining the feasibility of blockchain for electronic health record (EHR) systems, finding several trade-offs that need to be considered during the design and development of blockchain. Trade-offs were further explored by O’Donoghue et al [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
        <p>Farouk et al [<xref ref-type="bibr" rid="ref13">13</xref>] provided a similar review to this one on the use of blockchain in the health care industry but mostly focused on its integration with Internet of Things devices and record management. Hasselgren et al [<xref ref-type="bibr" rid="ref21">21</xref>] conducted a scoping review of blockchain in health care and, while focusing on peer-reviewed publications rather than the industry, they found that both the number and quality of blockchain research is growing.</p>
        <p>Chukwu and Garg [<xref ref-type="bibr" rid="ref22">22</xref>] provide a systematic review of blockchain applications specifically for the use of EHRs and health data sharing and do not focus on industry applications.</p>
        <p>Agbo et al [<xref ref-type="bibr" rid="ref23">23</xref>] conducted a systematic review of blockchain applications in health care, also focusing on academic literature, although some studies mention companies working with blockchain. The use cases found in this work are very similar to the use cases explored in this paper (suggesting a convergence between academia and industry research), but Agbo et al [<xref ref-type="bibr" rid="ref23">23</xref>] found a predominance of studies focusing on EHRs when compared with other areas.</p>
        <p>Most of these did not have an industry focus; rather, they usually discussed the computer science aspects of the technology or evaluated mostly academic work. In addition, as found by Agbo et al [<xref ref-type="bibr" rid="ref23">23</xref>], most reviews focused on EHRs and not on additional use cases. Therefore, this review contributes to preview work by providing an overview of blockchain applications in the health care industry, while identifying what challenges and use cases are the current focus of health care companies working with blockchain.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>This narrative review [<xref ref-type="bibr" rid="ref24">24</xref>] focuses on providing eHealth experts with a comprehensive narrative review of blockchain in health care. Blockchain is a novel technology that can provide increased transparency to data transactions in health care and public health [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Owing to its novelty and early stage implementation, significant development has been accomplished at the industry level, driving this review toward a combination of peer-reviewed academic literature and gray literature.</p>
        <p>Our aim was to analyze blockchain in health care from an <italic>industry</italic> perspective, focusing on solutions developed by health and technology companies (although results from research and development initiatives and academia were used to complement knowledge when necessary).</p>
        <p>Although not a scoping review, this paper followed the framework defined by Levac et al [<xref ref-type="bibr" rid="ref25">25</xref>] for scoping reviews, ensuring that the findings were analyzed in a systematic manner. This framework consists of six stages: (1) identifying the research question (RQ); (2) identifying relevant studies; (3) selecting studies; (4) charting the data; (5) collating, summarizing, and reporting results; and (6) consultation (optional). In this narrative review, we leveraged phases 1-5.</p>
      </sec>
      <sec>
        <title>Identifying the RQ</title>
        <p>The primary objective is to identify how the health care industry views the potential of blockchain to solve current challenges. To fulfill this, two secondary goals need to be achieved: we must understand how blockchain works and the challenges facing the industry. Therefore, the following RQs were used to guide the reviews:</p>
        <list list-type="order">
          <list-item>
            <p>How do the blockchain systems work?</p>
          </list-item>
          <list-item>
            <p>What are the current challenges faced by the health care industry today that can be addressed by blockchain technology?</p>
          </list-item>
          <list-item>
            <p>For each of these challenges, which blockchain solutions are being developed by the health care industry?</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Identifying Relevant Studies</title>
        <p>Our review analyzes how the health care industry perceives the blockchain’s potential to solve current challenges. To this end, we looked at gray literature in addition to traditional databases such as IEEE and PubMed, including search and news outlets such as Google Scholar, CoinDesk [<xref ref-type="bibr" rid="ref26">26</xref>], CoinTelegraph [<xref ref-type="bibr" rid="ref27">27</xref>], and Medium [<xref ref-type="bibr" rid="ref28">28</xref>]. The keywords were a combination of “blockchain,” “distributed ledger,” “health,” “industry,” and “health care.” Whenever possible, we looked at technical reports (usually available on companies’ websites) in addition to news articles.</p>
      </sec>
      <sec>
        <title>Study Selection</title>
        <p>The primary exclusion criteria involved selecting solutions that address issues or challenges in health care. Blockchain solutions that only had applications in unrelated fields were not included. Additional restrictions included practical concerns regarding availability and language (only English references were included).</p>
      </sec>
      <sec>
        <title>Charting the Data</title>
        <p>To extract useful insights from the publications, we focused on two main types of information:</p>
        <list list-type="bullet">
          <list-item>
            <p>What are the main health care challenges that the solution aims to improve?</p>
          </list-item>
          <list-item>
            <p>How is blockchain being used to improve the challenges?</p>
          </list-item>
        </list>
        <p>More specifically, we looked at the main objective of the blockchain solution and the methods in which blockchain is being developed. Relevant bibliographical information, including title, authors, country, and year, was also extracted. This review focused on technical reports. If the technical report did not provide sufficient information, web articles were used to complement the results.</p>
      </sec>
      <sec>
        <title>Collating, Summarizing, and Reporting the Results</title>
        <p>Following the recommendations presented by Levac et al [<xref ref-type="bibr" rid="ref25">25</xref>], the steps are as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>Analysis: for each solution being presented, we mapped the challenges addressed and how blockchain is being used.</p>
          </list-item>
          <list-item>
            <p>Reporting results: after presenting additional information on blockchain, we will describe the challenge in question and its importance in health care, followed by a discussion on how blockchain is being used by the industry in this context.</p>
          </list-item>
          <list-item>
            <p>Implications for future research, practice, and policy: this final step will be addressed in the</p>
            <p>Discussion</p>
            <p>section, where we discuss the limitations of blockchain and additional concerns.</p>
          </list-item>
        </list>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>We started this review by presenting relevant background information about blockchain, followed by an overview of the main challenges identified in our review: EHRs, supply chain, health insurance, genomics, and consent management. For each of these areas, we have also presented blockchain solutions developed by industry. <xref ref-type="table" rid="table1">Table 1</xref> provides a summary of the results by describing each of the five identified challenges explaining how blockchain can offer a solution, along with examples.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Results of the literature review.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="140"/>
            <col width="370"/>
            <col width="490"/>
            <thead>
              <tr valign="top">
                <td>Challenges</td>
                <td>Description</td>
                <td>Solutions</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Electronic health records</td>
                <td>Blockchain can provide an overarching framework that allows transparent and auditable access to disparate individuals’ health records stored off-chain. Patients would control data sharing parameters and access. Some solutions also discuss integrating health data from less traditional sources (eg, connected devices) and the creation of a health data marketplace, in which patients can sell their data to buyers through crypto tokens</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>MedRec [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref29">29</xref>], PatientTruth [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>], CareX [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>], MEDIS [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>], GEM [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref40">40</xref>], MedicalChain [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], Humantiv and Medoplex [<xref ref-type="bibr" rid="ref43">43</xref>-<xref ref-type="bibr" rid="ref45">45</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Supply chain</td>
                <td>Blockchain can establish an immutable record of a product’s tracing throughout the supply chain. In the case of health care, there have been many solutions that implement a blockchain to track-and-trace drugs and food products. In addition, smart contracts can be used as monitoring and alert systems for proper transport conditions (eg, a certain temperature range)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Drug supply chain: BlockVerify [<xref ref-type="bibr" rid="ref46">46</xref>-<xref ref-type="bibr" rid="ref48">48</xref>], Merck [<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>], Modum [<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref54">54</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>Food supply chain: IBM Food Trust [<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref58">58</xref>], Alibaba and Ant Financial [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Health insurance</td>
                <td>Smart contracts on the blockchain can potentially help to settle health insurance claims and manage payment in real time, making the process more efficient and transparent for payers, providers, and patients. Other potential use cases include pharmaceutical and medical benefits, checks, and payment risk calculation</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>PokitDok and DokChain [<xref ref-type="bibr" rid="ref61">61</xref>-<xref ref-type="bibr" rid="ref67">67</xref>], GEM [<xref ref-type="bibr" rid="ref39">39</xref>], Payspan [<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Genomics</td>
                <td>Much like with electronic health records, blockchain can provide a mechanism for controlling access to separate existing data banks of genetic information. In addition, blockchain can directly connect sellers of genomic data-to-data buyers, creating a genomic data marketplace. Data buyers could even provide rewards for individuals to sequence their genomes, creating their own data sets (eg, providing crypto tokens to individuals with a certain feature to be researched, in return for their genomic information)</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Nebula Genomics [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref70">70</xref>], LunaDNA [<xref ref-type="bibr" rid="ref71">71</xref>-<xref ref-type="bibr" rid="ref75">75</xref>], Shivom [<xref ref-type="bibr" rid="ref76">76</xref>-<xref ref-type="bibr" rid="ref79">79</xref>], Zenome [<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref81">81</xref>], EncrypGen [<xref ref-type="bibr" rid="ref82">82</xref>-<xref ref-type="bibr" rid="ref85">85</xref>], Macrogen [<xref ref-type="bibr" rid="ref86">86</xref>-<xref ref-type="bibr" rid="ref88">88</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Consent management</td>
                <td>Blockchain can provide an immutable and timestamped log of consent, allowing individuals to grant and revoke consent for different data types and periods. In the case of health studies, it can also help researchers to easily track, manage, and update user consent</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>My31 app [<xref ref-type="bibr" rid="ref89">89</xref>,<xref ref-type="bibr" rid="ref90">90</xref>], Bitfury [<xref ref-type="bibr" rid="ref91">91</xref>,<xref ref-type="bibr" rid="ref92">92</xref>], HealthVerity Consent [<xref ref-type="bibr" rid="ref93">93</xref>], Verifiable Audit Trail (tracking of events related to health data) [<xref ref-type="bibr" rid="ref94">94</xref>-<xref ref-type="bibr" rid="ref98">98</xref>], INSERM<sup>a</sup> and APHP<sup>b</sup> consent project [<xref ref-type="bibr" rid="ref14">14</xref>], Queen’s University BlockTrial [<xref ref-type="bibr" rid="ref99">99</xref>], Patient Control and Consent Blockchain initiative [<xref ref-type="bibr" rid="ref100">100</xref>-<xref ref-type="bibr" rid="ref102">102</xref>], Ubiquitous Health Technology Lab [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref103">103</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>INSERM: Institut National de la Santé Et de la Recherche Médicale.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>APHP: Assistance Publique-Hôpitaux de Paris.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>What Is Blockchain?</title>
        <p>Blockchain is a virtual distributed ledger that records transactions among parties. It is operated by a network of computers in which each participant is called a node and possesses a copy of the ledger, regularly updated to ensure consistency. In other words, all nodes have access to the exact information [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>When a user makes a transaction, this transaction is timestamped and <italic>sealed</italic> in a block [<xref ref-type="bibr" rid="ref12">12</xref>]. Through a consensus mechanism, this block is linked to previous existing blocks—hence the name blockchain. Different blockchains (eg, Bitcoin and Ethereum) have different consensus mechanisms [<xref ref-type="bibr" rid="ref12">12</xref>]. A typical consensus mechanism, called Proof of Work, requires the nodes in the network to randomly guess a number that solves a mathematical puzzle; the first node to discover it seals the block. This process is called mining [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>The linkage between blocks is achieved through a method called hashing, in which new blocks point to the previous ones [<xref ref-type="bibr" rid="ref12">12</xref>]. This technique converts data into a string of characters, called a hash. For example, a user may convert a text into the following hash: “f1abc234b79f6d6ay42a12c53468a1b13553r1r0fgr4039 rf08h958b5232b9n8.” If a single character from this hash is changed, an entirely new string is generated. Although it is easy to generate a hash from a piece of information, it is impossible to discover the original information from a hash [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. The Bitcoin blockchain hashes the nonce, alongside the transaction information and the hash of the preceding block. If a malicious party tries to tamper with information already stored in a block, the hash is altered, breaking the chain. This ensures that the blocks cannot be tampered with, and the information contained in the blockchain cannot be altered. Therefore, blockchain is a tamperproof digital ledger where all participants have access to an immutable version of the truth [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. The flow of a transaction in the blockchain is shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Flow of a transaction in the blockchain.</p>
          </caption>
          <graphic xlink:href="medinform_v9i6e20713_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Blockchain is a type of distributed ledger technology, in which a consistent ledger is shared among parties to store a record, creating a distributed database. It is a distributed ledger technology that uses cryptographic and consensus mechanisms to increase trust [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
        <p>There are also different types of blockchains. Although the nomenclature varies, they are usually defined as follows [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref104">104</xref>,<xref ref-type="bibr" rid="ref105">105</xref>]:</p>
        <list list-type="bullet">
          <list-item>
            <p>Public blockchain: all participants can read and write new information to the ledger. Although new information can be added, no information can be deleted. Bitcoin is an example of a public blockchain.</p>
          </list-item>
          <list-item>
            <p>Permission (consortium and federated) blockchain: this is owned by a consortium of participants who define the permissions for joining and updating the network. For example, a consortium blockchain owned by health care providers can allow patients to change their information, but only providers may upload new information.</p>
          </list-item>
          <list-item>
            <p>Private blockchain: this is owned by a single entity that manages access, permission to read or write data, and even data deletion. Among the blockchain communities, some are of the opinion that private blockchains defeat the purpose of decentralized technologies by introducing a central authority.</p>
          </list-item>
        </list>
        <p>From a health care perspective, one of the biggest concerns in capturing and coding patient information is privacy [<xref ref-type="bibr" rid="ref106">106</xref>]. Several blockchain implementations allow the creation of smart, codified contracts that allow for the storage of immutable information. For example, Ethereum enabled the creation of smart contracts that codify contract agreements. When several parties agree to a transaction, they create mechanisms to ensure trust [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref107">107</xref>]. Smart contracts write the terms of a contract in code, which is executed on the blockchain, and has <italic>the ability to be self-executing and self-enforcing</italic> [<xref ref-type="bibr" rid="ref12">12</xref>]. Therefore, smart contracts can minimize trust concerns among parties [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref107">107</xref>].</p>
        <p>Blockchain’s features and design make it a model for processes plagued by trust issues [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref108">108</xref>], and it is ideal for increasing trust in contexts involving parties that do not have reason to trust each other [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref108">108</xref>]. One such context is health care [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
      </sec>
      <sec>
        <title>Blockchain in Health Care: Challenges and Solutions</title>
        <p>The following subsections describe a challenge in health care and discuss blockchain solutions being developed by companies to address them.</p>
        <sec>
          <title>Electronic Health Records</title>
          <sec>
            <title>Challenge Description</title>
            <p>EHRs digitally store patients’ health data [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref109">109</xref>,<xref ref-type="bibr" rid="ref110">110</xref>]. However, data are fragmented throughout EHR systems: patients often interact with different health care providers (usually the stewards of the data), creating challenges related to accessing past information [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. In addition, providers have different EHR systems that may not be fully interoperable [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. These factors contribute to difficulties in data sharing [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>].</p>
            <p>Patients’ health data end up in silos and cannot be integrated with data from other providers or sources, such as connected devices. Ultimately, there is no easy way to obtain a holistic view of a patient’s health, leading to errors, delays, and poorer health outcomes [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref110">110</xref>].</p>
          </sec>
          <sec>
            <title>Use of Blockchain</title>
            <p>Blockchain solutions can create an overarching hub, potentially on the cloud, to link all records of individual patients [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref29">29</xref>], without storing health data on the blockchain itself [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref111">111</xref>]. Rather, the blockchain infrastructure would act as a hub that points to the location of a patient’s records off-chain [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. Data access and changes to records can be tracked and displayed to the patient in real time. Furthermore, patients could control access to their records by giving permission to providers, researchers, and third parties to access their data. In this manner, an EHR-blockchain solution would allow for all health data from individuals to be accessed and controlled by the patient, facilitating a complete view of patients’ health [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. This solution would also give patients greater control and transparency over their health data [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
            <p>For example, MedRec is a blockchain-enabled solution for EHRs [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. It is a system developed by the Massachusetts Institute of Technology that provides a transparent view of medical history. MedRec uses smart contracts in Ethereum to encode metadata by referencing medical data from different sources, including information about ownership and permission. These references “create an accessible bread crumb trail for medical histor[ies]” [<xref ref-type="bibr" rid="ref7">7</xref>]. Providers may append a new patient record in MedRec, but patients are the ones who give permission for data to be accessed and shared. This increases transparency and allows patients to keep track of their records [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
            <p>Similar solutions include PatientTruth [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>], CareX [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>], MEDIS [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>], and MedicalChain [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Typically, EHR-blockchain solutions store references to off-chain files containing EHRs and also work with less traditional sources, such as data from connected devices. Patients control their records and with whom they wish to share their data (eg, health care professionals, hospitals, and insurance providers). Some of these solutions allow patients to sell deidentified records (eg, to health studies) with a crypto token from the platform. The financial component creates a form of health data marketplace in which patients own and are able to profit from their health data.</p>
            <p>Another organization working with blockchain in an EHR context is CitizenHealth [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref43">43</xref>], which developed two solutions: Humantiv [<xref ref-type="bibr" rid="ref44">44</xref>], which also combines data from EHRs and other sources with an added gamification component in which patients earn rewards according to their health indicators, and Medoplex [<xref ref-type="bibr" rid="ref45">45</xref>], the company’s marketplace component. GEM, a US-based start-up, is developing a solution that uses Ethereum to create a shared network where providers have real-time access to medical documents [<xref ref-type="bibr" rid="ref18">18</xref>]. GEM is partnering with Nordic-based Tieto to create a blockchain platform that enables patient control over medical records and genomic data [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref113">113</xref>].</p>
            <p>It is important to note that a blockchain infrastructure, as described above, could mitigate data sharing issues by providing an interoperable, auditable, and secure landscape of transactions controlled by data owners. This, in turn, would allow easy and transparent access to disparate health records. As stated by McGhin et al [<xref ref-type="bibr" rid="ref18">18</xref>], when discussing blockchain cloud infrastructures, “the role of blockchain in cloud data infrastructure is facilitating the creation of a decentralized and trusted cloud data provenance architecture that allows tamperproof records, greater transparency of data accountability, and enhanced privacy and availability of the data.” However, the blockchain itself does not impact the interoperability of the health data itself or the local systems in which it is stored. Rather, it acts as an overarching infrastructure with references to off-chain resources whose access is auditable, secure, and transparent to all authorized parties within the distributed network.</p>
          </sec>
        </sec>
        <sec>
          <title>Drug Supply Chain</title>
          <sec>
            <title>Challenge Description</title>
            <p>One of the biggest challenges faced by pharmaceutical companies today is counterfeit drugs. In total, US $200 billion are lost to counterfeit drugs annually, and their use puts patients’ lives at risk [<xref ref-type="bibr" rid="ref46">46</xref>]. Manufacturers do not have a unified and interoperable system of supply chain management, lack incentives to share data and information, and are consequently siloed, making end-to-end traceability and drug provenance difficult [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref114">114</xref>].</p>
            <p>In the United States, the Drug Supply Chain Security Act (DSCSA) established a set of requirements that must be implemented by pharmaceutical companies until 2023. These requirements include product tracing and verification [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref115">115</xref>,<xref ref-type="bibr" rid="ref116">116</xref>].</p>
          </sec>
          <sec>
            <title>Use of Blockchain</title>
            <p>By storing transactional data from the supply chain on blockchain, it is possible to establish an <italic>immutable record of provenance</italic> [<xref ref-type="bibr" rid="ref117">117</xref>]. Blockchain can provide a transparent ledger that traces products throughout the supply chain, from manufacturing to distribution. This will ensure compliance with the DSCSA and improve patient safety. Furthermore, blockchain can also track whether products are being transported and handled under appropriate conditions [<xref ref-type="bibr" rid="ref111">111</xref>].</p>
            <p>One of the companies working in this scenario was BlockVerify. The company is working on a DSCSA-compliant solution that traces products and identifies counterfeit drugs [<xref ref-type="bibr" rid="ref46">46</xref>-<xref ref-type="bibr" rid="ref48">48</xref>] A product is labeled with BlockVerify’s tag and verified along the supply chain, with a permanent record on a private blockchain. Consumers and retail locations can use this record to ensure that the product is genuine. Merck has filed a patent to use blockchain to track drug information in the supply chain; while the company already has systems to prevent fraud, it is expected that blockchain could minimize existing inefficiencies [<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]. Modum uses blockchain to ensure that medical products are being transported at the correct temperature [<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref54">54</xref>]. Sensor devices are added to shipments, and smart contracts for each shipment are fixed with sensors, including the alarms. The sensors monitor the temperature during transportation and, when the shipment is received, the data are transferred to a blockchain and the smart contract evaluates whether conditions and regulations have been met [<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref54">54</xref>].</p>
            <p>Efforts have also been made to tackle the food supply chain. IBM Food Trust is a permissioned blockchain that allows stakeholders to view the supply chain history of a food item and complementary information (eg, certifications, testing, temperature, and location). For example, organizations can identify when a food item is contaminated and trace the contamination back to its source [<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref58">58</xref>]. Another solution is being used in China: Ant Financial, an affiliate of the e-commerce enterprise Alibaba, is using a permissioned blockchain that tracks the production of rice in the city of Wuchang. Quick Response codes were added to rice packages, so that users scan these codes to obtain information (eg, location of the harvest, type of seed used, or transportation). Alibaba is also working on developing a food trust framework that, in its pilot phase, tracked shipments from China to Australia and New Zealand [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>].</p>
          </sec>
        </sec>
        <sec>
          <title>Health Insurance</title>
          <sec>
            <title>Challenge Description</title>
            <p>There is a lack of trust between payers, providers, and patients with a complete view and coordination of health care [<xref ref-type="bibr" rid="ref6">6</xref>]. Patients often pay expensive premiums while dealing with a lack of transparency and the ability to compare prices, in addition to the risk of insurance fraud that affects all stakeholders [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. Providers must go through complex and bureaucratic processes to submit a claim [<xref ref-type="bibr" rid="ref41">41</xref>]. The challenging ecosystem can be exemplified through the claims management process: (1) first, a provider must be covered by health insurers—meaning that the provider must also maintain benefits’ databases and keep track of services delivered, adding additional expenses; (2) if patients receive services from the provider, the insurer checks the service against the patients’ health plans to check their eligibility; (3) the process takes several weeks and involves multiple people checking agreements, leading to delays [<xref ref-type="bibr" rid="ref41">41</xref>].</p>
          </sec>
          <sec>
            <title>Use of Blockchain</title>
            <p>In 2017, a survey revealed that 98% of payers with over 500,000 members are pursuing blockchain-enabled solutions [<xref ref-type="bibr" rid="ref69">69</xref>]. Through the use of smart contracts, it is possible to codify terms of agreement between providers, payers, and patients, automating processes and minimizing inefficiencies. For example, PokitDok developed DokChain, a private blockchain that references off-chain file systems. DokChain contains several smart contracts that request and return data from health insurance providers and payers in real time [<xref ref-type="bibr" rid="ref61">61</xref>-<xref ref-type="bibr" rid="ref63">63</xref>], possibly enabling real-time status checks and mechanisms for error identification. The goal is for DokChain to make decisions on insurance claims in real time using smart contracts. As soon as a patient receives a service, it is recorded on DokChain and visualized by all stakeholders. Smart contracts can determine whose responsibility the claim falls under and how much is owed to each party, processing that amount in real time [<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]. PokitDok also offers application programming interfaces to calculate payment risk for a patient [<xref ref-type="bibr" rid="ref66">66</xref>] and to allow patients to schedule and pay for health services [<xref ref-type="bibr" rid="ref67">67</xref>], automating payments and checking benefits in real time.</p>
            <p>The start-up GEM created a blockchain prototype in 2017 that helped to settle a claim in less than 5 minutes [<xref ref-type="bibr" rid="ref39">39</xref>]. Payspan, a 25-year-old health care reimbursement company, is also working on blockchain networks to connect providers and payers for claims management and payment processing [<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>].</p>
            <p>Initiatives that focus on the creation of a health data marketplace (eg, Medoplex) want to allow health care buyers (eg, patients) and sellers (eg, providers) to connect without the need for insurance companies. Their goal is to create a marketplace platform where patients can search, select, and pay for health care services using a crypto token. CareX, MedicalChain, and BlockRx are other solutions that allow for the payment of health services with crypto tokens obtained from health record sharing [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref111">111</xref>,<xref ref-type="bibr" rid="ref114">114</xref>]. Many companies that deal with EHRs seem to view health insurance as a complementary use case: by creating a health data marketplace platform that allows patients to share their data with health care providers and professionals, the idea seems to be that intermediaries (eg, insurance companies) will not be needed or their role will be diminished.</p>
          </sec>
        </sec>
        <sec>
          <title>Genomics</title>
          <sec>
            <title>Challenge Description</title>
            <p>DNA is a molecule that encodes the genetic instructions of organisms [<xref ref-type="bibr" rid="ref9">9</xref>], where genes are collections of DNA [<xref ref-type="bibr" rid="ref118">118</xref>] and a genome is the collection of an organism’s genes [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref119">119</xref>]. The human genome comprises more than 20,000 genes [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref120">120</xref>,<xref ref-type="bibr" rid="ref121">121</xref>].</p>
            <p>The study of genomics data in conjunction with social and environmental determinants of health gave rise to precision medicine [<xref ref-type="bibr" rid="ref122">122</xref>]. This field of research and treatment can help individuals and researchers better understand the cause of diseases, contribute to the development of new drugs, and aid in the creation of personalized interventions for individuals with specific genetic traits, in addition to many other benefits [<xref ref-type="bibr" rid="ref123">123</xref>]. However, for this potential to be fully realized, large volumes of genomic data are required [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref124">124</xref>].</p>
            <p>There are several barriers to the availability of massive genomic data sets, including security and privacy concerns, prohibitive costs, and data sharing [<xref ref-type="bibr" rid="ref9">9</xref>]. The latter is related to a lack of interoperability between systems that store genomic data and to data ownership [<xref ref-type="bibr" rid="ref9">9</xref>]. In addition, a human genome generates over 200 GB of data, and it is estimated that more than 100 million genomes will be sequenced by 2025. Therefore, storage and network transfer speeds also limit data sharing [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref121">121</xref>].</p>
          </sec>
          <sec>
            <title>Use of Blockchain</title>
            <p>The business model for genomic data involves individuals hiring companies such as 23andMe and Ancestry to sequence their genome and receive results. These companies then sell the sequenced data to researchers. With a blockchain network that connects data sellers (eg, an individual who sequenced their genome) and data buyers (eg, a pharmaceutical or research company), without the need for personal genomic companies acting as intermediaries, the transparency of the process will increase while costs will decrease. In addition, data sharing problems can be improved by connecting disparate genomic records on the blockchain, similar to what MedRec and other blockchain-EHR solutions have been proposing [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref111">111</xref>]. Although this will not solve all interoperability issues in the industry, it will allow easier, secure, and transparent access to disparate records of data, facilitating data sharing.</p>
            <p>One of the companies that hope to build a genomic and health data marketplace is Nebula Genomics, through the development of a <italic>storage, sharing, and computing platform for biomedical big data</italic> [<xref ref-type="bibr" rid="ref70">70</xref>]. The company has a partnership with Veritas Genomics. Veritas’ platform processes and stores large amounts of genetic information, and Nebula hopes to build on top of it. Individuals will be able to store their genetic information on Veritas’ platform and, with blockchain, share and sell their data in the genomic data marketplace. Similar to the case with EHRs, users own their data and control permissions for data sharing, increasing transparency and minimizing security and privacy concerns. Their proposed solution has the potential to [<xref ref-type="bibr" rid="ref9">9</xref>] (1) minimize costs, since data buyers will acquire data directly from owners who can receive sequencing subsidies from buyers to encourage the generation of genomic data sets (eg, offering sequencing subsidies to individuals with specific traits that a specific research group plans to study); (2) increase transparency, since owners will control access and data sharing will be protected through cryptography. Owners will remain anonymous, while buyers will have to provide information about their identity. Blockchain records all transactions in an immutable log that is easily auditable; and (3) increase the availability of data by integrating data from several sources. The network offers space-efficient data-encoding formats and leverages computer resources to facilitate the transfer of information [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref121">121</xref>].</p>
            <p>Other companies have similar solutions, with minor differences. LunaDNA allows anyone to join the blockchain network and win company shares based on shared data in the form of a crypto token. Researchers pay to conduct research on aggregated data, and proceeds earned from research are passed on to stakeholders as dividends. Unlike Nebula Genomics, LunaDNA currently does not provide genome sequencing services, but it accepts files from companies such as 23andMe and Ancestry. Blockchain is used to give individuals ownership of their data and for the generation of an immutable log of transactions [<xref ref-type="bibr" rid="ref71">71</xref>-<xref ref-type="bibr" rid="ref75">75</xref>]. Shivom [<xref ref-type="bibr" rid="ref76">76</xref>-<xref ref-type="bibr" rid="ref79">79</xref>], Zenome [<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref81">81</xref>], EncrypGen [<xref ref-type="bibr" rid="ref82">82</xref>-<xref ref-type="bibr" rid="ref85">85</xref>], and Macrogen [<xref ref-type="bibr" rid="ref86">86</xref>-<xref ref-type="bibr" rid="ref88">88</xref>] are other similar companies that are using blockchain to empower patients by allowing them to own and share genomic data.</p>
          </sec>
        </sec>
        <sec>
          <title>Consent Management</title>
          <sec>
            <title>Challenge Description</title>
            <p>In health studies, the process of obtaining consent from participants is fallible [<xref ref-type="bibr" rid="ref125">125</xref>]. The Food and Drug Administration cited the main deficiencies related to consent: the failure to obtain informed consent, use of expired or incomplete forms, failure to provide copies of the forms to participants, missing documents, and changes made to documents without the approval of a review ethics board [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref125">125</xref>]. These problems are aggravated given that reconsent has to be sought in several cases (eg, when there is a revision of the study protocol, new risks are discovered, or there is a worsening of the medical condition of a participant) [<xref ref-type="bibr" rid="ref126">126</xref>]. Oftentimes, consent needs to be obtained for cohabitants, caregivers, or legal guardians [<xref ref-type="bibr" rid="ref125">125</xref>-<xref ref-type="bibr" rid="ref128">128</xref>].</p>
            <p>In addition to limitations in traditional consent methods, the global society is moving into an age of ubiquitous smart technologies that monitor our health, which increases the complexity of data collection points and, in turn, of consent management. The challenge of obtaining consent for increasingly advanced methods of data collection, use, and disclosure calls for new solutions to perfect consent procedures and the need to protect the safety of individuals.</p>
          </sec>
          <sec>
            <title>Use of Blockchain</title>
            <p>Blockchain can provide an immutable and timestamped log of consent, making the process more transparent [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref111">111</xref>,<xref ref-type="bibr" rid="ref129">129</xref>]. In the case of health studies, participants will be able to monitor and manage consent, giving informed consent for certain types of data to be collected but not others and revoking their consent at any time. Through the use of cryptographic techniques of identity management, participants can make sure that they are reviewing the latest consent forms and that these were approved by the review ethics board. Researchers would also be benefited, as the measures taken to ensure ethical and legal requirements throughout the research would be clearly auditable. Moreover, it would be easier for them to obtain, track, and update patient consent during the study.</p>
            <p>With a consent management platform built on blockchain, authorized parties in the network will have access to timestamped and tamperproof logs of user consent. However, this does not serve as a magic bullet to solve all consent management issues, and researchers must still be careful when collecting informed consent and ensure all ethical and legal requirements. For example, participants may revoke their consent at any time during the study (revocability), and researchers would need to stop collecting participant data at this point despite the fact that data may already have been collected (nonretractability). Similar to traditional health studies, consent forms should include a description of the protocols necessary for revoking consent according to data protection regulations and indicate to participants whether their data are being deleted after their consent is nullified. For example, Article 17 of the General Data Protection Regulation describes the “right to be forgotten” [<xref ref-type="bibr" rid="ref130">130</xref>], in which personal data must be deleted after consent is revoked.</p>
            <p>This would not present a problem for blockchain systems, as the collected data would not be stored on the blockchain, rather the consent of the individual is. If a participant revokes consent, the system will instantly be updated to reflect this and notify the researchers of the change. All consent status updates of participants cannot be tampered with on the blockchain and can be easily auditable in case of problems [<xref ref-type="bibr" rid="ref129">129</xref>]. Furthermore, if the study uses connected devices for data collection, smart contracts can be developed to ensure that, as soon as a consent is revoked, data immediately stop being collected. What will happen to the data that were already collected depends on the study protocol designed by the researcher. If data deletion is needed, the researcher will have to delete the data manually from their own database (which is not related to blockchain in any way; as mentioned, blockchain only stores the information on consent and not the data as such). In this way, a blockchain-consent platform can facilitate the process of consent management and mitigate some trust issues, but it is still up to researchers to ensure correct and ethical protocols and guidelines are being followed.</p>
            <p>Hu-manity.co developed a mobile app called My31, built on IBM blockchain, to help individuals manage their consent to the use of their personal and health information. Users can consent to sharing their data with third parties and researchers, and receive compensation for it [<xref ref-type="bibr" rid="ref89">89</xref>,<xref ref-type="bibr" rid="ref90">90</xref>]. Another blockchain-powered platform for managing consent is being developed by Bitfury, with the goal of managing consent for research. All updates related to user consent are timestamped and recorded on the blockchain for future auditing [<xref ref-type="bibr" rid="ref91">91</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]. The solution can be used both as a new system and in conjunction with existing systems. HealthVerity is also developing a blockchain solution to manage consent. Unlike other solutions, HealthVerity’s consent platform seems to be more focused on consumer applications that collect health data than medical or clinical research [<xref ref-type="bibr" rid="ref93">93</xref>].</p>
            <p>Although not specifically on consent management, DeepMind (Google’s artificial intelligence conglomerate) is developing a project to allow hospitals and patients to track events related to health data in real time [<xref ref-type="bibr" rid="ref94">94</xref>-<xref ref-type="bibr" rid="ref98">98</xref>]. Any interaction with a patient’s health data is recorded on a distributed ledger, which will store information stating that the data were used and their purpose. This project, <italic>Verifiable Audit Trail</italic>, has the potential to increase transparency in health research and minimize some of the trust issues between stakeholders [<xref ref-type="bibr" rid="ref94">94</xref>-<xref ref-type="bibr" rid="ref98">98</xref>].</p>
            <p>There have also been several academic initiatives exploring the use of blockchain for consent management. For example, researchers from Institut National de la Santé Et de la Recherche Médicale and Assistance Publique-Hôpitaux de Paris in France have created a proof of concept to manage patient consent in clinical trials that use cryptographic signatures for e-signing. The timestamped consent for different form versions is recorded on the blockchain as a master document [<xref ref-type="bibr" rid="ref14">14</xref>]. In Canada, Queen’s University has also developed a similar solution for clinical trials, titled BlockTrial, where patients assign permission for data access and researchers can query off-chain data [<xref ref-type="bibr" rid="ref99">99</xref>]. The Toronto-based University Health Network, in partnership with IBM and digital health agencies, is working on the patient control and consent blockchain initiative to allow the permissioned access of data, managed by patients through individual consent and built on blockchain to allow immutable storage of consent directives. Patients can access a mobile app, managing who has access to their data and for what reason. Currently, only University Health Network–produced data are available, but the goal is to enable the integration of data from multiple sources [<xref ref-type="bibr" rid="ref100">100</xref>-<xref ref-type="bibr" rid="ref102">102</xref>].</p>
            <p>Velmovitsky et al [<xref ref-type="bibr" rid="ref129">129</xref>] also developed a proof-of-concept blockchain to help patients manage consent, focusing on third-party consumer apps that collect health data such as smart devices. In this prototype, patients can grant and revoke consent for different data types and different periods (eg, users give consent for temperature to be collected but not movement, from September to October). This work uses Hyperledger Fabric to create a blockchain network and proposes a governance structure to collect data from smart devices.</p>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Blockchain in Health Care</title>
        <p>The health care challenges in the areas of EHRs, supply chains, health insurance, genomics, and consent management are not mutually exclusive. For example, the use of blockchain to address challenges in genomics and EHRs shares many similar challenges regarding data ownership, data sharing, and the creation of a marketplace where owners and buyers can trade data. Consent management and EHRs can also be complementary, with blockchain-enabled solutions for consent acting as a sort of <italic>access control</italic>. Researchers and health care providers could potentially access individual health records stored in off-chain databases through blockchain infrastructure, provided that they have consent from the individual.</p>
        <p>It is interesting to note that many of the solutions described seem to consider only an ideal workflow. In an emergency situation where the patient is unable to authorize data sharing, there should be mechanisms for doctors and nurses to access data [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>Similar to any new technology, while blockchain seems to hold the potential to improve several existing challenges in health care and give more agency to patients, the actual impact of the technology is unclear. Many solutions want to eliminate intermediaries (eg, allowing patients and providers to connect without the need of insurance companies; however, it is impossible to determine whether this kind of disruption will actually happen and whether patients are ready for such complexity [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]). Although blockchain solutions can minimize inefficiencies, they are more likely to run in conjunction with existing systems from third parties. In other words, the solutions will incorporate third parties and make the process more transparent for the participants, thereby increasing trust [<xref ref-type="bibr" rid="ref12">12</xref>]. This would also ease the adoption of blockchain in the industry, as several stakeholders would offer less resistance.</p>
        <p>Most of the solutions we found, with a few exceptions, seem to be at the initial development or prototyping stage: their architecture and basic functionalities are planned out, and companies are now looking to raise funds and continue their implementation. Although this shows that the health care sector is positive about the potential of blockchain, it also makes it difficult to concretely evaluate the potential of the technology.</p>
      </sec>
      <sec>
        <title>Immutability, Decentralization, and Trust</title>
        <p>Blockchain is designed to be distributed, transparent, and immutable by design [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>] and can improve trust among stakeholders [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref108">108</xref>]. This is true in the scenarios described above. By eliminating centralized decision making, automating processes, and increasing transparency in data collection and use, blockchain can increase trust in health care processes.</p>
        <p>However, blockchain’s embedded features could prove to be a challenge if misused. For example, the fact that every node in the network maintains a copy of the ledger is redundant. Decentralized systems are less efficient, scalable, and cost-effective compared with centralized systems [<xref ref-type="bibr" rid="ref12">12</xref>]. By design, every participant node must possess a full copy of the distributed ledger; as the number of participants increases, so does the computational requirements such as storage and energy. Blockchain has been seen as a potential solution to address issues in the environment, such as creating a marketplace for energy trading. However, some critics point out that blockchain will do more harm than good because it expends a huge amount of energy [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref99">99</xref>]. These factors may limit the scalability of the blockchain solutions. They are not limitations of the technology per se, but design characteristics, and developers must consider a trade-off between these and the desired transparency and security provided by the distributed ledger. Trade-offs between different blockchain features must also be considered (eg, using a public or permissioned blockchain), as explored by O’Donoghue et al [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
        <p>Similarly, blockchain’s immutability means it is <italic>append-only</italic> for public implementation [<xref ref-type="bibr" rid="ref12">12</xref>]. Companies dealing with General Data Protection Regulation must abide by a key principle of regulation, which is the right to data deletion [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]. However, this is not an option for public blockchain implementations [<xref ref-type="bibr" rid="ref12">12</xref>]. This is one of the reasons why it is not recommended to store personal data on the blockchain [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Rather, it should be stored in off-chain databases with reference to the chain. A study conducted by Park et al [<xref ref-type="bibr" rid="ref132">132</xref>] studied the feasibility of storing, sharing, and managing records on the blockchain. The study confirmed that it was possible to manage records in a private blockchain, but several challenges need to be addressed first, such as data size and costs.</p>
        <p>Although blockchain provides an immutable ledger, it should also be noted that the information stored in the ledger is only as accurate as its input. This means that developers should create mechanisms to ensure that the correct data are uploaded to the blockchain [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref99">99</xref>].</p>
      </sec>
      <sec>
        <title>Key and Identity Management</title>
        <p>Information stored on the blockchain is secured through cryptographic techniques that require the use of public and private keys [<xref ref-type="bibr" rid="ref18">18</xref>]. Private keys act as a password that allows the user to access information. For example, in the Bitcoin blockchain, user A can send Bitcoins to user B using B’s public key. However, user B will only be able to access the Bitcoin with their private key. Users have one key to access all their blocks (analogous to a password to access all user data). If the key is compromised, all user data may be leaked. In the case of health care, which deals with sensitive data, this issue should not be understated [<xref ref-type="bibr" rid="ref18">18</xref>]. For blockchain-EHR solutions, if a malicious party obtains a patient’s private key, there is a significant risk of identity theft, as they will have access to the patient’s full medical history [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>One possible alternative to key management is through identity verification using blockchain [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]; it can provide an immutable ledger that stores and maintains legal documents such as birth certificates and business contracts. A person would then be able to prove their identity by accessing the blockchain [<xref ref-type="bibr" rid="ref18">18</xref>]. Many countries, such as Estonia, use blockchain to verify various attributes of its citizens [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]. By being able to say if a person is an Estonian resident through blockchain, the platform can provide additional web-based services (eg, allowing citizens to vote on the web). The country already has an EHR system, accessed by a unique ID that uses blockchain to ensure integrity [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]. PokitDok is studying the application of a protocol called the contextually relevant identity management protocol with DokChain, in which different aspects of an identity are used for validation. For example, to buy an alcoholic a drink, the only necessary information is age. DokChain’s solution would allow users to decide which specific personal information to share based on the context. To validate an identity, the technology is planning to create a consensus mechanism in which an individual’s private key is partitioned among third parties. The key can be regenerated by using a subset of partitions. This is initially used for key recovery, but the goal is to have this function as implicit identity verification every time an identity needs to be validated [<xref ref-type="bibr" rid="ref62">62</xref>]. A similar solution that distributes a user’s identity attributes is being developed by the Canadian company SecureKey [<xref ref-type="bibr" rid="ref131">131</xref>].</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Blockchain, an immutable ledger in which all participants view an immutable version of the truth, is a promising technology that can help to minimize several challenges currently experienced in health care. This paper focused on a literature review and market assessment to determine the main challenges that could be improved by blockchain in today’s health care industry. The results showed the following five challenges:</p>
        <list list-type="bullet">
          <list-item>
            <p>Health records are stored between different providers in systems that lack interoperability. This makes it difficult for stakeholders to share data and, therefore, to have a complete view of a patient’s health.</p>
          </list-item>
          <list-item>
            <p>Provenance and counterfeit products in drug supply chains are among the biggest hurdles faced by pharmaceutical companies today.</p>
          </list-item>
          <list-item>
            <p>There is a lack of connectivity among payers, providers, and patients in terms of insurance, which prevents access and coordination of care.</p>
          </list-item>
          <list-item>
            <p>Genomics data, one of the greatest promises of precision health, are limited by high costs, lack of massive data sets, and interoperability issues.</p>
          </list-item>
          <list-item>
            <p>Increasingly advanced methods of data collection and analysis raise concerns regarding ethics, ownership, privacy, and regulations of health data.</p>
          </list-item>
        </list>
        <p>Although solutions vary, blockchain can provide an immutable and tamperproof log of transactions. Blockchain’s features of immutability, decentralization, distribution, and transparency can optimize processes, minimize inefficiencies, and increase trust in all contexts covered in this review. However, no silver bullet to solve every need in health care exists, and companies, developers, and decision makers need to be careful when considering a blockchain solution. Although the technology has potential, it also brings new concerns about data ownership and security.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>As the aim of this review was to provide an industry point of view of the use of blockchain in health care, when defining the protocols for inclusion and exclusion, we did not include a critical component to evaluate the solutions included. Furthermore, while we searched for white papers and reports of the solutions whenever possible, we included in our results solutions already in place, in early stages of development, or recently announced, as our goal was to provide a mindset of the health care industry pertaining to blockchain. Future work should focus on critically analyzing the solutions described here for feasibility and efficiency. An interesting consideration from this analysis would be to define which challenges can be further improved with the use of blockchain. In other words, this analysis could point to where blockchain would be the most useful. In addition, blockchain can be used in conjunction with new fields of computer science, including big data and artificial intelligence [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref117">117</xref>]. Future work should also focus on studying blockchain in the context of these emerging technologies. Finally, it is important to note that the ontology used here, dividing the topics into five major challenges, is not exhaustive. There are many use cases where blockchain can be applied that, while not directly related to health care, may affect it (eg, key and identity management). In addition, many challenges described in the literature (eg, interoperability and data sharing of health systems) are encompassed by this ontology. In exploring these five areas, our aim was to provide an overview of the solutions being developed by the health care industry and which areas they are directing their efforts, rather than providing a defining list of use cases in health care in which blockchain can be used.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">DSCSA</term>
          <def>
            <p>Drug Supply Chain Security Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">RQ</term>
          <def>
            <p>research question</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This research was supported by the Canadian Standards Association Group and MITACS internship to the corresponding author.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>PEV wrote the manuscript and conducted a literature review. PEV, PPM, LXF, and FMB contributed to the conceptualization, design, and approach of the manuscript, as well as to the interpretation of the argument made in the manuscript. All authors contributed to the writing and revision of the manuscript. All authors provided the final approval of the manuscript and agree to be accountable for this manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Prosperi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Min</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Bian</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Modave</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Big data hurdles in precision medicine and precision public health</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2018</year>
          <month>12</month>
          <day>29</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>139</fpage>
          <pub-id pub-id-type="doi">10.1186/s12911-018-0719-2</pub-id>
          <pub-id pub-id-type="medline">30594159</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-018-0719-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC6311005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>de Arriba-Pérez</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Caeiro-Rodríguez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Santos-Gago</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Collection and processing of data from wrist wearable devices in heterogeneous and multiple-user scenarios</article-title>
          <source>Sensors (Basel)</source>
          <year>2016</year>
          <month>09</month>
          <day>21</day>
          <volume>16</volume>
          <issue>9</issue>
          <fpage>1538</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s16091538"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s16091538</pub-id>
          <pub-id pub-id-type="medline">27657081</pub-id>
          <pub-id pub-id-type="pii">s16091538</pub-id>
          <pub-id pub-id-type="pmcid">PMC5038811</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mooney</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Pejaver</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Big data in public health: terminology, machine learning, and privacy</article-title>
          <source>Annu Rev Public Health</source>
          <year>2018</year>
          <month>04</month>
          <day>01</day>
          <volume>39</volume>
          <issue>1</issue>
          <fpage>95</fpage>
          <lpage>112</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29261408"/>
          </comment>
          <pub-id pub-id-type="doi">10.1146/annurev-publhealth-040617-014208</pub-id>
          <pub-id pub-id-type="medline">29261408</pub-id>
          <pub-id pub-id-type="pmcid">PMC6394411</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sakr</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Elgammal</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Towards a comprehensive data analytics framework for smart healthcare services</article-title>
          <source>Big Data Res</source>
          <year>2016</year>
          <month>06</month>
          <volume>4</volume>
          <fpage>44</fpage>
          <lpage>58</lpage>
          <pub-id pub-id-type="doi">10.1016/j.bdr.2016.05.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barrett</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Humblet</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Hiatt</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Adler</surname>
              <given-names>NE</given-names>
            </name>
          </person-group>
          <article-title>Big data and disease prevention: from quantified self to quantified communities</article-title>
          <source>Big Data</source>
          <year>2013</year>
          <month>09</month>
          <volume>1</volume>
          <issue>3</issue>
          <fpage>168</fpage>
          <lpage>75</lpage>
          <pub-id pub-id-type="doi">10.1089/big.2013.0027</pub-id>
          <pub-id pub-id-type="medline">27442198</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bublitz</surname>
              <given-names>FM</given-names>
            </name>
            <name name-style="western">
              <surname>Oetomo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sahu</surname>
              <given-names>KS</given-names>
            </name>
            <name name-style="western">
              <surname>Kuang</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fadrique</surname>
              <given-names>LX</given-names>
            </name>
            <name name-style="western">
              <surname>Velmovitsky</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Nobrega</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Morita</surname>
              <given-names>PP</given-names>
            </name>
          </person-group>
          <article-title>Disruptive technologies for environment and health research: an overview of artificial intelligence, blockchain, and internet of things</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2019</year>
          <month>10</month>
          <day>11</day>
          <volume>16</volume>
          <issue>20</issue>
          <fpage>3847</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph16203847"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph16203847</pub-id>
          <pub-id pub-id-type="medline">31614632</pub-id>
          <pub-id pub-id-type="pii">ijerph16203847</pub-id>
          <pub-id pub-id-type="pmcid">PMC6843531</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</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>
          <source>Proceedings of the 2nd International Conference on Open and Big Data (OBD)</source>
          <year>2016</year>
          <conf-name>2nd International Conference on Open and Big Data (OBD)</conf-name>
          <conf-date>Aug. 22-24, 2016</conf-date>
          <conf-loc>Vienna, Austria</conf-loc>
          <fpage>30</fpage>
          <pub-id pub-id-type="doi">10.1109/obd.2016.11</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ekblaw</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>MedRec: blockchain for medical data access, permission management and trend analysis</article-title>
          <source>Massachusetts Institute of Technology</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dspace.mit.edu/bitstream/handle/1721.1/109658/987247095-MIT.pdf?sequence=1%0Ahttps://dspace.mit.edu/handle/1721.1/109658">https://dspace.mit.edu/bitstream/handle/1721.1/109658/987247095-MIT.pdf?sequence=1%0Ahttps://dspace.mit.edu/handle/1721.1/109658</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grishin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Obbad</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Estep</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cifric</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Church</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <source>Blockchain-enabled genomic data sharing and analysis platform</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arep.med.harvard.edu/pdf/Grishin_Church_v4.52_2018.pdf">https://arep.med.harvard.edu/pdf/Grishin_Church_v4.52_2018.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>Healthcare rallies for blockchains</article-title>
          <source>IBM Institute for Business Value</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ibm.com/downloads/cas/BBRQK3WY">https://www.ibm.com/downloads/cas/BBRQK3WY</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <article-title>Team Medicine: how life sciences can win with blockchain</article-title>
          <source>IBM Institute for Business Value</source>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ibm.com/downloads/cas/RYD0QA7G">https://www.ibm.com/downloads/cas/RYD0QA7G</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Urban</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Pineda</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>Inside the black blocks</source>
          <year>2018</year>
          <access-date>2021-05-25</access-date>
          <publisher-loc>Toronto, ON</publisher-loc>
          <publisher-name>Mowat Centre</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://munkschool.utoronto.ca/mowatcentre/wp-content/uploads/publications/168_inside_the_black_blocks.pdf">https://munkschool.utoronto.ca/mowatcentre/wp-content/uploads/publications/168_inside_the_black_blocks.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Farouk</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alahmadi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ghose</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mashatan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Blockchain platform for industrial healthcare: vision and future opportunities</article-title>
          <source>Comp Commun</source>
          <year>2020</year>
          <month>03</month>
          <volume>154</volume>
          <fpage>223</fpage>
          <lpage>35</lpage>
          <pub-id pub-id-type="doi">10.1016/j.comcom.2020.02.058</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Benchoufi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ravaud</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology for improving clinical research quality</article-title>
          <source>Trials</source>
          <year>2017</year>
          <month>07</month>
          <day>19</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>335</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://trialsjournal.biomedcentral.com/articles/10.1186/s13063-017-2035-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13063-017-2035-z</pub-id>
          <pub-id pub-id-type="medline">28724395</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13063-017-2035-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC5517794</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hollander</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Carr</surname>
              <given-names>BG</given-names>
            </name>
          </person-group>
          <article-title>Virtually perfect? Telemedicine for Covid-19</article-title>
          <source>N Engl J Med</source>
          <year>2020</year>
          <month>04</month>
          <day>30</day>
          <volume>382</volume>
          <issue>18</issue>
          <fpage>1679</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1056/nejmp2003539</pub-id>
        </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>Dragov</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Croce</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Hefny</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>How blockchain can help in the COVID-19 crisis and recovery</article-title>
          <source>IDC UK Blog</source>
          <year>2020</year>
          <access-date>2020-05-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blog-idcuk.com/blockchain-help-in-the-covid-19-and-recovery/">https://blog-idcuk.com/blockchain-help-in-the-covid-19-and-recovery/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>World Economic Forum: how blockchain could help with Covid-19 supply chain disruption</article-title>
          <source>Ledger Insights</source>
          <year>2020</year>
          <access-date>2020-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ledgerinsights.com/world-economic-forum-how-blockchain-could-help-with-covid-19-supply-chain-disruption/">https://www.ledgerinsights.com/world-economic-forum-how-blockchain-could-help-with-covid-19-supply-chain-disruption/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McGhin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Choo</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>CZ</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in healthcare applications: research challenges and opportunities</article-title>
          <source>J Net Comp Appl</source>
          <year>2019</year>
          <month>06</month>
          <volume>135</volume>
          <fpage>62</fpage>
          <lpage>75</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jnca.2019.02.027</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vazirani</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>O'Donoghue</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Brindley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Meinert</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Implementing blockchains for efficient health care: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>12</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12439</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/2/e12439/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12439</pub-id>
          <pub-id pub-id-type="medline">30747714</pub-id>
          <pub-id pub-id-type="pii">v21i2e12439</pub-id>
          <pub-id pub-id-type="pmcid">PMC6390185</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>O'Donoghue</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Vazirani</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Brindley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Meinert</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Design choices and trade-offs in health care blockchain implementations: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>05</month>
          <day>10</day>
          <volume>21</volume>
          <issue>5</issue>
          <fpage>e12426</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/5/e12426/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12426</pub-id>
          <pub-id pub-id-type="medline">31094344</pub-id>
          <pub-id pub-id-type="pii">v21i5e12426</pub-id>
          <pub-id pub-id-type="pmcid">PMC6533871</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hasselgren</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kralevska</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gligoroski</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Faxvaag</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in healthcare and health sciences-a scoping review</article-title>
          <source>Int J Med Inform</source>
          <year>2020</year>
          <month>02</month>
          <volume>134</volume>
          <fpage>104040</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(19)30526-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.104040</pub-id>
          <pub-id pub-id-type="medline">31865055</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(19)30526-X</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>Chukwu</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Garg</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of blockchain in healthcare: frameworks, prototypes, and implementations</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <volume>8</volume>
          <fpage>21196</fpage>
          <lpage>1214</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.2969881</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>Agbo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mahmoud</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Eklund</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology in healthcare: a systematic review</article-title>
          <source>Healthcare (Basel)</source>
          <year>2019</year>
          <month>04</month>
          <day>04</day>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>56</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare7020056"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare7020056</pub-id>
          <pub-id pub-id-type="medline">30987333</pub-id>
          <pub-id pub-id-type="pii">healthcare7020056</pub-id>
          <pub-id pub-id-type="pmcid">PMC6627742</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>Reviews: from systematic to narrative: narrative review</article-title>
          <source>University of Alabama - Birmingham</source>
          <access-date>2020-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://guides.library.uab.edu/c.php?g=63689&#38;p=409774">https://guides.library.uab.edu/c.php?g=63689&#38;p=409774</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Levac</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Colquhoun</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>KK</given-names>
            </name>
          </person-group>
          <article-title>Scoping studies: advancing the methodology</article-title>
          <source>Implement Sci</source>
          <year>2010</year>
          <month>09</month>
          <day>20</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>69</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/1748-5908-5-69"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1748-5908-5-69</pub-id>
          <pub-id pub-id-type="medline">20854677</pub-id>
          <pub-id pub-id-type="pii">1748-5908-5-69</pub-id>
          <pub-id pub-id-type="pmcid">PMC2954944</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <article-title>Leader in blockchain news</article-title>
          <source>CoinDesk</source>
          <access-date>2020-05-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.coindesk.com/">https://www.coindesk.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <source>Cointelegraph</source>
          <access-date>2020-05-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cointelegraph.com/">https://cointelegraph.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>Get smarter about what matters to you</article-title>
          <source>Medium</source>
          <access-date>2020-05-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medium.com/">https://medium.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <source>MedRec</source>
          <access-date>2018-10-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medrec.media.mit.edu/">https://medrec.media.mit.edu/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>PatientTruth</article-title>
          <source>Embleema - Blockchain for Real-World Evidence</source>
          <access-date>2018-11-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://embleema.com/2020/01/16/explore-real-world-evidence/">https://embleema.com/2020/01/16/explore-real-world-evidence/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <article-title>Embleema blockchain network v.2</article-title>
          <source>Embleema WhitePaper</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://icocube.io/uploads/Embleema.pdf">https://icocube.io/uploads/Embleema.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>CareX Whitepaper</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://coins.newbium.com/post/13327-carex-blockchain-healthcare-ecosystem">https://coins.newbium.com/post/13327-carex-blockchain-healthcare-ecosystem</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stoffregen</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Blockchain healthcare ecosystem in 2018</article-title>
          <source>Medium</source>
          <year>2018</year>
          <access-date>2018-11-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medium.com/@erikstoffregen/blockchain-healthcare-ecosystem-d21631024454">https://medium.com/@erikstoffregen/blockchain-healthcare-ecosystem-d21631024454</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kovach</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ronai</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <source>MyMEDIS: a new medical data storage and access system</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mymedis.in/documents/MEDIS-White-Paper.pdf">https://mymedis.in/documents/MEDIS-White-Paper.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <article-title>Globally decentralized medical data store and blockchain-based ecosystem</article-title>
          <source>MEDIS</source>
          <access-date>2019-03-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mymedis.in/">https://mymedis.in/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Allison</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Gem shows off first blockchain application for health claims</article-title>
          <source>Intenational Business Times</source>
          <year>2017</year>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ibtimes.co.uk/gem-shows-off-first-blockchain-application-health-claims-1622574">https://www.ibtimes.co.uk/gem-shows-off-first-blockchain-application-health-claims-1622574</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <article-title>Health</article-title>
          <source>Gem</source>
          <access-date>2018-10-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://enterprise.gem.co/health/">https://enterprise.gem.co/health/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rizzo</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Gem partners with Philips for blockchain healthcare initiative</article-title>
          <source>CoinDesk</source>
          <year>2016</year>
          <access-date>2018-10-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.coindesk.com/gem-philips-blockchain-healthcare/">https://www.coindesk.com/gem-philips-blockchain-healthcare/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Redman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Gem health unveils medical management blockchain platform</article-title>
          <source>Bitcoin</source>
          <year>2016</year>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://news.bitcoin.com/gem-health-blockchain-medical-mgmt/">https://news.bitcoin.com/gem-health-blockchain-medical-mgmt/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shieber</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Gem looks to CDC and European giant Tieto to take blockchain into healthcare</article-title>
          <source>TechCrunch</source>
          <year>2017</year>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://techcrunch.com/2017/09/25/gem-looks-to-cdc-and-european-giant-tieto-to-take-blockchain-into-healthcare/">https://techcrunch.com/2017/09/25/gem-looks-to-cdc-and-european-giant-tieto-to-take-blockchain-into-healthcare/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Albeyatti</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Whitepaper</article-title>
          <source>MedicalChain</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medicalchain.com/en/whitepaper/">https://medicalchain.com/en/whitepaper/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
          <article-title>Blockchain for electronic health records</article-title>
          <source>MedicalChain</source>
          <access-date>2019-02-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medicalchain.com/en/">https://medicalchain.com/en/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <article-title>Rebuilding healthcare for the next generation</article-title>
          <source>Citizen Health</source>
          <access-date>2018-11-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://citizenhealth.io/">https://citizenhealth.io/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <article-title>Humantiv</article-title>
          <source>A Citizen Health Development</source>
          <access-date>2018-11-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://citizenhealth.io/humantiv/">https://citizenhealth.io/humantiv/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <article-title>Medoplex</article-title>
          <source>Citizen Health</source>
          <access-date>2018-11-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://citizenhealth.io/medoplex/">https://citizenhealth.io/medoplex/</ext-link>
          </comment>
        </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>Siwicki</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The next big thing in pharmacy supply chain: Blockchain</article-title>
          <source>Healthcare IT News</source>
          <year>2017</year>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthcareitnews.com/news/next-big-thing-pharmacy-supply-chain-blockchain">https://www.healthcareitnews.com/news/next-big-thing-pharmacy-supply-chain-blockchain</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <source>Block Verify</source>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://true.global/startups/blockverify/#:~:text=Blockverify%20is%20a%20blockchain%2Dbased,%2C%20apparel%2C%20electronics%20and%20pharmaceuticals">https://true.global/startups/blockverify/#:~:text=Blockverify%20is%20a%20blockchain%2Dbased,%2C%20apparel%2C%20electronics%20and%20pharmaceuticals</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hulseapple</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Block verify uses blockchains to end counterfeiting and ‘make world more honest’</article-title>
          <source>Cointelegraph</source>
          <year>2015</year>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cointelegraph.com/news/block-verify-uses-blockchains-to-end-counterfeiting-and-make-world-more-honest">https://cointelegraph.com/news/block-verify-uses-blockchains-to-end-counterfeiting-and-make-world-more-honest</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>De</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Pharma giant merck eyes blockchain for fighting counterfeit meds</article-title>
          <source>CoinDesk</source>
          <year>2018</year>
          <access-date>2018-11-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.coindesk.com/merck-proposes-blockchain-platform-for-combat-counterfeiters/">https://www.coindesk.com/merck-proposes-blockchain-platform-for-combat-counterfeiters/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haring</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <source>BlockTribune</source>
          <access-date>2018-11-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blocktribune.com/blockchain-patent-filed-by-pharmaceutical-giant-merck-co/">https://blocktribune.com/blockchain-patent-filed-by-pharmaceutical-giant-merck-co/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <source>Modum</source>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://modum.io/">https://modum.io/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
          <article-title>Products</article-title>
          <source>Modum</source>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.modum.io/solutions">https://www.modum.io/solutions</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>Data integrity for supply chain operations, powered by blockchain technology</article-title>
          <source>Modum</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://assets.modum.io/wp-content/uploads/2017/08/modum-whitepaper-v.-1.0.pdf">https://assets.modum.io/wp-content/uploads/2017/08/modum-whitepaper-v.-1.0.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Uhlmann</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Reducing counterfeit products with blockchains</article-title>
          <source>University of Zurich</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.merlin.uzh.ch/contributionDocument/download/10024">https://www.merlin.uzh.ch/contributionDocument/download/10024</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stanley</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Ready to rumble: IBM launches food trust blockchain for commercial use</article-title>
          <source>Forbes</source>
          <year>2018</year>
          <access-date>2018-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.forbes.com/sites/astanley/2018/10/08/ready-to-rumble-ibm-launches-food-trust-blockchain-for-commercial-use/#68bf18817439">https://www.forbes.com/sites/astanley/2018/10/08/ready-to-rumble-ibm-launches-food-trust-blockchain-for-commercial-use/#68bf18817439</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="web">
          <article-title>IBM food trust expands blockchain network to foster a safer, more transparent and efficient global food system</article-title>
          <source>IBM News Room</source>
          <access-date>2018-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://newsroom.ibm.com/2018-10-08-IBM-Food-Trust-Expands-Blockchain-Network-to-Foster-a-Safer-More-Transparent-and-Efficient-Global-Food-System-1">https://newsroom.ibm.com/2018-10-08-IBM-Food-Trust-Expands-Blockchain-Network-to-Foster-a-Safer-More-Transparent-and-Efficient-Global-Food-System-1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
          <source>IBM Food Trust: a new era for the world’s food supply</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ibm.com/blockchain/solutions/food-trust">https://www.ibm.com/blockchain/solutions/food-trust</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <article-title>Walmart's food safety solution using IBM food trust built on the IBM blockchain platform</article-title>
          <source>IBM Blockchain</source>
          <year>2017</year>
          <access-date>2018-09-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?time_continue=173&#38;v=SV0KXBxSoio">https://www.youtube.com/watch?time_continue=173&#38;v=SV0KXBxSoio</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huillet</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Alibaba's Ant Financial to launch blockchain backend-as-a-service platform</article-title>
          <source>Cointelegraph</source>
          <year>2018</year>
          <access-date>2018-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cointelegraph.com/news/alibabas-ant-financial-to-launch-blockchain-backend-as-a-service-platform">https://cointelegraph.com/news/alibabas-ant-financial-to-launch-blockchain-backend-as-a-service-platform</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Ant Financial is launching a blockchain app to tackle food fraud</article-title>
          <source>CoinDesk</source>
          <year>2018</year>
          <access-date>2018-09-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.coindesk.com/ant-financial-is-launching-a-blockchain-app-to-tackle-food-fraud/">https://www.coindesk.com/ant-financial-is-launching-a-blockchain-app-to-tackle-food-fraud/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="web">
          <article-title>DokChain</article-title>
          <source>PokitDok</source>
          <access-date>2018-09-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pokitdok.com/dokchain/">https://pokitdok.com/dokchain/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>WB</given-names>
            </name>
          </person-group>
          <article-title>DokChain: intelligent automation in healthcare transaction processing</article-title>
          <source>PokitDok</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pokitdok.com/wp-content/uploads/2018/02/DokChain_Whitepaper.pdf">https://pokitdok.com/wp-content/uploads/2018/02/DokChain_Whitepaper.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brennan</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>DokChain by PokitDok – blockchain for healthcare</article-title>
          <source>Blockchain Healthcare Review</source>
          <access-date>2018-10-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blockchainhealthcarereview.com/dokchain-by-pokitdoc-blockchain-for-healthcare/">https://blockchainhealthcarereview.com/dokchain-by-pokitdoc-blockchain-for-healthcare/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="web">
          <article-title>Healthcare claims processing software</article-title>
          <source>PokitDok</source>
          <access-date>2018-10-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pokitdok.com/business/claims-management/">https://pokitdok.com/business/claims-management/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="web">
          <article-title>Autonomous Auto-Adjudication 101: blockchains in healthcare</article-title>
          <source>Pokitdok</source>
          <access-date>2018-10-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://techcrunch.com/2017/05/10/pokitdok-teams-with-intel-on-healthcare-blockchain-solution/">https://techcrunch.com/2017/05/10/pokitdok-teams-with-intel-on-healthcare-blockchain-solution/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="web">
          <article-title>Healthcare propensity to pay</article-title>
          <source>PokitDok</source>
          <access-date>2018-10-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pokitdok.com/business/payment-risk/">https://pokitdok.com/business/payment-risk/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="web">
          <article-title>Patient access solutions</article-title>
          <source>PokitDok</source>
          <access-date>2018-10-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pokitdok.com/business/patient-access-solutions/">https://pokitdok.com/business/patient-access-solutions/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="web">
          <article-title>Healthcare reimbursement solutions - hospital payment systems</article-title>
          <source>Payspan</source>
          <access-date>2018-11-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://payspan.com/">https://payspan.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="web">
          <article-title>How blockchain can connect payers, providers and consumers</article-title>
          <source>Payspan</source>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://payspan.com/wp-content/uploads/2018/02/Payspan-white-paper-February-2018.pdf">https://payspan.com/wp-content/uploads/2018/02/Payspan-white-paper-February-2018.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="web">
          <source>Nebula Genomics</source>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nebula.org/">https://www.nebula.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="web">
          <source>LunaDNA : frequently asked questions</source>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://support.lunadna.com/support/solutions/articles/43000038763-what-is-lunadna-">https://support.lunadna.com/support/solutions/articles/43000038763-what-is-lunadna-</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="web">
          <source>About LunaDNA - learn more about the LunaDNA team company</source>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.lunadna.com/what-we-do/">https://www.lunadna.com/what-we-do/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="web">
          <article-title>Interview with Luna DNA's Co-Founder and President Dawn Barry</article-title>
          <source>SanDiegOmics</source>
          <year>2018</year>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://sandiegomics.com/luna-dna-interview-with-co-founder-dawn-barry/">https://sandiegomics.com/luna-dna-interview-with-co-founder-dawn-barry/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bigelow</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Luna DNA uses blockchain to share genomic data as a “Public Benefit”</article-title>
          <source>Xconomy</source>
          <year>2018</year>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://xconomy.com/san-diego/2018/01/22/luna-dna-uses-blockchain-to-share-genomic-data-as-a-public-benefit/">https://xconomy.com/san-diego/2018/01/22/luna-dna-uses-blockchain-to-share-genomic-data-as-a-public-benefit/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Farr</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Levy</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Luna Coin project: sell your genetic data for crypto tokens</article-title>
          <source>CNBC Tech</source>
          <year>2017</year>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnbc.com/2017/12/18/luna-coin-project-sell-your-genetic-data-for-crypto-tokens.html">https://www.cnbc.com/2017/12/18/luna-coin-project-sell-your-genetic-data-for-crypto-tokens.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="web">
          <article-title>Project SHIVOM (Official Video) - powering the next era of genomics through blockchain</article-title>
          <source>Shivom</source>
          <year>2018</year>
          <access-date>2018-11-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?v=jce9vB5zbps">https://www.youtube.com/watch?v=jce9vB5zbps</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="web">
          <source>Shivom</source>
          <access-date>2018-11-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://shivom.io/">https://shivom.io/</ext-link>
          </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>Thrill</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Shivom: the uncanny synergy of blockchain and genomics</article-title>
          <source>Hacker Noon</source>
          <year>2018</year>
          <access-date>2018-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hackernoon.com/shivom-the-uncanny-synergy-of-blockchain-and-genomics-e1ca7f2a0173">https://hackernoon.com/shivom-the-uncanny-synergy-of-blockchain-and-genomics-e1ca7f2a0173</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="web">
          <article-title>Shivom innovation council</article-title>
          <source>Shivom</source>
          <access-date>2018-11-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?v=NuaOV82kCjc">https://www.youtube.com/watch?v=NuaOV82kCjc</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="web">
          <source>Zenome</source>
          <access-date>2018-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://zenome.io/">https://zenome.io/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kulemin</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Popov</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gorbachev</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The Zenome Project: whitepaper blockchain-based genomic ecosystem</article-title>
          <source>Zenome.io</source>
          <year>2017</year>
          <fpage>A</fpage>
          <pub-id pub-id-type="doi">10.13140/RG.2.2.25865.13925</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thrill</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>EncrypGen uses blockchain technology to store and manage DNA profiles</article-title>
          <source>Hacker Noon</source>
          <access-date>2018-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hackernoon.com/encrypgen-uses-blockchain-technology-to-store-and-manage-dna-profiles-a920e898b6a8">https://hackernoon.com/encrypgen-uses-blockchain-technology-to-store-and-manage-dna-profiles-a920e898b6a8</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="web">
          <article-title>Gene-chain DNA data marketplace</article-title>
          <source>EncrypGen</source>
          <access-date>2018-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://encrypgen.com/encrypgen-gene-chain-dna-data-marketplace/">https://encrypgen.com/encrypgen-gene-chain-dna-data-marketplace/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="web">
          <article-title>Marketplace partners</article-title>
          <source>EncrypGen</source>
          <access-date>2018-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://encrypgen.com/marketplace-partners/">https://encrypgen.com/marketplace-partners/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="web">
          <article-title>The DNA data marketplace</article-title>
          <source>EncrypGen</source>
          <access-date>2018-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://encrypgen.com/">https://encrypgen.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="web">
          <article-title>S Korea’s Macrogen to leverage blockchain for genomic data</article-title>
          <source>Cryptovest</source>
          <year>2018</year>
          <access-date>2018-10-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.investing.com/news/cryptocurrency-news/s-koreas-macrogen-to-leverage-blockchain-for-genomic-data-1562879">https://www.investing.com/news/cryptocurrency-news/s-koreas-macrogen-to-leverage-blockchain-for-genomic-data-1562879</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Say</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Macrogen develops blockchain platform to share genetic data</article-title>
          <source>Blockonomi</source>
          <year>2018</year>
          <access-date>2018-10-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blockonomi.com/macrogen-blockchain/">https://blockonomi.com/macrogen-blockchain/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ji-young</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Korea’s Macrogen, Bigster to create blockchain-based medical data platform</article-title>
          <source>The Korea Herald</source>
          <year>2018</year>
          <access-date>2018-10-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.koreaherald.com/view.php?ud=20180806000646">http://www.koreaherald.com/view.php?ud=20180806000646</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="web">
          <article-title>Hu-manity.co collaborates with IBM blockchain on consumer app to manage personal data property rights</article-title>
          <source>IBM Announcements</source>
          <year>2018</year>
          <access-date>2020-05-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://newsroom.ibm.com/2018-09-06-Hu-manity-co-Collaborates-with-IBM-Blockchain-on-Consumer-App-to-Manage-Personal-Data-Property-Rights">https://newsroom.ibm.com/2018-09-06-Hu-manity-co-Collaborates-with-IBM-Blockchain-on-Consumer-App-to-Manage-Personal-Data-Property-Rights</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Takahashi</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Hu-manity.co uses IBM blockchain to give you the right to control your personal data</article-title>
          <source>VentureBeat</source>
          <access-date>2020-05-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://venturebeat.com/2018/09/06/hu-manity-co-uses-ibm-blockchain-to-give-you-the-right-to-control-your-personal-data/">https://venturebeat.com/2018/09/06/hu-manity-co-uses-ibm-blockchain-to-give-you-the-right-to-control-your-personal-data/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alexandre</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>New Bitfury joint project to manage medical data permissions with blockchain tech</article-title>
          <source>Cointelegraph</source>
          <year>2019</year>
          <access-date>2020-05-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cointelegraph.com/news/new-bitfury-joint-project-to-manage-medical-data-permissions-with-blockchain-tech">https://cointelegraph.com/news/new-bitfury-joint-project-to-manage-medical-data-permissions-with-blockchain-tech</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="web">
          <article-title>Bitfury announces blockchain-based consent management system; partners with Hancom to distribute Crystal platform</article-title>
          <source>TokenPost</source>
          <year>2019</year>
          <access-date>2020-05-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tokenpost.com/Bitfury-announces-blockchain-based-consent-management-system-partners-with-Hancom-to-distribute-Crystal-platform-1603">https://tokenpost.com/Bitfury-announces-blockchain-based-consent-management-system-partners-with-Hancom-to-distribute-Crystal-platform-1603</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="web">
          <source>HealthVerity consent</source>
          <access-date>2020-05-21</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://healthverity.com/solutions/healthverity-consent/">https://healthverity.com/solutions/healthverity-consent/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hern</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Google's DeepMind plans bitcoin-style health record tracking for hospitals</article-title>
          <source>The Guardian</source>
          <year>2017</year>
          <access-date>2018-09-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.theguardian.com/technology/2017/mar/09/google-deepmind-health-records-tracking-blockchain-nhs-hospitals">https://www.theguardian.com/technology/2017/mar/09/google-deepmind-health-records-tracking-blockchain-nhs-hospitals</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Suleyman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Laurie</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Trust, confidence and verifiable data audit</article-title>
          <source>DeepMind</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://deepmind.com/blog/trust-confidence-verifiable-data-audit/">https://deepmind.com/blog/trust-confidence-verifiable-data-audit/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="web">
          <source>DeepMind</source>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://deepmind.com/">https://deepmind.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metz</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Google DeepMind's untrendy play to make the blockchain actually useful</article-title>
          <source>Wired</source>
          <year>2017</year>
          <access-date>2018-09-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.wired.com/2017/03/google-deepminds-untrendy-blockchain-play-make-actually-useful/">https://www.wired.com/2017/03/google-deepminds-untrendy-blockchain-play-make-actually-useful/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Powles</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hodson</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Google DeepMind and healthcare in an age of algorithms</article-title>
          <source>Health Technol (Berl)</source>
          <year>2017</year>
          <month>3</month>
          <day>16</day>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>351</fpage>
          <lpage>67</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29308344"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12553-017-0179-1</pub-id>
          <pub-id pub-id-type="medline">29308344</pub-id>
          <pub-id pub-id-type="pii">179</pub-id>
          <pub-id pub-id-type="pmcid">PMC5741783</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref99">
        <label>99</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maslove</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Brohman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Using blockchain technology to manage clinical trials data: a proof-of-concept study</article-title>
          <source>JMIR Med Inform</source>
          <year>2018</year>
          <month>12</month>
          <day>21</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e11949</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2018/4/e11949/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11949</pub-id>
          <pub-id pub-id-type="medline">30578196</pub-id>
          <pub-id pub-id-type="pii">v6i4e11949</pub-id>
          <pub-id pub-id-type="pmcid">PMC6320404</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wiljer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brudnicki</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Bringing blockchain to healthcare for a new view on data</article-title>
          <source>IBM Think Blog</source>
          <year>2019</year>
          <access-date>2020-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ibm.com/blogs/think/2019/08/bringing-blockchain-to-healthcare-for-a-new-view-on-data/">https://www.ibm.com/blogs/think/2019/08/bringing-blockchain-to-healthcare-for-a-new-view-on-data/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="web">
          <article-title>Canadian hospital collaborates with IBM for health consent blockchain</article-title>
          <source>Ledger Insights</source>
          <year>2020</year>
          <access-date>2020-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ledgerinsights.com/health-consent-blockchain-university-health-network-uhn/">https://www.ledgerinsights.com/health-consent-blockchain-university-health-network-uhn/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Clinician engagement, local impact awards, budget risk meetings and beyond</article-title>
          <source>University Health Network</source>
          <year>2019</year>
          <access-date>2020-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.uhn.ca/corporate/AboutUHN/Updates_from_CEO/Pages/Clinician_engagement_Local_Impact_Awards_budget_risk_meetings_and_beyond.aspx">https://www.uhn.ca/corporate/AboutUHN/Updates_from_CEO/Pages/Clinician_engagement_Local_Impact_Awards_budget_risk_meetings_and_beyond.aspx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velmovitsky</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Morita</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Blockchain platform for consent management in ambient assisted living</article-title>
          <source>AAL Forum Poster Presentations</source>
          <year>2019</year>
          <access-date>2020-05-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.aalforum.eu/about/poster-presentations-aal-forum-2019/">https://www.aalforum.eu/about/poster-presentations-aal-forum-2019/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guegan</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Public blockchain versus private blockhain</article-title>
          <source>HAL Archives-Ouvertes</source>
          <year>2017</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://halshs.archives-ouvertes.fr/halshs-01524440/document">https://halshs.archives-ouvertes.fr/halshs-01524440/document</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dias</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>HS</given-names>
            </name>
            <name name-style="western">
              <surname>Martins</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based scheme for access control in e-health scenarios</article-title>
          <source>Proceedings of the Tenth International Conference on Soft Computing and Pattern Recognition (SoCPaR 2018)</source>
          <year>2018</year>
          <publisher-loc>Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>238</fpage>
          <lpage>247</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abouelmehdi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Beni-Hssane</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khaloufi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Saadi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Big data security and privacy in healthcare: a review</article-title>
          <source>Procedia Comp Sci</source>
          <year>2017</year>
          <volume>113</volume>
          <fpage>73</fpage>
          <lpage>80</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2017.08.292</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="web">
          <article-title>Blockchain's healthcare technology impact</article-title>
          <source>Cognizant</source>
          <access-date>2018-11-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://soundcloud.com/cognizant-worldwide/impact-of-blockchain-technology-on-healthcare-codex2937">https://soundcloud.com/cognizant-worldwide/impact-of-blockchain-technology-on-healthcare-codex2937</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gorenflo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Golab</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Keshav</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Mitigating trust issues in electric vehicle charging using a blockchain</article-title>
          <source>Proceedings of the Tenth ACM International Conference on Future Energy Systems</source>
          <year>2019</year>
          <conf-name>e-Energy '19: The Tenth ACM International Conference on Future Energy Systems</conf-name>
          <conf-date>June, 2019</conf-date>
          <conf-loc>Phoenix AZ USA</conf-loc>
          <fpage>160</fpage>
          <lpage>164</lpage>
          <pub-id pub-id-type="doi">10.1145/3307772.3328283</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="web">
          <article-title>Electronic health records</article-title>
          <source>Canada Health Infoway</source>
          <access-date>2018-09-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.infoway-inforoute.ca/en/solutions/digital-health-foundation/electronic-health-records">https://www.infoway-inforoute.ca/en/solutions/digital-health-foundation/electronic-health-records</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Blockchain: the magic pill to alleviate the pain points of the healthcare industry?</article-title>
          <source>France Canada Chamber of Commerce Ontario</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fccco.org/post/blockchain-in-healthcare">https://www.fccco.org/post/blockchain-in-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velmovitsky</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Miranda</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Fadrique</surname>
              <given-names>LX</given-names>
            </name>
            <name name-style="western">
              <surname>Morita</surname>
              <given-names>PP</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in health care</article-title>
          <source>CSA Group Report</source>
          <year>2021</year>
          <access-date>2021-04-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.csagroup.org/article/research/blockchain-in-health-care/">https://www.csagroup.org/article/research/blockchain-in-health-care/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref112">
        <label>112</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stanley</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Better off abroad? Blockchain health firms gain ground outside the US</article-title>
          <source>CoinDesk</source>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.coindesk.com/better-off-abroad-blockchain-health-firms-are-gaining-ground-outside-the-us/">https://www.coindesk.com/better-off-abroad-blockchain-health-firms-are-gaining-ground-outside-the-us/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref113">
        <label>113</label>
        <nlm-citation citation-type="web">
          <article-title>Tieto establishes a blockchain pilot program in the Nordics – introduces a global identity network for secure digital interactions</article-title>
          <source>Tietoevry Newsroom</source>
          <access-date>2018-10-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tietoevry.com/en/newsroom/all-news-and-releases/press-releases/2017/11/tieto-establishes-a-blockchain-pilot-program-in-the-nordics--introduces-a-global-identity-network-for-secure-digital-in/">https://www.tietoevry.com/en/newsroom/all-news-and-releases/press-releases/2017/11/tieto-establishes-a-blockchain-pilot-program-in-the-nordics--introduces-a-global-identity-network-for-secure-digital-in/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref114">
        <label>114</label>
        <nlm-citation citation-type="web">
          <source>ICO alert report: BlockRx</source>
          <access-date>2018-11-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blog.icoalert.com/ico-alert-report-blockrx">https://blog.icoalert.com/ico-alert-report-blockrx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref115">
        <label>115</label>
        <nlm-citation citation-type="web">
          <article-title>Drug Supply Chain Security Act (DSCSA)</article-title>
          <source>US Food &#38; Drug Administration</source>
          <access-date>2020-02-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/drugs/drug-supply-chain-integrity/drug-supply-chain-security-act-dscsa">https://www.fda.gov/drugs/drug-supply-chain-integrity/drug-supply-chain-security-act-dscsa</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref116">
        <label>116</label>
        <nlm-citation citation-type="web">
          <article-title>The Drug Supply Chain Security Act and Blockchain : a white paper for stakeholders in the pharmaceutical supply chain</article-title>
          <source>Center for Supply Chain Studies</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://static1.squarespace.com/static/563240cae4b056714fc21c26/t/5b3426b088251b230ba9e6e5/1530144436146/C4SCS+White+Paper_+DSCSA+and+Blockchain+Study_FINAL3.pdf">https://static1.squarespace.com/static/563240cae4b056714fc21c26/t/5b3426b088251b230ba9e6e5/1530144436146/C4SCS+White+Paper_+DSCSA+and+Blockchain+Study_FINAL3.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="web">
          <article-title>Building block(chain)s for a better planet</article-title>
          <source>PwC Global</source>
          <year>2018</year>
          <access-date>2021-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pwc.com/gx/en/services/sustainability/building-blockchains-for-the-earth.html">https://www.pwc.com/gx/en/services/sustainability/building-blockchains-for-the-earth.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="web">
          <article-title>What is a gene?</article-title>
          <source>MedlinePlus</source>
          <access-date>2020-05-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ghr.nlm.nih.gov/primer/basics/gene">https://ghr.nlm.nih.gov/primer/basics/gene</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ferguson</surname>
              <given-names>GK</given-names>
            </name>
          </person-group>
          <article-title>Primer</article-title>
          <source>The Human Genome:  Poems on the Book of Life</source>
          <access-date>2020-05-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thehumangenome.co.uk/THE_HUMAN_GENOME/Primer.html">http://www.thehumangenome.co.uk/THE_HUMAN_GENOME/Primer.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref120">
        <label>120</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barry</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>There is nothing more personal than your genome</article-title>
          <source>Tedx Talks</source>
          <year>2016</year>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?v=M3SLHhWYxiY">https://www.youtube.com/watch?v=M3SLHhWYxiY</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="web">
          <article-title>Nebula genomics - platform overview</article-title>
          <source>Vimeo</source>
          <access-date>2018-11-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://vimeo.com/287152656">https://vimeo.com/287152656</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Precision medicine: opportunities, possibilities, and challenges for patients and providers</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>07</month>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>787</fpage>
          <lpage>90</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv215</pub-id>
          <pub-id pub-id-type="medline">26977101</pub-id>
          <pub-id pub-id-type="pii">ocv215</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khoury</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>The shift from personalized medicine to precision medicine and precision public health: words matter!</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <year>2016</year>
          <access-date>2019-08-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blogs.cdc.gov/genomics/2016/04/21/shift/">https://blogs.cdc.gov/genomics/2016/04/21/shift/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref124">
        <label>124</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Benke</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Benke</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Artificial Intelligence and Big Data in Public Health</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2018</year>
          <month>12</month>
          <day>10</day>
          <volume>15</volume>
          <issue>12</issue>
          <fpage>2796</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph15122796"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph15122796</pub-id>
          <pub-id pub-id-type="medline">30544648</pub-id>
          <pub-id pub-id-type="pii">ijerph15122796</pub-id>
          <pub-id pub-id-type="pmcid">PMC6313588</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barney</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Antisdel</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Common problems in informed consent</article-title>
          <source>Yale University</source>
          <year>2013</year>
          <access-date>2021-05-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://your.yale.edu/policies-procedures/other/common-problems-informed-consent">https://your.yale.edu/policies-procedures/other/common-problems-informed-consent</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Novitzky</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Smeaton</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Irving</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jacquemard</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brolcháin</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>O'Mathúna</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gordijn</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A review of contemporary work on the ethics of ambient assisted living technologies for people with dementia</article-title>
          <source>Sci Eng Ethics</source>
          <year>2015</year>
          <month>06</month>
          <day>19</day>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>707</fpage>
          <lpage>65</lpage>
          <pub-id pub-id-type="doi">10.1007/s11948-014-9552-x</pub-id>
          <pub-id pub-id-type="medline">24942810</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Informed consent in clinical research: revisiting few concepts and areas</article-title>
          <source>Perspect Clin Res</source>
          <year>2013</year>
          <month>01</month>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>26</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.picronline.org/article.asp?issn=2229-3485;year=2013;volume=4;issue=1;spage=26;epage=32;aulast=Gupta"/>
          </comment>
          <pub-id pub-id-type="doi">10.4103/2229-3485.106373</pub-id>
          <pub-id pub-id-type="medline">23533976</pub-id>
          <pub-id pub-id-type="pii">PCR-4-26</pub-id>
          <pub-id pub-id-type="pmcid">PMC3601699</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref128">
        <label>128</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morgan-Linnell</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kurzrock</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>U.S. Food and Drug Administration Inspections of Clinical Investigators: overview of results from 1977 to 2009</article-title>
          <source>Clin Cancer Res</source>
          <year>2014</year>
          <month>04</month>
          <day>15</day>
          <volume>20</volume>
          <issue>13</issue>
          <fpage>3364</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.1158/1078-0432.ccr-13-3206</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref129">
        <label>129</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velmovitsky</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Miranda</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Vaillancourt</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Donovska</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Teague</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Morita</surname>
              <given-names>PP</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based consent platform for active assisted living: modeling study and conceptual framework</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>12</month>
          <day>04</day>
          <volume>22</volume>
          <issue>12</issue>
          <fpage>e20832</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/12/e20832/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/20832</pub-id>
          <pub-id pub-id-type="medline">33275111</pub-id>
          <pub-id pub-id-type="pii">v22i12e20832</pub-id>
          <pub-id pub-id-type="pmcid">PMC7748951</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref130">
        <label>130</label>
        <nlm-citation citation-type="web">
          <article-title>Art. 17 GDPR : right to erasure (‘right to be forgotten’)</article-title>
          <source>General Data Protection Regulation (GDPR)</source>
          <access-date>2021-04-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/art-17-gdpr/">https://gdpr-info.eu/art-17-gdpr/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref131">
        <label>131</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Compert</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Luinetti</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Portier</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Blockchain and GDPR: how blockchain could address five areas associated with GDPR compliance</article-title>
          <source>IBM Security</source>
          <year>2018</year>
          <access-date>2021-05-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://iapp.org/media/pdf/resource_center/blockchain_and_gdpr.pdf">https://iapp.org/media/pdf/resource_center/blockchain_and_gdpr.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref132">
        <label>132</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Na</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Is blockchain technology suitable for managing personal health records? Mixed-methods study to test feasibility</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>08</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12533</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/2/e12533/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12533</pub-id>
          <pub-id pub-id-type="medline">30735142</pub-id>
          <pub-id pub-id-type="pii">v21i2e12533</pub-id>
          <pub-id pub-id-type="pmcid">PMC6384539</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
