<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="review-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v14i1e76980</article-id><article-id pub-id-type="doi">10.2196/76980</article-id><article-categories><subj-group subj-group-type="heading"><subject>Review</subject></subj-group></article-categories><title-group><article-title>Blockchain Smart Contracts for Automating Clinical Trials: Systematic Review and Proposed System Architecture</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Sheikh</surname><given-names>Zara</given-names></name><degrees>BSc (Hons), MBBS, MRCS, MPH</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Samarth</surname><given-names>Gargi</given-names></name><degrees>MBBS, MMEd, MRCS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Jaffer</surname><given-names>Usman</given-names></name><degrees>MRCS, PhD, FRCS</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref></contrib></contrib-group><aff id="aff1"><institution>Imperial Vascular Unit, St Mary's Hospital, Imperial College Healthcare NHS Trust</institution><addr-line>Praed Street</addr-line><addr-line>London</addr-line><country>United Kingdom</country></aff><aff id="aff2"><institution>Harvard Health Systems Innovation Lab, Harvard University</institution><country>United States</country></aff><aff id="aff3"><institution>Anglia Ruskin University</institution><addr-line>Cambridge</addr-line><country>United Kingdom</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Pau</surname><given-names>Giovanni</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Dawood</surname><given-names>Omar A</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Usman Jaffer, MRCS, PhD, FRCS, Imperial Vascular Unit, St Mary's Hospital, Imperial College Healthcare NHS Trust, Praed Street, London, W2 1NY, United Kingdom, 44 7933513065; <email>u.jaffer@imperial.ac.uk</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>28</day><month>5</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e76980</elocation-id><history><date date-type="received"><day>05</day><month>05</month><year>2025</year></date><date date-type="rev-recd"><day>18</day><month>11</month><year>2025</year></date><date date-type="accepted"><day>17</day><month>02</month><year>2026</year></date></history><copyright-statement>&#x00A9; Zara Sheikh, Gargi Samarth, Usman Jaffer. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 28.5.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<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, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://medinform.jmir.org/2026/1/e76980"/><abstract><sec><title>Background</title><p>Blockchain technologies have revolutionized the financial sector through their ability to generate immutable, cryptographically secure records. Clinical trials and health care data possess several synergies with those of the financial sector, specifically pertaining to the importance of tamper-resistant recording of processes. The evolution of blockchain to autonomously execute tasks contingent upon predefined contractual terms via smart contracts (SCs) allows a dynamic chain of interlinked events to unfold independently and in sequence, with time-stamped records. In recent years, mistrust in clinical trial data has grown significantly. Recording the entire clinical trial lifecycle from application, registration, recruitment to conduct, finance management, statistical analysis, and reporting in an immutable, cryptographically secure ledger with SC execution of trial processes could limit the potential for human intervention and tampering. This would produce a time-stamped record of all events within the trial lifecycle. Leveraging the capabilities of SCs could alleviate recruitment challenges and address ongoing concerns regarding data transparency, ownership, and integrity that currently undermine clinical trial processes.</p></sec><sec><title>Objective</title><p>This study aimed to review the existing literature on SC applications in clinical trials and propose a system architecture for using SCs to automate key processes throughout the clinical trial lifecycle.</p></sec><sec sec-type="methods"><title>Methods</title><p>A systematic search was conducted in accordance with the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) guidelines, identifying peer-reviewed studies and open-source repositories pertaining to the implementation of SCs in clinical trials. Data were extracted specific to the stage of the trial lifecycle described, SC architecture, and technical specifications for real-world implementation. Data were synthesized to propose an architecture for automating clinical trial processes within the lifecycle using SCs.</p></sec><sec sec-type="results"><title>Results</title><p>A total of 144 records were screened; 10 studies met the inclusion criteria. Most implementations used private Ethereum-based networks (7/10, 70%). Reported applications included automated patient matching (5/10, 50%), consent management with dynamic permissioning (6/10, 60%), protocol enforcement and time-stamped audit logs (9/10, 90%), adverse event reporting (3/10, 30%), and financial or workflow automation (3/10, 30%). SC-based recruitment systems demonstrated rapid matching performance (eg, 6000 simulated patients matched in 2.13 s). However, all included systems were prototypes or simulations, and none were tested in real-world regulatory settings. Scalability, interoperability limitations, regulatory ambiguity (eg, General Data Protection Regulation right-to-erasure conflicts), and high infrastructural complexity were common gaps noted across studies.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Current evidence suggests that SCs can enhance transparency, traceability, and automation throughout the clinical trial lifecycle. However, the literature remains dominated by simulation-based prototypes, primarily Ethereum-dependent architectures, and lacks analyses of cost-effectiveness, governance, and integration with institutional workflows. Future research should evaluate hybrid architectures, develop interoperability standards, and assess regulatory and ethical implications in real deployments.</p></sec></abstract><kwd-group><kwd>blockchain</kwd><kwd>ethereum</kwd><kwd>data transparency</kwd><kwd>smart contracts</kwd><kwd>clinical trials</kwd><kwd>drug trials</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>The successful execution of clinical trials presents numerous challenges, particularly in patient recruitment, incentivization, and data integrity [<xref ref-type="bibr" rid="ref1">1</xref>]. Traditional trial infrastructures rely heavily on centralized data management systems that are vulnerable to breaches, human error, and manipulation&#x2014;undermining the credibility of clinical outcomes [<xref ref-type="bibr" rid="ref2">2</xref>]. Furthermore, low public awareness, privacy concerns, and fragmented health records impede the identification and recruitment of eligible participants, while nontransparent reimbursement mechanisms and burdensome administrative procedures contribute to poor retention rates [<xref ref-type="bibr" rid="ref3">3</xref>].</p><p>Simultaneously, data transparency remains a core concern. Inconsistent documentation, delayed reporting, and limited traceability can erode trust among regulators, sponsors, investigators, and patients [<xref ref-type="bibr" rid="ref4">4</xref>]. These operational and ethical concerns highlight the need for secure, automated, and transparent systems to support clinical research.</p><p>Blockchain technology offers a compelling solution to these challenges. As a decentralized, cryptographically secure ledger, blockchain enables transparent, tamper-resistant record-keeping across distributed networks. Once data are entered into the blockchain, it becomes immutable, ensuring the authenticity of records such as trial protocols, consent logs, and clinical outcomes [<xref ref-type="bibr" rid="ref5">5</xref>].</p><p>A powerful feature of blockchain systems is the use of smart contracts (SCs), self-executing agreements coded with predefined conditions [<xref ref-type="bibr" rid="ref6">6</xref>]. In the context of clinical trials, SCs can automate critical processes such as patient matching, consent acquisition, data permissioning, trial monitoring, and stakeholder coordination [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Their ability to enforce protocol adherence, timestamp events, and track user activity without intermediaries reduces administrative burdens while improving trust, traceability, and auditability.</p><p>This review explores the role of blockchain SCs in enhancing transparency, security, and efficiency across the clinical trial lifecycle. Through a systematic evaluation of peer-reviewed publications, preprints, and open-source implementations, we identify key use cases and architectural patterns in SC-based clinical trial systems. Specifically, we examine how SCs have been applied to optimize patient recruitment, streamline consent workflows, improve data sharing and permissions, automate trial governance, and uphold regulatory compliance.</p><p>By analyzing a diverse set of implementations, from academic prototypes to open-source repositories, this review highlights both the potential and the limitations of current blockchain applications in clinical research. In doing so, it offers a foundation for future innovations that leverage SCs to build more trustworthy, efficient, and patient-centric clinical trial ecosystems.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Search Strategy</title><p>A systematic literature review was conducted in accordance with the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) [<xref ref-type="bibr" rid="ref9">9</xref>] guidelines to identify peer-reviewed studies and open-source implementations relevant to the use of blockchain SCs in clinical trials. Two independent reviewers (ZS and GS) reviewed all eligible articles across 3 main sources: PubMed, arXiv, and GitHub, yielding 144 articles for screening, as well as manual cross-referencing of reference lists of screened papers. Conflicts were resolved through discussion. Only articles available in the English language were included. Studies were imported into the Covidence systematic review software.</p></sec><sec id="s2-2"><title>Eligibility Criteria</title><p>Studies were included if they reported on the use of blockchain technology in SCs within any stage of the clinical trial lifecycle. Examples of eligible studies included but were not limited to patient recruitment, consent acquisition, protocol adherence, interinstitutional data sharing, and outcome reporting. Both academic publications and open-source repositories were eligible for inclusion if they contained sufficient technical detail on system architecture, deployment, or simulation. Studies were excluded if they lacked detail on SCs, had inadequate clinical trial relevance, failed to detail implementation methodology, or reported on nonclinical applications.</p></sec><sec id="s2-3"><title>Data Extraction</title><p>Data were extracted from each included study using a standardized framework to capture study characteristics, blockchain platform, SC structure and function, use of off-chain storage systems, and targeted stage of the clinical trial cycle. Additional technical parameters such as programming language (eg, Solidity), performance simulation outcomes, stakeholder roles, and system testing (where reported) were also recorded. For GitHub repositories, associated documentation, proposals, and code structure were also reviewed.</p></sec><sec id="s2-4"><title>Outcomes and Definitions</title><p>The primary outcome was the identification and synthesis of architectural and functional use cases for SCs in clinical trial management. These included applications in trial setup, patient matching, consent and permissions, protocol enforcement, data integrity, real-time monitoring, and reporting. Data were synthesized to develop a system architecture for the integration of SCs into the clinical trial lifecycle.</p></sec><sec id="s2-5"><title>Study Quality</title><p>Academic studies were appraised for methodological rigor based on descriptive completeness, technical transparency, and real-world relevance. For open-source implementations, code completeness, versioning, accompanying documentation, and alignment with described functionality were assessed. Evaluation was performed independently by 2 reviewers (ZS and GS) and cross-checked for consistency. All final inclusions were agreed upon through consensus.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overview</title><p>In total, 144 records were identified using the search strategy (PubMed=80, GitHub=43, and arXiv=21). Following title and abstract screening, 20 publications (PubMed and arXiv) underwent full-text screening. From this, 6 publications met the inclusion criteria. Following reference screening, a further 2 publications were identified for full-text screening, and one met eligibility criteria. Of the 43 data repositories identified on GitHub, 5 repositories were evaluated after screening, and one was associated with a publication which was included in the final analysis. One further repository detailing the SC code, with an accompanying proposal document, was included in the final analysis. The full search strategy is included in the PRISMA flowchart for study inclusion, shown in <xref ref-type="fig" rid="figure1">Figure 1</xref>.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>PRISMA (Preferred Items for Systematic Reviews and Meta-Analyses) flow diagram.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e76980_fig01.png"/></fig><p>Studies detailed several stages of the trial process which could be optimized using SCs. The majority implemented private Ethereum-based blockchains, using Solidity, a programming language specifically designed for writing SCs in Ethereum [<xref ref-type="bibr" rid="ref10">10</xref>]. One used Quorum, an Ethereum-based blockchain platform, and another used Hyperledger Fabric. Across studies, SCs facilitated trial application [<xref ref-type="bibr" rid="ref2">2</xref>], patient recruitment [<xref ref-type="bibr" rid="ref3">3</xref>], consent [<xref ref-type="bibr" rid="ref4">4</xref>], and dynamic data permissions, allowing patients to grant or revoke access to data [<xref ref-type="bibr" rid="ref2">2</xref>] (<xref ref-type="table" rid="table1">Table 1</xref>). SCs were also used to randomize patients [<xref ref-type="bibr" rid="ref1">1</xref>], set up trial protocols [<xref ref-type="bibr" rid="ref3">3</xref>], and ensure data transparency [<xref ref-type="bibr" rid="ref5">5</xref>]. Other applications included trial workflow management [<xref ref-type="bibr" rid="ref5">5</xref>], reporting of serious adverse events (SAEs) [<xref ref-type="bibr" rid="ref3">3</xref>], statistical analysis and final reporting [<xref ref-type="bibr" rid="ref4">4</xref>], data exchange between institutions, and financial management [<xref ref-type="bibr" rid="ref1">1</xref>]. Several studies [<xref ref-type="bibr" rid="ref5">5</xref>] described a multilayer architecture with multiple SCs for different stages of clinical trial management (<xref ref-type="table" rid="table2">Table 2</xref>). Extracted data were synthesized to develop a novel system architecture for the integration of SCs in all aspects of the clinical trial lifecycle (<xref ref-type="fig" rid="figure2">Figure 2</xref>).</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Matrix of smart contract features used in clinical trial applications.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" colspan="2">Authors<break/>(years)</td><td align="left" valign="bottom">Blockchain</td><td align="left" valign="bottom">Public or<break/>private</td><td align="left" valign="bottom">Trial application</td><td align="left" valign="bottom">Trial protocol</td><td align="left" valign="bottom">Patient recruitment</td><td align="left" valign="bottom">Randomization double blinding</td><td align="left" valign="bottom">Consent</td><td align="left" valign="bottom">Dynamic data permissions</td><td align="left" valign="bottom">Data transparency and protocol adherence</td><td align="left" valign="bottom">Trial monitoring</td><td align="left" valign="bottom">Trial<break/>workflow<break/>management</td><td align="left" valign="bottom">Reporting adverse<break/>events</td><td align="left" valign="bottom">Data analysis or final<break/>reporting</td><td align="left" valign="bottom">Data<break/>exchange</td><td align="left" valign="bottom">Financial<break/>management</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Zhuang et al [<xref ref-type="bibr" rid="ref11">11</xref>]<break/>(2020)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">PR<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Maslove et al [<xref ref-type="bibr" rid="ref12">12</xref>]<break/>(2018)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">PR</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Zhuang et al [<xref ref-type="bibr" rid="ref11">11</xref>]<break/>(2020)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Zhuang et al [<xref ref-type="bibr" rid="ref13">13</xref>]<break/>(2022)</td><td align="left" valign="top">Quorum Blockchain</td><td align="left" valign="top">PU<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup>-PR</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top" colspan="2">Chaudhry et al [<xref ref-type="bibr" rid="ref3">3</xref>]<break/>(2019)</td><td align="left" valign="top">Hyperledger Fabric</td><td align="left" valign="top">PR</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Nugent et al [<xref ref-type="bibr" rid="ref8">8</xref>]<break/>(2016)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">PR</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Sendin and Miani [<xref ref-type="bibr" rid="ref14">14</xref>]<break/>(2021)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">PR</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Omar et al [<xref ref-type="bibr" rid="ref15">15</xref>]<break/>(2020)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">PR</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Fok [<xref ref-type="bibr" rid="ref16">16</xref>]<break/>(2022)</td><td align="left" valign="top">Polka Dot<break/>Substrate</td><td align="left" valign="top">PU</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="2">Hyclem [<xref ref-type="bibr" rid="ref17">17</xref>]<break/>(2019)</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">PR</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2014;</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>PR: private.</p></fn><fn id="table1fn2"><p><sup>b</sup>&#x2014;: feature not evaluated.</p></fn><fn id="table1fn3"><p><sup>c</sup>&#x2713;: feature evaluated.</p></fn><fn id="table1fn4"><p><sup>d</sup>PU: public.</p></fn></table-wrap-foot></table-wrap><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Blockchain applications in clinical trial management: comparative summary of key studies.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Authors<break/>(years)</td><td align="left" valign="bottom">Title</td><td align="left" valign="bottom">Region</td><td align="left" valign="bottom">Blockchain</td><td align="left" valign="bottom">Recruitment</td><td align="left" valign="bottom">Consent</td><td align="left" valign="bottom">Trial data management</td><td align="left" valign="bottom">Features</td><td align="left" valign="bottom">Technical</td><td align="left" valign="bottom">Outcomes</td></tr></thead><tbody><tr><td align="left" valign="top">Zhuang et al [<xref ref-type="bibr" rid="ref11">11</xref>]<break/>(2020)</td><td align="left" valign="top">Applying blockchain technology to enhance clinical trial recruitment</td><td align="left" valign="top">United States and Taiwan</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">Smart contract&#x2013;based patient-trial matching</td><td align="left" valign="top">On-chain E-signature using private key; encrypted identifiers</td><td align="left" valign="top">SCs<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> manage electronic health record, enrollment, and access control</td><td align="left" valign="top">Master contract for subject matching + individual trial contracts for enrollment and monitoring</td><td align="left" valign="top">Ethereum + remote procedure cell (RPC), EHR<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup> adapters, Solidity or NodeJS or SQL, ABI (application binary interface)-linked GUI<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup>, and private chain genesis block</td><td align="left" valign="top">Simulated recruitment (6000 patients); fast, secure, and scalable (~2.13 s match time)</td></tr><tr><td align="left" valign="top">Maslove et al [<xref ref-type="bibr" rid="ref12">12</xref>]<break/>(2018)</td><td align="left" valign="top">Using blockchain technology to manage clinical trials data: a proof-of-concept study</td><td align="left" valign="top">Canada</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">Web app for permission control (not focused on recruitment)</td><td align="left" valign="top">Dynamic consent via SCs (add or edit permissions)</td><td align="left" valign="top">Patients set data permissions; emphasizes autonomy</td><td align="left" valign="top">Two SCs: patient (permissions) and research (queries); web-based interface</td><td align="left" valign="top">Private Ethereum network, Solidity SCs, web UI<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup>, off-chain Oracle</td><td align="left" valign="top">Proof-of-concept; enabled auditability, patient control, and ethics board integration</td></tr><tr><td align="left" valign="top">Zhuang et al [<xref ref-type="bibr" rid="ref11">11</xref>]<break/>(2020)</td><td align="left" valign="top">Generalizable layered blockchain architecture for health care applications: development, case studies, and evaluation</td><td align="left" valign="top">United States</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">Simulated opt-in matching via SCs</td><td align="left" valign="top">Consent managed via GUI; immutably recorded on-chain</td><td align="left" valign="top">Off-chain EHR with on-chain metadata and data access traceability</td><td align="left" valign="top">3-layer architecture: transaction (SCs), interfacing (metadata exchange), application (trial tools and AI<sup><xref ref-type="table-fn" rid="table2fn5">e</xref></sup>)</td><td align="left" valign="top">Health info exchange via SCs; patient-controlled EHR access; blockchain-based authentication</td><td align="left" valign="top">Simulated recruitment + health information exchange (40,000 patients, 331K transactions); avg. 3.07s consent</td></tr><tr><td align="left" valign="top">Zhuang et al [<xref ref-type="bibr" rid="ref13">13</xref>]<break/>(2022)</td><td align="left" valign="top">Re-engineering a clinical trial management system using blockchain technology: system design, development, and case studies</td><td align="left" valign="top">China, United States, and Taiwan</td><td align="left" valign="top">Quorum + IPFS<sup><xref ref-type="table-fn" rid="table2fn6">f</xref></sup></td><td align="left" valign="top">Automated matching via SCs + digital consent</td><td align="left" valign="top">Digital signature verified and stored on-chain</td><td align="left" valign="top">End-to-end trial system; data in IPFS, hashes on-chain</td><td align="left" valign="top">Clinical trial management systems with SCs for 5 trial phases: planning, recruitment, conduct, reporting and finance</td><td align="left" valign="top">Quorum + Raft, SCs, IPFS, blockchain GUI, 6-node sponsor or testbed setup</td><td align="left" valign="top">21.6M transactions, 100% success, 335.4 TPS; scalable and secure in real-world scenarios</td></tr><tr><td align="left" valign="top">Chauhdhry et al [<xref ref-type="bibr" rid="ref3">3</xref>]<break/>(2019)</td><td align="left" valign="top">A blockchain framework for managing and monitoring data in multi-site clinical trials</td><td align="left" valign="top">United States</td><td align="left" valign="top">Hyperledger Fabric</td><td align="left" valign="top">Eligibility-based enrollment via subject channel</td><td align="left" valign="top">Private channel stores PHI<sup><xref ref-type="table-fn" rid="table2fn7">g</xref></sup>; access tied to deidentified info</td><td align="left" valign="top">Emphasis on data security and cost optimization</td><td align="left" valign="top">Audit trail, privacy, protocol enforcement, and adverse event reporting</td><td align="left" valign="top">Hyperledger Fabric (orderer or peer or client nodes), Practical Byzantine Fault Tolerance (PBFT) or proof-of-elapsed-time (PoET) consensus, private ledgers, auto chaincode</td><td align="left" valign="top">Meets NIH<sup><xref ref-type="table-fn" rid="table2fn8">h</xref></sup> guidelines; supports versioning, privacy, audit trails, adverse event tracking</td></tr><tr><td align="left" valign="top">Nugent et al [<xref ref-type="bibr" rid="ref8">8</xref>]<break/>(2016)</td><td align="left" valign="top">Improving data transparency in clinical trials using blockchain SCs</td><td align="left" valign="top">United Kingdom</td><td align="left" valign="top">Ethereum, IPFS, Swarm</td><td align="left" valign="top">SCs restrict recruitment to approved period</td><td align="left" valign="top">Encrypted documents on-chain; future use of zero knowledge proofs proposed</td><td align="left" valign="top">Protocol integrity and subject tracking via SCs</td><td align="left" valign="top">Immutable logs, tamper-proof protocol, auto-deploy contracts, subject tracking</td><td align="left" valign="top">Private Ethereum deployment for Tamiflu trial simulation, append-only logs, 14-s block time, historic query support</td><td align="left" valign="top">Private Ethereum trial logs; verifiable protocol adherence and timestamped data on number of participants and trials at any time</td></tr><tr><td align="left" valign="top">Omar et al [<xref ref-type="bibr" rid="ref15">15</xref>]<break/>(2020)</td><td align="left" valign="top">Ensuring protocol compliance and data transparency in clinical trials using blockchain SCs</td><td align="left" valign="top">United Arab Emirates</td><td align="left" valign="top">Ethereum, IPFS</td><td align="left" valign="top">Physician-controlled enrollment via verified addresses</td><td align="left" valign="top">Hashed consent via IPFS; traceable by Ethereum address</td><td align="left" valign="top">Staged trial process with IPFS-based immutable records</td><td align="left" valign="top">Decentralized control: SCs, IPFS, access via Ethereum addresses</td><td align="left" valign="top">Remix integrated development environment (IDE), solidity, open-source modular trial framework (eg, crossover, placebo)</td><td align="left" valign="top">Validated system with high compliance, traceability, and role-specific access</td></tr><tr><td align="left" valign="top">Sendin and Miani [<xref ref-type="bibr" rid="ref14">14</xref>]<break/>(2021)</td><td align="left" valign="top">Toward reliable and transparent vaccine phase III trials with SCs</td><td align="left" valign="top">Brazil</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">Randomized matching using commitment schemes</td><td align="left" valign="top">Implicit via registration; confirms status without disclosure</td><td align="left" valign="top">Fully on-chain illness registration and shot tracking</td><td align="left" valign="top">Double-blind randomization, fraud prevention, public auditability</td><td align="left" valign="top">Solidity+ Brownie+ Python frontend, open-source VaccSC repo</td><td align="left" valign="top">Transparent, tamper-proof Phase III vaccine trial protocol; publicor private use-ready</td></tr><tr><td align="left" valign="top">Fok [<xref ref-type="bibr" rid="ref16">16</xref>] (2022)</td><td align="left" valign="top">Clinical trial data smart contract</td><td align="left" valign="top">United States and Europe</td><td align="left" valign="top">Substrate, Polka dot</td><td align="left" valign="top">Enrollment via smart contract forms linked to wallets</td><td align="left" valign="top">Dynamic consent via smart contract; supports revocable access</td><td align="left" valign="top">Off-chain data with on-chain hashes and consent metadata</td><td align="left" valign="top">Wallet-linked form submission, verifiable logs, modular design with Rust + React</td><td align="left" valign="top">Rust SCs (Substrate), React frontend, Polkadot.js integration, optional IPFS</td><td align="left" valign="top">Full-stack decentralized trial system with modern Web3 stack</td></tr><tr><td align="left" valign="top">Hyclem<break/>(2019) [<xref ref-type="bibr" rid="ref17">17</xref>]</td><td align="left" valign="top">EssaisCliniques smart contract for blockchain-based clinical trial registration and feedback</td><td align="left" valign="top">Europe</td><td align="left" valign="top">Ethereum</td><td align="left" valign="top">Physician enrollment after registration</td><td align="left" valign="top">Consent implied via physician action; no cryptographic proof</td><td align="left" valign="top">On-chain patient-drug mapping and feedback via smart contract</td><td align="left" valign="top">Role-based access, drug-patient mapping, feedback submission via smart contract</td><td align="left" valign="top">Solidity (v0.4&#x2010;0.6), access via mappings, trial data in struct arrays, no encryption or access control</td><td align="left" valign="top">Basic proof-of-concept; enforces roles and feedback, lacks advanced security</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>SC: smart contract.</p></fn><fn id="table2fn2"><p><sup>b</sup>EHR: electronic health record.</p></fn><fn id="table2fn3"><p><sup>c</sup>GUI: graphical user interface.</p></fn><fn id="table2fn4"><p><sup>d</sup>UI: user interface.</p></fn><fn id="table2fn5"><p><sup>e</sup>AI: artificial intelligence.</p></fn><fn id="table2fn6"><p><sup>f</sup>IPFS: interplanetary file system.</p></fn><fn id="table2fn7"><p><sup>g</sup>PHI: protected health information.</p></fn><fn id="table2fn8"><p><sup>h</sup>NIH: National Institutes of Health.</p></fn></table-wrap-foot></table-wrap><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Proposed system architecture for smart contract integration in clinical trials. FDA: US Food and Drug Administration; MHRA: Medicines and Healthcare products Regulatory Agency; SC: smart contract.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e76980_fig02.png"/></fig></sec><sec id="s3-2"><title>Patient Recruitment</title><p>Recruitment for clinical trials is frequently challenging, often constrained by bureaucratic processes, multisite coordination requirements, and reliance on site-based recruiters. These inefficiencies hinder enrollment, delay trial timelines, and raise study costs. Patient enrollment is also hindered by a lack of awareness regarding available trials, exacerbated by inadequate outreach and poor trial visibility. Moreover, the necessity of additional hospital visits to discuss trial protocols can act as a further deterrent to participation.</p><p>SCs can be used to &#x201C;auto-match&#x201D; eligible patients to suitable clinical trials, thereby streamlining the recruitment process. Zhuang et al [<xref ref-type="bibr" rid="ref7">7</xref>] propose a 2-tier blockchain architecture consisting of a Master Smart Contract and multiple Trial Contracts. The Master Smart Contract is managed by a trusted authority, such as the US Food and Drug Administration (FDA), and is designed to match patients to clinical trials based on predefined inclusion and exclusion criteria. To ensure trial authenticity and regulatory compliance, each sponsor is required to submit a transaction to the authority. This transaction includes a National Clinical Trial identifier and supporting trial information for validation. Once the authority has verified the sponsor&#x2019;s identity and authenticity of the trial, it can execute the master smart contract, based on inclusion or exclusion criteria submitted by the sponsor. Patient information is inputted by clinical sites for patients who have opted in for consideration of trial participation. This enables the system to automatically match eligible patients to appropriate trials.</p><p>Once a patient is matched, they are notified by the authority that there is a clinical trial they may be eligible to participate in. Patient authorization is subsequently required to permit sponsor access to electronic health records (EHRs). Sponsors can then verify that the patient information supplied to the authority matches their clinical records and precise matching can be performed by the clinical site. If patients fully match, the sponsor can send the patient a transaction to enroll in the trial which can be authenticated using an eSignature. Patient records are then stored in the trial contract. Trial-specific contracts also contain information on trial protocols, sponsor details, and other relevant documentation. Importantly, trial contracts are only accessible to individuals who have agreed to participate in the trial.</p><p>The authors simulate the use of the master contract, demonstrating the ability to auto-match 1145 of 6000 patients to a trial in 2.13 seconds. Once patients have enrolled using a trial-specific contract, the sponsor can access data on the geographical location of patients and choose clinical trial sites convenient to the majority of subjects. This significantly attenuates the time and resources associated with patient screening processes, widening accessibility and trial awareness.</p></sec><sec id="s3-3"><title>Data Permissions and Consent</title><p>Lack of transparency on how health care data are used can lead to mistrust in the clinical trial process. Blocktrial, a web-based application developed by Maslove et al [<xref ref-type="bibr" rid="ref12">12</xref>], is a simple patient SC that enables patients to specify data sharing permissions. These permissions can be changed through an &#x201C;editPermissions&#x201D; feature on the patient SC, allowing patients to control who has access to their data. Once consent to data sharing is edited, an immutable record is generated on the blockchain. SCs allowing real-time editing of data sharing permissions promote patient autonomy and agency, and may enhance trust and transparency in how patient data are used.</p></sec><sec id="s3-4"><title>Protocol Compliance and Data Transparency</title><p>While patient-centric models offer valuable enhancements to consent management, broader systemic trust requires secure, verifiable collaboration between institutions involved in clinical trials. To this end, Nugent et al [<xref ref-type="bibr" rid="ref8">8</xref>] propose a private, permissioned Ethereum-based blockchain network jointly maintained by regulatory bodies (eg, Medicines and Healthcare products Regulatory Agency and FDA), pharmaceutical companies, and contract research organizations (CROs) [<xref ref-type="bibr" rid="ref8">8</xref>]. This network is intended to operate alongside traditional clinical data management systems, serving as a transactional, interorganizational record-keeping system. The authors illustrate that SCs can function as trusted administrative agents, enhancing transparency in clinical trial reporting by immutably recording key elements prone to manipulation, such as trial registration, protocols, subject enrollment, and clinical measurements. Within this architecture, Nugent et al [<xref ref-type="bibr" rid="ref8">8</xref>] outline a hierarchical SC model comprising two core types:</p><list list-type="order"><list-item><p>Regulator contract: this SC maintains a data structure that holds Clinical Trial Authorization details. It is controlled and updated by regulatory authorities such as the Medicines and Healthcare products Regulatory Agency or the FDA, based on off-chain licensing agreements. The contract also includes a container to store individual trial contracts.</p></list-item><list-item><p>Trial contract: this is executed by the CROs through a function in the regulator contract; this contract&#x2019;s deployment is governed by permissioning logic tied to the Clinical Trial Authorization data. It holds a data structure for storing the trial protocol, leveraging the interplanetary file system (IPFS) or Ethereum&#x2019;s Swarm protocol for large file storage. The contract enforces rules requiring the protocol to be deposited and trial endpoints defined before subject data can be added to the associated container.</p></list-item></list><p>Finally, a trial report is generated, reading all data from the blockchain, with details of each subject and data points that have been added with timestamping. Such systems can strengthen trust in clinical data integrity and improve the credibility of trial outcomes, ultimately enabling more informed medical decisions while helping to reduce patient risk and the financial burden caused by data manipulation.</p><p>By leveraging the cryptographic security of modern blockchain protocols, the system extends beyond simple proof-of-existence to support complex, tamper-resistant data handling. This work illustrates how SCs on the Ethereum blockchain can enhance transparency in clinical trial data management.</p><p>As part of their evaluation, Nugent et al [<xref ref-type="bibr" rid="ref8">8</xref>] deployed SCs on a private Ethereum blockchain to record synthetic data simulating clinical trials for Tamiflu, a medication stockpiled by the British government at a cost of US $575 million, despite 60% of the trial data being unpublished at the time. This test demonstrated the system&#x2019;s ability to provide real-time access to trial data, including participant numbers, number of trials, transaction addresses (linked to a CRO), and timestamps, while the blockchain&#x2019;s immutability allowed for retrieval of historical data, confirming the viability of using SCs to maintain transparent, verifiable records in clinical trials.</p><p>Similarly, Omar et al [<xref ref-type="bibr" rid="ref15">15</xref>] propose a blockchain-based clinical trial framework using Ethereum SCs and IPFS to enhance transparency, traceability, and automation in trial data management. IPFS is used to store trial documents, such as protocols, consent, SAE reports, and lab results, while their cryptographic hashes are securely linked to the blockchain via SCs. These SCs automate critical tasks at each stage of the trial process, such as Investigational New Drug submission, trial initiation, patient enrollment, monitoring, and SAE occurrence. At the end of the trial, the sponsor is required to submit an analysis to the SC, following which the FDA can approve the final outcome.</p><p>Each stakeholder (eg, FDA, institutional review board, sponsor, and physician) is assigned a unique Ethereum address, enabling secure, permissioned interactions with the contract&#x2019;s specific functions, such as submitting data or accessing trial updates. The contracts enforce role-based access controls, ensuring that only authorized individuals can perform actions within the system. Events, such as patient enrollment or trial stage completion, trigger real-time notifications to the relevant stakeholders, enhancing communication and transparency throughout the trial lifecycle. By automating these processes, SCs reduce administrative bottlenecks, improve data integrity, and ensure the auditability of every action taken in the clinical trial.</p><p>The authors successfully tested this SC framework across various scenarios in the clinical trial process. At each stage, from Investigational New Drug submission to final analysis, the system correctly executed role-specific tasks with access controls in place to prevent unauthorized actions. If an unauthorized action was attempted, the SC triggered an error, ensuring that only valid operations could be performed. Additionally, real-time notifications were generated for stakeholders at key points, such as patient enrollment or SAE reporting. The framework also enabled the retrieval of patient monitoring data per visit and correctly managed patient dropouts by preventing further data updates for removed participants. SAEs were reported by the principal investigator, reviewed by the institutional review board, and the final decisions were broadcast to all stakeholders through blockchain events. The simulated trial concludes with the FDA issuing a decision based on the final report, triggering an event that informs all stakeholders of the outcome, further demonstrating the ability of Ethereum SCs to manage clinical trials in a secure, transparent, and auditable manner.</p></sec><sec id="s3-5"><title>SCs in Vaccine Development</title><p>Mistrust in vaccine development, driven by concerns over data transparency and trial integrity, remains a major challenge to public confidence. Sendin et al [<xref ref-type="bibr" rid="ref14">14</xref>] attempt to address this through vaccine supply chain (VaccSC), using SCs to securely automate and coordinate key stages of a phase III vaccine trial while preserving double-blind conditions.</p><p>VaccSC leverages SCs on the Ethereum blockchain to automate randomization and requires the developer to specify the number of participants, the infected threshold (number of patients infected before allocations are revealed), minimum vaccine efficacy for approval, and the Ethereum address of clinics administering the vaccine in the SC before deployment. Once deployed by the vaccine developer, the SC governs the entire trial workflow. First, the developer distributes vaccine and placebo shots to clinics and records their association on-chain. Randomization is achieved through private number generation by the patient and the clinic; both numbers are then committed to the SC and combined to give a unique number, assigning a shot to the patient. Clinics then administer the shots and link unique shot identifiers to each patient within the contract, which the patient confirms. If a patient becomes ill, they report this directly to the contract. When a predefined infection threshold is met, the SC emits an event notifying the vaccine developer that the trial is complete. Using Ethereum addresses, the developer submits which patients received the control, allowing the contract to calculate how many received the actual vaccine. The contract then computes vaccine efficacy and approval status based on previously defined thresholds, making the results publicly accessible. By immutably capturing each step, from shot distribution, randomization, infection rates, and efficacy calculations, VaccSC uses SCs not only as a secure data ledger but also as an autonomous, unbiased administrator, reducing the risk of data manipulation and making the process transparent and accessible to the public. This methodology can be replicated in other drug development settings.</p></sec><sec id="s3-6"><title>Multilayered SC Architectures for Comprehensive Trial Oversight</title><p>Several studies describe a multilayered approach to clinical trial management. Zhuang et al [<xref ref-type="bibr" rid="ref11">11</xref>] initially proposed a 3-level architecture, consisting of a transaction, interface, and application layer. The transaction layer consists of 2 SCs, the EHR manager and the user manager. The EHR system automatically extracts patient ID, hospital ID, patient name, and a dataset related to patient health care use as an execution function of the SC on receiving a new EHR from a health institution. This data are then submitted to the blockchain. The user manager enables patients to grant institutions access to their metadata. Once access permission is verified, the blockchain adaptor will automatically retrieve the patient&#x2019;s metadata from the EHR manager, request the encrypted EHR dataset from the remote health facility in which it is stored, retrieve the encrypted data using dataset location information from the EHR metadata, and decrypt the data.</p><p>The interfacing layer enables secure data exchange between institutions through 4 functions. These include accessing external data, storing encrypted data off-chain, posting metadata and access requests to the blockchain via SCs, and transmitting encrypted data to authorized recipients. It retrieves metadata from the blockchain, verifies data integrity, and decrypts off-chain data as needed. The data retrieval and permission setting application programming interface calls on the SCs in the transaction layer to retrieve metadata from the blockchain and set access policies.</p><p>The application layer relies on the transaction SCs and interfacing layer to securely access data applications, which can be developed to interact with the preceding layers, such as data analytic tools to match patients to relevant trials or for patients to grant or revoke access to their records and track how they are being used.</p><p>Building on their earlier 3-layer architecture, the authors outline a more granular SC-based framework spanning five phases of the clinical trial process: (1) study planning, using a transparent electronic trial master file for protocol development; (2) study start-up, including patient recruitment and enrollment; (3) study conduct, supporting electronic data capture and monitoring of treatment safety and efficacy; (4) study closeout, incorporating statistical tools for reproducible analytics reporting; and (5) study finance, which leverages blockchain&#x2019;s cryptocurrency capabilities for payment and reimbursement [<xref ref-type="bibr" rid="ref13">13</xref>].</p><p>The study planning stage uses SCs to control access to electronic documents relevant to the trial, validate file consistency, and manage collaboration in electronic trial master file development, and the IPFS network is used for file storage and file indexing. Trial master file documents are identified in the SC at the start of the trial, and sponsors are required to add the blockchain account of users who are permitted to work on the file. The SC only permits 1 user at a time to work on a document, ensuring traceability and auditability of any modifications to trial documents. Once a user has finished working on a document, the blockchain adaptor will encrypt the document with a random new set of keys.</p><p>The study start-up phase builds on earlier work using SCs to automate matching and enhance recruitment. During the conduct phase, patient data are entered on an electronic case report form following each clinic visit; these are automatically hashed and stored in the IPFS. The SC determines whether a trial site has permission to store a patient&#x2019;s data. Once verified, the SC will send a visit ID and decryption key through the Quorum blockchain&#x2019;s private transaction. The sponsor will receive the decryption key and hash from the blockchain, and the blockchain adaptor will automatically decrypt and hash the records to compare with the hash stored on the blockchain, thereby identifying hash mismatches and data inconsistencies. Mismatches trigger alerts for investigation. The blockchain&#x2019;s immutability prevents overwriting erroneous data; instead, linking it to previous record hashes for validation.</p><p>The closeout phase involves encoding statistical analysis methods into an SC, with both the analyzed data and methods stored on the blockchain for reproducibility and result authentication. The final component pertains to finances, encoding a list of payable entities and predefined rates into an SC at the start of the study. This standardization reduces the risk of hidden fees during the trial and can be customized to the trial site to accommodate different rates. Encoding payables into the SCs can expedite the validation process. Furthermore, all financial transactions are recorded and time-stamped on the blockchain, allowing transparency around trial finances.</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>In recent years, public confidence in the validity of clinical research has been challenged, with multiple reports documenting that a substantial proportion of published studies contain methodological flaws or, in some cases, fabricated data [<xref ref-type="bibr" rid="ref2">2</xref>]. This erosion of trust has intensified interest in technologies capable of enhancing transparency, auditability, and accountability across the clinical trial lifecycle. Since Satoshi Nakamoto&#x2019;s [<xref ref-type="bibr" rid="ref18">18</xref>] 2008 white paper introduced a decentralized, time-stamped ledger for peer-to-peer financial exchange, blockchain technology has transformed the financial sector and has increasingly been explored for its potential applications in health care data management [<xref ref-type="bibr" rid="ref19">19</xref>]. The fundamental properties of decentralized data storage, cryptographic integrity, and tamper-resistant audit trails have drawn attention as possible mechanisms for strengthening trust in clinical trials.</p><p>The emergence of SCs extends these capabilities from static, &#x201C;proof-of-existence&#x201D; records to programmable logic, capable of automating key operational processes. SCs can function as autonomous administrators of trial workflows, implementing predefined rules, and eliminating opportunities for retrospective alteration. This embodies Lawrence Lessig&#x2019;s idea that &#x201C;code is law,&#x201D; such that the software logic itself becomes the governing framework for how stakeholders interact. Within the context of clinical trials, this has motivated the development of prototype systems that automate tasks ranging from eligibility screening and recruitment to dynamic consent management, protocol enforcement, data access tracking, and even automated reporting of results.</p><p>The studies included in this review demonstrate that many such applications are technically feasible in controlled environments. For example, SC-based recruitment workflows have been shown to match large numbers of simulated participants to trial criteria within seconds, and immutable audit trails can capture the entire sequence of procedural steps across the trial lifecycle. Dynamic data permissioning enabled by SCs may strengthen patient autonomy by allowing individuals to regulate access to their data in real time. The Ethereum blockchain, used in the majority of reviewed studies, has proven well-suited to these prototypes due to its mature SC infrastructure and developer ecosystem.</p><p>However, the findings also reveal a substantial gap between technical promise and real-world readiness. All identified implementations were prototypes or simulations, with no evidence of deployment in actual regulated trials. Assertions that clinical trial processes could be fully automated should therefore be interpreted with caution. Although the reviewed systems demonstrate the potential of SCs to automate constrained, deterministic processes, they do not address the complexities of real-world trial environments, such as the need for human judgment, protocol deviations, unstructured clinical data, and the heterogeneity of institutional workflows. Furthermore, Ethereum&#x2019;s dominance in the literature introduces platform bias, and few studies critically examine its well-known limitations, including fluctuating transaction costs, constraints on throughput, and the absence of built-in privacy protections.</p><p>Regulatory and legal challenges present even greater obstacles. The immutability of blockchain data conflicts with requirements under frameworks such as the General Data Protection Regulation, which grant individuals the right to erasure or correction of their personal data. While hybrid on-chain or off-chain architectures offer partial solutions, they also reintroduce trust dependencies that undermine decentralization. In addition, governments may impose abrupt regulatory changes or restrictions on blockchain platforms, as demonstrated by cryptocurrency bans in China and other jurisdictions. Such policy shifts pose risks to any clinical trial infrastructure built on blockchain technology. Adoption will therefore require not only technical adaptation but also careful consideration of governance, compliance, and stakeholder engagement.</p><p>Another critical gap in the current literature is the lack of evidence regarding stakeholder perspectives. No included study evaluated how patients, investigators, regulators, data monitors, or ethics committees perceive blockchain-based systems. The introduction of SCs could alter roles, responsibilities, and liabilities within clinical trials, and resistance to such changes may limit adoption. Moreover, the reviewed studies did not assess cost-effectiveness, integration with existing EHR or clinical trial management systems, or long-term sustainability, all of which are essential for real-world implementation.</p><p>Taken together, the findings indicate that blockchain SCs offer meaningful conceptual advantages, particularly in transparency, auditability, and automation, but their practical value remains unproven. Future progress will require a shift from idealized prototypes to rigorous evaluation within real clinical and regulatory environments, informed by legal expertise, operational realities, and stakeholder acceptance. The transition to blockchain-enabled clinical trials, if it occurs, will not be a purely technical transformation but a broader organizational and regulatory evolution involving new models of data governance and oversight.</p></sec><sec id="s4-2"><title>Limitations</title><p>This review is subject to several limitations. First, the number of eligible studies was small, and all relied on prototype or simulation-based evaluations, which limits the generalizability of the findings. Second, given the technical nature of the field, important developments may exist outside traditional academic publishing channels. Although GitHub repositories were included, some relevant implementations may not have met the inclusion criteria due to insufficient documentation. Third, the heterogeneity of study designs, blockchain platforms, and evaluation methods precluded quantitative synthesis and necessitated a qualitative approach. Fourth, because the field is evolving rapidly, newer implementations may have emerged after the final search date. Fifth, no study included direct engagement with regulators, trial sponsors, investigators, or patient groups, meaning the review could not assess acceptability or practical feasibility from a stakeholder perspective. These limitations reflect the early stage of this research area and reinforce the need for more comprehensive, empirically grounded studies.</p></sec><sec id="s4-3"><title>Future Directions</title><p>Future research should prioritize real-world pilot implementations that integrate SCs within existing clinical trial infrastructures, including EHRs, electronic data capture systems, and regulatory submission platforms. Development of privacy-preserving blockchain technologies, such as zero-knowledge proofs, secure multiparty computation, or trusted execution environments, will be essential for reconciling immutability with data protection requirements. Comparative studies evaluating different blockchain platforms, including permissioned and permissionless architectures, would help determine appropriate use cases and clarify the trade-offs between privacy, performance, and decentralization.</p><p>Hybrid systems that combine blockchain components with traditional clinical trial management frameworks offer a promising compromise and warrant further exploration. Researchers should also examine governance models for blockchain-enabled trials, ensuring that the encoded logic reflects clinical, ethical, and regulatory expectations. Economic evaluations will be essential to determine whether SC systems can deliver cost savings or improved efficiency relative to conventional solutions. Finally, engagement with stakeholders, including regulators, ethics committees, clinicians, patients, and data managers, will be vital to understand practical adoption barriers and align technical development with real-world priorities.</p></sec><sec id="s4-4"><title>Conclusions</title><p>Blockchain-based SCs have the potential to revolutionize the way clinical trials are operated, audited, and disseminated. Through unrealized resources and finance efficiencies, recruitment to trials, trial timelines, and conduct could be optimized. The immutable core of the blockchain ledger, greater data decentralization, and patient data ownership could lead to greater trust and transparency in the body of scientific work produced. This review demonstrates that nearly all elements of a clinical trial could be efficiently executed using SC and blockchain technologies.</p></sec></sec></body><back><notes><sec><title>Funding</title><p>The authors declared no financial support was received for this work.</p></sec></notes><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">CRO</term><def><p>contract research organization</p></def></def-item><def-item><term id="abb2">EHR</term><def><p>electronic health record</p></def></def-item><def-item><term id="abb3">FDA</term><def><p>US Food and Drug Administration</p></def></def-item><def-item><term id="abb4">IPFS</term><def><p> interplanetary file system</p></def></def-item><def-item><term id="abb5">PRISMA</term><def><p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p></def></def-item><def-item><term id="abb6">SAE</term><def><p>serious adverse event</p></def></def-item><def-item><term id="abb7">SC</term><def><p>smart contract</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Briel</surname><given-names>M</given-names> </name><name name-style="western"><surname>Elger</surname><given-names>BS</given-names> </name><name name-style="western"><surname>McLennan</surname><given-names>S</given-names> </name><name name-style="western"><surname>Schandelmaier</surname><given-names>S</given-names> </name><name name-style="western"><surname>von Elm</surname><given-names>E</given-names> </name><name name-style="western"><surname>Satalkar</surname><given-names>P</given-names> </name></person-group><article-title>Exploring reasons for recruitment failure in clinical trials: a qualitative study with clinical trial stakeholders in Switzerland, Germany, and Canada</article-title><source>Trials</source><year>2021</year><month>11</month><day>25</day><volume>22</volume><issue>1</issue><fpage>844</fpage><pub-id pub-id-type="doi">10.1186/s13063-021-05818-0</pub-id><pub-id pub-id-type="medline">34823582</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Van Noorden</surname><given-names>R</given-names> </name></person-group><article-title>Medicine is plagued by untrustworthy clinical trials. How many studies are faked or flawed?</article-title><source>Nature New Biol</source><year>2023</year><month>07</month><day>20</day><volume>619</volume><issue>7970</issue><fpage>454</fpage><lpage>458</lpage><pub-id pub-id-type="doi">10.1038/d41586-023-02299-w</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chaudhari</surname><given-names>N</given-names> </name><name name-style="western"><surname>Ravi</surname><given-names>R</given-names> </name><name name-style="western"><surname>Gogtay</surname><given-names>NJ</given-names> </name><name name-style="western"><surname>Thatte</surname><given-names>UM</given-names> </name></person-group><article-title>Recruitment and retention of the participants in clinical trials: challenges and solutions</article-title><source>Perspect Clin Res</source><year>2020</year><volume>11</volume><issue>2</issue><fpage>64</fpage><lpage>69</lpage><pub-id pub-id-type="doi">10.4103/picr.PICR_206_19</pub-id><pub-id pub-id-type="medline">32670830</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zarin</surname><given-names>DA</given-names> </name><name name-style="western"><surname>Tse</surname><given-names>T</given-names> </name></person-group><article-title>Medicine. Moving toward transparency of clinical trials</article-title><source>Science</source><year>2008</year><month>03</month><day>7</day><volume>319</volume><issue>5868</issue><fpage>1340</fpage><lpage>1342</lpage><pub-id pub-id-type="doi">10.1126/science.1153632</pub-id><pub-id pub-id-type="medline">18323436</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hasselgren</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kralevska</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gligoroski</surname><given-names>D</given-names> </name><name name-style="western"><surname>Pedersen</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Faxvaag</surname><given-names>A</given-names> </name></person-group><article-title>Blockchain in healthcare and health sciences-a scoping review</article-title><source>Int J Med Inform</source><year>2020</year><month>02</month><volume>134</volume><fpage>104040</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.104040</pub-id><pub-id pub-id-type="medline">31865055</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khan</surname><given-names>SN</given-names> </name><name name-style="western"><surname>Loukil</surname><given-names>F</given-names> </name><name name-style="western"><surname>Ghedira-Guegan</surname><given-names>C</given-names> </name><name name-style="western"><surname>Benkhelifa</surname><given-names>E</given-names> </name><name name-style="western"><surname>Bani-Hani</surname><given-names>A</given-names> </name></person-group><article-title>Blockchain smart contracts: applications, challenges, and future trends</article-title><source>Peer Peer Netw Appl</source><year>2021</year><volume>14</volume><issue>5</issue><fpage>2901</fpage><lpage>2925</lpage><pub-id pub-id-type="doi">10.1007/s12083-021-01127-0</pub-id><pub-id pub-id-type="medline">33897937</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhuang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Sheets</surname><given-names>LR</given-names> </name><name name-style="western"><surname>Shae</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>YW</given-names> </name><name name-style="western"><surname>Tsai</surname><given-names>JJP</given-names> </name><name name-style="western"><surname>Shyu</surname><given-names>CR</given-names> </name></person-group><article-title>Applying blockchain technology to enhance clinical trial recruitment</article-title><source>AMIA Annu Symp Proc</source><year>2019</year><volume>2019</volume><fpage>1276</fpage><lpage>1285</lpage><pub-id pub-id-type="medline">32308925</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nugent</surname><given-names>T</given-names> </name><name name-style="western"><surname>Upton</surname><given-names>D</given-names> </name><name name-style="western"><surname>Cimpoesu</surname><given-names>M</given-names> </name></person-group><article-title>Improving data transparency in clinical trials using blockchain smart contracts</article-title><source>F1000Res</source><year>2016</year><volume>5</volume><issue>2541</issue><fpage>2541</fpage><pub-id pub-id-type="doi">10.12688/f1000research.9756.1</pub-id><pub-id pub-id-type="medline">28357041</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Page</surname><given-names>MJ</given-names> </name><name name-style="western"><surname>McKenzie</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Bossuyt</surname><given-names>PM</given-names> </name><etal/></person-group><article-title>The PRISMA 2020 statement: an updated guideline for reporting systematic reviews</article-title><source>BMJ</source><year>2021</year><month>03</month><day>29</day><volume>372</volume><fpage>n71</fpage><pub-id pub-id-type="doi">10.1136/bmj.n71</pub-id><pub-id pub-id-type="medline">33782057</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Bauer</surname><given-names>DP</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Bauer</surname><given-names>DP</given-names> </name></person-group><article-title>Solidity</article-title><source>Getting Started with Ethereum: A Step-by-Step Guide to Becoming A Blockchain Developer</source><year>2022</year><publisher-name>Apress</publisher-name><fpage>13</fpage><lpage>16</lpage><pub-id pub-id-type="doi">10.1007/978-1-4842-8045-4_2</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhuang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>YW</given-names> </name><name name-style="western"><surname>Shae</surname><given-names>ZY</given-names> </name><name name-style="western"><surname>Shyu</surname><given-names>CR</given-names> </name></person-group><article-title>Generalizable layered blockchain architecture for health care applications: development, case studies, and evaluation</article-title><source>J Med Internet Res</source><year>2020</year><month>07</month><day>27</day><volume>22</volume><issue>7</issue><fpage>e19029</fpage><pub-id pub-id-type="doi">10.2196/19029</pub-id><pub-id pub-id-type="medline">32716300</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Maslove</surname><given-names>DM</given-names> </name><name name-style="western"><surname>Klein</surname><given-names>J</given-names> </name><name name-style="western"><surname>Brohman</surname><given-names>K</given-names> </name><name name-style="western"><surname>Martin</surname><given-names>P</given-names> </name></person-group><article-title>Using blockchain technology to manage clinical trials data: a proof-of-concept study</article-title><source>JMIR Med Inform</source><year>2018</year><month>12</month><day>21</day><volume>6</volume><issue>4</issue><fpage>e11949</fpage><pub-id pub-id-type="doi">10.2196/11949</pub-id><pub-id pub-id-type="medline">30578196</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhuang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>L</given-names> </name><name name-style="western"><surname>Gao</surname><given-names>X</given-names> </name><etal/></person-group><article-title>Re-engineering a clinical trial management system using blockchain technology: system design, development, and case studies</article-title><source>J Med Internet Res</source><year>2022</year><month>06</month><day>27</day><volume>24</volume><issue>6</issue><fpage>e36774</fpage><pub-id pub-id-type="doi">10.2196/36774</pub-id><pub-id pub-id-type="medline">35759315</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="other"><person-group person-group-type="author"><name name-style="western"><surname>Sendin</surname><given-names>I</given-names> </name><name name-style="western"><surname>Miani</surname><given-names>RS</given-names> </name></person-group><article-title>Towards reliable and transparent vaccine phase III trials with smart contracts</article-title><source>arXiv</source><comment>Preprint posted online on  Feb 13, 2021</comment><pub-id pub-id-type="doi">10.48550/arXiv.2102.07022</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Omar</surname><given-names>IA</given-names> </name><name name-style="western"><surname>Jayaraman</surname><given-names>R</given-names> </name><name name-style="western"><surname>Salah</surname><given-names>K</given-names> </name><name name-style="western"><surname>Simsekler</surname><given-names>MCE</given-names> </name><name name-style="western"><surname>Yaqoob</surname><given-names>I</given-names> </name><name name-style="western"><surname>Ellahham</surname><given-names>S</given-names> </name></person-group><article-title>Ensuring protocol compliance and data transparency in clinical trials using blockchain smart contracts</article-title><source>BMC Med Res Methodol</source><year>2020</year><month>09</month><day>7</day><volume>20</volume><issue>1</issue><fpage>224</fpage><pub-id pub-id-type="doi">10.1186/s12874-020-01109-5</pub-id><pub-id pub-id-type="medline">32894068</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Fok</surname><given-names>C</given-names> </name></person-group><article-title>Clinical trial data smart contract</article-title><year>2022</year><access-date>2026-05-05</access-date><publisher-name>GitHub</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://github.com/christopherfkk/clinical-trial-data-smart-contract">https://github.com/christopherfkk/clinical-trial-data-smart-contract</ext-link></comment></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="report"><person-group person-group-type="author"><collab>Hyclem</collab></person-group><article-title>Blockchain</article-title><year>2024</year><access-date>2026-05-05</access-date><publisher-name>GitHub</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://github.com/hyclem/blockchain/blob/master/README.md">https://github.com/hyclem/blockchain/blob/master/README.md</ext-link></comment></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="report"><article-title>Bitcoin: a peer-to-peer electronic cash system</article-title><year>2008</year><access-date>2026-03-05</access-date><publisher-name>Satoshi Nakamoto</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.ussc.gov/sites/default/files/pdf/training/annual-national-training-seminar/2018/Emerging_Tech_Bitcoin_Crypto.pdf">https://www.ussc.gov/sites/default/files/pdf/training/annual-national-training-seminar/2018/Emerging_Tech_Bitcoin_Crypto.pdf</ext-link></comment></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Haleem</surname><given-names>A</given-names> </name><name name-style="western"><surname>Javaid</surname><given-names>M</given-names> </name><name name-style="western"><surname>Singh</surname><given-names>RP</given-names> </name><name name-style="western"><surname>Suman</surname><given-names>R</given-names> </name><name name-style="western"><surname>Rab</surname><given-names>S</given-names> </name></person-group><article-title>Blockchain technology applications in healthcare: an overview</article-title><source>International Journal of Intelligent Networks</source><year>2021</year><volume>2</volume><fpage>130</fpage><lpage>139</lpage><pub-id pub-id-type="doi">10.1016/j.ijin.2021.09.005</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Checklist 1</label><p>PRISMA checklist.</p><media xlink:href="medinform_v14i1e76980_app1.pdf" xlink:title="PDF File, 613 KB"/></supplementary-material></app-group></back></article>