﻿<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "JATS-journalpublishing1.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="systematic-review">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Explor Digit Health Technol</journal-id>
<journal-id journal-id-type="publisher-id">EDHT</journal-id>
<journal-title-group>
<journal-title>Exploration of Digital Health Technologies</journal-title>
</journal-title-group>
<issn pub-type="epub">2996-9409</issn>
<publisher>
<publisher-name>Open Exploration Publishing</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.37349/edht.2024.00014</article-id>
<article-id pub-id-type="manuscript">101114</article-id>
<article-categories>
<subj-group>
<subject>Systematic Review</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Do you need a blockchain in healthcare data sharing? A tertiary review</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid">https://orcid.org/0009-0000-2744-7417</contrib-id>
<name>
<surname>Li</surname>
<given-names>Kun</given-names>
</name>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role content-type="https://credit.niso.org/contributor-roles/investigation/">Investigation</role>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing—original draft</role>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing—review &amp; editing</role>
<xref ref-type="aff" rid="I1">
<sup>1</sup>
</xref>
<xref ref-type="corresp" rid="cor1">
<sup>*</sup>
</xref>
</contrib>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0003-3639-2854</contrib-id>
<name>
<surname>Sai</surname>
<given-names>Ashish Rajendra</given-names>
</name>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing—original draft</role>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing—review &amp; editing</role>
<xref ref-type="aff" rid="I2">
<sup>2</sup>
</xref>
</contrib>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0003-2817-3950</contrib-id>
<name>
<surname>Urovi</surname>
<given-names>Visara</given-names>
</name>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing—review &amp; editing</role>
<role content-type="https://credit.niso.org/contributor-roles/supervision/">Supervision</role>
<xref ref-type="aff" rid="I1">
<sup>1</sup>
</xref>
</contrib>
<contrib contrib-type="editor">
<name>
<surname>Asche</surname>
<given-names>Carl</given-names>
</name>
<role>Academic Editor</role>
<aff>University of Utah Health, USA</aff>
</contrib>
</contrib-group>
<aff id="I1">
<sup>1</sup>Institute of Data Science, Maastricht University, 6229 EN Maastricht, The Netherlands</aff>
<aff id="I2">
<sup>2</sup>Department of Advanced Computing Sciences, Maastricht University, 6229 EN Maastricht, The Netherlands</aff>
<author-notes>
<corresp id="cor1">
<sup>*</sup>
<bold>Correspondence:</bold> Kun Li, Institute of Data Science, Maastricht University, Paul-Henri Spaaklaan 1, 6229 EN Maastricht, The Netherlands. <email>k.li@maastrichtuniversity.nl</email></corresp>
</author-notes>
<pub-date pub-type="ppub">
<year>2024</year>
</pub-date>
<pub-date pub-type="epub">
<day>14</day>
<month>06</month>
<year>2024</year>
</pub-date>
<volume>2</volume>
<issue>3</issue>
<fpage>101</fpage>
<lpage>123</lpage>
<history>
<date date-type="received">
<day>10</day>
<month>02</month>
<year>2024</year>
</date>
<date date-type="accepted">
<day>25</day>
<month>04</month>
<year>2024</year>
</date>
</history>
<permissions>
<copyright-statement>© The Author(s) 2024.</copyright-statement>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This is an Open Access article licensed under a Creative Commons Attribution 4.0 International License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, sharing, adaptation, distribution and reproduction in any medium or format, for any purpose, even commercially, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.</license-p>
</license>
</permissions>
<abstract>
<sec>
<title>Background:</title>
<p id="absp-1">This study addresses the complexities of utilizing blockchain technology in healthcare, aiming to provide a decision-making tool for healthcare professionals and policymakers evaluating blockchain’s suitability for healthcare data sharing applications.</p>
</sec>
<sec>
<title>Methods:</title>
<p id="absp-2">A tertiary review was conducted on existing systematic literature reviews concerning blockchain in the healthcare domain. Reviews that focused on data sharing were selected, and common key factors assessing blockchain’s suitability in healthcare were extracted.</p>
</sec>
<sec>
<title>Results:</title>
<p id="absp-3">Our review synthesized findings from 27 systematic literature reviews, which led to the development of a refined decision-making flowchart. This tool outlines criteria such as scalability, integrity/immutability, interoperability, transparency, patient involvement, cost, and public verifiability, essential for assessing the suitability of blockchain in healthcare data sharing. This flowchart was validated through multiple case studies from various healthcare domains, testing its utility in real-world scenarios.</p>
</sec>
<sec>
<title>Discussion:</title>
<p id="absp-4">Blockchain technology could significantly benefit healthcare data sharing, provided its application is carefully evaluated against tailored criteria for healthcare needs. The decision-making flowchart developed from this review offers a systematic approach to assist stakeholders in navigating the complexities of implementing blockchain technology in healthcare settings.</p>
</sec>
</abstract>
<kwd-group>
<kwd>Blockchain</kwd>
<kwd>healthcare data sharing</kwd>
<kwd>decision-making</kwd>
<kwd>systematic literature review</kwd>
</kwd-group>
<funding-group>
<award-group id="award001">
<funding-source>
<institution-wrap>
<institution>the China Scholarship Council</institution>
</institution-wrap>
</funding-source>
<award-id>202109650003</award-id>
</award-group>
</funding-group>
</article-meta>
</front>
<body>
<sec id="s1">
<title>Introduction</title>
<p id="p-1">Blockchain technology has received considerable attention as a potentially transformative innovation through cryptocurrency [<xref ref-type="bibr" rid="B1">1</xref>]. However, skepticism has grown regarding its practical, real-world applications, particularly beyond cryptocurrencies and associated use cases [<xref ref-type="bibr" rid="B2">2</xref>]. In healthcare, specifically, the promises of blockchain technology may not have materialized yet despite academic surveys highlighting its potential for enhancing data sharing, security, and decentralization of patient information [<xref ref-type="bibr" rid="B3">3</xref>].</p>
<p id="p-2">One primary concern is the lack of real-world applications, as noted in the literature [<xref ref-type="bibr" rid="B4">4</xref>]. This lack of practical examples hinders the ability of healthcare professionals to fully understand and evaluate the applicability of blockchain technology in the healthcare domain. Additionally, the implementation of blockchain technology is often characterized by inherent complexity [<xref ref-type="bibr" rid="B5">5</xref>]. A case in point is the concept of decentralization within the blockchain, which lacks standardized definitions and a clear understanding [<xref ref-type="bibr" rid="B6">6</xref>]. The absence of comprehensive guidelines and frameworks exacerbates these issues, leaving healthcare professionals and policymakers uncertain regarding the suitability and potential trade-offs of adopting blockchain technology [<xref ref-type="bibr" rid="B5">5</xref>]. Addressing these gaps is crucial for informed decision-making and effective integration of blockchain.</p>
<p id="p-3">Existing research articles, such as [<xref ref-type="bibr" rid="B3">3</xref>, <xref ref-type="bibr" rid="B7">7</xref>], exploring blockchain in a healthcare context, present potential use cases and discuss areas where blockchain could be advantageous. However, these articles often need a more transparent framework for decisively determining the appropriateness of blockchain technology for a given healthcare issue. The absence of a systematic decision-making process may be a challenge faced by healthcare professionals and policymakers in establishing the relevance of blockchain in the healthcare domain. In this study, we aim to answer the following question:</p>
<p id="p-4">
<list list-type="bullet">
<list-item>
<p>Which decision-making criteria are important in assessing the suitability of blockchain technology for sharing healthcare data?</p>
</list-item>
</list>
</p>
<p id="p-5">To answer this question, we developed a novel conceptual framework and decision-making flowchart that assists healthcare stakeholders in understanding the usefulness of blockchain technology in healthcare settings. Building upon the work of Wüst and Gervais [<xref ref-type="bibr" rid="B8">8</xref>], we conducted a tertiary review of 27 systematic literature reviews (SLRs) focusing on blockchain in healthcare data sharing. This review analyzes existing literature, identifying critical criteria for assessing the suitability of blockchain solutions in healthcare data sharing.</p>
<p id="p-6">By extracting insights from prior research, we devise a comprehensive decision-making framework to assist the understanding of the trade-offs associated with using blockchain in a healthcare context. The developed framework considers the following essential factors:</p>
<p id="p-7">
<list list-type="bullet">
<list-item>
<p>The necessity of data sharing.</p>
</list-item>
<list-item>
<p>Trusted third-party replacement.</p>
</list-item>
<list-item>
<p>Data integrity and immutability.</p>
</list-item>
<list-item>
<p>Transparency in information processing.</p>
</list-item>
<list-item>
<p>Relevant actors.</p>
</list-item>
<list-item>
<p>Patient involvement.</p>
</list-item>
<list-item>
<p>Cost.</p>
</list-item>
<list-item>
<p>Public verifiability.</p>
</list-item>
</list>
</p>
<p id="p-8">This study provides three critical contributions to the understanding and application of blockchain technology in healthcare data sharing: First, it offers insights into the criteria that can influence the use of blockchain in a healthcare context; second, it translates these criteria into apparent, relevant factors for the healthcare sector; lastly, it introduces a flowchart that guides healthcare stakeholders in systematically evaluating the adoption of blockchain technology. By following the flowchart and responding to a series of questions, stakeholders can navigate the decision-making process more structured and better understand blockchain’s applicability to their specific use case.</p>
<p id="p-9">Blockchain technology is a decentralized digital ledger that records transactions across multiple computer nodes in such a way that the verified transactions cannot be altered. Transactions can be seen as the exchange of valuable information between two actors (from a sender to a receiver).</p>
<p id="p-10">While conceptually rooted in its application in cryptocurrencies [<xref ref-type="bibr" rid="B9">9</xref>], blockchain technology exhibits various characteristics that make it a versatile and potential solution for various applications across domains [<xref ref-type="bibr" rid="B10">10</xref>, <xref ref-type="bibr" rid="B11">11</xref>]. These characteristics define its operational mechanics and contribute to its growing popularity and adoption in fields like healthcare, finance, and supply chain management [<xref ref-type="bibr" rid="B10">10</xref>]. The following are the key characteristics that underscore the potential and versatility of blockchain technology:</p>
<p id="p-11">
<list list-type="bullet">
<list-item>
<p>Decentralization. Blockchain operates on a decentralized network architecture, which reduces the dependency on central authorities, enhancing system resilience and integrity [<xref ref-type="bibr" rid="B12">12</xref>].</p>
</list-item>
<list-item>
<p>Immutability. Once data is recorded in a blockchain, it is difficult to alter. This immutability ensures the integrity of the transaction ledger, making blockchain a robust platform for secure transactions [<xref ref-type="bibr" rid="B13">13</xref>].</p>
</list-item>
<list-item>
<p>Transparency and Anonymity. While transactions are transparent and traceable in the blockchain network, the participants’ identities are protected through complex cryptographic techniques, which balances transparency and anonymity [<xref ref-type="bibr" rid="B14">14</xref>].</p>
</list-item>
<list-item>
<p>Enforceable agreements. In blockchain technology, transactions are checked for validity via Smart contracts. Smart contracts are self-executing contracts with terms of agreements directly written into code. They run on the blockchain, allowing transactions to be executed automatically when certain conditions are met without intermediaries. This feature facilitates trustless agreements, reduces the potential for disputes, and enhances the efficiency of transactions [<xref ref-type="bibr" rid="B15">15</xref>].</p>
</list-item>
</list>
</p>
<p id="p-12">The key characteristics of blockchain technology lay the foundation for its diverse applications. However, implementing these characteristics can vary significantly depending on different use cases’ specific requirements and constraints. This variability has led to several types of blockchain networks, each tailored to meet unique access, control, speed, and privacy needs. The types of blockchain networks can be categorized into public permissionless, public permissioned, and private blockchains:</p>
<p id="p-13">
<list list-type="bullet">
<list-item>
<p>Public permissionless blockchains: Public permissionless blockchains, or public blockchains, are fully decentralized, with no single entity owning the network. They are open to anyone joining and participating in the core activities of the blockchain network, such as validating and recording transactions. Well-known examples include Bitcoin and Ethereum. These networks are characterized by their high transparency and security but often face challenges in terms of scalability and throughput [<xref ref-type="bibr" rid="B16">16</xref>].</p>
</list-item>
<list-item>
<p>Private blockchains: Private blockchains are permissioned networks with access restricted to specific members. Due to their greater control over participants’ activities, organizations often use them for internal purposes. This type of blockchain is suited for scenarios requiring privacy and faster transaction speeds but lacks extensive decentralization [<xref ref-type="bibr" rid="B17">17</xref>].</p>
</list-item>
<list-item>
<p>Public permissioned blockchains: A public permissioned blockchain, or consortium blockchain, is a semi-decentralized type where organizations govern the network. This model combines elements of both private and public blockchains. It is often used in business collaborations where multiple stakeholders require control and shared access. Consortium blockchains are ideal for industries like banking, supply chain, and healthcare, where data privacy and shared governance are essential [<xref ref-type="bibr" rid="B18">18</xref>].</p>
</list-item>
</list>
</p>
<p id="p-14">Blockchain technology has gained attention in various sectors, including healthcare [<xref ref-type="bibr" rid="B19">19</xref>]. The features of blockchain, such as decentralization, transparency, and immutability, present novel solutions to challenges in this domain [<xref ref-type="bibr" rid="B3">3</xref>, <xref ref-type="bibr" rid="B20">20</xref>].</p>
<p id="p-15">The application of blockchain technology in healthcare can be categorized into a comprehensive, multidimensional taxonomy, reflecting the technology’s versatility in addressing various sector-specific challenges:</p>
<p id="p-16">
<list list-type="bullet">
<list-item>
<p>Healthcare data management: Blockchain technology provides innovative solutions for managing, storing, and sharing healthcare data, including electronic health records (EHRs) and electronic medical records (EMRs) [<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B22">22</xref>]. It distributes data across a network with the decentralization feature, enhancing patient control and privacy. Immutability and transparency ensure that once data is recorded, it cannot be altered, maintaining the integrity of patient information, and facilitating interoperability between healthcare systems [<xref ref-type="bibr" rid="B23">23</xref>–<xref ref-type="bibr" rid="B26">26</xref>]. For example, by leveraging the immutable and transparent nature of blockchain, Azaria et al. [<xref ref-type="bibr" rid="B27">27</xref>] proposed a blockchain-based system designed to revolutionize the management and accessibility of EMRs, ensuring secure, patient-centered management of EMRs with seamless sharing across providers.</p>
</list-item>
<list-item>
<p>Pharmaceutical supply chain and healthcare logistics: In this domain, blockchain enhances the transparency of drug manufacturing and delivery processes, allowing for real-time tracking and verification of pharmaceutical products, organ transplants, and blood donations [<xref ref-type="bibr" rid="B21">21</xref>]. Immutability provides a tamper-proof record of each step in the supply chain, ensuring product authenticity and safety [<xref ref-type="bibr" rid="B24">24</xref>, <xref ref-type="bibr" rid="B25">25</xref>]. As an example, Huang et al. [<xref ref-type="bibr" rid="B28">28</xref>] introduce Drugledger, a blockchain-based system designed to enhance the traceability and regulation of drugs across the supply chain. The system addresses the limitations of traditional centralized approaches by offering a decentralized solution that ensures data authenticity, resilience, and flexibility.</p>
</list-item>
<list-item>
<p>Interoperability and consolidated healthcare systems: Blockchain technology promotes decentralization to remove intermediaries in data exchange, creating a unified view of patient data across healthcare providers [<xref ref-type="bibr" rid="B21">21</xref>]. Transparency ensures this data is accessible and consistent across platforms, improving care coordination and outcomes. For example, Yue et al. [<xref ref-type="bibr" rid="B29">29</xref>] propose a novel architecture, Healthcare Data Gateway (HDG), that leverages blockchain technology to empower patients to own, control, and share their healthcare data without compromising privacy. By leveraging a unified data schema and purpose-centric access control, this architecture facilitates the organization and sharing of healthcare data across different systems and stakeholders.</p>
</list-item>
<list-item>
<p>Clinical trials and medical research: In clinical trials, immutability safeguards the integrity of data collection, patient recruitment, and results dissemination, preventing unauthorized changes and ensuring reliability [<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B23">23</xref>, <xref ref-type="bibr" rid="B25">25</xref>]. Transparency fosters trust in the research process by making methodologies and findings accessible for verification, which is significant for biomedical research and education. As an example, Zhang et al. [<xref ref-type="bibr" rid="B30">30</xref>] present FHIRChain, a blockchain-based architecture tailored for the secure and scalable sharing of clinical data in healthcare. Addressing the “Shared Nationwide Interoperability Roadmap” requirements from the Office of the National Coordinator for Health Information Technology, FHIRChain integrates Health Level Seven International’s Fast Healthcare Interoperability Resources (FHIR) standard within a blockchain framework to ensure interoperable, privacy-preserving, and secure data exchange.</p>
</list-item>
<list-item>
<p>Remote care and Internet of Things (IoT) architectures: By integrating with IoT devices, blockchain enhances security through cryptographic protocols and smart contracts against unauthorized data access [<xref ref-type="bibr" rid="B23">23</xref>, <xref ref-type="bibr" rid="B24">24</xref>]. Decentralization enables the efficient aggregation of patient data from multiple sources, placing patients at the center of their care, even in remote settings. For example, Azbeg et al. [<xref ref-type="bibr" rid="B31">31</xref>] present a healthcare system, BlockMedCare, designed to address security and privacy challenges in remote patient monitoring. The proposed system integrates IoT with blockchain technology to create a secure, scalable, and efficient system for managing chronic diseases that require continuous monitoring. The system leverages proxy re-encryption and smart contracts for access control. It employs the InterPlanetary File System (IPFS) for off-chain data storage to ensure scalability and reduce the processing time associated with data management.</p>
</list-item>
<list-item>
<p>Health insurance and claims processing: Blockchain streamlines the claims process with smart contracts that execute automatically upon meeting predefined conditions, reducing opportunities for fraud and improving efficiency [<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B25">25</xref>]. Transparency provides clear, auditable trails of transactions, fostering trust among patients, providers, and insurers. Karmakar et al. [<xref ref-type="bibr" rid="B32">32</xref>] introduce a blockchain-based framework, ChainSure, for automating and enhancing the security of health insurance systems. By leveraging smart contracts and the Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS) method, this framework automates the insurance process, minimizes administrative overhead, and provides a transparent and secure platform for transactions between insurers, healthcare providers, and patients.</p>
</list-item>
<list-item>
<p>Governance: Across the applications, the immutability and transparency of blockchain ensure a secure, unchangeable record of transactions, supporting compliance and governance through reliable audit trails and access controls [<xref ref-type="bibr" rid="B26">26</xref>, <xref ref-type="bibr" rid="B33">33</xref>]. For example, Urovi et al. [<xref ref-type="bibr" rid="B34">34</xref>] introduced a blockchain-based platform, License accoUntability and CompliancE (LUCE), to support data sharing for research. Using dynamic consent mechanisms [<xref ref-type="bibr" rid="B35">35</xref>], the authors automate the management of consent and purpose of use for health-related datasets. In general, by utilizing smart contracts, LUCE provides a secure and transparent method to monitor and enforce compliance with data sharing agreements, thereby overcoming issues related to trust and legal clarity in data reuse.</p>
</list-item>
</list>
</p>
<p id="p-17">The taxonomy of blockchain applications in healthcare data sharing is summed up in <xref ref-type="table" rid="t1">Table 1</xref>.</p>
<table-wrap id="t1">
<label>Table 1</label>
<caption>
<p id="t1-p-1">The taxonomy of blockchain applications in healthcare</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th>Category</th>
<th>Description</th>
<th>Blockchain properties supporting the applications</th>
</tr>
</thead>
<tbody>
<tr>
<td>Healthcare data management</td>
<td>Management, storage, and sharing of electronic health records (EHRs) and electronic medical records (EMRs). Enhancing patient data control and interoperability</td>
<td>Transparency<break />Immutability<break />Decentralization</td>
</tr>
<tr>
<td>Pharmaceutical supply chain and healthcare logistics</td>
<td>Ensuring authenticity, traceability, and safety of pharmaceutical products, organ transplants, and blood donations</td>
<td>Transparency<break />Immutability</td>
</tr>
<tr>
<td>Interoperability and consolidated healthcare systems</td>
<td>Creating a unified view of patient data across healthcare providers to improve care coordination and outcomes</td>
<td>Transparency<break />Decentralization</td>
</tr>
<tr>
<td>Clinical trials and medical research</td>
<td>Securing data collection, patient recruitment, and results sharing for clinical trials. Supporting reliability and verifiability of medical research</td>
<td>Immutability<break />Transparency</td>
</tr>
<tr>
<td>Remote care and Internet of Things (IoT) architectures</td>
<td>Real-time patient monitoring, secure data collection, and remote healthcare delivery through integration with IoT devices</td>
<td>Enforceable agreements<break />Decentralization</td>
</tr>
<tr>
<td>Health insurance and claims processing</td>
<td>Automating and securing health insurance claims processing via smart contracts. Reducing fraud and streamlining the claims lifecycle</td>
<td>Enforceable agreements<break />Transparency</td>
</tr>
<tr>
<td>Governance</td>
<td>Ensuring health data security and privacy across applications through cryptographic methods. Providing audit trails, access control, and data aggregation for governance</td>
<td>Immutability<break />Transparency<break />Enforceable agreements<break />Decentralization</td>
</tr>
</tbody>
</table>
</table-wrap>
<p id="p-18">Pilot projects and theoretical models have attempted to use blockchain in healthcare [<xref ref-type="bibr" rid="B8">8</xref>], but have faced challenges in scalability, integration with existing systems, and regulatory compliance [<xref ref-type="bibr" rid="B36">36</xref>]. These mixed outcomes reflect the early nature of blockchain application in healthcare and illustrate the need for a more nuanced understanding of the practicality of these technologies.</p>
<p id="p-19">Blockchain technology has emerged as a pivotal innovation in healthcare, offering secure, immutable, transparent, and decentralized solutions for dealing with a wide array of data types [<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B36">36</xref>]:</p>
<p id="p-20">
<list list-type="bullet">
<list-item>
<p>Clinical and laboratory data: Blockchain systems provide a platform that supports the sharing of patient data, including clinical data, laboratory results, and medical imaging [<xref ref-type="bibr" rid="B36">36</xref>]. By integrating blockchain technology, healthcare providers can ensure the integrity and confidentiality of patient data, facilitating seamless access and interoperability across different healthcare systems [<xref ref-type="bibr" rid="B36">36</xref>].</p>
</list-item>
<list-item>
<p>Medical claims and cost data: The management of insurance claims and associated cost data benefits from blockchain technology [<xref ref-type="bibr" rid="B25">25</xref>]. Through smart contracts, blockchain systems can automate the claims processing workflow, reducing fraud, eliminating intermediaries, and ensuring transparency in the billing and payment process [<xref ref-type="bibr" rid="B21">21</xref>].</p>
</list-item>
<list-item>
<p>Patient-generated data: With the increasing use of IoT devices in healthcare [<xref ref-type="bibr" rid="B25">25</xref>], blockchain serves as a backbone for securely managing the vast amounts of data generated by these devices, ensuring the integrity and security of data collected from wearable devices, home monitoring systems, and other IoT applications [<xref ref-type="bibr" rid="B37">37</xref>]. Additionally, blockchain technology empowers patients by giving them control over their healthcare data, facilitating real-time monitoring and personalized care interventions.</p>
</list-item>
<list-item>
<p>Pharmaceutical and organ data: Blockchain’s application extends to managing pharmaceutical data and organ donation records [<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B33">33</xref>]. It ensures the authenticity of pharmaceutical products, tracks their distribution, and manages organ donor registries and transplant records. By providing a tamper-proof ledger for these sensitive data types, blockchain technology can combat counterfeit drugs and streamline organ donation processes.</p>
</list-item>
</list>
</p>
<p id="p-21">Although data security encompasses a range of challenges, blockchain-based applications mainly focus on addressing three areas: ensuring data integrity, managing access control, and preserving privacy [<xref ref-type="bibr" rid="B38">38</xref>]:</p>
<p id="p-22">
<list list-type="bullet">
<list-item>
<p>Ensuring data integrity: Data integrity is paramount in healthcare to maintain the accuracy and completeness of healthcare data overtime [<xref ref-type="bibr" rid="B39">39</xref>]. Blockchain technology enhances data integrity in healthcare by creating a decentralized and tamper-evident record system. Every transaction on the blockchain is timestamped and linked to the previous transaction, forming a chronological chain. This feature makes unauthorized alterations evident and allows for easy verification of data history [<xref ref-type="bibr" rid="B40">40</xref>].</p>
</list-item>
<list-item>
<p>Managing access control: Access control in healthcare is critical for protecting patient privacy and ensuring that sensitive healthcare data is only accessible to authorized individuals [<xref ref-type="bibr" rid="B41">41</xref>]. In blockchain-based healthcare applications, users can innovatively manage access control through smart contracts [<xref ref-type="bibr" rid="B35">35</xref>]. These are self-executing contracts with the terms of the agreement directly written into code, enforcing who can access what data under which circumstances automatically.</p>
</list-item>
<list-item>
<p>Preserving privacy: Privacy preservation is essential in healthcare due to the sensitive nature of the data involved [<xref ref-type="bibr" rid="B42">42</xref>]. The transparency of blockchain introduces complexities in ensuring privacy; however, cryptographic techniques such as zero-knowledge proofs enable the verification of data without exposing the underlying details [<xref ref-type="bibr" rid="B43">43</xref>]. Integrating blockchain with advanced cryptographic technologies like proxy re-encryption further enhances privacy [<xref ref-type="bibr" rid="B44">44</xref>, <xref ref-type="bibr" rid="B45">45</xref>]. This technique allows encrypted data to be re-encrypted for a new recipient without decrypting it first. Additionally, decentralized privacy-preserving identity mechanisms can be employed to protect individual identities [<xref ref-type="bibr" rid="B46">46</xref>]. These mechanisms operate through blockchain, ensuring that while data remains traceable, the identities behind the data are safeguarded without central authority oversight, providing a robust framework for privacy.</p>
</list-item>
</list>
</p>
<p id="p-23">Managing healthcare data is a complex process with various application domains, data types, and security objectives [<xref ref-type="bibr" rid="B7">7</xref>]. Issues like data breaches, unauthorized access, and the inefficiency of traditional centralized systems highlight the vulnerability of current healthcare data management practices [<xref ref-type="bibr" rid="B5">5</xref>]. The sensitive nature of health data requires a system that ensures privacy and security while maintaining accessibility and accuracy [<xref ref-type="bibr" rid="B7">7</xref>].</p>
<p id="p-24">Despite the growing body of literature on blockchain in healthcare, there remains a disconnect between theoretical research and real-world application [<xref ref-type="bibr" rid="B8">8</xref>]. This gap is partly from the early nature of blockchain technology and the complexity of healthcare systems. Current research often focuses on potential use cases without adequately addressing the practical challenges of implementing blockchain solutions in diverse healthcare environments [<xref ref-type="bibr" rid="B47">47</xref>].</p>
<p id="p-25">Given the complexities and the early stage of blockchain research and applications in healthcare, there is a critical need for a structured decision-making framework [<xref ref-type="bibr" rid="B48">48</xref>]. Such a framework would assist healthcare stakeholders in evaluating the feasibility and appropriateness of blockchain technology in specific healthcare contexts [<xref ref-type="bibr" rid="B49">49</xref>].</p>
</sec>
<sec id="s2">
<title>Materials and methods</title>
<p id="p-26">This section outlines the materials and methods employed to develop and validate the decision-making framework. We conducted a tertiary review [<xref ref-type="bibr" rid="B50">50</xref>] of SLRs that focus on blockchain and healthcare data sharing. Following this review, we perform data extraction and analysis to refine the flowchart initially proposed by Wüst and Gervais [<xref ref-type="bibr" rid="B8">8</xref>]. Our primary goal is to analyze and synthesize the findings of multiple SLRs to establish a comprehensive understanding of the current state of knowledge in this field. Through this tertiary review, we aim to identify key themes and challenges present in the existing literature concerning the application of blockchain in healthcare data sharing. <xref ref-type="fig" rid="fig1">Figure 1</xref> shows the overall methodology steps used for selecting papers and extracting data.</p>
<fig id="fig1" position="float">
<label>Figure 1</label>
<caption>
<p id="fig1-p-1">Overview of the methodology</p>
</caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="edht-02-101114-g001.tif" />
</fig>
<sec id="t2-1">
<title>Search strategy</title>
<p id="p-27">To identify relevant SLRs focusing on the application of blockchain technology in healthcare, we developed a comprehensive search strategy, which involved a systematic and structured search across various databases and sources to ensure a thorough coverage of the topic.</p>
</sec>
<sec id="t2-2">
<title>Data sources</title>
<p id="p-28">We conducted searches in several electronic databases recognized for their comprehensive coverage of literature in the fields of technology and healthcare. These included:</p>
<p id="p-29">
<list list-type="bullet">
<list-item>
<p>PubMed</p>
</list-item>
<list-item>
<p>IEEE Xplore</p>
</list-item>
<list-item>
<p>ACM Digital Library</p>
</list-item>
<list-item>
<p>Science Direct</p>
</list-item>
<list-item>
<p>Springer Link</p>
</list-item>
</list>
</p>
<p id="p-30">Additionally, to ensure exhaustive coverage and capture literature that might not be indexed in the aforementioned databases, we conducted supplementary searches in:</p>
<p id="p-31">
<list list-type="bullet">
<list-item>
<p>Google Scholar</p>
</list-item>
</list>
</p>
</sec>
<sec id="t2-3">
<title>Search terms and strategy</title>
<p id="p-32">The development of the search strategy involved an integration of specific keywords and Boolean logic. The core search terms employed were “blockchain”, “healthcare”, and “systematic literature review”. These terms were interconnected using Boolean operators. For instance, the search query “blockchain” AND “healthcare” AND “systematic literature review” was utilized. To ensure compatibility with the unique indexing systems and search functionalities of each database, the search queries were customized accordingly. The temporal scope of the search was confined to the period from 2008, marking the publication of Bitcoin’s white paper, to December 2023, the knowledge cutoff date of this study. The retrieved articles were then listed according to their relevance to the search purposes.</p>
</sec>
<sec id="t2-4">
<title>Study selection</title>
<p id="p-33">As shown in <xref ref-type="table" rid="t2">Table 2</xref>, the initial results were screened based on titles and abstracts to identify studies that potentially met our inclusion criteria. The inclusion criteria were:</p>
<p id="p-34">
<list list-type="bullet">
<list-item>
<p>Articles focusing on the application of blockchain in healthcare.</p>
</list-item>
<list-item>
<p>Studies that were SLRs.</p>
</list-item>
<list-item>
<p>Publications in English.</p>
</list-item>
</list>
</p>
<table-wrap id="t2">
<label>Table 2</label>
<caption>
<p id="t2-p-1">The results were screened by titles and abstracts</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th>
<bold>Data sources</bold>
</th>
<th>
<bold>Search results</bold>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>PubMed</td>
<td>10</td>
</tr>
<tr>
<td>IEEE Xplore</td>
<td>6</td>
</tr>
<tr>
<td>ACM Digital Library</td>
<td>1</td>
</tr>
<tr>
<td>Science Direct</td>
<td>3</td>
</tr>
<tr>
<td>SpringerLink</td>
<td>2</td>
</tr>
<tr>
<td>Google Scholar</td>
<td>15</td>
</tr>
<tr>
<td>Total</td>
<td>37</td>
</tr>
</tbody>
</table>
</table-wrap>
<p id="p-35">Exclusion criteria included:</p>
<p id="p-36">
<list list-type="bullet">
<list-item>
<p>Non-peer-reviewed articles.</p>
</list-item>
<list-item>
<p>Articles not relevant to the core focus of blockchain in healthcare.</p>
</list-item>
<list-item>
<p>Studies lacking a systematic approach in methodology.</p>
</list-item>
</list>
</p>
<p id="p-37">Then, the duplicates were removed using digital object identifiers (DOIs).</p>
</sec>
<sec id="t2-5">
<title>Data extraction and management</title>
<p id="p-38">To answer the research question proposed, selected articles underwent a full-text review for detailed analysis. Relevant information was extracted and compiled into a predefined data extraction template, which included:</p>
<p id="p-39">
<list list-type="bullet">
<list-item>
<p>Study objectives and research questions.</p>
</list-item>
<list-item>
<p>Key findings and conclusions.</p>
</list-item>
</list>
</p>
</sec>
</sec>
<sec id="s3">
<title>Results</title>
<p id="p-40">In this section, we present the results of our tertiary review, outlining the specific criteria used to assess the suitability of blockchain technology for sharing healthcare data. Building upon the flowchart by Wüst and Gervais [<xref ref-type="bibr" rid="B8">8</xref>], we have developed a refined version that enhances precision, focus, and comprehensibility, specifically tailored for healthcare practitioners.</p>
<sec id="t3-1">
<title>Criteria for blockchain application in healthcare data sharing</title>
<p id="p-41">In examining the applicability of blockchain technology for healthcare data sharing, our analysis identified eight critical criteria: scalability, privacy, integrity/immutability, interoperability/accessibility, transparency, patient involvement, legal compliance, and cost/incentive, as shown in <xref ref-type="table" rid="t3">Table 3</xref>. These criteria, combined with the flowchart by Wüst and Gervais [<xref ref-type="bibr" rid="B8">8</xref>], collectively form a comprehensive framework, guiding the evaluation of blockchain’s application in healthcare data sharing.</p>
<table-wrap id="t3">
<label>Table 3</label>
<caption>
<p id="t3-p-1">Criteria and decision points for blockchain application in healthcare data sharing</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th>
<bold>Criteria</bold>
</th>
<th>
<bold>Decision point</bold>
</th>
<th>
<bold>Reference</bold>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Scalability</td>
<td>Can you share via trusted third parties?</td>
<td>[<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B25">25</xref>, <xref ref-type="bibr" rid="B51">51</xref>–<xref ref-type="bibr" rid="B55">55</xref>]</td>
</tr>
<tr>
<td>Privacy</td>
<td>Are all actors trusted?</td>
<td>[<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B25">25</xref>, <xref ref-type="bibr" rid="B26">26</xref>, <xref ref-type="bibr" rid="B51">51</xref>, <xref ref-type="bibr" rid="B54">54</xref>, <xref ref-type="bibr" rid="B56">56</xref>, <xref ref-type="bibr" rid="B57">57</xref>]</td>
</tr>
<tr>
<td>Integrity/immutability</td>
<td>Is data integrity and immutability crucial?</td>
<td>[<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B22">22</xref>, <xref ref-type="bibr" rid="B38">38</xref>, <xref ref-type="bibr" rid="B39">39</xref>, <xref ref-type="bibr" rid="B54">54</xref>, <xref ref-type="bibr" rid="B56">56</xref>–<xref ref-type="bibr" rid="B65">65</xref>]</td>
</tr>
<tr>
<td>Interoperability/accessibility</td>
<td>Are the identities of actors known?</td>
<td>[<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B25">25</xref>, <xref ref-type="bibr" rid="B51">51</xref>, <xref ref-type="bibr" rid="B52">52</xref>, <xref ref-type="bibr" rid="B54">54</xref>, <xref ref-type="bibr" rid="B55">55</xref>, <xref ref-type="bibr" rid="B58">58</xref>, <xref ref-type="bibr" rid="B61">61</xref>, <xref ref-type="bibr" rid="B66">66</xref>, <xref ref-type="bibr" rid="B67">67</xref>]</td>
</tr>
<tr>
<td>Transparency</td>
<td>Is transparency towards actors important?</td>
<td>[<xref ref-type="bibr" rid="B57">57</xref>, <xref ref-type="bibr" rid="B61">61</xref>–<xref ref-type="bibr" rid="B65">65</xref>]</td>
</tr>
<tr>
<td>Patient involvement</td>
<td>Do you need to involve patients?</td>
<td>[<xref ref-type="bibr" rid="B25">25</xref>, <xref ref-type="bibr" rid="B58">58</xref>]</td>
</tr>
<tr>
<td>Legal compliance</td>
<td>Is public verifiability required?</td>
<td>[<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B54">54</xref>, <xref ref-type="bibr" rid="B67">67</xref>]</td>
</tr>
<tr>
<td>Cost/incentive</td>
<td>Is cost a limiting factor?</td>
<td>[<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B26">26</xref>, <xref ref-type="bibr" rid="B55">55</xref>, <xref ref-type="bibr" rid="B67">67</xref>]</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="t3-2">
<title>Do you need a blockchain in healthcare data sharing? A flowchart</title>
<p id="p-42">Determining the suitability of blockchain technology for healthcare applications requires a systematic evaluation of various factors. To address this, we have developed a comprehensive decision-making flowchart, as shown in <xref ref-type="fig" rid="fig2">Figure 2</xref>.</p>
<fig id="fig2" position="float">
<label>Figure 2</label>
<caption>
<p id="fig2-p-1">The decision-making flowchart</p>
</caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="edht-02-101114-g002.tif" />
</fig>
<p id="p-43">The flowchart serves as a valuable tool for healthcare practitioners, facilitating informed decision-making regarding the implementation of blockchain solutions. It encompasses factors such as the requirements of data sharing, data integrity, and immutability, the identity verification and trustworthiness of healthcare actors, patient involvement, and public verifiability. Each step of the flowchart is accompanied by three elements, a rationale, term definitions, and a decision pathway. The rationale explicates the purpose of each step, ensuring that stakeholders understand the importance of the considerations involved. Term definitions are provided to clarify technical and healthcare-specific terminology, catering, especially to practitioners less familiar with blockchain technology. Finally, the decision pathway guides users to subsequent steps based on their specific circumstances and requirements.</p>
</sec>
<sec id="t3-3">
<title>Step 1: Do you need to share data?</title>
<p id="p-44">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>This initial question focuses on the necessity of data sharing. It serves as the primary filter for assessing the applicability of blockchain in the health domain.</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Data” refers to information that is relevant to the health domain, often related to the physical, mental, and social well-being of individuals or populations. This encompasses a wide range of data types including, but not limited to, medical histories, diagnostic results, treatment information, and lifestyle specifics [<xref ref-type="bibr" rid="B21">21</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>If a healthcare organization does not have a requirement to share data, the integration of blockchain may not offer substantial benefits. Thus, this question lays the foundation for the subsequent inquiries and decision-making processes.</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-4">
<title>Step 2: Can you share via trusted third parties?</title>
<p id="p-45">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>This step examines the necessity of trusted third parties in traditional and centralized healthcare data sharing systems [<xref ref-type="bibr" rid="B68">68</xref>], such as hospitals, insurance companies, and government agencies. It directly confronts the scalability challenge of transitioning traditional, centralized healthcare data sharing to a decentralized blockchain approach [<xref ref-type="bibr" rid="B21">21</xref>, <xref ref-type="bibr" rid="B51">51</xref>, <xref ref-type="bibr" rid="B52">52</xref>]. This step also prompts an evaluation of whether the existing infrastructure, predominantly based on trusted third parties, meets the demands of healthcare data sharing. It invites stakeholders to assess the scalability challenge of current blockchain technology. The decision to integrate blockchain in healthcare should consider scale and balance the benefits of decentralization against the established trust in centralized systems.</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Trusted third party” refers to centralized entities responsible for storing, processing, and sharing health information [<xref ref-type="bibr" rid="B25">25</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>In the healthcare sector, trusted third parties offer established systems for data sharing, yet this comes with potential drawbacks, including increased vulnerability to data breaches, alongside a shift in control and trust towards these entities. On the other hand, blockchain technology provides a decentralized framework, ensuring data owners maintain ownership over their data, dictating access and sharing terms. This approach may mitigate trust and data security concerns; however, as a novel technology, it is challenged by efficiency and difficulties in integrating with existing healthcare systems. Therefore, if sharing via trusted third parties is possible, sharing with the support of blockchain technology may be unnecessary. This is particularly true if high transaction speed is required. However, if there is a need to scale data sharing to multiple actors and a trusted third-party model is not possible or not available, then a blockchain model could contribute.</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-5">
<title>Step 3: Is data integrity and immutability crucial?</title>
<p id="p-46">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>In this step, data integrity and immutability ascend to paramount importance [<xref ref-type="bibr" rid="B57">57</xref>, <xref ref-type="bibr" rid="B63">63</xref>, <xref ref-type="bibr" rid="B65">65</xref>]. This step prompts stakeholders to consider whether the existing data sharing mechanisms afford sufficient control over the data’s integrity once it is out of their direct custody. It challenges them to evaluate if traditional systems offer adequate safeguards against unauthorized alterations, deletions, or breaches.</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definitions</p>
<p>“Data integrity” entails the accuracy and consistency of data over its lifecycle [<xref ref-type="bibr" rid="B38">38</xref>]. “Data Immutability”, on the other hand, refers to the data’s unchangeability once recorded, preventing unauthorized alterations that could compromise its reliability [<xref ref-type="bibr" rid="B62">62</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<list list-type="bullet">
<list-item>
<p>If data integrity and immutability are not deemed crucial for a specific healthcare data sharing scenario, the necessity for employing blockchain technology is reduced. In these cases, the complexities and costs associated with implementing a blockchain solution may not be justified because the data in question does not significantly impact patient care outcomes, regulatory compliance, or where traditional database systems provide sufficient security and audit capabilities.</p>
</list-item>
<list-item>
<p>When data integrity and immutability are crucial in this context, blockchain technology emerges as a pivotal solution. Blockchain’s inherent features, such as decentralized storage, cryptographic hashing, and consensus algorithms, provide a potential solution when maintaining control over data integrity and immutability is a primary concern in data sharing scenarios.</p>
</list-item>
</list>
</list-item>
</list>
</p>
</sec>
<sec id="t3-6">
<title>Step 4: Is transparency towards actors important?</title>
<p id="p-47">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>Transparency is not just a preference but a necessity in modern healthcare data management [<xref ref-type="bibr" rid="B69">69</xref>, <xref ref-type="bibr" rid="B70">70</xref>]. It fosters trust among stakeholders [<xref ref-type="bibr" rid="B63">63</xref>] and aids in compliance with regulatory standards [<xref ref-type="bibr" rid="B48">48</xref>]. Given the sensitive nature of healthcare data, stakeholders must be assured that the data is handled appropriately and that activities are traceable and accountable [<xref ref-type="bibr" rid="B55">55</xref>].</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Actors” refers to all individuals and entities interacting with the shared data, including patients, healthcare providers, insurance companies, administrators, and possibly others like researchers or pharmaceutical companies [<xref ref-type="bibr" rid="B55">55</xref>, <xref ref-type="bibr" rid="B59">59</xref>].</p>
<p>“Transparency” within a healthcare system refers to the extent of access and visibility offered to various stakeholders. Generally, it includes a transparent and auditable record of one or many of the following: data access, processing, and sharing. In the context of blockchain-based systems, the level of transparency varies depending on the type of blockchain [<xref ref-type="bibr" rid="B63">63</xref>]. This transparency ensures that all actions are conducted with integrity and align with established protocols and regulations [<xref ref-type="bibr" rid="B55">55</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>When evaluating blockchain integration for healthcare data sharing, it is essential to assess the necessity of transparency across all healthcare actors, thereby guiding the selection of the blockchain type.</p>
<p>
<list list-type="bullet">
<list-item>
<p>For environments where transparency needs are balanced with privacy concerns, a private permissioned blockchain could be more appropriate. Such a blockchain allows for selective visibility of transactions, ensuring only authorized parties can access specific data. It supports regulatory compliance and protects sensitive information while offering transparency to those granted access.</p>
</list-item>
<list-item>
<p>Conversely, in a scenario where transparency is required to build trust and ensure accountability among all actors, exploring a public permissioned or permissionless blockchain might be advisable. It provides an open environment where data transactions are visible to anyone, enhancing transparency but requiring careful consideration of privacy and data sensitivity.</p>
</list-item>
</list>
</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-7">
<title>Step 5: Are the identities of actors known?</title>
<p id="p-48">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>In healthcare scenarios where the identities of the actors are known, the data sharing is typically limited to a few organizations identifying a solution to share information. In other health scenarios, the identities of the actors are not well known due to a need for information sharing across multiple organizations. In this later case, the information is generated or collected in different technical systems thereby, interoperability becomes an important concept linked to this question. Therefore, identifying actors within a data-sharing network aligns with ensuring interoperability, which is significant in healthcare [<xref ref-type="bibr" rid="B71">71</xref>, <xref ref-type="bibr" rid="B72">72</xref>]. Interoperability, in this context, refers to the ability of different entities to communicate, exchange data, and use the information that has been exchanged efficiently and effectively based on the identification of healthcare actors [<xref ref-type="bibr" rid="B73">73</xref>]. This step underscores the importance of interoperable systems in ensuring that the identities of all participants in the healthcare data sharing process are accurately known and verifiable. The level of identity disclosure directly impacts the appropriate blockchain type [<xref ref-type="bibr" rid="B74">74</xref>].</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Known identities” implies that the real-world identities of these actors are verified and authenticated within the system [<xref ref-type="bibr" rid="B74">74</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>Identifying all participants is crucial for determining the type of blockchain when integrating it into healthcare data sharing.</p>
<p>
<list list-type="bullet">
<list-item>
<p>If the identities of all actors do not need to be publicly known or verified, a public permissionless blockchain may be considered. It allows for anonymous or pseudonymous participation, facilitating a broader engagement. However, interoperability may be challenging where identity verification is necessary.</p>
</list-item>
<list-item>
<p>On the other hand, if verifying the identities of all healthcare actors is essential, a public permissioned blockchain would be more suitable. This approach supports interoperability by enabling secure, authenticated interactions across different actors. It also ensures that each actor’s identity is known and verified, enhancing trust and compliance with healthcare regulations.</p>
</list-item>
</list>
</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-8">
<title>Step 6: Are all actors trusted?</title>
<p id="p-49">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>Trust among actors in a healthcare data-sharing context is important to ensure that the data is not misused and that all parties adhere to the agreed-upon protocols and ethical standards. In a blockchain network, trust can be related to confidence in the actors’ behavior and the security of the transactions [<xref ref-type="bibr" rid="B24">24</xref>, <xref ref-type="bibr" rid="B75">75</xref>]. The level of trust among the actors will influence the governance model and the degree of decentralization appropriate for the blockchain system [<xref ref-type="bibr" rid="B6">6</xref>, <xref ref-type="bibr" rid="B76">76</xref>].</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definitions</p>
<p>“Trusted actors” refers to entities and individuals that have established a record of reliability and ethical handling of healthcare data. Trust can be derived from historical interactions, reputation, or regulatory compliance [<xref ref-type="bibr" rid="B71">71</xref>]. In blockchain terms, this might translate into the need for less stringent consensus mechanisms or the ability to operate with a higher degree of autonomy within the network [<xref ref-type="bibr" rid="B55">55</xref>, <xref ref-type="bibr" rid="B59">59</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>
<list list-type="bullet">
<list-item>
<p>If all actors are trusted, a private blockchain might be sufficient. It could be suitable for a group of healthcare providers or between trusted entities with existing relationships. It leverages the inherent trust to ensure data security and compliance while benefiting from advantages like immutability and transparency. It is sufficient for controlled, secure data exchange, where wide-scale decentralization is less critical, allowing for efficient and streamlined operations within the trusted network.</p>
</list-item>
<list-item>
<p>If there is a mix of trusted and untrusted actors, or if trust needs to be established through system architecture, a public permissioned blockchain may be necessary with further consideration. It allows for a more controlled environment than a public permissionless blockchain, which balances between openness and the need for specific restrictions. It requires actors to have permission to join, which can help main security and trustworthiness while still leveraging the benefits of blockchain technology to ensure data integrity.</p>
</list-item>
<list-item>
<p>In cases where no actor is fully trusted, a public permissionless blockchain might be employed, combining further filtering factors. Here, trust is not placed on any single actor but on the blockchain protocol and the distributed network of participants to maintain integrity. This approach ensures transparency and accountability, making it suitable for scenarios requiring high levels of trust and security without centralized control.</p>
</list-item>
</list>
</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-9">
<title>Step 7: Do you need to involve patients?</title>
<p id="p-50">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>In healthcare, patient-centric care models are increasingly important, and involving patients in their data management is a key aspect of this [<xref ref-type="bibr" rid="B77">77</xref>]. Patient involvement can empower individuals to take control of their health information, allowing them to grant or revoke access to their data [<xref ref-type="bibr" rid="B78">78</xref>, <xref ref-type="bibr" rid="B79">79</xref>]. Blockchain can offer a platform where patients can actively engage with their data securely and transparently [<xref ref-type="bibr" rid="B80">80</xref>].</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Patient involvement” refers to the participation of patients in managing and controlling access to their healthcare data. It includes viewing their medical records, sharing them with healthcare providers, and possibly contributing data from wearables or other personal health devices [<xref ref-type="bibr" rid="B78">78</xref>, <xref ref-type="bibr" rid="B81">81</xref>]. Patient involvement could be direct or indirect. Direct patient involvement refers to sharing information directly, empowering patients to manage and control access to their healthcare data actively. Indirect patient involvement refers to the data sharing being pseudonymous or anonymous, where direct identifiers are removed from healthcare data to protect patient privacy, and data owners retain a mapping between the identities of patients and their de-identified records.</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>
<list list-type="bullet">
<list-item>
<p>If patient involvement is required, a public permissionless or permissioned blockchain could be suitable, combined with further discussion. Such blockchains facilitate patient interaction with their healthcare data and allow patients to claim ownership of their healthcare data, placing them at the center of healthcare data sharing.</p>
</list-item>
<list-item>
<p>If patient involvement is not required, a private blockchain or a public permissioned blockchain may be adequate, where healthcare providers or administrators hold control over data access and management, facilitating efficient data sharing and management within the healthcare sector. It focuses on operational efficiency and compliance with regulatory standards without requiring direct patient involvement in the data sharing process.</p>
</list-item>
</list>
</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-10">
<title>Step 8: Is cost a limiting factor?</title>
<p id="p-51">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>Cost is a significant consideration for healthcare organizations when integrating blockchain technology, which can vary widely depending on the network type and the implementation scale [<xref ref-type="bibr" rid="B4">4</xref>]. The decision balances the financial resources available with the benefits a blockchain solution could provide.</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Cost” in the context of integrating blockchain technology in healthcare data sharing encompasses the financial expenditure required for the system’s initiation and maintenance, including upfront investment needed for hardware, software, and expert labor and the recurrent costs like energy consumption, system upgrades, and security measures. In the context of blockchain, transaction fees should also be considered. These are necessary considerations in deciding the type and scale of blockchain implementations suitable for healthcare organizations [<xref ref-type="bibr" rid="B3">3</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>
<list list-type="bullet">
<list-item>
<p>If cost is a limiting factor, a public permissioned blockchain might be more appropriate, leading to lower operational and infrastructure expenses due to restricted access and optimized network requirements.</p>
</list-item>
<list-item>
<p>In cases where the budget allows for a more robust and decentralized solution, and the benefits of such a solution outweigh the costs, a public permissionless blockchain could be considered. Public permissionless blockchains stand out for their open and decentralized nature, leading to higher operational costs due to the extensive computational power needed to validate transactions and maintain the network.</p>
</list-item>
</list>
</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-11">
<title>Step 9: Is public verifiability required?</title>
<p id="p-52">
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Rationale</p>
<p>Public verifiability is an important factor in the choice of blockchain architecture, especially in the healthcare sector, where the integrity of data and the accountability of actors are subject to scrutiny by external parties [<xref ref-type="bibr" rid="B54">54</xref>, <xref ref-type="bibr" rid="B67">67</xref>]. In such scenarios, the blockchain’s inherent audibility feature becomes invaluable, as it provides a tamper-proof ledger where all transactions are recorded in a manner that is secure and accessible for verification purposes. The decision here will largely depend on the nature of the data being shared and the broader objectives of the healthcare organization regarding public trust and accountability [<xref ref-type="bibr" rid="B8">8</xref>].</p>
</list-item>
<list-item>
<label>2.</label>
<p>Term definition</p>
<p>“Public verifiability” means the capability of any external party, without necessarily being part of the blockchain network, to validate the data and transactions on the blockchain [<xref ref-type="bibr" rid="B8">8</xref>]. This feature is critical in ensuring transparency and integrity of data, where the public or independent entities can audit and confirm the legitimacy of the information stored on the blockchain [<xref ref-type="bibr" rid="B8">8</xref>].</p>
</list-item>
<list-item>
<label>3.</label>
<p>Decision pathway</p>
<p>
<list list-type="bullet">
<list-item>
<p>If public verifiability is a requirement, indicating that the recorded data is of public interest and not sensitive, a public permissioned blockchain is likely an appropriate choice. It allows for public verification while controlling access and maintaining some level of privacy and security, fostering transparency and trust, particularly in public health data or research findings.</p>
</list-item>
<list-item>
<p>In cases where public verifiability is not essential, or data sensitivity necessitates more restricted access, a private blockchain might be more suitable. This blockchain limits verifiability to specific, authorized parties, offering a controlled environment while maintaining security and privacy.</p>
</list-item>
</list>
</p>
</list-item>
</list>
</p>
</sec>
<sec id="t3-12">
<title>Evaluating the suitability of blockchain in healthcare: case studies</title>
<p id="p-53">To evaluate the utility of our decision-making flowchart in guiding blockchain implementation decisions within the healthcare sector, we analyze MedRec [<xref ref-type="bibr" rid="B27">27</xref>], Drugledger [<xref ref-type="bibr" rid="B28">28</xref>], iWellChain [<xref ref-type="bibr" rid="B82">82</xref>], DACIL [<xref ref-type="bibr" rid="B83">83</xref>], REALM [<xref ref-type="bibr" rid="B84">84</xref>], ChainSure [<xref ref-type="bibr" rid="B32">32</xref>], and LUCE [<xref ref-type="bibr" rid="B85">85</xref>], as shown in <xref ref-type="table" rid="t4">Table 4</xref>. In this table, the category column classifies each project into functional areas. The case description provides brief summaries of each project’s objectives. Assumptions detail the underlying premises for each project’s evaluation, focusing on aspects like data privacy and cost distribution. The decision path outlines the step-by-step choices made based on the decision-making flowchart, indicating decisions with ‘Yes’ or ‘No’. Finally, the final outcome column shows the type of blockchain technology adopted by each project. Detailed analysis can be found in <xref ref-type="sec" rid="s-suppl">Supplementary material</xref>.</p>
<table-wrap id="t4">
<label>Table 4</label>
<caption>
<p id="t4-p-1">Case studies of evaluating the suitability of blockchain applications in healthcare</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th>
<bold>Category</bold>
</th>
<th>
<bold>Case description</bold>
</th>
<th>
<bold>Assumptions</bold>
</th>
<th>
<bold>Decision path</bold>
</th>
<th>
<bold>Final outcome</bold>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Healthcare data management</td>
<td>MedRec—enables patients a comprehensive, immutable log and convenient access to their medical information across providers and treatment sites</td>
<td>No</td>
<td>1-Yes, 2-No, 3-Yes, 4-Yes, 5-Yes, 6-No, 7-Yes, 8-Yes</td>
<td>Public permissioned blockchain</td>
</tr>
<tr>
<td>Pharmaceutical supply chain and healthcare logistics</td>
<td>Drugledger is designed to enhance traceability and regulation throughout the drug supply chain</td>
<td>Prioritize operational efficiency and long-term sustainability over initial cost</td>
<td>1-Yes, 2-No, 3-Yes, 4-Yes, 5-Yes, 6-No, 7-Yes, 8-Yes</td>
<td>Public permissioned blockchain</td>
</tr>
<tr>
<td>Interoperability and consolidated healthcare systems</td>
<td>iWellChain—is designed to improve data sharing among healthcare providers and patients, ensuring data interoperability and security</td>
<td>Transaction costs are paid by the users initiating transactions, allowing them to operate without incurring the full burden of the network costs, and distributing it among users</td>
<td>1-Yes, 2-No, 3-Yes, 4-Yes, 5-Yes, 6-No, 7-Yes, 8-No</td>
<td>Public permissionless blockchain</td>
</tr>
<tr>
<td>Clinical trials and medical research</td>
<td>DACIL—to define decision support and a digital companion to aid patients (and their caregivers) during lung attacks. The project requires trials to collect user data and to have them interact with the platform</td>
<td>Phase 1: User’s data and some previously collected cohorts will be stored on a trusted platform. Few data analysts will have access to the data<break />Phase 2: The investigators would like to find a way to share data later with the broader research community</td>
<td>Phase 1: 1-Yes, 2-Yes<break />Phase 2: 1-Yes, 2-No, 3-Yes, 4-Yes, 5-No</td>
<td>Initially, blockchain is not needed. When sharing broadly, a public permissionless blockchain would help to better control the data</td>
</tr>
<tr>
<td>Remote care and Internet of Things (IoT) architectures</td>
<td>REALM—aims to define a monitoring platform in support of the health Artificial Intelligence (AI) software certification process</td>
<td>In order to test health AI software, special data needs to be used. Health data is not shared but the outcomes of the tests on the AI models should be seen and trusted by all the members of the REALM network. No trusted third party can be used</td>
<td>1-Yes, 2-No, 3-Yes, 4-Yes, 5-Yes, 6-No, 7-No, 9-Yes</td>
<td>REALM requires a public permissioned blockchain for public verifiability</td>
</tr>
<tr>
<td>Health insurance and claims processing</td>
<td>ChainSure—aims to create a decentralized, tamper-proof system for health insurance management. It automates policy selection, claims processing, and data sharing, thereby reducing administrative overhead and enhancing data integrity</td>
<td>Transaction costs are paid by the users initiating transactions, allowing them to operate without incurring the full burden of the network costs, and distributing it among users</td>
<td>1-Yes, 2-No, 3-Yes, 4-Yes, 5-Yes, 6-No, 7-Yes, 8-No</td>
<td>Public permissionless blockchain</td>
</tr>
<tr>
<td>Governance</td>
<td>License accoUntability and CompliancE (LUCE)—is designed to facilitate compliance with data licensing terms and General Data Protection Regulation (GDPR) requirements through a blockchain solution</td>
<td>Transaction costs are paid by the users initiating transactions, allowing them to operate without incurring the full burden of the network costs, and distributing it among users</td>
<td>1-Yes, 2-No, 3-Yes, 4-Yes, 5-Yes, 6-No, 7-Yes, 8-No</td>
<td>Public permissionless blockchain</td>
</tr>
</tbody>
</table>
</table-wrap>
<p id="p-54">To have a more comparative understanding of our decision-making framework, we integrate the case studies into the original flowchart, as shown in <xref ref-type="fig" rid="fig3">Figure 3</xref>. The color-coded paths indicate different routes that can be taken depending on the answers to the yes/no questions at each decision point. These paths represent distinct case studies, each with unique considerations and endpoints.</p>
<fig id="fig3" position="float">
<label>Figure 3</label>
<caption>
<p id="fig3-p-1">Case studies of the decision-making flowchart</p>
</caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="edht-02-101114-g003.tif" />
</fig>
</sec>
</sec>
<sec id="s4">
<title>Discussion</title>
<sec id="t4-1">
<title>Implications of the results for healthcare professionals and policymakers</title>
<p id="p-55">The findings of this review, resulting in a decision-making flowchart for determining the suitability of blockchain in healthcare applications, have significant implications for healthcare professionals and policymakers.</p>
<p id="p-56">For healthcare professionals, the flowchart serves as a valuable tool for assessing the potential benefits and challenges of integrating blockchain into their practice. It guides them in considering factors such as the necessity of data sharing, trusted third parties, date immutability and integrity, participant knowledge, patient involvement, and public verifiability. By leveraging blockchain technology in appropriate scenarios, healthcare professionals can enhance data security and privacy, improve interoperability, and enhance patient care coordination [<xref ref-type="bibr" rid="B3">3</xref>]. Understanding the conditions under which blockchain is most likely to yield positive outcomes is essential for effective utilization by healthcare professionals.</p>
<p id="p-57">Policymakers can also benefit from the insights provided by this study to develop appropriate regulations and guidelines regarding the implementation of blockchain in healthcare. The flowchart offers policymakers a comprehensive understanding of the factors to consider when assessing the feasibility associated with adopting blockchain technology. Policymakers can utilize this information to shape policies that support innovation while ensuring privacy, security, and ethical use of blockchain in healthcare. Additionally, they can address legal and regulatory challenges that may arise, promoting responsible and effective integration of blockchain in the healthcare ecosystem [<xref ref-type="bibr" rid="B86">86</xref>].</p>
</sec>
<sec id="t4-2">
<title>Identification of gaps in the current literature and areas for future research</title>
<p id="p-58">This review has also identified gaps and areas for future research in the healthcare blockchain field. While the literature on this topic has expanded, certain aspects require further investigation.</p>
<p id="p-59">Firstly, more empirical studies are needed to evaluate blockchain solutions’ actual implementation and impact in real-world healthcare settings. While existing literature provides theoretical insights and frameworks, empirical evidence of blockchain applications’ effectiveness, efficiency, and user experiences in healthcare is limited. Future research should focus on conducting expert interviews, stakeholder surveys, and pilot projects to assess the practical implications, challenges, and benefits of implementing blockchain technology across various healthcare domains and organizational contexts.</p>
<p id="p-60">Secondly, blockchain’s ethical, legal, and social implications in healthcare require further exploration. As blockchain technology becomes more prevalent in healthcare, examining ethical considerations related to patient privacy, data ownership, consent management, and data governance is crucial. Additionally, legal and regulatory frameworks should be developed to address unique challenges posed by blockchain, such as jurisdictional issues, liability, and dispute resolution. Future research should provide comprehensive guidance on the ethical and legal aspects of blockchain implementation, facilitating responsible and transparent use of the technology in healthcare.</p>
<p id="p-61">Furthermore, as the volume and complexity of healthcare data continue to rise, the scalability of blockchain solutions becomes a critical concern. Scalability in this context refers to the ability of blockchain networks to handle increasing amounts of data without compromising on speed or efficiency. Efficient data processing is crucial in healthcare, where real-time data availability can significantly impact patient care and outcomes. Future research needs to focus on enhancing the scalability of these networks through innovative approaches such as sharding, which divides the network into smaller, more manageable segments, or through layer two solutions that process transactions off the main blockchain to decrease load and increase speed. This will ensure that as healthcare data grows, blockchain networks remain efficient and responsive to the needs of the industry.</p>
<p id="p-62">Lastly, interoperability between blockchain platforms and existing healthcare systems is critical for successfully adopting and implementing blockchain technology in healthcare. This interoperability involves the seamless integration and exchange of data across different blockchain platforms, blockchain networks, and legacy healthcare systems. The challenge lies in creating a standardized framework for secure, reliable, and efficient data exchange. Future studies should explore the development of technical solutions and standards that facilitate this integration. Adopting common standards can significantly enhance the potential for blockchain to support diverse healthcare applications, from patient records management to supply chain transparency, thereby improving healthcare delivery.</p>
</sec>
<sec id="t4-3">
<title>Limitations of the review and suggestions for improving future studies</title>
<p id="p-63">Despite employing a rigorous methodology, this review has some limitations. Firstly, it relies on existing SLRs as the primary source of information, which may vary in quality and coverage. To address this, future studies could consider incorporating primary research studies to complement findings from SLRs.</p>
<p id="p-64">Secondly, the validation of the decision-making flowchart is currently conducted using case studies, primarily due to constraints in time and resources. To enhance the validity of the flowchart in future iterations, future studies should incorporate a broader range of methods, such as expert interviews, stakeholder surveys, and pilot projects. These additional methods will gather diverse perspectives and more comprehensive feedback, contributing significantly to developing a more robust and reliable decision-making tool.</p>
<p id="p-65">Lastly, the decision-making flowchart presented in this study is based on synthesizing existing literature. It may not capture all possible factors or considerations relevant to specific healthcare contexts. Therefore, healthcare professionals and policymakers should contextualize the flowchart within their unique organizational settings and critically reflect before making decisions about adopting blockchain technology.</p>
<p id="p-66">In conclusion, this tertiary review underscores the potential benefits and complexities of integrating blockchain technology in healthcare. The study developed and validated a decision-making flowchart to assist healthcare professionals and policymakers in making informed decisions about blockchain applications in healthcare. The flowchart, tested through various case studies, offers a structured approach to evaluating the viability and implications of blockchain technology. Our findings stress the necessity of assessing key factors such as scalability, privacy, interoperability, and legal compliance to harness blockchain’s benefits effectively. The inclusion of practical case studies confirms the applicability of the decision-making tool across various healthcare domains, promoting a responsible and informed approach to adopting blockchain technology in the healthcare sector.</p>
</sec>
</sec>
</body>
<back>
<glossary>
<title>Abbreviations</title>
<def-list>
<def-item>
<term>EMRs</term>
<def>
<p>electronic medical records</p>
</def>
</def-item>
<def-item>
<term>IoT</term>
<def>
<p>Internet of Things</p>
</def>
</def-item>
<def-item>
<term>LUCE</term>
<def>
<p>License accoUntability and CompliancE</p>
</def>
</def-item>
<def-item>
<term>SLRs</term>
<def>
<p>systematic literature reviews</p>
</def>
</def-item>
</def-list>
</glossary>
<sec id="s-suppl" sec-type="supplementary-material">
<title>Supplementary materials</title>
<p>The supplementary material for this article is available at: <uri xlink:href="https://www.explorationpub.com/uploads/Article/file/101114_sup_1.pdf">https://www.explorationpub.com/uploads/Article/file/101114_sup_1.pdf</uri>.</p>
<supplementary-material id="SD1" content-type="local-data">
<media xlink:href="101114_sup_1.pdf" mimetype="application" mime-subtype="pdf"></media>
</supplementary-material>
</sec>
<sec id="s6">
<title>Declarations</title>
<sec>
<title>Author contributions</title>
<p>KL: Conceptualization, Investigation, Writing—original draft, Writing—review &amp; editing. ARS: Conceptualization, Writing—original draft, Writing—review &amp; editing. VU: Conceptualization, Writing—review &amp; editing, Supervision. All authors read and approved the submitted version.</p>
</sec>
<sec sec-type="COI-statement">
<title>Conflicts of interest</title>
<p>The authors declare that they have no conflicts of interest.</p>
</sec>
<sec>
<title>Ethical approval</title>
<p>Not applicable.</p>
</sec>
<sec>
<title>Consent to participate</title>
<p>Not applicable.</p>
</sec>
<sec>
<title>Consent to publication</title>
<p>Not applicable.</p>
</sec>
<sec sec-type="data-availability">
<title>Availability of data and materials</title>
<p>The datasets that support the findings of this study are available from the corresponding author upon reasonable request.</p>
</sec>
<sec>
<title>Funding</title>
<p>This work was partially funded by the following grants: the China Scholarship Council [202109650003]. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</p>
</sec>
<sec>
<title>Copyright</title>
<p>© The Author(s) 2024.</p>
</sec>
</sec>
<ref-list>
<ref id="B1">
<label>1</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Cong</surname>
<given-names>LW</given-names>
</name>
<name>
<surname>He</surname>
<given-names>Z</given-names>
</name>
</person-group>
<article-title>Blockchain Disruption and Smart Contracts</article-title>
<source>Rev Financ Stud</source>
<year iso-8601-date="2019">2019</year>
<volume>32</volume>
<fpage>1754</fpage>
<lpage>97</lpage>
<pub-id pub-id-type="doi">10.1093/rfs/hhz007</pub-id></element-citation>
</ref>
<ref id="B2">
<label>2</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zīle</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Strazdiņa</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Blockchain Use Cases and Their Feasibility</article-title>
<source>Appl Comput Syst</source>
<year iso-8601-date="2018">2018</year>
<volume>23</volume>
<fpage>12</fpage>
<lpage>20</lpage>
<pub-id pub-id-type="doi">10.2478/acss-2018-0002</pub-id></element-citation>
</ref>
<ref id="B3">
<label>3</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Attaran</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Blockchain technology in healthcare: Challenges and opportunities</article-title>
<source>Int J Healthc Manag</source>
<year iso-8601-date="2022">2022</year>
<volume>15</volume>
<fpage>70</fpage>
<lpage>83</lpage>
<pub-id pub-id-type="doi">10.1080/20479700.2020.1843887</pub-id></element-citation>
</ref>
<ref id="B4">
<label>4</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>AbuHalimeh</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Ali</surname>
<given-names>O</given-names>
</name>
</person-group>
<article-title>Comprehensive review for healthcare data quality challenges in blockchain technology</article-title>
<source>Front Big Data</source>
<year iso-8601-date="2023">2023</year>
<volume>6</volume>
<elocation-id>1173620</elocation-id>
<pub-id pub-id-type="doi">10.3389/fdata.2023.1173620</pub-id><pub-id pub-id-type="pmid">37252129</pub-id><pub-id pub-id-type="pmcid">PMC10213639</pub-id></element-citation>
</ref>
<ref id="B5">
<label>5</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>O’Donoghue</surname>
<given-names>O</given-names>
</name>
<name>
<surname>Vazirani</surname>
<given-names>AA</given-names>
</name>
<name>
<surname>Brindley</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Meinert</surname>
<given-names>E</given-names>
</name>
</person-group>
<article-title>Design Choices and Trade-Offs in Health Care Blockchain Implementations: Systematic Review</article-title>
<source>J Med Internet Res</source>
<year iso-8601-date="2019">2019</year>
<volume>21</volume>
<elocation-id>e12426</elocation-id>
<pub-id pub-id-type="doi">10.2196/12426</pub-id><pub-id pub-id-type="pmid">31094344</pub-id><pub-id pub-id-type="pmcid">PMC6533871</pub-id></element-citation>
</ref>
<ref id="B6">
<label>6</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hoffman</surname>
<given-names>MR</given-names>
</name>
<name>
<surname>Ibáñez</surname>
<given-names>L-D</given-names>
</name>
<name>
<surname>Simperl</surname>
<given-names>E</given-names>
</name>
</person-group>
<article-title>Toward a Formal Scholarly Understanding of Blockchain-Mediated Decentralization: A Systematic Review and a Framework</article-title>
<source>Front Blockchain</source>
<year iso-8601-date="2020">2020</year>
<volume>3</volume>
<elocation-id>35</elocation-id>
<pub-id pub-id-type="doi">10.3389/fbloc.2020.00035</pub-id></element-citation>
</ref>
<ref id="B7">
<label>7</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yaqoob</surname>
<given-names>I</given-names>
</name>
<name>
<surname>Salah</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Jayaraman</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Al-Hammadi</surname>
<given-names>Y</given-names>
</name>
</person-group>
<article-title>Blockchain for healthcare data management: opportunities, challenges, and future recommendations</article-title>
<source>Neural Comput Applic</source>
<year iso-8601-date="2022">2022</year>
<volume>34</volume>
<fpage>11475</fpage>
<lpage>90</lpage>
<pub-id pub-id-type="doi">10.1007/s00521-020-05519-w</pub-id></element-citation>
</ref>
<ref id="B8">
<label>8</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Wüst</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Gervais</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>Do you Need a Blockchain?</article-title>
<comment>In: 2018 Crypto Valley Conference on Blockchain Technology (CVCBT). Crypto Valley Conference on Blockchain Technology (CVCBT); 2018 Jun 20-22; Zug, Switzerland. IEEE; 2018. pp. 45–54.</comment>
<pub-id pub-id-type="doi">10.1109/cvcbt.2018.00011</pub-id></element-citation>
</ref>
<ref id="B9">
<label>9</label>
<element-citation publication-type="web">
<person-group person-group-type="author">
<name>
<surname>Nakamoto</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Bitcoin: A Peer-to-Peer Electronic Cash System [Internet]</article-title>
<comment>[cited 2023 Nov 1]. Available from: <uri xlink:href="https://assets.pubpub.org/d8wct41f/31611263538139.pdf">https://assets.pubpub.org/d8wct41f/31611263538139.pdf</uri></comment>
</element-citation>
</ref>
<ref id="B10">
<label>10</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Casino</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Dasaklis</surname>
<given-names>TK</given-names>
</name>
<name>
<surname>Patsakis</surname>
<given-names>C</given-names>
</name>
</person-group>
<article-title>A systematic literature review of blockchain-based applications: Current status, classification and open issues</article-title>
<source>Telemat Inform</source>
<year iso-8601-date="2019">2019</year>
<volume>36</volume>
<fpage>55</fpage>
<lpage>81</lpage>
<pub-id pub-id-type="doi">10.1016/j.tele.2018.11.006</pub-id></element-citation>
</ref>
<ref id="B11">
<label>11</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Levis</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Fontana</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Ughetto</surname>
<given-names>E</given-names>
</name>
</person-group>
<article-title>A look into the future of blockchain technology</article-title>
<source>Plos One</source>
<year iso-8601-date="2021">2021</year>
<volume>16</volume>
<elocation-id>e0258995</elocation-id>
<pub-id pub-id-type="doi">10.1371/journal.pone.0258995</pub-id><pub-id pub-id-type="pmid">34788307</pub-id><pub-id pub-id-type="pmcid">PMC8598042</pub-id></element-citation>
</ref>
<ref id="B12">
<label>12</label>
<element-citation publication-type="web">
<person-group person-group-type="author">
<name>
<surname>Yaga</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Mell</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Roby</surname>
<given-names>N</given-names>
</name>
<name>
<surname>Scarfone</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>Blockchain Technology Overview</article-title>
<comment>arXiv: 1906.11078v1 [Preprint]. 2019 [cited 2023 Nov 1]: [68 p.]. Available from: <uri xlink:href="https://arxiv.org/pdf/1906.11078">https://arxiv.org/pdf/1906.11078</uri></comment>
</element-citation>
</ref>
<ref id="B13">
<label>13</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Khan</surname>
<given-names>MA</given-names>
</name>
<name>
<surname>Salah</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>IoT security: Review, blockchain solutions, and open challenges</article-title>
<source>Future Gener Comput Syst</source>
<year iso-8601-date="2018">2018</year>
<volume>82</volume>
<fpage>395</fpage>
<lpage>411</lpage>
<pub-id pub-id-type="doi">10.1016/j.future.2017.11.022</pub-id></element-citation>
</ref>
<ref id="B14">
<label>14</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Fernández-Caramés</surname>
<given-names>TM</given-names>
</name>
<name>
<surname>Fraga-Lamas</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>A Review on the Use of Blockchain for the Internet of Things</article-title>
<source>IEEE Access</source>
<year iso-8601-date="2018">2018</year>
<volume>6</volume>
<fpage>32979</fpage>
<lpage>3001</lpage>
<pub-id pub-id-type="doi">10.1109/access.2018.2842685</pub-id></element-citation>
</ref>
<ref id="B15">
<label>15</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Taherdoost</surname>
<given-names>H</given-names>
</name>
</person-group>
<article-title>Smart Contracts in Blockchain Technology: A Critical Review</article-title>
<source>Information</source>
<year iso-8601-date="2023">2023</year>
<volume>14</volume>
<elocation-id>117</elocation-id>
<pub-id pub-id-type="doi">10.3390/info14020117</pub-id></element-citation>
</ref>
<ref id="B16">
<label>16</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Naaz</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Saxena</surname>
<given-names>AK</given-names>
</name>
<name>
<surname>Shah</surname>
<given-names>PK</given-names>
</name>
</person-group>
<article-title>Blockchain technology’s overview: Consensus, architecture and future trends</article-title>
<source>AIP Conf Proc</source>
<year iso-8601-date="2023">2023</year>
<volume>2427</volume>
<elocation-id>020018</elocation-id>
<pub-id pub-id-type="doi">10.1063/5.0125073</pub-id></element-citation>
</ref>
<ref id="B17">
<label>17</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hawlitschek</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Notheisen</surname>
<given-names>B</given-names>
</name>
<name>
<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 iso-8601-date="2018">2018</year>
<volume>29</volume>
<fpage>50</fpage>
<lpage>63</lpage>
<pub-id pub-id-type="doi">10.1016/j.elerap.2018.03.005</pub-id></element-citation>
</ref>
<ref id="B18">
<label>18</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Belchior</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Vasconcelos</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Guerreiro</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Correia</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>A Survey on Blockchain Interoperability: Past, Present, and Future Trends</article-title>
<source>ACM Comput Surv</source>
<year iso-8601-date="2021">2021</year>
<volume>54</volume>
<fpage>1</fpage>
<lpage>41</lpage>
<pub-id pub-id-type="doi">10.1145/3471140</pub-id></element-citation>
</ref>
<ref id="B19">
<label>19</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mackey</surname>
<given-names>TK</given-names>
</name>
<name>
<surname>Kuo</surname>
<given-names>TT</given-names>
</name>
<name>
<surname>Gummadi</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Clauson</surname>
<given-names>KA</given-names>
</name>
<name>
<surname>Church</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Grishin</surname>
<given-names>D</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>‘Fit-for-purpose?’ – challenges and opportunities for applications of blockchain technology in the future of healthcare</article-title>
<source>BMC Med</source>
<year iso-8601-date="2019">2019</year>
<volume>17</volume>
<elocation-id>68</elocation-id>
<pub-id pub-id-type="doi">10.1186/s12916-019-1296-7</pub-id><pub-id pub-id-type="pmid">30914045</pub-id><pub-id pub-id-type="pmcid">PMC6436239</pub-id></element-citation>
</ref>
<ref id="B20">
<label>20</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Haleem</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Javaid</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Singh</surname>
<given-names>RP</given-names>
</name>
<name>
<surname>Suman</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Rab</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Blockchain technology applications in healthcare: An overview</article-title>
<source>Int J Intell Networks</source>
<year iso-8601-date="2021">2021</year>
<volume>2</volume>
<fpage>130</fpage>
<lpage>9</lpage>
<pub-id pub-id-type="doi">10.1016/j.ijin.2021.09.005</pub-id></element-citation>
</ref>
<ref id="B21">
<label>21</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Soltanisehat</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Alizadeh</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Hao</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Choo</surname>
<given-names>K-KR</given-names>
</name>
</person-group>
<article-title>Technical, Temporal, and Spatial Research Challenges and Opportunities in Blockchain-Based Healthcare: A Systematic Literature Review</article-title>
<source>IEEE Trans Eng Manage</source>
<year iso-8601-date="2020">2020</year>
<volume>70</volume>
<fpage>353</fpage>
<lpage>68</lpage>
<pub-id pub-id-type="doi">10.1109/tem.2020.3013507</pub-id></element-citation>
</ref>
<ref id="B22">
<label>22</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Elangovan</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Long</surname>
<given-names>CS</given-names>
</name>
<name>
<surname>Bakrin</surname>
<given-names>FS</given-names>
</name>
<name>
<surname>Tan</surname>
<given-names>CS</given-names>
</name>
<name>
<surname>Goh</surname>
<given-names>KW</given-names>
</name>
<name>
<surname>Yeoh</surname>
<given-names>SF</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>The Use of Blockchain Technology in the Health Care Sector: Systematic Review</article-title>
<source>JMIR Med Inf</source>
<year iso-8601-date="2022">2022</year>
<volume>10</volume>
<elocation-id>e17278</elocation-id>
<pub-id pub-id-type="doi">10.2196/17278</pub-id><pub-id pub-id-type="pmid">35049516</pub-id><pub-id pub-id-type="pmcid">PMC8814929</pub-id></element-citation>
</ref>
<ref id="B23">
<label>23</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Merlo</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Pio</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Giusto</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Bilancia</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>On the exploitation of the blockchain technology in the healthcare sector: A systematic review</article-title>
<source>Expert Syst Appl</source>
<year iso-8601-date="2023">2023</year>
<volume>213</volume>
<elocation-id>118897</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.eswa.2022.118897</pub-id></element-citation>
</ref>
<ref id="B24">
<label>24</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Saeed</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Malik</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Bashir</surname>
<given-names>U</given-names>
</name>
<name>
<surname>Ahmad</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Riaz</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Ilyas</surname>
<given-names>M</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>Blockchain technology in healthcare: A systematic review</article-title>
<source>Plos One</source>
<year iso-8601-date="2022">2022</year>
<volume>17</volume>
<elocation-id>e0266462</elocation-id>
<pub-id pub-id-type="doi">10.1371/journal.pone.0266462</pub-id><pub-id pub-id-type="pmid">35404955</pub-id><pub-id pub-id-type="pmcid">PMC9000089</pub-id></element-citation>
</ref>
<ref id="B25">
<label>25</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Agbo</surname>
<given-names>CC</given-names>
</name>
<name>
<surname>Mahmoud</surname>
<given-names>QH</given-names>
</name>
<name>
<surname>Eklund</surname>
<given-names>JM</given-names>
</name>
</person-group>
<article-title>Blockchain Technology in Healthcare: A Systematic Review</article-title>
<source>Healthcare</source>
<year iso-8601-date="2019">2019</year>
<volume>7</volume>
<elocation-id>56</elocation-id>
<pub-id pub-id-type="doi">10.3390/healthcare7020056</pub-id><pub-id pub-id-type="pmid">30987333</pub-id><pub-id pub-id-type="pmcid">PMC6627742</pub-id></element-citation>
</ref>
<ref id="B26">
<label>26</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chukwu</surname>
<given-names>E</given-names>
</name>
<name>
<surname>Garg</surname>
<given-names>L</given-names>
</name>
</person-group>
<article-title>A Systematic Review of Blockchain in Healthcare: Frameworks, Prototypes, and Implementations</article-title>
<source>IEEE Access</source>
<year iso-8601-date="2020">2020</year>
<volume>8</volume>
<fpage>21196</fpage>
<lpage>214</lpage>
<pub-id pub-id-type="doi">10.1109/access.2020.2969881</pub-id></element-citation>
</ref>
<ref id="B27">
<label>27</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Azaria</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Ekblaw</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Vieira</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Lippman</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>MedRec: Using Blockchain for Medical Data Access and Permission Management</article-title>
<comment>In: 2016 2nd International Conference on Open and Big Data (OBD). International Conference on Open and Big Data (OBD); 2016 Aug 22-24; Vienna, Austria. IEEE; 2016. pp. 25–30.</comment>
<pub-id pub-id-type="doi">10.1109/obd.2016.11</pub-id></element-citation>
</ref>
<ref id="B28">
<label>28</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Huang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Long</surname>
<given-names>C</given-names>
</name>
</person-group>
<article-title>Drugledger: A Practical Blockchain System for Drug Traceability and Regulation</article-title>
<comment>In: 2018 IEEE international conference on internet of things (iThings) and IEEE green computing and communications (GreenCom) and IEEE cyber, physical and social computing (CPSCom) and IEEE smart data (SmartData). IEEE/ACM Int’l Conference on &amp; Int’l Conference on Cyber, Physical and Social Computing (CPSCom) Green Computing and Communications (GreenCom); 2018 Aug 03-2018 Jul 30; Halifax, NS, Canada. IEEE; 2018. pp. 1137–44.</comment>
<pub-id pub-id-type="doi">10.1109/cybermatics_2018.2018.00206</pub-id></element-citation>
</ref>
<ref id="B29">
<label>29</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yue</surname>
<given-names>X</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Jin</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Jiang</surname>
<given-names>W</given-names>
</name>
</person-group>
<article-title>Healthcare Data Gateways: Found Healthcare Intelligence on Blockchain with Novel Privacy Risk Control</article-title>
<source>J Med Syst</source>
<year iso-8601-date="2016">2016</year>
<volume>40</volume>
<elocation-id>218</elocation-id>
<pub-id pub-id-type="doi">10.1007/s10916-016-0574-6</pub-id><pub-id pub-id-type="pmid">27565509</pub-id></element-citation>
</ref>
<ref id="B30">
<label>30</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>P</given-names>
</name>
<name>
<surname>White</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Schmidt</surname>
<given-names>DC</given-names>
</name>
<name>
<surname>Lenz</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Rosenbloom</surname>
<given-names>ST</given-names>
</name>
</person-group>
<article-title>FHIRChain: Applying Blockchain to Securely and Scalably Share Clinical Data</article-title>
<source>Comput Struct Biotechnol J</source>
<year iso-8601-date="2018">2018</year>
<volume>16</volume>
<fpage>267</fpage>
<lpage>78</lpage>
<pub-id pub-id-type="doi">10.1016/j.csbj.2018.07.004</pub-id><pub-id pub-id-type="pmid">30108685</pub-id><pub-id pub-id-type="pmcid">PMC6082774</pub-id></element-citation>
</ref>
<ref id="B31">
<label>31</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Azbeg</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Ouchetto</surname>
<given-names>O</given-names>
</name>
<name>
<surname>Andaloussi</surname>
<given-names>SJ</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 Inf J</source>
<year iso-8601-date="2022">2022</year>
<volume>23</volume>
<fpage>329</fpage>
<lpage>43</lpage>
<pub-id pub-id-type="doi">10.1016/j.eij.2022.02.004</pub-id></element-citation>
</ref>
<ref id="B32">
<label>32</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Karmakar</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Ghosh</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Banerjee</surname>
<given-names>PS</given-names>
</name>
<name>
<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 iso-8601-date="2023">2023</year>
<volume>17</volume>
<elocation-id>200177</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.iswa.2023.200177</pub-id></element-citation>
</ref>
<ref id="B33">
<label>33</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hölbl</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Kompara</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Kamišalić</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Nemec</surname>
<given-names>Zlatolas L</given-names>
</name>
</person-group>
<article-title>A Systematic Review of the Use of Blockchain in Healthcare</article-title>
<source>Symmetry</source>
<year iso-8601-date="2018">2018</year>
<volume>10</volume>
<elocation-id>470</elocation-id>
<pub-id pub-id-type="doi">10.3390/sym10100470</pub-id></element-citation>
</ref>
<ref id="B34">
<label>34</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Urovi</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Jaiman</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Angerer</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Dumontier</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>LUCE: A blockchain-based data sharing platform for monitoring data License accoUntability and CompliancE</article-title>
<source>Blockchain Res Appl</source>
<year iso-8601-date="2022">2022</year>
<volume>3</volume>
<elocation-id>100102</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.bcra.2022.100102</pub-id></element-citation>
</ref>
<ref id="B35">
<label>35</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Jaiman</surname>
<given-names>V</given-names>
</name>
<name>
<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 iso-8601-date="2020">2020</year>
<volume>8</volume>
<fpage>143734</fpage>
<lpage>45</lpage>
<pub-id pub-id-type="doi">10.1109/access.2020.3014565</pub-id></element-citation>
</ref>
<ref id="B36">
<label>36</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Khezr</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Moniruzzaman</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Yassine</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Benlamri</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Blockchain Technology in Healthcare: A Comprehensive Review and Directions for Future Research</article-title>
<source>Appl Sci</source>
<year iso-8601-date="2019">2019</year>
<volume>9</volume>
<elocation-id>1736</elocation-id>
<pub-id pub-id-type="doi">10.3390/app9091736</pub-id></element-citation>
</ref>
<ref id="B37">
<label>37</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Peng</surname>
<given-names>Z</given-names>
</name>
<name>
<surname>Xu</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Xu</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Chu</surname>
<given-names>X</given-names>
</name>
</person-group>
<article-title>P<sup>2</sup>B-Trace: Privacy-Preserving Blockchain-based Contact Tracing to Combat Pandemics</article-title>
<comment>In: 2021 International Conference on Management of Data. International Conference on Management of Data; 2021 Jun 20-25; China. MOD; 2021. pp. 2389–93.</comment>
<pub-id pub-id-type="doi">10.1145/3448016.3459237</pub-id></element-citation>
</ref>
<ref id="B38">
<label>38</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Adere</surname>
<given-names>EM</given-names>
</name>
</person-group>
<article-title>Blockchain in healthcare and IoT: A systematic literature review</article-title>
<source>Array</source>
<year iso-8601-date="2022">2022</year>
<volume>14</volume>
<elocation-id>100139</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.array.2022.100139</pub-id></element-citation>
</ref>
<ref id="B39">
<label>39</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pandey</surname>
<given-names>AK</given-names>
</name>
<name>
<surname>Khan</surname>
<given-names>AI</given-names>
</name>
<name>
<surname>Abushark</surname>
<given-names>YB</given-names>
</name>
<name>
<surname>Alam</surname>
<given-names>MM</given-names>
</name>
<name>
<surname>Agrawal</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Kumar</surname>
<given-names>R</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>Key Issues in Healthcare Data Integrity: Analysis and Recommendations</article-title>
<source>IEEE Access</source>
<year iso-8601-date="2020">2020</year>
<volume>8</volume>
<fpage>40612</fpage>
<lpage>28</lpage>
<pub-id pub-id-type="doi">10.1109/access.2020.2976687</pub-id></element-citation>
</ref>
<ref id="B40">
<label>40</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chandol</surname>
<given-names>MK</given-names>
</name>
<name>
<surname>Kameswara</surname>
<given-names>Rao M</given-names>
</name>
</person-group>
<article-title>Blockchain-based cryptographic approach for privacy enabled data integrity model for IoT healthcare</article-title>
<source>J Exp Theor Artif Intell</source>
<year iso-8601-date="2023">2023</year>
<fpage>1</fpage>
<lpage>22</lpage>
<pub-id pub-id-type="doi">10.1080/0952813x.2023.2183268</pub-id></element-citation>
</ref>
<ref id="B41">
<label>41</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Jiang</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>X</given-names>
</name>
<name>
<surname>Yu</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Ding</surname>
<given-names>W</given-names>
</name>
</person-group>
<article-title>Risk and UCON-based access control model for healthcare big data</article-title>
<source>J Big Data</source>
<year iso-8601-date="2023">2023</year>
<volume>10</volume>
<elocation-id>104</elocation-id>
<pub-id pub-id-type="doi">10.1186/s40537-023-00783-8</pub-id></element-citation>
</ref>
<ref id="B42">
<label>42</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ali</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Al-Rimy</surname>
<given-names>BAS</given-names>
</name>
<name>
<surname>Alsubaei</surname>
<given-names>FS</given-names>
</name>
<name>
<surname>Almazroi</surname>
<given-names>AA</given-names>
</name>
<name>
<surname>Almazroi</surname>
<given-names>AA</given-names>
</name>
</person-group>
<article-title>HealthLock: Blockchain-Based Privacy Preservation Using Homomorphic Encryption in Internet of Things Healthcare Applications</article-title>
<source>Sensors (Basel)</source>
<year iso-8601-date="2023">2023</year>
<volume>23</volume>
<elocation-id>6762</elocation-id>
<pub-id pub-id-type="doi">10.3390/s23156762</pub-id><pub-id pub-id-type="pmid">37571545</pub-id><pub-id pub-id-type="pmcid">PMC10422473</pub-id></element-citation>
</ref>
<ref id="B43">
<label>43</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Moosa</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Ali</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Alaswad</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Elmedany</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Balakrishna</surname>
<given-names>C</given-names>
</name>
</person-group>
<article-title>A combined Blockchain and zero-knowledge model for healthcare B2B and B2C data sharing</article-title>
<source>Arab J Basic Appl Sci</source>
<year iso-8601-date="2023">2023</year>
<volume>30</volume>
<fpage>179</fpage>
<lpage>96</lpage>
<pub-id pub-id-type="doi">10.1080/25765299.2023.2188701</pub-id></element-citation>
</ref>
<ref id="B44">
<label>44</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mittal</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Ghosh</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>A three-phase framework for secure storage and sharing of healthcare data based on blockchain, IPFS, proxy re-encryption and group communication</article-title>
<source>J Supercomput</source>
<year iso-8601-date="2024">2024</year>
<volume>80</volume>
<fpage>7955</fpage>
<lpage>92</lpage>
<pub-id pub-id-type="doi">10.1007/s11227-023-05735-w</pub-id></element-citation>
</ref>
<ref id="B45">
<label>45</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Liu</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Xie</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>H</given-names>
</name>
</person-group>
<article-title>A secure and efficient electronic medical record data sharing scheme based on blockchain and proxy re-encryption</article-title>
<source>J Cloud Comput</source>
<year iso-8601-date="2024">2024</year>
<volume>13</volume>
<elocation-id>44</elocation-id>
<pub-id pub-id-type="doi">10.1186/s13677-024-00608-w</pub-id></element-citation>
</ref>
<ref id="B46">
<label>46</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhou</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Diro</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Saini</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Kaisar</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Hiep</surname>
<given-names>PC</given-names>
</name>
</person-group>
<article-title>Leveraging zero knowledge proofs for blockchain-based identity sharing: A survey of advancements, challenges and opportunities</article-title>
<source>J Inf Secur Appl</source>
<year iso-8601-date="2024">2024</year>
<volume>80</volume>
<elocation-id>103678</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.jisa.2023.103678</pub-id></element-citation>
</ref>
<ref id="B47">
<label>47</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Ramzan</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Aqdus</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Ravi</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Koundal</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Amin</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Al</surname>
<given-names>Ghamdi MA</given-names>
</name>
</person-group>
<article-title>Healthcare Applications Using Blockchain Technology: Motivations and Challenges</article-title>
<comment>In: IEEE Transactions on Engineering Management. IEEE Transactions on Engineering Management; 2022 Jul 25; 2022. pp. 2874–90.</comment>
<pub-id pub-id-type="doi">10.1109/tem.2022.3189734</pub-id></element-citation>
</ref>
<ref id="B48">
<label>48</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Minssen</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Rajam</surname>
<given-names>N</given-names>
</name>
<name>
<surname>Bogers</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Clinical trial data transparency and GDPR compliance: Implications for data sharing and open innovation</article-title>
<source>Sci Public Policy</source>
<year iso-8601-date="2020">2020</year>
<volume>47</volume>
<fpage>616</fpage>
<lpage>26</lpage>
<pub-id pub-id-type="doi">10.1093/scipol/scaa014</pub-id></element-citation>
</ref>
<ref id="B49">
<label>49</label>
<element-citation publication-type="web">
<person-group person-group-type="author">
<name>
<surname>Ritz</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Althauser</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Wilson</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>Connecting Health Information Systems for Better Health: Leveraging interoperability standards to link patient, provider, payor, and policymaker data [Internet]</article-title>
<comment>PATH; 2014 [cited 2023 Nov 1]. Available from: <uri xlink:href="https://www.r4d.org/wp-content/uploads/Connecting-Health-Information-Systems-for-Better-Health.pdf">https://www.r4d.org/wp-content/uploads/Connecting-Health-Information-Systems-for-Better-Health.pdf</uri></comment>
</element-citation>
</ref>
<ref id="B50">
<label>50</label>
<element-citation publication-type="web">
<person-group person-group-type="author">
<name>
<surname>Keele</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Guidelines for performing Systematic Literature Reviews in Software Engineering [Internet]</article-title>
<comment>Kitchenham; 2007 [cited 2023 Nov 1]. Available from: <uri xlink:href="https://www.researchgate.net/profile/Barbara-Kitchenham/publication/302924724_Guidelines_for_performing_Systematic_Literature_Reviews_in_Software_Engineering/links/61712932766c4a211c03a6f7/Guidelines-for-performing-Systematic-Literature-Reviews-in-Software-Engineering.pdf">https://www.researchgate.net/profile/Barbara-Kitchenham/publication/302924724_Guidelines_for_performing_Systematic_Literature_Reviews_in_Software_Engineering/links/61712932766c4a211c03a6f7/Guidelines-for-performing-Systematic-Literature-Reviews-in-Software-Engineering.pdf</uri></comment>
</element-citation>
</ref>
<ref id="B51">
<label>51</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Haddad</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Habaebi</surname>
<given-names>MH</given-names>
</name>
<name>
<surname>Islam</surname>
<given-names>MR</given-names>
</name>
<name>
<surname>Hasbullah</surname>
<given-names>NF</given-names>
</name>
<name>
<surname>Zabidi</surname>
<given-names>SA</given-names>
</name>
</person-group>
<article-title>Systematic Review on AI-Blockchain Based E-Healthcare Records Management Systems</article-title>
<source>IEEE Access</source>
<year iso-8601-date="2022">2022</year>
<volume>10</volume>
<fpage>94583</fpage>
<lpage>615</lpage>
<pub-id pub-id-type="doi">10.1109/access.2022.3201878</pub-id></element-citation>
</ref>
<ref id="B52">
<label>52</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Javed</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Aabid</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Danish</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Tahir</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Zainab</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Role of Blockchain Technology in Healthcare: A Systematic Review</article-title>
<comment>In: 2021 International Conference on Innovative Computing (ICIC). International Conference on Innovative Computing (ICIC); 2021 Nov 9-10; Lahore, Pakistan. IEEE; 2021. pp. 1–8.</comment>
<pub-id pub-id-type="doi">10.1109/icic53490.2021.9692981</pub-id></element-citation>
</ref>
<ref id="B53">
<label>53</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Fang</surname>
<given-names>HSA</given-names>
</name>
<name>
<surname>Tan</surname>
<given-names>TH</given-names>
</name>
<name>
<surname>Tan</surname>
<given-names>YFC</given-names>
</name>
<name>
<surname>Tan</surname>
<given-names>CJM</given-names>
</name>
</person-group>
<article-title>Blockchain Personal Health Records: Systematic Review</article-title>
<source>J Med Internet Res</source>
<year iso-8601-date="2021">2021</year>
<volume>23</volume>
<elocation-id>e25094</elocation-id>
<pub-id pub-id-type="doi">10.2196/25094</pub-id><pub-id pub-id-type="pmid">33847591</pub-id><pub-id pub-id-type="pmcid">PMC8080150</pub-id></element-citation>
</ref>
<ref id="B54">
<label>54</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Tandon</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Dhir</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Islam</surname>
<given-names>AN</given-names>
</name>
<name>
<surname>Mäntymäki</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Blockchain in healthcare: A systematic literature review, synthesizing framework and future research agenda</article-title>
<source>Comput Ind</source>
<year iso-8601-date="2020">2020</year>
<volume>122</volume>
<elocation-id>103290</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.compind.2020.103290</pub-id></element-citation>
</ref>
<ref id="B55">
<label>55</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yaqoob</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Khan</surname>
<given-names>MM</given-names>
</name>
<name>
<surname>Talib</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Butt</surname>
<given-names>AD</given-names>
</name>
<name>
<surname>Saleem</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Arif</surname>
<given-names>F</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>Use of Blockchain in Healthcare: A Systematic Literature Review</article-title>
<source>Int J Adv Comput Sci Appl</source>
<year iso-8601-date="2019">2019</year>
<volume>10;644–53</volume>
<pub-id pub-id-type="doi">10.14569/ijacsa.2019.0100581</pub-id></element-citation>
</ref>
<ref id="B56">
<label>56</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kiania</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Jameii</surname>
<given-names>SM</given-names>
</name>
<name>
<surname>Rahmani</surname>
<given-names>AM</given-names>
</name>
</person-group>
<article-title>Blockchain-based privacy and security preserving in electronic health: a systematic review</article-title>
<source>Multimed Tools Appl</source>
<year iso-8601-date="2023">2023</year>
<fpage>1</fpage>
<lpage>27</lpage>
<pub-id pub-id-type="doi">10.1007/s11042-023-14488-w</pub-id><pub-id pub-id-type="pmid">36811000</pub-id><pub-id pub-id-type="pmcid">PMC9936121</pub-id></element-citation>
</ref>
<ref id="B57">
<label>57</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kamangar</surname>
<given-names>ZU</given-names>
</name>
<name>
<surname>Memon</surname>
<given-names>RA</given-names>
</name>
<name>
<surname>Murtaza</surname>
<given-names>Memon G</given-names>
</name>
<name>
<surname>Kamangar</surname>
<given-names>UA</given-names>
</name>
</person-group>
<article-title>Integration of Internet of Things and blockchain technology in healthcare domain: A systematic literature review</article-title>
<source>Int J Commun Syst</source>
<year iso-8601-date="2023">2023</year>
<volume>36</volume>
<elocation-id>e5582</elocation-id>
<pub-id pub-id-type="doi">10.1002/dac.5582</pub-id></element-citation>
</ref>
<ref id="B58">
<label>58</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hussien</surname>
<given-names>HM</given-names>
</name>
<name>
<surname>Yasin</surname>
<given-names>SM</given-names>
</name>
<name>
<surname>Udzir</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Zaidan</surname>
<given-names>AA</given-names>
</name>
<name>
<surname>Zaidan</surname>
<given-names>BB</given-names>
</name>
</person-group>
<article-title>A Systematic Review for Enabling of Develop a Blockchain Technology in Healthcare Application: Taxonomy, Substantially Analysis, Motivations, Challenges, Recommendations and Future Direction</article-title>
<source>J Med Syst</source>
<year iso-8601-date="2019">2019</year>
<volume>43</volume>
<elocation-id>320</elocation-id>
<pub-id pub-id-type="doi">10.1007/s10916-019-1445-8</pub-id><pub-id pub-id-type="pmid">31522262</pub-id></element-citation>
</ref>
<ref id="B59">
<label>59</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Saranya</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Murugan</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>A systematic review of enabling blockchain in healthcare system: Analysis, current status, challenges and future direction</article-title>
<source>Mater Today Proc</source>
<year iso-8601-date="2023">2023</year>
<volume>80</volume>
<fpage>3010</fpage>
<lpage>5</lpage>
<pub-id pub-id-type="doi">10.1016/j.matpr.2021.07.105</pub-id></element-citation>
</ref>
<ref id="B60">
<label>60</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Alghazwi</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Turkmen</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Van</surname>
<given-names>Der Velde J</given-names>
</name>
<name>
<surname>Karastoyanova</surname>
<given-names>D</given-names>
</name>
</person-group>
<article-title>Blockchain for Genomics: A Systematic Literature Review</article-title>
<source>Distrib Ledger Technol Res Pract</source>
<year iso-8601-date="2022">2022</year>
<volume>1</volume>
<fpage>1</fpage>
<lpage>28</lpage>
<pub-id pub-id-type="doi">10.1145/3563044</pub-id></element-citation>
</ref>
<ref id="B61">
<label>61</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Thomson</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Beale</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Is blockchain ready for orthopaedics? A systematic review</article-title>
<source>J Clin Orthop Trauma</source>
<year iso-8601-date="2021">2021</year>
<volume>23</volume>
<elocation-id>101615</elocation-id>
<pub-id pub-id-type="doi">10.1016/j.jcot.2021.101615</pub-id><pub-id pub-id-type="pmid">34671546</pub-id><pub-id pub-id-type="pmcid">PMC8507193</pub-id></element-citation>
</ref>
<ref id="B62">
<label>62</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mayer</surname>
<given-names>AH</given-names>
</name>
<name>
<surname>da Costa</surname>
<given-names>CA</given-names>
</name>
<name>
<surname>Righi</surname>
<given-names>RdR</given-names>
</name>
</person-group>
<article-title>Electronic health records in a Blockchain: A systematic review</article-title>
<source>Health Informatics J</source>
<year iso-8601-date="2020">2020</year>
<volume>26</volume>
<fpage>1273</fpage>
<lpage>88</lpage>
<pub-id pub-id-type="doi">10.1177/1460458219866350</pub-id><pub-id pub-id-type="pmid">31566472</pub-id></element-citation>
</ref>
<ref id="B63">
<label>63</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Fatoum</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Hanna</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Halamka</surname>
<given-names>JD</given-names>
</name>
<name>
<surname>Sicker</surname>
<given-names>DC</given-names>
</name>
<name>
<surname>Spangenberg</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Hashmi</surname>
<given-names>SK</given-names>
</name>
</person-group>
<article-title>Blockchain Integration With Digital Technology and the Future of Health Care Ecosystems: Systematic Review</article-title>
<source>J Med Internet Res</source>
<year iso-8601-date="2021">2021</year>
<volume>23</volume>
<elocation-id>e19846</elocation-id>
<pub-id pub-id-type="doi">10.2196/19846</pub-id><pub-id pub-id-type="pmid">34726603</pub-id><pub-id pub-id-type="pmcid">PMC8596226</pub-id></element-citation>
</ref>
<ref id="B64">
<label>64</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lopez-Barreiro</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Alvarez-Sabucedo</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Garcia-Soidan</surname>
<given-names>JL</given-names>
</name>
<name>
<surname>Santos-Gago</surname>
<given-names>JM</given-names>
</name>
</person-group>
<article-title>Use of Blockchain Technology in the Domain of Physical Exercise, Physical Activity, Sport, and Active Ageing: A Systematic Review</article-title>
<source>Int J Environ Res Public Health</source>
<year iso-8601-date="2022">2022</year>
<volume>19</volume>
<elocation-id>8129</elocation-id>
<pub-id pub-id-type="doi">10.3390/ijerph19138129</pub-id><pub-id pub-id-type="pmid">35805788</pub-id><pub-id pub-id-type="pmcid">PMC9265962</pub-id></element-citation>
</ref>
<ref id="B65">
<label>65</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Dubovitskaya</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Novotny</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Xu</surname>
<given-names>Z</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>F</given-names>
</name>
</person-group>
<article-title>Applications of blockchain technology for data-sharing in oncology: Results from a systematic literature review</article-title>
<source>Oncology</source>
<year iso-8601-date="2020">2020</year>
<volume>98</volume>
<fpage>403</fpage>
<lpage>11</lpage>
<pub-id pub-id-type="doi">10.1159/000504325</pub-id><pub-id pub-id-type="pmid">31794967</pub-id></element-citation>
</ref>
<ref id="B66">
<label>66</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zukaib</surname>
<given-names>U</given-names>
</name>
<name>
<surname>Cui</surname>
<given-names>X</given-names>
</name>
<name>
<surname>Hassan</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Harris</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Hadi</surname>
<given-names>HJ</given-names>
</name>
<name>
<surname>Zheng</surname>
<given-names>C</given-names>
</name>
</person-group>
<article-title>Blockchain and Machine Learning in EHR Security: A Systematic Review</article-title>
<source>IEEE Access</source>
<year iso-8601-date="2023">2023</year>
<volume>11</volume>
<fpage>130230</fpage>
<lpage>56</lpage>
<pub-id pub-id-type="doi">10.1109/access.2023.3333229</pub-id></element-citation>
</ref>
<ref id="B67">
<label>67</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Vazirani</surname>
<given-names>AA</given-names>
</name>
<name>
<surname>O’Donoghue</surname>
<given-names>O</given-names>
</name>
<name>
<surname>Brindley</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Meinert</surname>
<given-names>E</given-names>
</name>
</person-group>
<article-title>Implementing Blockchains for Efficient Health Care: Systematic Review</article-title>
<source>J Med Internet Res</source>
<year iso-8601-date="2019">2019</year>
<volume>21</volume>
<elocation-id>e12439</elocation-id>
<pub-id pub-id-type="doi">10.2196/12439</pub-id><pub-id pub-id-type="pmid">30747714</pub-id><pub-id pub-id-type="pmcid">PMC6390185</pub-id></element-citation>
</ref>
<ref id="B68">
<label>68</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hulsen</surname>
<given-names>T</given-names>
</name>
</person-group>
<article-title>Sharing Is Caring-Data Sharing Initiatives in Healthcare</article-title>
<source>Int J Environ Res Public Health</source>
<year iso-8601-date="2020">2020</year>
<volume>17</volume>
<elocation-id>3046</elocation-id>
<pub-id pub-id-type="doi">10.3390/ijerph17093046</pub-id><pub-id pub-id-type="pmid">32349396</pub-id><pub-id pub-id-type="pmcid">PMC7246891</pub-id></element-citation>
</ref>
<ref id="B69">
<label>69</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hutchings</surname>
<given-names>E</given-names>
</name>
<name>
<surname>Loomes</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Butow</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Boyle</surname>
<given-names>FM</given-names>
</name>
</person-group>
<article-title>A systematic literature review of health consumer attitudes towards secondary use and sharing of health administrative and clinical trial data: a focus on privacy, trust, and transparency</article-title>
<source>Syst Rev</source>
<year iso-8601-date="2020">2020</year>
<volume>9</volume>
<elocation-id>235</elocation-id>
<pub-id pub-id-type="doi">10.1186/s13643-020-01481-9</pub-id><pub-id pub-id-type="pmid">33036664</pub-id><pub-id pub-id-type="pmcid">PMC7547503</pub-id></element-citation>
</ref>
<ref id="B70">
<label>70</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Boué</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Byrne</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Hayes</surname>
<given-names>AW</given-names>
</name>
<name>
<surname>Hoeng</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Peitsch</surname>
<given-names>MC</given-names>
</name>
</person-group>
<article-title>Embracing Transparency Through Data Sharing</article-title>
<source>Int J Toxicol</source>
<year iso-8601-date="2018">2018</year>
<volume>37</volume>
<fpage>466</fpage>
<lpage>71</lpage>
<pub-id pub-id-type="doi">10.1177/1091581818803880</pub-id><pub-id pub-id-type="pmid">30282506</pub-id><pub-id pub-id-type="pmcid">PMC6291903</pub-id></element-citation>
</ref>
<ref id="B71">
<label>71</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kerasidou</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Kerasidou</surname>
<given-names>CX</given-names>
</name>
</person-group>
<article-title>Data-driven research and healthcare: public trust, data governance and the NHS</article-title>
<source>BMC Med Ethics</source>
<year iso-8601-date="2023">2023</year>
<volume>24</volume>
<elocation-id>51</elocation-id>
<pub-id pub-id-type="doi">10.1186/s12910-023-00922-z</pub-id><pub-id pub-id-type="pmid">37452393</pub-id><pub-id pub-id-type="pmcid">PMC10349411</pub-id></element-citation>
</ref>
<ref id="B72">
<label>72</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kalkman</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Mostert</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Gerlinger</surname>
<given-names>C</given-names>
</name>
<name>
<surname>van Delden</surname>
<given-names>JJM</given-names>
</name>
<name>
<surname>van Thiel</surname>
<given-names>GJMW</given-names>
</name>
</person-group>
<article-title>Responsible data sharing in international health research: a systematic review of principles and norms</article-title>
<source>BMC Med Ethics</source>
<year iso-8601-date="2019">2019</year>
<volume>20</volume>
<elocation-id>21</elocation-id>
<pub-id pub-id-type="doi">10.1186/s12910-019-0359-9</pub-id><pub-id pub-id-type="pmid">30922290</pub-id><pub-id pub-id-type="pmcid">PMC6437875</pub-id></element-citation>
</ref>
<ref id="B73">
<label>73</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Reegu</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Daud</surname>
<given-names>SM</given-names>
</name>
<name>
<surname>Alam</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Interoperability Challenges in Healthcare Blockchain System - A Systematic Review</article-title>
<source>Ann Rom Soc Cell Biol</source>
<year iso-8601-date="2021">2021</year>
<fpage>15487</fpage>
<lpage>99</lpage>
</element-citation>
</ref>
<ref id="B74">
<label>74</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mulaji</surname>
<given-names>SS</given-names>
</name>
<name>
<surname>Roodt</surname>
<given-names>SS</given-names>
</name>
</person-group>
<article-title>The Practicality of Adopting Blockchain-Based Distributed Identity Management in Organisations: A Meta-Synthesis</article-title>
<source>Secur Commun Networks</source>
<year iso-8601-date="2021">2021</year>
<volume>2021</volume>
<elocation-id>9910078</elocation-id>
<pub-id pub-id-type="doi">10.1155/2021/9910078</pub-id></element-citation>
</ref>
<ref id="B75">
<label>75</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Xue</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>L</given-names>
</name>
</person-group>
<article-title>Security and Privacy for Healthcare Blockchains</article-title>
<source>IEEE Trans Serv Comput</source>
<year iso-8601-date="2021">2021</year>
<volume>15</volume>
<fpage>3668</fpage>
<lpage>86</lpage>
<pub-id pub-id-type="doi">10.1109/tsc.2021.3085913</pub-id></element-citation>
</ref>
<ref id="B76">
<label>76</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Schädler</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Lustenberger</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Spychiger</surname>
<given-names>F</given-names>
</name>
</person-group>
<article-title>Analyzing decision-making in blockchain governance</article-title>
<source>Front Blockchain</source>
<year iso-8601-date="2023">2023</year>
<volume>23</volume>
<pub-id pub-id-type="doi">10.3389/fbloc.2023.1256651</pub-id></element-citation>
</ref>
<ref id="B77">
<label>77</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hylock</surname>
<given-names>RH</given-names>
</name>
<name>
<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 iso-8601-date="2019">2019</year>
<volume>21</volume>
<elocation-id>e13592</elocation-id>
<pub-id pub-id-type="doi">10.2196/13592</pub-id><pub-id pub-id-type="pmid">31471959</pub-id><pub-id pub-id-type="pmcid">PMC6743266</pub-id></element-citation>
</ref>
<ref id="B78">
<label>78</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>de Freitas</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Amorim</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Machado</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Leão</surname>
<given-names>Teles E</given-names>
</name>
<name>
<surname>Baptista</surname>
<given-names>MJ</given-names>
</name>
<name>
<surname>Renedo</surname>
<given-names>A</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>Public and patient involvement in health data governance (DATAGov): protocol of a people-centred, mixed-methods study on data use and sharing for rare diseases care and research</article-title>
<source>BMJ Open</source>
<year iso-8601-date="2021">2021</year>
<volume>11</volume>
<elocation-id>e044289</elocation-id>
<pub-id pub-id-type="doi">10.1136/bmjopen-2020-044289</pub-id><pub-id pub-id-type="pmid">33722870</pub-id><pub-id pub-id-type="pmcid">PMC7959217</pub-id></element-citation>
</ref>
<ref id="B79">
<label>79</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Arnstein</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Wadsworth</surname>
<given-names>AC</given-names>
</name>
<name>
<surname>Yamamoto</surname>
<given-names>BA</given-names>
</name>
<name>
<surname>Stephens</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Sehmi</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Jones</surname>
<given-names>R</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>Patient involvement in preparing health research peer-reviewed publications or results summaries: a systematic review and evidence-based recommendations</article-title>
<source>Res Involv Engagem</source>
<year iso-8601-date="2020">2020</year>
<volume>6</volume>
<elocation-id>34</elocation-id>
<pub-id pub-id-type="doi">10.1186/s40900-020-00190-w</pub-id><pub-id pub-id-type="pmcid">PMC7313171</pub-id></element-citation>
</ref>
<ref id="B80">
<label>80</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Westphal</surname>
<given-names>E</given-names>
</name>
<name>
<surname>Seitz</surname>
<given-names>H</given-names>
</name>
</person-group>
<article-title>Digital and Decentralized Management of Patient Data in Healthcare Using Blockchain Implementations</article-title>
<source>Front Blockchain</source>
<year iso-8601-date="2021">2021</year>
<volume>4</volume>
<elocation-id>732112</elocation-id>
<pub-id pub-id-type="doi">10.3389/fbloc.2021.732112</pub-id></element-citation>
</ref>
<ref id="B81">
<label>81</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>McCarron</surname>
<given-names>TL</given-names>
</name>
<name>
<surname>Moffat</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Wilkinson</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Zelinsky</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Boyd</surname>
<given-names>JM</given-names>
</name>
<name>
<surname>White</surname>
<given-names>D</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>Understanding patient engagement in health system decision-making: a co-designed scoping review</article-title>
<source>Syst Rev</source>
<year iso-8601-date="2019">2019</year>
<volume>8</volume>
<elocation-id>97</elocation-id>
<pub-id pub-id-type="doi">10.1186/s13643-019-0994-8</pub-id><pub-id pub-id-type="pmid">30999950</pub-id><pub-id pub-id-type="pmcid">PMC6474065</pub-id></element-citation>
</ref>
<ref id="B82">
<label>82</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lo</surname>
<given-names>YS</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>CY</given-names>
</name>
<name>
<surname>Chien</surname>
<given-names>HF</given-names>
</name>
<name>
<surname>Chang</surname>
<given-names>SS</given-names>
</name>
<name>
<surname>Lu</surname>
<given-names>CY</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>RJ</given-names>
</name>
</person-group>
<article-title>Blockchain-Enabled iWellChain Framework Integration With the National Medical Referral System: Development and Usability Study</article-title>
<source>J Med Internet Res</source>
<year iso-8601-date="2019">2019</year>
<volume>21</volume>
<elocation-id>e13563</elocation-id>
<pub-id pub-id-type="doi">10.2196/13563</pub-id><pub-id pub-id-type="pmid">31799935</pub-id><pub-id pub-id-type="pmcid">PMC6920914</pub-id></element-citation>
</ref>
<ref id="B83">
<label>83</label>
<element-citation publication-type="web">
<article-title>Developing A digital COPD companion for Improving Lifestyle (DACIL) [Internet]</article-title>
<comment>NOW; c2024 [cited 2024 Apr 16]. Available from: <uri xlink:href="https://www.nwo.nl/en/projects/kich1gz0321023">https://www.nwo.nl/en/projects/kich1gz0321023</uri></comment>
</element-citation>
</ref>
<ref id="B84">
<label>84</label>
<element-citation publication-type="web">
<article-title>Real-world-data enabled assessment for health regulatory decision-making [Internet]</article-title>
<comment>[cited 2024 Apr 16]. Available from: <uri xlink:href="https://realm-ai.eu/">https://realm-ai.eu/</uri></comment>
</element-citation>
</ref>
<ref id="B85">
<label>85</label>
<element-citation publication-type="web">
<person-group person-group-type="author">
<name>
<surname>Havelange</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Dumontier</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Wouters</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Linde</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Townend</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Riedl</surname>
<given-names>A</given-names>
</name>
<etal>et al.</etal>
</person-group>
<article-title>LUCE: A Blockchain Solution for monitoring data License accoUntability and CompliancE</article-title>
<comment>arXiv:190802287v1. [Preprint]. 2019 [cited 2023 Nov 1]: [14 p.]. Available from: <uri xlink:href="https://arxiv.org/abs/1908.02287">https://arxiv.org/abs/1908.02287</uri></comment>
</element-citation>
</ref>
<ref id="B86">
<label>86</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Bayle</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Koscina</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Manset</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Perez-Kempner</surname>
<given-names>O</given-names>
</name>
</person-group>
<article-title>When Blockchain Meets the Right to Be Forgotten: Technology versus Law in the Healthcare Industry</article-title>
<comment>In: 2018 IEEE/WIC/ACM International Conference on Web Intelligence (WI). IEEE WIC ACM International Conference on Web Intelligence (WI); 2018 Dec 3-6; Santiago, Chile; 2018. pp. 788–92.</comment>
<pub-id pub-id-type="doi">10.1109/wi.2018.00133</pub-id></element-citation>
</ref>
</ref-list>
</back>
</article>