<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v23i12e24109</article-id>
      <article-id pub-id-type="pmid">34932009</article-id>
      <article-id pub-id-type="doi">10.2196/24109</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>The Health Care Sector’s Experience of Blockchain: A Cross-disciplinary Investigation of Its Real Transformative Potential</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Martin</surname>
            <given-names>Lea</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Prasser</surname>
            <given-names>Fabian</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mircheva</surname>
            <given-names>Iskra</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Yeung</surname>
            <given-names>Karen</given-names>
          </name>
          <degrees>BComm, BCL, LLB, DPhil</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Birmingham Law School and School of Computer Science</institution>
            <institution>University of Birmingham</institution>
            <addr-line>Edgbaston</addr-line>
            <addr-line>Birmingham, B15 2TT</addr-line>
            <country>United Kingdom</country>
            <phone>44 0121 414 3344</phone>
            <email>k.yeung@bham.ac.uk</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9241-8134</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Birmingham Law School and School of Computer Science</institution>
        <institution>University of Birmingham</institution>
        <addr-line>Birmingham</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Karen Yeung <email>k.yeung@bham.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>12</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>20</day>
        <month>12</month>
        <year>2021</year>
      </pub-date>
      <volume>23</volume>
      <issue>12</issue>
      <elocation-id>e24109</elocation-id>
      <history>
        <date date-type="received">
          <day>4</day>
          <month>9</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>14</day>
          <month>11</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>16</day>
          <month>3</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>3</day>
          <month>4</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Karen Yeung. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 20.12.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2021/12/e24109" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Academic literature highlights blockchain’s potential to transform health care, particularly by seamlessly and securely integrating existing <italic>data silos</italic> while enabling patients to exercise automated, fine-grained control over access to their electronic health records. However, no serious scholarly attempt has been made to assess how these technologies have <italic>in fact</italic> been applied to real-world health care contexts.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The primary aim of this paper is to assess whether blockchain’s theoretical potential to deliver transformative benefits to health care is likely to become a reality by undertaking a critical investigation of the health care sector’s actual experience of blockchain technologies to date.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>This mixed methods study entailed a series of iterative, in-depth, theoretically oriented, desk-based investigations and 2 focus group investigations. It builds on the findings of a companion research study documenting real-world engagement with blockchain technologies in health care. Data were sourced from academic and gray literature from multiple disciplinary perspectives concerned with the configuration, design, and functionality of blockchain technologies. The analysis proceeded in 3 stages. First, it undertook a qualitative investigation of observed patterns of blockchain for health care engagement to identify the application domains, data-sharing problems, and the challenges encountered to date. Second, it critically compared these experiences with claims about blockchain’s potential benefits in health care. Third, it developed a theoretical account of challenges that arise in implementing blockchain in health care contexts, thus providing a firmer foundation for appraising its future prospects in health care.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Health care organizations have actively experimented with blockchain technologies since 2016 and have demonstrated proof of concept for several applications (<italic>use cases</italic>) primarily concerned with administrative data and to facilitate medical research by enabling algorithmic models to be trained on multiple disparately located sets of patient data in a secure, privacy-preserving manner. However, blockchain technology is yet to be implemented at scale in health care, remaining largely in its infancy. These early experiences have demonstrated blockchain’s potential to generate meaningful value to health care by facilitating data sharing between organizations in circumstances where computational trust can overcome a lack of social trust that might otherwise prevent valuable cooperation. Although there are genuine prospects of using blockchain to bring about positive transformations in health care, the successful development of blockchain for health care applications faces a number of very significant, multidimensional, and highly complex challenges. Early experience suggests that blockchain is unlikely to rapidly and radically revolutionize health care.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The successful development of blockchain for health care applications faces numerous significant, multidimensional, and complex challenges that will not be easily overcome, suggesting that blockchain technologies are unlikely to revolutionize health care in the near future.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>blockchain</kwd>
        <kwd>health information management</kwd>
        <kwd>health information systems</kwd>
        <kwd>electronic health record</kwd>
        <kwd>data sharing</kwd>
        <kwd>health services administration</kwd>
        <kwd>privacy of patient data</kwd>
        <kwd>computer security</kwd>
        <kwd>mobile phone</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>In recent years, distributed ledger technologies commonly referred to as <italic>blockchain</italic> have generated considerable interest and excitement across many industries, including health care, supported by claims of their radically disruptive and transformative potential. Academic literature focusing on blockchain’s potential to solve health care problems has proliferated [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. Although scholars have identified many possible applications of blockchain in health care [<xref ref-type="bibr" rid="ref8">8</xref>], blockchain’s perceived value ultimately rests on its potential to create a highly secure, tamper-proof, auditable electronic ledger that can enable responsive, fine-grained, and privacy-respecting access to and sharing of health care data. Accordingly, blockchain is often portrayed as a technological solution that can overcome existing barriers to health information exchange [<xref ref-type="bibr" rid="ref8">8</xref>], one of the most stubborn challenges that continues to plague contemporary health care [<xref ref-type="bibr" rid="ref9">9</xref>]. Blockchain advocates claim that these technologies will generate higher quality, more trustworthy, and readily accessible data, which can drive improvements across health care [<xref ref-type="bibr" rid="ref10">10</xref>]. These improvements would then lead to (1) better quality medical care, including improvements in clinical decision-making and more effective public health management and disease prevention [<xref ref-type="bibr" rid="ref11">11</xref>]; (2) more efficient, cost-effective, and timely health care administration; and (3) improvements in medical and health care research, resulting from more accurate and secure clinical trial data management and storage [<xref ref-type="bibr" rid="ref12">12</xref>]. In particular, many believe blockchain will enable fine-grained, patient-controlled access, sharing, and management of electronic health records (EHRs), thereby overcoming existing problems associated with the current <italic>siloed</italic> approach to the storage and management of patient data, which is often regarded as blockchain’s <italic>favorite use case</italic> for health care [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>].</p>
      </sec>
      <sec>
        <title>The Blockchain for Health Care Promise: Rhetoric or Reality?</title>
        <p>However, expecting blockchain technologies to provide an effective, efficient, patient-centered solution to the multiplicity of problems associated with health care data management and sharing is a tall order. This was one of the expected benefits of EHRs; however, despite their widespread take-up in health care settings, ethically sensitive, lawful, timely, and secure sharing and management of health care data remain a critical but seemingly intractable challenge [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Academic literature concerned with health care applications remains overwhelmingly centered on blockchain’s <italic>potential,</italic> focusing on identifying the possible range of benefits that <italic>could</italic> be delivered. However, no serious scholarly attempt has been made to assess the extent to which these technologies have <italic>in fact</italic> been applied to real-world health care contexts and with what consequences, with little attention paid to real-world implementation challenges [<xref ref-type="bibr" rid="ref17">17</xref>]. In short, academic scholarship remains largely speculative (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]).</p>
      </sec>
      <sec>
        <title>Technical Dimensions of Blockchain Technologies</title>
        <sec>
          <title>Overview</title>
          <p>To identify what blockchain technologies can and cannot realistically deliver, it is necessary to understand what these technologies are and how they function. Although computer security specialists ascribe a particular technical meaning to <italic>blockchain technologies</italic>, they are understood in a much looser, broader sense for the purposes of this study. In this paper, blockchain technologies refer to a time-stamped database, duplicated across a distributed network of computers (each computer in the network is called a <italic>node</italic>), which is configured such that its technical architecture and operation effectively prevent the rewriting and removal of prior entries. At a basic level, blockchains enable a community of users to record transactions (ie, an interaction between parties) in a shared ledger such that, under the normal operation of the blockchain network, no transaction record can be altered once published. These systems can, as the Bitcoin blockchain demonstrates, enable transactions between strangers without the need for a conventional trusted third-party intermediary, such as a bank or government. Instead, transactions between parties with no pre-existing relationship of trust are enabled by 4 key characteristics of blockchain technologies [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        </sec>
        <sec>
          <title>Ledger</title>
          <p>The technology relies on an append-only ledger to provide a complete transactional history, which, because of its technological design, is almost impossible to amend or alter. This differs from a traditional database in which transactions and entries can be altered or overridden.</p>
        </sec>
        <sec>
          <title>Tamper-Proof</title>
          <p>Blockchains use cryptographic methods that rely upon mathematical consensus to confirm the consistency and technical authenticity of each transaction’s digital record, which is then permanently recorded on the ledger and cannot be altered or deleted. The security and accuracy of the ledger are maintained through the use of cryptographic <italic>keys</italic> and signatures that automatically control who can do what with the ledger. If conflicts between different copies of the database arise (eg, because someone is trying to tamper with the data), the automatic consensus mechanism is designed to ensure that only transactions that are consistent with the earlier, stored version of the database are updated and permanently recorded. Distributed ledger systems that take the blockchain form aggregate transactions into <italic>blocks,</italic> and these are added to a <italic>chain</italic> of existing blocks using a cryptographic signature (hence the name <italic>blockchain</italic>). As the data stored on the ledger can be mathematically attested and cannot be tampered with, it is highly secure.</p>
        </sec>
        <sec>
          <title>Shared</title>
          <p>A copy of the ledger is replicated and shared across multiple participating nodes, providing transparency across the node participants in the network.</p>
        </sec>
        <sec>
          <title>Distributed</title>
          <p>As more nodes are added across the network, the ledger becomes increasingly resistant to malicious attacks because it becomes more difficult to interfere with the intended operation of the consensus protocol through which transactions are validated and appended to the ledger. The resilience of the ledger is rooted in its distributed nature. In contrast, conventional databases are based on a centralized, hierarchical design, thus creating a single point of failure.</p>
          <p>Blockchain systems can be designed to operate in many ways because of the malleability of the software and protocols through which they are configured. Blockchains may be <italic>permissionless</italic> or <italic>permissioned</italic>, referring to who is entitled to become a network node. Within permissionless blockchain networks, anyone with a computer that has sufficient computing capacity can download the software and participate in the consensus process, storing and updating the shared ledger (referred to as <italic>write</italic> access) without needing permission to do so. As write access is <italic>open</italic> to all for permissionless blockchains, anyone can also <italic>read</italic> or otherwise inspect the ledger. In contrast, permissioned blockchains restrict write access: only those granted advance permission by the relevant authority within the network can participate in the consensus process through which the shared ledger is updated and stored. For permissioned blockchains, the ability of others to <italic>read</italic> and inspect the ledger may be <italic>open</italic> to anyone or can be restricted or <italic>closed</italic> so that only those with authorized access may read its contents. Permissioned blockchains can provide similar functionality to permissionless blockchains but are considerably less computationally demanding. As participating nodes must first be identified and authorized before joining a permissioned network, this provides an assurance of trust across the network, backed by the threat that write access can be withdrawn from misbehaving nodes. As a result, consensus models applied within permissioned blockchains need not provide the same high levels of mathematical and computational security. Therefore, they offer faster performance and are computationally less expensive [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
          <p>The elasticity and malleability of blockchain systems, including the variety of different forms and functionalities that they can offer, has resulted in considerable variation in the way the term <italic>blockchain</italic> is used, particularly in discussions about blockchain for health care. The very broad definition of blockchain adopted here reflects the health care sector use of the term, encompassing any sociotechnical system that uses a distributed, append-only database that relies on cryptographic methods to verify and validate transactions before they are added to the ledger, including both permissioned and permissionless systems, which include distributed ledger technologies that do not aggregate and store data into linked blocks [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Aims, Objectives, and Research Questions</title>
        <p>The aim of this study is to critically investigate the health care sector’s engagement with blockchain technologies to date, analyzing those experiences from a theoretical, cross-disciplinary perspective to ground a more realistic appraisal of the potential benefits, difficulties, and implications of implementing blockchain in health care settings. This investigation was animated by the following research questions:</p>
        <list list-type="order">
          <list-item>
            <p>To what extent and in what ways have blockchain technologies been taken up in the health care sector?</p>
          </list-item>
          <list-item>
            <p>What are the primary real-world opportunities and challenges that blockchain technology generates in health care contexts?</p>
          </list-item>
          <list-item>
            <p>What are the prospects of blockchain take-up and implementation in health care settings to solve real-world problems in the short to medium term?</p>
          </list-item>
        </list>
        <p>Taken together, these questions can be amalgamated into a single overarching research question: what does health care’s actual experience of blockchain technologies to date reveal about the technologies’ <italic>real</italic> revolutionary potential [<xref ref-type="bibr" rid="ref20">20</xref>]?</p>
        <p>This paper proceeds by outlining the study’s design, data sources, analytic approach, and theoretical foundations. It then sets out its findings by first providing a qualitative overview and explanation of the extent to which blockchain technologies have been taken up in the health care domain. Second, it offers a critical examination of a series of multidimensional challenges, organized thematically, that constitute (or are likely to constitute) very substantial hurdles that must be overcome if blockchain is to be widely taken up in health care settings. Finally, it discusses these challenges in light of the most promising opportunities for generating real value in health care settings and suggests that the use of blockchain to provide fine-grained patient control over medical records is unlikely to live up to its perceived promise.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design and Data Sources</title>
        <p>The mixed methods study reported in this paper forms the major component of a Wellcome Trust–funded cross-disciplinary project aimed at understanding the challenges, risks, opportunities, and experiences of the health care sector in using blockchain technologies. It took the form of a theoretical investigation, building upon the initial research study by Motsi-Omoijiade and Kharlamov [<xref ref-type="bibr" rid="ref21">21</xref>] that sought to identify and map evidence of real-world engagement with blockchain technologies in the health care sector, classifying them according to their context of application (as patient care support, administration, or research data management), level of maturity, and the primary geographic region from which the application appeared to originate. The integrated catalog of health care blockchain applications and use cases created in that study provided a snapshot of the state of health care blockchain take-up on November 30, 2019. It identified 128 <italic>applications</italic>, referring to real-world instances in which blockchain technology has been developed into a commercially viable health-related service created largely from a web-based review of English language websites, gray literature, and academic papers (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]). This study builds on the results of that earlier mapping and classification exercise by drawing on 2 focus group investigations and a series of iterative, in-depth, theoretically oriented desk-based investigations.</p>
      </sec>
      <sec>
        <title>Focus Group Workshops</title>
        <p>The 2 focus group discussions were organized in which a mix of both academic researchers and blockchain-for-health care sector experts participated. The first workshop, hosted at the outset of the project, was designed to generate insights that could inform and guide the direction of the study’s inquiries and help understand the current state of health care sector engagement and experience with blockchain technologies for specific health care purposes. The second workshop occurred toward the end of the study. Its aim was to share the provisional study findings with participants to elicit their critical feedback and provoke discussion. The focus group participants were identified and invited with the aim of bringing wide-ranging, relevant expertise to the discussion, given the project’s aim of adopting a multidisciplinary perspective to address the project’s research questions. This approach to recruitment reflects a belief that technical, legal, ethical, management, clinical care, and health service industry knowledge and experience would be needed to successfully apply blockchain to real-world settings.</p>
        <p>The participant invitation list was compiled from the principal investigator’s existing knowledge of academic experts with existing or related interests in blockchain from several disciplinary backgrounds, combined with a light touch review of recent academic and digital health care industry publications to identify key health care sector experts with direct and ongoing experience in seeking to apply blockchain technologies to health care. This initial list was supplemented by the use of snowball sampling techniques (asking each academic and industry invitee to nominate 1 or 2 colleagues) to identify others with relevant expertise. The specific composition of the workshops differed in light of their different objectives and participant availability: the initial workshop comprised more academics than industry experts, whereas the final workshop was attended predominantly by industry experts relative to academics (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>).</p>
      </sec>
      <sec>
        <title>Desk-Based Review and Theoretical Investigation</title>
        <p>The project’s theoretical, desk-based investigations primarily drew on 2 data sources. First, the investigations drew from a wide variety of academic literature from multiple disciplinary perspectives, including computer science, computer security, digital health, organizational management, operations research, medical law, data protection law, medicine, medical sociology, and innovation studies. Given that relatively little information about health-related blockchain projects is publicized via academic journals [<xref ref-type="bibr" rid="ref29">29</xref>], and existing scholarly literature on blockchain in health care settings has not hitherto been concerned with real-world engagement and experience, relevant academic sources were identified by deductive critical reflection. This entailed developing and refining a series of thematically focused investigations aimed at acquiring a deeper, more fine-grained, cross-disciplinary understanding of the major issues and challenges that would invariably confront those endeavoring to apply blockchain to health care settings. These included matters of data security and integrity, health information technology (IT) implementation, user resistance, internal and external governance, interoperability, organizational management, and data privacy. Second, gray literature (including observations and reflections from those with direct experience of the health sector’s engagement with blockchain to date) provided a vitally important source of insight, given that the published scholarly literature represents only a small snapshot of global blockchain activity. This literature included reflections collected from various informal sources, such as guidance and opinion pieces published in various formats, including essay collections [<xref ref-type="bibr" rid="ref30">30</xref>], blog posts, news articles, newsletters by industry bodies (particularly those published by the Healthcare Information Management and Systems Society [HIMSS]) and key industry experts from organizations offering blockchain for health care consultancy services such as Consensys Health and Hashed Health.</p>
      </sec>
      <sec>
        <title>Analytical Approach</title>
        <p>This study proceeded from the premise that blockchain’s reliance upon cryptographic techniques and networked, distributed computing facilities to provide a highly secure, shared but tamper-proof database means that its foundational value lies in its capacity to facilitate <italic>secure data sharing and collaboration</italic>, particularly between parties in circumstances where a lack of social trust would otherwise inhibit cooperation. So understood, the development, implementation, and scale up of blockchain technologies into health care contexts are likely to pose distinctive and novel challenges because of both its technological design and the health care contexts in which attempts are being made to implement it.</p>
        <p>The analysis proceeded in 3 stages. First, it began by seeking to acquire a deeper, more qualitatively oriented understanding of the observed patterns of blockchain for health care engagement mapped from the Motsi-Omoijiade and Kharlamov [<xref ref-type="bibr" rid="ref21">21</xref>] study. These first-stage inquiries drew heavily on insights and observations contained in industry publications [<xref ref-type="bibr" rid="ref29">29</xref>], government reports, mainstream media, and initial focus group discussions. The resulting analysis produced a clearer, richer, and more nuanced understanding of (1) how blockchain technologies were intended to provide specific functional capacities across a variety of real-world health care contexts; (2) the range of applications, context-domains, and participants who were expected to engage with and those expected to benefit from these applications; (3) how blockchain was expected to address specific data-sharing problems encountered in health care settings; and (4) the wide-ranging and multidimensional difficulties or <italic>challenges</italic> that have been encountered in the course of these engagements to date or that can be expected to arise if those engagements continue to expand and deepen, particularly if they extend into clinical settings.</p>
        <p>The second-stage analysis entailed a critical comparison of the benefits, difficulties, and drawbacks identified in stage 1 against the claims appearing in the academic literature about blockchain’s potential benefits and shortcomings (both generally and those specific to health care). This analysis sought to evaluate these claims, which were focused almost exclusively on the benefits of blockchain, with little mention or consideration of shortcomings, against early-stage experiences with blockchain implementation in real-world health care settings. The resulting mismatch between academic claims and actual experiences of the technology prompted further scrutinization and critical analysis of the implementation problems identified from the first-stage analysis, grouping them together thematically (rather than primarily in relation to specific functional applications or particular kinds of health care data). This grouping was based on recurring difficulties and challenges that have been encountered (or are likely to arise in relation to specific health care applications, particularly those that directly affect clinical practice) in seeking to design, configure, and implement blockchain technologies in health care settings. The encountered challenges were typically multidimensional in character, entailing dynamic interacting and often complex technical, social, regulatory, and organizational difficulties that would need to be addressed successfully before the technology is likely to produce significant value for health care.</p>
        <p>The final stage of analysis sought to develop a more theoretically grounded account of the observations generated at the second stage analysis, drawing upon different fields of scholarship, including academic discussions focused on blockchain’s <italic>revolutionary</italic> potential; the nature, dimensions, and challenges of innovation more generally; and of health IT implementation in particular (including studies of EHR implementation). The aim was to produce an integrated, theoretically informed, cross-disciplinary understanding of the experience of the health care sector’s engagement with blockchain technologies to date, providing a firmer foundation for appraising its prospects by reference to the underlying nature and form of coordination that blockchain technologies currently enable.</p>
      </sec>
      <sec>
        <title>Theoretical Frame</title>
        <p>The theoretical framework for this study draws primarily on 3 different but complementary perspectives that collectively contribute to addressing the project’s overarching research question. First, it draws upon the growing cross-disciplinary literature that has typically emphasized blockchain’s <italic>revolutionary</italic> potential to enable novel forms of social cooperation between strangers without the need for a trusted third-party intermediary. Blockchain’s potential to enable <italic>trustless</italic> cooperation is ultimately attributable to its underlying technological architecture and distributed operation to produce a shared database that is effectively tamper-proof, enabling the replacement of social trust with computational trust in specific contexts. This has prompted some scholars to describe blockchain as a <italic>truth machine</italic> [<xref ref-type="bibr" rid="ref31">31</xref>]. More recently, however, a more skeptical strand of literature has started to emerge, drawing attention to a wide range of reasons why the technology may fail to live up to its promise [<xref ref-type="bibr" rid="ref32">32</xref>]. As these inquiries progressed, it became necessary to look to a wider variety of literature to make sense of these real-world implementation challenges. This led to the investigation of a second body of academic scholarship located within the field of <italic>innovation studies</italic>, a different multidisciplinary strand of work that includes a wide range of industry studies that demonstrate that technologies do not arise in the fully developed form [<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref35">35</xref>]. Instead, they find that a period of considerable confusion usually follows the emergence of a new technological invention, with little agreement about what its major subsystems should be or how it can best be put together as a product or service, resulting in significant experimentation [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        <p>Health care’s current and ongoing engagements with blockchain can be located within this early experimental phase, situated at the entrance to the so-called <italic>valley of death</italic>. This refers to a <italic>gap</italic> between the development of new scientific knowledge and the establishment of proof of concept but before full development and commercialization [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Industry estimates suggest that 4 in 5 new inventions are never commercialized because of their failure to overcome numerous <italic>barriers to innovation</italic> encountered during this crucial development phase [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Innovation studies scholars have identified multiple <italic>valleys of death</italic>, which they have explored from various angles. Some understand the valley primarily as a financing and funding problem that arises after the establishment of a proof of concept. At that moment, significant investment is required to scale up; however, there is considerable technical and commercial uncertainty about its likely success, which thus discourages further investment [<xref ref-type="bibr" rid="ref34">34</xref>]. Occasionally, this leads to various policy prescriptions, such as government funding initiatives and <italic>translational</italic> centers comprising academic and commercial stakeholders, to help bridge the gap [<xref ref-type="bibr" rid="ref42">42</xref>]. Others focus on the difficult transition of university research to a product or service brought to market by a commercial firm, particularly in the case of drug development [<xref ref-type="bibr" rid="ref43">43</xref>].</p>
        <p>For the purposes of examining the prospects of blockchain in health care, the most salient strand of this literature is concerned with identifying the <italic>barriers to innovation</italic> that create and contribute to the valley of death. Scholars have classified these barriers as either <italic>internal</italic> to the organization (including factors such as a restrictive mindset, lack of competence, insufficient resources, and an unsupportive organizational structure) or <italic>external</italic> and thus largely beyond the firm’s direct control (including factors such as a paucity of external finance; resistance or lack of support from specific actors, such as customer resistance or an unsupportive government; and various factors which result in a restrictive macroenvironment, such as an undeveloped network and ecosystem, technological volatility that narrows the window of opportunity during which an innovation can be introduced, inappropriate infrastructure, and a restrictive local culture) [<xref ref-type="bibr" rid="ref44">44</xref>]. However, these largely generic, rather abstract, accounts of various obstacles that must be overcome for technological innovations to largely succeed treat the underlying technology as a <italic>black box</italic> rather than engaging with technological design and specific development challenges in seeking to configure and embed the technology into sector-specific social and organizational systems, processes, and practices [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>].</p>
        <p>Rather than treating blockchain in health care as a closed <italic>black-box</italic>, these theoretical investigations drew upon a third set of analytical lenses situated within academic investigations of health care IT system implementations, particularly studies undertaken from a <italic>social practice</italic> perspective [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref49">49</xref>]. These studies highlight the critical role of context, culture, and the values that are brought to bear by medical professionals in clinical environments, identifying clinical consultation as a complex social encounter that occurs within a heavily institutionalized environment [<xref ref-type="bibr" rid="ref50">50</xref>]. In particular, scholars from these traditions emphasize the role of values in clinicians’ understanding of what constitutes and how they seek to practice <italic>excellent care</italic>. Moreover, they stress the nature of clinical knowledge as <italic>tacit, context bound, and ephemeral rather than codifiable, transferable, and enduring</italic> such that the implementation of health IT into clinical settings often departs substantially from those envisaged by system developers and designers [<xref ref-type="bibr" rid="ref50">50</xref>]. Accordingly, insights of this kind cast significant doubt on the capacity to hard code norms into technological systems in ways that can be seamlessly integrated into clinical environments, especially when these norms concern the sharing of health data, which is typically and legally understood as highly sensitive and worthy of special protection.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>The results of this study are presented in 3 parts, which correspond with the study’s analytical approach outlined in previous sections. First, it briefly describes the health care sector’s engagement with blockchain technologies to date in the United States, United Kingdom, and at the transnational level. Second, it critically reflects upon a series of 6 challenges that must be overcome and 3 normative trade-offs that must be satisfactorily resolved if blockchain technologies are to cross the <italic>valley of death</italic>, transitioning successfully from <italic>invention</italic> to <italic>innovation</italic> in health care settings. Third, it critically discusses key findings by referring to a selection of wider academic literature concerned with organizational cooperation and radical versus incremental technological innovation and reflects upon the promises of patient-controlled blockchain-enabled EHRs before offering some concluding reflections.</p>
      </sec>
      <sec>
        <title>Interrogating Blockchain in Real-world Health Care Contexts</title>
        <p>The Motsi-Omoijiade and Kharlamov study [<xref ref-type="bibr" rid="ref21">21</xref>] revealed that, apart from the Estonian government’s eHealth initiative [<xref ref-type="bibr" rid="ref22">22</xref>], active engagement with blockchain technology in health care began around 2016, primarily in the United States and, to a lesser extent, in Europe, with several recent initiatives occurring at the transnational level. As of November 30, 2019, their study had identified 128 health care blockchain applications (in which a blockchain <italic>application</italic> is defined as providing a specific functional health care purpose so that a single blockchain system might provide multiple applications) from an English-language website review, over half of which were geographically located in the United States (65 applications), with the United Kingdom as the next most popular site of activity (12 applications) [<xref ref-type="bibr" rid="ref21">21</xref>]. However, less than half of these had a commercially available blockchain product or service, with most still at the experimental or development stage. Of these applications, a substantial minority (50/128, 39.1%) focused on applications to enable user-controlled access to some kind of personal health data, with a significant proportion concerned primarily with using blockchain to facilitate health care administration (34/128, 26.6%) and support for patient care or health management (primarily in facilitating remote care consultations between patient and clinician located elsewhere) or in the form of <italic>wellness</italic> applications to encourage healthy behaviors (31/128, 24.2%) and for medical research data management (13/128, 10.2%; <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p>
        <p>A closer examination of the technical and contextual dimensions of these applications and their primary sources of funding revealed that, first, the overwhelming majority of blockchain for health care initiatives had used permissioned or hybrid systems, in which the tasks of sharing and updating the ledger are restricted to those authorized to do so. Second, in both the United States and the United Kingdom, private sector investment and funding have been driving these initiatives, although various government programs support blockchain initiatives, including funding support [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. Although some early initiatives sought to generate funding via an <italic>initial coin offering</italic>, including start-up firms claiming specialist blockchain expertise, these have failed to generate positive returns for investors (and a significant number of initial coin offerings generally were merely vehicles for fraud) [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. More recently, investment funding has been provided by venture capitalists, evidencing their confidence in the technology’s potential value to the health care sector. The commercial and entrepreneurial expertise that they bring to the sector might help the fledgling industry navigate the fraught and uncertain early development phase [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>]. Third, the current and ongoing focus of interest in blockchain for health care, at least in the US context, has been predominantly at the intraorganizational and business-to-business (B2B) level rather than being primarily concerned with clinical care provision. Much of this activity has primarily concerned blockchain systems for managing <italic>nonclinical</italic> data, as health care providers explore the capacity to harness blockchain technologies to enhance administrative and operational efficiency. Fourth, by comparison, the UK health sector’s experience and engagement with blockchain technology has been far more muted, with only a handful of initiatives, all at the pilot or early-stage implementation phase. These initiatives are primarily for patient care management, with very limited reliance on blockchain functionality. Finally, several promising transnational blockchain initiatives to facilitate medical and health research have been launched in recent years. The following discussion briefly outlines the US and UK experiences (as the 2 most active sites of blockchain engagement in health care) and more recent transnational blockchain initiatives.</p>
      </sec>
      <sec>
        <title>The United States</title>
        <p>In the United States, ongoing blockchain activity in health care is coalescing at the intraorganizational and B2B level. These applications are intended to facilitate data sharing between business units within the same umbrella health care organization or within recently established consortia of health care organizations seeking to cooperate in the sharing and management of specific forms of health care data stored via a blockchain-enabled ledger [<xref ref-type="bibr" rid="ref55">55</xref>]. The primary drivers supporting blockchain development to date appear to have focused on its potential to reduce costs and enhance efficiency in health care administration and operations. These applications are broadly concerned with either health care operations management, primarily in the management of supply chains, or administrative data pooling.</p>
        <p>Turning first to health care operations management, considerable blockchain activity has occurred either to streamline and automate internal operational processes or to improve the efficiency and verifiability of supply-chain management [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]. Examples of the former include the Coalesce Health Alliance consortium’s development of blockchain to improve the accuracy and efficiency of patient health care claims management across different entities within the Blue Cross Blue Shield ecosystem [<xref ref-type="bibr" rid="ref57">57</xref>]. Similarly, the US Department of Health’s Office of National Security has built a blockchain providing organizational units with linked, real-time access to a standard set of spend data to improve the department’s procurement process, reportedly generating major efficiency gains [<xref ref-type="bibr" rid="ref58">58</xref>]. In health care supply chain management, significant blockchain activity has occurred to address the potentially serious risks of a compromised health care supply chain [<xref ref-type="bibr" rid="ref56">56</xref>]. The Food and Drug Administration has actively encouraged these applications by launching a pilot project (announced in February 2019) to encourage drug supply chain stakeholders to develop digital systems to comply with the Drug Supply Chain Security Act 2013, which mandates the creation of an electronic, interoperable system that can trace and identify distributed prescription drugs across the United States. It attracted 26 participants (including several pharmaceutical supply chain stakeholders [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]), generating a variety of projects. These include the MediLedger Project, which sought to build a blockchain network around a tamper-proof ledger of pharmaceutical supply-chain transactions to inform responses to product ID verification requests communicated via a permissioned messaging network [<xref ref-type="bibr" rid="ref61">61</xref>]. The Pharmaceutical Utility Network has taken a different approach, pursuing a <italic>platform first</italic> strategy [<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>] rather than focusing on a specific <italic>use case</italic>. It is developing an open-source blockchain platform that integrates regulatory requirements (such as the Drug Supply Chain Security Act) to enable those involved in the pharmaceutical supply chain (including pharmaceutical manufacturers, distributors, dispensers, and software vendors) to use the platform’s services to demonstrate compliance with regulatory requirements, seeking to use blockchain as a form of <italic>RegTech</italic>. [<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref64">64</xref>] Other supply-chain management blockchains in the health care sector focus on single use cases, often with some RegTech functionality, such as the Clinical Supply Blockchain Working Group’s platform [<xref ref-type="bibr" rid="ref65">65</xref>], which is now seeking to apply its blockchain-based inventory and event-tracking system to a real clinical trial [<xref ref-type="bibr" rid="ref66">66</xref>].</p>
        <p>Blockchain applications are also being used to facilitate administrative data pooling at the intra- and interorganizational levels. Health care consortia in the United States began emerging in 2018, seeking to use blockchain either to create a single ledger shared between member organizations to serve as a single source of <italic>truth</italic> or to enable network members to create a shared pool of records to which access is controlled and recorded via the blockchain. For example, the Synaptic Health Alliance [<xref ref-type="bibr" rid="ref67">67</xref>] aims to use a blockchain network to address costs, delays, and inefficiencies in provider directory data (comprising demographic information about physicians and other providers), which insurers are required by federal law to maintain and keep up to date. Each insurer has typically maintained its own directory; however, these often contain inaccurate data, resulting in delayed claims and payment processing. Synaptic’s blockchain pilot seeks to create a common source of <italic>truth</italic> for provider directory data created by pooling and comparing each member’s directory data to create a complete, accurate shared directory.</p>
        <p>Similarly, the Professionals Credentials Exchange (ProCredEx) is a consortium of health care organizations seeking to enhance the efficiency of the physician credentialing process [<xref ref-type="bibr" rid="ref57">57</xref>]. In the United States, when a new physician is hired or begins working for a new payer’s network, the employing health care organization must gather a wide variety of certificates and credentials, a process that takes up to 6 months (sometimes longer), with physicians often required to supply evidence of their professional credentials to a dozen different organizations or more, which must be repeated for all physicians every 2 years by each organization [<xref ref-type="bibr" rid="ref29">29</xref>]. The ProCredEx blockchain network enables organizations to contribute their credentialing records (essentially, a digital asset) to a shared pool, effectively creating a members-only digital asset exchange so that members can access verified credentials and actively contribute credentials information that other members can acquire. The shared ledger tracks asset ownership, exchange, and use and forms a basis for asset reputation. Buyers of these information assets finance the platform, whereas curators of the assets receive payment for their contributions, as do partners who help facilitate the use of the blockchain network [<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>].</p>
      </sec>
      <sec>
        <title>The United Kingdom</title>
        <p>In comparison with its US counterpart, interest in blockchain in UK health care has been considerably more limited [<xref ref-type="bibr" rid="ref70">70</xref>]. The UK blockchain use cases have been directed at patient care management largely outside the clinic, in which secure and auditable data sharing remains the central functionality provided by blockchain technologies. Unlike the United States, UK health care is delivered primarily via a publicly funded National Health Service (NHS), in which NHS hospital treatment and primary care are free at the point of use to UK residents. Decisions about the commissioning of services, including the use of new technologies, are taken primarily at the local level by entities known as clinical commissioning groups or exceptionally at the national level by NHS England, which is informed by guidance issued by the UK’s National Institute for Health and Care Excellence [<xref ref-type="bibr" rid="ref71">71</xref>]. The NHS Long Term Plan states that the NHS will seek to “make better use of data and digital technology” [<xref ref-type="bibr" rid="ref72">72</xref>] as part of the NHS digital transformation agenda; however, it makes no explicit reference to blockchain technologies. However, the NHS England’s Director of Digital Development has been reported as having a general interest in considering blockchain as one of a variety of technologies that the NHS will explore [<xref ref-type="bibr" rid="ref73">73</xref>].</p>
        <p>Nevertheless, NHS England has commissioned Dovetail Labs to develop a novel digital application to enable different members of a multidisciplinary team working with type 2 diabetes patients to share health information. The application operates via a distributed ledger that logs patient consent to share digital data along with user authentication, data access, and transfer records [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>]. In addition, at least two local clinical commissioning groups have commissioned small-scale digital applications that are described as using blockchain technology. Hence, a partnership between Guardtime and Instant Access Medical and Healthcare Gateway has produced a comprehensive blockchain-supported personal care record platform (called <italic>MyPCR</italic>). The platform is intended to assist patients in managing chronic long-term health conditions by issuing digital alerts to help them adhere to their personalized treatment plan or personal care pathway via a smartphone app, granting patients complete access to their personal care pathway while generating an automated tamper-proof record of health data provenance and integrity that is compliant with data protection legislation [<xref ref-type="bibr" rid="ref76">76</xref>]. Similarly, MedicalChain has launched a blockchain pilot enabling patients to create a free wallet to manage access to their digital health records, enable general practitioner video consultations, and enable them to pay for services using cryptocurrency (with users incentivized to pay for telemedicine services with Medicalchain’s MedTokens) [<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref78">78</xref>].</p>
      </sec>
      <sec>
        <title>Transnational Blockchain Systems</title>
        <p>At the transnational level, a rather different kind of blockchain application has emerged, which enables network members to run secure but privacy-preserving computational analyses on the data of other members to improve their algorithmic models for research purposes while the data never leaves the host organization [<xref ref-type="bibr" rid="ref79">79</xref>]. For example, members of the Machine Learning Ledger Orchestration for Drug Discovery blockchain network, comprising 10 large pharmaceutical companies, 5 technical partners, and 2 universities, use blockchain and federated learning to train an algorithm to identify a rare mutation in cancer, enabling pharmaceutical companies to collaborate on therapeutic drug discovery. Each pharmaceutical company can, via the network, run the machine learning algorithms of their academic partners on each other’s data sets. The data remain at their local site so that proprietary information from one data set cannot be leaked to another. Nonsensitive algorithmic models are exchanged between the members, which are then collectively consolidated to improve the predictive performance of the algorithmic models by leveraging all the data across the federation. A permissioned blockchain tracks and logs all operations taking place on the federated data using a software framework (Substra) for enabling the execution of distributed machine learning tasks in a secure way. The value of collaboration is particularly evident in attempts to develop drug treatments for rare diseases: each individual organization will have too few patients with a given rare disease to undertake statistically significant analysis; however, by pooling access to their data to enable federated learning, collaboration without data sharing becomes possible. Similarly, the AI Centre for Value-Based Healthcare consortium has created a federated learning network with patient data from 4 hospitals and 3 universities, allowing research partners to train algorithms on the federated data set. Collaborations of this kind, which use blockchain networks to facilitate privacy-preserving, federated data access, offer considerable promise to advance medical research [<xref ref-type="bibr" rid="ref29">29</xref>]. Health care blockchain industry expert Robert Miller [<xref ref-type="bibr" rid="ref80">80</xref>] observes the following:</p>
        <disp-quote>
          <p>Health data is inherently sensitive, and thus demanding of privacy. Yet at the same time health data is inherently statistical, and thus holds within it insights that could improve health for all. The promise of federated learning is to unlock these insights without compromising on privacy. Moreover, federated learning will enable us to assemble more data than ever in federated networks, leading to better algorithms and ultimately better outcomes.</p>
        </disp-quote>
      </sec>
      <sec>
        <title>Challenges for Blockchain Take-up and Implementation in Health Care Settings</title>
        <sec>
          <title>Overview</title>
          <p>We have seen how the health care sector is beginning to develop viable blockchain applications for specific health care purposes and contexts to establish proof of concept, which are yet to be widely implemented at scale [<xref ref-type="bibr" rid="ref58">58</xref>]. This invariably invites questions about the prospects of blockchain’s sector-wide take-up, implementation, and diffusion, particularly given the limited success of health IT adoption more generally [<xref ref-type="bibr" rid="ref81">81</xref>]. To begin addressing these questions, a set of 6 interrelated <italic>implementation challenges</italic> associated with seeking to implement and integrate blockchain into real-world health care contexts were identified using the methodological approach described above. Of these, 3 challenges were already being encountered in seeking to use blockchain technologies to facilitate the sharing and collaboration of health care data for administrative and research purposes, namely (1) organizational commitment, (2) interoperability and standardization, and (3) internal governance. A total of 3 additional emerging challenges are likely to be particularly acute if, in the future, sustained attempts are made to introduce blockchain technologies into clinical settings for which only modest experimentation has occurred to date, namely (4) data security and integrity, (5) quality and safety, and (6) truth and immutability (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>).</p>
          <p>In addition to these implementation challenges, 3 further <italic>normative tensions</italic> or value conflicts invariably arise in configuring blockchain technologies to meet specific functional requirements in health care contexts, which were also identified (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>). Accordingly, acceptable compromises between competing objectives and values must be identified in an attempt to apply blockchain to real-world settings that can be designed into the software and system architecture and implemented into specific organizational contexts [<xref ref-type="bibr" rid="ref82">82</xref>].</p>
          <boxed-text id="box1" position="float">
            <title>Blockchain in health care implementation challenges.</title>
            <p>
              <bold>Implementation challenges</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Organizational commitment</p>
              </list-item>
              <list-item>
                <p>Interoperability</p>
              </list-item>
              <list-item>
                <p>Internal governance and standardization</p>
              </list-item>
              <list-item>
                <p>Data security and integrity</p>
              </list-item>
              <list-item>
                <p>Quality and safety</p>
              </list-item>
              <list-item>
                <p>Truth and immutability</p>
              </list-item>
            </list>
          </boxed-text>
          <boxed-text id="box2" position="float">
            <title>Normative tensions requiring resolution in applying blockchain to health care.</title>
            <p>
              <bold>Normative tensions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>High performance and scalability while providing adequate security</p>
              </list-item>
              <list-item>
                <p>Providing transparency and accountability while ensuring due respect for privacy and confidentiality</p>
              </list-item>
              <list-item>
                <p>Establishing computational trust while securing adequate social trust between network participants</p>
              </list-item>
            </list>
          </boxed-text>
          <p>Common to each of these challenges and normative tensions is their multifaceted, dynamic, context-sensitive, and complex character, comprising both technical and nontechnical dimensions. Moreover, addressing these challenges typically requires internal organizational adaptations <italic>and</italic> changes external to the organization because of the inherent character of blockchain as a <italic>process</italic> innovation [<xref ref-type="bibr" rid="ref83">83</xref>], particularly when used to facilitate trustworthy data sharing beyond organizational boundaries. Each of these challenges is outlined below, beginning with 3 near-term challenges, followed by a brief discussion of 3 further challenges that are likely to be particularly acute if blockchain applications are applied in clinical contexts.</p>
        </sec>
        <sec>
          <title>Organizational Commitment</title>
          <p>The decision by any organization to adopt a new IT system is not made lightly. Making a commitment to experiment with a technology to establish proof of concept as a bounded, time-limited project is likely to be considerably easier for an organization than committing to implementing a novel technology on an ongoing basis, particularly for health care organizations [<xref ref-type="bibr" rid="ref84">84</xref>]. Difficulties associated with eliciting the funding and commitment necessary to move a technological invention beyond the proof-of-concept stage are one of the characteristic features of the so-called valley of death described above. For organizations, this requires a compelling business case demonstrating that such a move will generate significant, sustainable net gains (such as increased revenues, reduced costs, or better-quality patient care) to justify the substantial investment and risks associated with doing so [<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref86">86</xref>]. Given that the nature and magnitude of benefits of blockchain for health care remain largely unproven, and experience has shown that implementing health IT programs involves a great deal of time, money, and effort, making such a case will be difficult [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref87">87</xref>]. When proposed to support administrative functions, such as supply-chain management, the cost of blockchain adoption and implementation may be difficult for an organization to justify, as the expected benefits take the form of enhanced compliance and, hopefully, lower costs and reduced risk, all of which are difficult to quantify. For example, consider difficulties in quantifying the value gained from using blockchain-enabled pharmaceutical supply chains to reduce the risks associated with the production of fake medicines whose scope and prevalence are not well-known, and alternative cheaper technologies which may be more attractive [<xref ref-type="bibr" rid="ref29">29</xref>]. Organizations willing to attempt blockchain implementations will also need to join a suitable network of participants willing to align and collaborate over a common interest in a particular kind of health care data via a blockchain network and avoid generating significant user resistance from staff. Neither task is likely to be easy [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref88">88</xref>-<xref ref-type="bibr" rid="ref90">90</xref>].</p>
          <p>Nonetheless, the proliferation of health care consortia in the United States, throughout 2019 and early 2020, seeking to develop blockchain-based collaborations over administrative data suggests that a variety of health care organizations increasingly recognize the potential value of blockchain-based data sharing for administrative and research purposes. The use of blockchain-enabled data sharing to support highly labor-and time-intensive administrative processes (such as provider credentialing) could significantly enhance administrative efficiency and reduce workloads. As one leading commentator has observed, almost every insurance company and pharmaceutical company has announced participation in a cooperative data-sharing health care consortium, including health systems, IT companies, and nontraditional health care companies such as PNC Bank and Walmart [<xref ref-type="bibr" rid="ref91">91</xref>]. However, blockchain applications that have gained the most organizational buy-in have either avoided sharing of patient data, focusing instead on collaboration over administrative data, or have involved research collaborations that share and manage patient data in a privacy-preserving manner.</p>
          <p>This points to a further hurdle that is likely to arise in eliciting organizational commitment: the need to ensure that blockchain applications comply with applicable legal and regulatory requirements, which are especially demanding in relation to clinical applications. Legal requirements that apply to patient-related health care data and the broader regulatory environment in which health care is provided are substantial, complex, and often difficult to navigate, both in the United States and Europe. Accordingly, ensuring that blockchain-enabled <italic>clinical</italic> applications demonstrably comply with applicable laws will be very challenging [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]. That said, blockchain advocates place considerable optimism in <italic>smart contracts</italic>—computer programs that automate the verification, execution, and enforcement of certain terms and conditions of an arrangement, built on top of a blockchain system that enables a distributed ledger to function as a distributed computer [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref93">93</xref>-<xref ref-type="bibr" rid="ref95">95</xref>]. Accordingly, blockchain systems in combination with smart contracts could operate as a form of <italic>RegTech</italic> through which compliance with legal and other regulatory requirements can be <italic>hardwired</italic> to execute automatically. However, whether these technologies will live up to this potential, given the messiness and unpredictability of real-world contexts, remains unknown [<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref97">97</xref>]. Overcoming each of these barriers to organizational commitment presents formidable challenges and taken together, generate major obstacles that lie in the path of successful blockchain innovation and diffusion in health care [<xref ref-type="bibr" rid="ref98">98</xref>].</p>
        </sec>
        <sec>
          <title>Interoperability and Standardization</title>
          <p>Another significant obstacle that continues to frustrate health care data-sharing efforts is the lack of interoperability within and between health IT systems [<xref ref-type="bibr" rid="ref99">99</xref>]. This is equally true for blockchain-based data management systems. HIMSS explains that, for the purposes of a health data ecosystem, interoperability is “the ability of health information systems to work together within and across organizational boundaries in order to advance the effective delivery of healthcare for individuals and communities.” HIMSS [<xref ref-type="bibr" rid="ref100">100</xref>] notes that:</p>
          <disp-quote>
            <p>In the healthcare space, interoperability is important across systems and organizations for information to flow seamlessly between actors like patients, doctors, hospitals, payers, etc. However, it has been one of the hardest challenges healthcare has faced as vendors, providers, policies, payers and patients have, at times, set roadblocks up and created misaligned incentives to achieve true exchange of data between disparate systems. Realizing the benefits of blockchain technology depends on the associated network of healthcare organizations being able to share data and collaborate via the blockchain. These net-new requirements increase the scope of interoperability challenges that pre-dated blockchain. When systems are not interoperable, the cost of verification and networking of the information is very high. The same is true for the cost of settlement and reconciliation of the transactions of information.</p>
          </disp-quote>
          <p>To maximize the capacity for data sharing, <italic>full</italic> interoperability between blockchain systems is needed; however, achieving this remains a very long way off and arguably will forever remain an impossible dream [<xref ref-type="bibr" rid="ref101">101</xref>]. Interoperability in relation to health care IT can be understood at 3 levels. First, foundational interoperability allows data exchange from one IT system to be received by another without needing the receiving IT system to have the capacity to interpret that data. Second, structural interoperability allows the movement of health care data from one IT system to another such that the clinical or operational purpose and meaning of the data are preserved and unaltered, which is enabled by defining the structure or format of data exchange. Third, semantic interoperability refers to the ability of 2 or more IT systems or elements to exchange information and use the information that has been exchanged [<xref ref-type="bibr" rid="ref102">102</xref>], requiring both the structuring of the data exchange and the codification of the data (including vocabulary) so that the receiving IT systems can interpret the data. Critical to the achievement of interoperability is the shared use of common standards (that are either mandated or very widely accepted and adopted) at the relevant level. To this end, important and ongoing efforts are being made to establish international standards for health care data and IT architecture to enable all 3 levels of interoperability for health care data sharing, including the work of standard-setting organizations such as Integrating Healthcare Enterprise International [<xref ref-type="bibr" rid="ref103">103</xref>] and Health Level Seven International [<xref ref-type="bibr" rid="ref104">104</xref>,<xref ref-type="bibr" rid="ref105">105</xref>].</p>
          <p>The need for interoperability may help explain why the blockchain use cases with the greatest prospects of success in the near term are largely concerned with sharing <italic>back office</italic> functions and associated records, such as credentialing and provider identity verification, and claims management and billing rather than the sharing of patient data for clinical purposes [<xref ref-type="bibr" rid="ref106">106</xref>,<xref ref-type="bibr" rid="ref107">107</xref>]. Although these applications entail interorganizational record sharing, which may well be in different formats and structures, the substantive content of the records themselves is likely to have a high degree of <italic>semantic</italic> interoperability that tends to avoid subjective evaluations and is not readily prone to misinterpretation or misunderstanding. For example, the ProCredEx consortia enable the pooling of records concerning whether a particular individual possesses particular professional qualifications; these records can be readily shared between participants without any serious likelihood that the meaning of those records will be misinterpreted by other members [<xref ref-type="bibr" rid="ref57">57</xref>].</p>
          <p>In other words, blockchain-based record sharing among multiple participants is more likely to succeed if the underlying data are highly stable and readily verifiable as evidencing the <italic>truth</italic> of the underlying phenomena that the data purports to represent (eg, such as whether a clinician has obtained a university degree from an approved medical school), and the consequences of an error or data inaccuracy are not safety-critical. However, experts worry that, as multiple blockchains for health care networks emerge supporting a wide variety of applications, they might not be interoperable <italic>with each other</italic>. This could seriously undermine the value and benefits of blockchain-enabled solutions [<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref109">109</xref>]. For example, an organization participating in a pharmaceutical supply-chain blockchain may find that it is not interoperable with a clinical trial blockchain network that it also wishes to join, significantly reducing the potential value it might otherwise derive from using blockchain. These anticipated challenges reflect the observations by Greenhalgh et al [<xref ref-type="bibr" rid="ref98">98</xref>] that a common but significant health care infrastructure challenge in many countries lies in enabling state-of-the-art individual technologies to interface with (but have often been designed with little awareness of) a legacy infrastructure and restrictive regulatory standards, all in the context of a complex, fast-changing, unpredictable, and underfunded service environment.</p>
        </sec>
        <sec>
          <title>Internal Governance</title>
          <p>A feature of the growing number of health care consortia seeking to use blockchain technologies to selectively share data and collaborate at the B2B level is that member organizations are often conventionally regarded as competitors [<xref ref-type="bibr" rid="ref110">110</xref>]. If these novel sociotechnical collaborations are to succeed, a clear set of agreed norms and arrangements to govern the terms of their collaboration will be essential, without which stable cooperation across the network is unlikely to be viable in practice. In open, permissionless blockchains, including Bitcoin and Ethereum, disagreements over proposed changes to the technical architecture have led to highly publicized disagreements, reflecting the different political viewpoints and motivations of participants, which often lead to the fragmentation of the blockchain network in the form of a <italic>fork</italic> in the ledger [<xref ref-type="bibr" rid="ref111">111</xref>-<xref ref-type="bibr" rid="ref114">114</xref>]. Although the overwhelming majority of health care distributed ledger technology applications use hybrid enterprise or permissioned systems, they face internal governance challenges that may be no less fraught than those that have arisen in open, permissionless blockchains [<xref ref-type="bibr" rid="ref115">115</xref>]. However, establishing a durable internal governance framework that commands widespread acceptance by members and participants across the network (including potential new members and participants) will be especially challenging, which is discussed more fully in the following sections in relation to the challenges of <italic>coopetition</italic> [<xref ref-type="bibr" rid="ref116">116</xref>].</p>
        </sec>
        <sec>
          <title>Data Security and Integrity</title>
          <p>Although the most promising engagements with blockchain in health care contexts have hitherto largely avoided the clinic, many industry experts believe that as the technology matures, clinical applications entailing collaboration over patient data are likely to emerge [<xref ref-type="bibr" rid="ref117">117</xref>]. A further 3 challenges are already being encountered within the health care sector in seeking to engage with blockchain technologies, but which are likely to be particularly acute if blockchain applications are applied in clinical contexts. Chief among them are the challenges associated with data security and integrity. For any blockchain-based system, the desired level of data security must be identified, established, and maintained across the system’s architecture and operation. For patient data, questions about data security are primarily informed by their size and high sensitivity. Accordingly, it is widely accepted that patient data are best stored <italic>off chain</italic>, for example, in a relational database with the shared ledger merely storing metadata together with pointers to where the actual patient data resides and hash codes to verify the integrity of the off-chain data [<xref ref-type="bibr" rid="ref82">82</xref>,<xref ref-type="bibr" rid="ref118">118</xref>]. By incorporating technological mechanisms for identity management and access control into blockchain systems, the on-chain record can also record when, whether, and by whom the relevant linked data are accessed. This approach is reflected in what HIMSS refers to as the principle of <italic>minimal sufficiency</italic> to on-chain data, which it advocates as best practice, stating the following [<xref ref-type="bibr" rid="ref92">92</xref>]:</p>
          <disp-quote>
            <p>Blockchain technology was not designed to be a storage mechanism for data and should not be leveraged as such, for security, privacy, compliance and performance reasons. Information added to the chain may be transparent to permitted network participants and difficult to remove without affecting the entire chain. Therefore, we strongly recommend that regulators and policymakers promote that organizations leveraging blockchain-enabled solutions employ a “minimal but sufficient” strategy for the data that should be included on-chain. This strategy should be guided by the use case’s data needs, and implementers should keep in mind not only the privacy and security risks but also the performance of blockchain transactions when deciding the amount of data and/or personally identifiable information (PII) included on the chain. Whenever possible, privacy-enhancing technologies should be used to secure private data on the blockchain.</p>
          </disp-quote>
          <p>However, by storing patient data offline, the blockchain ledger cannot ensure data security. Although there are various measures, including encryption, that can enhance off-chain data security, these are separate and distinct from blockchain’s technological protections for securing on-chain data. Given that one of blockchain’s most significant <italic>promises</italic> lies in the iron-clad security it purportedly brings to on-chain data, the inability to extend that protection to the data stored off chain seriously limits the technology’s capacity to deliver on this promise. In addition, a frequently overlooked and neglected issue in the blockchain literature is the problem of <italic>data leakage</italic> or <italic>escape</italic>. Although blockchain offers the technological capacity for fine-grained, auditable data sharing through technological access controls that protect the privacy and confidentiality of stored records, blockchains do not address the possibility that, once data are revealed, those with access will generally be able to copy and extract the data and store it perpetually. As Finck [<xref ref-type="bibr" rid="ref93">93</xref>] warns, the purposes of blockchain projects can be completely undermined when data escape is possible, particularly in circumstances where data are sold once, and the buyer can then resell or manipulate the data set at will.</p>
        </sec>
        <sec>
          <title>Truth and Immutability</title>
          <p>A critical feature emphasized by blockchain advocates is the technology’s capacity to create a single, immutable, shared authoritative record, reflected in descriptions of blockchain as a <italic>truth machine</italic>. However, the validity of this claim assumes that the data recorded on the blockchain has <italic>integrity</italic>—meaning that they are accurate, up to date, and comprehensive. Although often discussed in terms of providing assurance that the data have not been tampered with or subject to unauthorized alteration [<xref ref-type="bibr" rid="ref119">119</xref>,<xref ref-type="bibr" rid="ref120">120</xref>], data integrity also requires that the data faithfully and accurately represent the underlying real-world phenomenon they purport to represent. For example, if a health care record is labeled as representing a particular item, such as an X-ray taken of patient Y on Z date at location P and stored at an off-chain location Q, then it must represent precisely that. This also requires (among other things) that blockchain consistently keeps transaction information associated with the correct person. Although considerable work is being devoted toward identifying universal identity management solutions for blockchain-based systems, this remains an unresolved challenge. Questions concerning how blockchain can ensure that the records appended to the blockchain ledger are accurately tethered to and reflect the underlying reality that they purport to be associated with remain surprisingly overlooked (or perhaps conveniently ignored) in the existing blockchain literature. In health care, these challenges are particularly acute if data are to have clinical relevance. However, they sit uncomfortably with developers’ and entrepreneurs’ claims that blockchain will enable the creation of accurate and comprehensive patient records that draw data directly from a patient’s wearable device, which is gathered via sensor technologies, without mechanisms that guarantee the accuracy, veracity, and reliability of data thereby collected [<xref ref-type="bibr" rid="ref21">21</xref>]. Although sensor technologies can help establish direct connections between the digital and physical world in a secure manner, sensors can be easily tricked (even if tamper-proof hardware is used); thus, conventional social trust is needed to trust the veracity of the underlying data. This calls into question the value that blockchain purports to offer in the first place. In the context of supply chain management, Wüst and Gervais [<xref ref-type="bibr" rid="ref119">119</xref>] refer to the following:</p>
          <disp-quote>
            <p>The inherent problem of the interface between the digital and the physical world. A human, or some machine under the control of a single writer, typically is required to register that a good has arrived in a warehouse and, if for example, its quality is appropriate. If there is no trust in the operation of these employees, then the whole supply chain is technically compromised as any data can be supplied by a malicious writer. If, on the other hand, all writers are trusted, a blockchain is not needed as a regular database with shared write access can be used instead.</p>
          </disp-quote>
          <p>Although the accuracy of health care administrative data may not always be safety-critical, there is little value in a blockchain that maintains a tamper-proof record of inaccurate or poor-quality data. Accordingly, descriptions of blockchain as a <italic>truth machine</italic> appear somewhat overstated [<xref ref-type="bibr" rid="ref31">31</xref>]. Data integrity is a necessary prerequisite for establishing trustworthiness and providing a reliable basis for decision-making. Houlder [<xref ref-type="bibr" rid="ref121">121</xref>] explains the following:</p>
          <disp-quote>
            <p>Data security is often equated with protecting data confidentiality: but it is data integrity that must be protected – and this requires ensuring that the data is accurate, up-to-date and complete. Blockchain only protects what arrives at blockchain. From an immutability and transparency standpoint, if that data is compromised or of poor quality before it reaches the blockchain you end up with garbage in, garbage out, where you’re protecting garbage on the blockchain. Unless the data has the integrity and quality needed, blockchain will not realise its potential.</p>
          </disp-quote>
          <p>The yet-to-be-resolved challenge of assuring data integrity may help explain why the handful of patient-facing blockchain applications offered through the NHS (in partnership with private technology providers) have largely confined blockchain functionality to storing records of patient consent and providing computational assurance concerning when a patient has accessed (and securely copied) his or her NHS records.</p>
          <p>In addition, the application of blockchain to health care will entail human interaction and engagement. Even if users are provided with high-quality training, help, and guidance, mistakes will be inevitable. However, identifying and correcting errors generates new challenges, particularly given that blockchain ledgers cannot be retroactively altered. Although blockchain’s tamper-proof character prevents certain kinds of mistakes and problems that arise in relation to conventional centralized databases (such as inadvertently overwriting data stored on the database), they will inevitably introduce new ones. This is particularly so given the complex and dynamic nature of health care settings and the multiple intersecting and sometimes conflicting interests, rights and obligations, expectations, and anxieties they typically implicate. In other words, the vagaries of human behavior and decision-making in real-world health care contexts could prevent blockchain’s expected benefits from being fully realized.</p>
        </sec>
        <sec>
          <title>Quality and Safety</title>
          <p>Data integrity is but one element of the larger, multidimensional challenge of ensuring that blockchain systems can be implemented in health care without compromising quality and safety, particularly when they interface with and operate within clinical contexts. Although the safety implications arising from the digital transformation of health care have been well-documented [<xref ref-type="bibr" rid="ref122">122</xref>], patient safety has received relatively little attention to date, perhaps because of the relative scarcity of clinical blockchain use cases being trialed and implemented. Patient safety issues include the need to ensure that blockchain systems that affect clinical workflows and environments are subject to rigorous testing, validation, and independent evaluation before their introduction into the clinic. However, in the US health care context, no systematic attention appears to have been given to the technical robustness, safety, or ethical dimensions of blockchain implementation. Rather, health care blockchain projects appear to move from proof of concept through to implementation without necessarily being subjected to formal testing and validation to provide assurance of the system’s robustness, resilience, or clinical safety. Accordingly, health care blockchain expert Heather Flannery argues that these projects should be understood as experiments to learn and discover the kinds of conditions that produce the desired results; although these conditions are partially technical, in her view, most are clinical, social, economic, legal, ethical, and governance-related. Hence, Flannery argues that these projects should be undertaken as studies subject to proper research protocols as the only ethically viable way to move past the point of experimenting with the technology [<xref ref-type="bibr" rid="ref123">123</xref>,<xref ref-type="bibr" rid="ref124">124</xref>]. In contrast, regulatory oversight of health IT systems in the United Kingdom is more developed. Thus, the Health and Social Care Act 2012 requires the development and implementation of clinical risk management processes to ensure patient safety with respect to the manufacture of new health IT systems, or the modification or decommissioning of an existing system, and their deployment and use [<xref ref-type="bibr" rid="ref125">125</xref>,<xref ref-type="bibr" rid="ref126">126</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Normative Conflict Requiring Satisfactory Resolution</title>
        <p>Although the above 6 challenges might be overcome in time, several further challenges rooted in inherent tensions between desirable qualities or functional requirements that arise when configuring blockchain applications may prove more intractable. Although technical blockchain experts have identified various <italic>design trade-offs</italic> when building blockchain systems for specific purposes [<xref ref-type="bibr" rid="ref82">82</xref>], reflecting the <italic>micropolitical nature of software choices</italic> [<xref ref-type="bibr" rid="ref98">98</xref>], the following 3 are particularly apposite to health care settings:</p>
        <sec>
          <title>Performance and Scalability Versus Security</title>
          <p>Ideally, an IT system would provide high levels of security and resilience for the system and the data it stores and generates while offering high-speed performance at scale. However, achieving these objectives in blockchain systems is technically impossible (on currently available technology) because of inherent trade-offs in functionality. There is a loose <italic>trilemma</italic> in the design and configuration of blockchain systems such that they can have at most two of the following three properties: (1) decentralization, (2) scalability, and (3) security. The more computationally demanding and time intensive the consensus protocols for validating transactions [<xref ref-type="bibr" rid="ref127">127</xref>] before being appended to the ledger and the greater the degree of decentralization across the network, the greater the ledger’s security and resilience against attack but the slower the performance in terms of speed and throughput [<xref ref-type="bibr" rid="ref128">128</xref>]. In addition, as blockchains ledgers are distributed, they entail high storage costs, precluding large data from being effectively stored on the blockchain. As already noted, although blockchain can be used for access control (and auditing), large data must be stored <italic>off chain</italic> [<xref ref-type="bibr" rid="ref129">129</xref>]. This generates the need to assure off-chain data security; simply using a blockchain to manage access does not thereby offer the security of the stored data, pointing to an inherent tension between the desired values of scalability versus security in their design and operation [<xref ref-type="bibr" rid="ref130">130</xref>].</p>
        </sec>
        <sec>
          <title>Transparency Versus Privacy</title>
          <p>The transparency of all transactions appended to the ledger is a critical feature of open, permissionless blockchains, contributing to the ledger’s trustworthiness. However, this level of transparency is fundamentally at odds with the private and confidential nature of patient data and other health-related personal information. Accordingly, there is an inherent tension between the need to respect privacy and confidentiality and the design and operation of open blockchain networks that are transparent to the world at large [<xref ref-type="bibr" rid="ref93">93</xref>]. Under the European Union’s General Data Protection Regulation, data collectors and processors must not collect or process personal data without a lawful basis, which includes, but is not limited to, consent by the data subject. In common law systems, additional legal obligations attach to information acquired in circumstances of confidence by clinicians and other care providers, including information communicated by patients to doctors during clinical encounters. At the same time, health care organizations typically seek to keep details of their business records confidential. As already indicated, the <italic>minimum sufficiency</italic> principle of information collection and storage is considered best practice in health care IT design and operation so that health care blockchain systems have hitherto largely taken the form of <italic>permissioned</italic> systems, thereby limiting <italic>read</italic> access to the ledger to those authorized to do so, with health care data being stored off chain and only the hashed metadata stored on chain.</p>
        </sec>
        <sec>
          <title>Computational Trust Versus Social Trust</title>
          <p>Although the hyperbole associated with blockchain technologies has begun to subside, early industry activity and engagement with blockchain appears largely to have been <italic>technology lead</italic>, arguably motivated by the desire to engage with the latest cutting-edge technology [<xref ref-type="bibr" rid="ref131">131</xref>] without either a deep understanding of the technology or a desire to meet a specific need that blockchain might usefully address. As the technology has begun to mature, so too have academic investigations, with more recent academic critiques arguing that conventional database structures and systems will often provide cheaper, faster, more sustainable, and scalable approaches to specific real-world data access, management, and storage needs [<xref ref-type="bibr" rid="ref119">119</xref>,<xref ref-type="bibr" rid="ref132">132</xref>]. Several scholars have sought to identify the circumstances in which blockchain technologies have a genuine prospect of addressing real-world problems for which conventional centralized, networked databases are inadequate. For example, Wüst and Gervais [<xref ref-type="bibr" rid="ref119">119</xref>] argue that if either a trusted third party who can verify transactions is always available on the web or if all writers mutually trust others, then a conventional database with shared write access is likely to be preferable. However, if the writers of the ledger do not trust each other, a permissioned blockchain may provide a viable solution. Their insight resonates with, and may help to explain, the recent emergence of consortia of health care organizations who compete with each other in many respects but recognize that they share a limited common interest in relation to specific kinds of data and forms of data sharing. In these circumstances, member organizations may not fully trust each other, and a permissioned blockchain may provide a technological solution to address this trust deficit.</p>
          <p>Permissioned systems (including so-called <italic>enterprise</italic> systems) have hitherto been favored in health care blockchain applications. They appear to offer the greatest opportunities for generating value from network effects arising from the creation of a shared, trustworthy transactions ledger between a limited number of authorized participants, enabling members to benefit from effectively sharing elements of a <italic>back office</italic> administrative system (ie, shared records management in a single shared ledger). However, the security and integrity of the shared record will only be as strong as its weakest link, giving rise to what may be called the <italic>computational trust</italic> paradox. On the one hand, the use of computational consensus mechanisms to verify transactions and maintain a single shared ledger across a distributed network of computers obviates the need for each participant to maintain their own ledger and reconcile their ledger with that of other participants, generating significant administrative efficiencies. On the other hand, this means that each participant must trust the integrity, quality, and security of the participant’s records, including the accuracy of the information contained in those records. This relies, in turn, upon the integrity of the practices and processes underpinning the events and transactions that each record purports to represent (subject to those records being validated by the network and appended to the shared ledger). By pooling their records, each participant is thereby exposed to the vulnerabilities of the record keeping and information security practices of their fellow participants. A paradox arises because, although blockchain systems offer the possibility of coordination with others <italic>without</italic> the need for social trust in those others by relying instead on <italic>computational trust</italic>, when these systems take the form of permissioned ledgers, this is likely to <italic>enhance</italic> the need for conventional (social) trust in the practices and systems of other network members. Hence, reliance on computational trust serves, ultimately, to heighten the importance and need for social trust to reap the gains from cooperation [<xref ref-type="bibr" rid="ref133">133</xref>]. A leading industry expert [<xref ref-type="bibr" rid="ref121">121</xref>] commented as follows:</p>
          <disp-quote>
            <p>If you have a consortium of 10 organisations and one of them is a kind of weak link...in terms of they’re connecting to the blockchain and pulling information off the blockchain, or in interactions that are enabled by blockchain, and putting information in their own enterprise systems which are insecure and a breach occurs, it impacts everyone...you’re not just worried about securing your own organisation, you’ve got to make sure that everyone connecting to that blockchain is adequately secure.</p>
          </disp-quote>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Overview</title>
        <p>The above findings draw attention to the number and variety of formidable, multidimensional challenges that must be satisfactorily addressed if blockchain technologies are to traverse the valley of death. Nevertheless, this study also shows how early engagements with blockchain in health care have begun to demonstrate that these technologies <italic>can</italic> enable and facilitate novel, valuable forms of health care data sharing and cooperation in real-world health care settings under specific circumstances. The following discussion critically reflects upon these key findings by reference to 3 quite different strands of academic literature: first, it examines the character and tensions inherent in these incipient forms of blockchain-enabled cooperation; second, it draws on insights from innovation studies to consider the character of blockchain as <italic>radical</italic> or <italic>incremental</italic> health care technologies; and third, it evaluates the prospects of blockchain for health care’s <italic>favorite use case</italic>, that is, to enable <italic>patient sovereignty</italic> over EHRs while overcoming the currently siloed approach to patient data.</p>
      </sec>
      <sec>
        <title>The Blockchain in Health Care Promise: Rhetoric, Reality, and Blockchain-Enabled Coopetition</title>
        <p>Recent health care blockchain initiatives have successfully demonstrated how technology can facilitate limited, purpose-specific forms of cooperation through the shared pooling of data to solve common problems. These incipient forms of cooperation involving data sharing, which consortia of health care organizations are actively seeking to develop, rely upon interactions that organizational studies scholars refer to as <italic>coopetition</italic>. Although the interaction between firms conventionally focuses on either of 2 contrasting and antagonistic logics—competition (traditionally defined as the conflicting and rivalrous relationship between firms) on the one hand and cooperation on the other [<xref ref-type="bibr" rid="ref134">134</xref>]—the actual interaction between firms can involve cooperation in some activities while competing in others [<xref ref-type="bibr" rid="ref135">135</xref>]. As these coopetitive relationships entail 2 diametrically opposing logics of interaction, they are inherently complex, generating tensions between and within organizations [<xref ref-type="bibr" rid="ref136">136</xref>,<xref ref-type="bibr" rid="ref137">137</xref>]. In particular, each organization faces conflicting incentives: a desire to cooperate through the pooling of resources to generate shared benefits on the one hand and the incentive to capture private benefits for themselves on the other [<xref ref-type="bibr" rid="ref137">137</xref>,<xref ref-type="bibr" rid="ref138">138</xref>]. Several theories have been offered, claiming to predict the effect of coopetition on firm performance [<xref ref-type="bibr" rid="ref137">137</xref>,<xref ref-type="bibr" rid="ref139">139</xref>], including transaction cost theories. Transaction cost theories highlight the difficulties of fostering trust between parties in a coopetitive relationship, as each participant has incentives to opportunistically behave while facing high levels of uncertainty [<xref ref-type="bibr" rid="ref140">140</xref>]. This creates barriers to open collaboration, making it difficult to develop the necessary level of trust needed for common projects to succeed. On the other hand, several scholars have noted that the inherent tension between cooperation and competition arising within coopetitive relationships can, if managed efficiently, create shared value and generate beneficial outcomes for each party [<xref ref-type="bibr" rid="ref137">137</xref>]. On this view, the key to successful coopetition is effective management of the coopetitive tensions within the relationship that nurtures and maintains an appropriate balance between competition and collaboration. Various insights from this literature help illuminate the challenges likely to arise within health care consortia comprising organizations that would otherwise regard themselves as competitors seeking to share health care data via a permissioned blockchain network. The configuration of access rules within a permissioned blockchain system offers a potentially novel mechanism through which <italic>social distrust</italic> might be replaced by <italic>computational trust</italic>, thereby enabling new forms of cooperation at the B2B level that might not otherwise occur, as the trust gap is too difficult to overcome.</p>
        <p>That said, the need for strategies to successfully manage the tension between organizations within the network highlights the importance of a blockchain network’s internal governance arrangements, particularly in establishing and maintaining rules concerning changes to the network’s architecture, protocols, rules of admission, and incentive mechanisms. Details about the internal governance arrangements that underpin the various blockchain consortia that have emerged in recent years are not publicly available because of the confidential nature of the underlying partnership agreements. Nevertheless, one would expect that formulating and maintaining a set of governance arrangements that will prove durable and resilient over time is likely to be extremely difficult, as the interests of participants are not <italic>wholly</italic> aligned and hence, difficult to settle in advance. These internal governance arrangements must identify how critical decisions about, for example, the structure of economic incentives or rewards for participants to engage in the consensus protocol, how the network will be maintained, and how other changes to the network’s structure and operation will be made and by whom. Potentially conflicting interests may not be readily apparent at the time of the network’s inception but may subsequently arise as organizational needs, the larger industry context, and other external factors inevitably change over time. However, perhaps it is only when the <italic>rubber hits the road</italic> in the context of specific disagreement between network participants that the critical need for robust governance structures that command the respect and allegiance of the network’s members becomes apparent.</p>
        <p>Finding an appropriate but flexible equilibrium between the need for social trust between network participants on the one hand and <italic>hardwiring</italic> computational trust into the technical architecture and operation of the blockchain system will be a very tough nut to crack. It remains an ongoing and continuing challenge for the foreseeable future, at least until blockchain in health care achieves a level of maturity in which a widely shared set of agreed norms concerning the core requirements of good blockchain governance can emerge. Furthermore, these networks are likely to encounter what has been referred to above as the <italic>computational trust</italic> paradox; by seeking to rely on computational trust to provide a basis for enabling cooperation between firms, this may reinforce and accentuate the need to nurture and maintain social trust between the parties in domains in which computational trust cannot be secured.</p>
      </sec>
      <sec>
        <title>Permissioned Blockchains in Health Care: Incremental or Radical Innovation?</title>
        <p>Early engagement with blockchain technologies in health care contexts has largely used <italic>permissioned</italic> blockchain systems (including so-called <italic>enterprise</italic> blockchains) rather than open, permissionless systems that many blockchain advocates believe will revolutionize social cooperation between strangers without the need for conventional trusted third-party intermediaries, such as banks and governments. Although the blockchain for health care promise has not typically emphasized the role of permissionless blockchains, a significant <italic>revolutionary</italic> narrative is evident in claims that blockchain technology will <italic>disrupt</italic> health care [<xref ref-type="bibr" rid="ref17">17</xref>]. Within this narrative, blockchain is portrayed as enabling radical patient empowerment achieved via hard-coded access controls, securely facilitating the seamless exchange of patient records currently stored in disparate data silos while enabling patients to exert fine-grained control over who is granted access to those records, wherever located, and on what terms [<xref ref-type="bibr" rid="ref141">141</xref>,<xref ref-type="bibr" rid="ref142">142</xref>]. It is blockchain’s potential to overcome the many existing technical, legal, and bureaucratic obstacles that obstruct the free flow of health data while preventing patients from exerting control over access to their own health care records that is typically highlighted rather than emphasizing the role of permissionless blockchains in achieving this vision.</p>
        <p>The health care sector’s focus on permissioned (rather than permissionless) blockchain systems to date will disappoint radical blockchain enthusiasts such as Bruce Schneier, a well-known computer security expert. Schneier claims that permissioned blockchains are “completely uninteresting” as they are no different from centralized databases in relying on conventional forms of trust to facilitate social cooperation [<xref ref-type="bibr" rid="ref143">143</xref>]. However, his perspective fails to recognize that even open, permissionless blockchains ultimately and invariably rely on social trust to support their internal governance arrangements [<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref113">113</xref>]. By enabling participants to rely on computational trust mechanisms to enforce the explicitly agreed terms of their cooperation, permissioned blockchains could facilitate novel forms of cooperation, leading to valuable and potentially transformational change.</p>
        <p>The transformational potential of permissioned blockchain systems can be illuminated by reference to a distinction drawn by technology management researchers between <italic>inventions</italic>, which refers to an “idea, sketch, or model for a new or improved device, product, process or system” and <italic>innovations,</italic> which, in the economic sense, arise “only with the first commercial transaction involving the new product, system or device” [<xref ref-type="bibr" rid="ref144">144</xref>]. Within this literature, a further distinction is commonly made between <italic>incremental</italic> and <italic>radical</italic> innovation. Incremental innovations introduce relatively minor changes to an existing product, exploiting the potential of the established design (although they may entail considerable skill and ingenuity) [<xref ref-type="bibr" rid="ref145">145</xref>-<xref ref-type="bibr" rid="ref148">148</xref>]. In contrast, radical innovations are based on different engineering and scientific principles, potentially opening up whole new markets and applications [<xref ref-type="bibr" rid="ref146">146</xref>,<xref ref-type="bibr" rid="ref147">147</xref>,<xref ref-type="bibr" rid="ref149">149</xref>]. This distinction is considered to have important competitive consequences: incremental innovation tends to <italic>reinforce</italic> the capabilities of established organizations, whereas radical innovation forces them to <italic>ask a new set of questions</italic>, draw on new technical and commercial skills, and use new problem-solving approaches [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref146">146</xref>,<xref ref-type="bibr" rid="ref148">148</xref>,<xref ref-type="bibr" rid="ref150">150</xref>]. Hence, radical innovation often creates great difficulties for established firms [<xref ref-type="bibr" rid="ref148">148</xref>,<xref ref-type="bibr" rid="ref151">151</xref>-<xref ref-type="bibr" rid="ref153">153</xref>]. As the late Clayton Christensen famously argued, radical innovation can <italic>disrupt</italic> the entire industry as incumbent firms lose out to smaller firms with fewer resources who use these radical innovations to deliver superior functional performance, eventually leading to their adoption by the incumbent’s established customers [<xref ref-type="bibr" rid="ref154">154</xref>].</p>
        <p>It is too early to assess whether permissionless blockchains will ultimately form the basic technological architecture underpinning a dominant design for particular kinds of health care applications. It is not possible to reliably predict whether they will come to be regarded as incremental or radical innovations or, indeed, whether they come to be understood as innovations at all or merely just an interesting invention with little real-world utility. However, the preceding insights suggest that we cannot assume that the use of permissioned rather than permissionless blockchains in health care necessarily implies that they cannot subsequently establish themselves as <italic>radical innovations</italic>. Bruce Schneier’s dismissal of permissioned blockchains overlooks the possibility that they may offer particular functional properties capable of meeting a very specific sectoral need. In functional terms, permissioned blockchains are something of a hybrid—analogous to centralized databases insofar as participation and access require authorization from a network controller but can mathematically provide the verified security and automated audit functionality of permissionless blockchains without the heavy computational expense. Accordingly, they might prove <italic>radical</italic> in their effects [<xref ref-type="bibr" rid="ref155">155</xref>], creating shared value by facilitating new forms of coopetitive collaboration between health care organizations while generating significant efficiencies.</p>
      </sec>
      <sec>
        <title>Blockchain-Enabled EHRs and the Promise of Patient Data Sovereignty</title>
        <p>Mention has already been made of frequent references in both academic and industry literature to the potential of blockchain-enabled EHRs to <italic>revolutionize</italic> health care. According to this vision, blockchain operates as a form of <italic>middleware</italic>, facilitating the flow of data between independent IT systems, thereby integrating disparately located silos of patient health care records while enabling patients to exercise fine-grained but automated control over their EHRs via <italic>smart contracts</italic> that automate the execution of patient instructions or consents [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref109">109</xref>]. In so doing, blockchain is widely portrayed as <italic>solving</italic> the tension between the need to respect the privacy and confidentiality of individual health records and recognizing the tremendous knowledge potential unleashed by pooling and aggregating patient data. Blockchain for health care scholarship has largely taken these claims at face value. Although various blockchain-enabled EHR projects are currently being experimented with, the preponderance of activity appears to reflect the views of industry experts, who advise that blockchain applications focusing on patient care records are best avoided in the early stages of the sector’s engagement with the technology because of the demanding and complex legal and regulatory requirements that apply to personal health information. Nevertheless, many believe that these demands can eventually be overcome, so that patient-controlled, blockchain-enabled EHRs will eventually emerge [<xref ref-type="bibr" rid="ref91">91</xref>,<xref ref-type="bibr" rid="ref117">117</xref>]. Even if the difficult and complex challenges and tensions identified in the preceding section can be satisfactorily overcome, whether these systems will live up to their promise depends upon the validity of underlying assumptions about their benefits, particularly in clinical contexts.</p>
        <p>Academic literature concerned with health IT implementation has hitherto been dominated by the <italic>technology acceptance model</italic> (TAM), which originates from the perspective of health information systems research that studies the systems that support health and medical work [<xref ref-type="bibr" rid="ref156">156</xref>]. This approach, developed jointly by doctors with an interest in computers and computer scientists with an interest in medicine, adopts a positivist outlook that regards the relationship between technology and their expected benefit as linear and causal [<xref ref-type="bibr" rid="ref81">81</xref>]. Similar assumptions appear to underpin 2 distinct, albeit related, elements of the vision of blockchain-enabled EHRs offered by their proponents. The first assumption is that blockchain will enable the seamless integration of patient records currently stored in distinct <italic>data silos,</italic> thereby effectively providing patients and clinicians with a single, up-to-date, and comprehensive repository of each patient’s medical records over his or her lifetime. The second assumption is that configuring blockchain-enabled EHR systems to enable patients to control access to their records will ensure respect for privacy without impeding the transfer and sharing of patient data for clinical and other legitimate purposes.</p>
        <p>In relation to the first assumption, Berg et al [<xref ref-type="bibr" rid="ref157">157</xref>] highlighted studies of EHR implementation that emphasize the personalized nature of health care work, thus setting “natural limits to the possibilities of IT to revolutionise this work.” These studies suggest that the considerable energy and resources thus far devoted to various components of the EHR failed to substantially improve the quality or efficiency of frontline clinical work. Moreover, they argue that EHRs are <italic>unlikely ever</italic> to produce dramatic gains in the quality of care because of the importance of the creative human work needed to bridge the gap between clinical design and technical reality [<xref ref-type="bibr" rid="ref50">50</xref>]. In contrast, biomedical literature often rests on a TAM model, evoking a belief that IT systems will make clinical information instantly available, implicitly assuming that <italic>meaning</italic> can be transmitted unproblematically along with the data contained in the EHR. This assumption also appears to underpin the <italic>beautiful dream</italic> of blockchain-enabled EHR systems, suggesting that, if properly designed, blockchain will enable more accurate, secure, and timely data access that will drive quality improvements across health care, including clinical care. However, studies from more sociologically informed traditions roundly reject this assumption, providing evidence that clinical data must be interpreted in context and <italic>framed</italic> before they become meaningful, and this is not achieved simply by placing information on an electronic platform that is accessible by multiple users [<xref ref-type="bibr" rid="ref50">50</xref>]. These studies rest on assumptions that differ from those underpinning the TAM model (including understandings of what counts as <italic>success</italic> for the purposes of evaluating health IT systems), drawing on a wider range of methodological approaches [<xref ref-type="bibr" rid="ref158">158</xref>]. They highlight the critical role of context, culture, and the values brought to bear by medical professionals in clinical environments, identifying the clinical consultation as a complex social encounter that occurs within a heavily institutionalized environment [<xref ref-type="bibr" rid="ref50">50</xref>]. In particular, scholars from these traditions emphasize the role of values in clinicians’ understanding of what constitutes and how they seek to practice <italic>excellent care</italic> and the nature of clinical knowledge as <italic>tacit, context-bound, and ephemeral rather than codifiable, transferable and enduring</italic> [<xref ref-type="bibr" rid="ref50">50</xref>]. These studies find that in many <italic>failed</italic> EHR projects, technical designers typically missed these subtleties and produced artifacts that fitted poorly with the situated nature of knowledge and the microdetail of clinical work practices [<xref ref-type="bibr" rid="ref81">81</xref>].</p>
        <p>Conversely, the TAM model assumes that the failure of EHRs to generate their expected benefits can be largely explained by shortcomings in EHR system design and implementation, resulting in user <italic>resistance</italic> to the technology [<xref ref-type="bibr" rid="ref50">50</xref>], which can be overcome by system design improvements and more sensitive implementation. One of the most significant lessons from studies of EHR adoption is that considerable clinician resistance to these systems has often resulted from the unintended but radical alteration and disruption of clinical workflows and patient interactions accompanying the introduction of EHRs, adversely affecting physician workload [<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref122">122</xref>,<xref ref-type="bibr" rid="ref159">159</xref>]. In addition, the data captured in these records have been described by a legal expert as often error prone, incomplete, unprotected, and dispersed across numerous organizations unknown to the patient [<xref ref-type="bibr" rid="ref130">130</xref>]. However, if used as <italic>middleware</italic> to support the integration of EHRs across disparate data silos, blockchain technologies should not, in theory, affect clinical workflows or practices, as they operate as a <italic>backend</italic> technology. In other words, blockchain should not exacerbate workload burdens or introduce additional integration work of the kind that has typically accompanied EHR implementation. However, HIMSS [<xref ref-type="bibr" rid="ref160">160</xref>] warns that:</p>
        <disp-quote>
          <p>Blockchain technology is meant to operate on the back end and should avoid, where possible, adding additional steps for the end user. If this technology is poorly implemented without a strong federated approach, workflow may be negatively impacted, potentially affecting the quality of care.</p>
        </disp-quote>
        <disp-quote>
          <p>Adding a blockchain-enabled solution without considering its applicability to a use case, potential value, or relationship with a partnering stakeholder, could add a layer of complexity to an already convoluted health IT ecosystem. Furthermore, if this complexity detracts from the end goal of sound care, ethical and other questions may arise from the implementation of this kind of solution that is not well suited for the coordination and delivery of care.</p>
        </disp-quote>
        <p>This cautious view, offered by one of the health care IT sectors’ leading industry bodies, suggests that one cannot assume that implementation of blockchain as a <italic>backend</italic> technology will not add further system complexity simply by avoiding any change to the <italic>front end</italic> experience of users [<xref ref-type="bibr" rid="ref98">98</xref>].</p>
        <p>The second assumption underpinning the promise of blockchain-enabled EHR systems—that they will enable patient data sovereignty and empowerment by providing patients with fine-grained control over who may securely access their health care records and on what terms—resonates with broader societal shifts in favor of <italic>self-service economy</italic> models across many sectors [<xref ref-type="bibr" rid="ref161">161</xref>]. Blockchain for health care advocates assumes that patient-controlled health care records will resolve dilemmas arising from the tension between ensuring compliance with privacy and confidentiality norms and duties and fostering the aggregation of patient care records for medical research and other legitimate purposes [<xref ref-type="bibr" rid="ref162">162</xref>]. This assumption is likely to be both mistaken and naive for several reasons. First, although it is essential that patients are enabled to exercise their rights of informational self-determination in relation to health and care information that directly pertains to them [<xref ref-type="bibr" rid="ref163">163</xref>], some patients will enthusiastically embrace the capacity to control access to their medical records [<xref ref-type="bibr" rid="ref164">164</xref>], whereas others will not [<xref ref-type="bibr" rid="ref165">165</xref>]. A significant proportion of patients (including children and those with mental illness or disability) cannot make informed decisions about access to and sharing of their clinical data; therefore, alternative consent models will be needed. Second, there will be circumstances in which patient consent cannot be secured; however, the ability to access that patient’s health records will be necessary, particularly in emergency situations. Third, in other circumstances, patient rights to data privacy and confidentiality may be legitimately overridden by compelling public interests, particularly when appropriate technical and organizational measures are taken to safeguard those interests so that patient consent is neither legally nor ethically needed to justify access to their records. For example, the public interest in data sharing and access can, particularly in times of public health care emergency, justifiably override individual rights to privacy and the need for patient consent to data sharing.</p>
        <p>Taken together, the vision of <italic>patient data sovereignty</italic> underpinning blockchain-enabled health records exhibits a <italic>techno-solutionist</italic> mindset, reflecting a belief that technological fixes can be used to <italic>solve</italic> complex social problems [<xref ref-type="bibr" rid="ref166">166</xref>]. Critiques of this kind draw attention to the complex and messy set of interacting norms, practices, and dynamics that arise in the real-world contexts for which simple technological <italic>solutions</italic> are unlikely to be found, which the disappointing experience of EHR implementation has vividly demonstrated. Despite this, the underlying <italic>information as property</italic> paradigm that informs these beliefs appears to hold considerable sway in contemporary debates about data governance, both within health care and beyond [<xref ref-type="bibr" rid="ref167">167</xref>]. However, as the German Data Ethics Commission points out, supporting and promoting the practical capacity of patients to access their health care records and take an active role in decisions about access to those records does not necessitate a <italic>propertisation</italic> model of data governance, which underpins the views of those who favor the making of micropayments to data subjects in return for access to their personal data [<xref ref-type="bibr" rid="ref163">163</xref>,<xref ref-type="bibr" rid="ref168">168</xref>,<xref ref-type="bibr" rid="ref169">169</xref>].</p>
        <p>Apart from unfounded assumptions that technological access controls built into health IT systems can be expected to successfully mediate and resolve the complex interests in patient data, any such shift in favor of patient sovereignty over health care records may reflect an underlying reconfiguration of the ethical basis upon which patients receive care. Rather than characterizing patients as vulnerable individuals and beneficiaries of care provided by an expert clinician who is professionally obliged to act in their best interests, patients may increasingly be expected to <italic>self-manage</italic> their own medical records based on largely unexamined claims that this will <italic>empower</italic> them to exert greater control over their own care [<xref ref-type="bibr" rid="ref85">85</xref>]. However, if these systems are configured in ways that force adherence to norms that are at odds with the basic cultural and moral norms of contemporary health care settings, this might provoke backlash. This might occur, for example, if systems are designed to shift responsibility for care to patients and away from clinicians and care providers in ways considered contrary to the professional duty and commitment of clinicians to act in the best interests of their patients [<xref ref-type="bibr" rid="ref170">170</xref>]. Alternatively, if patients are unable to make meaningful decisions about the sharing of their data, they are likely to stick with defaults; however, these might fail to reflect legitimate patient expectations and existing informational privacy and confidentiality norms. These and other similar risks underline the importance of meaningful stakeholder engagement in the design and implementation of blockchain systems, as well as the importance of more critical engagement with the logic of <italic>empowerment</italic> that frequently accompanies their promised benefits [<xref ref-type="bibr" rid="ref50">50</xref>].</p>
        <p>Accordingly, the vision underpinning blockchain for health care’s <italic>favorite use case</italic>, which is capable of seamlessly integrating patient-controlled EHRs accessible by clinicians in real time wherever located, is based on problematic and unrealistic assumptions. Their promised benefits are therefore unlikely to be realized in practice. Even if blockchain technologies can operate as <italic>middleware</italic>, enabling organizations to access and retrieve patient health care records stored at different sites in real time, blockchain cannot ensure that the information stored in those records is an accurate representation of the underlying real-world events they purport to reflect. Conferring responsibility for making access decisions on patients themselves will not avoid conflicting and sometimes difficult trade-offs between respect for patient privacy and other rights and legitimate interests implicated in health care. In other words, the health care <italic>data silo</italic> problem is only one aspect of a much larger, more complex set of needs, rights, and interests associated with medical and health care information, which are likely to continue to defy hard-coded solutions.</p>
        <p>However, one of the most valuable insights arising from <italic>technology-in-practice</italic> studies of EHRs for understanding the real value that blockchain-enabled EHRs might create arises from the recognition that there are two conflicting work processes in play with EHRs: immediate clinical care (primary use) on the one hand and tasks such as audit and research, which are one step removed from the clinical encounter (secondary use) on the other. These studies show that when EHRs are used as a formal tool (eg, with structured templates and a requirement for data to be coded), they often slow down and frustrate the clinical encounter but can greatly accelerate secondary uses of clinical data. Accordingly, Greenhalgh et al [<xref ref-type="bibr" rid="ref50">50</xref>] argue that, rather than promising that the EHR will <italic>save time</italic> or <italic>make clinical care more efficient</italic>, a more honest message would be that creating accurate and complete clinical records requires the sacrifice of time and effort by frontline clinical and admin staff, which is (sometimes) justified by more benefits for efficient business processes (eg, billing) governance and research. In other words, the real value of blockchain-enabled health records might rest in their secondary use, enhancing health care administration and medical research rather than in substantially improving clinical care.</p>
      </sec>
      <sec>
        <title>Study Strengths and Limitations</title>
        <p>This study has both empirical and theoretical strengths. Its strengths are 3-fold. First, by focusing attention on the health care sector’s experience in attempting to use blockchain technologies for specific purposes, it fills an important gap in the existing literature by offering a more grounded, evidence-based but theoretically informed appraisal of blockchain’s prospects for transforming health care, unlike the burgeoning academic literature that has focused overwhelmingly on the technology’s <italic>potential</italic> to solve health care problems. Second, it identifies and critically examines a series of complex, multidimensional implementation challenges that must be satisfactorily confronted if blockchain technologies are to be widely taken up within health care contexts, illuminating the nature and dimension of these difficulties by referring to a range of theoretical perspectives. Third, the critique offered here contrasts sharply with the considerable hype that accompanied the emergence of blockchain technologies. It provides a more theoretically and empirically grounded appraisal of the oft-proclaimed radically transformative potential of blockchain technologies in a specific domain, notably within complex health care environments that are typically saturated with technologies, many of which are highly sophisticated and often safety-critical.</p>
        <p>The limitations of the study rest in the lack of publicly available, authoritative data concerning blockchain uptake in health care. Hence, the snapshot provided by the study of current and ongoing industry engagement and experience with blockchain relies heavily on web-based investigations of gray literature, particularly industry publications, to investigate the focus and tenor of discussions about these technologies in health care and the trajectory of their development. This methodological approach was limited in several significant aspects, insofar as it relied on unconfirmed industry sources publicly available on English-language websites as a substantial source of evidence for understanding the current state of blockchain development and implementation in health care contexts. As the accuracy of claims made on public websites is practically impossible to verify and often fails to provide significant financial information about the level of investment or revenue generated (or expected to be generated), the findings on blockchain take-up in the health care sector are not comprehensive, particularly given the growing interest in developing blockchain applications in non–English-speaking countries (eg, China [<xref ref-type="bibr" rid="ref171">171</xref>,<xref ref-type="bibr" rid="ref172">172</xref>] and Japan [<xref ref-type="bibr" rid="ref173">173</xref>]).</p>
        <p>Although significant assurance about the reliability and robustness of the study’s provisional findings was obtained by eliciting feedback from industry experts through the second focus group workshop while cross-checking the validity of these provisional findings against the published insights of industry specialists [<xref ref-type="bibr" rid="ref174">174</xref>-<xref ref-type="bibr" rid="ref176">176</xref>], the findings concerning the state of industry experimentation and maturity offered here are neither authoritative nor comprehensive. Nevertheless, they provide worthwhile insights into the general state of the health care sector’s engagement with blockchain technologies to date, the particular domains and applications in which this engagement is occurring, and the current direction of travel. Accordingly, these findings offer a useful reference point for critical reflection in the context of future investigations of blockchain in health care and beyond.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This paper has demonstrated that the health care sector’s engagement with blockchain technology has grown steadily since 2016, with the most promising activity occurring at the intra- and interorganizational level to enable data sharing and cooperation in health care administration and medical research. Although various blockchain initiatives have appeared in response to the COVID-19 pandemic [<xref ref-type="bibr" rid="ref177">177</xref>], in which the rapid spread of misinformation intensified the importance of ensuring trustworthy health care information management, industry experts suggest that they have not hitherto taken root [<xref ref-type="bibr" rid="ref178">178</xref>]. Contrary to the focus of the academic literature, the health care sector’s engagement with blockchain has not focused primarily on enabling and integrating patient-controlled EHRs into clinical practice. It is in nonclinical contexts that early-stage health care engagement with blockchain is now producing evidence that blockchain-enabled cooperation can create both collective and individual value for network members that is greater than the sum of its parts, generating potentially significant efficiency gains [<xref ref-type="bibr" rid="ref121">121</xref>]. Accordingly, blockchain in health care cannot currently be dismissed as a passing fad. Although scholars of innovation studies have identified various <italic>barriers to innovation</italic> that arise when technological inventions seek to cross the <italic>valley of death</italic> during the development phase of innovation, this literature has tended to treat technological inventions as a <italic>black box</italic>. In contrast, the analysis offered here highlights the importance of attending to the design and functionality of the technology itself and the particular health care contexts and fields of practice into which it might be applied in ways that may deepen and enrich innovation studies literature that has tended toward a high level of generality and abstraction.</p>
        <p>This study identified 6 complex and multidimensional challenges and 3 normative tensions that must be resolved if blockchain technologies are to be made readily implementable in health care. Negotiating and overcoming these challenges and tensions will require considerable commitment, including time, investment, and willingness by health care organizations to take substantial risks, experiment, learn, and share knowledge across the sector. It suggests that the technology’s progress through the development process will be difficult and lengthy. Moreover, as the National Advisory Group on Health Information Technology advised in its 2016 report, “implementing health IT is one of the most complex adaptive changes in the history of healthcare, and perhaps of any industry” [<xref ref-type="bibr" rid="ref179">179</xref>]. Another leading expert observes that “while policy makers are calling for technology to be implemented rapidly and at scale, the reality is that when dealing with the multiple complexities of health and care, it is extremely difficult to go beyond small-scale demonstration projects” [<xref ref-type="bibr" rid="ref85">85</xref>].</p>
        <p>Even if blockchain succeeds in crossing the valley of death, it does not necessarily follow that these technologies will live up to their promise. The underwhelming experience of health IT offers a sobering reminder, with Kellermann and Jones [<xref ref-type="bibr" rid="ref180">180</xref>] noting that despite the increased use of health IT in the United States, with aggregate annual national expenditure on health care growing from US $2 trillion in 2005 to roughly US $2.8 trillion in 2013, the efficiency of patient care is only marginally better. In the United Kingdom, 10 years after the launch of the National Program for IT, which promised to revolutionize care in the English NHS [<xref ref-type="bibr" rid="ref181">181</xref>,<xref ref-type="bibr" rid="ref182">182</xref>], it was described by the UK Secretary of State for Health as a “huge disaster that became impossible to deliver” despite costing £3.66 billion (US $4.84 billion) [<xref ref-type="bibr" rid="ref183">183</xref>,<xref ref-type="bibr" rid="ref184">184</xref>]. These experiences highlight the serious gap between the grand visions of IT’s transformative potential in health care and the fraught nature of implementation, given the inherently complex, dynamic, and context-driven nature of health care. They throw into high relief the inherent difficulties associated with seeking to <italic>hard code</italic> norms into complex sociotechnical systems in ways that that can satisfactorily resolve and mediate a wide variety of often conflicting rights, interests, expectations, norms, and risks associated with information sharing in dynamic, complex but safety-critical health care settings.</p>
        <p>Although the <italic>blockchain for health care promise</italic> is rooted in a belief that blockchain systems will facilitate secure data sharing while enabling more fine-grained management of health care data, thereby creating <italic>more and better data</italic> that will drive improvements across the sector, real-world engagements and experiences with the technology in health care settings to date suggests that blockchain’s core <italic>value proposition</italic> is more nuanced and narrowly framed. Blockchain’s value generally (both within health care and beyond) rests primarily on its capacity to provide an automated, mathematically verifiable, highly secure, and therefore, highly trustworthy record-keeping function. It is this functional capacity that supports the technology’s nascent potential as <italic>middleware</italic>, facilitating various kinds of health care data sharing and exchange, particularly between health care organizations where a lack of social trust rooted in institutional incentives for opportunistic behavior might be replaced with the computational trust that permissioned blockchain systems can provide. In so doing, blockchain systems may enable new forms of cooperation that generate shared value from the pooling of health care data, although whether these networks can develop governance strategies that can successfully and sustainably mediate the relevant interests of network participants remains to be seen.</p>
        <p>However, the difficulties of ensuring that the ledger accurately, systematically, and comprehensively tracks and reflects the real-world phenomenon that it claims to record may mean that the envisaged benefits of blockchain’s automated <italic>track and trace</italic> function may not be fully realized. Computer scientists and mathematicians have long recognized the <italic>garbage in, garbage out</italic> problem: the quality of output is determined by the quality of the input. Blockchain technology cannot guarantee that data arriving at and recorded in the ledger is an accurate, complete, and comprehensive record of the underlying real-world events that it purports to track; however, blockchain advocates typically overlook this critical vulnerability. In other words, although blockchain systems can deliver valuable functionality in terms of automatically and securely recording the handling of data items (for example, when a digital record has been viewed by a particular user), they cannot guarantee the integrity of the underlying data.</p>
        <p>Nevertheless, blockchain’s automated audit function might offer real and significant value because, by creating a highly secure and verifiable record, it offers a vehicle through which organizations can <italic>demonstrate compliance with data handling norms</italic> at scale, thus operating as a form of <italic>RegTech</italic>. In this way, blockchain as middleware can automatically and securely track and record the location and handling of data items. Therefore, it might have real potential to facilitate the <italic>integration</italic> of health data <italic>silos</italic> stored in a variety of locations across multiple organizations using different IT systems [<xref ref-type="bibr" rid="ref185">185</xref>]. The value of this contribution could potentially be significant, reducing costs and improving efficiency, transparency, and security, and could be widely applied across any sector in which sensitive data generation, processing, and sharing occur in large volumes.</p>
        <p>Blockchain is frequently portrayed as offering the potential to deliver radical and positive transformations to many sectors, including health care. This study has identified significant activity within the health care sector aimed at exploring how blockchain technologies might deliver real value. It has been found that the technology is still in its infancy and that the nature and scale of its value to health care remain unproven [<xref ref-type="bibr" rid="ref29">29</xref>]. Experience of early health care sector engagement has shown that the relevant question is not <italic>how can blockchain be used</italic> in health care settings but <italic>under what conditions can blockchain be realistically expected to provide a viable, scalable and efficient solution to a concrete health care problem in real-world health care settings that would add significant value relative to alternative solutions?</italic> In other words, when considering whether to engage with blockchain technologies, organizations must ask themselves whether a blockchain is really necessary to solve the problem at hand or whether other alternative approaches are preferable.</p>
        <p>This shift in mindset is reflected in the divergence between the <italic>rhetoric</italic> of blockchain-enabled health care data sharing, which focuses primarily on the capacity of blockchain technologies to enable the seamless yet secure sharing of patient records that will enhance clinical decision-making, and the <italic>reality of</italic> engagement with blockchain, which has largely avoided clinical contexts. Instead, the most innovative health care blockchain applications have occurred at the interorganizational level, enabling the sharing of administrative data between health care organizations to improve the efficiency of health care administration. The most recent initiatives are aimed at facilitating shared access to the secondary use of patient data for medical research through cooperative endeavors to train algorithmic models on data sets in a secure, privacy-preserving manner.</p>
        <p>However, to succeed in this endeavor, there remain very significant challenges associated with achieving social trust and cooperation, including the need for the effective and legitimate governance of blockchain networks, that no amount of technological sophistication or hard-coded solutions can, on their own, satisfactorily resolve. It remains to be seen whether these and other tensions inherent in these incipient forms of blockchain-enabled <italic>coopetition</italic> between health care organizations will be satisfactorily overcome and whether blockchain applications in health care might be characterized as <italic>radical</italic> or <italic>incremental</italic> technologies. Accordingly, the possibility of blockchain technology precipitating a <italic>revolution</italic> in the delivery of health care of the kind envisaged by blockchain for health care advocates appears to have been exaggerated. Nevertheless, there are real prospects of using blockchain in ways that could lead to genuine health care improvements. However, progress toward this goal is likely to occur slowly, incrementally, and more <italic>by stealth</italic> rather than through radical and rapid <italic>disruption</italic> over a short period and—at least in the first instance—likely to be concentrated across a much narrower range of applications than the blockchain for health care promise suggests.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Summary of systematic literature reviews of blockchain in health care.</p>
        <media xlink:href="jmir_v23i12e24109_app1.docx" xlink:title="DOCX File , 23 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Summary of method and findings mapping blockchain in health care by Motsi-Omoijiade and Kharlamov [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
        <media xlink:href="jmir_v23i12e24109_app2.docx" xlink:title="DOCX File , 53 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Focus group participants and proceedings.</p>
        <media xlink:href="jmir_v23i12e24109_app3.docx" xlink:title="DOCX File , 26 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">B2B</term>
          <def>
            <p>business-to-business</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">HIMSS</term>
          <def>
            <p>Healthcare Information Management and Systems Society</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">IT</term>
          <def>
            <p>information technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">ProCredEx</term>
          <def>
            <p>Professionals Credentials Exchange</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">TAM</term>
          <def>
            <p>technology acceptance model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The author gratefully acknowledges funding support from the Wellcome Trust, grant reference number: 210337/Z/18/Z, “Regulating healthcare through blockchain: Mapping the legal, ethical, technical and governance challenges.” The author is grateful for the research and administrative assistance provided by Immaculate Motsi-Omoijiade and Alexander Kharlamov and for the editing and proofreading assistance provided by PhD candidate Nathalie Smuha. The author is also indebted to those who participated in the focus group meetings convened for the purposes of this study, including John Halamka for his support and encouragement. Special thanks are due to colleagues who kindly read and commented on earlier drafts: Atina Krajewska, Muireann Quigley, Natalie Pankova, Barbara Prainsack, and Mark Taylor. All errors remain the author’s own. Further information about the project is available on the web [<xref ref-type="bibr" rid="ref186">186</xref>].</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khezr</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Moniruzzaman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yassine</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Benlamri</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology in healthcare: a comprehensive review and directions for future research</article-title>
          <source>Appl Sci</source>
          <year>2019</year>
          <month>04</month>
          <day>26</day>
          <volume>9</volume>
          <issue>9</issue>
          <fpage>1736</fpage>
          <pub-id pub-id-type="doi">10.3390/app9091736</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>Hölbl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kompara</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kamišalić</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zlatolas</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of the use of blockchain in healthcare</article-title>
          <source>Symmetry</source>
          <year>2018</year>
          <month>10</month>
          <day>10</day>
          <volume>10</volume>
          <issue>10</issue>
          <fpage>470</fpage>
          <pub-id pub-id-type="doi">10.3390/sym10100470</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ohno-Machado</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Blockchain distributed ledger technologies for biomedical and health care applications</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>1211</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29016974"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocx068</pub-id>
          <pub-id pub-id-type="medline">29016974</pub-id>
          <pub-id pub-id-type="pii">4108087</pub-id>
          <pub-id pub-id-type="pmcid">PMC6080687</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <source>Blockchain for Healthcare Today</source>
          <access-date>2021-01-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blockchainhealthcaretoday.com">https://blockchainhealthcaretoday.com</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lenz</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology use cases in healthcare</article-title>
          <source>Advances in Computers</source>
          <year>2018</year>
          <publisher-loc>Amsterdam</publisher-loc>
          <publisher-name>Elsevier</publisher-name>
          <fpage>1</fpage>
          <lpage>41</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Durneva</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cousins</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The current state of research, challenges, and future research directions of blockchain technology in patient care: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>07</month>
          <day>20</day>
          <volume>22</volume>
          <issue>7</issue>
          <fpage>e18619</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/7/e18619/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18619</pub-id>
          <pub-id pub-id-type="medline">32706668</pub-id>
          <pub-id pub-id-type="pii">v22i7e18619</pub-id>
          <pub-id pub-id-type="pmcid">PMC7399962</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gaynor</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tuttle-Newhall</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Parker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Adoption of blockchain in health care</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>09</month>
          <day>17</day>
          <volume>22</volume>
          <issue>9</issue>
          <fpage>e17423</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/9/e17423/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17423</pub-id>
          <pub-id pub-id-type="medline">32940618</pub-id>
          <pub-id pub-id-type="pii">v22i9e17423</pub-id>
          <pub-id pub-id-type="pmcid">PMC7530694</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mello</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Adler-Milstein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Savage</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Legal barriers to the growth of health information exchange-boulders or pebbles?</article-title>
          <source>Milbank Q</source>
          <year>2018</year>
          <month>12</month>
          <volume>96</volume>
          <issue>1</issue>
          <fpage>110</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.1111/1468-0009.12313</pub-id>
          <pub-id pub-id-type="medline">29504197</pub-id>
          <pub-id pub-id-type="pmcid">PMC5835678</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Biot</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Massart</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pecuchet</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Data sharing is the key to innovation in healthcare</article-title>
          <source>MIT Technology Review</source>
          <year>2019</year>
          <access-date>2021-12-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.technologyreview.com/s/614442/data-sharing-is-key-to-innovation-in-health-care/">https://www.technologyreview.com/s/614442/data-sharing-is-key-to-innovation-in-health-care/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Orcutt</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Why the CDC wants in on blockchain</article-title>
          <source>MIT Technology Review</source>
          <year>2017</year>
          <access-date>2021-12-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.technologyreview.com/s/608959/why-the-cdc-wants-in-on-blockchain/">https://www.technologyreview.com/s/608959/why-the-cdc-wants-in-on-blockchain/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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="ref13">
        <label>13</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Metcalf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hooper</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cahana</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dhillon</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Introduction</article-title>
          <source>Blockchain in Healthcare</source>
          <year>2019</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
          <fpage>3</fpage>
          <lpage>24</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Halamka</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lippman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ekblaw</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The potential for blockchain to transform electronic health records</article-title>
          <source>Harvard Business Review</source>
          <year>2017</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hbr.org/2017/03/the-potential-for-blockchain-to-transform-electronic-health-records">https://hbr.org/2017/03/the-potential-for-blockchain-to-transform-electronic-health-records</ext-link>
          </comment>
        </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>Adler-Milstein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The number of health information exchange efforts is declining, leaving the viability of broad clinical data exchange uncertain</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2016</year>
          <month>07</month>
          <day>01</day>
          <volume>35</volume>
          <issue>7</issue>
          <fpage>1278</fpage>
          <lpage>85</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1377/hlthaff.2015.1439"/>
          </comment>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2015.1439</pub-id>
          <pub-id pub-id-type="medline">27385245</pub-id>
          <pub-id pub-id-type="pii">35/7/1278</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El Emam</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rodgers</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Malin</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Anonymising and sharing individual patient data</article-title>
          <source>Br Med J</source>
          <year>2015</year>
          <month>03</month>
          <day>20</day>
          <volume>350</volume>
          <issue>mar20 1</issue>
          <fpage>h1139</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25794882"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.h1139</pub-id>
          <pub-id pub-id-type="medline">25794882</pub-id>
          <pub-id pub-id-type="pmcid">PMC4707567</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Engelhardt</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Hitching healthcare to the chain: an introduction to blockchain technology in the healthcare sector</article-title>
          <source>Technol Innovat Manag Rev (10)</source>
          <year>2017</year>
          <volume>7</volume>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://doi.org/10.22215/timreview/1111"/>
          </comment>
          <pub-id pub-id-type="doi">10.22215/timreview/1111</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Agbo</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Mahmoud</surname>
              <given-names>QH</given-names>
            </name>
            <name name-style="western">
              <surname>Eklund</surname>
              <given-names>JM</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>
          <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="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yaga</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mell</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Roby</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Scarfone</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology overview</article-title>
          <source>National Institute of Standards and Technology, Gaithersburg</source>
          <year>2018</year>
          <access-date>2021-12-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://nvlpubs.nist.gov/nistpubs/ir/2018/nist.ir.8202.pdf">https://nvlpubs.nist.gov/nistpubs/ir/2018/nist.ir.8202.pdf</ext-link>
          </comment>
        </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>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Macfarlane</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bate</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kyriakidou</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Diffusion of innovations in service organizations: systematic review and recommendations</article-title>
          <source>Milbank Q</source>
          <year>2004</year>
          <volume>82</volume>
          <issue>4</issue>
          <fpage>581</fpage>
          <lpage>629</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/15595944"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/j.0887-378X.2004.00325.x</pub-id>
          <pub-id pub-id-type="medline">15595944</pub-id>
          <pub-id pub-id-type="pii">MILQ325</pub-id>
          <pub-id pub-id-type="pmcid">PMC2690184</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Motsi-Omoijiade</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kharlamov</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>De Gregorio</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Pollicino</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for healthcare applications and use-cases</article-title>
          <source>Blockchain and Public Law</source>
          <year>2021</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>Edward Elgar Publishing</publisher-name>
          <fpage>136</fpage>
          <lpage>89</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <source>E-Estonia Heathcare</source>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://e-estonia.com/solutions/healthcare/">https://e-estonia.com/solutions/healthcare/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>An update on healthcare ICOs</article-title>
          <source>Bertcmiller</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bertcmiller.com/2019/02/24/An-update-on-healthcare-ICOs.html">https://bertcmiller.com/2019/02/24/An-update-on-healthcare-ICOs.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>Healthcare and biomedical blockchains</article-title>
          <source>Centre for Biomedical Blockchain Research</source>
          <year>2019</year>
          <access-date>2020-10-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://db.biomedicalblockchain.org/companies_detail">https://db.biomedicalblockchain.org/companies_detail</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coravos</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Open-source landscape map for healthcare-related blockchains</article-title>
          <source>GitHub</source>
          <year>2018</year>
          <access-date>2018-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/acoravos/healthcare-blockchains">https://github.com/acoravos/healthcare-blockchains</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>2019-10-20</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="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mire</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>40 Startups using blockchain to transform healthcare</article-title>
          <source>Disruptor Daily</source>
          <year>2018</year>
          <access-date>2019-10-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.disruptordaily.com/blockchain-market-map-healthcare/">https://www.disruptordaily.com/blockchain-market-map-healthcare/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>Listing of Healthcare ICOs (Initial Coin/Cryptoasset Offerings) / Token Offerings</article-title>
          <source>Healthcare ICOs/Tokens-Medium</source>
          <year>2018</year>
          <access-date>2021-12-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://docs.google.com/spreadsheets/d/1TANOZmuYtVhyn1C9PV6YLsOBlQNOEOBExB7u2_Kkork/edit#gid=0">https://docs.google.com/spreadsheets/d/1TANOZmuYtVhyn1C9PV6YLsOBlQNOEOBExB7u2_Kkork/edit#gid=0</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>TK</given-names>
            </name>
            <name name-style="western">
              <surname>Kuo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gummadi</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Clauson</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Church</surname>
              <given-names>G</given-names>
            </name>
            <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>Barkovich</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Palombini</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>'Fit-for-purpose?' - challenges and opportunities for applications of blockchain technology in the future of healthcare</article-title>
          <source>BMC Med</source>
          <year>2019</year>
          <month>03</month>
          <day>27</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>68</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-019-1296-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12916-019-1296-7</pub-id>
          <pub-id pub-id-type="medline">30914045</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12916-019-1296-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6436239</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metcalf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hooper</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cahana</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dhillon</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <source>Blockchain in Healthcare: Innovations That Empower Patients, Connect Professionals and Improve Care</source>
          <year>2019</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vigna</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Casey</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <source>The Truth Machine: The Blockchain and the Future of Everything</source>
          <year>2019</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Picador</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El-Gazzar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Stendal</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in health care: hope or hype?</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>07</month>
          <day>10</day>
          <volume>22</volume>
          <issue>7</issue>
          <fpage>e17199</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/7/e17199"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17199</pub-id>
          <pub-id pub-id-type="medline">32673219</pub-id>
          <pub-id pub-id-type="pii">v22i7e17199</pub-id>
          <pub-id pub-id-type="pmcid">PMC7382018</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abernathy</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Utterback</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Patterns of industrial innovation</article-title>
          <source>Technol Rev</source>
          <year>1978</year>
          <volume>80</volume>
          <issue>7</issue>
          <fpage>40</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://scholar.google.com/citations?view_op=view_citation&#38;hl=en&#38;user=ygiHPoQAAAAJ&#38;citation_for_view=ygiHPoQAAAAJ:D03iK_w7-QYC"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rosenberg</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Nathan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <source>Inside the Black Box: Technology and Economics</source>
          <year>1982</year>
          <publisher-loc>Cambridge</publisher-loc>
          <publisher-name>Cambridge University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sahal</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Technological guideposts and innovation avenues</article-title>
          <source>Res Policy</source>
          <year>1985</year>
          <month>4</month>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>61</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1016/0048-7333(85)90015-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bums</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Stalker</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <source>The Management of Innovation</source>
          <year>1994</year>
          <publisher-loc>Oxfordshire, United Kingdom</publisher-loc>
          <publisher-name>Oxford Scholarship Online</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abernathy</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <source>The Productivity Dilemma: Roadblock to Innovation in the Automobile Industry</source>
          <year>1978</year>
          <publisher-loc>Baltimore, MD</publisher-loc>
          <publisher-name>Johns Hopkins University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Biemans</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Huizingh</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bitran</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Conn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gernreich</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Heber</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Huizingh</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kokshagina</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Torkkeli</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mapping the valley of death ecosystem</article-title>
          <source>Proceedings of ISPIM Connects Bangkok: Partnering for an Innovative Community</source>
          <year>2020</year>
          <publisher-loc>Bangkok</publisher-loc>
          <publisher-name>ISPIM</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Markham</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Moving technologies from lab to market</article-title>
          <source>Res Technol Manag</source>
          <year>2016</year>
          <month>01</month>
          <day>27</day>
          <volume>45</volume>
          <issue>6</issue>
          <fpage>31</fpage>
          <lpage>42</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1080/08956308.2002.11671531"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/08956308.2002.11671531</pub-id>
        </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>Helmstetter</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Bridging the valley of death between Ag Innovation Funding and market adoption</article-title>
          <source>Forbes</source>
          <year>2018</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.forbes.com/sites/michaelhelmstetter/2018/08/03/bridging-the-valley-of-death-between-innovation-funding-and-market-adoption/">https://www.forbes.com/sites/michaelhelmstetter/2018/08/03/bridging-the-valley-of-death-between-innovation-funding-and-market-adoption/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Broens</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Huis in't Veld</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Vollenbroek-Hutten</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Hermens</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>van Halteren</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Nieuwenhuis</surname>
              <given-names>LJ</given-names>
            </name>
          </person-group>
          <article-title>Determinants of successful telemedicine implementations: a literature study</article-title>
          <source>J Telemed Telecare</source>
          <year>2007</year>
          <volume>13</volume>
          <issue>6</issue>
          <fpage>303</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1258/135763307781644951"/>
          </comment>
          <pub-id pub-id-type="doi">10.1258/135763307781644951</pub-id>
          <pub-id pub-id-type="medline">17785027</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parrish</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Grimes</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mochly-Rosen</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Surviving in the valley of death: opportunities and challenges in translating academic drug discoveries</article-title>
          <source>Annu Rev Pharmacol Toxicol</source>
          <year>2019</year>
          <month>01</month>
          <day>06</day>
          <volume>59</volume>
          <fpage>405</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1146/annurev-pharmtox-010818-021625"/>
          </comment>
          <pub-id pub-id-type="doi">10.1146/annurev-pharmtox-010818-021625</pub-id>
          <pub-id pub-id-type="medline">30208282</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Branscomb</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Morse</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Managing technical risk: Understanding private sector decision making on early stage technology-based projects</article-title>
          <source>Prepared for U.S. Department of Commerce Economic Assessment Office, Advanced Technology Program, National Institute of Standards and Technology, NIST GCR 00-787</source>
          <year>2000</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.atp.nist.gov/eao/gcr_787.pdf">http://www.atp.nist.gov/eao/gcr_787.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sandberg</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Aarikka-Stenroos</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>What makes it so difficult? A systematic review on barriers to radical innovation</article-title>
          <source>Ind Mark Manag</source>
          <year>2014</year>
          <month>11</month>
          <volume>43</volume>
          <issue>8</issue>
          <fpage>1293</fpage>
          <lpage>305</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.indmarman.2014.08.003"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.indmarman.2014.08.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grisot</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hanseth</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Thorseng</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Innovation of, in, on infrastructures: articulating the role of architecture in information infrastructure evolution</article-title>
          <source>J Assoc Info Syst</source>
          <year>2014</year>
          <month>04</month>
          <volume>15</volume>
          <issue>4</issue>
          <fpage>197</fpage>
          <lpage>219</lpage>
          <pub-id pub-id-type="doi">10.17705/1jais.00357</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Slayton</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Spinardi</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Radical innovation in scaling up: Boeing’s Dreamliner and the challenge of socio-technical transitions</article-title>
          <source>Technovation</source>
          <year>2016</year>
          <month>01</month>
          <volume>47</volume>
          <fpage>47</fpage>
          <lpage>58</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.technovation.2015.08.004"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.technovation.2015.08.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Timmermans</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Orders and their others: on the constitution of universalities in medical work</article-title>
          <source>Configurations</source>
          <year>2000</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.1353/con.2000.0001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maniatopoulos</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Llewellyn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Boyd</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Moving beyond local practice: reconfiguring the adoption of a breast cancer diagnostic technology</article-title>
          <source>Soc Sci Med</source>
          <year>2015</year>
          <month>04</month>
          <volume>131</volume>
          <fpage>98</fpage>
          <lpage>106</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.socscimed.2015.02.036"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.socscimed.2015.02.036</pub-id>
          <pub-id pub-id-type="medline">25769108</pub-id>
          <pub-id pub-id-type="pii">S0277-9536(15)00128-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>On distribution, drift and the electronic medical record</article-title>
          <source>Proceedings of the Fifth European Conference on Computer Supported Cooperative Work</source>
          <year>1997</year>
          <conf-name>Fifth European Conference on Computer Supported Cooperative Work</conf-name>
          <conf-date>Sept 7-11, 1997</conf-date>
          <conf-loc>Lancaster, UK</conf-loc>
          <fpage>141</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="doi">10.1007/978-94-015-7372-6_10</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Potts</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bark</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Swinglehurst</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Tensions and paradoxes in electronic patient record research: a systematic literature review using the meta-narrative method</article-title>
          <source>Milbank Q</source>
          <year>2009</year>
          <month>12</month>
          <volume>87</volume>
          <issue>4</issue>
          <fpage>729</fpage>
          <lpage>88</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20021585"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/j.1468-0009.2009.00578.x</pub-id>
          <pub-id pub-id-type="medline">20021585</pub-id>
          <pub-id pub-id-type="pii">MILQ578</pub-id>
          <pub-id pub-id-type="pmcid">PMC2888022</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <article-title>EU-funded projects in blockchain technology</article-title>
          <source>European Commission</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital-strategy.ec.europa.eu/en/news/eu-funded-projects-blockchain-technology">https://digital-strategy.ec.europa.eu/en/news/eu-funded-projects-blockchain-technology</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>UK Government-backed accelerator will sponsor blockchain startups</article-title>
          <source>Coindesk</source>
          <year>2018</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.coindesk.com/uk-government-backed-accelerator-will-sponsor-blockchain-startups;">https://www.coindesk.com/uk-government-backed-accelerator-will-sponsor-blockchain-startups;</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuraitis</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>The biggest trend you've probably never heard of: a status report on 138 healthcare ICOs</article-title>
          <source>The Health Care Blog</source>
          <year>2018</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://thehealthcareblog.com/blog/2018/09/24/the-biggest-trend-youve-probably-never-heard-of-a-status-report-on-138-healthcare-icos/">https://thehealthcareblog.com/blog/2018/09/24/the-biggest-trend-youve-probably-never-heard-of-a-status-report-on-138-healthcare-icos/</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>John</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>State of blockchain Q3: the professionals have moved in with VC investments soaring to an all time high</article-title>
          <source>Outlier Ventures</source>
          <year>2018</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://outlierventures.io/research/state-of-blockchains-q3-the-professionals-have-moved-in-with-vc-investments-soaring-to-all-time-high/">https://outlierventures.io/research/state-of-blockchains-q3-the-professionals-have-moved-in-with-vc-investments-soaring-to-all-time-high/</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>Miller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in healthcare in 2019</article-title>
          <source>Bertcmiller</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bertcmiller.com/2019/12/29/blockchain-healthcare-2019.html">https://www.bertcmiller.com/2019/12/29/blockchain-healthcare-2019.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Clauson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Breeden</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Davidson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Leveraging Blockchain Technology to Enhance Supply Chain Management in Healthcare: an exploration of challenges and opportunities in the health supply chain</article-title>
          <source>Blockchain Healthc Today</source>
          <year>2018</year>
          <month>03</month>
          <day>23</day>
          <volume>1</volume>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.30953/bhty.v1.20"/>
          </comment>
          <pub-id pub-id-type="doi">10.30953/bhty.v1.20</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The seven major consortia (in chronological order)</article-title>
          <source>Hashed Health Newsletter</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hashedhealth.com/consortia-july-2019-2/">https://hashedhealth.com/consortia-july-2019-2/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The 2018 stories that shaped blockchain in healthcare</article-title>
          <source>Hashed Health Newsletter</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hashedhealth.com/2018_hhighlights/">https://hashedhealth.com/2018_hhighlights/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <article-title>DCSMA Pilot Project</article-title>
          <source>US Food and Drug Administration</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa/dscsa-pilot-project-program">https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa/dscsa-pilot-project-program</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chien</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>De Jesus</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Dods</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Alekseyev</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Shoda</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shieh</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The last mile: DSCSA solution through blockchain technology: drug tracking, tracing, and verification at the last mile of the pharmaceutical supply chain with BRUINchain</article-title>
          <source>Blockchain Healthc Today</source>
          <year>2020</year>
          <month>03</month>
          <day>12</day>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.30953/bhty.v3.134"/>
          </comment>
          <pub-id pub-id-type="doi">10.30953/bhty.v3.134</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Iyengar-Emens</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Blockchain to secure a more personalized pharma</article-title>
          <source>Genet Eng Biotechnol News</source>
          <year>2019</year>
          <month>01</month>
          <volume>39</volume>
          <issue>1</issue>
          <fpage>27</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1089/gen.39.01.08"/>
          </comment>
          <pub-id pub-id-type="doi">10.1089/gen.39.01.08</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Subramanian</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Chaudhuri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kayikci</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Blockchain applications in health care supply chain</article-title>
          <source>Blockchain and Supply Chain Logistics</source>
          <year>2020</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Palgrave Pivot</publisher-name>
          <fpage>31</fpage>
          <lpage>8</lpage>
        </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>Walport</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>FinTech futures: The UK as a world leader in financial technologies</article-title>
          <source>Report to UK Government Office for Science</source>
          <year>2015</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/413095/gs-15-3-fintech-futures.pdf">https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/413095/gs-15-3-fintech-futures.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yeung</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Regulation by blockchain: the emerging battle for supremacy between the code                                        Law and Code                                        Law</article-title>
          <source>Modern Law Rev</source>
          <year>2019</year>
          <month>03</month>
          <day>05</day>
          <volume>82</volume>
          <issue>2</issue>
          <fpage>207</fpage>
          <lpage>39</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1111/1468-2230.12399"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/1468-2230.12399</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fassenbender</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Pfizer, Biogen-led blockchain project demonstrates proof of concept in pursuit of a better supply chain</article-title>
          <source>Outsourcing-Pharma</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.outsourcing-pharma.com/Article/2019/08/14/Clinical-Supply-Blockchain-Working-Group-led-by-Pfizer-and-Biogen-completes-proof-of-concept-project">https://www.outsourcing-pharma.com/Article/2019/08/14/Clinical-Supply-Blockchain-Working-Group-led-by-Pfizer-and-Biogen-completes-proof-of-concept-project</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Henderson</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in research, from business to personal</article-title>
          <source>Applied Clinical Trials (11)</source>
          <year>2018</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://search.proquest.com/scholarly-journals/blockchain-research-business-personal/docview/2153565380/se-2?accountid=8630">https://search.proquest.com/scholarly-journals/blockchain-research-business-personal/docview/2153565380/se-2?accountid=8630</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="web">
          <source>Synaptic Health Alliance</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.synaptichealthalliance.com/project">https://www.synaptichealthalliance.com/project</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Begando</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Metcalf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hooper</surname>
              <given-names>m</given-names>
            </name>
            <name name-style="western">
              <surname>Cahana</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dhillon</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Developing a professional credentials exchange levering distributed ledger technology?</article-title>
          <source>Blockchain in Healthcare</source>
          <year>2019</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
          <fpage>3</fpage>
          <lpage>24</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>See</surname>
              <given-names>CJ</given-names>
            </name>
          </person-group>
          <article-title>How ProCredEx is leveraging blockchain to speed up credentialing</article-title>
          <source>Mobile Health News</source>
          <year>2018</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mobihealthnews.com/content/how-procredex-leveraging-blockchain-speed-credentialing">https://www.mobihealthnews.com/content/how-procredex-leveraging-blockchain-speed-credentialing</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Armstrong</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Bitcoin technology could take a bite out of NHS data problem</article-title>
          <source>Br Med J</source>
          <year>2018</year>
          <month>05</month>
          <day>08</day>
          <fpage>k1996</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1136/bmj.k1996"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.k1996</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="web">
          <source>National Institute for Health and Care Excellence (NICE)</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nice.org.uk/">https://www.nice.org.uk/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="web">
          <article-title>The NHS Long Term Plan</article-title>
          <source>National Health Service</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.longtermplan.nhs.uk/wp-content/uploads/2019/08/nhs-long-term-plan-version-1.2.pdf">https://www.longtermplan.nhs.uk/wp-content/uploads/2019/08/nhs-long-term-plan-version-1.2.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bourne</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Six Questions with Sam Shah, Director of Digital Development, NHS England</article-title>
          <source>Blockchain Expo World Series</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.blockchain-expo.com/2019/02/blockchain/blockchain-expo-global-nhs/">https://www.blockchain-expo.com/2019/02/blockchain/blockchain-expo-global-nhs/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="web">
          <source>Dovetail Labs</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dovetaillabs.com/">https://dovetaillabs.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="web">
          <article-title>Acquisition of Dovetail Digital Limited</article-title>
          <source>EMIS Group</source>
          <year>2018</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.emisgroupplc.com/news-and-media/news/acquisition-of-dovetail-digital-limited/">https://www.emisgroupplc.com/news-and-media/news/acquisition-of-dovetail-digital-limited/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="web">
          <article-title>World’s first blockchain-supported Personal Care Record Platform launched by Guardtime and partners to up to 30 million NHS patients in the UK</article-title>
          <source>Guardtime</source>
          <year>2018</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://guardtime.com/blog/world-s-first-blockchain-supported-personal-care-record-platform-launched-by-guardtime-and-partners">https://guardtime.com/blog/world-s-first-blockchain-supported-personal-care-record-platform-launched-by-guardtime-and-partners</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="web">
          <article-title>Medicalchain announces partnership with the Grove Medical Group</article-title>
          <source>Journal of mHealth</source>
          <year>2018</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://thejournalofmhealth.com/medicalchain-announces-partnership-groves-medical-group/">https://thejournalofmhealth.com/medicalchain-announces-partnership-groves-medical-group/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="web">
          <article-title>Medicalchain and Better by Marrand announce partnership</article-title>
          <source>Medicalchain</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medicalchain.com/en/medicalchain-and-better-by-marand-announce-partnership/">https://medicalchain.com/en/medicalchain-and-better-by-marand-announce-partnership/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Passerat-Palmbach</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Farnan</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gross</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Flannery</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Gleim</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-orchestrated Federated Learning architecture for healthcare consortia</article-title>
          <source>arXiv</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1910.12603">https://arxiv.org/abs/1910.12603</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <source>Why federated learning is important</source>
          <year>2020</year>
          <access-date>2021-12-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bertcmiller.com/2020/05/17/why-federated-learning-is-important.html">https://bertcmiller.com/2020/05/17/why-federated-learning-is-important.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Swinglehurst</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Stones</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Rethinking resistance to ‘big IT’: a sociological study of why and when healthcare staff do not use nationally mandated information and communication technologies</article-title>
          <source>Health Services and Delivery Research</source>
          <year>2014</year>
          <publisher-loc>Southampton (UK)</publisher-loc>
          <publisher-name>NIHR Journals Library</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>MacFarlane</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Peacock</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Adopting and assimilating new non-pharmaceutical technologies into health care: a systematic review</article-title>
          <source>J Health Serv Res Policy</source>
          <year>2010</year>
          <month>10</month>
          <volume>15</volume>
          <issue>4</issue>
          <fpage>243</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1258/jhsrp.2010.009137"/>
          </comment>
          <pub-id pub-id-type="doi">10.1258/jhsrp.2010.009137</pub-id>
          <pub-id pub-id-type="medline">20592046</pub-id>
          <pub-id pub-id-type="pii">jhsrp.2010.009137</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Vijayaraghavan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell-Richards</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ramoutar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Collard</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hodkinson</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Real-world implementation of video outpatient consultations at macro, meso, and micro levels: mixed-method study</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>12</month>
          <day>17</day>
          <volume>20</volume>
          <issue>4</issue>
          <fpage>e150</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2018/4/e150/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9897</pub-id>
          <pub-id pub-id-type="medline">29625956</pub-id>
          <pub-id pub-id-type="pmcid">PMC5930173</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>A'Court</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hinder</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fahy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Beyond Adoption: A New Framework for Theorizing and Evaluating Nonadoption, Abandonment, and Challenges to the Scale-Up, Spread, and Sustainability of Health and Care Technologies</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>e367</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2017/11/e367/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8775</pub-id>
          <pub-id pub-id-type="medline">29092808</pub-id>
          <pub-id pub-id-type="pii">v19i11e367</pub-id>
          <pub-id pub-id-type="pmcid">PMC5688245</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brynjolfsson</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The productivity paradox of information technology</article-title>
          <source>Commun ACM</source>
          <year>1993</year>
          <month>12</month>
          <volume>36</volume>
          <issue>12</issue>
          <fpage>66</fpage>
          <lpage>77</lpage>
          <pub-id pub-id-type="doi">10.1145/163298.163309</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Fahy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The bright elusive butterfly of value in health technology development comment on "Providing value to new health technology: the early contribution of entrepreneurs, investors, and regulatory agencies"</article-title>
          <source>Int J Health Policy Manag</source>
          <year>2018</year>
          <month>01</month>
          <day>01</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>81</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29325407"/>
          </comment>
          <pub-id pub-id-type="doi">10.15171/ijhpm.2017.65</pub-id>
          <pub-id pub-id-type="medline">29325407</pub-id>
          <pub-id pub-id-type="pmcid">PMC5745872</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in health care innovation: literature review and case study from a business ecosystem perspective</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>08</month>
          <day>31</day>
          <volume>22</volume>
          <issue>8</issue>
          <fpage>e19480</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/8/e19480/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19480</pub-id>
          <pub-id pub-id-type="medline">32865501</pub-id>
          <pub-id pub-id-type="pii">v22i8e19480</pub-id>
          <pub-id pub-id-type="pmcid">PMC7490679</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hau</surname>
              <given-names>YS</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>MC</given-names>
            </name>
          </person-group>
          <article-title>Attitudes toward blockchain technology in managing medical information: survey study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>12</month>
          <day>09</day>
          <volume>21</volume>
          <issue>12</issue>
          <fpage>e15870</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/12/e15870/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15870</pub-id>
          <pub-id pub-id-type="medline">31815676</pub-id>
          <pub-id pub-id-type="pii">v21i12e15870</pub-id>
          <pub-id pub-id-type="pmcid">PMC6928691</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Ji</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Perspectives of patients, health care professionals, and developers toward blockchain-based health information exchange: qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>11</month>
          <day>13</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>e18582</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/11/e18582/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18582</pub-id>
          <pub-id pub-id-type="medline">33185553</pub-id>
          <pub-id pub-id-type="pii">v22i11e18582</pub-id>
          <pub-id pub-id-type="pmcid">PMC7695529</pub-id>
        </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>Bass</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Healthcare blockchain dreams: 5 things people thought would happen by 2020</article-title>
          <source>Hashed Health</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hashedhealth.com/5-things-by-2020/">https://hashedhealth.com/5-things-by-2020/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="web">
          <article-title>Considerations for Policymakers: The Application of Blockchain to Healthcare</article-title>
          <source>HIMSS</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/considerations-policymakers-application-blockchain-technology-healthcare">https://www.himss.org/resources/considerations-policymakers-application-blockchain-technology-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Finck</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <source>Blockchain Regulation and Governance in Europe</source>
          <year>2018</year>
          <publisher-loc>Cambridge University Press</publisher-loc>
          <publisher-name>Cambridge</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Werbach</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Trustless trust</article-title>
          <source>SSRN J</source>
          <year>2016</year>
          <fpage>31</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ssrn"/>
          </comment>
          <pub-id pub-id-type="doi">10.2139/ssrn.2844409</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Szabo</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Formalizing and securing relationships on public networks</article-title>
          <source>First Monday</source>
          <year>1997</year>
          <volume>2</volume>
          <issue>9</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.uic.edu/ojs/index.php/fm/article/view/548"/>
          </comment>
          <pub-id pub-id-type="doi">10.5210/fm.v2i9.548</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arner</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Barberis</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Buckey</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>FinTech, RegTech, and the reconceptualization of financial regulation</article-title>
          <source>Nw J Int'l L &#38; Bus</source>
          <year>2017</year>
          <volume>37</volume>
          <fpage>371</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://scholarlycommons.law.northwestern.edu/njilb/vol37/iss3/2/"/>
          </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>Walport</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Distributed ledger technology: beyond block chain</article-title>
          <source>UK Government Office for Science</source>
          <year>2016</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/government/news/distributed-ledger-technology-beyond-block-chain">https://www.gov.uk/government/news/distributed-ledger-technology-beyond-block-chain</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>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Vijayaraghavan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stones</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Infrastructure revisited: an ethnographic case study of how health information infrastructure shapes and constrains technological innovation</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>12</month>
          <day>19</day>
          <volume>21</volume>
          <issue>12</issue>
          <fpage>e16093</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/12/e16093/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/16093</pub-id>
          <pub-id pub-id-type="medline">31855184</pub-id>
          <pub-id pub-id-type="pii">v21i12e16093</pub-id>
          <pub-id pub-id-type="pmcid">PMC6940857</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>Shull</surname>
              <given-names>JG</given-names>
            </name>
          </person-group>
          <article-title>Digital health and the state of interoperable electronic health records</article-title>
          <source>JMIR Med Inform</source>
          <year>2019</year>
          <month>11</month>
          <day>01</day>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>e12712</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2019/4/e12712/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12712</pub-id>
          <pub-id pub-id-type="medline">31682583</pub-id>
          <pub-id pub-id-type="pii">v7i4e12712</pub-id>
          <pub-id pub-id-type="pmcid">PMC6913749</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="web">
          <article-title>Interoperability and blockchain</article-title>
          <source>HIMSS (No longer open access on 15.1.21)</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/interoperability-and-blockchain-healthcare">https://www.himss.org/interoperability-and-blockchain-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oosterwijk</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Determining the measures of success for interoperability</article-title>
          <source>HIMSS</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/determining-measures-success-interoperability">https://www.himss.org/resources/determining-measures-success-interoperability</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="web">
          <article-title>Interoperability in healthcare</article-title>
          <source>HIMSS</source>
          <access-date>2021-12-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/interoperability-healthcare">https://www.himss.org/resources/interoperability-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="web">
          <article-title>IHE International</article-title>
          <source>IHE USA</source>
          <access-date>2021-12-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iheusa.org/ihe-international">https://www.iheusa.org/ihe-international</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="web">
          <article-title>HL7</article-title>
          <source>Health Level Seven International</source>
          <access-date>2021-12-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.hl7.org/about/index.cfm?ref=nav">http://www.hl7.org/about/index.cfm?ref=nav</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Lenz</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenbloom</surname>
              <given-names>ST</given-names>
            </name>
          </person-group>
          <article-title>FHIRChain: applying blockchain to securely and scalably share clinical data</article-title>
          <source>Comput Struct Biotechnol J</source>
          <year>2018</year>
          <volume>16</volume>
          <fpage>267</fpage>
          <lpage>78</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2001-0370(18)30037-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.csbj.2018.07.004</pub-id>
          <pub-id pub-id-type="medline">30108685</pub-id>
          <pub-id pub-id-type="pii">S2001-0370(18)30037-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC6082774</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="web">
          <article-title>Beyond Blocks biennial blockchain in healthcare report</article-title>
          <source>Miller R</source>
          <year>2019</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bertcmiller.com/2019/07/07/Beyond-Blocks-Report.html">https://bertcmiller.com/2019/07/07/Beyond-Blocks-Report.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Healthcare blockchain consortia initiatives</article-title>
          <source>Hashed Health Newsletter</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hashedhealth.com/newsletter-july-2019/">https://hashedhealth.com/newsletter-july-2019/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A note on the challenges in interoperability between pharmaceutical supply chain blockchain networks</article-title>
          <source>10 May 2020</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bertcmiller.com/2020/05/10/interoperability-supply-chain-blockchain.html">https://bertcmiller.com/2020/05/10/interoperability-supply-chain-blockchain.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dubovitskaya</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Baig</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Shukla</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zambani</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Swaminathan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jahangir</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Chowdhry</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lachhani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Idnani</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schumacher</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aberer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Stoller</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Ryu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>ACTION-EHR: patient-centric blockchain-based electronic health record data management for cancer care</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>08</month>
          <day>21</day>
          <volume>22</volume>
          <issue>8</issue>
          <fpage>e13598</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/8/e13598/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13598</pub-id>
          <pub-id pub-id-type="medline">32821064</pub-id>
          <pub-id pub-id-type="pii">v22i8e13598</pub-id>
          <pub-id pub-id-type="pmcid">PMC7474412</pub-id>
        </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>Miller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Top posts of 2019</article-title>
          <source>Bertcmiller</source>
          <year>2020</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bertcmiller.com/2019/12/29/blockchain-healthcare-2019.html">https://www.bertcmiller.com/2019/12/29/blockchain-healthcare-2019.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Walch</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Deng</surname>
              <given-names>RH</given-names>
            </name>
          </person-group>
          <article-title>Open-source operational risk: should public blockchains serve as financial market infrastructures?</article-title>
          <source>Handbook of Blockchain, Digital Finance, and Inclusion</source>
          <year>2018</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Academic Press</publisher-name>
          <fpage>243</fpage>
          <lpage>69</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref112">
        <label>112</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vidan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lehdonvirta</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Mine the gap: Bitcoin and the maintenance of trustlessness</article-title>
          <source>New Media Society</source>
          <year>2018</year>
          <month>07</month>
          <day>11</day>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>42</fpage>
          <lpage>59</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1177/1461444818786220"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1461444818786220</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref113">
        <label>113</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dodd</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>The social life of Bitcoin</article-title>
          <source>Theory Cult Society</source>
          <year>2017</year>
          <month>12</month>
          <day>17</day>
          <volume>35</volume>
          <issue>3</issue>
          <fpage>35</fpage>
          <lpage>56</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1177/0263276417746464"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/0263276417746464</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref114">
        <label>114</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>De Fillippi</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Loveluck</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The invisible politics of bitcoin: governance crisis of a decentralized infrastructure</article-title>
          <source>Internet Policy Rev</source>
          <year>2016</year>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>35</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="doi">10.14763/2016.3.427</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref115">
        <label>115</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yeung</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Galindo</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Why do public blockchains need formal and effective internal governance mechanisms?</article-title>
          <source>Eur J Risk Regul</source>
          <year>2019</year>
          <month>09</month>
          <day>18</day>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>359</fpage>
          <lpage>75</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1017/err.2019.42"/>
          </comment>
          <pub-id pub-id-type="doi">10.1017/err.2019.42</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref116">
        <label>116</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Howell</surname>
              <given-names>BE</given-names>
            </name>
            <name name-style="western">
              <surname>Potgieter</surname>
              <given-names>PH</given-names>
            </name>
            <name name-style="western">
              <surname>Sadowski</surname>
              <given-names>BM</given-names>
            </name>
          </person-group>
          <article-title>Governance of blockchain and distributed ledger technology projects</article-title>
          <source>SSRN J</source>
          <year>2020</year>
          <pub-id pub-id-type="doi">10.2139/ssrn.3365519</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rosenbaum</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Anthem will use blockchain to secure medical data for its 40 million members in three years</article-title>
          <source>Forbes</source>
          <year>2019</year>
          <month>12</month>
          <day>12</day>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.forbes.com/sites/leahrosenbaum/2019/12/12/anthem-says-its-40-million-members-will-be-using-blockchain-to-secure-patient-data-in-three-years/?&#38;utm_source=newsletter&#38;utm_medium=email&#38;utm_campaign=healthcare_blockchain_dreams_5_things_people_thought_would_happen_by_2020&#38;utm_term=2020-01-08#9c7015b68377">https://tinyurl.com/2p9dmxxj</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Na</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Is blockchain technology suitable for managing personal health records? Mixed-methods study to test feasibility</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>08</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12533</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2019/2/e12533/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12533</pub-id>
          <pub-id pub-id-type="medline">30735142</pub-id>
          <pub-id pub-id-type="pii">v21i2e12533</pub-id>
          <pub-id pub-id-type="pmcid">PMC6384539</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wüst</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gervais</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Do you need a blockchain?</article-title>
          <source>Proceedings of the Crypto Valley Conference on Blockchain Technology (CVCBT)</source>
          <year>2018</year>
          <month>11</month>
          <day>08</day>
          <conf-name>Crypto Valley Conference on Blockchain Technology (CVCBT)</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Zug, Switzerland</conf-loc>
          <publisher-name>IEE</publisher-name>
          <fpage>45</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.1109/CVCBT.2018.00011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref120">
        <label>120</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garrard</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Fielke</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for trustworthy provenances: a case study in the Australian aquaculture industry</article-title>
          <source>Technol Soc</source>
          <year>2020</year>
          <month>08</month>
          <volume>62</volume>
          <fpage>101298</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.techsoc.2020.101298"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.techsoc.2020.101298</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Houlding</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Metcalf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hooper</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cahana</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dhillon</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Thought leader perspectives: an interview with David Houlding on blockchain, enterpriseHealth</article-title>
          <source>Blockchain in Healthcare</source>
          <year>2019</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
          <fpage>167</fpage>
          <lpage>177</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wachter</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <source>The Digital Doctor: Hope, Hype, and Harm at the Dawn of Medicine's Computer Age</source>
          <year>2015</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>McGraw-Hill Education</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Flannery</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Metcalf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hooper</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cahana</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dhillon</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Standards</article-title>
          <source>Blockchain in Healthcare</source>
          <year>2019</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
          <fpage>233</fpage>
        </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>Mathews</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>McShea</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hanley</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Ravitz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Labrique</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>AB</given-names>
            </name>
          </person-group>
          <article-title>Digital health: a path to validation</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <month>5</month>
          <day>13</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>38</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0111-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0111-3</pub-id>
          <pub-id pub-id-type="medline">31304384</pub-id>
          <pub-id pub-id-type="pii">111</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550273</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="web">
          <article-title>NHS Clinical Digital Safety Team, Standard DCB0129: Clinical Risk Management: its application in the manufacture of health IT systems</article-title>
          <source>NHS Digital</source>
          <year>2020</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dcb0129-clinical-risk-management-its-application-in-the-manufacture-of-health-it-systems">https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dcb0129-clinical-risk-management-its-application-in-the-manufacture-of-health-it-systems</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>NHS Clinical Digital Safety Team</collab>
          </person-group>
          <article-title>Clinical Risk Management: Its Application in the Deployment and Use of Health IT Systems</article-title>
          <source>NHS Digital</source>
          <year>2020</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dcb0160-clinical-risk-management-its-application-in-the-deployment-and-use-of-health-it-systems">https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dcb0160-clinical-risk-management-its-application-in-the-deployment-and-use-of-health-it-systems</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Qin</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gervais</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>An Overview of Blockchain Scalability, Interoperability and Sustainability</source>
          <year>2018</year>
          <publisher-loc>Hochschule Luzern, Imperial College London</publisher-loc>
          <publisher-name>Liquidity Network</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref128">
        <label>128</label>
        <nlm-citation citation-type="web">
          <article-title>Blockchain in healthcare</article-title>
          <source>HIMMS</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/blockchain-healthcare">https://www.himss.org/resources/blockchain-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref129">
        <label>129</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dagher</surname>
              <given-names>GG</given-names>
            </name>
            <name name-style="western">
              <surname>Mohler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Milojkovic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Marella</surname>
              <given-names>PB</given-names>
            </name>
          </person-group>
          <article-title>Ancile: privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology</article-title>
          <source>Sustainable Cities Society</source>
          <year>2018</year>
          <month>05</month>
          <volume>39</volume>
          <fpage>283</fpage>
          <lpage>97</lpage>
          <pub-id pub-id-type="doi">10.1016/j.scs.2018.02.014</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref130">
        <label>130</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sater</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain transforming healthcare data flows</article-title>
          <source>SSRN Network</source>
          <year>2020</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3171005">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3171005</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref131">
        <label>131</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kyratsis</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmad</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Holmes</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Technology adoption and implementation in organisations: comparative case studies of 12 English NHS Trusts</article-title>
          <source>BMJ Open</source>
          <year>2012</year>
          <month>04</month>
          <day>04</day>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>e000872</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=22492183"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2012-000872</pub-id>
          <pub-id pub-id-type="medline">22492183</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2012-000872</pub-id>
          <pub-id pub-id-type="pmcid">PMC3329608</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref132">
        <label>132</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Blockchain insiders tell us why we don't need blockchain</article-title>
          <source>Financial Times</source>
          <year>2018</year>
          <month>06</month>
          <day>14</day>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ft.com/content/469d9dae-3d82-344d-a8f2-e5376dbf4517">https://www.ft.com/content/469d9dae-3d82-344d-a8f2-e5376dbf4517</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref133">
        <label>133</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lehdonvirta</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>The blockchain paradox: why distributed ledger technologies may do little to transform the economy</article-title>
          <source>OII Blog</source>
          <year>2016</year>
          <month>11</month>
          <day>21</day>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.oii.ox.ac.uk/news-events/news/the-blockchain-paradox-why-distributed-ledger-technologies-may-do-little-to-transform-the-economy/">https://www.oii.ox.ac.uk/news-events/news/the-blockchain-paradox-why-distributed-ledger-technologies-may-do-little-to-transform-the-economy/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref134">
        <label>134</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bengtsson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Raza-Ullah</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of research on coopetition: toward a multilevel understanding</article-title>
          <source>Ind Mark Manag</source>
          <year>2016</year>
          <month>08</month>
          <volume>57</volume>
          <fpage>23</fpage>
          <lpage>39</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.indmarman.2016.05.003"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.indmarman.2016.05.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref135">
        <label>135</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brandenburger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nalebuff</surname>
              <given-names>BJ</given-names>
            </name>
          </person-group>
          <source>Co-opetition</source>
          <year>1996</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>HarperCollins Business</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref136">
        <label>136</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Le Roy</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Czakon</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Managing coopetition: the missing link between strategy and performance</article-title>
          <source>Ind Mark Manag</source>
          <year>2016</year>
          <month>02</month>
          <volume>53</volume>
          <fpage>3</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1016/j.indmarman.2015.11.005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref137">
        <label>137</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Le Roy</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Fernandez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chiambaretto</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Fernandez</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Chiambaretto</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Le Roy</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Czakon</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>From strategizing coopetition to managing coopetition</article-title>
          <source>The Routledge Companion to Coopetition Strategies</source>
          <year>2018</year>
          <publisher-loc>Abingdon</publisher-loc>
          <publisher-name>Taylor &#38; Francis</publisher-name>
          <fpage>36</fpage>
          <lpage>46</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref138">
        <label>138</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fernandez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Le Roy</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gnyawali</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Sources and management of tension in co-opetition case evidence from telecommunications satellites manufacturing in Europe</article-title>
          <source>Ind Mark Manag</source>
          <year>2014</year>
          <month>02</month>
          <volume>43</volume>
          <issue>2</issue>
          <fpage>222</fpage>
          <lpage>35</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.indmarman.2013.11.004"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.indmarman.2013.11.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref139">
        <label>139</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Czakon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Le Roy</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gnyawali</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Coopetition strategies: critical issues and research directions</article-title>
          <source>Long Range Plan</source>
          <year>2020</year>
          <month>02</month>
          <volume>53</volume>
          <issue>1</issue>
          <fpage>101948</fpage>
          <pub-id pub-id-type="doi">10.1016/j.lrp.2019.101948</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref140">
        <label>140</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yami</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Castaldo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dagnino</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Le Roy</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <source>Coopetition: Winning Strategies for the 21st Century</source>
          <year>2010</year>
          <publisher-loc>Cheltenham</publisher-loc>
          <publisher-name>Edward Elgar Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref141">
        <label>141</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Avdoshin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pesotskaya</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Blockchain revolution in the healthcare industry</article-title>
          <source>Proceedings of the Future Technologies Conference</source>
          <year>2018</year>
          <conf-name>Future Technologies Conference</conf-name>
          <conf-date>November 15-16, 2018</conf-date>
          <conf-loc>Vancouver</conf-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>626</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.1007/978-3-030-02686-8_47</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref142">
        <label>142</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Catalini</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology for healthcare: facilitating the transition to patient-driven interoperability</article-title>
          <source>Computat Struct Biotechnol J</source>
          <year>2018</year>
          <volume>16</volume>
          <fpage>224</fpage>
          <lpage>30</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2001-0370(18)30028-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.csbj.2018.06.003</pub-id>
          <pub-id pub-id-type="medline">30069284</pub-id>
          <pub-id pub-id-type="pii">S2001-0370(18)30028-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC6068317</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref143">
        <label>143</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schneier</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>There's no good reason to trust blockchain technology</article-title>
          <source>Wired</source>
          <year>2019</year>
          <month>06</month>
          <day>02</day>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.wired.com/story/theres-no-good-reason-to-trust-blockchain-technology/amp">https://www.wired.com/story/theres-no-good-reason-to-trust-blockchain-technology/amp</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref144">
        <label>144</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Freeman</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Soete</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>The Economics of Industrial Innovation</source>
          <year>1997</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Frances Pinter</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref145">
        <label>145</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Winter</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The Schumpeterian trade-off revisited</article-title>
          <source>Am Econ Rev</source>
          <year>1982</year>
          <volume>72</volume>
          <issue>1</issue>
          <fpage>114</fpage>
          <lpage>32</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref146">
        <label>146</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ettlie</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bridges</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>O'Keefe</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Organization strategy and structural differences for radical versus incremental i</article-title>
          <source>Manag Sci</source>
          <year>1984</year>
          <month>06</month>
          <volume>30</volume>
          <issue>6</issue>
          <fpage>682</fpage>
          <lpage>95</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1287/mnsc.30.6.682"/>
          </comment>
          <pub-id pub-id-type="doi">10.1287/mnsc.30.6.682</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref147">
        <label>147</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dewar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dutton</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The adoption of radical and incremental innovations: an empirical analysis</article-title>
          <source>Manag Sci</source>
          <year>1986</year>
          <month>11</month>
          <volume>32</volume>
          <issue>11</issue>
          <fpage>1422</fpage>
          <lpage>33</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1287/mnsc.32.11.1422"/>
          </comment>
          <pub-id pub-id-type="doi">10.1287/mnsc.32.11.1422</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref148">
        <label>148</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tushman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Technological discontinuities and organizational environments</article-title>
          <source>Admin Sci Q</source>
          <year>1986</year>
          <month>09</month>
          <volume>31</volume>
          <issue>3</issue>
          <fpage>439</fpage>
          <lpage>65</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.2307/2392832"/>
          </comment>
          <pub-id pub-id-type="doi">10.2307/2392832</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref149">
        <label>149</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dess</surname>
              <given-names>GG</given-names>
            </name>
            <name name-style="western">
              <surname>Beard</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Dimensions of organizational task environments</article-title>
          <source>Admin Sci Q</source>
          <year>1984</year>
          <month>03</month>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>52</fpage>
          <pub-id pub-id-type="doi">10.2307/2393080</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref150">
        <label>150</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hage</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Theories of Organizations: Form, Process, and Transformation</source>
          <year>1980</year>
          <publisher-loc>Hoboken, New Jersey, United States</publisher-loc>
          <publisher-name>John Wiley &#38; Sons</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref151">
        <label>151</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cooper</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schendel</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Strategic responses to technological threats</article-title>
          <source>Bus Horiz</source>
          <year>1976</year>
          <month>02</month>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>61</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/0007-6813(76)90024-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/0007-6813(76)90024-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref152">
        <label>152</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Daft</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Bureaucratic versus nonbureaucratic structure and the process of innovation and change</article-title>
          <source>Res Sociol Organ</source>
          <year>1982</year>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>129</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1108/s0733-558x20140000042019</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref153">
        <label>153</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rothwell</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Innovation and re-innovation: a role for the user</article-title>
          <source>J Mark Manag</source>
          <year>1986</year>
          <month>01</month>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>109</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1080/0267257X.1986.9964004"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/0267257x.1986.9964004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref154">
        <label>154</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Christensen</surname>
              <given-names>CM</given-names>
            </name>
          </person-group>
          <source>The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail</source>
          <year>2015</year>
          <publisher-loc>Boston</publisher-loc>
          <publisher-name>Harvard Business Review Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref155">
        <label>155</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Henderson</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>KB</given-names>
            </name>
          </person-group>
          <article-title>Architectural innovation: the reconfiguration of existing product technologies and the failure of established firms</article-title>
          <source>Admin Sci Q</source>
          <year>1990</year>
          <month>03</month>
          <volume>35</volume>
          <issue>1</issue>
          <fpage>9</fpage>
          <lpage>30</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.2307/2393549"/>
          </comment>
          <pub-id pub-id-type="doi">10.2307/2393549</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref156">
        <label>156</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holden</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Karsh</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The technology acceptance model: its past and its future in health care</article-title>
          <source>J Biomed Inform</source>
          <year>2010</year>
          <month>03</month>
          <volume>43</volume>
          <issue>1</issue>
          <fpage>159</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(09)00096-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2009.07.002</pub-id>
          <pub-id pub-id-type="medline">19615467</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(09)00096-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC2814963</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref157">
        <label>157</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The search for synergy: interrelating medical work and patient care information systems</article-title>
          <source>Methods Inf Med</source>
          <year>2018</year>
          <month>02</month>
          <day>08</day>
          <volume>42</volume>
          <issue>04</issue>
          <fpage>337</fpage>
          <lpage>44</lpage>
          <pub-id pub-id-type="doi">10.1055/s-0038-1634227</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref158">
        <label>158</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maniatopoulos</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Llewellyn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Lost in translation?: negotiating technological innovation in healthcare</article-title>
          <source>Proceedings of the European Group for Organisational Studies Colloquium</source>
          <year>2011</year>
          <conf-name>The European Group for Organisational Studies Colloquium</conf-name>
          <conf-date>2011</conf-date>
          <conf-loc>Gotenberg</conf-loc>
          <fpage>1</fpage>
          <lpage>20</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref159">
        <label>159</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smaglik</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Fixing a broken record</article-title>
          <source>Nature</source>
          <year>2005</year>
          <month>06</month>
          <day>23</day>
          <volume>435</volume>
          <issue>7045</issue>
          <fpage>1131</fpage>
          <pub-id pub-id-type="doi">10.1038/nj7045-1131a</pub-id>
          <pub-id pub-id-type="medline">15981321</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref160">
        <label>160</label>
        <nlm-citation citation-type="web">
          <article-title>Considerations for policymakers: the application of blockchain in healthcare</article-title>
          <source>HIMMS</source>
          <year>2019</year>
          <month>12</month>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/considerations-policymakers-application-blockchain-technology-healthcare">https://www.himss.org/resources/considerations-policymakers-application-blockchain-technology-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref161">
        <label>161</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wajcman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Pressed for Time: The Acceleration of Life in Digital Capitalism</source>
          <year>2015</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>University of Chicago Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref162">
        <label>162</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alexaki</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Alexandris</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Katos</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Petroulakis</surname>
              <given-names>NE</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based electronic patient records for regulated circular healthcare jurisdictions</article-title>
          <source>Proceedings of the IEEE 23rd International Workshop on Computer Aided Modelling and Design of Communication Links and Networks (CAMAD)</source>
          <year>2018</year>
          <conf-name>IEEE 23rd International Workshop on Computer Aided Modelling and Design of Communication Links and Networks (CAMAD)</conf-name>
          <conf-date>2018</conf-date>
          <conf-loc>Barcelona, Spain</conf-loc>
          <publisher-name>IEEE</publisher-name>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/camad.2018.8514954</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref163">
        <label>163</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>German Federal Ministry of the Interior</collab>
          </person-group>
          <article-title>Building and Community, Federal Ministry of Justice and Consumer Protection</article-title>
          <source>Opinion of the Data Ethics Commission</source>
          <year>2019</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmjv.de/DE/Themen/FokusThemen/Datenethikkommission/Datenethikkommission_EN_node.html;jsessionid=0B3B04760010083EFF159EE67CA14572.1_cid289">https://www.bmjv.de/DE/Themen/FokusThemen/Datenethikkommission/Datenethikkommission_EN_node.html;jsessionid=0B3B04760010083EFF159EE67CA14572.1_cid289</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref164">
        <label>164</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Batista</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hamouda</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lemieux</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Consumers' intentions to adopt blockchain-based personal health records and data sharing: Focus Group Study</article-title>
          <source>JMIR Form Res</source>
          <year>2020</year>
          <month>11</month>
          <day>05</day>
          <volume>4</volume>
          <issue>11</issue>
          <fpage>e21995</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2020/11/e21995/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21995</pub-id>
          <pub-id pub-id-type="medline">33151149</pub-id>
          <pub-id pub-id-type="pii">v4i11e21995</pub-id>
          <pub-id pub-id-type="pmcid">PMC7677023</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref165">
        <label>165</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Esmaeilzadeh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mirzaei</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>The potential of blockchain technology for health information exchange: experimental study from patients' perspectives</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>06</month>
          <day>20</day>
          <volume>21</volume>
          <issue>6</issue>
          <fpage>e14184</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/6/e14184/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/14184</pub-id>
          <pub-id pub-id-type="medline">31223119</pub-id>
          <pub-id pub-id-type="pii">v21i6e14184</pub-id>
          <pub-id pub-id-type="pmcid">PMC6610459</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref166">
        <label>166</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morozov</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <source>To Save Everything, Click Here: The Folly of Technological Solutionism</source>
          <year>2013</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Allen Lane</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref167">
        <label>167</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lynskey</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <source>The Foundations of EU Data Protection Law</source>
          <year>2015</year>
          <publisher-loc>Oxford</publisher-loc>
          <publisher-name>Oxford University Press</publisher-name>
          <fpage>177</fpage>
          <lpage>253</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref168">
        <label>168</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lanier</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Who Owns the Future?</source>
          <year>2014</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Simon and Schuster</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref169">
        <label>169</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schwartz</surname>
              <given-names>PM</given-names>
            </name>
          </person-group>
          <article-title>Property, privacy, and personal data</article-title>
          <source>Harvard Law Rev</source>
          <year>2004</year>
          <month>05</month>
          <volume>117</volume>
          <issue>7</issue>
          <fpage>2056</fpage>
          <pub-id pub-id-type="doi">10.2307/4093335</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref170">
        <label>170</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Lyles</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sarkar</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Adler-Milstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Are patients electronically accessing their medical records? Evidence from national hospital data</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2019</year>
          <month>11</month>
          <volume>38</volume>
          <issue>11</issue>
          <fpage>1850</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1377/hlthaff.2018.05437"/>
          </comment>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2018.05437</pub-id>
          <pub-id pub-id-type="medline">31682494</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref171">
        <label>171</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Application of a blockchain platform to manage and secure personal genomic data: a case study of LifeCODE.ai in China</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>09</month>
          <day>10</day>
          <volume>21</volume>
          <issue>9</issue>
          <fpage>e13587</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/9/e13587/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13587</pub-id>
          <pub-id pub-id-type="medline">31507268</pub-id>
          <pub-id pub-id-type="pii">v21i9e13587</pub-id>
          <pub-id pub-id-type="pmcid">PMC6786844</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref172">
        <label>172</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Su</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Is China the world’s blockchain leader? Evidence, evolution and outlook of China’s blockchain research</article-title>
          <source>J Clean Prod</source>
          <year>2020</year>
          <month>08</month>
          <volume>264</volume>
          <fpage>121742</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.jclepro.2020.121742"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jclepro.2020.121742</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref173">
        <label>173</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bekki</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Matsuzaki</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Mizushima</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Examining the Potential of Blockchain Technology to Meet the Needs of 21st-Century Japanese Health Care: Viewpoint on Use Cases and Policy</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>01</month>
          <day>09</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>e13649</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/1/e13649/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13649</pub-id>
          <pub-id pub-id-type="medline">31917371</pub-id>
          <pub-id pub-id-type="pii">v22i1e13649</pub-id>
          <pub-id pub-id-type="pmcid">PMC6996742</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref174">
        <label>174</label>
        <nlm-citation citation-type="web">
          <source>Hashed Health</source>
          <access-date>2021-12-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hashedhealth.com/about/">https://hashedhealth.com/about/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref175">
        <label>175</label>
        <nlm-citation citation-type="web">
          <source>Robert Miller</source>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bertcmiller.com/">https://bertcmiller.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref176">
        <label>176</label>
        <nlm-citation citation-type="web">
          <article-title>Blockchain in healthcare and the life sciences</article-title>
          <source>Consensys</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://consensys.net/blockchain-use-cases/healthcare-and-the-life-sciences/">https://consensys.net/blockchain-use-cases/healthcare-and-the-life-sciences/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref177">
        <label>177</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khurshid</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Applying blockchain technology to address the crisis of trust during the COVID-19 pandemic</article-title>
          <source>JMIR Med Inform</source>
          <year>2020</year>
          <month>09</month>
          <day>22</day>
          <volume>8</volume>
          <issue>9</issue>
          <fpage>e20477</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2020/9/e20477/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/20477</pub-id>
          <pub-id pub-id-type="medline">32903197</pub-id>
          <pub-id pub-id-type="pii">v8i9e20477</pub-id>
          <pub-id pub-id-type="pmcid">PMC7511222</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref178">
        <label>178</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Top 5 blockchain and healthcare trends in 2020: on business networks, the effect of COVID, and the direction of the market</article-title>
          <source>Bertcmiller</source>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bert.substack.com/p/top-5-blockchain-and-healthcare-trends?token=eyJ1c2VyX2lkIjozMzc1OTA3LCJwb3N0X2lkIjoyODkzNTc3MiwiXyI6IjA5TDdyIiwiaWF0IjoxNjExMzQ0Mzc5LCJleHAiOjE2MTEzNDc5NzksImlzcyI6InB1Yi0xMzM5Iiwic3ViIjoicG9zdC1yZWFjdGlvbiJ9.J_oc8lb6XC-ONmX808QVq-qfPtY5BVNYtvhg1SID2rI">https://tinyurl.com/yckt223b</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref179">
        <label>179</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wachter</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>National Advisory Group on health information technology in England</article-title>
          <source>Making It Work: Harnessing the Power of Health Information Technology to Improve Care in England. London: Department of Health</source>
          <year>2016</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Department of Health</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref180">
        <label>180</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kellermann</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>SS</given-names>
            </name>
          </person-group>
          <article-title>What it will take to achieve the as-yet-unfulfilled promises of health information technology</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2013</year>
          <month>01</month>
          <volume>32</volume>
          <issue>1</issue>
          <fpage>63</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1377/hlthaff.2012.0693"/>
          </comment>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2012.0693</pub-id>
          <pub-id pub-id-type="medline">23297272</pub-id>
          <pub-id pub-id-type="pii">32/1/63</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref181">
        <label>181</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <collab>Department of Health</collab>
          </person-group>
          <source>Liberating the NHS: An Information Revolution</source>
          <year>2010</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>HMSO</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref182">
        <label>182</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Neville</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Jeremy Hunt reveals push for more IT use in NHS</article-title>
          <source>Financial Times</source>
          <year>2013</year>
          <access-date>2021-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ft.com/content/60861f74-c3b5-11e2-8c30-00144feab7de">https://www.ft.com/content/60861f74-c3b5-11e2-8c30-00144feab7de</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref183">
        <label>183</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Keen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>England's national programme for IT</article-title>
          <source>Br Med J</source>
          <year>2013</year>
          <month>06</month>
          <day>28</day>
          <volume>346</volume>
          <issue>jun28 2</issue>
          <fpage>f4130</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.f4130</pub-id>
          <pub-id pub-id-type="medline">23810959</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref184">
        <label>184</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Campion-Awwad</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Hayton</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Vuaran</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The National Programme for IT in the NHS</article-title>
          <source>A Case History, University of Cambridge</source>
          <year>2014</year>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.589.4954&#38;rep=rep1&#38;type=pdf">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.589.4954&#38;rep=rep1&#38;type=pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref185">
        <label>185</label>
        <nlm-citation citation-type="web">
          <source>Healthcare Information and Management Systems Society (HIMSS)</source>
          <access-date>2021-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/blockchain-deployment-architecture">https://www.himss.org/blockchain-deployment-architecture</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref186">
        <label>186</label>
        <nlm-citation citation-type="web">
          <source>Blockchain for Healthcare</source>
          <access-date>2021-12-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://kyeung8.wixsite.com/blockchain4health">https://kyeung8.wixsite.com/blockchain4health</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
