<?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 article-type="review-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v13i1e58575</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/58575</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Smart Contracts and Shared Platforms in Sustainable Health Care: Systematic Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mistry</surname>
            <given-names>Jinal</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kale</surname>
            <given-names>Santosh</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Parra-Dominguez</surname>
            <given-names>Javier</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Marino</surname>
            <given-names>Carlos Antonio</given-names>
          </name>
          <degrees>MSci, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>CENTRUM Católica Graduate Business School</institution>
            <institution>Pontificia Universidad Católica del Perú</institution>
            <addr-line>Jirón Daniel Alomía Robles 125</addr-line>
            <addr-line>Lima, 15023</addr-line>
            <country>Peru</country>
            <phone>51 626 7100</phone>
            <email>cmarino@pucp.pe</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6393-6346</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Diaz Paz</surname>
            <given-names>Claudia</given-names>
          </name>
          <degrees>DPhil, DBA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0001-3334-0015</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>CENTRUM Católica Graduate Business School</institution>
        <institution>Pontificia Universidad Católica del Perú</institution>
        <addr-line>Lima</addr-line>
        <country>Peru</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Carlos Antonio Marino <email>cmarino@pucp.pe</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>31</day>
        <month>1</month>
        <year>2025</year>
      </pub-date>
      <volume>13</volume>
      <elocation-id>e58575</elocation-id>
      <history>
        <date date-type="received">
          <day>5</day>
          <month>4</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>5</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>2</day>
          <month>7</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>25</day>
          <month>11</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Carlos Antonio Marino, Claudia Diaz Paz. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 31.01.2025.</copyright-statement>
      <copyright-year>2025</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2025/1/e58575" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The benefits of smart contracts (SCs) for sustainable health care are a relatively recent topic that has gathered attention given its relationship with trust and the advantages of decentralization, immutability, and traceability introduced in health care. Nevertheless, more studies need to explore the role of SCs in this sector based on the frameworks propounded in the literature that reflect business logic that has been customized, automatized, and prioritized, as well as system trust. This study addressed this lacuna.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to provide a comprehensive understanding of SCs in health care based on reviewing the frameworks propounded in the literature.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A structured literature review was performed based on the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) principles. One database—Web of Science (WoS)—was selected to avoid bias generated by database differences and data wrangling. A quantitative assessment of the studies based on machine learning and data reduction methodologies was complemented with a qualitative, in-depth, detailed review of the frameworks propounded in the literature.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 70 studies, which constituted 18.7% (70/374) of the studies on this subject, met the selection criteria and were analyzed. A multiple correspondence analysis—with 74.44% of the inertia—produced 3 factors describing the advances in the topic. Two of them referred to the leading roles of SCs: (1) health care process enhancement and (2) assurance of patients’ privacy protection. The first role included 6 themes, and the second one included 3 themes. The third factor encompassed the technical features that improve system efficiency. The in-depth review of these 3 factors and the identification of stakeholders allowed us to characterize the system trust in health care SCs. We assessed the risk of coverage bias, and good percentages of overlap were obtained—66% (49/74) of PubMed articles were also in WoS, and 88.3% (181/205) of WoS articles also appeared in Scopus.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This comprehensive review allows us to understand the relevance of SCs and the potentiality of their use in patient-centric health care that considers more than technical aspects. It also provides insights for further research based on specific stakeholders, locations, and behaviors.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health care</kwd>
        <kwd>smart contracts</kwd>
        <kwd>blockchain</kwd>
        <kwd>security</kwd>
        <kwd>privacy</kwd>
        <kwd>supply chain</kwd>
        <kwd>patient centricity</kwd>
        <kwd>system trust</kwd>
        <kwd>stakeholders</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>New technologies have disrupted health care and imply exposure to complex scenarios. The Internet of Medical Things (IoMT) is increasingly receiving attention from practitioners and scholars to provide more alternatives for monitoring patients’ conditions; allowing access to private medical data; and obtaining secure and flawless tools to protect data from attacks that can access or steal essential information or, in some cases, produce a patient fatality [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. In this new technological landscape, recent studies have highlighted that blockchain technology with smart contracts (SCs) provides the most reliable data security, cryptographic capacities, and decentralized storage and can lead to a low-cost ecosystem and sustainability in the medical setting [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>The health care value chain is another research area where SCs have consistently shown effectiveness in avoiding counterfeiting and ensuring product security and safety. Implementing SCs on value chains can guarantee data provenance, eliminate unnecessary intermediaries, and provide an immutable history of transactions considering all the internal and external stakeholders. Although electronic health records (EHRs) are the most sensitive information in the SC environment, all the sensor devices are essential to provide a robust framework [<xref ref-type="bibr" rid="ref6">6</xref>]. A health care value chain faces different challenges and aims to monitor diseases by considering real-time patient status updates. Furthermore, some visible barriers include data interoperability and communication among applications, medical devices or machines, and institutions. This increases complexity and continuously impacts costs and efficiency [<xref ref-type="bibr" rid="ref7">7</xref>]. However, acquiring the logic of the value chain and adapting cutting-edge technologies to specific needs can save millions of lives and enhance quality of life for others.</p>
        <p>There are different approaches to analyzing literature data. A classic methodology considers a small number of research studies to synthesize the different perspectives and angles of the topic and provide future avenues of research. In addition, there are various frameworks, such as systematic or structured reviews. Thus, a bibliometric framework considers an extensive quantity of literature by using statistical software. Multiple objectives are pursued, such as recognizing intellectual models and new trends. Our study aimed to provide a bibliometric analysis of SCs on the health care value chain and, thus, obtain a fundamental knowledge of the intellectual, social, and conceptual structure and other clustering techniques. This review’s analysis was primarily interdisciplinary, seeking to discover barriers and possible gaps in the SC domain.</p>
      </sec>
      <sec>
        <title>Motivation</title>
        <p>Trust reduces complexity [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], manages uncertainty by compensation [<xref ref-type="bibr" rid="ref8">8</xref>], and is an element of social capital [<xref ref-type="bibr" rid="ref10">10</xref>]. Trust involves the truster and trustee as actors and expectations about actions in the future that could entail some risk for the trustee [<xref ref-type="bibr" rid="ref11">11</xref>]. Trust applied to new technologies implies the transition from personal trust to system trust [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>The literature refers to trust as a requirement of sustainable and human-centered technology [<xref ref-type="bibr" rid="ref13">13</xref>]. Technologies, through trust, also look to fulfill social interests and be responsive. This affirmation is essential when technologies—including blockchain and SCs—are introduced in fields such as health care [<xref ref-type="bibr" rid="ref11">11</xref>].</p>
        <p>A blockchain is a distributed ledger [<xref ref-type="bibr" rid="ref14">14</xref>] formed by chronologically ordered blocks [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. It consists of multiple nodes connected peer to peer [<xref ref-type="bibr" rid="ref15">15</xref>] and without a hierarchy among them [<xref ref-type="bibr" rid="ref15">15</xref>]. Each block has an identification linked to the previous one via a reference or hash [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. There is a genesis block, which is the first block of the chain, and any subsequent block also has the hash that allows for the identification of the previous one [<xref ref-type="bibr" rid="ref15">15</xref>]. Blocks have a block header—that usually includes the hash of the last block, a time stamp, and a nonce [<xref ref-type="bibr" rid="ref16">16</xref>]—and a payload or data with transactions [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. The blockchain holds a consensus algorithm [<xref ref-type="bibr" rid="ref14">14</xref>] that adds information to the chain [<xref ref-type="bibr" rid="ref16">16</xref>]. Blocks are accepted or refused based on this algorithm [<xref ref-type="bibr" rid="ref15">15</xref>]. In doing so, miners, who are a particular type of node, solve a challenge (ie, a mathematical puzzle) to verify the block and receive a reward [<xref ref-type="bibr" rid="ref16">16</xref>] (ie, “gas”). Information cannot be modified once a block has been added to the chain. SCs are codes stored in a blockchain [<xref ref-type="bibr" rid="ref17">17</xref>] containing transactions executed without intermediaries [<xref ref-type="bibr" rid="ref14">14</xref>]. Thus, technologies such as blockchains and SCs promise transactions that do not require trust among parties—called trust-free, trustless [<xref ref-type="bibr" rid="ref18">18</xref>], or trustless trust [<xref ref-type="bibr" rid="ref11">11</xref>]—and distribute trust among the system—called distributed trust [<xref ref-type="bibr" rid="ref11">11</xref>]. It is relevant to point out that their origins are independent despite the extensive joint use of blockchains and SCs. SCs were propounded as a transaction protocol [<xref ref-type="bibr" rid="ref19">19</xref>], whereas blockchains uses cryptography to allow for the exchange between participants worldwide without the necessity of a central authority [<xref ref-type="bibr" rid="ref20">20</xref>]. Blockchains and SCs look for trust development, where trust lies in the system design [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>SCs strengthen the capabilities of a blockchain [<xref ref-type="bibr" rid="ref21">21</xref>], aiming to (1) implement customizable business logic [<xref ref-type="bibr" rid="ref22">22</xref>] through different functionalities [<xref ref-type="bibr" rid="ref23">23</xref>] and (2) automatize the execution of preassigned transactions [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. One of the most essential characteristics of SCs is that transactions are automatically executed [<xref ref-type="bibr" rid="ref27">27</xref>]. For this, the interposition of a third party is not required [<xref ref-type="bibr" rid="ref27">27</xref>]. This characteristic improves efficiency, accountability [<xref ref-type="bibr" rid="ref28">28</xref>], and trust building [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. SCs are transparently auditable [<xref ref-type="bibr" rid="ref30">30</xref>] owing to their immutability. The decentralization of these systems also improves their resilience. Centralized systems represent a unique vertex of failure, a limitation that is overcome by SCs [<xref ref-type="bibr" rid="ref31">31</xref>] deployed in blockchains [<xref ref-type="bibr" rid="ref32">32</xref>]. Thus, SCs are especially relevant in health care as system trust generators [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
      </sec>
      <sec>
        <title>Contribution and Related Works</title>
        <p>This study fills a gap and responds to a request in the literature. Even though SCs are relevant in health care, a sufficient assessment is necessary. Some studies characterize SCs but do not refer to health care. It is the case of the proposal by Alzhrani et al [<xref ref-type="bibr" rid="ref32">32</xref>], which presented a characterization of some SCs in real-world systems based on a blockchain’s taxonomy. Nevertheless, this study does not focus on health care, and only 11 SCs were selected to exemplify its taxonomy. Other studies have focused on the health care sector but had a limited scope [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref33">33</xref>] and have not provided an in-depth characterization of SCs. Vargas and da Silva [<xref ref-type="bibr" rid="ref14">14</xref>] assessed 3 case studies or frameworks related to SCs in the IoMT. Sookhak et al [<xref ref-type="bibr" rid="ref33">33</xref>] limited their study to entering patient data into EHRs.</p>
        <p>Several theoretical studies or literature reviews regarding blockchains in health care have considered or mentioned SCs in the health care domain. Nevertheless, they need to focus on providing in-depth information about the role and features of SCs. The closest one is the review by Marbouh et al [<xref ref-type="bibr" rid="ref1">1</xref>], who inquired about the advantages of blockchains in improving patient safety. The challenges and opportunities of this technology were the starting point of the aforementioned study, which referred to the uses of blockchains in health care. It introduced SCs and some uses of blockchains. Still, these contracts were not the study’s primary goal, and it did not offer a systematic survey of the literature based on propounded frameworks.</p>
        <p>Furthermore, Villarreal et al [<xref ref-type="bibr" rid="ref29">29</xref>] studied blockchains in health care management systems and classified the architectural mechanisms in the literature. This study acknowledged SCs’ relevance and problems in health care, but they were not systematized and referred to one specific telemedicine case. Similarly, in the study by Arbabi et al [<xref ref-type="bibr" rid="ref34">34</xref>], the authors surveyed studies on blockchains in health care. They acknowledged the relevance of SCs but did not review their attributes in depth and suggested further assessment of the role of SCs.</p>
        <p>Similarly, Khatri et al [<xref ref-type="bibr" rid="ref35">35</xref>] systematically analyzed the broad topic of health care and blockchain integration and selected 50 publications for an in-depth analysis. In their study, the authors mentioned SCs; nevertheless, they did not propound specific functionalities or roles of SCs or link them with the authors’ proposal about blockchains. Finally, McBee and Wilcox [<xref ref-type="bibr" rid="ref36">36</xref>] studied the application of blockchains in medical imaging. Nonetheless, the literature has barely mentioned SCs to specify the origin of the name “blockchain 2.0” and its relationship with artificial intelligence (AI) [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        <p>Finally, Arbabi et al [<xref ref-type="bibr" rid="ref34">34</xref>] suggested further research on SCs in health care. The authors mentioned that the potential of SCs in health care requires an in-depth assessment. In addition, Hawlitschek et al [<xref ref-type="bibr" rid="ref38">38</xref>] propounded the development of additional research on the design of trusted interfaces. Thus, our study aimed to fill a gap in the literature—detailed in <xref ref-type="table" rid="table1">Table 1</xref>—and be responsive to its suggestions [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref38">38</xref>], focusing on an extensive review of SC frameworks in health care as elements that enhance trust and shift the traditional concept of trust among people to system trust, providing a characterization of it.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Gaps in the literature.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="150"/>
            <col width="150"/>
            <col width="150"/>
            <col width="150"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td>Study</td>
                <td>Health care sector</td>
                <td>Focused on SCs<sup>a</sup></td>
                <td>Included different topics (extensive review)</td>
                <td>Review based on propounded frameworks</td>
                <td>The roles or characteristics of SCs were developed</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Alzhrani et al [<xref ref-type="bibr" rid="ref32">32</xref>]</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
              </tr>
              <tr valign="top">
                <td>Vargas and da Silva [<xref ref-type="bibr" rid="ref14">14</xref>]</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
              </tr>
              <tr valign="top">
                <td>Sookhak et al [<xref ref-type="bibr" rid="ref33">33</xref>]</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Marbouh et al [<xref ref-type="bibr" rid="ref1">1</xref>]</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
                <td>Yes</td>
              </tr>
              <tr valign="top">
                <td>Villarreal et al [<xref ref-type="bibr" rid="ref29">29</xref>]</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Arbabi et al [<xref ref-type="bibr" rid="ref34">34</xref>]</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Khatri et al [<xref ref-type="bibr" rid="ref35">35</xref>]</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>McBee and Wilcox [<xref ref-type="bibr" rid="ref36">36</xref>]</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Our study</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>Yes</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>SC: smart contract.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Research Goals</title>
        <p>Our study aimed to provide a holistic understanding of SCs in health care. We focused on developing a structured literature review of the state-of-the-art scientific landscape of new technological advances, tendencies, and bibliometric analysis to help provide a comprehensive understanding and up-to-date overview of the recent research and outline new perspectives and future research directions.</p>
        <p>These contributions allow this research to fill a gap in understanding and respond to the suggestions by Arbabi et al [<xref ref-type="bibr" rid="ref34">34</xref>] and Hawlitschek et al [<xref ref-type="bibr" rid="ref38">38</xref>]. We adopted a systematic literature review approach because it allows for the replication of this study. A quantitative bibliometric analysis followed by an in-depth qualitative review of the studies enabled us to provide a detailed standpoint of the topic.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>We used the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) principles [<xref ref-type="bibr" rid="ref37">37</xref>] for our systematic literature review [<xref ref-type="bibr" rid="ref39">39</xref>]. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> contains the PRISMA checklist. The Web of Science (WoS) database provided the data, which were retrieved on July 4, 2023. The selection of databases for literature reviews is a topic under discussion [<xref ref-type="bibr" rid="ref40">40</xref>], and there is no unique response. Some studies have used several databases, whereas others have been restricted to 1. Among the latter, several systematic reviews have selected WoS as their search database [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref41">41</xref>], including some in health care [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>] and digital health [<xref ref-type="bibr" rid="ref44">44</xref>]. The propounded reasons were the reputation and reliability of this source [<xref ref-type="bibr" rid="ref45">45</xref>] and its extended use [<xref ref-type="bibr" rid="ref39">39</xref>].</p>
      <p>We chose to use only 1 database, WoS, because the joint use of several databases could introduce bias in our study. First, the search engines need to be unified and standardized. If we compare 2 of the most well-established databases of academic literature, WoS and Scopus [<xref ref-type="bibr" rid="ref46">46</xref>], and one of the most relevant specialized databases in medical topics, PubMed [<xref ref-type="bibr" rid="ref47">47</xref>], we could highlight some differences. For example, PubMed, Scopus, and WoS have the search option All Fields; nevertheless, this option encompasses different meanings for each database as they have other fields that are difficult to integrate [<xref ref-type="bibr" rid="ref48">48</xref>] (ie, PubMed has the field Pharmacological Action that is absent from WoS; WoS has the search fields Keyword Plus and Author Keyword, whereas PubMed has the search field Word-Term, MeSH Term, and Other Terms; Scopus includes a field named References, which is absent in the other 2 databases; and WoS has the search field Topic encompassing Title, Abstract, Keyword Plus, and Author Keyword, whereas Scopus has the search field Article, Title, Abstract, Keyword. Even though they could seem the same, they are not because WoS includes KeywordPlus, which responds to a proprietary algorithm, and Scopus’s Keyword field includes both Author Keywords and Index Terms [controlled vocabulary]). Something similar happens with other well-known databases such as EBSCOhost (ie, EBSCOhost consists of a field named All Text, which is absent in WoS and other databases). The literature has highlighted the discrepancies among WoS, Scopus, and PubMed regarding different topics [<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>], such as document type [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>], funding information [<xref ref-type="bibr" rid="ref53">53</xref>], and subject classification [<xref ref-type="bibr" rid="ref54">54</xref>].</p>
      <p>The combination of information obtained from ≥2 databases also generates an additional source of bias caused by data wrangling [<xref ref-type="bibr" rid="ref55">55</xref>]. Each database provides its search results in its format (ie, WoS uses commas [,] in some fields such as Keywords, whereas Scopus uses semicolons [;]). The different files require to be combined to assess them as one sample. This procedure could be performed manually or using an informatic tool; nevertheless, the data are always altered. For example, the order of the fields is different, and thus, we would have had to uniformize the data and the fields.</p>
      <p>In addition to the possible bias caused by combining multiple databases as our main decision criteria to select only WoS, there is also the concern regarding coverage and overlap with other databases as different databases have unequal scopes and coverage policies [<xref ref-type="bibr" rid="ref56">56</xref>].</p>
      <p>There are several studies on different databases’ coverage, but they are inconclusive regarding which database could be considered the most suitable for all cases. Some databases, including Scopus, could generally encompass a higher number of articles than WoS [<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref58">58</xref>]; nevertheless, when specific topics are searched for, the coverage could be very similar [<xref ref-type="bibr" rid="ref59">59</xref>], and some authors have also remarked that WoS coverage depth is better [<xref ref-type="bibr" rid="ref47">47</xref>]. WoS is a multidisciplinary database with more articles than PubMed [<xref ref-type="bibr" rid="ref57">57</xref>], but PubMed specializes in medicine and biomedical sciences [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]. On the basis of the novelty of the topic under study and its relationship with other disciplines, such as engineering, using a multidisciplinary database with a broader scope was considered the most suitable option. In addition, WoS has also essential coverage in medicine, similarly to Scopus. As an example, the evaluation of the content of Scopus and WoS in the context of Norway’s scientific and scholarly publications concludes that both databases are highly and similarly comprehensive in medicine and health—with 89% of scientific publications and 87% of scholarly publications in Scopus and WoS, respectively—and natural sciences and technology—with 85% of scientific publications and 84% of scholarly publications in Scopus and WoS, respectively [<xref ref-type="bibr" rid="ref60">60</xref>]. In addition, WoS has high levels of overlap with Scopus [<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref59">59</xref>] and PubMed [<xref ref-type="bibr" rid="ref57">57</xref>], which means that WoS shares an essential number of publications that are the same as those in each of the other databases (Scopus and PubMed).</p>
      <p>Therefore, the most suitable option was to use only 1 database, WoS, for our study to avoid possible bias caused by the differences in the structures of different databases and data wrangling. In addition, WoS is a well-known and esteemed database with comprehensive coverage of the topic under study, presenting a high level of overlap with other multidisciplinary and specialized databases.</p>
      <p>Furthermore, peer review is relevant to avoid selection bias [<xref ref-type="bibr" rid="ref61">61</xref>]. Both authors participated in the different stages of the identification and screening process and discussed and agreed on the search terms, procedure, and screening and selection criteria before executing this process. Following previous studies [<xref ref-type="bibr" rid="ref62">62</xref>], one of the authors (CDP) conducted a detailed review of the titles and abstracts and, when necessary, the complete texts to apply the selection criteria in the screening stage. The senior researcher (CAM) then shared and peer reviewed the results. Both authors discussed doubts and discrepancies until they reached an agreement.</p>
      <p>Exact searches were used to identify articles to reduce the risk of bias. The terms used to refer SCs included 6 variations encompassing singular and plural for the word with and without a hyphen and the joint form, similarly to the study by Dwivedi et al [<xref ref-type="bibr" rid="ref63">63</xref>]. The search was exact for each variation, and brackets were used. Adopting this approach did not leave the interpretation of term combinations to the subjective judgment of the researchers. The use of loose or approximate phrases was allowed for “health care.” For the term “health care,” we used an open search with a wildcard in the middle and at the end of the word (“health care*” or “health*care”). The search was Boolean. The query included the connectors OR for the same concepts and AND between different ideas considering the sense of the search and the rules of precedence of these operators in the WoS database. The query was as follows: (“smart contract” or “smart contracts” or “smart legal contract,” or “smart-contract” or “smart-contracts” or “smart legal contracts”) and (Health care* or health*care) (All Fields).</p>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>The search produced 374 results. The exclusion criteria were based on language (only English), type of source (review article, retraction, editorial material, and retracted publications were excluded), and availability (green submitted publications were excluded, and only open access publications were included). All these restrictions were established based on WoS filters. Finally, 163 publications were assessed. The selection encompassed the following criteria. Only those publications that (1) had the health care industry as their focus, (2) included a framework (framework, system, model, prototype, or similar), and (3) incorporated details about the roles of SCs and identified SCs were included in the study. In addition, the texts of the studies by Subramanian et al [<xref ref-type="bibr" rid="ref64">64</xref>] and Elgendy et al [<xref ref-type="bibr" rid="ref65">65</xref>] could not be accessed. A list of the 163 papers and their assessment results based on the aforementioned criteria can be reviewed in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. A final sample of 70 publications was selected to be reviewed. <xref rid="figure1" ref-type="fig">Figure 1</xref>, which was made using the template propounded by the PRISMA organization, details the selection process [<xref ref-type="bibr" rid="ref66">66</xref>].</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) framework for literature assessment.</p>
          </caption>
          <graphic xlink:href="medinform_v13i1e58575_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Bibliometric Assessment</title>
        <p>We assessed the selected studies to find the main trends. The biblioshiny app and the <italic>bibliometrix</italic> tool (K-Synth Srl) was used in this process [<xref ref-type="bibr" rid="ref67">67</xref>]. First, the data were screened. A total of 7% (5/70) of the studies had incomplete information about the authors’ keywords. Some techniques such as multiple correspondence analysis [<xref ref-type="bibr" rid="ref68">68</xref>] and network analysis [<xref ref-type="bibr" rid="ref50">50</xref>] are sensible to missing data [<xref ref-type="bibr" rid="ref69">69</xref>]. Keeping these studies could have biased the results.</p>
        <p>Consequently, we decided to withdraw 7% (5/70) of the articles [<xref ref-type="bibr" rid="ref70">70</xref>-<xref ref-type="bibr" rid="ref74">74</xref>]. Thus, we included 65 articles in the bibliometric assessment. The aforementioned 7% (5/70) of the articles were withdrawn only for these purposes; they were read in depth for reporting in the literature review section. In addition, the terms “smart contract,” “smart legal contract,” “smart contracts,” and “smart legal contracts” were signaled as synonyms where required.</p>
        <p>The studies were published in 34 journals, and one of the journals, <italic>IEEE Access</italic>, published 29% (19/65) of the studies. The countries with the most citations were the United States, the United Arab Emirates, South Korea, and Egypt with &gt;100 citations per country. <xref ref-type="table" rid="table2">Table 2</xref> summarizes the descriptive information.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Descriptive information.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="500"/>
            <col width="500"/>
            <thead>
              <tr valign="top">
                <td>Topic</td>
                <td>Values</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Sources (eg, journals and books), N</td>
                <td>34</td>
              </tr>
              <tr valign="top">
                <td>Documents, N</td>
                <td>65</td>
              </tr>
              <tr valign="top">
                <td>Annual growth rate (%)</td>
                <td>67.03</td>
              </tr>
              <tr valign="top">
                <td>Document age (y), mean (SD)</td>
                <td>2.52 (1.16)</td>
              </tr>
              <tr valign="top">
                <td>Authors, N</td>
                <td>246</td>
              </tr>
              <tr valign="top">
                <td>Single-authored documents (n=65), n (%)</td>
                <td>2 (3)</td>
              </tr>
              <tr valign="top">
                <td>International coauthorship, n (%)</td>
                <td>32 (49)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The historical evolution of this topic encompasses 6 years, from 2018 to 2023. The oldest study in our group was the one by Dagher et al [<xref ref-type="bibr" rid="ref75">75</xref>], published in 2018. Although this theme is relatively new, its historical evolution (<xref rid="figure2" ref-type="fig">Figure 2</xref>) reflects the relevance of COVID-19. The literature has propounded that this disease was one of the most important in recent years [<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>]. Until 2020, a total of 3 topics represented the field. After 2020, a new independent concept, <italic>security</italic>, emerged, and the term <italic>health care</italic> acquired relevance. In addition, the map of subjects organizes them into 4 groups given their significance and development (<xref rid="figure3" ref-type="fig">Figure 3</xref>). It shows that security, privacy, medical services, traceability, innovative health care, cybersecurity, and data sharing are the most developed and relevant topics, known as motor subjects. The IoMT constitutes a niche theme and developed topic. Cloud and edge computing are also niche themes. On the other hand, machine learning has a low level of development, which could be explained by its novelty and a medium level of relevance. This situation could reflect the first attempts to use SCs and machine learning together in the same framework.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Historical evolution of the topic.</p>
          </caption>
          <graphic xlink:href="medinform_v13i1e58575_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Map of subjects. IoMT: Internet of Medical Things.</p>
          </caption>
          <graphic xlink:href="medinform_v13i1e58575_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>We obtained the conceptual map and keyword cluster [<xref ref-type="bibr" rid="ref67">67</xref>] through factor analysis, a data reduction technique. Multiple correspondence analysis was used. This technique depicts the words on a map based on a similarity measure [<xref ref-type="bibr" rid="ref67">67</xref>]. The study yielded 3 factors in 2 dimensions (<xref rid="figure4" ref-type="fig">Figures 4</xref> and <xref rid="figure5" ref-type="fig">5</xref>), representing 74.44% of the variability or inertia (dimension 1: 51.28%; dimension 2: 23.18%). The factorial analysis tree supported the existence of 3 dimensions under the cutting line (<xref rid="figure5" ref-type="fig">Figure 5</xref>). The first factor represents the concern for the technical aspects of the topic. In this factor, Ethereum and InterPlanetary File System (IPFS) had the highest contributions (Ethereum: 3.083%; IPFS: 2.054%; together: 5.137%). The second factor concerns data privacy and security. Security, privacy, and data privacy represented the highest contributions to this factor (security: 8.191%; privacy: 4.498%; data privacy: 4.026%; together: 16.715%). Finally, the third factor is concerned with the processes themselves. Supply chain and supply chains had the highest contributions (supply chain: 5.135%; supply chains: 10.066%; together: 15.2%).</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Factorial analysis. IoMT: Internet of Medical Things; IPFS: InterPlanetary File System.</p>
          </caption>
          <graphic xlink:href="medinform_v13i1e58575_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>Factorial analysis tree. IoMT: Internet of Medical Things; IPFS: InterPlanetary File System.</p>
          </caption>
          <graphic xlink:href="medinform_v13i1e58575_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Literature Review</title>
        <sec>
          <title>Overview</title>
          <p>The literature review encompassed the in-depth reading of the 70 selected articles. The factors related to processes and patients’ privacy provided an initial approach to comprehending the role of SCs in health care. A detailed review of frameworks also permitted learning of SCs’ technological characteristics, which are linked to the third factor in the quantitative stage. In addition, and following the motivation of this study, the assessment of the authors’ proposals also allowed for propounding the building elements of system trust in health care SCs.</p>
        </sec>
        <sec>
          <title>Roles of SCs in Health Care</title>
          <sec>
            <title>Overview</title>
            <p>SCs in health care encompassed 2 main kinds of business logic, depicted in <xref ref-type="table" rid="table3">Table 3</xref>: process improvement and protecting patient privacy rights. The first business logic, process improvement, included six themes: (1) the medicine and medical equipment supply chain [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref78">78</xref>-<xref ref-type="bibr" rid="ref83">83</xref>], (2) insurance claim attention [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref84">84</xref>], (3) vaccination passports and certificates [<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref85">85</xref>], (4) clinical research [<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref87">87</xref>], (5) emergency attention process [<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref89">89</xref>], and (6) regulatory compliance [<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]. The second business logic, protecting patient privacy rights, incorporated three themes: (1) patient consent management [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]; (2) authentication, authorization, and access [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref73">73</xref>-<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref92">92</xref>-<xref ref-type="bibr" rid="ref114">114</xref>]; and (3) telemedicine and eHealth care [<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref115">115</xref>-<xref ref-type="bibr" rid="ref126">126</xref>]. This classification aims to understand the business logic reflected in SCs based on the main goal or goals pursued in developing the framework and the most relevant stakeholders.</p>
            <table-wrap position="float" id="table3">
              <label>Table 3</label>
              <caption>
                <p>Roles of smart contracts in health care.</p>
              </caption>
              <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="30"/>
                <col width="470"/>
                <col width="500"/>
                <thead>
                  <tr valign="top">
                    <td colspan="2">Roles and themes</td>
                    <td>References</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Role 1: process improvement</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Medicine and medical equipment supply chain</td>
                    <td>[<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref78">78</xref>-<xref ref-type="bibr" rid="ref83">83</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Insurance claim attention</td>
                    <td>[<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref84">84</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Vaccination passports and certificates</td>
                    <td>[<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref85">85</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Clinical research</td>
                    <td>[<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref87">87</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Emergency attention process</td>
                    <td>[<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref89">89</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Regulatory compliance</td>
                    <td>[<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Role 2: protecting patient privacy rights</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Patient consent management</td>
                    <td>[<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Authentication, authorization, and access</td>
                    <td>[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref73">73</xref>-<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref92">92</xref>-<xref ref-type="bibr" rid="ref114">114</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Telemedicine and eHealth care</td>
                    <td>[<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref115">115</xref>-<xref ref-type="bibr" rid="ref126">126</xref>]</td>
                  </tr>
                </tbody>
              </table>
            </table-wrap>
          </sec>
          <sec>
            <title>Role 1: Improving Health Care Processes</title>
            <p>The studies that adopted this perspective used SCs as a lever to face problems related to processes, and their frameworks presented solutions to generate accountability and efficiency as their primary challenge. The topics encompassed in this group were medicines and medical equipment supply chain, insurance claim attention, telemedicine and eHealth, vaccination passports and certificates, clinical research, emergency attention processes, and regulatory compliance.</p>
            <p>Medicine and medical equipment supply chains constituted the primary category of this group. The use of SCs in health supply chains [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref78">78</xref>-<xref ref-type="bibr" rid="ref82">82</xref>] aimed to solve problems related to efficiency. These problems could be associated with tracing the supply chain stages, reducing overproduction and underconsumption, automating procurement contracts, or verifying the route of resealable returned drugs. Some studies had the specific mission of correcting malpractice, as exemplified by cases of counterfeit medicines and medical equipment [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref82">82</xref>].</p>
            <p>Immutability, decentralization, transparency, and automatized execution of blockchains are valuable features that could solve these problems. Musamih et al [<xref ref-type="bibr" rid="ref79">79</xref>] aimed to track all controlled drugs. SCs were required to follow all actions; thus, the actors in the supply chain would be individually accountable for their participation in the process because their activities could be tracked back. The framework included 7 actors: the controlled drug regulator, manufacturer, distributor, hospital and pharmacy, nurse station, and patient. The drug manufacturer controls the process. In total, 3 SCs were propounded in this framework: registration, production, and consumption.</p>
            <p>One particularity of these frameworks is that several included the participation of specific government regulators, such as the Food and Drug Administration in the United States [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref81">81</xref>] and the Central Drugs Standard Control Organization in India [<xref ref-type="bibr" rid="ref80">80</xref>], or nonspecific ones [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref79">79</xref>] that interact with private stakeholders. It is relevant to mention that SCs look to generate relationships without the necessity of trust among participants. Trust goes from the interpersonal level to the system level. In this case, government agencies that participate in blockchains could interact with their counterparts without the need to trust them, and vice versa.</p>
            <p>As was previously stated, some frameworks depicted the extraordinary complexities of their stakeholders. As an example, Munasinghe and Halgamuge [<xref ref-type="bibr" rid="ref82">82</xref>] propounded a framework that tried to uncover counterfeited COVID-19 vaccines. The authors realized that there was an international move of vaccines and then a nationwide distribution. This framework considered the ingredient provider, the vaccine manufacturer, the external company (vaccine supply), consolidation (government), the primary distribution, hospitals, clinics, pharmacies, and zone distributions as stakeholders. On the basis of these characteristics, the authors propounded 4 SCs.</p>
            <p>Similarly, the study by Omar et al [<xref ref-type="bibr" rid="ref24">24</xref>] depicted a particular negotiation structure of transactions. The authors applied SCs to procurement contracts negotiated by group purchasing organizations. In this context, several health providers negotiate procurement contracts with manufacturers. These health providers must pay a membership fee to the group, but they achieve better prices or loyalty rebates under this form of negotiation. The group negotiates prices with the manufacturer and determines the distributor for the entire group. This framework encompassed 5 SCs that represent the joint negotiation, the individual interests (rebates), and health care providers’ actions (purchase placement).</p>
            <p>The frameworks related to the health supply chain could also use additional technologies in the solution, but these are the exceptions. For example, Abbas et al [<xref ref-type="bibr" rid="ref78">78</xref>] suggested combining blockchain and machine learning techniques in the same framework. This framework sought more efficient supply chain management and provided final consumer recommendations. SCs improved the supply chain. Recommendations were propounded based on machine learning outputs. In these solutions, SCs include functionalities related to registration and production, consumption, and waste assessment.</p>
            <p>Insurance claim frameworks include SCs to facilitate the attention of these claims, reduce [<xref ref-type="bibr" rid="ref24">24</xref>] fraudulent activities [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref64">64</xref>], or improve efficiency [<xref ref-type="bibr" rid="ref84">84</xref>]. These contracts could include government entities as stakeholders [<xref ref-type="bibr" rid="ref26">26</xref>], health insurance providers [<xref ref-type="bibr" rid="ref84">84</xref>], claimants, patients, and health care providers or hospitals. The process automatized by SCs includes claim submission and attention and could also encompass billing and payment processes. Unlike in supply chain studies, patients have a relevant participation in these frameworks.</p>
            <p>SCs could also enhance the processes related to vaccination passports and vaccination certificates. These vaccination records can (1) certify the status of vaccination required to do other activities, such as traveling; (2) provide information related to possible causes of the symptoms of a patient to physicians [<xref ref-type="bibr" rid="ref72">72</xref>]; and (3) be used in sanitary emergencies [<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref85">85</xref>]. In the first and second cases, the stakeholders are mainly patients and hospitals or clinics—where the patient was vaccinated and where they request later attention based on specific symptoms—and the primary function of the propounded technology is recording and providing access to the data. The third case, referring to vaccination records in emergencies such as the COVID-19 pandemic, involves more complex frameworks, including generating certificates and providing access to them to several stakeholders. These frameworks also consider the international movement of people and countries’ requirements regarding vaccination [<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref85">85</xref>]. Stakeholders include hospitals, vaccination centers, and governmental entities—ministries of health and foreign affairs [<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref85">85</xref>].</p>
            <p>Clinical research can use SCs for sharing and aggregating health care–related data because SCs provide secure storage and querying while protecting privacy in managing the data [<xref ref-type="bibr" rid="ref86">86</xref>]. Both features are particularly relevant for research because they could promote collaboration among entities and data aggregation. Increasing the amount of data could also improve the generalization of studies [<xref ref-type="bibr" rid="ref86">86</xref>]. Hospitals, as stakeholders, could act together to develop research activities [<xref ref-type="bibr" rid="ref87">87</xref>]. For example, Kuo and Pham [<xref ref-type="bibr" rid="ref87">87</xref>] introduced a framework allowing different hospitals to assess data during the COVID-19 pandemic. This inquiry encompassed 13 hospitals that acted as a federation, which means that these institutions were required to share information and obtain, in some cases, a global aggregate.</p>
            <p>The provision of attention to patients in an emergency context can also benefit from this technology [<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref89">89</xref>]. For example, Ksibi et al [<xref ref-type="bibr" rid="ref88">88</xref>] suggested using SCs to manage processes related to an emergency caused by a car crash. This framework allowed emergency vehicles to improve communication with the cars involved in the accident and with hospital emergency services. Peyvandi et al [<xref ref-type="bibr" rid="ref89">89</xref>] established a framework that supported the prediction of diagnoses—or computer-aided diagnosis—in an emergency. Machine learning technology was used to forecast a diagnosis, whereas SCs preserved patients’ privacy and granted access to the data. The stakeholders are emergency units that attend hospital emergency services.</p>
            <p>Regulatory compliance could be enhanced using SCs [<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref91">91</xref>], detecting and flagging privacy regulation violations. SCs allow patients to select their data privacy preferences, record events, and verify compliance with regulations. Regulatory compliance could also be enhanced using edge computing [<xref ref-type="bibr" rid="ref90">90</xref>]. In these appraisals, the stakeholders are patients, health care providers—including hospitals—and clinical researchers. Governmental agencies are not included as the perspective of these frameworks is not enforcement but private compliance.</p>
            <p>It is pertinent to note that these frameworks mentioned the United States [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref81">81</xref>] and India [<xref ref-type="bibr" rid="ref80">80</xref>] through their regulators. They also referenced other regions such as Southeast Asia [<xref ref-type="bibr" rid="ref85">85</xref>]. The studies were also concerned with complying with the regulations of the European Union [<xref ref-type="bibr" rid="ref91">91</xref>] and the United States [<xref ref-type="bibr" rid="ref90">90</xref>]. In addition, institutions located in the United Kingdom [<xref ref-type="bibr" rid="ref87">87</xref>] and the United States [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref86">86</xref>] provided datasets used to test proposals.</p>
          </sec>
          <sec>
            <title>Role 2: Improving Patient Privacy Protection</title>
            <p>A new paradigm has influenced patient data management: patient centrality [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref92">92</xref>-<xref ref-type="bibr" rid="ref94">94</xref>]. Patients are acknowledged as owners and managers of their health data [<xref ref-type="bibr" rid="ref92">92</xref>]. Moreover, Jadav et al [<xref ref-type="bibr" rid="ref115">115</xref>] have also alluded to a new reality in this field characterized by machine-centric interaction [<xref ref-type="bibr" rid="ref92">92</xref>], where technology—especially the IoMT—provides different solutions for the health care sector. Both new complementary paradigms, patient centrality and machine-centric interactions, guide data management.</p>
            <p>Data fragmentation [<xref ref-type="bibr" rid="ref17">17</xref>], data breaches [<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref116">116</xref>], compliance with regulations [<xref ref-type="bibr" rid="ref115">115</xref>], cross-organizational coordination [<xref ref-type="bibr" rid="ref95">95</xref>], and interoperability [<xref ref-type="bibr" rid="ref96">96</xref>] are some challenges that the frameworks deal with. The stakeholders are patients and health facilities—including hospitals, clinics, physicians, laboratories, and researchers. Hospitals and clinics could act independently or as a consortium. Moreover, the blockchain could also act as a federation. Hashim et al [<xref ref-type="bibr" rid="ref96">96</xref>] highlighted the problems that arise from the interoperability of independent blockchains and proposed a solution based on 3 SCs (search, global, and local). It is also relevant to mention that one study applied its framework in an animal health care service [<xref ref-type="bibr" rid="ref97">97</xref>].</p>
            <p>This role includes three main topics: (1) patient consent management; (2) authentication, authorization, and access; and (3) eHealth care. The patient centrality paradigm is reflected in patient consent management, which includes the possibility of patients defining viewer authorizations. For example, El Majdoubi et al [<xref ref-type="bibr" rid="ref71">71</xref>] propounded a framework in which patients could manage their health data privacy preferences. A privacy agreement and enforcement were automatically settled if patients’ preferences coincided with provider policies and privacy law. A privacy offer was published; this privacy offer could become a privacy agreement if it was accepted. After that, the system tracked the execution of this agreement. Thus, compliance with legal requirements and the stakeholders’ preferences was ensured. In addition, this framework encompassed 3 levels of privacy. The first one, or P0, included data that could be viewed only by patients. The second one, or P1, referred to data that health care providers could also access. Finally, the third one, or P2, contained publicly available data [<xref ref-type="bibr" rid="ref76">76</xref>].</p>
            <p>Authentication, authorization, and access are central topics in patient privacy protection. SCs in these frameworks deploy different functions. They manage patients’ consent, transfer and share data, search for patients, administer registration (add new users, view users, delete users, and create accounts), actualize data (add and update information), request access permission, restrict access, store data, provide search functions, and establish viewership criteria. The complexity of SC functions depends on the framework scope. The main stakeholders are hospitals and patients, as well as insurance companies and governmental agencies [<xref ref-type="bibr" rid="ref98">98</xref>].</p>
            <p>In addition, some frameworks use additional protocols or technologies to protect patient data privacy better. Saidi et al [<xref ref-type="bibr" rid="ref99">99</xref>] used the self-sovereign identity (SSI) model. SSI aims to prove the identity in a digital environment, and a verifiable credential and a decentralized identifier underpin it. SSI has given rise to the SSI-based access control that allows for separate authentication, which is decentralized, and authorization, which is centralized. The SC—policy decision SC—provides efficiency and security to role assignments. In addition, this framework introduced an adaptive access control policy for emergencies. Other authors used ciphertext-policy attribute-based encryption (CP-ABE) [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref100">100</xref>] and attribute-based access control [<xref ref-type="bibr" rid="ref95">95</xref>]. CP-ABE [<xref ref-type="bibr" rid="ref81">81</xref>] and attribute-based access control determine access based on attributes; nevertheless, the first one, CP-ABE, offers a higher degree of granularity and is related to data encryption [<xref ref-type="bibr" rid="ref100">100</xref>]. Biometric technology [<xref ref-type="bibr" rid="ref20">20</xref>] such as fingerprints was also included in access control [<xref ref-type="bibr" rid="ref21">21</xref>]. The use of ring signature and stealth address [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref87">87</xref>] to improve security was also considered [<xref ref-type="bibr" rid="ref101">101</xref>]. Ring signature can hide the sender’s identity, keeping the transaction safe because the receiver has the elements to verify the transaction authenticity [<xref ref-type="bibr" rid="ref101">101</xref>]. Meanwhile, a stealth address maintains the anonymity of the sender’s address, creating a 1-time address [<xref ref-type="bibr" rid="ref101">101</xref>].</p>
            <p>eHealth care and telemedicine represent a particular case, where SCs are mainly recommended for granting patient data access in a secure environment. Commonly, these frameworks are mentioned together in telemedicine, the IoMT, and eHealth [<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref117">117</xref>], including wearable sensors, smart devices [<xref ref-type="bibr" rid="ref118">118</xref>], and ambient intelligence [<xref ref-type="bibr" rid="ref119">119</xref>]. Telemedicine faces several challenges, including interoperability, incorrect diagnosis, and unfavorable perceptions. These perceptions are grounded on the fact that they are not the same as physical environments [<xref ref-type="bibr" rid="ref120">120</xref>]. In telemedicine, the frameworks use SCs to generate secure transactions and automate participant communication [<xref ref-type="bibr" rid="ref120">120</xref>]. In doing so, the frameworks could encompass laboratory test results [<xref ref-type="bibr" rid="ref90">90</xref>], payment, and drug delivery, among other things [<xref ref-type="bibr" rid="ref102">102</xref>,<xref ref-type="bibr" rid="ref118">118</xref>,<xref ref-type="bibr" rid="ref120">120</xref>]. The stakeholders include the usual ones—patients, hospitals, physicians, insurers, medical research organizations, and laboratories—and special ones, such as a telemedicine center [<xref ref-type="bibr" rid="ref120">120</xref>] or diagnostic center [<xref ref-type="bibr" rid="ref102">102</xref>] and federated hospital clouds [<xref ref-type="bibr" rid="ref90">90</xref>]. Javed et al [<xref ref-type="bibr" rid="ref2">2</xref>] referred to the health care regulator in their framework and gave the regulator control of the blockchain.</p>
            <p>Telemedicine and eHealth care are concerned with malicious nodes and use additional technologies to deal with this problem or detect health abnormalities. Puri et al [<xref ref-type="bibr" rid="ref70">70</xref>] suggested using SCs and AI to identify malicious nodes and security breaches. Similarly, Jadav et al [<xref ref-type="bibr" rid="ref115">115</xref>] recommended including AI, specifically recurrent neural networks, to ensure data integrity. Neural networks train data to detect attacks and review data before storing them. Baiju et al [<xref ref-type="bibr" rid="ref121">121</xref>] relied on machine learning (logistic regression) to anticipate abnormalities in the stored data. Dhasarathan et al [<xref ref-type="bibr" rid="ref116">116</xref>] adopted a supervised machine learning approach to monitor risk factors in data transmission. In addition, Masud et al [<xref ref-type="bibr" rid="ref119">119</xref>] suggested a framework that uses biometrics, among other technologies. The use of edge computing [<xref ref-type="bibr" rid="ref122">122</xref>] and fog-cloud computers was also suggested [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref123">123</xref>,<xref ref-type="bibr" rid="ref124">124</xref>].</p>
            <p>In addition, Shaikh et al [<xref ref-type="bibr" rid="ref125">125</xref>] suggested a framework that aimed to transform medical data into wisdom. In this framework, data collected from patients were cleaned and transformed into information, which was evaluated and converted into knowledge. Finally, metadata were extracted and converted into wisdom that could be used in medical research. The stakeholders were patients, physicians, data analysts, and knowledge managers. SCs provided registration advantages, data privacy customization, and exchange policies in this proposal. Abou-Nassar et al [<xref ref-type="bibr" rid="ref126">126</xref>] were also concerned about the knowledge management and interoperability of IoMT devices related to semantic differences. The authors proposed an ontology model to achieve a higher level of trust.</p>
            <p>It is relevant to mention that, without prejudice to their generalization capability, several studies obtained their testing dataset from institutions in the United States [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref89">89</xref>,<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref101">101</xref>,<xref ref-type="bibr" rid="ref103">103</xref>,<xref ref-type="bibr" rid="ref115">115</xref>] and South Korea [<xref ref-type="bibr" rid="ref127">127</xref>]. Some studies dealt with regulatory privacy concerns in the United States (Health Insurance Portability and Accountability Act; HIPAA [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref75">75</xref>]) and Europe (General Data Protection Regulation [<xref ref-type="bibr" rid="ref95">95</xref>]). Finally, 2 frameworks were tailored for specific countries: the United Arab Emirates [<xref ref-type="bibr" rid="ref98">98</xref>] and Italy [<xref ref-type="bibr" rid="ref104">104</xref>].</p>
          </sec>
        </sec>
        <sec>
          <title>Technical Characteristics That Provide Efficiency to Frameworks That Incorporate SCs in Health Care</title>
          <p>The frameworks that propound the use of SCs face an essential challenge regarding their efficiency, requiring specific technical strategies to optimize their use [<xref ref-type="bibr" rid="ref128">128</xref>]. The literature [<xref ref-type="bibr" rid="ref28">28</xref>] mentioned limited data storage and inefficient execution as problems of SCs [<xref ref-type="bibr" rid="ref129">129</xref>]. One of the strategies used to solve data storage problems is in-chain and off-chain data storage. Only the most relevant information is kept in the chain; additional information is sent to another source. IPFS is the preferred solution for maintaining data off the chain. This system optimizes resources because access to the data requires only the hash generated when the data are stored [<xref ref-type="bibr" rid="ref105">105</xref>].</p>
          <p>Some frameworks had an essential level of complexity and were required to preserve a critical quantity of data. Doing it in the blockchain could turn the system into an inefficient one. For example, Debe et al [<xref ref-type="bibr" rid="ref22">22</xref>] propounded a framework for tracking resalable returned drugs that included several stakeholders and SCs. The medicines were produced by manufacturers in lots. These manufacturers were also required to share images of the package. Storing these images in the blockchain would be costly and inefficient. Thus, they were stored off the chain in the IPFS. Rai [<xref ref-type="bibr" rid="ref80">80</xref>] suggested a similar solution, which also proposed keeping a lot of drug images in the IPFS.</p>
          <p>The IPFS was also used in frameworks focused on patient data privacy and security. For example, Azbeg et al [<xref ref-type="bibr" rid="ref105">105</xref>] propounded that only hash data should be stored in the chain. The IPFS preserved additional data as the off-chain storage, and Hussien et al [<xref ref-type="bibr" rid="ref100">100</xref>] introduced a procedure to encrypt medical data before their storage in the IPFS, extending the CP-ABE and comprising searchable symmetric encryption [<xref ref-type="bibr" rid="ref86">86</xref>].</p>
          <p>Another strategy proposed to optimize resources was the specialization of SCs. SCs contain functions deployed when they are called. Under this strategy, the different parts that the framework requires are organized in several specialized SCs that could be individually deployed when needed, optimizing the resources. The quantity of SCs and the functions included in each could vary, and they are related to the complexity of the objectives that the framework aims to achieve. Frameworks based on 1 SC were the exception (ie, the study by Peyvandi et al [<xref ref-type="bibr" rid="ref89">89</xref>], who proposed a single SC for patient data sharing).</p>
          <p>In addition, the specialization of nodes was also propounded [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref97">97</xref>]. For example, Abbas et al [<xref ref-type="bibr" rid="ref78">78</xref>] established a framework to manage medicine supply chain management and a recommendation system to avoid counterfeit drugs. This framework leveraged the attributes of SCs using machine learning. The SCs had an execution rate that was lower than desirable. The solution was to deploy them only on specified nodes, and only some of them—called endorsers—could validate the transactions. This solution enhanced the efficiency of the system.</p>
          <p>The frameworks’ efficiency and optimization are reflected in their cost analysis. The Ethereum platform provides the cost of gas or ether for function deployment. This cost can be converted to a specific national currency. Gas is relevant because it incentivizes miners to work [<xref ref-type="bibr" rid="ref24">24</xref>] and protects them from distributed denial of service attacks [<xref ref-type="bibr" rid="ref82">82</xref>]. Omar et al [<xref ref-type="bibr" rid="ref24">24</xref>] and Chen et al [<xref ref-type="bibr" rid="ref72">72</xref>] reported the cost based on a low average and fast execution in this platform converted to US dollars. The Hyperledger Fabric platform does not include ether; nevertheless, a computational cost can be calculated and compared. Munasinghe and Halgamuge [<xref ref-type="bibr" rid="ref82">82</xref>], for example, calculated and compared the cost of their framework developed in Hyperledger Fabric based on previous inquiries.</p>
          <p>It is relevant to mention that the frameworks used extended cryptography mechanisms of blockchains, such as hash functions, digital signatures, public-private keys, and Merkle trees. Ethereum and Hyperledger Fabric were the preferred platforms. The frameworks used the features and facilities provided for these platforms (ie, the programming language Solidity in Ethereum). The different types of blockchain were represented in the frameworks. There were private blockchains (ie, the study by Omar et al [<xref ref-type="bibr" rid="ref23">23</xref>]), public blockchains (ie, the study by Debe et al [<xref ref-type="bibr" rid="ref22">22</xref>]), and consortiums (ie, the study by Mackey et al [<xref ref-type="bibr" rid="ref26">26</xref>]). A detailed review of this specific topic can be found in the study by Sookhak et al [<xref ref-type="bibr" rid="ref33">33</xref>]. Ganache, Truffle, and MetaMask were frequently used [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. The SCs were commonly tested in Remix IDE [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        </sec>
        <sec>
          <title>Characterization of System Trust in Health Care SCs</title>
          <p>SCs imply a transition from trust in people to trust in systems [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>] where people interact without needing to trust each other or a central authority. On the basis of the previously exposed findings, we characterized system trust in health care SCs. The object of trust, or what is trusted, is represented by the 2 roles identified and the subjects they encompass. The stakeholders that interact without the necessity of a central authority are the subjects that are trusting and represent whom they trust. Finally, the technical strategies that these frameworks adopt support the trust in this system. <xref rid="figure6" ref-type="fig">Figure 6</xref> summarizes these elements.</p>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>Characterization of system trust in health care smart contracts. CDSCO: Central Drugs Standard Control Organization; FDA: Food and Drug Administration.</p>
            </caption>
            <graphic xlink:href="medinform_v13i1e58575_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Coverage Bias Assessment</title>
        <sec>
          <title>Overview</title>
          <p>This study used a single database, WoS, to avoid bias caused by the differences in database structure and data wrangling considering that the literature supports WoS’s acceptable coverage and overlap with other databases. Nevertheless, assessing possible bias caused by the difference in coverage among different databases was considered relevant. Thus, subsequently, in our study, a comparison of coverage and overlap between WoS and other databases was conducted. The selected databases were (1) a multidisciplinary one of extended use, Scopus; and (2) a specialized one, PubMed.</p>
          <p>The procedure had 2 stages. The first conducted a comparison between WoS and Scopus and between WoS and PubMed regarding their coverage and overlap. In this stage, the queries were evaluated to make them as similar as possible. The raw results on WoS were compared to identify the overlap between studies in both WoS and Scopus or both WoS and PubMed.</p>
          <p>The second stage asked whether the articles published in Scopus or PubMed but not in WoS could provide relevant additional information to our literature review. Thus, we selected those studies that were only in Scopus or PubMed and were published until June 2023. They were then evaluated based on the 3 selection criteria of our research. For such purposes, the titles and abstracts and, in case of doubt, the full texts were reviewed by one of the researchers. The results were then discussed between the researchers, and the doubts and discrepancies were resolved. Third, the selected studies were read and compared with the literature review results. The searches for comparison purposes in PubMed, Scopus, and WoS were conducted on June 5, 2024.</p>
        </sec>
        <sec>
          <title>Coverage Bias Between Multidisciplinary Databases: WoS and Scopus</title>
          <p>The starting point of the comparison between WoS and Scopus was to select the most suitable field in both databases to conduct the search as All Fields was not adequate. The fields Topic in WoS and Article, Title, Abstract, Keyword in Scopus were close enough to our purposes. In addition, the difference between a search of All Fields and Topic was only 8 articles. Restrictions regarding language (only English), access, and type of article were included. The queries were as follows: Refine results for (“smart contract” or “smart-contract” or “smart contracts” or “smart legal contract” or “smart-contracts” or “smart legal contracts”) (Topic) AND (Healthcare* or health*care) (Topic) and English (Languages) and Review Article or Retracted Publication or Retraction or Editorial Material (Exclude – Document Types) and Green Submitted (Exclude – Open Access) and All Open Access (Open Access) for WoS and ( TITLE-ABS-KEY ( “smart contract” OR “smart-contract” OR “smart contracts” OR “smart legal contract” OR “smart-contracts” OR “smart legal contracts” ) AND TITLE-ABS-KEY ( ( healthcare* OR health*care ) ) ) AND ( LIMIT-TO ( LANGUAGE, “English” ) ) AND ( LIMIT-TO ( OA, “all” ) ) AND ( LIMIT-TO ( DOCTYPE, “ar” ) ) for Scopus.</p>
          <p>These searches produced 205 and 270 documents for WoS and Scopus, respectively. The results were then compared based on the digital object identifiers to obtain the level of overlap between both databases. The databases shared 181 documents, which represents an 88.3% (181/205) coincidence for WoS and a 67% (181/270) coincidence for Scopus. Notably, these percentages are higher than those obtained in other systematic reviews that also used WoS as their search engine. Maia et al [<xref ref-type="bibr" rid="ref130">130</xref>] obtained a 61.4% (167/272) and 56.1% (213/380) overlap for the WoS and Scopus results, respectively.</p>
          <p>Despite the high level of overlap, the next question was whether Scopus’s additional documents could provide relevant qualitative information for our study. Thus, in the second stage, we selected the Scopus documents published before July 2023 because we conducted the search for our review on July 4, 2023, and 71 papers were obtained. We then applied the selection criteria used in our study. Finally, a list of 15 articles was retrieved and reviewed in depth. Most of them referred to data exchange and EHRs and could be included in the second role of SCs related to privacy and security [<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref131">131</xref>-<xref ref-type="bibr" rid="ref140">140</xref>]. The additional ones could be included in the first role of SCs related to process improvement [<xref ref-type="bibr" rid="ref141">141</xref>-<xref ref-type="bibr" rid="ref144">144</xref>].</p>
        </sec>
        <sec>
          <title>Coverage Bias Between Multidisciplinary and Specialized Databases: WoS and PubMed</title>
          <p>A procedure similar to the previously detailed one was performed between WoS and PubMed. PubMed used the field Title/Abstract. Filters for language—only English—and text availability—free full text—were then applied. The WoS query was the one previously detailed, and the PubMed query was as follows: ((“smart contract”[Title/Abstract] OR “smart-contract”[Title/Abstract] OR “smart contracts”[Title/Abstract] OR “smart legal contract”[Title/Abstract] OR “smart-contracts”[Title/Abstract] OR “smart legal contracts”[Title/Abstract])) AND ((Healthcare*[Title/Abstract] OR health*care[Title/Abstract])).</p>
          <p>These searches produced 77 and 205 documents for PubMed and WoS, respectively. A total of 4 PubMed documents did not have a digital object identifier and were not considered in the comparison with the remaining 74 papers. A total of 49 of those documents were also included in WoS, which represents a 66% (49/74) overlap with PubMed. On the basis of previous studies [<xref ref-type="bibr" rid="ref130">130</xref>], this percentage can be considered satisfactory.</p>
          <p>The second step started with selecting PubMed documents published until June 2023. The result was 11 documents. The 3 selection criteria were applied to those documents, and only 9% (1/11) fulfilled them [<xref ref-type="bibr" rid="ref145">145</xref>]. This study [<xref ref-type="bibr" rid="ref145">145</xref>] dealt with privacy preservation and can be included in the second role of SCs.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study aimed to provide an extensive understanding of SCs in health care through a comprehensive review of their roles and characteristics based on the frameworks developed in the literature. In doing so, this study fills a gap in the literature [<xref ref-type="bibr" rid="ref34">34</xref>]. SCs are code or short programs whose output is a transaction [<xref ref-type="bibr" rid="ref15">15</xref>] that is produced automatically when certain previously established conditions are met. These programs reflect the business logic [<xref ref-type="bibr" rid="ref15">15</xref>] and provide flexibility (requirements can be introduced) and efficiency (their execution does not need additional enforcement) to a blockchain. The extensive review of frameworks offered insights into the business logic that was prioritized.</p>
        <p>A quantitative bibliometric assessment highlighted the topic’s novelty and importance, including subjects with high relevance and development. In addition, 3 factors were identified. These factors guided the in-depth review of each framework. Two roles of SCs were found—(1) process improvement, which encompassed 6 topics; and (2) patient data privacy enhancement, which encompassed 3 topics—and technical strategies and features that provide efficiency were found. These results provide more detailed information than previous inquiries, which have mentioned only this technology’s use for medical devices, prescription tracking, remote patient monitoring, counterfeit drugs, EHRs, and incident report systems [<xref ref-type="bibr" rid="ref1">1</xref>]. In addition, several stakeholders were identified.</p>
        <p>This study acknowledged the relevance of technical topics. Previous studies have provided taxonomies based on technological features that consider the blockchain type, ledger type, consensus, identification, authentication and authorization, and EHR storage and features [<xref ref-type="bibr" rid="ref33">33</xref>]. This study provided a new perspective based on the features selected by the literature that provide efficiency to systems.</p>
        <p>The studies on trust and health care had different scopes. Some authors focused on trust in the system [<xref ref-type="bibr" rid="ref146">146</xref>,<xref ref-type="bibr" rid="ref147">147</xref>]. Others considered trust among various actors in this system, such as physicians and patients [<xref ref-type="bibr" rid="ref25">25</xref>]. Independently of the orientation, the main proposal was that trust is relevant for accomplishing health care goals. The quantitative and qualitative review findings characterized system trust in health care SCs, which considered systems [<xref ref-type="bibr" rid="ref146">146</xref>,<xref ref-type="bibr" rid="ref147">147</xref>] and actors [<xref ref-type="bibr" rid="ref25">25</xref>], through what is trusted, who trusts, and how trust is supported.</p>
        <p>Finally, this study revealed different levels of impact on the concerns of multiple health care stakeholders. Individuals’ rights—such as privacy [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref71">71</xref>], mobility [<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref85">85</xref>], or health [<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref89">89</xref>]—can be better protected. Physicians and researchers can use enhanced access to traceable and secure data when required [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref105">105</xref>]. SCs offer traceability, immutability, transparency, decentralization, automatization, and security to the different suppliers related to health care—such as hospitals, clinics, laboratories, research centers, and pharmacies—for their processes [<xref ref-type="bibr" rid="ref16">16</xref>]. Governments can also obtain benefits from SCs. SCs facilitate private compliance with governmental regulations [<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref91">91</xref>], preventing crime such as counterfeit drugs. In addition, SCs can facilitate the coordination of processes that require governmental intervention [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref81">81</xref>]. This study highlights new technologies, such as consensus and cryptographic methods, to address data security and privacy concerns. Second, this study details the different efforts to make potential solutions scalable and provide them to policyholders. Finally, this study shows the complexity of the health care systems, which is crucial for understanding the definition of multiple agreements among various involved stakeholders.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations of This Review</title>
        <p>The strength of this review lies in its systematicity and comprehensiveness. This review evaluated studies that included SCs in health care in their frameworks. We applied several procedures to reduce the risk of selection bias. The criteria used in the selection process tried to avoid researchers’ subjectivity, provide transparency, and allow for the review’s replicability [<xref ref-type="bibr" rid="ref148">148</xref>]. The PRISMA principles were followed, a peer review procedure was contemplated, 1 database was selected, and its coverage and overlap with 2 databases—a specialized and a multidisciplinary one—was assessed. Moreover, quantitative bibliometric techniques were guided by and complemented with an in-depth and detailed literature review.</p>
        <p>Even so, the selection of articles had 2 significant limitations. First, the different academic databases needed to be unified or standardized. Indeed, we had to decide between possible bias caused by the differences between databases and data wrangling or selecting 1 database and assessing its coverage and overlap. Our decision was the latter, but we acknowledge that it entails a limitation. Second, our study included only open access documents because they were relevant to guarantee the review of this study and ensure our research’s transparency.</p>
      </sec>
      <sec>
        <title>Conclusions and Further Research</title>
        <sec>
          <title>Overview</title>
          <p>The theme of SCs in health care is not only novel but also relevant. SCs reflect the business logic into the blockchain. Using SCs is advisable to enhance access to health records with advanced tiers of security and privacy. They can also solve other problems requiring security and traceability, such as counterfeit drugs. SCs provide benefits to several stakeholders, both individual (ie, patients, researchers, and physicians) and institutional (ie, hospitals, clinics, and governments), who interact in the context of the themes that SCs cover without the need to know each other or having a central authority or intermediaries, supported by the technical mechanisms that provide efficiency to the processes. SCs have limitations, such as data storage and use of resources [<xref ref-type="bibr" rid="ref129">129</xref>], but techniques have emerged to deal with these issues [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
          <p>The literature review provided some topics that could be considered in further research regarding specific stakeholders, locations, behaviors, and issues.</p>
        </sec>
        <sec>
          <title>Specific Stakeholders</title>
          <p>Although the relevance of children’s health data sharing is essential, there is a lack of studies that have dealt with the particular characteristics of this topic. The concept of patient centrality can be challenging in cases involving children and teenagers with limited control over their information. Moreover, no study has analyzed the characteristics of health care privacy protection for minors. The closest one is the study by Dagher et al [<xref ref-type="bibr" rid="ref75">75</xref>], which acknowledged possible special conditions of the owner, such as the existence of a parent or guardian [<xref ref-type="bibr" rid="ref84">84</xref>].</p>
        </sec>
        <sec>
          <title>Specific Locations</title>
          <p>SCs’ advantages can help solve problems related to low- and middle-income countries. Nevertheless, only some studies focused on solving the particular necessities of low- and middle-income countries using SCs. Abbas et al [<xref ref-type="bibr" rid="ref78">78</xref>] referred to counterfeit drugs as an extended problem in countries with weak economies, and Rai [<xref ref-type="bibr" rid="ref80">80</xref>] designed their framework for the specific case of drug traceability in India.</p>
        </sec>
        <sec>
          <title>Specific Behaviors</title>
          <p>Hawlitschek et al [<xref ref-type="bibr" rid="ref38">38</xref>] highlighted the relevance of considering fundamental interactions among people and systems. The authors named these interactions behavioral layers. It is necessary to decode these real-world behaviors so that they can be modeled into systems. This affirmation has an extended application to the SC because it oversees the deployment of business logic in the chain. Nevertheless, evidence must be provided regarding how these real-world behaviors are deciphered and converted into systems.</p>
        </sec>
        <sec>
          <title>Specific Topics</title>
          <p>First, the internet is a system requirement [<xref ref-type="bibr" rid="ref88">88</xref>] and is considered an element that provides ease and simplicity [<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref88">88</xref>,<xref ref-type="bibr" rid="ref106">106</xref>] to SCs. Nevertheless, only a few aspects are known about the proper relationship between the quality of internet connectivity and the possible expansion of the use of SCs. Second, the cost of transactions is an existing health care problem [<xref ref-type="bibr" rid="ref20">20</xref>]. SCs allow for the automation and optimization of these transactions and save costs [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref123">123</xref>]. Indeed, some studies provided a cost analysis based on the computational cost (gas cost) [<xref ref-type="bibr" rid="ref75">75</xref>] and indicated the execution cost in a specific currency [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]; a qualitative cost comparison between a blockchain-based solution and a traditional one was made [<xref ref-type="bibr" rid="ref85">85</xref>], and the execution cost based on workflow was also assessed [<xref ref-type="bibr" rid="ref123">123</xref>]. Nevertheless, contrary to other industries [<xref ref-type="bibr" rid="ref149">149</xref>-<xref ref-type="bibr" rid="ref151">151</xref>], there is a lack of studies evaluating cost as a factor in the adoption of SCs in health care.</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) checklist.</p>
        <media xlink:href="medinform_v13i1e58575_app1.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 14 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>List of 163 articles.</p>
        <media xlink:href="medinform_v13i1e58575_app2.docx" xlink:title="DOCX File , 14 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CP-ABE</term>
          <def>
            <p>ciphertext-policy attribute-based encryption</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HIPAA</term>
          <def>
            <p>Health Insurance Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">IoMT</term>
          <def>
            <p>Internet of Medical Things</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">IPFS</term>
          <def>
            <p>InterPlanetary File System</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">SC</term>
          <def>
            <p>smart contract</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">SSI</term>
          <def>
            <p>self-sovereign identity</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">WoS</term>
          <def>
            <p>Web of Science</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <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>Marbouh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Simsekler</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ellahham</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for patient safety: use cases, opportunities and open challenges</article-title>
          <source>Data</source>
          <year>2022</year>
          <month>12</month>
          <day>16</day>
          <volume>7</volume>
          <issue>12</issue>
          <fpage>182</fpage>
          <lpage>201</lpage>
          <pub-id pub-id-type="doi">10.3390/data7120182</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>Javed</surname>
              <given-names>IT</given-names>
            </name>
            <name name-style="western">
              <surname>Alharbi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bellaj</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Margaria</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Crespi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Qureshi</surname>
              <given-names>KN</given-names>
            </name>
          </person-group>
          <article-title>Health-ID: a blockchain-based decentralized identity management for remote healthcare</article-title>
          <source>Healthcare (Basel)</source>
          <year>2021</year>
          <month>06</month>
          <day>10</day>
          <volume>9</volume>
          <issue>6</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare9060712"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare9060712</pub-id>
          <pub-id pub-id-type="medline">34200778</pub-id>
          <pub-id pub-id-type="pii">healthcare9060712</pub-id>
          <pub-id pub-id-type="pmcid">PMC8230390</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>Hawashin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Musamih</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based solution for mitigating overproduction and underconsumption of medical supplies</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>07</month>
          <day>06</day>
          <volume>10</volume>
          <fpage>71669</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3188778</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>Zhuang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sheets</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Shae</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Tsai</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Shyu</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Applying blockchain technology for health information exchange and persistent monitoring for clinical trials</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2018</year>
          <month>12</month>
          <day>05</day>
          <volume>2018</volume>
          <fpage>1167</fpage>
          <lpage>75</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30815159"/>
          </comment>
          <pub-id pub-id-type="medline">30815159</pub-id>
          <pub-id pub-id-type="pmcid">PMC6371378</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhuang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>YW</given-names>
            </name>
            <name name-style="western">
              <surname>Shae</surname>
              <given-names>ZY</given-names>
            </name>
            <name name-style="western">
              <surname>Shyu</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Generalizable layered blockchain architecture for health care applications: development, case studies, and evaluation</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>07</month>
          <day>27</day>
          <volume>22</volume>
          <issue>7</issue>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/7/e19029/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19029</pub-id>
          <pub-id pub-id-type="medline">32716300</pub-id>
          <pub-id pub-id-type="pii">v22i7e19029</pub-id>
          <pub-id pub-id-type="pmcid">PMC7418010</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rahim</surname>
              <given-names>HA</given-names>
            </name>
            <name name-style="western">
              <surname>Pasha</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Dowsley</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Masud</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Baz</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Security, privacy, and reliability in digital healthcare systems using blockchain</article-title>
          <source>Electronics</source>
          <year>2021</year>
          <month>08</month>
          <day>23</day>
          <volume>10</volume>
          <issue>16</issue>
          <fpage>2034</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics10162034</pub-id>
        </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>Akhter Md Hasib</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Chowdhury</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Sakib</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Monirujjaman Khan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Alsufyani</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Alsufyani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bourouis</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record monitoring system and data security using blockchain technology</article-title>
          <source>Secur Commun Netw</source>
          <year>2022</year>
          <month>2</month>
          <day>4</day>
          <volume>2022</volume>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1155/2022/2366632</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>Gruber</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Personal trust and system trust in the sharing economy: a comparison of community- and platform-based models</article-title>
          <source>Front Psychol</source>
          <year>2020</year>
          <month>12</month>
          <day>10</day>
          <volume>11</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33362644"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2020.581299</pub-id>
          <pub-id pub-id-type="medline">33362644</pub-id>
          <pub-id pub-id-type="pmcid">PMC7758416</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>Kroeger</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Unlocking the treasure trove: how can Luhmann’s theory of trust enrich trust research?</article-title>
          <source>J Trust Res</source>
          <year>2018</year>
          <month>12</month>
          <day>20</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>110</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1080/21515581.2018.1552592</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bazarov</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gevorgyan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Karapetyan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Karieva</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kovalenko</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dallakyan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Modification of the concept of trust in the organization</article-title>
          <source>Wisdom</source>
          <year>2021</year>
          <month>09</month>
          <day>25</day>
          <volume>19</volume>
          <issue>3</issue>
          <fpage>68</fpage>
          <lpage>83</lpage>
          <pub-id pub-id-type="doi">10.24234/wisdom.v19i3.463</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Becker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bodó</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Trust in blockchain-based systems</article-title>
          <source>Internet Policy Rev</source>
          <year>2021</year>
          <month>04</month>
          <day>21</day>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.14763/2021.2.1555</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hanisch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Goldsby</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Fabian</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Oehmichen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digital governance: a conceptual framework and research agenda</article-title>
          <source>J Bus Res</source>
          <year>2023</year>
          <month>07</month>
          <day>01</day>
          <volume>162</volume>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jbusres.2023.113777</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>van der Velden</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Sustainable AI: an integrated model to guide public sector decision-making</article-title>
          <source>Technol Soc</source>
          <year>2022</year>
          <month>02</month>
          <day>01</day>
          <volume>68</volume>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.1016/j.techsoc.2022.101926</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vargas</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva</surname>
              <given-names>MM</given-names>
            </name>
          </person-group>
          <article-title>Case studies about smart contracts in healthcare</article-title>
          <source>Digit Health</source>
          <year>2023</year>
          <month>10</month>
          <day>08</day>
          <volume>9</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/20552076231203571?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/20552076231203571</pub-id>
          <pub-id pub-id-type="medline">37822961</pub-id>
          <pub-id pub-id-type="pii">10.1177_20552076231203571</pub-id>
          <pub-id pub-id-type="pmcid">PMC10563467</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abutaleb</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Alqahtany</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Syed</surname>
              <given-names>TA</given-names>
            </name>
          </person-group>
          <article-title>Integrity and privacy-aware, patient-centric health record access control framework using a blockchain</article-title>
          <source>Appl Sci</source>
          <year>2023</year>
          <month>01</month>
          <day>12</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.3390/app13021028</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>Sadawi</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Hassan</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Ndiaye</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A survey on the integration of blockchain with IoT to enhance performance and eliminate challenges</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>01</month>
          <day>19</day>
          <volume>9</volume>
          <fpage>1</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3070555</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>Hu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lei</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xing</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bao</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>CrowdMed-II: a blockchain-based framework for efficient consent management in health data sharing</article-title>
          <source>World Wide Web</source>
          <year>2022</year>
          <month>01</month>
          <day>01</day>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>1489</fpage>
          <lpage>515</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35002477"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11280-021-00923-1</pub-id>
          <pub-id pub-id-type="medline">35002477</pub-id>
          <pub-id pub-id-type="pii">923</pub-id>
          <pub-id pub-id-type="pmcid">PMC8720166</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>Zavolokina</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zani</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schwabe</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Designing for trust in blockchain platforms</article-title>
          <source>IEEE Trans Eng Manag</source>
          <year>2023</year>
          <month>3</month>
          <volume>70</volume>
          <issue>3</issue>
          <fpage>849</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.1109/tem.2020.3015359</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Imperius</surname>
              <given-names>NP</given-names>
            </name>
            <name name-style="western">
              <surname>Alahmar</surname>
              <given-names>AD</given-names>
            </name>
          </person-group>
          <article-title>Systematic mapping of testing smart contracts for blockchain applications</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <volume>10</volume>
          <fpage>112845</fpage>
          <lpage>57</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3216874</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Syed</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Alzahrani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Siddiqui</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Nadeem</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alghamdi</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>A comparative analysis of blockchain architecture and its applications: problems and recommendations</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>176838</fpage>
          <lpage>69</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2957660</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barka</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Al Baqari</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kerrache</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Herrera-Tapia</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Implementation of a biometric-based blockchain system for preserving privacy, security, and access control in healthcare records</article-title>
          <source>J Sens Actuator Netw</source>
          <year>2022</year>
          <month>12</month>
          <day>13</day>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.3390/jsan11040085</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Debe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Arshad</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based verifiable tracking of resellable returned drugs</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>10</month>
          <day>21</day>
          <volume>8</volume>
          <fpage>205848</fpage>
          <lpage>62</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3037363</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Omar</surname>
              <given-names>IA</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Simsekler</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ellahham</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Ensuring protocol compliance and data transparency in clinical trials using blockchain smart contracts</article-title>
          <source>BMC Med Res Methodol</source>
          <year>2020</year>
          <month>09</month>
          <day>07</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>17</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/s12874-020-01109-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12874-020-01109-5</pub-id>
          <pub-id pub-id-type="medline">32894068</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12874-020-01109-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7487835</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Omar</surname>
              <given-names>IA</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Debe</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Omar</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Automating procurement contracts in the healthcare supply chain using blockchain smart contracts</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>02</month>
          <day>26</day>
          <volume>9</volume>
          <fpage>2169</fpage>
          <lpage>3536</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3062471</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hasselgren</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hanssen Rensaa</surname>
              <given-names>J</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>Faxvaag</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for increased trust in virtual health care: proof-of-concept study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>07</month>
          <day>30</day>
          <volume>23</volume>
          <issue>7</issue>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/7/e28496/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/28496</pub-id>
          <pub-id pub-id-type="medline">34328437</pub-id>
          <pub-id pub-id-type="pii">v23i7e28496</pub-id>
          <pub-id pub-id-type="pmcid">PMC8367164</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>TK</given-names>
            </name>
            <name name-style="western">
              <surname>Miyachi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Fung</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Qian</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Short</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Combating health care fraud and abuse: conceptualization and prototyping study of a blockchain antifraud framework</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>09</month>
          <day>10</day>
          <volume>22</volume>
          <issue>9</issue>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/9/e18623/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18623</pub-id>
          <pub-id pub-id-type="medline">32909952</pub-id>
          <pub-id pub-id-type="pii">v22i9e18623</pub-id>
          <pub-id pub-id-type="pmcid">PMC7516680</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based multiple authorities attribute-based encryption for EHR access control scheme</article-title>
          <source>Appl Sci</source>
          <year>2022</year>
          <month>10</month>
          <day>25</day>
          <volume>12</volume>
          <issue>21</issue>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.3390/app122110812</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Qi</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Di</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pei</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Trustworthy AI: from principles to practices</article-title>
          <source>ACM Comput Surv</source>
          <year>2023</year>
          <month>01</month>
          <day>16</day>
          <volume>55</volume>
          <issue>9</issue>
          <fpage>1</fpage>
          <lpage>46</lpage>
          <pub-id pub-id-type="doi">10.1145/3555803</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Villarreal</surname>
              <given-names>ER</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia-Alonso</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Moguel</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Alegria</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for healthcare management systems: a survey on interoperability and security</article-title>
          <source>IEEE Access</source>
          <year>2023</year>
          <month>01</month>
          <day>12</day>
          <volume>11</volume>
          <fpage>2169</fpage>
          <lpage>3536</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2023.3236505</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schlatt</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Guggenberger</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Schmid</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Urbach</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Attacking the trust machine: developing an information systems research agenda for blockchain cybersecurity</article-title>
          <source>Int J Inf Manage</source>
          <year>2023</year>
          <month>02</month>
          <day>01</day>
          <volume>68</volume>
          <fpage>102470</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijinfomgt.2022.102470</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Musamih</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hasan</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Hammadi</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based solution for the administration of controlled medication</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>10</month>
          <day>20</day>
          <volume>9</volume>
          <fpage>2169</fpage>
          <lpage>3536</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3121545</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alzhrani</surname>
              <given-names>FE</given-names>
            </name>
            <name name-style="western">
              <surname>Saeedi</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A taxonomy for characterizing blockchain systems</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>10</month>
          <day>14</day>
          <volume>10</volume>
          <fpage>110568</fpage>
          <lpage>89</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3214837</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>Sookhak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jabbarpour</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Safa</surname>
              <given-names>NS</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>FR</given-names>
            </name>
          </person-group>
          <article-title>Blockchain and smart contract for access control in healthcare: a survey, issues and challenges, and open issues</article-title>
          <source>J Netw Comput Appl</source>
          <year>2021</year>
          <month>03</month>
          <day>15</day>
          <volume>178</volume>
          <fpage>102950</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jnca.2020.102950</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arbabi</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Lal</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Veeraragavan</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Marijan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nygård</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Vitenberg</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A survey on blockchain for healthcare: challenges, benefits, and future directions</article-title>
          <source>IEEE Commun Surv Tutor</source>
          <year>2023</year>
          <month>11</month>
          <day>24</day>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>386</fpage>
          <lpage>424</lpage>
          <pub-id pub-id-type="doi">10.1109/comst.2022.3224644</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khatri</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Alzahrani</surname>
              <given-names>FA</given-names>
            </name>
            <name name-style="western">
              <surname>Ansari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Agrawal</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>RA</given-names>
            </name>
          </person-group>
          <article-title>A systematic analysis on blockchain integration with healthcare domain: scope and challenges</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>06</month>
          <day>09</day>
          <volume>9</volume>
          <fpage>84666</fpage>
          <lpage>87</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3087608</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McBee</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology: principles and applications in medical imaging</article-title>
          <source>J Digit Imaging</source>
          <year>2020</year>
          <month>06</month>
          <volume>33</volume>
          <issue>3</issue>
          <fpage>726</fpage>
          <lpage>34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31898037"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10278-019-00310-3</pub-id>
          <pub-id pub-id-type="medline">31898037</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10278-019-00310-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7256149</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>McKenzie</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Bossuyt</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Boutron</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Mulrow</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Shamseer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Brennan</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Glanville</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Grimshaw</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Hróbjartsson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lalu</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loder</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Mayo-Wilson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McGuinness</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Welch</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Whiting</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The PRISMA 2020 statement: an updated guideline for reporting systematic reviews</article-title>
          <source>PLoS Med</source>
          <year>2021</year>
          <month>03</month>
          <day>29</day>
          <volume>18</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pmed.1003583"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pmed.1003583</pub-id>
          <pub-id pub-id-type="medline">33780438</pub-id>
          <pub-id pub-id-type="pii">PMEDICINE-D-21-01172</pub-id>
          <pub-id pub-id-type="pmcid">PMC8007028</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hawlitschek</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Notheisen</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Teubner</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>The limits of trust-free systems: a literature review on blockchain technology and trust in the sharing economy</article-title>
          <source>Electron Commer Res Appl</source>
          <year>2018</year>
          <month>05</month>
          <day>01</day>
          <volume>29</volume>
          <fpage>50</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.1016/j.elerap.2018.03.005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>NC</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>The field of resource-based view research: mapping past, present and future trends</article-title>
          <source>Manag Decis (Forthcoming)</source>
          <year>2024</year>
          <month>01</month>
          <day>08</day>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.emerald.com/insight/content/doi/10.1108/md-10-2023-1908/full/html"/>
          </comment>
          <pub-id pub-id-type="doi">10.1108/md-10-2023-1908</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>de Granda-Orive</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Alonso-Arroyo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Roig-Vázquez</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Which data base should we use for our literature analysis? Web of science versus SCOPUS</article-title>
          <source>Arch Bronconeumol</source>
          <year>2011</year>
          <month>02</month>
          <day>01</day>
          <volume>47</volume>
          <issue>4</issue>
          <fpage>213</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/S1579-2129(11)70049-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>LL</given-names>
            </name>
          </person-group>
          <article-title>Mapping digital innovation: a bibliometric analysis and systematic literature review</article-title>
          <source>Technol Forecast Soc Change</source>
          <year>2023</year>
          <month>09</month>
          <day>01</day>
          <volume>194</volume>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1016/j.techfore.2023.122706</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>Sabe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Perez</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Solmi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mucci</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Galderisi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Strauss</surname>
              <given-names>GP</given-names>
            </name>
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Thirty years of research on negative symptoms of schizophrenia: a scientometric analysis of hotspots, bursts, and research trends</article-title>
          <source>Neurosci Biobehav Rev</source>
          <year>2023</year>
          <month>01</month>
          <day>01</day>
          <volume>144</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0149-7634(22)00468-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.neubiorev.2022.104979</pub-id>
          <pub-id pub-id-type="medline">36463972</pub-id>
          <pub-id pub-id-type="pii">S0149-7634(22)00468-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Sher</surname>
              <given-names>CY</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>YH</given-names>
            </name>
          </person-group>
          <article-title>Progress and future directions for research on social media addiction: visualization-based bibliometric analysis</article-title>
          <source>Telemat Inform</source>
          <year>2023</year>
          <month>05</month>
          <day>01</day>
          <volume>80</volume>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.1016/j.tele.2023.101968</pub-id>
        </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>Gu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Visualizing the intellectual structure and evolution of electronic health and telemedicine research</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>10</month>
          <day>01</day>
          <volume>130</volume>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.08.007</pub-id>
          <pub-id pub-id-type="medline">31450080</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30677-4</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>Zhao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Nan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Che</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Bibliometric study on environmental, social, and governance research using CiteSpace</article-title>
          <source>Front Environ Sci</source>
          <year>2023</year>
          <month>1</month>
          <day>4</day>
          <volume>10</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.3389/fenvs.2022.1087493</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>Carmine</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>De Marchi</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Reviewing paradox theory in corporate sustainability toward a systems perspective</article-title>
          <source>J Bus Ethics</source>
          <year>2022</year>
          <month>04</month>
          <day>17</day>
          <volume>184</volume>
          <issue>1</issue>
          <fpage>139</fpage>
          <lpage>58</lpage>
          <pub-id pub-id-type="doi">10.1007/S10551-022-05112-2</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>Pranckutė</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Web of Science (WoS) and Scopus: the titans of bibliographic information in today’s academic world</article-title>
          <source>Publications</source>
          <year>2021</year>
          <month>03</month>
          <day>12</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.3390/publications9010012</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>Rotolo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Leydesdorff</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Matching Medline/PubMed data with web of science: a routine in R language</article-title>
          <source>J Assoc Inf Sci Technol</source>
          <year>2015</year>
          <month>12</month>
          <day>03</day>
          <volume>66</volume>
          <issue>10</issue>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.2139/ssrn.2451436</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Falagas</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Pitsouni</surname>
              <given-names>EI</given-names>
            </name>
            <name name-style="western">
              <surname>Malietzis</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Pappas</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Comparison of PubMed, Scopus, Web of Science, and Google Scholar: strengths and weaknesses</article-title>
          <source>FASEB J</source>
          <year>2008</year>
          <month>02</month>
          <day>22</day>
          <volume>22</volume>
          <issue>2</issue>
          <fpage>338</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1096/fj.07-9492LSF</pub-id>
          <pub-id pub-id-type="medline">17884971</pub-id>
          <pub-id pub-id-type="pii">fj.07-9492LSF</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>Li</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Same same but different: self-citations identified through Scopus and Web of Science core collection</article-title>
          <source>Scientometrics</source>
          <year>2020</year>
          <month>06</month>
          <day>19</day>
          <volume>124</volume>
          <issue>3</issue>
          <fpage>2723</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1007/S11192-020-03573-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kan Yeung</surname>
              <given-names>AW</given-names>
            </name>
          </person-group>
          <article-title>Document type assignment by Web of Science, Scopus, PubMed, and publishers to “Top 100” papers</article-title>
          <source>Malays J Libr Inf Sci</source>
          <year>2021</year>
          <month>12</month>
          <day>1</day>
          <volume>26</volume>
          <issue>3</issue>
          <fpage>97</fpage>
          <lpage>103</lpage>
          <pub-id pub-id-type="doi">10.22452/mjlis.vol26no3.5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mokhnacheva</surname>
              <given-names>YV</given-names>
            </name>
          </person-group>
          <article-title>Document types indexed in WoS and Scopus: similarities, differences, and their significance in the analysis of publication activity</article-title>
          <source>Sci Tech Inf Process</source>
          <year>2023</year>
          <month>05</month>
          <day>22</day>
          <volume>50</volume>
          <issue>1</issue>
          <fpage>40</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.3103/S0147688223010033</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kokol</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Discrepancies among Scopus and Web of Science, coverage of funding information in medical journal articles: a follow-up study</article-title>
          <source>J Med Libr Assoc</source>
          <year>2023</year>
          <month>07</month>
          <day>10</day>
          <volume>111</volume>
          <issue>3</issue>
          <fpage>703</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37483361"/>
          </comment>
          <pub-id pub-id-type="doi">10.5195/jmla.2023.1513</pub-id>
          <pub-id pub-id-type="medline">37483361</pub-id>
          <pub-id pub-id-type="pii">jmla.2023.1513</pub-id>
          <pub-id pub-id-type="pmcid">PMC10361553</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Piryani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>VK</given-names>
            </name>
            <name name-style="western">
              <surname>Pinto</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Revisiting subject classification in academic databases: a comparison of the classification accuracy of Web of Science, Scopus and Dimensions</article-title>
          <source>J Intell Fuzzy Syst</source>
          <year>2020</year>
          <month>08</month>
          <day>31</day>
          <volume>39</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.3233/jifs-179906</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kumpulainen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Seppänen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Combining Web of Science and Scopus datasets in citation-based literature study</article-title>
          <source>Scientometrics</source>
          <year>2022</year>
          <month>08</month>
          <day>25</day>
          <volume>127</volume>
          <issue>10</issue>
          <fpage>5613</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.1007/S11192-022-04475-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Archambault</surname>
              <given-names>É</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gingras</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Larivière</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Comparing bibliometric statistics obtained from the Web of Science and Scopus</article-title>
          <source>J Am Soc Inf. Sci</source>
          <year>2009</year>
          <month>04</month>
          <day>13</day>
          <volume>60</volume>
          <issue>7</issue>
          <fpage>1320</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1002/asi.21062</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gavel</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Iselid</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Web of Science and Scopus: a journal title overlap study</article-title>
          <source>Online Inf Rev</source>
          <year>2008</year>
          <month>02</month>
          <day>22</day>
          <volume>32</volume>
          <issue>1</issue>
          <fpage>8</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.1108/14684520810865958</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Visser</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Eck</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Waltman</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Large-scale comparison of bibliographic data sourcescopus, Web of Science, Dimensions, Crossref, and Microsoft Academic</article-title>
          <source>Quant Sci Stud</source>
          <year>2021</year>
          <month>01</month>
          <day>17</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>20</fpage>
          <lpage>41</lpage>
          <pub-id pub-id-type="doi">10.1162/qss_a_00112</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>VK</given-names>
            </name>
            <name name-style="western">
              <surname>Piryani</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Scholarly article retrieval from Web of Science, Scopus and Dimensions: a comparative analysis of retrieval quality</article-title>
          <source>J Inf Sci</source>
          <year>2023</year>
          <month>08</month>
          <day>21</day>
          <volume>5</volume>
          <fpage>11</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1177/01655515231191351</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aksnes</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sivertsen</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>A criteria-based assessment of the coverage of Scopus and Web of Science</article-title>
          <source>J Data Inf Sci</source>
          <year>2019</year>
          <month>02</month>
          <day>20</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.2478/jdis-2019-0001</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>Rethlefsen</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Kirtley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Waffenschmidt</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ayala</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Koffel</surname>
              <given-names>JB</given-names>
            </name>
            <collab>PRISMA-S Group</collab>
          </person-group>
          <article-title>PRISMA-S: an extension to the PRISMA statement for reporting literature searches in systematic reviews</article-title>
          <source>Syst Rev</source>
          <year>2021</year>
          <month>01</month>
          <day>26</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>39</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://systematicreviewsjournal.biomedcentral.com/articles/10.1186/s13643-020-01542-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13643-020-01542-z</pub-id>
          <pub-id pub-id-type="medline">33499930</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13643-020-01542-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC7839230</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mills</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mangone</surname>
              <given-names>ER</given-names>
            </name>
            <name name-style="western">
              <surname>Lesh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jayal</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Mohan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baraitser</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Chatbots that deliver contraceptive support: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <month>02</month>
          <day>27</day>
          <volume>26</volume>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e46758/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/46758</pub-id>
          <pub-id pub-id-type="medline">38412028</pub-id>
          <pub-id pub-id-type="pii">v26i1e46758</pub-id>
          <pub-id pub-id-type="pmcid">PMC10933731</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dwivedi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Pattanaik</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Deval</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Dixit</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Norta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Draheim</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Legally enforceable smart-contract languages</article-title>
          <source>ACM Comput Surv</source>
          <year>2021</year>
          <month>06</month>
          <day>05</day>
          <volume>54</volume>
          <issue>5</issue>
          <fpage>1</fpage>
          <lpage>34</lpage>
          <pub-id pub-id-type="doi">10.1145/3453475</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Subramanian</surname>
              <given-names>HC</given-names>
            </name>
            <name name-style="western">
              <surname>Cousins</surname>
              <given-names>KC</given-names>
            </name>
            <name name-style="western">
              <surname>Bouyad</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sheth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Conway</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Blockchain regulations and decentralized applications: panel report from AMCIS 2018</article-title>
          <source>Commun Assoc Inf Syst</source>
          <year>2020</year>
          <month>10</month>
          <day>22</day>
          <volume>47</volume>
          <issue>1</issue>
          <fpage>189</fpage>
          <lpage>207</lpage>
          <pub-id pub-id-type="doi">10.17705/1cais.04709</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Elgendy</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Aborizka</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Allam</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based model for securing IoT transactions in a healthcare environment</article-title>
          <source>Int J Adv Comput Sci Appl</source>
          <year>2022</year>
          <month>10</month>
          <day>04</day>
          <volume>13</volume>
          <issue>9</issue>
          <fpage>67</fpage>
          <lpage>75</lpage>
          <pub-id pub-id-type="doi">10.14569/IJACSA.2022.0130908</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haddaway</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Pritchard</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>McGuinness</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>PRISMA2020: an R package and shiny app for producing PRISMA 2020-compliant flow diagrams, with interactivity for optimised digital transparency and open synthesis</article-title>
          <source>Campbell Syst Rev</source>
          <year>2022</year>
          <month>06</month>
          <day>27</day>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36911350"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/cl2.1230</pub-id>
          <pub-id pub-id-type="medline">36911350</pub-id>
          <pub-id pub-id-type="pii">CL21230</pub-id>
          <pub-id pub-id-type="pmcid">PMC8958186</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aria</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cuccurullo</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>bibliometrix: an R-tool for comprehensive science mapping analysis</article-title>
          <source>J Informetr</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>959</fpage>
          <lpage>75</lpage>
          <pub-id pub-id-type="doi">10.1016/j.joi.2017.08.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dreyer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bergmann</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Köhler</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hochgraeber</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Pinkert</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Roes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Thyrian</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Wiegelmann</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Holle</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Differences and commonalities of home-based care arrangements for persons living with dementia in Germany - a theory-driven development of types using multiple correspondence analysis and hierarchical cluster analysis</article-title>
          <source>BMC Geriatr</source>
          <year>2022</year>
          <month>09</month>
          <day>01</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcgeriatr.biomedcentral.com/articles/10.1186/s12877-022-03310-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12877-022-03310-1</pub-id>
          <pub-id pub-id-type="medline">36050645</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12877-022-03310-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC9438141</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>De Moor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vandeviver</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Vander Beken</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Assessing the missing data problem in criminal network analysis using forensic DNA data</article-title>
          <source>Soc Netw</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <volume>61</volume>
          <fpage>99</fpage>
          <lpage>106</lpage>
          <pub-id pub-id-type="doi">10.1016/j.socnet.2019.09.003</pub-id>
        </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>Puri</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Kataria</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence‐powered decentralized framework for internet of things in Healthcare 4.0</article-title>
          <source>Trans Emerging Tel Tech</source>
          <year>2021</year>
          <month>03</month>
          <day>02</day>
          <volume>35</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.1002/ett.4245</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El Majdoubi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>El Bakkali</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sadki</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>SmartMedChain: a blockchain-based privacy-preserving smart healthcare framework</article-title>
          <source>J Healthc Eng</source>
          <year>2021</year>
          <month>11</month>
          <day>05</day>
          <volume>2021</volume>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2021/4145512"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2021/4145512</pub-id>
          <pub-id pub-id-type="medline">34777733</pub-id>
          <pub-id pub-id-type="pmcid">PMC8589497</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>CL</given-names>
            </name>
          </person-group>
          <article-title>A traceable blockchain-based vaccination record storage and sharing system</article-title>
          <source>J Healthc Eng</source>
          <year>2022</year>
          <month>3</month>
          <day>9</day>
          <volume>2022</volume>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2022/2211065"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2022/2211065</pub-id>
          <pub-id pub-id-type="medline">35310180</pub-id>
          <pub-id pub-id-type="pmcid">PMC8926549</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nishi</surname>
              <given-names>FK</given-names>
            </name>
            <name name-style="western">
              <surname>Shams-E-Mofiz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Alsufyani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bourouis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Saini</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>Electronic healthcare data record security using blockchain and smart contract</article-title>
          <source>J Sens</source>
          <year>2022</year>
          <month>5</month>
          <day>29</day>
          <volume>2022</volume>
          <fpage>1</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1155/2022/7299185</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Shaikh</surname>
              <given-names>ZA</given-names>
            </name>
            <name name-style="western">
              <surname>Baitenova</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mutaliyeva</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Moiseev</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mikhaylov</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Laghari</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Idris</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Alshazly</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>QoS-ledger: smart contracts and metaheuristic for secure quality-of-service and cost-efficient scheduling of medical-data processing</article-title>
          <source>Electronics</source>
          <year>2021</year>
          <month>12</month>
          <day>10</day>
          <volume>10</volume>
          <issue>24</issue>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics10243083</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dagher</surname>
              <given-names>GG</given-names>
            </name>
            <name name-style="western">
              <surname>Mohler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Milojkovic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Marella</surname>
              <given-names>PB</given-names>
            </name>
          </person-group>
          <article-title>Ancile: privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology</article-title>
          <source>Sustain Cities Soc</source>
          <year>2018</year>
          <month>05</month>
          <day>01</day>
          <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="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Razzaq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mohsan</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Ghayyur</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Kahtani</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Alkahtani</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Mostafa</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Blockchain in Healthcare: a decentralized platform for digital health passport of COVID-19 based on vaccination and immunity certificates</article-title>
          <source>Healthcare (Basel)</source>
          <year>2022</year>
          <month>12</month>
          <day>05</day>
          <volume>10</volume>
          <issue>12</issue>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare10122453"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare10122453</pub-id>
          <pub-id pub-id-type="medline">36553977</pub-id>
          <pub-id pub-id-type="pii">healthcare10122453</pub-id>
          <pub-id pub-id-type="pmcid">PMC9778149</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rashid</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Kwon</surname>
              <given-names>KR</given-names>
            </name>
          </person-group>
          <article-title>Block-HPCT: blockchain enabled digital health passports and contact tracing of infectious diseases like COVID-19</article-title>
          <source>Sensors (Basel)</source>
          <year>2022</year>
          <month>06</month>
          <day>02</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s22114256"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s22114256</pub-id>
          <pub-id pub-id-type="medline">35684876</pub-id>
          <pub-id pub-id-type="pii">s22114256</pub-id>
          <pub-id pub-id-type="pmcid">PMC9185340</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abbas</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Afaq</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed Khan</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>WC</given-names>
            </name>
          </person-group>
          <article-title>A blockchain and machine learning-based drug supply chain management and recommendation system for smart pharmaceutical industry</article-title>
          <source>Electronics</source>
          <year>2020</year>
          <month>05</month>
          <day>21</day>
          <volume>9</volume>
          <issue>5</issue>
          <fpage>1</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics9050852</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Musamih</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Arshad</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Debe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Hammadi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ellahham</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based approach for drug traceability in healthcare supply chain</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>01</month>
          <day>08</day>
          <volume>9</volume>
          <fpage>9728</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3049920</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rai</surname>
              <given-names>BK</given-names>
            </name>
          </person-group>
          <article-title>BBTCD: blockchain based traceability of counterfeited drugs</article-title>
          <source>Health Serv Outcomes Res Methodol</source>
          <year>2022</year>
          <month>11</month>
          <day>20</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>17</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36438614"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10742-022-00292-w</pub-id>
          <pub-id pub-id-type="medline">36438614</pub-id>
          <pub-id pub-id-type="pii">292</pub-id>
          <pub-id pub-id-type="pmcid">PMC9676821</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Omar</surname>
              <given-names>IA</given-names>
            </name>
            <name name-style="western">
              <surname>Debe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Omar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Arshad</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based supply chain traceability for COVID-19 personal protective equipment</article-title>
          <source>Comput Ind Eng</source>
          <year>2022</year>
          <month>05</month>
          <day>01</day>
          <volume>167</volume>
          <fpage>1</fpage>
          <lpage>30</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35153368"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cie.2022.107995</pub-id>
          <pub-id pub-id-type="medline">35153368</pub-id>
          <pub-id pub-id-type="pii">S0360-8352(22)00065-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC8817762</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Munasinghe</surname>
              <given-names>UJ</given-names>
            </name>
            <name name-style="western">
              <surname>Halgamuge</surname>
              <given-names>MN</given-names>
            </name>
          </person-group>
          <article-title>Supply chain traceability and counterfeit detection of COVID-19 vaccines using novel blockchain-based  system</article-title>
          <source>Expert Syst Appl</source>
          <year>2023</year>
          <month>10</month>
          <day>15</day>
          <volume>228</volume>
          <fpage>1</fpage>
          <lpage>25</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37197005"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.eswa.2023.120293</pub-id>
          <pub-id pub-id-type="medline">37197005</pub-id>
          <pub-id pub-id-type="pii">S0957-4174(23)00795-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC10168198</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>Gebreab</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zemerly</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Trusted traceability and certification of refurbished medical devices using dynamic composable NFTs</article-title>
          <source>IEEE Access</source>
          <year>2023</year>
          <month>03</month>
          <day>24</day>
          <volume>11</volume>
          <fpage>30373</fpage>
          <lpage>89</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2023.3261555</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>Panda</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Jena</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Das</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based distributed authentication system for healthcare</article-title>
          <source>Int J Healthc Inf. Syst Inform</source>
          <year>2021</year>
          <month>01</month>
          <day>01</day>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.4018/ijhisi.20211001.oa12</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>Lee</surname>
              <given-names>HA</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>WC</given-names>
            </name>
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>HH</given-names>
            </name>
            <name name-style="western">
              <surname>Udayasankaran</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kijsanayotin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Marcelo</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Design of a vaccine passport validation system using blockchain-based architecture: development study</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2022</year>
          <month>04</month>
          <day>26</day>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2022/4/e32411/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/32411</pub-id>
          <pub-id pub-id-type="medline">35377316</pub-id>
          <pub-id pub-id-type="pii">v8i4e32411</pub-id>
          <pub-id pub-id-type="pmcid">PMC9045485</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>Kuo</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Pham</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Edelson</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ohno-Machado</surname>
              <given-names>L</given-names>
            </name>
            <collab>R2D2 Consortium</collab>
          </person-group>
          <article-title>Blockchain-enabled immutable, distributed, and highly available clinical research activity logging system for federated COVID-19 data analysis from multiple institutions</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2023</year>
          <month>05</month>
          <day>19</day>
          <volume>30</volume>
          <issue>6</issue>
          <fpage>1167</fpage>
          <lpage>78</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36916740"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocad049</pub-id>
          <pub-id pub-id-type="medline">36916740</pub-id>
          <pub-id pub-id-type="pii">7077141</pub-id>
          <pub-id pub-id-type="pmcid">PMC10198529</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>Kuo</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Pham</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Quorum-based model learning on a blockchain hierarchical clinical research network using smart contracts</article-title>
          <source>Int J Med Inform</source>
          <year>2023</year>
          <month>01</month>
          <day>01</day>
          <volume>169</volume>
          <fpage>1</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(22)00238-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2022.104924</pub-id>
          <pub-id pub-id-type="medline">36402113</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(22)00238-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC9984225</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>Ksibi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mhamdi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ayadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Almuqren</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Alqahtani</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Ansari</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hedi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Secure and fast emergency road healthcare service based on blockchain technology for smart cities</article-title>
          <source>Sustainability</source>
          <year>2023</year>
          <month>03</month>
          <day>25</day>
          <volume>15</volume>
          <issue>7</issue>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.3390/su15075748</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>Peyvandi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Majidi</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Peyvandi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patra</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Computer-aided-diagnosis as a service on decentralized medical cloud for efficient and rapid emergency response intelligence</article-title>
          <source>New Gener Comput</source>
          <year>2021</year>
          <month>06</month>
          <day>27</day>
          <volume>39</volume>
          <issue>3-4</issue>
          <fpage>677</fpage>
          <lpage>700</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34219860"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s00354-021-00131-5</pub-id>
          <pub-id pub-id-type="medline">34219860</pub-id>
          <pub-id pub-id-type="pii">131</pub-id>
          <pub-id pub-id-type="pmcid">PMC8236221</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>Li</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mathew</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>ChainSDI: a software-defined infrastructure for regulation-compliant home-based healthcare services secured by blockchains</article-title>
          <source>IEEE Syst J</source>
          <year>2020</year>
          <month>09</month>
          <day>18</day>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>2042</fpage>
          <lpage>53</lpage>
          <pub-id pub-id-type="doi">10.1109/jsyst.2019.2937930</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barati</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aujla</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Llanos</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Duodu</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Rana</surname>
              <given-names>OF</given-names>
            </name>
            <name name-style="western">
              <surname>Carr</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ranjan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Privacy-aware cloud auditing for GDPR compliance verification in online healthcare</article-title>
          <source>IEEE Trans Ind Inf</source>
          <year>2022</year>
          <month>7</month>
          <day>27</day>
          <volume>18</volume>
          <issue>7</issue>
          <fpage>4808</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1109/tii.2021.3100152</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rai</surname>
              <given-names>BK</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-enabled electronic health records for healthcare 4.0</article-title>
          <source>Int J E-Health Med Commun</source>
          <year>2022</year>
          <month>01</month>
          <day>01</day>
          <volume>13</volume>
          <issue>4</issue>
          <fpage>342</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.4018/ijehmc.309438</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kshirsagar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vaidya</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ducrée</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Convergence of blockchain, autonomous agents, and knowledge graph to share electronic health records</article-title>
          <source>Front Blockchain</source>
          <year>2021</year>
          <month>4</month>
          <day>6</day>
          <volume>4</volume>
          <fpage>33</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.3389/fbloc.2021.661238</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sonkamble</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Bongale</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Phansalkar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rajput</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Secure data transmission of electronic health records using blockchain technology</article-title>
          <source>Electronics</source>
          <year>2023</year>
          <month>02</month>
          <day>17</day>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics12041015</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>De Oliveira</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Reis</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Verginadis</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mattos</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Olabarriaga</surname>
              <given-names>SD</given-names>
            </name>
          </person-group>
          <article-title>SmartAccess: attribute-based access control system for medical records based on smart contracts</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>10</month>
          <day>26</day>
          <volume>10</volume>
          <fpage>117836</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3217201</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>Hashim</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Shuaib</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sallabi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Connected blockchain federations for sharing electronic health records</article-title>
          <source>Cryptography</source>
          <year>2022</year>
          <month>09</month>
          <day>16</day>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.3390/cryptography6030047</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iqbal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Matulevicius</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Exploring sybil and double-spending risks in blockchain systems</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>05</month>
          <day>19</day>
          <volume>9</volume>
          <fpage>76153</fpage>
          <lpage>77</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3081998</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Madine</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Hammadi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ellahham</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Calyam</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Fully decentralized multi-party consent management for secure sharing of patient health records</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>12</month>
          <day>15</day>
          <volume>8</volume>
          <fpage>225777</fpage>
          <lpage>91</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3045048</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>Saidi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Labraoui</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ari</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Maglaras</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Emati</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>DSMAC: privacy-aware decentralized self-management of data access control based on blockchain for health data</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>09</month>
          <day>29</day>
          <volume>10</volume>
          <fpage>101011</fpage>
          <lpage>28</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3207803</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hussien</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Yasin</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Udzir</surname>
              <given-names>NI</given-names>
            </name>
            <name name-style="western">
              <surname>Ninggal</surname>
              <given-names>MI</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based access control scheme for secure shared personal health records over decentralised storage</article-title>
          <source>Sensors (Basel)</source>
          <year>2021</year>
          <month>04</month>
          <day>02</day>
          <volume>21</volume>
          <issue>7</issue>
          <fpage>1</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s21072462"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s21072462</pub-id>
          <pub-id pub-id-type="medline">33918266</pub-id>
          <pub-id pub-id-type="pii">s21072462</pub-id>
          <pub-id pub-id-type="pmcid">PMC8038200</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>MEXchange: a privacy-preserving blockchain-based framework for health information exchange using ring signature and stealth address</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>11</month>
          <day>25</day>
          <volume>9</volume>
          <fpage>158122</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3130552</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Raj</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Prakash</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Smart contract-based secure decentralized smart healthcare system</article-title>
          <source>Int J Softw Innov</source>
          <year>2022</year>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.4018/ijsi.315742</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhuang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sheets</surname>
              <given-names>LR</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>YW</given-names>
            </name>
            <name name-style="western">
              <surname>Shae</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Tsai</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Shyu</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A patient-centric health information exchange framework using blockchain technology</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2020</year>
          <month>8</month>
          <day>01</day>
          <volume>24</volume>
          <issue>8</issue>
          <fpage>2169</fpage>
          <lpage>76</lpage>
          <pub-id pub-id-type="doi">10.1109/jbhi.2020.2993072</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Celesti</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ruggeri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fazio</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Galletta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Villari</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Romano</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based healthcare workflow for tele-medical laboratory in federated hospital IoT clouds</article-title>
          <source>Sensors (Basel)</source>
          <year>2020</year>
          <month>05</month>
          <day>02</day>
          <volume>20</volume>
          <issue>9</issue>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s20092590"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s20092590</pub-id>
          <pub-id pub-id-type="medline">32370129</pub-id>
          <pub-id pub-id-type="pii">s20092590</pub-id>
          <pub-id pub-id-type="pmcid">PMC7249089</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Azbeg</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ouchetto</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Jai Andaloussi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>BlockMedCare: a healthcare system based on IoT, Blockchain and IPFS for data management security</article-title>
          <source>Egypt Inform J</source>
          <year>2022</year>
          <month>07</month>
          <day>01</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>329</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.1016/j.eij.2022.02.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Daraghmi</surname>
              <given-names>EY</given-names>
            </name>
            <name name-style="western">
              <surname>Daraghmi</surname>
              <given-names>YA</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>MedChain: a design of blockchain-based system for medical records access and permissions management</article-title>
          <source>IEEE Access</source>
          <year>2019</year>
          <month>11</month>
          <day>21</day>
          <volume>7</volume>
          <fpage>164595</fpage>
          <lpage>613</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2019.2952942</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gohar</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Abdelmawgoud</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Farhan</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <article-title>A patient-centric healthcare framework reference architecture for better semantic interoperability based on blockchain, cloud, and IoT</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>08</month>
          <day>29</day>
          <volume>10</volume>
          <fpage>92137</fpage>
          <lpage>57</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3202902</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haddad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Habaebi</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Suliman</surname>
              <given-names>FE</given-names>
            </name>
            <name name-style="western">
              <surname>Elsheikh</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Zabidi</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Generic patient-centered blockchain-based EHR management system</article-title>
          <source>Appl Sci</source>
          <year>2023</year>
          <month>01</month>
          <day>30</day>
          <volume>13</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.3390/app13031761</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnamurthi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Nayyar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Grover</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Hossain</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>A novel smart healthcare design, simulation, and implementation using healthcare 4.0 processes</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>06</month>
          <day>25</day>
          <volume>8</volume>
          <fpage>118433</fpage>
          <lpage>71</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3004790</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mhamdi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ayadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ksibi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Rasheed</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Soufiene</surname>
              <given-names>BO</given-names>
            </name>
            <name name-style="western">
              <surname>Hedi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>SEMRAchain: a secure electronic medical record based on blockchain technology</article-title>
          <source>Electronics</source>
          <year>2022</year>
          <month>11</month>
          <day>06</day>
          <volume>11</volume>
          <issue>21</issue>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics11213617</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Palanikkumar</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Alrasheedi</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Parthasarathi</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Askar</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Abouhawwash</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Hybrid smart contracts for securing IoMT data</article-title>
          <source>Comput Syst Sci Eng</source>
          <year>2023</year>
          <month>01</month>
          <day>07</day>
          <volume>44</volume>
          <issue>1</issue>
          <fpage>457</fpage>
          <lpage>69</lpage>
          <pub-id pub-id-type="doi">10.32604/csse.2023.024884</pub-id>
        </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>Sonkamble</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Phansalkar</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Potdar</surname>
              <given-names>VM</given-names>
            </name>
            <name name-style="western">
              <surname>Bongale</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Survey of interoperability in electronic health records management and proposed blockchain based framework: MyBlockEHR</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>11</month>
          <day>18</day>
          <volume>9</volume>
          <fpage>158367</fpage>
          <lpage>401</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3129284</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>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ning</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ying</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-enabled decentralized attribute-based access control with policy hiding for smart healthcare</article-title>
          <source>J King Saud Univ Comput Inf Sci</source>
          <year>2022</year>
          <month>11</month>
          <day>01</day>
          <volume>34</volume>
          <issue>10</issue>
          <fpage>8350</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jksuci.2022.08.015</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>Salonikias</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khair</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mastoras</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Mavridis</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based access control in a globalized healthcare provisioning ecosystem</article-title>
          <source>Electronics</source>
          <year>2022</year>
          <month>08</month>
          <day>25</day>
          <volume>11</volume>
          <issue>17</issue>
          <fpage>1</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics11172652</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>Jadav</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jadav</surname>
              <given-names>NK</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Tanwar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Alfarraj</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Tolba</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Raboaca</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Marina</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>A trustworthy healthcare management framework using amalgamation of AI and blockchain network</article-title>
          <source>Mathematics</source>
          <year>2023</year>
          <month>01</month>
          <day>27</day>
          <volume>11</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.3390/math11030637</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>Dhasarathan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hasan</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Abdullah</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khapre</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Alsulami</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Alqahtani</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>User privacy prevention model using supervised federated learning‐based block chain approach for internet of Medical Things</article-title>
          <source>CAAI Trans Intell Technol</source>
          <year>2023</year>
          <month>05</month>
          <day>04</day>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1049/cit2.12218</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shahbazi</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Byun</surname>
              <given-names>YC</given-names>
            </name>
          </person-group>
          <article-title>Towards a secure thermal-energy aware routing protocol in wireless body area network based on blockchain technology</article-title>
          <source>Sensors (Basel)</source>
          <year>2020</year>
          <month>06</month>
          <day>26</day>
          <volume>20</volume>
          <issue>12</issue>
          <fpage>1</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s20123604"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s20123604</pub-id>
          <pub-id pub-id-type="medline">32604851</pub-id>
          <pub-id pub-id-type="pii">s20123604</pub-id>
          <pub-id pub-id-type="pmcid">PMC7349352</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Taralunga</surname>
              <given-names>DD</given-names>
            </name>
            <name name-style="western">
              <surname>Florea</surname>
              <given-names>BC</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-enabled framework for mHealth systems</article-title>
          <source>Sensors (Basel)</source>
          <year>2021</year>
          <month>04</month>
          <day>16</day>
          <volume>21</volume>
          <issue>8</issue>
          <fpage>1</fpage>
          <lpage>24</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s21082828"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s21082828</pub-id>
          <pub-id pub-id-type="medline">33923842</pub-id>
          <pub-id pub-id-type="pii">s21082828</pub-id>
          <pub-id pub-id-type="pmcid">PMC8073055</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Masud</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gaba</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gurtov</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A user-centric privacy-preserving authentication protocol for IoT-AmI environments</article-title>
          <source>Comput Commun</source>
          <year>2022</year>
          <month>12</month>
          <day>01</day>
          <volume>196</volume>
          <fpage>45</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.1016/j.comcom.2022.09.021</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>Abugabah</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nizamuddin</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Alzubi</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>Decentralized telemedicine framework for a smart healthcare ecosystem</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>09</month>
          <day>04</day>
          <volume>8</volume>
          <fpage>2169</fpage>
          <lpage>3536</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3021823</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baiju</surname>
              <given-names>VB</given-names>
            </name>
            <name name-style="western">
              <surname>Saranya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sriram</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Mohammed</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Decentralizing electronic medical records on the blockchain using smart contracts</article-title>
          <source>J Pharm Negat Results</source>
          <year>2022</year>
          <month>01</month>
          <day>01</day>
          <volume>13</volume>
          <issue>SO3</issue>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.47750/pnr.2022.13.s03.050</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Akkaoui</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hei</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>EdgeMediChain: a hybrid edge blockchain-based framework for health data exchange</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>06</month>
          <day>19</day>
          <volume>8</volume>
          <fpage>113467</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3003575</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ravikumar</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Venkatachalam</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Masud</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abouhawwash</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Cost efficient scheduling using smart contract cognizant Ethereum for IoMT</article-title>
          <source>Intell Autom Soft Comput</source>
          <year>2022</year>
          <month>01</month>
          <day>01</day>
          <volume>33</volume>
          <issue>2</issue>
          <fpage>865</fpage>
          <lpage>77</lpage>
          <pub-id pub-id-type="doi">10.32604/iasc.2022.024278</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref124">
        <label>124</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lakhan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mohammed</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Rashid</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Kadry</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Panityakul</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Abdulkareem</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Thinnukool</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Smart-contract aware Ethereum and client-fog-cloud healthcare system</article-title>
          <source>Sensors (Basel)</source>
          <year>2021</year>
          <month>06</month>
          <day>14</day>
          <volume>21</volume>
          <issue>12</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s21124093"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s21124093</pub-id>
          <pub-id pub-id-type="medline">34198608</pub-id>
          <pub-id pub-id-type="pii">s21124093</pub-id>
          <pub-id pub-id-type="pmcid">PMC8232207</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shaikh</surname>
              <given-names>ZA</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Teng</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wagan</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Laghari</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>BIoMT modular infrastructure: the recent challenges, issues, and limitations in blockchain Hyperledger-enabled e-healthcare application</article-title>
          <source>Wirel Commun Mob Comput</source>
          <year>2022</year>
          <month>9</month>
          <day>21</day>
          <volume>2022</volume>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1155/2022/3813841</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abou-Nassar</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Iliyasu</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>El-Kafrawy</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>OY</given-names>
            </name>
            <name name-style="western">
              <surname>Bashir</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>El-Latif</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>DITrust chain: towards blockchain-based trust models for sustainable healthcare IoT systems</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>06</month>
          <day>02</day>
          <volume>8</volume>
          <fpage>111223</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.2999468</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iqbal</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jamil</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmad</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A novel blockchain-based integrity and reliable veterinary clinic information management system using predictive analytics for provisioning of quality health services</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <month>01</month>
          <day>05</day>
          <volume>9</volume>
          <fpage>8069</fpage>
          <lpage>98</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3049325</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref128">
        <label>128</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vacca</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Di Sorbo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Visaggio</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Canfora</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>A systematic literature review of blockchain and smart contract development: techniques, tools, and open challenges</article-title>
          <source>J Syst Softw</source>
          <year>2021</year>
          <month>04</month>
          <day>01</day>
          <volume>174</volume>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jss.2020.110891</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref129">
        <label>129</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Xiong</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Xiong</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yi</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>A review on recent progress of smart contract in blockchain</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>05</month>
          <day>10</day>
          <volume>10</volume>
          <fpage>50839</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3174052</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref130">
        <label>130</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maia</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>de Benedicto</surname>
              <given-names>GC</given-names>
            </name>
            <name name-style="western">
              <surname>do Prado</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Robb</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>de Almeida Bispo</surname>
              <given-names>ON</given-names>
            </name>
            <name name-style="western">
              <surname>de Brito</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Mapping the literature on credit unions: a bibliometric investigation grounded in Scopus and Web of Science</article-title>
          <source>Scientometrics</source>
          <year>2019</year>
          <month>7</month>
          <day>5</day>
          <volume>120</volume>
          <issue>3</issue>
          <fpage>929</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1007/S11192-019-03165-1</pub-id>
        </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>Hylock</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>A blockchain framework for patient-centered health records and exchange (HealthChain): evaluation and proof-of-concept study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>08</month>
          <day>31</day>
          <volume>21</volume>
          <issue>8</issue>
          <fpage>1</fpage>
          <lpage>19</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/8/e13592/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13592</pub-id>
          <pub-id pub-id-type="medline">31471959</pub-id>
          <pub-id pub-id-type="pii">v21i8e13592</pub-id>
          <pub-id pub-id-type="pmcid">PMC6743266</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref132">
        <label>132</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>DH</given-names>
            </name>
          </person-group>
          <article-title>A novel EMR integrity management based on a medical blockchain platform in hospital</article-title>
          <source>Electronics</source>
          <year>2019</year>
          <month>04</month>
          <day>25</day>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>27</lpage>
          <pub-id pub-id-type="doi">10.3390/electronics8040467</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref133">
        <label>133</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jaiman</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Urovi</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>A consent model for blockchain-based health data sharing platforms</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>08</month>
          <day>05</day>
          <volume>8</volume>
          <fpage>143734</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3014565</pub-id>
        </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>Madine</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Battah</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jayaraman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Hammadi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Pesic</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ellahham</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain for giving patients control over their medical records</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>10</month>
          <day>20</day>
          <volume>8</volume>
          <fpage>193102</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.3032553</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref135">
        <label>135</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vangipuram</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Mohanty</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Kougianos</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>CoviChain: a blockchain based framework for nonrepudiable contact tracing in healthcare cyber-physical systems during pandemic outbreaks</article-title>
          <source>SN Comput Sci</source>
          <year>2021</year>
          <month>06</month>
          <day>20</day>
          <volume>2</volume>
          <issue>5</issue>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34179827"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s42979-021-00746-x</pub-id>
          <pub-id pub-id-type="medline">34179827</pub-id>
          <pub-id pub-id-type="pii">746</pub-id>
          <pub-id pub-id-type="pmcid">PMC8214843</pub-id>
        </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>Hasan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chowdhury</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Biswas</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Usman</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based secure data-sharing framework for software defined wireless body area networks</article-title>
          <source>Computer Networks</source>
          <year>2022</year>
          <month>07</month>
          <day>01</day>
          <volume>211</volume>
          <fpage>1</fpage>
          <lpage>28</lpage>
          <pub-id pub-id-type="doi">10.1016/j.comnet.2022.109004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref137">
        <label>137</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>A blockchain-based secure storage scheme for medical information</article-title>
          <source>J Wireless Com Network</source>
          <year>2022</year>
          <month>04</month>
          <day>25</day>
          <volume>2022</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1186/S13638-022-02122-6</pub-id>
        </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>Puneeth</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Parthasarathy</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Seamless data exchange: advancing healthcare with cross-chain interoperability in blockchain for electronic health records</article-title>
          <source>Int J Adv Comput Sci Appl</source>
          <year>2023</year>
          <month>01</month>
          <day>01</day>
          <volume>14</volume>
          <issue>10</issue>
          <fpage>280</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.14569/ijacsa.2023.0141031</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>Rastogi</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bedi</surname>
              <given-names>SS</given-names>
            </name>
          </person-group>
          <article-title>Fully decentralized block chain with proxy re-encryption algorithm for healthcare security</article-title>
          <source>Int J Adv Comput Sci Appl</source>
          <year>2023</year>
          <month>2</month>
          <day>28</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>572</fpage>
          <lpage>83</lpage>
          <pub-id pub-id-type="doi">10.22266/ijies2023.0228.49</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref140">
        <label>140</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Jacky</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Amin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Miah</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Hossain</surname>
              <given-names>MI</given-names>
            </name>
          </person-group>
          <article-title>Distributed ledger technology based integrated healthcare solution for Bangladesh</article-title>
          <source>IEEE Access</source>
          <year>2023</year>
          <month>05</month>
          <day>24</day>
          <volume>11</volume>
          <fpage>51527</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2023.3279724</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref141">
        <label>141</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amponsah</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Adekoya</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Weyori</surname>
              <given-names>BA</given-names>
            </name>
          </person-group>
          <article-title>A novel fraud detection and prevention method for healthcare claim processing using machine learning and blockchain technology</article-title>
          <source>Decis Anal J</source>
          <year>2022</year>
          <month>09</month>
          <day>01</day>
          <volume>4</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1016/j.dajour.2022.100122</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>Taylor</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kugler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marella</surname>
              <given-names>PB</given-names>
            </name>
            <name name-style="western">
              <surname>Dagher</surname>
              <given-names>GG</given-names>
            </name>
          </person-group>
          <article-title>VigilRx: a scalable and interoperable prescription management system using blockchain</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <month>03</month>
          <day>02</day>
          <volume>10</volume>
          <fpage>25973</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3156015</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref143">
        <label>143</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karmakar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ghosh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Banerjee</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>De</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>ChainSure: agent free insurance system using blockchain for healthcare 4.0</article-title>
          <source>Intell Syst Appl</source>
          <year>2023</year>
          <month>02</month>
          <day>01</day>
          <volume>17</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1016/j.iswa.2023.200177</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref144">
        <label>144</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rai</surname>
              <given-names>BK</given-names>
            </name>
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-based traceability of counterfeited drugs</article-title>
          <source>Int J Reliab Qual E-Healthc</source>
          <year>2023</year>
          <month>5</month>
          <day>01</day>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.4018/IJRQEH.318129</pub-id>
        </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>Rodriguez-Garcia</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sicilia</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Dodero</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>A privacy-preserving design for sharing demand-driven patient datasets over permissioned blockchains and P2P secure transfer</article-title>
          <source>PeerJ Comput Sci</source>
          <year>2021</year>
          <month>06</month>
          <day>09</day>
          <volume>7</volume>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34179449"/>
          </comment>
          <pub-id pub-id-type="doi">10.7717/peerj-cs.568</pub-id>
          <pub-id pub-id-type="medline">34179449</pub-id>
          <pub-id pub-id-type="pii">cs-568</pub-id>
          <pub-id pub-id-type="pmcid">PMC8205266</pub-id>
        </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>Baguso</surname>
              <given-names>GN</given-names>
            </name>
            <name name-style="western">
              <surname>Aguilar</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sicro</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mañacop</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Quintana</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>EC</given-names>
            </name>
          </person-group>
          <article-title>"Lost trust in the system": system barriers to publicly available mental health and substance use services for transgender women in San Francisco</article-title>
          <source>BMC Health Serv Res</source>
          <year>2022</year>
          <month>07</month>
          <day>19</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-022-08315-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-022-08315-5</pub-id>
          <pub-id pub-id-type="medline">35854359</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-022-08315-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC9295874</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>Marín-Cos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marbán-Castro</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Nedic</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ferrari</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Crespo-Mirasol</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ventura</surname>
              <given-names>LF</given-names>
            </name>
            <name name-style="western">
              <surname>Zamora</surname>
              <given-names>BN</given-names>
            </name>
            <name name-style="western">
              <surname>Fumadó</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Menéndez</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Martínez Bueno</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Llupià</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>López</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Goncé</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bardají</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>"Maternal vaccination greatly depends on your trust in the healthcare system": a qualitative study on the acceptability of maternal vaccines among pregnant women and healthcare workers in Barcelona, Spain</article-title>
          <source>Vaccines (Basel)</source>
          <year>2022</year>
          <month>11</month>
          <day>25</day>
          <volume>10</volume>
          <issue>12</issue>
          <fpage>1</fpage>
          <lpage>17</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=vaccines10122015"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/vaccines10122015</pub-id>
          <pub-id pub-id-type="medline">36560425</pub-id>
          <pub-id pub-id-type="pii">vaccines10122015</pub-id>
          <pub-id pub-id-type="pmcid">PMC9783547</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>Rojon</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McDowall</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Saunders</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>On the experience of conducting a systematic review in industrial, work, and organizational psychology</article-title>
          <source>J Pers Psychol</source>
          <year>2011</year>
          <month>01</month>
          <day>23</day>
          <volume>10</volume>
          <issue>3</issue>
          <fpage>133</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1027/1866-5888/A000041</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>Ameyaw</surname>
              <given-names>EE</given-names>
            </name>
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Thurairajah</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Owusu-Manu</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Oppong</surname>
              <given-names>GD</given-names>
            </name>
          </person-group>
          <article-title>Critical factors influencing adoption of blockchain-enabled smart contracts in construction projects</article-title>
          <source>J Constr Eng Manag</source>
          <year>2023</year>
          <month>03</month>
          <day>01</day>
          <volume>149</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1061/jcemd4.coeng-12081</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref150">
        <label>150</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Budayan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Okudan</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Assessment of barriers to the implementation of smart contracts in construction projects—evidence from Turkey</article-title>
          <source>Buildings</source>
          <year>2023</year>
          <month>08</month>
          <day>17</day>
          <volume>13</volume>
          <issue>8</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.3390/buildings13082084</pub-id>
        </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>Shang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Pheng</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Xia</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Adoption of smart contracts in the construction industry: an institutional analysis of drivers and barriers</article-title>
          <source>Constr Innov</source>
          <year>2023</year>
          <month>04</month>
          <day>06</day>
          <volume>24</volume>
          <issue>5</issue>
          <fpage>1401</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.1108/ci-03-2022-0066</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
